Cause: Creation of the consensus log failed on one or multiple peers.

Cause: The specified consensus log did not exist in the database.

Cause: The append entry operation on the consensus log failed.

Cause: The consensus service operation failed because the current peer was not the leader.

Cause: The consensus service operation failed because the specified peer was not enabled.

Cause: The drop operation on the consensus log failed on one or multiple peers.

Cause: The consensus service operation failed because the current peer was not included.

Cause: The consensus service operation failed because the specified schema did not exist at the peer database.

Cause: The consensus service operation failed because the entry at the specified index did not exist in the consensus log.

Cause: The operation failed because the consensus service was not running.

Cause: The consensus service failed to start because the database was not open in read/write mode.

Cause: The operation failed because the specified consensus log was not enabled.

Cause: The consensus entry header contained checksum that did not match the recomputed value at the receiving peer.

Cause: The operation failed because previous configuration change was not yet committed.

Cause: An error was encountered while executing consensus log pre-append entry callback.

Cause: An error was encountered while executing consensus log post-append entry callback.

Cause: An error was encountered while executing consensus log new entry callback.

Cause: An error was encountered while executing consensus log cache load callback.

Cause: An error was encountered while executing consensus log varray column read callback.

Cause: An error was encountered while executing consensus log varray column write callback.

Cause: Buffer size was not enough to hold consensus log entry.

Cause: An error was encountered while computing the signature for entry in the consensus log.

Cause: The signature of originator of consensus log entry cannot be verified.

Cause: A valid input value was not specified.

Cause: The operation failed because the specified user does not exist.

Cause: The database initialization parameter GLOBAL_NAMES was not set to be TRUE in a blockchain peer database.

Cause: The database link referenced does not exist.

Cause: The user referenced does not exist.

Cause: The blockchain referenced does not exist.

Cause: The specified blockchain had already been bootstrapped.

Cause: The bootstrap command did not include the initiating database.

Cause: The referenced blockchain either did not exist or was disabled.

Cause: Connection information was not found for the referenced peer.

Cause: The referenced peer already existed in the blockchain.

Cause: The referenced peer referenced did not exist in the blockchain.

Cause: The referenced blockchain's tentative_epoch# was not NULL.

Cause: There were blockchain type objects in the database that were created in a release later than the selected release for downgrade.

Cause: The blockchain transaction could not achieve the quorum to commit successfully.

Cause: The table was insert-only table and, therefore, could not be updated or deleted.

Cause: Parallel DML was enabled in this blockchain procedure or DML statement.

Cause: An error was encountered when freeing up blockchain execution context memory.

Cause: Abstract Data Type (ADT) was not supported in the blockchain procedure.

Cause: An error was encountered when creating a blockchain table.

Cause: An error was encountered when dropping the tombstone table for a blockchain table.

Cause: The transaction was prepared when a commit was issued. The consensus result was to abort the transaction.

Cause: Autologin unable to open port

Cause: Autologin unable to change port attributes

Cause: Autologin unable to read from port

Cause: Autologin unable to write to port

Cause: Autologin unable to open dialogue file

Cause: Autologin unable to read dialogue file

Cause: Expected response never received

Cause: Dialogue file contains syntax error

Cause: Full file spec for dialogue file exceeds 64 bytes

Cause: Dialogue file exceeds 768 bytes in length

Cause: One of two: 1. Dialogue contains more than 24 exchange blocks 2. Dialogue send string exceeds 84 bytes in length

Cause: Async driver gets I/O error while doing network read operation

Cause: Async driver gets I/O error while doing network write operation

Cause: Syntax error in login string.

Cause: Async driver unable to complete initialisation

Cause: Async driver unable to establish connection with partner

Cause: no free channel [should never happen]

Cause: Async driver unable to open port

Cause: Virtual Terminal Manager unable to read/write to port

Cause: Async driver genned for server-only, but client service requested

Cause: Async driver unable to close port

Cause: Async driver unable to close channel

Cause: Async driver unable to initialise for logging I/O

Cause: Async driver unable to assign port to channel [should never happen]

Cause: Node name specified in host string is unknown (probably misspelled)

