ORA-27015: skgfcls: failed to close the file

Cause : sbtclose returned error, additional information indicates error returned from sbtclose

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

verify that vendor's storage subsystem product is operating correctly

update : 28-07-2017

ORA-27015 - skgfcls: failed to close the file
ORA-27015 - skgfcls: failed to close the file

  • ora-02780 : Name given for the core dump directory is invalid
  • ora-12844 : cluster reconfiguration in progress
  • ora-01241 : an external cache has died
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-33261 : (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number.
  • ora-32804 : invalid value string, string should have form string
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-16074 : ARCH processes must be active
  • ora-19644 : datafile string: incremental-start SCN is prior to resetlogs SCN string
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-24095 : invalid transformation, source type does not match that of the queue
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • ora-29357 : object string already exists
  • ora-24410 : scrollable cursor max size exceeded
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-01107 : database must be mounted for media recovery
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-19661 : datafile string could not be verified
  • ora-01567 : dropping log string would leave less than 2 log files for instance string (thread string)
  • ora-16585 : illegal operation on a primary site
  • ora-24402 : error occured while creating connections in the pool
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-19707 : invalid record block number - string
  • ora-19581 : no files have been named
  • ora-02819 : Write failed
  • 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.