ORA-27060: could not set close-on-exec bit on file

Cause : cftn lystsmec la lerutnrdee rrro

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

hcce krenro

update : 24-04-2017
ORA-27060

ORA-27060 - could not set close-on-exec bit on file
ORA-27060 - could not set close-on-exec bit on file

  • ora-39708 : component 'string' not a string component
  • ora-01583 : unable to get block size of control file to be backed up
  • ora-13434 : GeoRaster metadata cellRepresentation error
  • ora-24099 : operation not allowed for 8.0 compatible queues
  • ora-33064 : (XSAGDNGL31) In AGGMAP workspace object, the hierarchy dimension QDR workspace object cannot refer to the related dimension of the relation.
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-15007 : name is already used by an existing template
  • ora-07707 : error in archive text: need tape label name
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-37155 : OLAP API bootstrap error: (case string)
  • ora-02089 : COMMIT is not allowed in a subordinate session
  • ora-14261 : partition bound may not be specified when adding this Hash partition
  • ora-40290 : model incompatible with data mining function
  • ora-07710 : sksaprs: file name buffer too small
  • ora-25117 : MIN/MAX/Block Number expected
  • ora-12659 : Error received from other process
  • ora-29279 : SMTP permanent error: string
  • ora-30068 : Internal Event to turn on nested
  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-29805 : missing COLUMN keyword
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-23321 : Pipename may not be null
  • ora-02850 : File is closed
  • ora-09960 : Unable to establish signal handler for termination signal
  • ora-29267 : illegal call
  • ora-06121 : NETTCP: access failure
  • ora-10652 : Object has on-commit materialized views
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-13705 : There was a instance shutdown/startup between the snapshots in the range [string, string].
  • ora-09260 : sigpidu: error obtaining process id
  • 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.