Oracle Error Messages: 01/27/12

Friday 27 January 2012

ORA-02727: osnpop: access error on orapop executable

ORA-02727: osnpop: access error on orapop executable

Cause: The Pipe driver could not access the orapop executable.

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

ORA-02726: osnpop: access error on oracle executable

ORA-02726: osnpop: access error on oracle executable

Cause: The Pipe 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-02725: osnpbr: cannot send break signal

ORA-02725: osnpbr: cannot send break signal

Cause: The Pipe driver could not send a break message to the ORACLE shadow process.

Action: Kill system call failed. Check errno and contact customer support.

ORA-02724: osnpbr: cannot send break message to orapop

ORA-02724: osnpbr: cannot send break message to orapop

Cause: The Pipe driver could not send a break message to orapop.

Action: Contact your customer support representative.

ORA-02723: osnpui: cannot send break signal

ORA-02723: osnpui: cannot send break signal

Cause: The Pipe driver could not send a break message to the ORACLE shadow process.

Action: Contact your customer support representative.

ORA-02722: osnpui: cannot send break message to orapop

ORA-02722: osnpui: cannot send break message to orapop

Cause: The Pipe driver could not send a break message to orapop.

Action: Contact your customer support representative.

ORA-02721: osnseminit: cannot create semaphore set

ORA-02721: osnseminit: cannot create semaphore set

Cause: The Fast driver failed to get a semaphore set.

Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator.

ORA-02720: osnfop: shmat failed

ORA-02720: osnfop: shmat failed

Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.

Action: Try invoking the Fast driver later, or use the default attach address.

ORA-02719: osnfop: fork failed

ORA-02719: osnfop: fork failed

Cause: The fast driver could not fork the oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-02718: osnprs: reset protocol error

ORA-02718: osnprs: reset protocol error

Cause: The two-task driver could not reset the connection.

Action: Contact your customer support representative.

ORA-02717: osnpfs: incorrect number of bytes written

ORA-02717: osnpfs: incorrect number of bytes written

Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver.

Action: Contact your customer support representative.

ORA-02716: osnpgetdatmsg: message from host had incorrect message type

ORA-02716: osnpgetdatmsg: message from host had incorrect message type

Cause: The Pipe driver received a message having an unrecognizable message type.

Action: Contact your customer support representative.

ORA-02715: osnpgetbrkmsg: message from host had incorrect message type

ORA-02715: osnpgetbrkmsg: message from host had incorrect message type

Cause: The pipe driver received a message having an unrecognizable message type.

Action: Contact your customer support representative.

ORA-02714: osnpwr: message send failure

ORA-02714: osnpwr: message send failure

Cause: The pipe driver failed to write a message to the communications channel.

Action: Contact your customer support representative.

ORA-02713: osnprd: message receive failure

ORA-02713: osnprd: message receive failure

Cause: The pipe driver failed to read a message from the communications channel.

Action: Contact your customer support representative.

ORA-02712: osnpop: malloc failed

ORA-02712: osnpop: malloc failed

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

Action: Contact your customer support representative.

ORA-02711: osnpvalid: write to validation channel failed

ORA-02711: osnpvalid: write to validation channel failed

Cause: The pipe driver failed to write to the orapop process.

Action: Contact your customer support representative.

ORA-02710: osnpop: fork failed

ORA-02710: osnpop: fork failed

Cause: The pipe driver could not fork the oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-02709: osnpop: pipe creation failed

ORA-02709: osnpop: pipe creation failed

Cause: The pipe 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-02708: osnrntab: connect to host failed, unknown ORACLE_SID

ORA-02708: osnrntab: connect to host failed, unknown ORACLE_SID

Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied.

Action: First, check whether you have read access to oratab, and see if the desired sid is there. Add an entry to oratab for the desired sid, if necessary.

ORA-02707: osnacx: cannot allocate context area

ORA-02707: osnacx: cannot allocate context area

Cause: The invoked Unix two-task driver could not allocate heap space for the context area.

Action: Contact your customer support representative.

ORA-02706: osnshs: host name too long

ORA-02706: osnshs: host name too long

Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit.

Action: Contact your customer support representative.

ORA-02705: osnpol: polling of communication channel failed

ORA-02705: osnpol: polling of communication channel failed

Cause: The pipe driver failed while polling the communications channel.

Action: Contact your customer support representative.

ORA-02704: osndopop: fork failed

ORA-02704: osndopop: fork failed

Cause: The two-task driver could not fork orapop.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-02703: osnpopipe: pipe creation failed

ORA-02703: osnpopipe: pipe creation failed

Cause: The pipe driver failed to create pipes for communications with the orapop 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-02702: osnoraenv: error translating orapop image name