Cause: Host string contains reference to object (which doesn't exist): @d:node-obj => object is ORDNobj; when node is VMS, the object is ORDNobj.COM when node is UNIX, the object is ORDNobj @d:node::"task=obj" => object is obj; when node is VMS, the object is obj.COM when node is UNIX, the object is obj

Cause: Host string contains invalid username/password

Cause: Connection with partner was made but was rejected.

Cause: Connection with host node was made but partner aborted

Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.

Cause: Host node is down.

Cause: Connect failed for unexpected reason (see OSD error).

Cause: Syntax error in login string.

Cause: Driver gets error while doing network close operation

Cause: Driver gets I/O error while doing network read operation

Cause: Driver gets I/O error while doing network write operation

Cause: Connect failed because of insufficient byte count quota.

Cause: Insufficient dynamic memory available for connection context area.

Cause: Host name specified in the login (connect) string is unknown.

Cause: Process open file quota probably exceeded.

Cause: No entry in SERVICES file for ORACLE server.

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).

Cause: I/O error occurred while attempting network read operation.

Cause: I/O error occurred while attempting network write operation.

Cause: Error occurred while closing a socket.

Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).

Cause: The maximum no. of concurrently open connections has been reached.

Cause: From the remote host's SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized.

Cause: The host's SQL*Net TCP/IP server was unable to create the necessary logicals required by the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.

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.

Cause: The host's SQL*Net TCP/IP server was unable to create the ORACLE server process because of quota depletion.

Cause: The ORACLE server process was started but failed to complete its initialization.

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.

Cause: The TCP/IP network driver is not loaded.

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.

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.

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.

Cause: The ORACLE server process was started but failed to respond after N secs.

Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_SID.OUT

Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV.

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 OS).

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.

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.

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.

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.

Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password.

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.

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.

Cause: The host's SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping.

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.

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.

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.

Cause: A proxy login connect attempt failed because the client username has no 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.

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.

Cause: The connect failed because the maximum conncurrent connections supported by the host's SQL*Net TCP/IP server has already been reached.

Cause: The database administrator on the host has varied the SID offline.

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.

Cause: Two-task driver could not allocate data buffers.

Cause: ORACLE_HOME environment variable not set.

Cause: The NTT two-task driver could not open a file containing address information.

Cause: The NTT two-task driver could not read addressing information from its addressing file.

Cause: The NTT two-task driver could not share a connection to the cube.

Cause: An error occurred while reading the NTT communications link.

Cause: The Oracle listener process on the cube could not fork off a shadow process.

Cause: An error occurred while writing the NTT communications link.

Cause: Two-task driver could not allocate data buffers.

Cause: An error occurred while reading the NTT communications link.

Cause: An error occurred while writing the NTT communications linke.

Cause: The call to 'nrange()' failed while attempting to establish a connection.

Cause: The call to 'nfconn()' failed while attempting to establish a connection.

Cause: Two-task driver could not allocate data buffers.

Cause: The NTT two-task driver received an unexpected message type."

Cause: The NTT two-task driver received an unexpected message type."

Cause: The NTT two-task driver failed on an internal consistency check.

Cause: The NTT two-task driver failed on an internal consistency check.

Cause: The NTT two-task driver could not read configuration information from /etc/oratab.

Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.

Cause: The memory pool is exhausted.

Cause: The cause may be one of the following: - there is no ADI server defined to reflect a connection to the specified host. - the remote host is not known by the local system. - the ORACLE kernel on the remote host is not generated with the IPA driver

Cause: The SQL*Net IPA driver could not write the message into the message queue.

Cause: The SQL*Net IPA driver could not read a message from the message queue.

Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued.

Cause: The IPA driver tried to write a message in the queue that was too big for the queue.

Cause: A fatal error occurred during the resetting of the connection.

Cause: You have exhausted all your connections.

Cause: The SQL*Net IPA servers have not been started.

Cause: Environment variable(s) not set correctly.

Cause: Maximum number of servers reached.

Cause: Incorrect outgoing service name supplied.

Cause: The shared memory has not been set up correctly.

Cause: Fatal interprocess communication error.

Cause: The connect string is malformed.

Cause: The SID is unknown at the remote side.

Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side.

Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.

Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side.

Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.

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.

Cause: An internal error has occurred in the shared memory handling.

Cause: Fatal interprocess communication error.

Cause: There was no default host string specified in the configuration and the user didn't specify any explicit connect string.

Cause: The login (connect) string contains an invalid driver designator.

Cause: Error occurred while attempting to read a break message.

