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 : 21-07-2017

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

  • ora-16235 : DDL skipped because import has occurred
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-31154 : invalid XML document
  • ora-07586 : spdcr: $SEARCH failure
  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-23431 : wrong state: string
  • ora-02047 : cannot join the distributed transaction in progress
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-30551 : The index depends on a package/type body which does not exist
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-29903 : error in executing ODCIIndexFetch() routine
  • ora-39955 : invalid PL/SQL warning message number
  • ora-14017 : partition bound list contains too many elements
  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-06721 : TLI Driver: spurious client req
  • ora-26676 : Table 'string.string' has string columns in the LCR and string columns in the replicated site
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-30553 : The function is not deterministic
  • ora-29307 : datafile string error, string
  • ora-19576 : datafile string not defined in control file
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-00569 : Failed to acquire global enqueue.
  • ora-12046 : cannot use trusted constraints for refreshing remote MV
  • ora-12724 : regular expression corrupt
  • ora-16126 : loading table or sequence string
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-12511 : TNS:service handler found but it is not accepting connections
  • ora-29824 : operator is invalid
  • 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.