ORA-02702: osnoraenv: error translating orapop image name

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.

ORA-02701: osnoraenv: error translating oracle image name

ORA-02701: osnoraenv: error translating oracle image name

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.

ORA-02700: osnoraenv: error translating ORACLE_SID

ORA-02700: osnoraenv: error translating ORACLE_SID

Cause: Two-task driver could not find the value of ORACLE_SID in the environment.

Action: Make sure that the ORACLE_SID environment variable has been properly set and exported.

ORA-02495: cannot resize file string, tablespace string is read only

ORA-02495: cannot resize file string, tablespace string is read only

Cause: An attempt was made to resize a data file in a tablespace that is read only.

Action: Change the tablespace to read or write and retry the resize operation.

ORA-02494: invalid or missing maximum file size in MAXSIZE clause

ORA-02494: invalid or missing maximum file size in MAXSIZE clause

Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value.

Action: Use correct syntax.

ORA-02493: invalid file increment size in NEXT clause

ORA-02493: invalid file increment size in NEXT clause

Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.

Action: Use correct syntax.

ORA-02492: missing required file block increment size in NEXT clause

ORA-02492: missing required file block increment size in NEXT clause

Cause: No value was specified for the NEXT clause.

Action: Use correct syntax.

ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause

ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause

Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.

Action: Use correct syntax.

ORA-02490: missing required file size in RESIZE clause

ORA-02490: missing required file size in RESIZE clause

Cause: No value was specified for the RESIZE clause.

Action: Use correct syntax.

ORA-02488: Error encountered when accessing file (string( for trace conversion

ORA-02488: Error encountered when accessing file (string( for trace conversion

Cause: An attempt was made to open or access the trace file during a trace conversion.

Action: Check the permissions for both input and output files. Also, check the file compatibility for the trace conversion.

ORA-02487: Error in converting trace data

ORA-02487: Error in converting trace data

Cause: Incompatible binary trace data was specified.

Action: Check the format of the input data.

ORA-02486: Error in writing trace file string

ORA-02486: Error in writing trace file string

Cause: Error occurred in creating or writing the file.

Action: Check file name and make sure it is constructed properly. Also, check permissions for directories.

ORA-02485: Invalid _trace_options parameter specification (string)

ORA-02485: Invalid _trace_options parameter specification (string)

Cause: Bad syntax for _trace_options INIT.ORA parameter.

Action: none

ORA-02484: Invalid _trace_buffers parameter specification (string)

ORA-02484: Invalid _trace_buffers parameter specification (string)

Cause: Bad process or size in _trace_buffers INIT.ORA parameter.

Action: none

ORA-02483: Syntax error in process specification (string)

ORA-02483: Syntax error in process specification (string)

Cause: Illegal process string

Action: Enter a legal process string

ORA-02482: Syntax error in event specification (string)

ORA-02482: Syntax error in event specification (string)

Cause: Illegal event string

Action: Enter a legal event string

ORA-02481: Too many processes specified for events (max string)

ORA-02481: Too many processes specified for events (max string)

Cause: Too many processes specified than allowed per event.

Action: Enter fewer processes by using ranges or wildcards if possible.

ORA-02479: error while translating file name for parallel load

ORA-02479: error while translating file name for parallel load

Cause: An invalid file name was specified to load data into.

Action: Specify a valid database file.

ORA-02478: merge into base segment would overflow MAXEXTENTS limit

ORA-02478: merge into base segment would overflow MAXEXTENTS limit

Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments

Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger

ORA-02477: can not perform parallel direct load on object string

ORA-02477: can not perform parallel direct load on object string

Cause: A parallel direct load is not possible because an index is is being created on the table.

Action: Retry load after index creation is complete.

ORA-02476: can not create index due to parallel direct load on table

ORA-02476: can not create index due to parallel direct load on table

Cause: A parallel direct load is occurring to the specified table.

Action: Retry statement after load is complete.

ORA-02475: maximum cluster chain block count of string has been exceeded

ORA-02475: maximum cluster chain block count of string has been exceeded

Cause: The number of blocks in a cluster chain exceeds the maximum number allowed.

Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key.

ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)

ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)

Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.

Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.

ORA-02473: Error while evaluating the cluster s hash expression.

ORA-02473: Error while evaluating the cluster s hash expression.

Cause: An error occurred while evaluating the clusters hash expression.

Action: Correct the query and retry.

ORA-02472: PL or SQL functions not allowed in hash expressions

ORA-02472: PL or SQL functions not allowed in hash expressions

Cause: A PL or SQL function was used in the hash expression.

Action: Recreate the cluster and remove the PL or SQL function.

ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre or ssion.

ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre or ssion.

Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression or s.

Action: Recreate the cluster and remove the offending keywords.