Cause: System unable to allocate needed virtual memory.

Cause: Syntax error in login string.

Cause: Unable to reset out of break state.

Cause: Error occurred while attempting to send a break message.

Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.

Cause: Message from partner contains bad header.

Cause: Unable to establish connection.

Cause: Error occurred while testing I/O status of the network connection.

Cause: The remote server was unable to start an ORACLE process on behalf of the client.

Cause: From the remote host's server: the database SID, specified in the login (connect) string, was not recognized.

Cause: Error found during recomputation of checksum or CRC.

Cause: Unable to transmit data to remote host.

Cause: Unable to receive data from remote host.

Cause: A function was called with an invalid argument.

Cause: The file block number is out of range of the file. The additional information returns the block number.

Cause: The I/O buffer was not aligned on a 2K boundary.

Cause: The additional information returns the block number

Cause: The read system call returned an error.

Cause: The write system call returned an error.

Cause: The Asynchronous I/O system call returned an error.

Cause: The Asynchronous I/O system call returned an error.

Cause: The Asynchronous I/O system call returned an error.

Cause: This write call may have been truncated. The additional information returns the block number and number of bytes.

Cause: This read call may have been truncated. The additional information returns the block number and number of bytes.

Cause: Either the ORACLE process id, or wait time or event ID is invalid.

Cause: Some system problems may exists on your system, please check error logs.

Cause: An invalid event ID is passed in to this routine.

Cause: Some system problems may exist on your system, please check error logs.

Cause: An invalid event id, or the low and high event ID do not exist.

Cause: Some system problems may exist on your system, please check error logs.

Cause: Invalid oracle process ID is passed in to this routine.

Cause: Some system problems may exists on your system, please check error logs.

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.

Cause: PL/SQL was unable to allocate additional storage. This message normally appears with an ORA-4030 or ORA-4031 error which gives additional information. Sometimes this error can be caused by runaway programs.

Cause: This is an internal error message. An error has been detected in a PL/SQL program.

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).

Cause: A call to PL/SQL function completed, but no RETURN statement was executed.

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.

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.

Cause: A user-defined exception was raised by PL/SQL code, but not handled.

Cause: An attempt was made to open a cursor that was already open.

Cause: Backtrace message as the stack is unwound by unhandled exceptions.

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.

Cause: The remote call has parameters that are cursor variables or lob variables. This cannot be handled by stored procedures on your server.

Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors.

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.

Cause: An error occurred while passing a Probe operation to the server for execution.

Cause: The current version of Probe is incompatible with the version on the ORACLE server.

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.

Cause: An error was detected by PL/SQL trying to load the external library dynamically.

Cause: An error was detected by PL/SQL trying to map the specified function dynamically.

Cause: ORA-06520 or ORA-065211 could stack this error with a system specific error string. Because this error may reveal sensitive file system information, it is not commonly used.

Cause: There is an upper limit on the number of arguments that one can pass to the external function.

Cause: The option specified is an unsupported feature for external procedures.

Cause: The length specified in the length variable has an illegal value. This can happen if you have requested 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.

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.

Cause: An error occurred in sqllib during execution of a Pro* external procedure.

Cause: An error occurred in during execution of a PL/SQL profiler procedure.

Cause: The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not match the version of the code in the server implementing the profiler.

Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized.

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.

Cause: A subscript was greater than the limit of a varray or non-positive for a varray or nested table.

Cause: An in-limit subscript was greater than the count of a varray or too large for a nested table.

Cause: The program attempted to access a Serially Reusable package in PL/SQL called from SQL context (trigger or otherwise). Such an access is currently unsupported.

Cause: The program attempted to use a dynamic statement string that was either NULL or 0 length.

Cause: The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position.

Cause: The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position.

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.

Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.

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.

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.

Cause: A pl/sql internal error occurred.

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 accompaning PLS-nnnnn error messages.

Cause: DDL statement is executed dynamically in illegal PL/SQL context. - Dynamic OPEN cursor for a DDL in PL/SQL - Bind variable's used in USING clause to EXECUTE IMMEDIATE a DDL - Define variable's used in INTO clause to EXECUTE IMMEDIATE a DDL

Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only.

Cause: The caller of a pipelined function did not need more rows to be produced by the pipelined function.

Cause: One possible cause might be there are too many DLLs open at the same time.

Cause: Usually a PL/SQL compilation 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.

