Oracle Error Messages: 02/11/12

Saturday 11 February 2012

ORA-09925: Unable to create audit trail file

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-09924: Can t spawn process - core dump directory not created properly

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-09923: Can t spawn process - user log directory not created properly

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-09922: Can t spawn process - background log directory not created properly

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-09921: Unable to get information label from connection

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-09920: Unable to get sensitivity label from connection

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-09919: Unable to set label of dedicated server

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-09918: Unable to get user privileges from SQL*Net

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-09916: Required password was not specified.

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-09915: Password encryption failed.

ORA-09915: Password encryption failed.

Cause: ORACLE was unable to encrypt a password.

Action: This is an internal error - contact ORACLE customer support.

ORA-09914: Unable to open the ORACLE password file.

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-09913: Malloc of dummy name failed.

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-09912: Malloc of name buffer(s) failed.

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-09911: Incorrect user password.

ORA-09911: Incorrect user password.

Cause: The password entered by the user was incorrect.

Action: Enter the correct password.

ORA-09910: Unable to find ORACLE password file entry for user.

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-09909: Malloc of scratch buffer failed.

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-09908: slkmnm: gethostname returned error code.

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-09890: osnTXtt: malloc failed

ORA-09890: osnTXtt: malloc failed

Cause: The txipx driver failed to allocate enough heap space for its context area buffers.

Action: Contact your customer support representative.

ORA-09889: osnTXtt: access error on oracle executable

ORA-09889: osnTXtt: access error on oracle executable

Cause: The txipc driver could not access the oracle executable.

Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME or bin path.

ORA-09888: osnTXtt: txipc channel creation failed

ORA-09888: osnTXtt: txipc channel creation failed

Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator.

ORA-09886: osnTXtt: translation error while expanding txipc.trc.

ORA-09886: osnTXtt: translation error while expanding txipc.trc.

Cause: Failure of sltln(txipc.trc) while creating debug channel.

Action: Check additional return error for more information.

ORA-09885: osnTXtt: cannot create TXIPC channel

ORA-09885: osnTXtt: cannot create TXIPC channel

Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.

ORA-09884: Two Task interface: SID doens t match current PU

ORA-09884: Two Task interface: SID doens t match current PU

Cause: You are trying to start oracle on another PU than you configured oracle on or there is no entry for this SID in oratab file.

Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID.

ORA-09883: Two Task interface: oratab file does not exist

ORA-09883: Two Task interface: oratab file does not exist

Cause: The oratab file does not exist.

Action: Install oracle before you use it or recreate the oratab file.

ORA-09882: sstasfre or sstasdel: shmctl error, unable to remove tas shm page

ORA-09882: sstasfre or sstasdel: shmctl error, unable to remove tas shm page

Cause: Error in shmctl.

Action: Check errno returned.

ORA-09881: sstasfre or sstasdel: shmdt error, unable to detach tas read page

ORA-09881: sstasfre or sstasdel: shmdt error, unable to detach tas read page

Cause: Error in shmdt.

Action: Check errno returned.

ORA-09880: sstasfre or sstasdel: shmdt error, unable to detach tas write page

ORA-09880: sstasfre or sstasdel: shmdt error, unable to detach tas write page

Cause: Error in shmdt.

Action: Check errno returned.

ORA-09879: sstascre or sstasat: shmat error, unable to attach tas read page

ORA-09879: sstascre or sstasat: shmat error, unable to attach tas read page

Cause: Error in shmat.

Action: Check errno returned.Verify that enough shared memory is available on the system.

ORA-09878: sstascre or sstasat: shmat error, unable to attach tas write page

ORA-09878: sstascre or sstasat: shmat error, unable to attach tas write page

Cause: Error in shmat.

Action: Check errno returned.Verify that enough shared memory is available on the system.

ORA-09877: sstascre: shmget error, unable to get a shared memory segment.

ORA-09877: sstascre: shmget error, unable to get a shared memory segment.

Cause: Error in shmget.

Action: Check errno returned. Verify that enough shared memory is available on the system.

ORA-09876: TASDEF_CLOSE: unable to close ? or dbs or tasdef.dbf file.

ORA-09876: TASDEF_CLOSE: unable to close ? or dbs or tasdef.dbf file.

Cause: Close system call returned an error.

Action: Check errno returned. Possible operating system failure.

ORA-09875: TASDEF_WRITE: write error when writing ? or dbs or tasdef.dbf file.

ORA-09875: TASDEF_WRITE: write error when writing ? or dbs or tasdef.dbf file.

Cause: Write call failed.

Action: Check errno returned. Possibly out of space on device.

ORA-09874: TASDEF_READ: read error, unable to read tasdef.dbf file.

ORA-09874: TASDEF_READ: read error, unable to read tasdef.dbf file.

Cause: Read system call returned an error when attempting to read ? or dbs or tasdef.dbf.

Action: Check errno returned. Sgadef file may be corrupted or incompatible with oracle version.

ORA-09873: TASDEF_OPEN: open error when opening tasdef.dbf file.

ORA-09873: TASDEF_OPEN: open error when opening tasdef.dbf file.

Cause: Unable to open tasdef.dbf file.

Action: Check errno. Possible permission problem. Verify that tasdef.dbf file exists.

ORA-09872: TASDEF_CREATE: create failure in creating ? or dbs or tasdef.dbf.

ORA-09872: TASDEF_CREATE: create failure in creating ? or dbs or tasdef.dbf.

Cause: Create() failed when trying to create the tasdef file.

Action: Verify permissions on $(ORACLE_HOME) or dbs directory.

ORA-09871: TASDEF_NAME: translation error while expanding ? or dbs or tasdef.dbf.

ORA-09871: TASDEF_NAME: translation error while expanding ? or dbs or tasdef.dbf.

Cause: Failure of sltln(? or tasdef.dbf) while creating test and set pages.

Action: Check additional return error for more information.

ORA-09870: spini: failure initializing maximum number of open files.

ORA-09870: spini: failure initializing maximum number of open files.

Cause: ulimit system call returned an error.

Action: Check errno.

ORA-07499: spglk: Cannot reschedule.

ORA-07499: spglk: Cannot reschedule.

Cause: The rescheduling driver or dev or resched is not open. This is an internal error and should not occur.

Action: Contact your customer support representative.

ORA-07498: spstp: Unable to open or dev or resched.

ORA-07498: spstp: Unable to open or dev or resched.

Cause: The rescheduling driver or dev or resched is not found or is not working properly.

Action: Check installation of the ORACLE rescheduling driver in the AIX kernel.

ORA-07497: sdpri: cannot create trace file string ; errno = string.

ORA-07497: sdpri: cannot create trace file string ; errno = string.

Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic link.

Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the symbolic link.