ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

Cause : sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

update : 24-04-2017

ORA-27192 - skgfcls: sbtclose2 returned error - failed to close file
ORA-27192 - skgfcls: sbtclose2 returned error - failed to close file

  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-28221 : REPLACE not specified
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • ora-30015 : previously offlined undo tablespace 'string' is still pending
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-02448 : constraint does not exist
  • ora-14107 : partition specification is required for a partitioned object
  • ora-25461 : rule set not specified
  • ora-00302 : limit of string logs exceeded
  • ora-29909 : label for the ancillary operator is not a literal number
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-12589 : TNS:connection not bequeathable
  • ora-23331 : column group string does not exist
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-31062 : Cannot delete an unsaved resource
  • ora-02094 : replication option not installed
  • ora-38783 : Instance recovery required.
  • ora-22873 : primary key not specified for primary key based object table
  • ora-38421 : attribute string already exists
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-16512 : parameter exceeded maximum size limit
  • ora-36680 : (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
  • ora-19932 : control file is not clone or standby
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-22332 : a dependent object in schema "string" has errors. string
  • ora-14263 : new subpartition name must differ from that of any other subpartition of the object
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-16045 : circular archive log destination dependency chain
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.