Cause: You tried to create a package named "STANDARD", "DBMS_STANDARD" or "DEBUG_IO". These are currently reserved for use by user SYS.

Cause: There are no more items in the pipe.

Cause: Internal error from the dbms_pipe package.

Cause: The pipe buffer size has been exceeded.

Cause: The sender put different datatype on the pipe than that being requested (package 'dbms_pipe'). The numbers are: 6 - number, 9 - char, 12 - date.

Cause: Internal error from the dbms_pipe package.

Cause: Attempting to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.

Cause: Attempting 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.

Cause: The name to be resolved was specified as one of the following: - With three parts (A.B.C) but the A.B parts resolved to an object that did not expose visible nested procedures; the C part could not be resolved. - With two parts (A.B) and the A part resolved to an object that did not expose visible nested procedures; the B part could not be resolved.

Cause: The named object could not be found. Either it does not exist or you do not have 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.

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.

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 must have specified the same number of values to be bound for all bind variables.

Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an eralier release of 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 then at execute time there will be no value for this bind and the statement is meaningless.

Cause: The specified shared pool shared cursor could not be found, therefore it cannot be pinned/purged.

Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated. * A SQL statement references a stand-alone, PL/SQL function that contains an instruction to update the database.

Cause: A SQL statement references either a packaged, or a stand-alone, 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.

Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the 'Write no Package State' (WNPS). * A SQL statement references a stand-alone, PL/SQL function that modifies a package state. A stand-alone, PL/SQL function referenced by a SQL statement cannot modify a package state.

Cause: There are two possible causes for this message: * A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package state. * A remote, stand-alone function or a remote-mapped, local, stand-alone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.

Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.

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.

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.

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.

Cause: The bind variable specified by the user is not large enough to hold the output returned by the function or a procedure.

Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.

Cause: A CASE statement must either list all possible cases or have an else clause.

Cause: Specified feature is not yet supported for natively compiled PL/SQL modules yet.

Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR parameter.

Cause: The specified object was permanently kept, therefore, cannot be purged.

Cause: PL/SQL program execution used more call stack memory than permitted.

Cause: An attempt was made to run an AUTHID CURRENT_USER function or procedure, or to reference a BEQUEATH CURRENT_USER view, and the owner of that function, procedure, or view lacks INHERIT PRIVILEGES privilege on the calling user.

Cause: An attempt was made to perform certain large object (LOB) date type operations (for example, deep copying of a temporary or abstract LOB on the client side) while performing a remote procedural call (RPC). This is not currently supported.

Cause: The SNA software is not running.

Cause: The database string in the connect was invalid.

Cause: Context area failure.

Cause: Operating system refused request for memory.

Cause: Allocate system call failed.

Cause: SNA software switched from send to receive unexpectedly.

Cause: A parameter in an SNA call returned an unexpected value.

Cause: A reset was issued whilst in send state.

Cause: A reset was received from the partner whilst in receive state. This may be because the partner deallocated.

Cause: LU6.2 driver was unable to deallocate gracefully.

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.

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.

Cause: TLI received a message with an unrecognizable message type.

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.

Cause: TLI could not allocate heap space for the context area.

Cause: TLI failed to send a break message across the connection.

Cause: TLI failed to receive an expected break message.

Cause: TLI could not find your remote host information.

Cause: TLI could not find service information for the specified service name.

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.

Cause: TLI encountered an error receiving a message from the communication channel.

Cause: TLI encountered an error sending a message across the communication channel.

Cause: TLI failed to send a break message while handling an interrupt signal from the user.

Cause: TLI failed to assign a network address to the communication channel.

Cause: TLI failed to accept a connection request from the client.

Cause: TLI failed to connect the client to the remote server. The network line to the remote host may be down.

Cause: The database SID supplied in the database login string was not recognized by the remote host.

Cause: The remote TLI server received an undefined request.

Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message.

Cause: TLI failed to open the Streams clone device associated with the transport provider.

Cause: TLI cannot allocate space for the client's connection information.

Cause: TLI cannot allocate space for the client's disconnection information.

Cause: TLI failed to receive an expected disconnection message during connection release.

Cause: TLI failed to connect the client to the remote server.

Cause: TLI failed to properly close a connection after an error was received.

Cause: TLI timed out while attempting to connect to the remote TLI server.

