Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: Either Shared Sequence Number operating system component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.
Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the operating system command ps -ef | grep instance_name. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by issuing the ipcs -b operating system command. If there are shared memory segments or processes still on the system, use SVRMGRL to shut down the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the CNXSHOW command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital's customer support organization.
Cause: A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem.
Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Support Services.
Cause: A call to the SSN failed to increment the sequence number.
Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Support Services.
Cause: A valid service identifier existed before the sequence number service was opened.
Action: Verify that the instance is completely shut down.
Cause: A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated.
Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle Support Services.
Cause: A process has timed out trying to get or convert the SCN recovery lock. Another process probably has the lock in EX or SHR mode, but is not releasing it.
Action: Contact Oracle Support Services.
Cause: ORACLE binary has been optimized with unsupported options or a required option has not been used.
Action: Check the documentation for a list of supported and required flags for the optimizing utility that you used to optimize ORACLE. Shutdown the instance, optimize ORACLE again with a supported combination of options, and restart the instance.
Cause: Autologin unable to open port.
Action: Check log file for operating system-specific error code.
Cause: Autologin unable to change port attributes.
Action: Check log file for operating system-specific error code.
Cause: Autologin unable to read from port.
Action: Check log file for operating system-specific error code.
Cause: Autologin unable to write to port.
Action: Check log file for operating system-specific error code.
Cause: Autologin unable to open dialogue file.
Action: Check connect string for accuracy/typos.
Cause: Autologin unable to read dialogue file.
Action: Check log file for operating system-specific error code.
Cause: Expected response never received.
Action: Check log file for operating system-specific error code.
Cause: Dialogue file contains syntax error.
Action: Correct the dialogue file.
Cause: Full file specification for dialogue file exceeds 64 bytes.
Action: Amend connect string accordingly.
Cause: Dialogue file exceeds 768 bytes in length.
Action: Simplify dialogue (for example, such as remove comments, redundant white space), or split into two and link with the MORE command.
Cause: One of the following:
Action: Simplify dialogue or split into two and link with the MORE command.
Cause: Asynchronous driver gets I/O error while doing network read operation.
Action: Check log file for operating system-specific error code and contact Oracle Support Services.
Cause: Asynchronous driver gets I/O error while doing network write operation.
Action: Check log file for operating system-specific error code and contact Oracle Support Services.
Cause: Syntax error in login string.
Action: Resubmit with correct string.
Cause: Asynchronous driver unable to complete initialization.
Action: Check log file for operating system-specific error code.
Cause: Asynchronous driver unable to establish connection with partner.
Action: Check log file for operating system-specific error code.
Cause: No free channel.
Action: Contact Oracle Support Services.
Cause: Asynchronous driver unable to open port.
Action: Check log file for operating system-specific error code.
Cause: Virtual Terminal Manager unable to read/write to port.
Action: Check log file for operating system-specific error code.
Cause: Asynchronous driver generated for server-only, but client service requested.
Action: Contact Oracle Support Services.
Cause: Asynchronous driver unable to close port.
Action: Check log file for operating system-specific error code.
Cause: Asynchronous driver unable to close channel.
Action: Check log file for operating system-specific error code.
Cause: Asynchronous driver unable to initialize for logging I/O.
Action: Contact Oracle Support Services.
Cause: Asynchronous driver unable to assign port to channel.
Action: Contact Oracle Support Services.
Cause: Node name specified in host string is unknown (probably misspelled).
Action: Retry with correct node name.
Cause: Host string contains reference to object (which does not exist):
@d:node-obj => object is ORDNobj;
Action: Retry with correct object name or create the required object on host node.
Cause: Host string contains invalid username/password.
Action: Retry with correct username/password.
Cause: Connection with partner was made but was rejected.
Action: Contact your network administrator.
Cause: Connection with host node was made but partner aborted.
Action: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the Oracle server process starts up); sometimes happens when the network/node is under stress; in this case, a retry often works.
Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.
Action: Contact your network administrator.
Cause: Host node is down.
Action: Contact your network administrator.
Cause: Connect failed for unexpected reason (see OSD error).
Action: Contact Oracle Support Services.
Cause: Syntax error in login string.
Action: Resubmit with correct string.
Cause: Driver gets error while doing network close operation.
Action: Contact Oracle Support Services.
Cause: Driver gets I/O error while doing network read operation.
Action: Contact Oracle Support Services.
Cause: Driver gets I/O error while doing network write operation.
Action: Contact Oracle Support Services.
Cause: Connect failed because of insufficient byte count quota.
Action: Increase byte count quota.
Cause: Insufficient dynamic memory available for connection context area.
Action: Contact Oracle Support Services.
Cause: Host name specified in the login (connect) string is unknown.
Action: Check spelling; make sure name is in the TCP/IP HOST file.
Cause: Process open file quota probably exceeded.
Action: Contact Oracle Support Services.
Cause: No entry in SERVICES file for Oracle server.
Action: Add (ORASRV) entry to the TCP/IP SERVICES file.
Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet).
Action: Start the SQL*Net TCP/IP server process on the remote host.
Cause: I/O error occurred while attempting network read operation.
Action: Contact Oracle Support Services.
Cause: I/O error occurred while attempting network write operation.
Action: Contact Oracle Support Services.
Cause: Error occurred while closing a socket.
Action: Contact Oracle Support Services.
Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).
Action: Re-submit with valid buffer size.
Cause: The maximum no. of concurrently open connections has been reached.
Action: Exit an application with an open connection which is no longer required.
Cause: From the remote host's SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server).
Cause: The host's SQL*Net TCP/IP server was unable to create the necessary logical names required by the Oracle server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your system administrator.
Cause: The host's SQL*Net TCP/IP server was unable to create the Oracle server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your system administrator.
Cause: The host's SQL*Net TCP/IP server was unable to create the Oracle server process because of quota depletion.
Action: Increase quota allocations to the SQL*Net TCP/IP server process.
Cause: The Oracle server process was started but failed to complete its initialization.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The TCP/IP network driver is not loaded.
Action: Check that the TCP/IP driver is loaded correctly.
Cause: The host's SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The Oracle server process was started but failed to respond after N seconds.
Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = no_of_secs which will come into effect the next time the SQL*Net TCP/IP server is started.
Cause: The Oracle server process was started but exited unexpectedly. Possible causes:
Action: If appropriate action is not obvious from the ORASRV output file, then contact Oracle Support Services.
Cause: The Oracle server process was started but was unable to open the socket passed to it by ORASRV.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host operating system).
Action: Create new user account on host.
Cause: The host's SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the Oracle server process). See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server was unable to transfer the network communication handle to the Oracle server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host's CONFIG.ORA.
Action: To grant access, add appropriate entry to the host's VNT.
Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege, as determined by the contents of the Username Mapping Table (UMT), a component of the host's CONFIG.ORA.
Action: To grant access, add appropriate entry to the host's UMT.
Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password.
Action: To grant access, get passwords in sync.
Cause: The host's SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Check CONFIG.ORA for spelling; make correct entry.
Cause: The host's SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Change protection on SID mapping file.
Cause: The host's SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping.
Action: Restart SQL*Net TCP/IP server.
Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.
Action: Try again with a user that has a counterpart on the host.
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account.
Action: Change account protection; change server privileges.
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details.
Action: Contact Oracle Support Services.
Cause: The connect failed because the maximum concurrent connections supported by the host's SQL*Net TCP/IP server has already been reached.
Action: Wait for a short period and retry.
Cause: The database administrator on the host has varied the SID offline.
Action: Wait for it to be varied back online.
Cause: The host's SQL*Net TCP/IP server was unable to start the Oracle server process because the Oracle protected images were not installed.
Action: Install the images.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
Cause: The NTT two-task driver could not open a file containing address information.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not read addressing information from its addressing file.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not share a connection to the cube.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: An error occurred while reading the NTT communications link.
Action: Contact Oracle Support Services.
Cause: The Oracle listener process on the cube could not fork off a shadow process.
Action: The instance you are trying to connect to probably does not have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.
Cause: An error occurred while writing the NTT communications link.
Action: Contact Oracle Support Services.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: An error occurred while reading the NTT communications link.
Action: Contact Oracle Support Services.
Cause: An error occurred while writing the NTT communications link.
Action: Contact Oracle Support Services.
Cause: The call to NRANGE() failed while attempting to establish a connection.
Action: Contact Oracle Support Services.
Cause: The call to NFCONN() failed while attempting to establish a connection.
Action: Contact Oracle Support Services.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact Oracle Support Services.
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact Oracle Support Services.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact Oracle Support Services.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact Oracle Support Services.
Cause: The NTT two-task driver could not read configuration information from /etc/oratab.
Action: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.
Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
Action: If there is no message queue, restart the SQL*Net IPA servers using IPACTL. Otherwise contact Oracle Support Services.
Cause: The memory pool is exhausted.
Action: Check the circumstances and try to allocate less memory in your program or adjust the parameters in your initialization parameter file and retry.
Cause: One of the following:
Action: Check sequentially for the above causes and eliminate the actual cause found.
Cause: The SQL*Net IPA driver could not write the message into the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL.
Cause: The SQL*Net IPA driver could not read a message from the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL.
Cause: The communication between user and Oracle is out of synchronization. This message should not normally be issued.
Action: Contact Oracle Support Services.
Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
Action: Contact Oracle Support Services.
Cause: A fatal error occurred during the resetting of the connection.
Action: Contact Oracle Support Services.
Cause: You have exhausted all your connections.
Action: Try again when some of the current users have logged off.
Cause: The SQL*Net IPA servers have not been started.
Action: Run IPACTL.
Cause: Environment variable(s) not set correctly.
Action: Check and correct.
Cause: Maximum number of servers reached.
Action: Shut down and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start enough servers to support database links.
Cause: Incorrect outgoing service name supplied.
Action: Check and correct the service name.
Cause: The shared memory has not been set up correctly.
Action: Contact your system administrator.
Cause: Fatal interprocess communication error.
Action: Contact your system administrator.
Cause: The connect string is malformed.
Action: Check and correct.
Cause: The SID is unknown at the remote side.
Action: Either the database does not exist, is not running, or there are no reserved servers for that SID.
Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side.
Action: Wait for free connections to become available. If the problem persists, contact your system administrator.
Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.
Action: Wait for free connections to become available. If the problem persists, contact your system administrator.
Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side.
Action: Wait for free connections to become available. If the problem persists, contact your system administrator.
Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.
Action: Wait for free connections to become available. If the problem persists, contact your system administrator.
Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect.
Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied.
Cause: An internal error has occurred in the shared memory handling.
Action: Contact Oracle Support Services.
Cause: Fatal interprocess communication error.
Action: Contact your system administrator.
Cause: There was no default host string specified in the configuration and the user did not specify any explicit connect string.
Action: Either reconfigure the system specifying a default connect string or use an explicit connect string.
Cause: The login (connect) string contains an invalid driver designator.
Action: Correct the string and re-submit.
Cause: Error occurred while attempting to read a break message.
Action: Contact Oracle Support Services.
Cause: System unable to allocate needed virtual memory.
Action: Configure more memory, reduce load, or try again.
Cause: Syntax error in login string.
Action: Correct string and re-submit.
Cause: Unable to reset out of break state.
Action: Contact Oracle Support Services.
Cause: Error occurred while attempting to send a break message.
Action: Contact Oracle Support Services.
Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.
Action: Contact Oracle Support Services.
Cause: Message from partner contains bad header.
Action: Contact Oracle Support Services.
Cause: Unable to establish connection.
Action: Use diagnostic procedures to ascertain exact problem.
Cause: Error occurred while testing I/O status of the network connection.
Action: Contact Oracle Support Services.
Cause: The remote server was unable to start an Oracle process on behalf of the client.
Action: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator.
Cause: From the remote host's server: the database SID, specified in the login (connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA or ORATAB file on the remote host (restarting the remote server may be needed).
Cause: Error found during recomputation of checksum or CRC.
Action: Possible hardware failures of communication nodes. Contact system administrator immediately.
Cause: Unable to transmit data to remote host.
Action: Try reconnect to remote host, and contact your system administrator.
Cause: Unable to receive data from remote host.
Action: Try reconnect to remote host, and contact your system administrator.
Cause: A function was called with an invalid argument.
Action: Contact Oracle Support Services.
Cause: The file block number is out of range of the file. The additional information returns the block number.
Action: Verify that the block number is correct. Run DBFSIZE and check if the block number is in that range. Contact Oracle Support Services.
Cause: The I/O buffer was not aligned on a 2K boundary.
Action: Contact Oracle Support Services.
Cause: The additional information returns the block number.
Action: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct.
Cause: The read system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The write system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: This write call may have been truncated. The additional information returns the block number and number of bytes.
Action: Verify that the block number and the number of bytes written are correct.
Cause: This read call may have been truncated. The additional information returns the block number and number of bytes.
Action: Verify that the block number and the number of bytes read are correct.
Cause: Either the Oracle process ID, or wait time or event ID is invalid.
Action: The additional information indicates the process ID, time and event ID.
Cause: Some system problems may exist on your system; check the error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: An invalid event ID is passed in to this routine.
Action: The additional information indicates the event ID.
Cause: Some system problems may exist on your system; check the error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: An invalid event ID, or the low and high event ID do not exist.
Action: The additional information indicates the error number. It also contains the event ID, low boundary and high boundary.
Cause: Some system problems may exist on your system; check the error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: Invalid Oracle process ID is passed in to this routine.
Action: The additional information indicates the process ID.
Cause: Some system problems may exist on your system; check the error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: Oracle tries to use the SYSVENDOR interface (INIT.ORA parameter USE_SYSVENDOR=TRUE) but the UNIX kernel does not have the Oracle SYSVENDOR interface linked in.
Action: Set USE_SYSVENDOR=FALSE in INIT.ORA, if you do not want to use this interface or link the UNIX kernel with this interface so that Oracle can use it.
Cause: This is a rare internal error message. Memory has been exhausted or corrupted.
Action: Contact Oracle Support Services.
Cause: This is an internal error message. An error has been detected in a PL/SQL program.
Action: Contact Oracle Support Services.
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).
Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.
Cause: A call to PL/SQL function completed, but no RETURN statement was executed.
Action: Rewrite PL/SQL function, making sure that it always returns a value of a proper type.
Cause: Number and/or types of columns in a query does not match declared return type of a result set variable, or declared types of two Result Set variables do not match.
Action: Change the program statement or declaration. Verify what query the variable actually refers to during execution.
Cause: A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes.
Action: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code.
Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.
Action: Check that all referenced programs, including their package bodies, exist and are compatible.
Cause: This indicates a version clash between some package distributed with an Oracle product and the product executable.
Action: Contact Oracle Support Services.
Cause: A user-defined exception was raised by PL/SQL code, but not handled.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.
Cause: An attempt was made to open a cursor that was already open.
Action: Close cursor first before reopening.
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.
Cause: An attempt is being made to copy a PL/SQL table to a host language array. But an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, etc. If an table entry has not been assigned then the corresponding element in the host language array is set to null.
Action: Increase size of host language array, or decrease size of PL/SQL table. Also make sure that you do not use index values less than 1.
Cause: The remote call has parameters that are cursor variables or lob variables. This cannot be handled by stored procedures on your server.
Action: Avoid using cursor variables or lob variables as parameters for stored procedures on this server or upgrade your server to a release that supports this.
Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.
Cause: A Probe operation, probably an attempt to initialize the Oracle server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid.
Action: DBA should load the Probe packages. This can be done by running the PBLOAD.SQL script supplied with the RDBMS.
Cause: An error occurred while passing a Probe operation to the server for execution.
Action: Refer to the entry for the embedded error message.
Cause: The current version of Probe is incompatible with the version on the Oracle server.
Action: Refer to the documentation to ensure that this degree of compatibility is supported.
Cause: Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised.
Action: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back.
Cause: An error was detected by PL/SQL trying to load the external library dynamically.
Action: Check the stacked error (if any) for more details.
Cause: An error was detected by PL/SQL trying to map the mentioned function dynamically.
Action: Check the stacked error (if any) for more details.
Cause: ORA-06520 or ORA-06521could stack this error with a system-specific error string.
Action: This error string should give the cause for errors ORA-06520 or ORA-06521
Cause: There is an upper limit on the number of arguments that one can pass to the external function.
Action: Check the port-specific documentation on how to calculate the upper limit.
Cause: The option specified is an unsupported feature for external procedures.
Action: Correct the syntax in the external specification.
Cause: The length specified in the length variable has an illegal value. This can happen if you have requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the ORLVSTR or ORLRAW.
Action: Correct the external procedure code and set the length variable correctly.
Cause: PL/SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen.
Action: Report this problem to Oracle Support Services.
Cause: An error occurred in SQLLIB during execution of a Pro* external procedure.
Action: The message text indicates the actual SQLLIB error that occurred.
Cause: An error occurred during execution of a PL/SQL profiler procedure.
Action: Check the stacked errors for more details.
Cause: The PL/SQL profiler package (DBMSPB.SQL, PRVTPBP.PLB) does not match the version of the code in the server implementing the profiler.
Action: Run the package PROFLOAD.SQL in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages.
Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized.
Action: Initialize the composite with an appropriate constructor or whole-object assignment.
Cause: An element or member function of a nested table or VARRAY was referenced (where an initialized collection is needed) without the collection having been initialized.
Action: Initialize the collection with an appropriate constructor or whole-object assignment.
Cause: A subscript was greater than the limit of a VARRAY or non-positive for a VARRAY or nested table.
Action: Check the program logic and increase the VARRAY limit if necessary.
Cause: An in-limit subscript was greater than the count of a VARRAY or too large for a nested table.
Action: Check the program logic and explicitly extend if necessary.
Cause: The program attempted to access a Serially Reusable package in the context of a trigger. Such an access is currently unsupported.
Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in the context of a trigger.
Cause: The program attempted to use a dynamic statement string that was either NULL or 0 length.
Action: Check the program logic and ensure that the dynamic statement string is properly initialized.
Cause: The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position.
Action: Make sure that an OUT or IN OUT bind mode is specified for the bind argument.
Cause: The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position.
Action: Make sure that an IN or IN OUT bind mode is specified for the bind argument.
Cause: The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement.
Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement.
Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.
Action: Ensure that the OPEN cursor operation is done on a dynamic query statement.
Cause: A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn error messages.
Cause: A PL/SQL compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ORA-06545, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn error messages.
Cause: A PL/SQL internal error occurred.
Action: Report as a bug; the first argument is the internal error number.
Cause: A PL/SQL compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ORA-06541, the user will always see this error along with the accompanying PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn error messages.
Cause: DDL statement is executed dynamically in illegal PL/SQL context.
Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement.
Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only.
Action: Use the RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use the USING clause instead.
Cause: The caller of a pipelined function does not need more rows to be produced by the pipelined function.
Action: Catch the NO_DATA_NEEDED exception is an exception handling block.
Cause: One possible cause might be that there are too many DLLs open at the same time.
Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
Cause: The DBMS-specific extensions to PL/SQL's package STANDARD are in package DBMS_STANDARD. This package must be created before using PL/SQL.
Action: Create package DBMS_STANDARD. The source for this PL/SQL stored package is provided with the distribution.
Cause: An attempt was made to create a package named STANDARD, DBMS_STANDARD or DEBUG_IO. These are currently reserved for use by user SYS.
Action: Choose another name for your package.
Cause: There are no more items in the pipe.
Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.
Cause: Internal error from the DBMS_PIPE package.
Action: Contact Oracle Support Services.
Cause: The pipe buffer size has been exceeded.
Action: Inspect the program to analyze the rate of input and output to the pipe. You might need to take items out of the pipe by executing RECEIVE_MESSAGE, or empty the entire pipe by executing PURGE on the pipe.
Cause: The sender put different datatype on the pipe than that being requested (package DBMS_PIPE). The numbers are:
Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.
Cause: Internal error from the DBMS_PIPE package.
Action: Contact Oracle Support Services.
Cause: An attempt was made to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.
Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE, or << (PL/SQL label delimiter) are supported.
Cause: An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.
Action: Pass in an out argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable.
Cause: The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to a top level procedure or function (which do not have nested procedures). This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure.
Action: Specify a procedure/function within a package, or a top level procedure/function.
Cause: The named object could not be found. Either it does not exist or you do not have permission to access it.
Action: Create the object or get permission to access it.
Cause: The named procedure cannot be executed from within a stored procedure, function or package. This function can only be used from PL/SQL anonymous blocks.
Action: Remove the procedure from the calling stored procedure.
Cause: An invalid number of rows was specified in a call to the procedure DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows.
Action: Specify a number that matches that for previously defined columns.
Cause: An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must have specified the same number of values to be bound for all bind variables.
Action: Make sure that the same number of values have been bound for all of the bind variables.
Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of RDBMS.
Action: Make sure that all PL/SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the CATPROC.SQL script supplied with the RDBMS.
Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present, at execute time, there will be no value for this bind and the statement is meaningless.
Action: Fill the collection with the elements you want to bind and try the bind call again.
Cause: The specified shared pool shared cursor could not be found, therefore it cannot be pinned.
Action: Make sure that a correct shared cursor name is given. Names are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8 digit hex number from the 'address' column of V$SQLAREA, and the D's are a 1 to 10 digit decimal number with an optional leading sign (from the HASH_VALUE column) Remove the procedure from the calling stored procedure.
Cause: One of the following:
Action: If the referenced function is a packaged, PL/SQL function, re-create the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma. If the referenced function is standalone, PL/SQL function, do not use the function.
Cause: A SQL statement references either a packaged or standalone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.
Action: Re-create the PL/SQL function without the OUT parameter in the argument list.
Cause: One of the following:
Action: If the function is a packaged, PL/SQL function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS). If the function is standalone PL/SQL function, delete the function from the SQL statement.
Cause: One of the following:
SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.Action: If the function is a packaged function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. If the function is a standalone function: Do not call the function.
Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.
Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.
Cause: Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call.
Action: Change the statement to invoke a function or procedure.
Cause: The argument corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable.
Action: Change the argument to a bind variable.
Cause: The bind variable corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable.
Action: Change the bind variable to be unique.
Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.
Action: Increase HASH_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased.
Cause: A CASE statement must either list all possible cases or have an else clause.
Action: Add all missing cases or an ELSE clause.
Cause: The specified feature is not yet supported for natively compiled PL/SQL modules.
Action: Recompile the relevant PL/SQL modules in non-native mode by setting the PLSQL_COMPILER_FLAGS parameter to INTERPRETED.
Cause: The SNA software is not running.
Action: Start the SNA software and try again.
Cause: The database string in the connect was invalid.
Action: Provide a valid database string, as defined in documentation.
Cause: Context area failure.
Action: Contact Oracle Support Services.
Cause: Operating system refused request for memory.
Action: Contact Oracle Support Services.
Cause: Allocate system call failed.
Action: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter.
Cause: SNA software switched from send to receive unexpectedly.
Action: Check the SNA configuration data, particularly parameters associated with a session.
Cause: A parameter in an SNA call returned an unexpected value.
Action: Attempt to reproduce problem, debug and record the value of the 'what' data parameter at the time of error. Then contact your service representative.
Cause: A reset was issued while in send state.
Action: Check the SNA LOG data, if relevant, for further information.
Cause: A reset was received from the partner while in receive state. This may be because the partner deallocated.
Action: Check the SNA LOG data, if relevant, for further information.
Cause: LU6.2 driver was unable to deallocate gracefully.
Action: Check the reason for deallocation. Consult the SNA LOG data.
Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU.
Action: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational.
Cause: The SQL*Net LU6.2 driver could not attach to the SNA software on your machine. The most likely cause is that the SNA software is not operational.
Action: Check the status of the SNA software, ensure that it is operational and then try again.
Cause: TLI received a message with an unrecognizable message type.
Action: Contact Oracle Support Services.
Cause: TLI sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes supplied to the driver.
Action: Contact Oracle Support Services.
Cause: TLI could not allocate heap space for the context area.
Action: Contact Oracle Support Services.
Cause: TLI failed to send a break message across the connection.
Action: Contact Oracle Support Services.
Cause: TLI failed to receive an expected break message.
Action: Contact Oracle Support Services.
Cause: TLI could not find your remote host information.
Action: Make sure you specified the host name correctly on the command line. (Also, check your capitalization and spelling.)
Cause: TLI could not find service information for the specified service name.
Action: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system administrator to add it.
Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error.
Action: See the SQL*Net TCP/IP User's Guide or the Oracle9i Net Services Administrator's Guide for the specific cause and action.
Cause: TLI encountered an error receiving a message from the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error sending a message across the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI failed to send a break message while handling an interrupt signal from the user.
Action: Contact Oracle Support Services.
Cause: TLI failed to assign a network address to the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI failed to accept a connection request from the client.
Action: Contact Oracle Support Services.
Cause: TLI failed to connect the client to the remote server. The network line to the remote host may be down.
Action: Use other network login programs to make sure that the remote host is accessible.
Cause: The database SID supplied in the database login string was not recognized by the remote host.
Action: Ask your system administrator to add the appropriate SID entry to ORATAB on the remote host.
Cause: The remote TLI server received an undefined request.
Action: Contact Oracle Support Services.
Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message.
Action: Contact Oracle Support Services.
Cause: TLI failed to open the Streams clone device associated with the transport provider.
Action: Contact Oracle Support Services.
Cause: TLI cannot allocate space for the client's connection information.
Action: Contact Oracle Support Services.
Cause: TLI cannot allocate space for the client's disconnection information.
Action: Contact Oracle Support Services.
Cause: TLI failed to receive an expected disconnection message during connection release.
Action: Contact Oracle Support Services.
Cause: TLI failed to connect the client to the remote server.
Action: Check that the remote TLI server is running.
Cause: TLI failed to properly close a connection after an error was received.
Action: Contact Oracle Support Services.
Cause: TLI timed out while attempting to connect to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the transport provider you are using. If it is not, ask your system administrator to start it.
Cause: TLI could not establish a connection to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the transport provider you are using.
Cause: The TLI server failed to open the Streams device associated with the transport provider.
Action: Contact Oracle Support Services.
Cause: The TLI server cannot allocate space for its requested network address.
Action: Contact Oracle Support Services.
Cause: The TLI server cannot allocate space for its actual network address.
Action: Contact Oracle Support Services.
Cause: The TLI server failed to assign the correct network address on which to listen for connections.
Action: Contact Oracle Support Services.
Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running.
Action: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact Oracle Support Services.
Cause: TLI cannot allocate space for the TLI server's connection information.
Action: Contact Oracle Support Services.
Cause: The TLI server encountered an error while listening for connection requests.
Action: Contact Oracle Support Services.
Cause: TLI cannot allocate space for the TLI server's disconnection information.
Action: Contact Oracle Support Services.
Cause: The requested TLI server command must be issued from the same host on which the server is running.
Action: Log in to the remote host and try again.
Cause: The Oracle process started by the TLI server was unable to synchronize its inherited connection.
Action: Contact Oracle Support Services.
Cause: The OSN check server address failed. The bound server address was not the same as the requested binding address.
Action: Contact Oracle Support Services.
Cause: A call to SIGACTION() returned with a system error.
Action: Contact Oracle Support Services.
Cause: For SVR4, the NETDIR_GETBYNAME() call failed for some unknown reason.
Action: Contact Oracle Support Services.
Cause: The name of the remote host to connect to was not specified, and the name of the local host cannot be retrieved from the HOSTS file.
Action: Contact your system administrator.
Cause: The TLI server was unable to close a connection after passing it to an Oracle process.
Action: Contact Oracle Support Services.
Cause: The TLI server could not open the file used to define the locations of remotely accessible databases.
Action: Ask your system administrator to check that the file exists and has the correct permissions.
Cause: The TLI server received an invalid command.
Action: Contact Oracle Support Services.
Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI failed to close the communication channel after receiving a disconnect message.
Action: Contact Oracle Support Services.
Cause: TLI cannot allocate space for disconnection information while closing the communication channel.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while sending its version information during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected version information during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while sending a command message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected command message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while sending break-mode message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while sending the connection parameters during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while sending the completion status message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting an expected error message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment.
Action: Contact Oracle Support Services.
Cause: TLI was unable to poll the communication channel for possible incoming messages.
Action: Contact Oracle Support Services.
Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.
Action: Contact Oracle Support Services.
Cause: The remote TLI server was unable to start an Oracle process on behalf of the client.
Action: Note the operating system error message or number and contact your system administrator. The permissions on the remote Oracle program may be set incorrectly.
Cause: The remote TLI server was unable to start an Oracle process on behalf of the client.
Action: Note the operating system error message or number and contact your system administrator. The remote host may be unable to create any new processes due to a full process table.
Cause: The Oracle process either failed to allocate memory to store the protocol information record, or the protocol rejected the request for some unknown reason.
Action: Contact Oracle Support Services.
Cause: The client process was aborted by the system or the user, and was unable to complete the connection establishment with the server listener process.
Action: Determine the cause of the client exit, and reattempt the connection.
Cause: An unknown event occurred on the client's listening socket.
Action: Contact Oracle Support Services.
Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process.
Action: Insure the file exists and is readable. Make sure that the server machine's node name, network number, ethernet address, and listening socket number are encoded in the file.
Cause: The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.
Action: Contact Oracle Support Services.
Cause: A step in the SPX/IPX protocol initialization failed.
Action: Check the previous error reported, and follow corrective action.
Cause: The file /dev/eth does not exist, or the driver it references could not be opened.
Action: The system's real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Support Services for a list of supported ethernet drivers.
Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported.
Action: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Support Services for a list of supported ethernet drivers.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid.
Action: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The ethernet driver is not installed correctly, or does not support this operation.
Action: Contact Oracle Support Services for a list of supported ethernet drivers.
Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server.
Action: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file.
Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The SPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The SPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing.
Action: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentionally deleted, run SPXCTL (net option) to reset the configured Novell network number for SQL*Net SPX.
Cause: CMX is not started on your system.
Action: Install and/or start CMX on your system.
Cause: Local application ORACMX has no local name assigned.
Action: Enter unique local name for ORACMX in the TNS directory.
Cause: CCP-xxxx is not started.
Action: Start your CCP software on the communication controller.
Cause: Remote application not entered in TNS directory.
Action: Enter remote application in TNS directory.
Cause: No local name assigned to remote application.
Action: Assign local name to remote application.
Cause: Remote partner not listening.
Action: Make sure remote node has CMX installed and running make sure ORACMX is running on remote host.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Remote partner aborted.
Action: Contact Oracle Support Services.
Cause: Remote partner aborted.
Action: Contact Oracle Support Services.
Cause: Remote partner aborted.
Action: Contact Oracle Support Services.
Cause: Oracle process not found or wrong mode (should be 4751).
Action: Change /etc/oratab or set mode to 4751.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: ORACMX has been stopped, or user process has been aborted.
Action: Contact Oracle Support Services.
Cause: Connect sequence out of sync.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Remote partner aborted.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Received packets are corrupted.
Action: Contact Oracle Support Services.
Cause: Received packets are corrupted.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Break handling out of sync.
Action: Contact Oracle Support Services.
Cause: Received packets are corrupted.
Action: Contact Oracle Support Services.
Cause: Partner is not responding.
Action: Make sure partner is up and running and reachable.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: ORACLE_SID is not entered in remote ORATAB.
Action: Add ORACLE_SID to remote ORATAB.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: Internal error in CMX.
Action: Contact Oracle Support Services.
Cause: SQL*Net AppleTalk error codes base. This is not an error.
Action: No action required.
Cause: AppleTalk API received error in VMS system service.
Action: Contact Oracle Support Services.
Cause: Peer program may have aborted.
Action: Investigate network problems and try again.
Cause: Not enough memory available.
Action: Check VMS process quotas and/or SYSGEN parameters.
Cause: Erroneous file name.
Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols.
Cause: Too many database connections.
Action: Check ATKSRV_MAXCON parameter in configuration file.
Cause: Unable to get Appletalk host name.
Action: Check Appletalk configuration.
Cause: Incoming SQL*Net connection specified invalid SID name.
Action: Specify correct SID in connect string and retry.
Cause: Unable to access CONFIG.ATK.
Action: Check file protections.
Cause: Buffered I/O quota exceeded.
Action: Increase BIOLM using AUTHORIZE utility and retry.
Cause: SQL*Net Appletalk listener could not create log file.
Action: Check directory path and protections.
Cause: You do not have sufficient privileges for the attempted operation.
Action: Check process privileges and retry.
Cause: Host name specified in the login (connect string) is unknown.
Action: Check spelling; make sure name is in the X.25 HOST file.
Cause: The buffer size specified in the login string must be between 5 and 4096.
Action: Re-submit with valid buffer size.
Cause: From the remote host's SQL*Net X.25 server: the database SID, specified in the login (connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net X.25 server).
Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net X.25 server on the remote host is not up, or the host itself is not up.
Action: Start the SQL*Net X.25 server process on the remote host.
Cause: Process open file quota probably exceeded.
Action: Contact Oracle Support Services.
Cause: X.25 level 2 is down. X.25 link is not working.
Action: Run system checks to verify functioning of X.25 software. Contact your hardware vendor.
Cause: Call back address probably same as called address.
Action: Verify that the callback address and called address are different.
Cause: The remote X.25 server was unable to start an Oracle process on behalf of the client.
Action: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator.
Cause: The environment variable $(ORACLE_SID) is not set.
Action: Set ORACLE_SID environment variable.
Cause: $(ORACLE_HOME) environment variable not set.
Action: Set ORACLE_HOME.
Cause: The SLTLN name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length.
Action: Probable internal Oracle error. Contact Oracle Support Services.
Cause: A string was passed to SLTLN containing a long environment variable. SLTLN accepts environment names of 30 or less characters.
Action: Shorten environment variable name to less than 30 characters.
Cause: The SLTLN routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
Action: Possible internal error. Check output buffer length stored in sercose[0]. Path names are limited to 255 characters.
Cause: Time() system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: GETTIMEOFDAY() system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: The SIGPIDU routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The FSYNC system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: The size of the file to be opened exceeded the operating system limit imposed on this process.
Action: Run OSH to increase the file size limit.
Cause: GETRUSAGE system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: GETTIMEOFDAY system call returned an error. Possible operating system error.
Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.
Cause: The times system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: Times system call returned an error. Possible operating system error.
Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.
Cause: UNAME system call returned an error. Possible operating system error.
Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.
Cause: GETRUSAGE system call returned an error. Possible operating system error.
Action: Check additional information returned. Look for information in the operating system reference manual. Contact Oracle Support Services.
Cause: GETHOSTNAME system call returned an error. Possible operating system error.
Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.
Cause: GETENV call returned a null pointer.
Action: Set the environment variable and try again.
Cause: UNIX system() call failed.
Action: Examine system error message.
Cause: MALLOC failed to allocate space to hold spooler arguments.
Action: Check additional information returned in the operating system reference manual. The process may have run out of heap space. Contact Oracle Support Services.
Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error.
Action: Check additional information returned. Refer to the operating system reference manual. Contact Oracle Support Services.
Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.
Action: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.
Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.
Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional information.
Cause: Fork system call failed to create additional process. Probable resource limit reached.
Action: Check additional information returned. Retry operation. Contact system administrator.
Cause: The ULIMIT system call returned an error.
Action: Check errno and contact Oracle Support Services.
Cause: Additional information returned is error returned from SLTLN.
Action: Check additional information.
Cause: The IOCTL call returned an error. Possible operating system error.
Action: Check additional information for errno. Contact Oracle Support Services.
Cause: The IOCTL call returned an error. Possible operating system error.
Action: Check additional information for errno. Contact Oracle Support Services.
Cause: The IOCTL call returned an error. Possible operating system error.
Action: Check additional information for errno. Contact Oracle Support Services.
Cause: Error in MPCNTL system call.
Action: Examine errno. Contact your system administrator.
Cause: FOPEN failed to open file.
Action: Try to determine which file was not opened. Check that file exists and is accessible.
Cause: Function was called with an invalid argument. The file handle used was not obtained be SLEMCR. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An error was encountered when closing the file. Possible operating system error.
Action: Contact system administrator.
Cause: Function was called with an invalid file handle. File handle was not obtained by SLEMCR. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Unable to seek to desired position in file. Possible operating system error. Possible internal error.
Action: Verify that error message file is intact. Try to regenerate error message file. Contact Oracle Support Services.
Cause: Unable to write item to file. Possible operating system error. Possible permissions problem.
Action: Retry operation.
Cause: Unable to open error file. Possible permissions problem.
Action: Verify permission on error message file. Check additional information for errno.
Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to SLEMOP. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Unable to close file. Possible operating system error.
Action: Contact system administrator. Check additional information for errno.
Cause: Function was called with invalid file handle. Handle was not obtained by call to SLEMOP. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Unable to seek to desired position in file. Possible operating system error.
Action: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno.
Cause: Unable to read file. Possible operating system error.
Action: Verify that error file is intact. Regenerate error message file. Contact Oracle Support Services. Check additional information for errno.
Cause: Additional information indicates error returned from SLTLN.
Action: Check additional information.
Cause: The supplied buffer was not big enough. This is an internal error.
Action: Contact Oracle Support Services. Additional information indicates how big the supplied buffer was.
Cause: An attempt was made to create a file that exceeds the process's file size limit.
Action: Run OSH to raise the file size limit.
Cause: An attempt was made to move and write to a bad device address.
Action: Check errno. Possible lack of space on device.
Cause: SFOFI returns an error. This is an internal error.
Action: Contact Oracle Support Services.
Cause: SFRFB returns an error. This is an internal error.
Action: Contact Oracle Support Services.
Cause: SFWFB returns an error. This is an internal error.
Action: Contact Oracle Support Services.
Cause: OPEN() returns an error.
Action: Check that /proc has the right permissions.
Cause: An error occurred when trying to get first semaphore set.
Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
Cause: SEMGET failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores.
Action: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno.
Cause: SEMGET system call returned an error. Possible resource limit problem.
Action: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using IPCRM.
Cause: SEMCTL system call returned an error.
Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult operating system reference manual.
Cause: An error occurred while translating the name of the Oracle executable.
Action: Check sercose[0] for error returned from SLTLN. Perhaps $(ORACLE_HOME) is not set correctly.
Cause: System failed to set up signal handler.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: System failed to set up signal handler to catch exceptions.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: Error occurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of Oracle process.
Action: Check error returned by SLTLN returned in sercose[0].
Cause: An error occurred when creating a new process.
Action: Check errno. Perhaps a system limit on the number of processes has been exceeded.
Cause: An Oracle detached process died shortly after startup. Wait() indicated that a child process terminated.
Action: Check ?/dbs directory for trace or core files. Check errno.
Cause: Wait system call returned an error.
Action: Check errno.
Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process.
Action: Check errno.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Kill system call returned an error. Possible operating system error.
Action: Check errno. Additional information indicates the process ID tested.
Cause: SEMOP system call returned an error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running.
Cause: SEMOP system call returned an error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running.
Cause: Function was passed an invalid Oracle process ID. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Function was passed an invalid Oracle process ID. This is an internal error.
Action: Additional information indicates the invalid process ID. Contact Oracle Support Services.
Cause: GETPWUID() could not find an entry in the passwd file for a user.
Action: Add an entry for the user in the passwd file.
Cause: Detached process successfully executed, but died shortly thereafter. Additional information indicates exit code, and termination status.
Action: Check termination code for information as to why process exited. Check for core dump or trace file.
Cause: An error occurred while trying to set an interval timer. Probable porting problem.
Action: Check errno.
Cause: Function was called with an invalid Oracle process number (0).
Action: Internal Oracle error.
Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error.
Action: Check semaphore set index. Check Oracle process number.
Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error.
Action: Check semaphore set index. Check Oracle process number.
Cause: Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.
Action: Check errno returned.
Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist.
Action: Check errno.
Cause: A group has not been set up for dba users.
Action: Contact system administrator. Set up dba group in /ETC/GROUP.
Cause: A 0 PID was passed to SPDDE. This is an internal error.
Action: Contact Oracle Support Services.
Cause: SPLON constructed an OPS$USERNAME logon which exceeded the allocated buffer space.
Action: Use a shorter UNIX username, or use an Oracle username. Contact Oracle Support Services.
Cause: An error occurred when trying to get first semaphore set.
Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
Cause: The IOCTL call returned an error. Possible operating system error.
Action: Check additional information for errno. Contact Oracle Support Services.
Cause: Times system call returned an error. Possible operating system error.
Action: Check additional information returned. Contact Oracle Support Services.
Cause: The internal buffer is not big enough to hold the archive control string.
Action: Internal restriction. Try a shorter archive control string.
Cause: An invalid volume size was specified.
Action: Specify a valid volume size in archive control string.
Cause: Some non-numeric text follows the volume size specification.
Action: Enter a correct archive control string.
Cause: Volume size was specified for a disk file.
Action: If you are archiving to a disk file, do not specify its volume size.
Cause: STAT on the log archiving device failed.
Action: Check the returned OSD error for the reason of failure.
Cause: Log archiving to this device is unsupported.
Action: Try log archiving to a supported device.
Cause: The specified path name is not a directory.
Action: Verify that the archive destination directory exists.
Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size.
Action: Verify that the DB_BLOCK_SIZE initialization parameter is set properly in your initialization parameter file.
Cause: The redo buffer size must be a multiple of machine block size.
Action: Verify that the LOG_BUFFER initialization parameter is set properly in your initialization parameter file.
Cause: The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used.
Action: Verify that the DB_BLOCK_SIZE initialization parameter is set properly in your initialization parameter file, or disable the USE_INDIRECT_DATA_BUFFERS initialization parameter.
Cause: MALLOC library routine returned an error.
Action: Check errno. Possibly out of swap space.
Cause: SMPDAL was called when the PGA had not been previously created. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.
Action: Reconfigure operating system to have more semaphores per set.
Cause: The specified datafile name contains '..'.
Action: Correct the datafile name and retry the operation.
Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.
Action: Look up additional error code for further information.
Cause: FOPEN library routine returned an error.
Action: Verify existence and permissions.
Cause: FCLOSE library routine returned an error.
Action: Possible internal Oracle error.
Cause: An error occurred while deleting a text file.
Action: Verify that the file exists and check additional errors.
Cause: An error occurred while performing a string put operation.
Action: This is an internal error. Check additional information.
Cause: The name for the message file overflows internal buffer.
Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.
Cause: The system failed to restore user exception handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The system failed to restore user signal handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The DB_WRITERS initialization parameter in your initialization parameter file exceeds the system-dependent maximum or is less than 0.
Action: Change the DB_WRITERS initialization parameter in your initialization parameter file.
Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.
Action: Check all database writer trace files. Shut down the database and try to warm start.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: The supplied buffer is not big enough to hold the full path name.
Action: The construction of the full path name cannot be performed.
Cause: One of the database writer processes could not locate its entry in the SGA.
Action: Contact Oracle Support Services.
Cause: MALLOC() failed to allocate buffer for storing ORACLE_PATH.
Action: System has run out of heap space. Additional information indicates errno.
Cause: The SLPATH routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This may be an internal error.
Action: Check output buffer length stored in sercose[0] and constructed path name length in sercose[1].
Cause: One or more of the database writer processes is no longer running.
Action: Check the trace files for the database writers. Shut down the database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down the database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down the database and try to warm start.
Cause: An Oracle error occurred when translating the location of the dump file.
Action: Check the Oracle error code.
Cause: An Oracle error occurred when translating the location of the DBS directory.
Action: Check additional information for the error returned from SLTLN.
Cause: CHDIR system call returned an error. Possible permission problems.
Action: Check additional information for the operating system error code.
Cause: The server process was unable to fork a child 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.
Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.
Action: Try the SLEEP command when the process is not sleeping.
Cause: The wakeup monitor process died.
Action: Warm start instance.
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
Cause: An invalid function address was specified.
Action: Use a valid function address.
Cause: An invalid function name was specified.
Action: Use a valid function name.
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.
Cause: Oracle failed to create a shared arena file.
Action: Use SERCERRNO field to determine cause of failure.
Cause: Oracle attempted to create more shared arena files than permitted.
Action: Raise the value for MAX_ARENA in INIT.ORA.
Cause: Oracle failed to acquire a shared arena lock.
Action: Check result code in SERCERRNO to determine the cause of failure.
Cause: KSTAT library returned an error. Possible operating system failure.
Action: Check result code in sercose[0] for more information.
Cause: User tried to load a resource manager plan that does not exist.
Action: Use a resource manager plan that exists in the data dictionary.
Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group.
Action: Use a resource manager plan schema that contains the OTHER_GROUPS group.
Cause: User session queued for longer than maximum specified queue duration time for consumer group.
Action: Re-submit the job at a later time or increase queue timeout.
Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group.
Action: Execute job on behalf of another group, or increase the limit.
Cause: An attempt was made to turn on the Resource Manager when the database was closed.
Action: Open the database and try again.
Cause: The MSET routine returned an error. Semaphore may not exist.
Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].
Cause: The MCLEAR routine returned an error. Semaphore may not exist.
Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].
Cause: The CLUSTER_STATUS system call failed to get status information for the current cluster.
Action: Check result code in sercose[0]. Possible operating system failure.
Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from SLTLN in sercose[0].
Cause: Open failed when opening the file ?/dbs/sgadef@.dbf.
Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.
Cause: Read had an error when reading SGADEF.DBF file.
Action: Check errno. Verify file exists, and is correct size.
Cause: An error occurred in close, while closing the file ?/dbs/sgadef@.dbf.
Action: Check errno. Possible operating system error.
Cause: The VM_STATISTICS system call failed to get virtual memory statistics.
Action: Check result code in SERCERRNO. Possible operating system failure.
Cause: The VM_MAPMEM system call failed to get mapped memory statistics.
Action: Check result code in SERCERRNO. Possible operating system failure.
Cause: Lock manager must be initialized before converting locks.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_STAT_LOCK failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_OPEN or LM_OPEN_CONVERT failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: When creating an instance, SNLMINI could not change the permissions on ?/dbs/sgalm.dbf.
Action: Contact Oracle Support Services.
Cause: LM_ATTACH failed to attach to Lock Manager instance.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CREATE failed to create Lock Manager instance.
Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry.
Cause: LM_CONVERT failed to convert(get) lock.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CONVERT failed to put lock value.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_OPEN failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CONVERT failed to get lock value.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CREATE failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: Lock manager must be initialized before releasing locks.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_STAT_LOCK failed during lock release/cancel.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CONVERT failed during lock release/cancel.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CANCEL failed during lock release/cancel.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_CLOSE failed during lock release/cancel.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: An error was encountered releasing the lock.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: Unknown or unexpected error code.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_WAIT failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause: LM_POST failed.
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
Cause:
Action:
Cause: The rescheduling driver /dev/resched is not found or is not working properly.
Action: Check installation of the Oracle rescheduling driver in the AIX kernel.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur.
Action: Contact Oracle Support Services.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|