Oracle 11g Error Codes and Solution Suggestions from ORA-09900 to ORA-10000
- ORA-09908: slkmnm: gethostname returned error code.
- Cause: The system call gethostname returned an error.
- Action: This is most likely an internal error. Make sure gethostname is successful in other contexts, and if so contact Oracle support.
- ORA-09909: Malloc of scratch buffer failed.
- Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that ORACLE attempted to allocate.
- Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
- ORA-09910: Unable to find ORACLE password file entry for user.
- Cause: No entry exists for the user in the ORACLE password file.
- Action: Have the database administrator install a password entry by running orapasswd.
- ORA-09911: Incorrect user password.
- Cause: The password entered by the user was incorrect.
- Action: Enter the correct password.
- ORA-09912: Malloc of name buffer(s) failed.
- Cause: ORACLE was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users.
- Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
- ORA-09913: Malloc of dummy name failed.
- Cause: ORACLE was unable to allocate memory for the user name that is to to be used in the encryption of the user’s password.
- Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
- ORA-09914: Unable to open the ORACLE password file.
- Cause: ORACLE could not open the password file for reading.
- Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact ORACLE customer support.
- ORA-09915: Password encryption failed.
- Cause: ORACLE was unable to encrypt a password.
- Action: This is an internal error – contact ORACLE customer support.
- ORA-09916: Required password was not specified.
- Cause: A user attempted to connect as “internal,” but did not specify a password.
- Action: Connect as internal again and specify a password.
- ORA-09918: Unable to get user privileges from SQL*Net
- Cause: ORACLE was unable to retrieve the user’s privilege set from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support.
- ORA-09919: Unable to set label of dedicated server
- Cause: ORACLE was unable to set the label of the dedicated to server to the required value.
- Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the oracle executable. It should have at least “allowmacaccess” privilege.
- ORA-09920: Unable to get sensitivity label from connection
- Cause: ORACLE was unable to retrieve the user’s sensitivity label from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support.
- ORA-09921: Unable to get information label from connection
- Cause: ORACLE was unable to retrieve the user’s information label from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support.
- ORA-09922: Can’t spawn process – background log directory not created properly
- Cause: ORACLE was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.
- Action: Examine the directory pointed to by the initialization parameter “background_dump_dest”. Make sure that all of the following is true:
- 1. The directory exists.
- 2. The name indeed points to a directory, and is not a file.
- 3. The directory is accessible and writable to the ORACLE user.
- ORA-09923: Can’t spawn process – user log directory not created properly
- Cause: ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.
- Action: Examine the directory pointed to by the initialization parameter “user_dump_dest”. Make sure that all of the following is true:
- 1. The directory exists.
- 2. The name indeed points to a directory, and is not a file.
- 3. The directory is accessible and writable to the ORACLE user.
- ORA-09924: Can’t spawn process – core dump directory not created properly
- Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.
- Action: Examine the directory pointed to by the initialization parameter “core_dump_dest”. Make sure that all of the following is true:
- 1. The directory exists.
- 2. The name indeed points to a directory, and is not a file.
- 3. The directory is accessible and writable to the ORACLE user.
- ORA-09925: Unable to create audit trail file
- Cause: ORACLE was not able to create the file being used to hold audit trail records.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support.
- ORA-09926: Unable to set effective privilege set of the server
- Cause: A dedicated server was unable to set it’s own privilege set.
- Action: Check the privileges granted to the ORACLE executable. It must have at least “allowmacacess” privilege.
- ORA-09927: Unable to set label of server
- Cause: ORACLE was not able to set the label of a server to a new value.
- Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has “allowmacaccess” privilege.
- ORA-09928: Unable to restore the label of server
- Cause: ORACLE was unable to restore the label of the server to the value that it had before raising it to database high.
- Action: This is an internal error – contact ORACLE support.
- ORA-09929: GLB of two labels is invalid
- Cause: The result of a greatest lower bound operation on two labels was not valid.
- Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
- ORA-09930: LUB of two labels is invalid
- Cause: The result of a least upper bound operation on two labels was not valid.
- Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
- ORA-09931: Unable to open ORACLE password file for reading
- Cause: An attempt to open a password file for reading failed.
- Action: Make sure that the permissions on the file have not been changed so that the ORACLE user cannot open it.
- ORA-09932: Close of ORACLE password file failed.
- Cause: An attempt to close a password file failed.
- Action: Check the UNIX error number for the specific reason.
- ORA-09933: Deletion of old password file failed.
- Cause: The removal of the old password file failed.
- Action: Check the UNIX error number for the specific reason.
- ORA-09934: Link of current password file to old failed.
- Cause: ORACLE was unable to create a link so that the old password file could be saved.
- Action: Check the UNIX error number for the specific reason.
- ORA-09935: Unlink of current password file failed.
- Cause: ORACLE was unable to complete the saving of the current password file.
- Action: Check the UNIX error number for the specific reason.
- ORA-09936: Open of ORACLE password file for write failed.
- Cause: ORACLE was unable to create a password file.
- Action: Check the UNIX error number for the specific reason.
- ORA-09937: Chmod of ORACLE password file failed.
- Cause: ORACLE was unable to change a password file to be readonly.
- Action: Check the UNIX error number for the specific reason.
- ORA-09938: Save of signal handlers failed.
- Cause: ORACLE was unable to save the previous values of selected signal handlers.
- Action: This is an internal error. Contact ORACLE support.
- ORA-09939: Restoration of signal handlers failed.
- Cause: ORACLE was unable to restore the previous values of selected signal handlers.
- Action: This is an internal error. Contact ORACLE support.
- ORA-09940: ORACLE password file header is corrupt
- Cause: The header of one of the password files was not in the format that ORACLE expected.
- Action: Check the headers of both files. The header should be in the format “FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N” where N is a number. Remove the corrupt file(s) and re-run “orapasswd”.
- ORA-09941: Version of orapasswd or installer is older than file.
- Cause: The version of orapasswd or installer that is being run is older than that of the ORACLE password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.
- Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file.
- ORA-09942: Write of ORACLE password file header failed.
- Cause: The attempt to write out the header of the ORACLE password file failed.
- Action: Check the operating system error number. It is possible that the file system became full.
- ORA-09943: Allocation of memory for password list component failed.
- Cause: When it is building a list of password file entries, ORACLE allocates memory for various components. One of the allocations failed.
- Action: Check the operating system error number. The system has probably run out of memory.
- ORA-09944: Password entry is corrupt.
- Cause: An entry in an ORACLE password file was not in the format that ORACLE expected.
- Action: Removed the corrupt file(s) and re-run “orapasswd.”
- ORA-09945: Unable to initialize the audit trail file
- Cause: ORACLE unable to write header information to the file being used as the audit trail.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support.
- ORA-09946: File name too long for buffer
- Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.
- Action: Use a shorter file name.
- ORA-09947: Unable to allocate connection attributes structure
- Cause: ORACLE was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The “Additional Information” field holds the number of bytes that ORACLE attempted to allocate.
- Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE customer support.
- ORA-09948: Process information label retrieval failed.
- Cause: ORACLE was unable to get the information label for a process.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
- ORA-09949: Unable to get client operating system privileges
- Cause: ORACLE was unable to get the operating system privileges for the client process.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
- ORA-09950: Unable to get server operating system privileges
- Cause: ORACLE was unable to get its privileges from the operating system.
- Action: This is an error that should never happen. Contact ORACLE customer support.
- ORA-09951: Unable to create file
- Cause: ORACLE was unable to create a file.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
- ORA-09952: scgcmn: lk_open_convert unexpected return: open failed
- Cause: The distributed lock manager returned an unexpected value
- Action: Check for system error message and refer to the distributed lock manager documentation or contact your customer support representative.
- ORA-09953: scggc: unexpected return of a lock convert
- Cause: The distributed lock manager returned an unexpected value
- Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
- ORA-09954: scgcc: unexpected return status to callback of lock close
- Cause: The distributed lock manager returned an unexpected value
- Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
- ORA-09955: scgcan: unexpected return status when canceling a lock
- Cause: DLM system service x returned an unexpected value
- Action: Check for system error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
- ORA-09956: scgcm: unexpected lock status condition
- Cause: A global locking system service returned an unexpected value.
- Action: Check for system error message (if any) and refer to refer to the distributed lock manager documentation or contact your customer support representative.
- ORA-09957: Unable to send termination request to IMON
- Cause: The attempt to send a termination signal to IMON failed.
- Action: This is an internal error, contact ORACLE support.
- ORA-09958: IMON: two processes with the same ORACLE pid are active
- Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot.
- Action: This is an internal error, contact ORACLE support.
- ORA-09959: IMON: deletion of a process failed.
- Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found.
- Action: This is an internal error, contact ORACLE support.
- ORA-09960: Unable to establish signal handler for termination signal
- Cause: ORACLE was unable to set up a handler for the signal used to notify it that the instance was shutting down.
- Action: This is an internal error, contact ORACLE support.
- ORA-09961: Unable to restore termination signal handler
- Cause: ORACLE failed to set the handler for the termination signal to its previous value.
- Action: This is an internal error, contact ORACLE support.
- ORA-09966: falure in translation while expanding ?/dbs/lk for lock file
- Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the database mount lock or the instance startup/shutdown lock.
- Action: Check additional return errors for more information.
- ORA-09967: unable to create or open lock file
- Cause: Oracle failed, when making an open system call, inorder to acquire a file lock used by the database mount lock or the instance startup/shutdown lock.
- Action: Check errno for more information.
- ORA-09968: unable to lock file
- Cause: The system call for locking a file returned an error when trying to acquire a database mount lock or the instance startup/shutdown lock.
- Action: Check errno for more information.
- ORA-09969: unable to close or remove lock file
- Cause: The close system call or unlink system call returned an error.
- Action: Check errno for more information.
- ORA-09974: skxfidini: Error Initializing SDI Channel
- Cause: The process was unable to initialize the SDI channel properly.
- Action: Correct the operating system error and retry the operation.
- ORA-09975: kxfspini: Error Initializing SDI Process
- Cause: The process was unable to attach to the SDI channel.
- Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.
- ORA-09976: skxfqdini: Error Creating Port
- Cause: The process was unable to create a communications endpoint.
- Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.
- ORA-09977: skxfqhini: Error Connecting
- Cause: The process was unable to connect to another endpoint.
- Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.
- ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.
- Cause: The process was unable to disconnect cleanly from another endpoint.
- Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
- ORA-09979: skxfqhsnd: Error Sending a message to another endpoint
- Cause: The process was unable to send a message to an existing endpoint.
- Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
- ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint
- Cause: The process encountered an error while trying to receive a message.
- Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
- ORA-09981: skxfqdreg: Error Adding a page to the SDI buffer pool
- Cause: The process was unable to add a page to the SDI buffer pool.
- Action: Correct the operating system error and retry the operation.
- ORA-09982: skxfqddrg: Error Removing a page from the SDI buffer pool
- Cause: The process was unable to remove a page to the SDI buffer pool.
- Action: Correct the operating system error and retry the operation.
- ORA-09983: skxfidsht: Error shutting down SDI channel
- Cause: The process was unable shut down the SDI channel
- Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.
- ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist
- Cause: file does not exist or is not accessible
- Action: Restart the instance to create the SGA definition file.
- ORA-09985: SGA definition file could not be read
- Cause: UNIX read() operation failed
- Action: check errno and take appropriate action.
- ORA-09986: wrong number of bytes read from SGA definition file
- Cause: Struct skgmsdef size differs from no. of bytes read from SGA file
- Action: Compare the two struct definitions and ensure that they are identical in size and structure.
- ORA-09987: unable to attach to SGA in READ-ONLY mode
- Cause: The instance is not up, or SGA segments are not read-accessible
- Action: Verify that the instance is up and read permissions for the SGA segments are set.
- ORA-09988: error while detaching SGA
- Cause: skgmsdef struct is corrupted and/or segment addresses are modified
- Action: Safely shut down instance and mount SGA segments again.
- ORA-09989: attempt to use invalid skgmsdef struct pointer
- Cause: Pointer to skgmsdef struct used without validating it
- Action: Assign a valid address to the skgmsdef struct pointer before using it.