Cause: TLI could not establish a connection to the remote TLI server.

Cause: The TLI server failed to open the Streams device associated with the transport provider.

Cause: The TLI server cannot allocate space for its requested network address.

Cause: The TLI server cannot allocate space for its actual network address.

Cause: The TLI server failed to assign the correct network address on which to listen for connections.

Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running.

Cause: TLI cannot allocate space for the TLI server's connection information.

Cause: The TLI server encountered an error while listening for connection requests.

Cause: TLI cannot allocate space for the TLI server's disconnection information.

Cause: The requested TLI server command must be issued from the same host on which the server is running.

Cause: The ORACLE process started by the TLI server was unable to synchronize its inherited connection.

Cause: The osn check server address failed. The bound server address was not the same as the requested binding address.

Cause: A call to sigaction() returned with a system error.

Cause: For SVR4, the netdir_getbyname() call failed for some unknown reason.

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.

Cause: The TLI server was unable to close a connection after passing it to an ORACLE process.

Cause: The TLI server could not open the file used to define the locations of remotely accessible databases.

Cause: The TLI server received an invalid command.

Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel.

Cause: TLI encountered an error sending a disconnect message closing the communication channel.

Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel.

Cause: TLI encountered an error sending a disconnect message closing the communication channel.

Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel.

Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel.

Cause: TLI failed to close the communication channel after receiving a disconnect message.

Cause: TLI cannot allocate space for disconnection information while closing the communication channel.

Cause: TLI encountered an error while sending its version information during connection establishment.

Cause: TLI encountered an error while awaiting the expected version information during connection establishment.

Cause: TLI encountered an error while sending a command message during connection establishment.

Cause: TLI encountered an error while awaiting the expected command message during connection establishment.

Cause: TLI encountered an error while sending break-mode message during connection establishment.

Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment.

Cause: TLI encountered an error while sending the connection parameters during connection establishment.

Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment.

Cause: TLI encountered an error while sending the completion status message during connection establishment.

Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment.

Cause: TLI encountered an error while awaiting an expected error message during connection establishment.

Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment.

Cause: TLI was unable to poll the communication channel for possible incoming messages.

Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.

Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.

Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.

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.

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.

Cause: An unknown event occurred on the client's listening socket.

Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process.

Cause: The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly.

Cause: The IPX driver has not been correctly installed.

Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.

Cause: A step in the SPX/IPX protocol initialization failed.

Cause: The file /dev/eth does not exist, or the driver it references could not be opened.

Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported.

Cause: The IPX driver has not been correctly installed.

Cause: The IPX driver has not been correctly installed.

Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid.

Cause: The ethernet driver is not installed correctly, or does not support this operation.

Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server.

Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly.

Cause: The SPX driver has not been correctly installed.

Cause: The SPX driver has not been correctly installed.

Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing.

Cause: CMX is not started on your system.

Cause: Local application oracmx has no local name assigned

Cause: ccp-xxxx is not started

Cause: remote application not entered in tns directory

Cause: no local name assigned to remote application

Cause: remote partner not listening

Cause: internal error in CMX

Cause: remote partner aborted

Cause: remote partner aborted

Cause: remote partner aborted

Cause: oracle process not found or wrong mode (should be 4751)

Cause: internal error in CMX

Cause: internal error in CMX

Cause: oracmx has been stopped, or user process has been aborted

Cause: connect sequence out of sync

Cause: internal error in CMX

Cause: remote partner aborted

Cause: internal error in CMX

Cause: internal error in CMX

Cause: internal error in CMX

Cause: received packets are corrupted

Cause: received packets are corrupted

Cause: internal error in CMX

Cause: break handling out of sync

Cause: received packets are corrupted

Cause: partner is not responding

Cause: internal error in CMX

Cause: internal error in CMX

Cause: ORACLE_SID is not entered in remote oratab

Cause: internal error in CMX

Cause: internal error in CMX

Cause: internal error in CMX

Cause: internal error in CMX

Cause: internal error in CMX

Cause: SQL*Net AppleTalk error codes base. This is not an error.

Cause: AppleTalk API received error in VMS system service.

Cause: Peer program may have aborted

Cause: Not enough memory available.

Cause: Erroneous file name

Cause: Too many database connections.

Cause: Unable to get Appletalk host name.

Cause: Incoming SQL*Net connection specified invalid SID name.

Cause: Unable to access CONFIG.ATK

Cause: Buffered I/O quota exceeded.

Cause: SQL*Net Appletalk listener could not create log file.

Cause: Host name specified in the login (connect string) is unknown.

Cause: The buffer size specified in the login string must be between 5 and 4096.

Cause: From the remote host's SQL*Net X.25 server: the database SID, specified in the login (connect) string, was not recognized.

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.

Cause: Process open file quota probably exceeded.

Cause: X.25 level 2 is down. X.25 link is not working.

Cause: Call back address probably same as called address.

Cause: The remote X.25 server was unable to start an ORACLE process on behalf of the client.

Cause: The environment variable $(ORACLE_SID) is not set.

Cause: $(ORACLE_HOME) environment variable not set.

Cause: The sltln name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length.

Cause: A string was passed to sltln containing a long environment variable. sltln accepts environment names of 30 or less characters.

Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.

Cause: Time() system call returned an error. Possible OS error.

Cause: Gettimeofday() system call returned an error. Possible OS error.

Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred.

Cause: The fsync system call returned an error. Possible OS error.

Cause: The size of the file to be opened exceeded the OS limit imposed on this process.

Cause: Getrusage system call returned an error. Possible OS error.

Cause: Gettimeofday system call returned an error. Possible OS error.

Cause: times system call returned an error. Possible OS error.

Cause: times system call returned an error. Possible OS error.

Cause: uname system call returned an error. Possible OS error.

Cause: Getrusage system call returned an error. Possible OS error.

Cause: gethostname system call returned an error. Possible OS error.

Cause: getenv call returned a null pointer.

Cause: Unix system() call failed

Cause: Malloc failed to allocate space to hold spooler arguments.

Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error.

Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.

Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.

Cause: Fork system call failed to create additional process. Probable resource limit reached.

Cause: The ulimit system call returned an error.

Cause: Additional information returned is error returned from sltln.

Cause: The ioctl call returned an error. Possible OS error.

Cause: The ioctl call returned an error. Possible OS error.

Cause: The ioctl call returned an error. Possible OS error.

Cause: error in mpcntl system call

Cause: Fopen failed to open file.

Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr.

Cause: An error was encountered when closing the file. Possible OS error.

Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr.

Cause: Unable to seek to desired position in file. Possible OS error. Possible internal error.

Cause: Unable to write item to file. Possible OS error. Possible permissions problem.

Cause: Unable to open error file. Possible permissions problem.

Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop.

Cause: Unable to close file. Possible OS error.

Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop.

Cause: Unable to seek to desired position in file. Possible OS error.

Cause: Unable to read file. Possible OS error.

Cause: Additional information indicates error returned from sltln.

Cause: supplied buffer was not big enough

Cause: An attempt was made to create a file that exceeds the process's file size limit.

Cause: An attempt was made to move and write to a bad device address.

Cause: sfofi returns an error.

Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS.

Cause: sfwfb returns an error.

Cause: The open() system call returned an error.

Cause: An error occurred when trying to get first semaphore set.

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.

Cause: Semget system call returned an error. Possible resource limit problem.

Cause: Semctl system call returned an error.

Cause: An error occurred while translating the name of the oracle executable.

Cause: System failed to set up signal handler.

Cause: System failed to set up signal handler to catch exceptions.

Cause: Error ocurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of oracle process.

Cause: An error occurred when creating a new process.

Cause: An oracle detached process died shortly after startup. Wait() indicated that a child process terminated.

Cause: Wait system call returned an error.

Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process.

Cause: This is an internal error.

Cause: Kill system call returned an error. Possible OS error.

Cause: Semop system call returned an error. Semaphore set may not exist.

Cause: Semop system call returned an error. Semaphore set may not exist.

Cause: Function was passed an invalid oracle process id.

Cause: Function was passed an invalid oracle process id.

Cause: Getpwuid() could not find an entry in the passwd file for a user.

Cause: Detached process succesfully execed, but died shortly thereafter. Additional information indicates exit code, and termination status.

Cause: An error occurred while trying to set an interval timer. Probable porting problem.

Cause: Function was called with an invalid oracle process number (0).

Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number.

Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and oracle process number.

Cause: Unable to access "oracle" program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.

Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist.

Cause: A group has not been set up for dba users.

Cause: A 0 pid was passed to spdde.

Cause: Splon constructed an ops$username logon which exceeded the alloted buffer space.

Cause: An error occurred when trying to get first semaphore set.

Cause: The ioctl call returned an error. Possible OS error.

Cause: times system call returned an error. Possible OS error.

Cause: The internal buffer is not big enough to hold the archive control string.

Cause: An invalid volume size was specified.

Cause: Some non-numeric text follows the volume size specification.

Cause: Volume size was specified for a disk file.

Cause: Stat on the log archiving device failed.

Cause: Log archiving to this device is unsupported.

Cause: The specified pathname is not a directory.

Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size.

Cause: The redo buffer size must be a multiple of machine block size.

Cause: Malloc library routine returned an error.

Cause: Smpdal was called when the PGA had not been previously created.

Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.

Cause: The specified datafile name contains '..'.

Cause: After normalizing the specified file name, the resulting file name was too long.

Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.

Cause: Fopen library routine returned an error.

Cause: Fclose library routine returned an error.

Cause: An error occurred while deleting a text file.

Cause: An error occurred while performing a string put operation.

Cause: The name for the message file overflows internal buffer.

Cause: The system failed to restore user exception handlers.

Cause: The system failed to restore user signal handlers.

Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0.

Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.

Cause: The system failed to setup an alternate signal stack.

Cause: An impossible request for binary to decimal conversion was made.

Cause: An impossible request for binary to decimal conversion was made

Cause: An impossible request for binary to decimal conversion was made.

Cause: An impossible request for decimal to binary conversion was made.

Cause: An impossible request for decimal to binary conversion was made.

Cause: The supplied buffer is not big enough to hold the full path name.

Cause: One of the database writer processes could not locate its entry in the SGA.

Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH.

Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.

Cause: One or more of the database writer processes is no longer running.

Cause: An error occurred when the database writer called the system timing function.

Cause: An error occurred when the database writer called the system timing function.

Cause: An oracle error occurred when translating the location of the dump file.

Cause: An oracle error occurred when translating the location of the dbs directory.

Cause: Chdir system call returned an error. Possible permission problems.

Cause: The server process was unable to fork a child process.

Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.

Cause: The wakeup monitor process died.

Cause: An improperly aligned function address was specified.

Cause: An invalid function address was specified.

Cause: A nonexistent or an invalid function name was specified.

Cause: An invalid function name/address was specified.

Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.

Cause: The directory specified as the value for the stated parameter could not be used.

Cause: Oracle failed to create a shared arena file.

Cause: Oracle attempted to create more shared arena files than permitted.

Cause: Oracle failed to acquire a shared arena lock.

Cause: kstat library returned an error. Possible OS failure

Cause: User tried to load a resource manager plan that does not exist.

Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group.

Cause: User session queued for longer than maximum specified queue queue duration time for consumer group.

Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group.

Cause: An attempt was made to turn on the Resource Manager when the database was closed.

Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.

Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was quiesced.

Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored.

Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.

Cause: The mset routine returned an error. Semaphore may not exist.

Cause: The mclear routine returned an error. Semaphore may not exist.

Cause: The cluster_status system call failed to get status information for the current cluster.

Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.

Cause: open failed when opening the file ?/dbs/sgadef@.dbf

Cause: Read had an error when reading sgadef.dbf file.

Cause: An error occurred in close, while closing the file "?/dbs/sgadef@.dbf"

Cause: The vm_statistics system call failed to get virtual memory statistics.

Cause: The vm_mapmem system call failed to get mapped memory statistics.

Cause: Lock manager must be initialized before converting locks.

Cause: lm_stat_lock failed.

Cause: lm_open or lm_open_convert failed.

Cause: When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf

Cause: lm_attach failed to attach to lock manager instance.

Cause: lm_create failed to create lock manager instance.

Cause: lm_convert failed to convert(get) lock.

Cause: lm_convert failed to put lock value.

Cause: lm_open failed.

Cause: lm_convert failed to get lock value.

Cause: lm_create failed.

Cause: Lock manager must be initialized before releasing locks.

Cause: lm_stat_lock failed during lock release/cancel.

Cause: lm_convert failed during lock release/cancel.

Cause: lm_cancel failed during lock release/cancel.

Cause: lm_close failed during lock release/cancel.

Cause: An error was encountered releasing the lock.

Cause: Unknown or unexpected error code.

Cause: lm_wait failed.

Cause: lm_post failed.

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

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

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