Oracle Messages ‘Cause and Action’
Note that only error messages with cause and actions go in .msg/.msb files; other information messages stay in the resources of the components concerned and are displayed with a standard AfxMessageBox call, rather than using the full rmum error stack.
ORA-00000, 00000, "normal, successful completion" Cause: Normal exit. Action: None. ORA-00001, 00000, "unique constraint (%s.%s) violated" Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level. Action: Either remove the unique restriction or do not insert the key. /0002 reserved for v2 compatibility (null column) /0003 reserved for v2 compatibility (column value truncated) /0004 reserved for v2 compatibility (end-of-fetch) /0009 reserved for v2 compatibility / / 10 - 49 user session and session switching errors / ORA-00017, 00000, "session requested to set trace event" Cause: The current session was requested to set a trace event by another session. Action: This is used internally; no action is required. ORA-00018, 00000, "maximum number of sessions exceeded" Cause: All session state objects are in use. Action: Increase the value of the SESSIONS initialization parameter. ORA-00019, 00000, "maximum number of session licenses exceeded" Cause: All licenses are in use. Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter. ORA-00020, 00000, "maximum number of processes (%s) exceeded" Cause: All process state objects are in use. Action: Increase the value of the PROCESSES initialization parameter. ORA-00021, 00000, "session attached to some other process; cannot switch session" Cause: The user session is currently used by others. Action: Do not switch to a session attached to some other process. ORA-00022, 00000, "invalid session ID; access denied" Cause: Either the session specified does not exist or the caller does not have the privilege to access it. Action: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege. ORA-00023, 00000, "session references process private memory; cannot detach session" Cause: An attempt was made to detach the current session when it contains references to process private memory. Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed. ORA-00024, 00000, "logins from more than one process not allowed in single-process mode" Cause: Trying to login more than once from different processes for ORACLE started in single-process mode. Action: Logoff from the other process. ORA-00025, 00000, "failed to allocate %s" Cause: Out of memory. Action: Restart with larger sga heap. ORA-00026, 00000, "missing or invalid session ID" Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION. Action: Retry with a valid session ID. ORA-00027, 00000, "cannot kill current session" Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session. Action: None. ORA-00028, 00000, "your session has been killed" Cause: A privileged user has killed your session and you are no longer logged on to the database. Action: Login again if you wish to continue working. ORA-00029, 00000, "session is not a user session" Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.). Action: Retry with a user session ID. ORA-00030, 00000, "User session ID does not exist." Cause: The user session ID no longer exists, probably because the session was logged out. Action: Use a valid session ID. ORA-00031, 00000, "session marked for kill" Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done. Action: No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner. ORA-00032, 00000, "invalid session migration password" Cause: The session migration password specified in a session creation call was invalid (probably too long). Action: Retry with a valid password (less than 30 chars). ORA-00033, 00000, "current session has empty migration password" Cause: An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed. Action: Create the session with a non-empty migration password. ORA-00034, 00000, "cannot %s in current PL/SQL session" Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by 'alter session disable commit in procedure') Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session. ORA-00035, 00000, "LICENSE_MAX_USERS cannot be less than current number of users" Cause: Action: ORA-00036, 00000, "maximum number of recursive SQL levels (%s) exceeded" Cause: An attempt was made to go more than the specified number of recursive SQL levels. Action: Remove the recursive SQL, possibly a recursive trigger. ORA-00037, 00000, "cannot switch to a session belonging to a different server group" Cause: An attempt was made to switch to a session in a different server group. This is not allowed. Action: Make sure the server switches to a session that belongs to its server group. ORA-00038, 00000, "Cannot create session: server group belongs to another user" Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user. Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner. ORA-00050, 00000, "operating system error occurred while obtaining an enqueue" Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low. Action: Look up the operating system error in your system documentation and perform the needed action. ORA-00051, 00000, "timeout occurred while waiting for a resource" Cause: Usually due to a dead instance. Action: Check for any dead, unrecovered instances and recover them. ORA-00052, 00000, "maximum number of enqueue resources (%s) exceeded" Cause: Ran out of enqueue resources. Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter. ORA-00053, 00000, "maximum number of enqueues exceeded" Cause: Ran out of enqueue state objects. Action: Increase the value of the ENQUEUES initialization parameter. ORA-00054, 00000, "resource busy and acquire with NOWAIT specified" Cause: Resource interested is busy. Action: Retry if necessary. ORA-00055, 00000, "maximum number of DML locks exceeded" Cause: Ran out of DML lock state objects. Action: Increase the value of the DML_LOCKS initialization parameter and warm start. ORA-00056, 00000, "DDL lock on object '%s.%s' is already held in an incompatible mode" Cause: An attempt was made to acquire a DDL lock that is already locked. Action: This happens if you attempt to drop a table that has parse locks on it. ORA-00057, 00000, "maximum number of temporary table locks exceeded" Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts. Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start. ORA-00058, 00000, "DB_BLOCK_SIZE must be %s to mount this database (not %s)" Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database. Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value. ORA-00059, 00000, "maximum number of DB_FILES exceeded" Cause: The value of the DB_FILES initialization parameter was exceeded. Action: Increase the value of the DB_FILES parameter and warm start. ORA-00060, 00000, "deadlock detected while waiting for resource" Cause: Transactions deadlocked one another while waiting for resources. Action: Look at the trace file to see the transactions and resources involved. Retry if necessary. ORA-00061, 00000, "another instance has a different DML_LOCKS setting" Cause: The shared instance being started is using DML locks, and the running instances are not, or vice-versa. Action: Ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero. ORA-00062, 00000, "DML full-table lock cannot be acquired; DML_LOCKS is 0" Cause: The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX). Action: Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement. ORA-00063, 00000, "maximum number of LOG_FILES exceeded" Cause: LOG_FILES initialization parameter value exceeded Action: Increase the value of the LOG_FILES initialization parameter and warm start. The parameter needs to be as large as the highest number of log files that currently exist rather than just the count of logs that exist. ORA-00064, 00000, "object is too large to allocate on this O/S (%s,%s)" Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system. Action: Reduce the value of the initialization parameter. ORA-00065, 00000, "initialization of FIXED_DATE failed" Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. Action: Make sure the initialization parameter is in the correct date format. ORA-00066, 00000, "LOG_FILES is %s but needs to be %s to be compatible" Cause: The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. Action: Change the value of the LOG_FILES initialization parameter to be compatible. ORA-00067, 00000, "invalid value %s for parameter %s; must be at least %s" Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. ORA-00068, 00000, "invalid value %s for parameter %s, must be between %s and %s" Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. ORA-00069, 00000, "cannot acquire lock -- table locks disabled for %s" Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ... ADD (...), and so on. Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command. / / 70 .. 90 generic debugger errors / ORA-00070, 00000, "command %s is not valid" Cause: An invalid debugger command was specified. Action: Type HELP to see the list of available commands. ORA-00071, 00000, "process number must be between 1 and %s" Cause: An invalid process number was specified. Action: Specify a valid process number. ORA-00072, 00000, "process \"%s\" is not active" Cause: An invalid process was specified. Action: Specify a valid process. ORA-00073, 00000, "command %s takes between %s and %s argument(s)" Cause: An incorrect number of arguments was specified. Action: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax. ORA-00074, 00000, "no process has been specified" Cause: No debug process has been specified. Action: Specify a valid process. ORA-00075, 00000, "process \"%s\" not found in this instance" Cause: The specified process was not logged on to the current instance. Action: Specify a valid process. ORA-00076, 00000, "dump %s not found" Cause: An attempt was made to invoke a dump that does not exist. Action: Type DUMPLIST to see the list of available dumps. ORA-00077, 00000, "dump %s is not valid" Cause: An attempt was made to invoke an invalid dump. Action: Try another dump. ORA-00078, 00000, "cannot dump variables by name" Cause: An attempt was made to dump a variable by name on a system that does not support this feature. Action: Try the PEEK command. ORA-00079, 00000, "variable %s not found" Cause: An attempt was made to dump a variable that does not exist. Action: Use a valid variable name. ORA-00080, 00000, "invalid global area specified by level %s" Cause: An attempt was made to dump an invalid global area. Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use to dump global area as well as bytes for every pointer; must be a multiple of 4. ORA-00081, 00000, "address range [%s, %s) is not readable" Cause: An attempt was made to read/write an invalid memory address range. Action: Try another address or length. ORA-00082, 00000, "memory size of %s is not in valid set of [1], [2], [4]%s%s%s%s%s" Cause: An invalid length was specified for the POKE command. Action: Use a valid length (either 1, 2, 4, or possibly 8). ORA-00083, 00000, "warning: possibly corrupt SGA mapped" Cause: Even though there may be SGA corruptions, the SGA was mapped. Action: Use the DUMPSGA command to dump the SGA. ORA-00084, 00000, "global area must be PGA, SGA, or UGA" Cause: An attempt was made to dump an invalid global area. Action: Specify either PGA, SGA, or UGA. ORA-00085, 00000, "current call does not exist" Cause: An invalid attempt was made to dump the current call heap. Action: Wait until the process starts a call. ORA-00086, 00000, "user call does not exist" Cause: An invalid attempt was made to dump the user call heap. Action: Wait until the process starts a call. ORA-00087, 00000, "command cannot be executed on remote instance" Cause: Cluster database command issued for non cluster database ORADEBUG command. Action: Issue the command without the cluster database syntax. ORA-00088, 00000, "command cannot be executed by shared server " Cause: Debug command issued on shared server. Action: Reissue the command using a dedicated server. ORA-00089, 00000, "invalid instance number in ORADEBUG command " Cause: An invalid instance number was specified in a cluster database ORADEBUG command. Action: Reissue the command with valid instance numbers. ORA-00090, 00000, "failed to allocate memory for cluster database ORADEBUG command " Cause: Could not allocate memory needed to execute cluster database oradebug. Action: Reissue the command on each instance with single-instance oradebug. / 91 .. 95 ksm large_pool_size and large_pool_min_alloc size errors ORA-00091, 00000, "LARGE_POOL_SIZE must be at least %s" Cause: The value of LARGE_POOL_SIZE is below the minimum size. Action: Increase the value of LARGE_POOL_SIZE past the minimum size. ORA-00092, 00000, "LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC" Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC. Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC. ORA-00093, 00000, "%s must be between %s and %s" Cause: The parameter value is not in a valid range. Action: Modify the parameter value to be within the specified range. ORA-00094, 00000, "%s requires an integer value" Cause: The parameter value is not an integer. Action: Modify the parameter value to be an integer. / ORA-00096, 00000, "invalid value %s for parameter %s, must be from among %s" Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. / ORA-00097, 00000, "use of Oracle SQL feature not in SQL92 %s Level" Cause: Usage of Oracle's SQL extensions. Action: ORA-00099, 00000, "timed out while waiting for resource, potential PDML deadlock" Cause: The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system. Action: Increase the the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation. ORA-00100, 00000, "no data found" Cause: An application made reference to unknown or inaccessible data. Action: Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100. / / 101 .. 149 shared server errors / ORA-00101, 00000, "invalid specification for system parameter DISPATCHERS" Cause: The syntax for the DISPATCHERS parameter is incorrect. Action: Refer to the manual for correct syntax. ORA-00102, 00000, "network protocol %s cannot be used by dispatchers" Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers. Action: Refer to the manual on network protocols supported by the dispatchers. ORA-00103, 00000, "invalid network protocol; reserved for use by dispatchers" Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers. Action: Specify other network protocols in the connection string. ORA-00104, 00000, "deadlock detected; all public servers blocked waiting for resources" Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources. Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS. ORA-00105, 00000, "dispatching mechanism not configured for network protocol %s" Cause: Trying to alter the dispatcher's configuration for a network protocol that was not specified in the INIT.ORA file. Action: Include the network protocol in the system parameter DISPATCHERS in INIT.ORA and re-start the system. ORA-00106, 00000, "cannot startup/shutdown database when connected to a dispatcher" Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher. Action: Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string. ORA-00107, 00000, "failed to connect to ORACLE listener process" Cause: Most likely due to the fact that ORACLE listener has not been started. Action: Start ORACLE listener if it has not been started. Or else contact your ORACLE representative. ORA-00108, 00000, "failed to set up dispatcher to accept connection asynchronously" Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations. Action: Contact your ORACLE representative. ORA-00111, 00000, "not all servers started because number of servers is limited to %s" Cause: An attempt was made to start more servers than the maximum number specified by the system parameter MAX_SHARED_SERVERS. Action: Increase the value of MAX_SHARED_SERVERS in INIT.ORA as needed or re-issue the ALTER SYSTEM SET SHARED_SERVERS command with an appropriate number of servers. ORA-00112, 00000, "only created up to %s (maximum specified) dispatchers" Cause: An attempt was made to start more dispatchers than the maximum number specified by the system parameter MAX_DISPATCHERS. Action: Increase the value of MAX_DISPATCHERS in INIT.ORA as needed. ORA-00113, 00000, "protocol name %s is too long" Cause: A protocol name specified in the DISPATCHERS system parameter is too long. Action: Use a valid protocol name for the DISPATCHERS value. ORA-00114, 00000, "missing value for system parameter SERVICE_NAMES" Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter. Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified. ORA-00115, 00000, "connection refused; dispatcher connection table is full" Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections. Action: Connect to a different dispatcher, or use a dedicated server. ORA-00116, 00000, "SERVICE_NAMES name is too long" Cause: A service name specified in the SERVICE_NAMES system parameter is too long. Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars). ORA-00117, 00000, "value out of range for system parameter SERVICE_NAMES" Cause: The specified value of the SHARED_SERVERS parameter is incorrect. Action: SHARED_SERVERS must be >= 0 and <= MAX_SHARED_SERVERS. ORA-00118, 00000, "value out of range for system parameter DISPATCHERS" Cause: The value of the DISPATCHERS parameter is incorrect. Action: The sum of all DISPATCHERS values must be >= 0 and <= MAX_DISPATCHERS. ORA-00119, 00000, "invalid specification for system parameter MTS_LISTENER_ADDRESS" Cause: The syntax for the MTS_LISTENER_ADDRESS parameter is incorrect. Action: Refer to the Oracle8 Server Reference Manual for the correct syntax. ORA-00120, 00000, "dispatching mechanism not enabled or installed" Cause: Either the dispatching mechanism was not enabled or the ORACLE executable image was not installed with the dispatching mechanism. Action: Refer to manual on how to enable the dispatching mechanism using system parameters in the INIT.ORA file. Failing that, consult your ORACLE representative. ORA-00121, 00000, "SHARED_SERVERS specified without DISPATCHERS" Cause: A definition for SHARED_SERVERS was specified in the INIT.ORA file, but no definition for DISPATCHERS was specified. Without a value for DISPATCHERS, shared servers will never be used. Action: Add a definition for DISPATCHERS in the INIT.ORA file (or take out the definition for SHARED_SERVERS, if shareds servers are not being used). ORA-00122, 00000, "cannot initialize network configuration" Cause: ORACLE could not initialize SQL*Net version 2. Action: Check the error stack for detailed information. ORA-00123, 00000, "idle public server terminating" Cause: Too many idle servers were waiting on the common queue. Action: This error is used internally, no action is required. ORA-00124, 00000, "DISPATCHERS specified without MAX_SHARED_SERVERS" Cause: A definition for DISPATCHERS was specified in the INIT.ORA file, but MAX_SHARED_SERVERS was specified as zero. Action: Specify MAX_SHARED_SERVERS to be greater than zero. ORA-00125, 00000, "connection refused; invalid presentation" Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. Action: Correct the PRESENTATION specified in the TNS address. ORA-00126, 00000, "connection refused; invalid duplicity" Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. Action: Correct the DUPLICITY specified in the TNS address. ORA-00127, 00000, "dispatcher %s does not exist" Cause: There is currently no dispatcher running with the specified name. Action: Retry with a name of the form "D###" denoting an existing dispatcher process. ORA-00128, 00000, "this command requires a dispatcher name" Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name' / / 150 .. 159 Oracle*XA errors / ORA-00150, 00000, "duplicate transaction ID" Cause: Attempted to start a new transaction with an ID already in use by an existing transaction. Action: Check your application. ORA-00151, 00000, "invalid transaction ID" Cause: The specified transaction ID does not correspond to an existing valid transaction. Action: Check your application. ORA-00152, 00000, "current session does not match requested session" Cause: The current session is not the same as the session that was passed into a upixado() call. Action: Check your application. ORA-00153, 00000, "internal error in XA library" Cause: The XA library could not access thread-specific pointers. Action: Contact customer support. ORA-00154, 00000, "protocol error in transaction monitor" Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended. Action: Contact the transaction monitor customer support. ORA-00155, 00000, "cannot perform work outside of global transaction" Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction. Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work. / / 160 .. 199 Distributed transaction errors (continued) / ORA-00160, 00000, "global transaction length %s is greater than maximum (%s)" Cause: An external global transaction ID with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00161, 00000, "transaction branch length %s is illegal (maximum allowed %s)" Cause: An external transaction branch ID with a length either too large or 0 was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00162, 00000, "external dbid length %s is greater than maximum (%s)" Cause: An external database name with too large a length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00163, 00000, "internal database name length %s is greater than maximum (%s)" Cause: An internal database name with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00164, 00000, "autonomous transaction disallowed within distributed transaction" Cause: A request was made by the application to start an autonomous transaction when the application was already in a distributed transaction. Action: Roll back or commit the current distributed transaction first. / / 200 .. 249 controlfile management errors / ORA-00200, 00000, "controlfile could not be created" Cause: It was not possible to create the controlfile. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the controlfile again. ORA-00201, 00000, "controlfile version %s incompatible with ORACLE version %s" Cause: The controlfile was created by incompatible software. Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new controlfile that is compatible with this release. ORA-00202, 00000, "controlfile: '%s'" Cause: This message reports the name file involved in other messages. Action: See associated error messages for a description of the problem. ORA-00203, 00000, "using the wrong controlfiles" Cause: The mount ID in the controlfile is not the same as the mount ID in the controlfile used by the first instance to mount this database. The controlfiles are for the same database but they are not the same files. Most likely one instance is using a backup controlfile. Action: Check that the correct controlfiles were specified. ORA-00204, 00000, "error in reading (block %s, # blocks %s) of controlfile" Cause: A disk I/O failure was detected on reading the controlfile. Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk. ORA-00205, 00000, "error in identifying controlfile, check alert log for more info" Cause: The system could not find a controlfile of the specified name and size. Action: Check that ALL controlfiles are online and that they are the same files that the system created at cold start time. ORA-00206, 00000, "error in writing (block %s, # blocks %s) of controlfile" Cause: A disk I/O failure was detected on writing the controlfile. Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk. ORA-00207, 00000, "controlfiles are not for the same database" Cause: The database ID in the controlfile is not the same as the database ID in the controlfile used by the first instance to mount this database. Most likely one of the mounts used the wrong controlfile or there are two databases with the same name. Action: Check that the controlfile is for the correct database and is not an old version. ORA-00208, 00000, "number of controlfile names exceeds limit of %s" Cause: An attempt was made to use more controlfiles than Oracle supports. Action: Shut down Oracle. Reduce the number of controlfiles specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files. ORA-00209, 00000, "control file blocksize mismatch, check alert log for more info" Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter. Action: Look at the alert log for more information. ORA-00210, 00000, "cannot open the specified controlfile" Cause: Cannot open the controlfile. Action: Check to make sure the controlfile exists and is not locked by some other program. ORA-00211, 00000, "controlfile does not match previous controlfiles" Cause: A controlfile was specified that belongs to another database. Action: Find and install the correct controlfile. ORA-00212, 00000, "block size %s below minimum required size of %s bytes" Cause: The block size specified was too small. Space for the system overhead is required. Action: Specify a larger block size and retry the operation. ORA-00213, 00000, "cannot reuse controlfile; old file size %s, %s required" Cause: To reuse a controlfile, it must be the same size as the one previously used. Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement. ORA-00214, 00000, "controlfile '%s' version %s inconsistent with file '%s' version %s" Cause: An inconsistent set of controlfiles, datafiles/logfiles, and redo files was used. Action: Use a consistant set of controlfiles, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period. ORA-00215, 00000, "must be at least one controlfile" Cause: No controlfile is specified or the controlfile specified does not exist. Action: Specify at least one valid controlfile and retry the operation. ORA-00216, 00000, "controlfile could not be resized for migration from 8.0.2" Cause: Controlfiles created by release 8.0.2 were missing some records. These records are automatically added by resizing the contolfile when attempting to run a later release. The resize failed. Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the controlfile more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumpped to the trace file to create a new controlfile. ORA-00218, 00000, "block size %s of controlfile does not match DB_BLOCK_SIZE (%s)" Cause: The block size as stored in the controlfile header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the controlfile has either been corrupted or belongs to a different database. Action: Restore a good copy of the controlfile. ORA-00219, 00000, "required controlfile size %s exceeds maximum allowable size %s" Cause: An invocation of CREATE DATABASE, CREATE CONTROLFILE, cfileCalcSizeList, or cfileCalcSizeArray was executed specifying a combination of parameters that would require the controlfile size in blocks to exceed the maximum allowable value. Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts. ORA-00220, 00000, "controlfile not mounted by first instance, check alert log for more info" Cause: The specified controlfile has a different mount ID than the other controlfiles that are being mounted. This means that the first instance to mount the database did not use this controlfile. Action: Find and install the correct controlfile. ORA-00221, 00000, "error on write to controlfile" Cause: An error occurred when writing to one or more of the controlfiles. Action: See accompanying messages. ORA-00222, 00000, "operation would reuse name of a currently mounted controlfile" Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted controlfile. Action: Retry the operation with a different filename. ORA-00223, 00000, "convert file is invalid or incorrect version" Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued. Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set. ORA-00224, 00000, "controlfile resize attempted with illegal record type (%s)" Cause: An attempt was made to expand or shrink the controlfile by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16). ORA-00225, 00000, "expected size %s of controlfile differs from actual size %s" Cause: The expected size of the controlfile as stored in its header was different than the actual operating system file size. This usually indicates that the controlfile was corrupted. Action: Restore a good copy of the controlfile. ORA-00226, 00000, "operation disallowed while alternate controlfile open" Cause: The attempted operation could not be executed at this time because this process had an alternate controlfile open for fixed table access. Action: Retry the operation after calling cfileUseCurrent. ORA-00227, 00000, "corrupt block detected in controlfile: (block %s, # blocks %s)" Cause: A block header corruption or checksum error was detected on reading the controlfile. Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command. ORA-00228, 00000, "length of alternate controlfile name exceeds maximum of %s" Cause: The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system. Action: Retry the operation with a shorter filename. ORA-00229, 00000, "operation disallowed: already hold snapshot controlfile enqueue" Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot controlfile enqueue. Action: Retry the operation after calling cfileUseCurrent to release the snapshot controlfile enqueue. ORA-00230, 00000, "operation disallowed: snapshot controlfile enqueue unavailable" Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot controlfile enqueue. Action: Retry the operation after the concurrent operation that is holding the snapshot controlfile enqueue terminates. ORA-00231, 00000, "snapshot controlfile has not been named" Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot controlfile had previously been specified. Action: Specify a name for the snapshot controlfile by calling cfileSetSnapshotName. ORA-00232, 00000, "snapshot controlfile is nonexistent, corrupt, or unreadable" Cause: The snapshot controlfile was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time). ORA-00233, 00000, "copy controlfile is corrupt or unreadable" Cause: The specified copy controlfile was found to be corrupt or unreadable during an invocation of cfileUseCopy. Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy. ORA-00234, 00000, "error in identifying or opening snapshot or copy controlfile" Cause: A snapshot or copy controlfile of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy. Action: Re-create the snapshot or copy controlfile using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively. ORA-00235, 00000, "controlfile fixed table inconsistent due to concurrent update" Cause: Concurrent update activity on a controlfile caused a query on a controlfile fixed table to read inconsistent information. Action: Retry the operation. ORA-00236, 00000, "snapshot operation disallowed: mounted controlfile is a backup" Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted controlfile is a backup controlfile. Action: Mount a current controlfile and retry the operation. ORA-00237, 00000, "snapshot operation disallowed: controlfile newly created" Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted controlfile that was newly created with CREATE CONTROLFILE was made. Action: Mount a current controlfile and retry the operation. ORA-00238, 00000, "operation would reuse a filename that is part of the database" Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. Action: Retry the operation with a different filename. / / 250 .. 299 archival & media recovery errors / ORA-00250, 00000, "archiver not started" Cause: An attempt was made to stop automatic archiving, but the archiver process was not running. Action: No action required. ORA-00251, 00000, "LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string %s" Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command. Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command. ORA-00252, 00000, "log %s of thread %s is empty, cannot archive" Cause: A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty. Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file. ORA-00253, 00000, "character limit %s exceeded by archive destination string %s" Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long. Action: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message. ORA-00254, 00000, "error in archive control string '%s'" Cause: The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter. Action: Check the archive string used to make sure it refers to a valid online device. ORA-00255, 00000, "error archiving log %s of thread %s, sequence # %s" Cause: An error occurred during archiving. Action: Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo. ORA-00256, 00000, "cannot translate archive destination string %s" Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated. Action: Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string. ORA-00257, 00000, "archiver error. Connect internal only, until freed." Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file. Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. ORA-00258, 00000, "manual archiving in NOARCHIVELOG mode must identify log" Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename. Action: Specify log by filename, by group number or by thread and sequence number. ORA-00259, 00000, "log %s of open thread %s is the current log, cannot archive" Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries. Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread. ORA-00260, 00000, "cannot find online log sequence %s for thread %s" Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs. Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number. ORA-00261, 00000, "log %s of thread %s is being archived or modified" Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log. Action: Wait for the current operation to complete and try again. ORA-00262, 00000, "current log %s of closed thread %s cannot switch" Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused. Action: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed. ORA-00263, 00000, "there are no logs that need archiving for thread %s" Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving. Action: No action required. ORA-00264, 00000, "no recovery required" Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery. Action: Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames. ORA-00265, 00000, "instance recovery required, cannot set ARCHIVELOG mode" Cause: The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles. Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option. ORA-00266, 00000, "name of archived log file needed" Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered. Action: Mount the correct redo log file and enter its name when it is requested. ORA-00267, 00000, "name of archived log file not needed" Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested. Action: Continue media recovery, but do not enter a new log name. ORA-00268, 00000, "specified log file does not exist '%s'" Cause: The given redo log file does not exist. Action: Check the spelling and capitalization of the filename and retry the command. ORA-00269, 00000, "specified log file is part of thread %s not %s" Cause: The given redo log file is not part of the given thread Action: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error. ORA-00270, 00000, "error creating archive log %s" Cause: An error was encountered when either creating or opening the destination file for archiving. Action: Check that the archive destination is valid and that there is sufficient space on the destination device. ORA-00271, 00000, "there are no logs that need archiving" Cause: An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived. Action: No action required. ORA-00272, 00000, "error writing archive log %s" Cause: An I/O error occurred while archiving a redo log file. Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device. ORA-00273, 00000, "media recovery of direct load data that was not logged" Cause: A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt. Action: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error. ORA-00274, 00000, "illegal recovery option %s" Cause: An illegal option was specified for a recovery command. Action: Correct the syntax and retry the command. ORA-00275, 00000, "media recovery has already been started" Cause: An attempt was made to start a second media recovery operation in the same session. Action: Complete or cancel the first media recovery session or start another session to perform media recovery. ORA-00276, 00000, "CHANGE keyword specified but no change number given" Cause: The CHANGE keyword was specified on the command line, but no change number was given. Action: Retry the command using a valid change number after the CHANGE keyword. ORA-00277, 00000, "illegal option to the UNTIL recovery flag %s" Cause: Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword. Action: Correct the syntax. ORA-00278, 00000, "log file '%s' no longer needed for this recovery" Cause: The specified redo log file is no longer needed for the current recovery. Action: No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future. ORA-00279, 00000, "change %s generated at %s needed for thread %s" Cause: The requested log is required to proceed with recovery. Action: Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL". ORA-00280, 00000, "change %s for thread %s is in sequence #%s" Cause: This message helps to locate the redo log file with the specified change number requested by other messages. Action: Use the information provided in this message to specify the required archived redo log files for other errors. ORA-00281, 00000, "media recovery may not be performed using dispatcher" Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method. Action: Connect to the instance via a dedicated server process to perform media recovery. ORA-00282, 00000, "UPI %s call not supported, use ALTER DATABASE RECOVER" Cause: The given UPI call is no longer supported. Action: Use the ALTER DATABASE RECOVER command for all recovery actions. ORA-00283, 00000, "recovery session canceled due to errors" Cause: An error during recovery was determined to be fatal enough to end the current recovery session. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. ORA-00284, 00000, "recovery session still in progress" Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. ORA-00285, 00000, "TIME not given as a string constant" Cause: UNTIL TIME was not followed by a string constant for the time. Action: Enter the time enclosed in single quotation marks. ORA-00286, 00000, "no members available, or no member contains valid data" Cause: None of the members of a redo log file group are available, or the available members do not contain complete data. Action: If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames are being used, especially if the redo log file is being accessed from a remote location. ORA-00287, 00000, "specified change number %s not found in thread %s" Cause: The given change number does not appear in any of the online redo logs for the given thread. Action: Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs. ORA-00288, 00000, "to continue recovery type ALTER DATABASE RECOVER CONTINUE" Cause: During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and / report errors. Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume. ORA-00289, 00000, "suggestion : %s" Cause: This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived. Action: Consider using this filename for the next log needed for recovery. ORA-00290, 00000, "operating system archival error occurred. See error below" Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error. Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation. ORA-00291, 0000, "numeric value required for PARALLEL option" Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism. Action: Re-enter the command with a numeric argument specifying the degree of parallelism desired. ORA-00292, 00000, "parallel recovery feature not installed" Cause: A parallel recovery was requested when the parallel recovery option is not installed. Action: Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file. ORA-00293, 00000, "controlfile out of sync with redo log" Cause: The redo log file and controlfile are out of sync because a non-current controle file was specified when the instance was started. Action: Retry the RECOVER command using the current controlfile, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause. ORA-00294, 00000, "invalid archivelog format specifier '%s'" Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T. Action: Correct the initialization file and re-start the instance. ORA-00295, 00000, "datafile number %s is invalid, must be between 1 and %s" Cause: An invalid file number was specified. Action: Specify a correct datafile number and retry the operation. ORA-00296, 00000, "maximum number of files (%s) exceeded for RECOVER DATAFILE LIST" Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user's RECOVER command. Action: Re-start the instance with a higher value for DB_FILES. ORA-00297, 00000, "must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START" Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START. Action: Contact customer support ORA-00298, 00000, "Missing or invalid TIMEOUT interval" Cause: A non-zero integer timeout interval (in minutes) must be specified after the TIMEOUT keyword. Action: Correct the syntax and retry the command. ORA-00299, 00000, "must use file-level media recovery on data file %s" Cause: The control file does not contain an entry for this file, so block media recovery cannot be done. Action: Restore the data file and perform file-level media recovery. / / 300..369 - Redo File errors / ORA-00300, 00000, "illegal redo log block size %s specified - exceeds limit of %s" Cause: The specified block size of the redo log is greater than the maximum block size for the operating system. Action: Create the redo log on a device with a smaller block size ORA-00301, 00000, "error in adding log file '%s' - file cannot be created" Cause: The creation of the redo log file failed Action: Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size. ORA-00302, 00000, "limit of %s logs exceeded" Cause: The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16). Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES. ORA-00303, 00000, "cannot process Multi-Strand Redo" Cause: A redo log containing Multi-Strand Redo has been detected. The current Oracle release cannot process this format of redo. Action: Use a later release that supports Multi-Strand Redo. to process this log. ORA-00304, 00000, "requested INSTANCE_NUMBER is busy" Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use. Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number. ORA-00305, 00000, "log %s of thread %s inconsistent; belongs to another database" Cause: The database ID in the redo log file does not match the database ID in the controlfile. This redo log file is not from the current database. Action: Specify the correct redo log file, then retry the operation. ORA-00306, 00000, "limit of %s instances in this database" Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances. Action: You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time ORA-00307, 00000, "requested INSTANCE_NUMBER out of range, maximum is %s" Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range. Action: Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation. ORA-00308, 00000, "cannot open archived log '%s'" Cause: The system cannot access a required archived redo log file. Action: Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session. ORA-00309, 00000, "log belongs to wrong database" Cause: The system cannot access the archived redo log because it belongs to another database. Action: Specify the correct redo log file, then retry the operation. ORA-00310, 00000, "archived log contains sequence %s; sequence %s required" Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified / during recovery. Action: Specify the correct redo log file; then retry the operation. ORA-00311, 00000, "cannot read header from archived log" Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. ORA-00312, 00000, "online log %s thread %s: '%s'" Cause: This message reports the filename for details of another message. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. ORA-00313, 00000, "open failed for members of log group %s of thread %s" Cause: The online log cannot be opened. May not be able to find file. Action: See accompanying errors and make log available. ORA-00314, 00000, "log %s of thread %s, expected sequence# %s doesn't match %s" Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00315, 00000, "log %s of thread %s, wrong thread # %s in header" Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00316, 00000, "log %s of thread %s, type %s in header is not log file" Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00317, 00000, "file type %s in header is not log file" Cause: This is not an archived log file. Action: Find the correct file and try again. ORA-00318, 00000, "log %s of thread %s, expected file size %s doesn't match %s" Cause: On header read the file size indicated in the control file did not match the file size contained in the log file. Action: Restore correct file or reset logs. ORA-00319, 00000, "log %s of thread %s has incorrect log reset status" Cause: Check of log file header at database open found that an online log has log reset data that is different from the controlfile. The log is probably an incorrectly restored backup. Action: Restore correct file or reset logs. ORA-00320, 00000, "cannot read file header from log %s of thread %s" Cause: The file is not available. Action: Restore the log file. ORA-00321, 00000, "log %s of thread %s, cannot update log file header" Cause: Cannot write to the log file. Action: Restore the access to the file. ORA-00322, 00000, "log %s of thread %s is not current copy" Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup. Action: Restore correct file or reset logs. ORA-00323, 00000, "Current log of thread %s not useable and all others need archiving" Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used. Action: Archive the logs for the thread then retry open. ORA-00324, 00000, "log file '%s' translated name '%s' too long, %s characters exceeds %s limit" Cause: the translated name for a log file is too long. Action: Choose a untranslated name that yields a shorter translated name. ORA-00325, 00000, "archived log for thread %s, wrong thread # %s in header" Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo. Action: Find correct archived log. ORA-00326, 00000, "log begins at change %s, need earlier change %s" Cause: The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo. Action: Find correct archived log. ORA-00327, 00000, "log %s of thread %s, physical size %s less than needed %s" Cause: A log file has shrunk in size. This is likely to have been caused by operator or operating system error. Action: Restore the log file from backup. If backup is not available, drop this log and re-create. If the database was shut down cleanly, no further action should be required; otherwise incomplete recovery may be required. ORA-00328, 00000, "archived log ends at change %s, need later change %s" Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo. Action: Find correct archived log. ORA-00329, 00000, "archived log begins at change %s, need change %s" Cause: The archived log is not the correct log. An earlier log is needed. Action: Restore the correct log file. ORA-00330, 00000, "archived log ends at change %s, need change %s" Cause: The archived log is not the correct log. A later log is needed. Action: Restore the correct log file. ORA-00331, 00000, "log version %s incompatible with ORACLE version %s" Cause: The log was written by incompatible version of Oracle. Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software. ORA-00332, 00000, "archived log is too small - may be incompletely archived" Cause: The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver. Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived. ORA-00333, 00000, "redo log read error block %s count %s" Cause: An IO error occurred while reading the log described in the accompanying error. Action: Restore accessibility to file, or get another copy of the file. ORA-00334, 00000, "archived log: '%s'" Cause: Reporting filename for details of another error Action: See associated error messages ORA-00335, 00000, "online log %s: No log with this number, log does not exist" Cause: Reporting filename for details of another error Action: See associated error messages ORA-00336, 00000, "log file size %s blocks is less than minimum %s blocks" Cause: The log file size as specified in create database is too small. Action: Increase the log file size. ORA-00337, 00000, "log file '%s' does not exist and no size specified" Cause: An attempt to add a log found neither an existing file nor a size for creating the file. Action: Specify a size for the log file. ORA-00338, 00000, "log %s of thread %s is more recent than controlfile" Cause: The controlfile change sequence number in the log file is greater than the number in the controlfile. This implies that the wrong controlfile is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the controlfile change sequence number until it is great enough. Action: Use the current controlfile or do backup controlfile recovery to make the controlfile current. Be sure to follow all restrictions on doing a backup controlfile recovery. ORA-00339, 00000, "archived log does not contain any redo" Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log. Action: Restore the correct log file. ORA-00340, 00000, "IO error processing online log %s of thread %s" Cause: An IO error occurred on the named online log. Action: Restore accessibility to file, or restore file from backup. ORA-00341, 00000, "log %s of thread %s, wrong log # %s in header" Cause: The internal information in an online log file does not match the controlfile. Action: Restore correct file or reset logs. ORA-00342, 00000, "archived log was created before last RESETLOGS" Cause: Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo. Action: Supply the correct log file. ORA-00343, 00000, "too many errors, log member closed" Cause: The maximum number of errors on this log member has been exceeded. Action: Correct the underlying problem by referring to the other error messages found with this one. ORA-00344, 00000, "unable to re-create online log '%s'" Cause: An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. Action: Correct the file/device as indicated by accompanying errors. ORA-00345, 00000, "redo log write error block %s count %s" Cause: An IO error has occurred while writing the log Action: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery. ORA-00346, 00000, "log member marked as STALE" Cause: A log file member no longer is complete. Action: Correct the underlying problem by referring to the other error messages found with this one. ORA-00347, 00000, "log %s of thread %s, expected block size %s doesn't match %s" Cause: On header read the blocksize indicated in the control file did not match the blocksize contained in the log file. Action: Restore correct file or reset logs. ORA-00348, 00000, "single-process redo failure. Must abort instance" Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. Action: Shutdown abort and warmstart the database. ORA-00349, 00000, "failure obtaining block size for '%s'" Cause: The operating system was unable to determine the blocksize for the given filename. Action: Consult the accompanying error message, and correct the device or specify another filename. ORA-00350, 00000, "log %s of thread %s needs to be archived" Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled. Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files. ORA-00351, 00000, "recover-to time invalid" Cause: The time specified in a recover-until statement must be after January 1st 1988. Action: Specify a time after January 1st 1988. ORA-00352, 00000, "all logs for thread %s need to be archived - cannot enable" Cause: Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread. Action: Archive a log for the thread or disable media recovery. ORA-00353, 00000, "log corruption near block %s change %s time %s" Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption. Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time. ORA-00354, 00000, "corrupt redo log block header" Cause: The block header on the redo block indicated by the accompanying error, is not reasonable. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. ORA-00355, 00000, "change numbers out of order" Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. ORA-00356, 00000, "inconsistent lengths in change description" Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. ORA-00357, 00000, "too many members specified for log file, the maximum is %s" Cause: An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created. Action: Use fewer log file members. ORA-00358, 00000, "Too many file members specified, the maximum is %s" Cause: A create or alter statement specified too many members in a parenthesised file list. Action: Specify a number of file members that is within the port-defined limit. ORA-00359, 00000, "logfile group %s does not exist" Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist. Action: Check the configuration of the log files and reissue the command. ORA-00360, 00000, "not a logfile member: %s" Cause: A filename was given to drop logfile member that is not a part of the database, or which is a data file. Action: Supply a valid logfile member name. ORA-00361, 00000, "cannot remove last log member %s for group %s" Cause: An attempt has been made to remove the last member of a log file group. Action: If desired, delete the entire log, by using DROP LOGFILE. ORA-00362, 00000, "member is required to form a valid logfile in group %s" Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile. Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE; ORA-00363, 00000, "log is not the archived version" Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command. Action: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included. ORA-00364, 00000, "cannot write header to new log member" Cause: An i/o error occurred when attempting to write the header to a log member that is being added to an existing group. Action: See accompanying errors. Fix problem or use another file. ORA-00365, 00000, "the specified log is not the correct next log" Cause: The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database. Action: Find the log that was generated by this copy of the database and give that filename to recovery. ORA-00366, 00000, "log %s of thread %s, checksum error in the file header" Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted Action: Find and install correct version of log or reset logs. ORA-00367, 00000, "checksum error in log file header" Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted Action: Find the correct file and try again. ORA-00368, 00000, "checksum error in redo log block" Cause: The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Action: Restore correct file or reset logs. ORA-00369, 00000, "Current log of thread %s not useable and other log being cleared" Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used. Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs. / / 370-389 kcb external errors / ORA-00370, 00000, "potential deadlock during kcbchange operation" Cause: Error code used internally by software. Should never be reported Action: Treat as internal error. See error 600. ORA-00371, 00000, "not enough shared pool memory" Cause: Init.ora parameter shared_pool_size is too small Action: Increase the parameter value ORA-00372, 00000, "file %s cannot be modified at this time" Cause: attempting to modify the contents of a file that cannot be modified. The file is most likely part of a read only tablespace but may be in the process of going offline, or the database may be in the process of closing. Action: check the status of the file and its tablespace ORA-00373, 00000, "online log version %s incompatible with ORACLE version %s" Cause: The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle. Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software. ORA-00374, 00000, "parameter db_block_size = %s invalid ; must be a multiple of %s in the range [%s..%s]" Cause: invalid value for db_block_size parameter Action: adjust parameter and restart ORA-00375, 00000, "unable to get default db_block_size" Cause: the system was unable to determine the default db_block_size Action: see accompanying system specific error. As a workaround, specify the blocksize in the INIT.ORA file. ORA-00376, 00000, "file %s cannot be read at this time" Cause: attempting to read from a file that is not readable. Most likely the file is offline. Action: Check the state of the file. Bring it online ORA-00377, 00000, "Frequent backups of file %s causing write operation to stall" Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete. Action: Increase the interval between begin hot-backup commands for this file. ORA-00378, 00000, "buffer pools cannot be created as specified" Cause: Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration. Action: Either increase the number of buffers and/or number of lru latches or configure smaller buffer pools. ORA-00379, 00000, "no free buffers available in buffer pool %s for block size %sK" Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available. Action: Increase the number of buffers in the specified pool for the specified block size ORA-00380, 00000, "cannot specify db_%sk_cache_size since %sK is the standard block size" Cause: User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal. Action: Specify the standard block size cache using db_cache_size (DEFAULT pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are required). Do NOT use the corresponding db_nk_cache_size parameter for the standard block size. ORA-00381, 00000, "cannot use both new and old parameters for buffer cache size specification" Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32) } AND one or more of { db_block_buffers , buffer_pool_keep , buffer_pool_recycle }. This is illegal. Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don't specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes. ORA-00382, 00000, "%s not a valid block size, valid range [%s..%s]" Cause: User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform. Action: Remove corresponding parameter from the "init.ora" file and restart the instance. ORA-00383, 00000, "DEFAULT cache for blocksize %s cannot be reduced to zero" Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce db_K_cache_size to zero while there were still online tablespaces with blocksizeK. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero. Action: Offline any tablespaces with the corresponding blocksize and then perform the operation again. ORA-00384, 00000, "Insufficient memory to grow cache" Cause: The system could not allocate sufficient memory to grow the cache to the specified size. Action: Attempt a smaller increase in the value of the parameter. / / 390-399: more Redo log errors / ORA-00390, 00000, "log %s of thread %s is being cleared, cannot become current log" Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log. ORA-00391, 00000, "All threads must switch to new log format at the same time" Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time. Action: Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database. ORA-00392, 00000, "log %s of thread %s is being cleared, operation not allowed" Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log. ORA-00393, 00000, "log %s of thread %s is needed for recovery of offline datafiles" Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped. Action: Archive the log then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command. ORA-00394, 00000, "online log reused while attempting to archive it" Cause: It has been detected that an online log that is being archived has been reused Action: Cannot archive the logfile anymore since it has been overwritten ORA-00395, 00000, "online logs for the clone database must be renamed" Cause: A clone database open forces logfile renaming to avoid overwriting the primary logfiles Action Rename the logfiles manually or using the log_file_name_convert initialization parameter ORA-00396, 00000, "error %s required fallback to single-pass recovery" Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error. Action Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the new algorithm. This usually requires making more main storage available to the recovery process. ORA-00397, 00000, "lost write detected for file %s, block %s" Cause: The specified block is missing changes that should have been written to disk, indicating a lost write by the file i/o subsystem or volume manager. Action: Run diagnostic checks on the i/o subsystem and resolve any errors ORA-00398, 00000, "abort thread recovery due to reconfiguration" Cause: Global enqueue service reconfiguration occurred during instance/crash recovery. Action: This is used internally, no action is required. ORA-00399, 0000, "corrupt change description in redo log" Cause: A change vector in the redo log failed validation checks. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. / / 400-420: KCK errors / ORA-00400, 00000, "invalid release value %s for parameter %s" Cause: The release level given for the specified init parameter is invalid. Action: Correct the parameter value in the parameter file and retry. ORA-00401, 00000, "the value for parameter %s is not supported by this release" Cause: The value specified cannot be supported by this release of the software. Action: Choose an appropriate value, or remove the parameter value to use the default value. ORA-00402, 00000, "database changes by release %s cannot be used by release %s" Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters. Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the init file. ORA-00403, 00000, "%s (%s) is not the same as other instances (%s)" Cause: Another instance has set the compatible or compatible no recovery parameters differently than this instance. Action: Change the parameters of the current instance to match other instances already running. ORA-00404, 00000, "Convert file not found: '%s'" Cause: The file used for converting the database from V7 to V8 could not be found. Action: Verify that the migration process has been started on this database and that the convert filename is accessable. ORA-00405, 00000, "compatibility type \"%s\"" Cause: Reporting a type associated with another error. Action: See accompanying error ORA-00406, 00000, "COMPATIBLE parameter needs to be %s or greater" Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. Action: Shutdown and startup with a higher compatibility setting. ORA-00407, 00000, "rolling upgrade from release %s.%s to %s.%s is not allowed" Cause: Another instance executing software at a different point release already has the database mounted. Action: Shutdown all instances then startup with the new software. ORA-00408, 00000, "parameter %s is set to TRUE" Cause: Reporting the parameter that resulted in the compatibility error. Action: Shutdown and startup with a higher compatibility setting. / / 436-439: Oracle licensing ercs / ORA-00436, 00000, "ORACLE is not licensed. Contact Oracle Corp. for assistance" Cause: Action: ORA-00437, 00000, "ORACLE feature is not licensed. Contact Oracle Corp. for assistance" Cause: ORACLE feature is not licensed. Action: Contact ORACLE for assistance. ORA-00438, 00000, "%s Option not installed" Cause: The specified option is not installed. Action: Purchase and install the option. ORA-00439, 00000, "feature not enabled: %s" Cause: The specified feature is not enabled. Action: Do not attempt to use this feature. / / 440-460 Detached process startup errors / ORA-00443, 00000, "background process \"%s\" did not start" Cause: The specified process did not start. Action: Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory. ORA-00444, 00000, "background process \"%s\" failed while starting" Cause: Usually due to a bad (or non-existent) background process image. Action: Get a good background process image. ORA-00445, 00000, "background process \"%s\" did not start after %s seconds" Cause: The specified process did not start after the specified time. Action: Ensure that the background did not die and leave a trace file. ORA-00446, 00000, "background process started when not expected" Cause: The background process specified started up AFTER the RDBMS was already running. Action: If nobody at your site started the process, then this is an internal error. ORA-00447, 00000, "fatal error in background process" Cause: One of the background processes died unexpectedly. Action: Warm start the system. ORA-00448, 00000, "normal completion of background process" Cause: One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit. Action: Warm start the system. ORA-00449, 00000, "background process '%s' unexpectedly terminated with error %s" Cause: A foreground process needing service from a background process has discovered the process died. Action: Consult the error code, and the trace file for the process. / / 470-480 Detached process death errors (signaled in foreground) / ORA-00470, 00000, "LGWR process terminated with error" Cause: The log writer process died Action: Warm start instance ORA-00471, 00000, "DBWR process terminated with error" Cause: The database writer process died Action: Warm start instance ORA-00472, 00000, "PMON process terminated with error" Cause: The process cleanup process died Action: Warm start instance ORA-00473, 00000, "ARCH process terminated with error" Cause: The archive process died Action: Warm start instance ORA-00474, 00000, "SMON process terminated with error" Cause: The system cleanup process died Action: Warm start instance ORA-00475, 00000, "TRWR process terminated with error" Cause: The system tracing process died Action: Warm start instance ORA-00476, 00000, "RECO process terminated with error" Cause: The distributed transaction (two-phase commit) recovery process died. Action: Warm start instance ORA-00477, 00000, "SNP* process terminated with error" Cause: A materialized view refresh process died Action: PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle support. ORA-00480, 00000, "LCK* process terminated with error" Cause: A system lock process died Action: Warm start instance ORA-00481, 00000, "LMON process terminated with error" Cause: The global enqueue service monitor process died Action: Warm start instance ORA-00482, 00000, "LMD* process terminated with error" Cause: A global enqueue service daemon process died Action: Warm start instance ORA-00483, 00000, "During shutdown a process abnormally terminated" Cause: One of the background processes did not exit normally at or near the time of shutdown. Action: Use shutdown abort. ORA-00484, 00000, "LMS* process terminated with error" Cause: A global cache service process died Action: Warm start instance / / 00486-00569 / ORA-00568, 00000, "Maximum number of interrupt handlers exceeded" Cause: User specified too many ^c handlers Action: Remove some old handlers. / / 00570-00599 SQL*Connect Opening & Reading Files / ORA-00574, 00000, "osndnt: $CANCEL failure (break)" Cause: Action: ORA-00575, 00000, "osndnt: $QIO failure (send out-of-band break)" Cause: Action: ORA-00576, 00000, "in-band break protocol error" Cause: Action: ORA-00577, 00000, "out-of-band break protocol error" Cause: Action: ORA-00578, 00000, "reset protocol error" Cause: Action: ORA-00579, 00000, "osndnt: server received malformed connection request" Cause: Action: ORA-00580, 00000, "protocol versions do not match" Cause: Action: ORA-00581, 00000, "osndnt: cannot allocate context area" Cause: Action: ORA-00582, 00000, "osndnt: cannot deallocate context area" Cause: Action: ORA-00583, 00000, "osndnt: $TRNLOG failure" Cause: Action: ORA-00584, 00000, "cannot close connection" Cause: Action: ORA-00585, 00000, "host name has incorrect form" Cause: Action: ORA-00586, 00000, "osndnt: LIB$ASN_WTH_MBX failure" Cause: Action: ORA-00587, 00000, "cannot connect to remote host" Cause: Action: ORA-00588, 00000, "message from host was too short" Cause: Action: ORA-00589, 00000, "message from host had incorrect data length" Cause: Action: ORA-00590, 00000, "message from host had incorrect message type" Cause: Action: ORA-00591, 00000, "incorrect number of bytes written" Cause: Action: ORA-00592, 00000, "osndnt: $QIO failure (mailbox queue)" Cause: Action: ORA-00593, 00000, "osndnt: $DASSGN failure (network device)" Cause: Action: ORA-00594, 00000, "osndnt: $DASSGN failure (mailbox)" Cause: Action: ORA-00595, 00000, "osndnt: $QIO failure (receive)" Cause: Action: ORA-00596, 00000, "osndnt: $QIO failure (send)" Cause: Action: ORA-00597, 00000, "osndnt: $QIO failure (mailbox requeue)" Cause: Action: ORA-00598, 00000, "osndnt: $QIO failure (mailbox read)" Cause: Action: ORA-00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition. Action: Report as a bug - the first argument is the internal error number ORA-00601, 00000, "cleanup lock conflict" Cause: PMON process runs into lock conflict trying to recovery processes Action: This is trapped internally, no action necessary ORA-00602, 00000, "internal programming exception" Cause: Internal programming exception Action: Report as bug / Caution: following error code not relocatable ORA-00603, 00000, "ORACLE server session terminated by fatal error" Cause: An ORACLE server session is in an unrecoverable state. Action: Login to ORACLE again so a new server session will be created / automatically. Examine the session trace file for more / information. ORA-00604, 00000, "error occurred at recursive SQL level %s" Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables). Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. / /0605 reserved for v2 compatibility / ORA-00606, 00000, "Internal error code" Cause: A call to deferred upi functions was made in non deferred mode Action: Report as a bug. ORA-00607, 00000, "Internal error occurred while making a change to a data block" Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block. Action: call Oracle Support ORA-00701, 00000, "object necessary for warmstarting database cannot be altered" Cause: Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database. Action: None. ORA-00702, 00000, "bootstrap verison '%s' inconsistent with version '%s'" Cause: The reading version of the boostrap is incompatible with the current bootstrap version. Action: Restore a version of the software that is compatible with this bootstrap version. ORA-00703, 00000, "maximum number of row cache instance locks exceeded" Cause: There are not enough row cache enqueues. Action: Increase the row cache enqueue parameter and warm start the system. ORA-00704, 00000, "bootstrap process failure" Cause: Failure in processing bootstrap data - see accompanying error. Action: Contact your customer support representative. ORA-00705, 00000, "inconsistent state during start up; shut down the instance, then restart it" Cause: A previous attempt to start an instance was terminated. Action: Shut down the instance completely, then restart it. ORA-00816, 00000, "error message translation failed" Cause: Action: / / MODIFIED / msusaira 07/23/01 - modify 1257 error mesg / eyho 07/25/01 - remove obsolete v7 error messages on parallel server / mjstewar 04/04/01 - New OMF message. / jingliu 03/06/01 - fix error in message 1298, 1466 / eyho 03/06/01 - RAC name changes / dgprice 01/11/01 - bug 1394096 define buffer size limits error / yuli 01/18/01 - 1539879: change Cause and Action part of 1114 / amsrivas 12/12/00 - 1029386: modify 1153 - resetlogs/backup conflict. / mjstewar 12/13/00 - Automated standby file management / nlee 11/13/00 - Forward merge fix for bug 553250. / gkulkarn 10/30/00 - Add LogMiner Out-of-Memory Error / rpang 09/15/00 - Updated the cause of "unsupported character set" error / yuli 10/24/00 - Update message of 1092 / gkulkarn 08/01/00 - Reserve more error numbers for LogMiner / ajadams 07/07/00 - logminer dictionary message / aime 06/29/00 - Fix compile error / mjstewar 06/13/00 - OMF errors / ajadams 06/26/00 - even more Logminer errors / ajadams 06/21/00 - more LogMiner messages / jkundu 06/09/00 - adding Logminer trace event / apareek 04/14/00 - change 1162 text / gkulkarn 05/14/00 - Update Error #01312 / rjenkins 03/29/00 - change 1441 / ajadams 03/31/00 - add error code 1315 for logmnr / robermar 04/18/00 - Inspection Comments / apadmana 01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW / gkulkarn 02/01/00 - Add LogMiner sql function error messgaes / mjstewar 01/18/00 - Automatic removal of OS files. / robermar 01/27/00 - DB End Backout / msusaira 12/19/99 - add err 1257 / vsrihari 07/14/99 - add file locks error message / jkundu 07/06/99 - adding more LogMiner messages / nireland 04/14/99 - Imporove action text for ORA-1220. #863107 / swerthei 10/28/98 - noarchivelog -> NOARCHIVELOG in 1108 / swerthei 10/20/98 - modify 1108 for bug 719176 - online/backup conflict / vsrihari 08/29/98 - modifying file identify error message / fsanchez 08/19/98 - fix_kcv_mig / mcusson 05/29/98 - adding error message for LogMiner / swerthei 04/21/98 - messages for Oracle-managed hot-backup mode / / 900-999 parse errors - / carried over from V5 - desirable to add arguments wherever possible / ORA-00900, 00000, "invalid SQL statement" Cause: Action: ORA-00901, 00000, "invalid CREATE command" Cause: Action: ORA-00902, 00000, "invalid datatype" Cause: Action: ORA-00903, 00000, "invalid table name" Cause: Action: ORA-00904, 00000, "invalid column name" Cause: Action: ORA-00905, 00000, "missing keyword" Cause: Action: ORA-00906, 00000, "missing left parenthesis" Cause: Action: ORA-00907, 00000, "missing right parenthesis" Cause: Action: ORA-00908, 00000, "missing NULL keyword" Cause: Action: ORA-00909, 00000, "invalid number of arguments" Cause: Action: ORA-00910, 00000, "specified length too long for its datatype" Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000. Action: use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW ORA-00911, 00000, "invalid character" Cause: Action: ORA-00913, 00000, "too many values" Cause: Action: ORA-00914, 00000, "missing ADD keyword" Cause: Action: ORA-00915, 00000, "network access of dictionary table not currently allowed" Cause: Action: ORA-00917, 00000, "missing comma" Cause: Action: ORA-00918, 00000, "column ambiguously defined" Cause: Action: ORA-00919, 00000, "invalid function" Cause: Action: ORA-00920, 00000, "invalid relational operator" Cause: Action: ORA-00921, 00000, "unexpected end of SQL command" Cause: Action: ORA-00922, 00000, "missing or invalid option" Cause: Action: ORA-00923, 00000, "FROM keyword not found where expected" Cause: Action: ORA-00924, 00000, "missing BY keyword" Cause: Action: ORA-00925, 00000, "missing INTO keyword" Cause: Action: ORA-00926, 00000, "missing VALUES keyword" Cause: Action: ORA-00927, 00000, "missing equal sign" Cause: Action: ORA-00928, 00000, "missing SELECT keyword" Cause: Action: ORA-00929, 00000, "missing period" Cause: Action: ORA-00930, 00000, "missing asterisk" Cause: Action: ORA-00931, 00000, "missing identifier" Cause: Action: ORA-00932, 00000, "inconsistent datatypes" Cause: Action: ORA-00933, 00000, "SQL command not properly ended" Cause: Action: ORA-00934, 00000, "group function is not allowed here" Cause: Action: ORA-00935, 00000, "group function is nested too deeply" Cause: Action: ORA-00936, 00000, "missing expression" Cause: Action: ORA-00937, 00000, "not a single-group group function" Cause: Action: ORA-00938, 00000, "not enough arguments for function" Cause: Action: ORA-00939, 00000, "too many arguments for function" Cause: Action: ORA-00940, 00000, "invalid ALTER command" Cause: Action: ORA-00941, 00000, "missing cluster name" Cause: Action: ORA-00942, 00000, "table or view does not exist" Cause: Action: ORA-00943, 00000, "cluster does not exist" Cause: Action: ORA-00944, 00000, "insufficient number of clustered columns" Cause: Action: ORA-00945, 00000, "specified clustered column does not exist" Cause: Action: ORA-00946, 00000, "missing TO keyword" Cause: Action: ORA-00947, 00000, "not enough values" Cause: Action: ORA-00948, 00000, "ALTER CLUSTER statement no longer supported" Cause: Action: ORA-00949, 00000, "illegal reference to remote database" Cause: Action: ORA-00950, 00000, "invalid DROP option" Cause: Action: ORA-00951, 00000, "cluster not empty" Cause: Action: ORA-00952, 00000, "missing GROUP keyword" Cause: Action: ORA-00953, 00000, "missing or invalid index name" Cause: An index name of the form [ . ] is expected but not present. If OIDINDEX clause, index name must be Action: Enter an appropriate index name. ORA-00954, 00000, "missing IDENTIFIED keyword" Cause: Action: ORA-00955, 00000, "name is already used by an existing object" Cause: Action: ORA-00956, 00000, "missing or invalid auditing option" Cause: AUDIT or NOAUDIT statement contains an invalid auditing option. Action: Use a valid option. ORA-00957, 00000, "duplicate column name" Cause: Action: ORA-00958, 00000, "missing CHECK keyword" Cause: Action: ORA-00959, 00000, "tablespace '%s' does not exist" Cause: Action: ORA-00960, 00000, "ambiguous column naming in select list" Cause: A column name in the order-by list matches more than one select list columns. Action: Remove duplicate column naming in select list. ORA-00961, 00000, "bad datetime/interval value" Cause: Action: ORA-00962, 00000, "too many group-by / order-by expressions" Cause: The group-by or order-by column list contain more than 1000 expressions. Action: Use 1000 or less expressions in the group-by or order-by list. ORA-00963, 00000, "unsupported interval type" Cause: Action: ORA-00964, 00000, "table name not in FROM list" Cause: The table name referred in the select list is not specified in the from list. Action: Make sure the name is correctly specified and matches one of the names in the from list. ORA-00965, 00000, "column aliases not allowed for '*'" Cause: The statement is trying to alias the * expression in the select list which is not legal. Action: Remove the alias. ORA-00966, 00000, "missing TABLE keyword" Cause: Action: ORA-00967, 00000, "missing WHERE keyword" Cause: Action: ORA-00968, 00000, "missing INDEX keyword" Cause: Action: ORA-00969, 00000, "missing ON keyword" Cause: Action: ORA-00970, 00000, "missing WITH keyword" Cause: Action: ORA-00971, 00000, "missing SET keyword" Cause: Action: ORA-00972, 00000, "identifier is too long" Cause: An identifier with more than 30 characters was specified. Action: Specify at most 30 characters. ORA-00973, 00000, "invalid row count estimate" Cause: Action: ORA-00974, 00000, "invalid PCTFREE value (percentage)" Cause: Action: ORA-00975, 00000, "date + date not allowed" Cause: Action: ORA-00976, 00000, "LEVEL, PRIOR, or ROWNUM not allowed here" Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location. Action: Remove LEVEL, PRIOR, or ROWNUM. ORA-00977, 00000, "duplicate auditing option" Cause: AUDIT or NOAUDIT statement specifies an option more than once Action: Either use ALL with no other auditing options or make sure no option is listed more than once. ORA-00978, 00000, "nested group function without GROUP BY" Cause: Action: ORA-00979, 00000, "not a GROUP BY expression" Cause: Action: ORA-00980, 00000, "synonym translation is no longer valid" Cause: Action: ORA-00981, 00000, "cannot mix table and system auditing options" Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement. Action: You must issue table and system options in separate statements. ORA-00982, 00000, "missing plus sign" Cause: Action: ORA-00984, 00000, "column not allowed here" Cause: Action: ORA-00985, 00000, "invalid program name" Cause: Action: ORA-00986, 00000, "missing or invalid group name(s)" Cause: Action: ORA-00987, 00000, "missing or invalid username(s)" Cause: Action: ORA-00988, 00000, "missing or invalid password(s)" Cause: Action: ORA-00989, 00000, "too many passwords for usernames given" Cause: Action: ORA-00990, 00000, "missing or invalid privilege" Cause: Action: ORA-00991, 00000, "only MAC privileges may be granted to procedures" Cause: Object privileges or non-MAC system privileges were granted to the procedure. Action: Only grant MAC privileges using the PROCEDURE clause. ORA-00992, 00000, "invalid format for REVOKE command" Cause: Action: ORA-00993, 00000, "missing GRANT keyword" Cause: Action: ORA-00994, 00000, "missing OPTION keyword" Cause: Action: ORA-00995, 00000, "missing or invalid synonym identifier" Cause: Action: ORA-00996, 00000, "the concatenate operator is ||, not |" Cause: Action: ORA-00997, 00000, "illegal use of LONG datatype" Cause: Action: ORA-00998, 00000, "must name this expression with a column alias" Cause: Action: ORA-00999, 00000, "invalid view name" Cause: Action: / / parse errors continue at 1700 / / 1000-1099 program interface errors / ORA-01000, 00000, "maximum open cursors exceeded" Cause: Action: ORA-01001, 00000, "invalid cursor" Cause: Action: ORA-01002, 00000, "fetch out of sequence" Cause: This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement. Action: 1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then attempt to fetch again. ORA-01003, 00000, "no statement parsed" Cause: Action: ORA-01004, 00000, "default username feature not supported; logon denied" Cause: Action: ORA-01005, 00000, "null password given; logon denied" Cause: Action: ORA-01006, 00000, "bind variable does not exist" Cause: Action: ORA-01007, 00000, "variable not in select list" Cause: Action: ORA-01008, 00000, "not all variables bound" Cause: Action: ORA-01009, 00000, "missing mandatory parameter" Cause: Action: ORA-01010, 00000, "invalid OCI operation" Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You are using an Oracle client application linked with version 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0 (or lower) Oracle Server. 3) You are connected to a version 7.1 (or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or lower) Oracle Server. Action: For the above causes: 1) Do not use the invalid OCI operation. 2) If you do not wish to use encrypted connect passwords in your distributed database, set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If you do not wish to use encrypted database links in your distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, you must upgrade all Oracle Servers to version 7.1 (or higher). ORA-01011, 00000, "Cannot use v7 compatibility mode when talking to v6 server" Cause: Action: Use v6 sql language type. You may need to use the 'SET COMPATIBILITY V6' command ORA-01012, 00000, "not logged on" Cause: Action: ORA-01013, 00000, "user requested cancel of current operation" Cause: Action: ORA-01014, 00000, "ORACLE shutdown in progress" Cause: Action: ORA-01015, 00000, "logon called recursively" Cause: Action: ORA-01016, 00000, "This function can be called only after a fetch" Cause: Cursor in an invalid state. Action: Make sure that the oci/upi function is called after fetch. ORA-01017, 00000, "invalid username/password; logon denied" Cause: Action: ORA-01018, 00000, "column does not have a LONG datatype" Cause: Action: ORA-01019, 00000, "unable to allocate memory in the user side" Cause: The user side memory allocator returned error. Action: Increase the processes heap size or switch to the old set of calls. ORA-01020, 00000, "unknown context state" Cause: Action: ORA-01021, 00000, "invalid context size specified" Cause: Action: ORA-01022, 00000, "database operation not supported in this configuration" Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers. Action: You may need to upgrade one or more of your ORACLE servers or re-link your user side application with new libraries. Report the problem to Worldwide Customer Support. ORA-01023, 00000, "Cursor context not found (Invalid cursor number)" Cause: The cursor number is not a valid open cursor. Action: Make sure that the cursor is open. ORA-01024, 00000, "invalid datatype in OCI call" Cause: Action: ORA-01025, 00000, "UPI parameter out of range" Cause: An integer parameter to a upi function is out of range. Action: This usually indicates an error in a tool built on top of the oracle dbms. Report the error to your customer support representative. ORA-01026, 00000, "multiple buffers of size > 4000 in the bind list" Cause: More than one long buffer in the bind list. Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column. ORA-01027, 00000, "bind variables not allowed for data definition operations" Cause: An attempt was made to use a bind variable in a SQL data definition operation. Action: Such bind variables are not allowed. ORA-01028, 00000, "internal two task error" Cause: Received send long message but don't have the cursor context. Action: Report as a bug. ORA-01029, 00000, "internal two task error" Cause: Received a request to send the long again when there is no long Action: Report as a bug ORA-01030, 00000, "SELECT ... INTO variable does not exist" Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement. Action: If it is not possible to correct the statement, call customer support. ORA-01031, 00000, "insufficient privileges" Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login. Action: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label. ORA-01032, 00000, "no such userid" Cause: This is an internal error message related to Export/Import. Action: Contact customer support. ORA-01033, 00000, "ORACLE initialization or shutdown in progress" Cause: An attempt was made to log on while Oracle is being started up or shutdown. Action: Wait a few minutes. Then retry the operation. ORA-01034, 00000, "ORACLE not available" Cause: Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it. - The operating-system variable pointing to the instance is improperly defined. Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation. ORA-01035, 00000, "ORACLE only available to users with RESTRICTED SESSION privilege" Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on. Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege. ORA-01036, 00000, "illegal variable name/number" Cause: Unable to find bind context on user side Action: Make sure that the variable being bound is in the sql statement. ORA-01037, 00000, "maximum cursor memory exceeded" Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor. Action: Simplify the complex sql statement. ORA-01038, 00000, "cannot write database file version %s with ORACLE version %s" Cause: Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version. Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation. ORA-01039, 00000, "insufficient privileges on underlying objects of the view" Cause: Attempting to explain plan on other people's view without the necessary privileges on the underlying objects of the view. Action: Get necessary privileges or do not perform the offending operation. ORA-01040, 00000, "invalid character in password; logon denied" Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range. Action: Resubmit password with valid characters. ORA-01041, 00000, "internal error. hostdef extension doesn't exist" Cause: Pointer to hstdef extension in hstdef is null. Action: Report as a bug ORA-01042, 00000, "detaching a session with open cursors not allowed" Cause: An attempt was made to detach a seesio n which had open cursors. Action: Close all the cursors before detaching the session. ORA-01043, 00000, "user side memory corruption [%s], [%s], [%s], [%s]" Cause: The application code corrupted some of the usr memory used by oracle Action: Make sure that the application code is not overwriting memory. ORA-01044, 00000, "size %s of buffer bound to variable exceeds maximum %s" Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements) Action: Reduce buffer size. ORA-01045, 00000, "user %s lacks CREATE SESSION privilege; logon denied" Cause: A connect was attempted to a userid which does not have create session privilege. Action: Grant the user CREATE SESSION privilege. ORA-01046, 00000, "cannot acquire space to extend context area" Cause: Action: ORA-01047, 00000, "The above error occurred in schema=%s, package=%s, procedure=%s" Cause: Action: Informational message ORA-01048, 0000, "Couldn't find the specified procedure in the given context" Cause: The procedure user specified in deferred RPC doesn't exist. Action: Check to make sure that the procedure exists and is visible to the replication process. ORA-01049, 00000, "Bind by name is not spupportted in streamed RPC" Cause: A newer version of server is talking with this version requesting an operation not supported in this version. Action: ORA-01050, 00000, "cannot acquire space to open context area" Cause: Action: ORA-01051, 00000, "deferred rpc buffer format invalid" Cause: The deferred rpc data in sys.def$_call is corrupted. Action: Contact your customer support representive. ORA-01052, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST is not specified" Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two. Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one. ORA-01053, 00000, "user storage address cannot be read" Cause: Action: ORA-01054, 00000, "user storage address cannot be written" Cause: Action: ORA-01057, 00000, "invalid or ambiguous block.field reference in user exit" Cause: Action: ORA-01058, 00000, "internal New Upi interface error" Cause: Attempt to delete non existant hstdef extension. Action: Report as a bug. ORA-01059, 00000, "parse expected before a bind or execute" Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed. Action: Ensure the statement is parsed before a bind or execute. ORA-01060, 00000, "array binds or executes not allowed" Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor. Action: Bind a single cursor or execute the PL/SQL block once. ORA-01061, 00000, "cannot start up a V8 server using a V7 client application" Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server. Action: Use a client application linked with V8 (or higher) libraries.60 ORA-01062, 00000, "unable to allocate memory for define buffer" Cause: Exceeded the maximum buffer size for current plaform Action: Use piecewise fetch with a smaller buffer size / 1070 - 1099: V6 program interface errors ORA-01070, 00000, "Using an old version of Oracle for the server" Cause: Using pre 7.0.10.1 version of oracle for server Action: Upgrade server to post 7.0.10.1 version ORA-01071, 00000, "cannot perform operation without starting up ORACLE" Cause: Obvious Action: ORA-01072, 00000, "cannot stop ORACLE; ORACLE not running" Cause: Obvious Action: ORA-01073, 00000, "fatal connection error: unrecognized call type" Cause: An illegal internal operation was attempted. Action: Contact your customer support representative. ORA-01074, 00000, "cannot shut down ORACLE; inside a login session - log off first" Cause: Obvious Action: ORA-01075, 00000, "you are currently logged on" Cause: Attempt to login while logged in. Action: ORA-01076, 00000, "multiple logons per process not yet supported" Cause: Obvious Action: ORA-01077, 00000, "background process initialization failure" Cause: Failure during initialization of ORACLE background processes. Action: Further diagnostic information should be in the error stack or in the trace file. ORA-01078, 00000, "failure in processing system parameters" Cause: Failure during processing of INIT.ORA parameters during system startup. Action: Further diagnostic information should be in the error stack. ORA-01079, 00000, "ORACLE database was not properly created, operation aborted" Cause: There was an error when the database or controlfile was created. Action: Check what error was signaled when the database was first created or when the controlfile was recreated. Take appropriate actions to recreate the database or a new controlfile. ORA-01080, 00000, "error in shutting down ORACLE" Cause: Failure during system shutdown. Action: Further diagnostic information should be in the error stack. ORA-01081, 00000, "cannot start already-running ORACLE - shut it down first" Cause: Obvious Action: ORA-01082, 00000, "'row_locking = always' requires the transaction processing option" Cause: "row_locking = always" is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option. Action: Remove it from INIT.ORA file or set it to "default" or "intent". ORA-01083, 00000, "value of parameter \"%s\" is inconsistent with that of other instances" Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples. Action: Change the value of the parameter in INIT.ORA file to match that of other cluster database instances. ORA-01084, 00000, "invalid argument in OCI call" Cause: The failing OCI call contains an argument with an invalid value. Action: Use valid argument values. For more information, see the Programmer's Guide to the Oracle Call Interfaces and the appropriate programming language supplement. ORA-01085, 00000, "preceding errors in deferred rpc to \"%s.%s.%s\"" Cause: Errors were encountered when the named procedure was executed as a deferred remoted procedure call. Action: Correct the cause of the preceding errors. ORA-01086, 00000, "savepoint '%s' never established" Cause: Trying to roll back to a save point that was never established. Action: ORA-01087, 00000, "cannot start up ORACLE - currently logged on" Cause: Action: Logoff and then issue the STARTUP command. ORA-01088, 00000, "cannot shut down ORACLE while active processes exist" Cause: Users are still logged into the instance. Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. ORA-01089, 00000, "immediate shutdown in progress - no operations are permitted" Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated. Action: Wait for the instance to be restarted, or contact your DBA. ORA-01090, 00000, "shutdown in progress - connection is not permitted" Cause: The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE. Action: Wait for the instance to be restarted, or contact your DBA. ORA-01091, 00000, "failure during startup force" Cause: Unable to destroy the old SGA. Action: Manually remove the old SGA and reissue the STARTUP command ORA-01092, 00000, "ORACLE instance terminated. Disconnection forced" Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance. Action: Examine the alert log for more details. When the instance has been restarted, retry action. ORA-01093, 00000, "ALTER DATABASE CLOSE only permitted with no sessions connected" Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted. Action: Find the other sessions and log them out and resubmit the command ORA-01094, 00000, "ALTER DATABASE CLOSE in progress. Connections not permitted" Cause: Action: ORA-01095, 00000, "DML statement processed zero rows" Cause: During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point. Action: ORA-01096, 00000, "program version (%s) incompatible with instance (%s)" MERGE: 1095 RENUMBERED TO 1096 Cause: A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed. Action: Either relink the program with the same version as the database or restart the database using the old version of code. ORA-01097, 00000, "cannot shutdown while in a transaction - commit or rollback first" Cause: Obvious Action: ORA-01098, 00000, "program Interface error during Long Insert" Cause: Action: ORA-01099, 00000, "cannot mount database in SHARED mode if started in single process mode" Cause: Obvious Action: / / 1100 to 1260: db file errors / ORA-01100, 00000, "database already mounted" Cause: A database is already mounted in this instance. Action: ORA-01101, 00000, "database being created currently mounted by some other instance" Cause: Some other instance has the database of same name currently mounted and you are trying to create it. Action: Either change the database name or shutdown the other instance. ORA-01102, 00000, "cannot mount database in EXCLUSIVE mode" Cause: Some other instance has the database mounted exclusive or shared. Action: Shutdown other instance or mount in a compatible mode. ORA-01103, 00000, "database name '%s' in controlfile is not '%s'" Cause: The database name in the controlfile does not match your database name. Action: Either find the correct controlfile or change your database name. ORA-01104, 00000, "number of controlfiles (%s) does not equal %s" Cause: The number of controlfiles used by this instance disagrees with the number of controlfiles in an existing instance. Action: Check to make sure that all controlfiles are listed. ORA-01105, 00000, "mount is incompatible with mounts by other instances" Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why. Action: See accompanying errors. ORA-01106, 00000, "database must be closed before dismounting" Cause: Obvious Action: ORA-01107, 00000, "database must be mounted for media recovery" Cause: An attempt to perform media recovery was made but the database is not mounted. Action: Mount the database. ORA-01108, 00000, "file %s is in backup or media recovery" Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery. Action: Complete or cancel the media recovery session or backup. ORA-01109, 00000, "database not open" Cause: A command was attempted that requires the database to be open. Action: Open the database and try the command again ORA-01110, 00000, "data file %s: '%s'" Cause: Reporting file name for details of another error Action: See associated error message ORA-01111, 00000, "name for data file %s is unknown - rename to correct file" Cause: The data file was missing from a CREATE CONTROLFILE command or backup controlfile recovery was done with a controlfile that was saved before the file was created. Action: Rename the MISSING file to the name of the real file. ORA-01112, 00000, "media recovery not started" Cause: An attempt to continue media recovery is being made but media recovery was not started. Action: None. ORA-01113, 00000, "file %s needs media recovery" Cause: An attempt was made to online or open a database with a file that is in need of media recovery. Action: First apply media recovery to the file. ORA-01114, 00000, "IO error writing block to file %s (block # %s)" Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time. Action: Restore access to the device or remove unnecessary files to free up space. ORA-01115, 00000, "IO error reading block from file %s (block # %s)" Cause: Device on which the file resides is probably offline Action: Restore access to the device ORA-01116, 00000, "error in opening database file %s" Cause: Usually the file is not accessible. Action: Restore the database file. ORA-01117, 00000, "adding file '%s' with illegal block size: %s; limit is %s" Cause: An attempt was made to add a database file with a block size that is greater than the maximum block size allowed. Action: Retry the DDL command with a smaller block size. ORA-01118, 00000, "cannot add any more database files: limit of %s exceeded" Cause: There is no more room in the controlfile for adding database files. Action: Resize the controlfile or drop other tablespaces. ORA-01119, 00000, "error in creating database file '%s'" Cause: Usually due to not having enough space on the device. Action: ORA-01120, 00000, "cannot remove online database file %s" Cause: Attempting to drop a datafile when it is online Action: Take file offline before dropping. ORA-01121, 00000, "cannot rename database file %s - file is in use or recovery" Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered. Action: Close database in all instances and end all recovery sessions. ORA-01122, 00000, "database file %s failed verification check" Cause: The information in this file is inconsistent with information from the controlfile. See accompanying message for reason. Action: Make certain that the db files and controlfiles are the correct files for this database. ORA-01123, 00000, "cannot start online backup; media recovery not enabled" Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled. Action: Enable media recovery and retry this operation. ORA-01124, 00000, "cannot recover data file %s - file is in use or recovery" Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file. Action: Do not do media recovery. ORA-01125, 00000, "cannot disable media recovery - file %s has online backup set" Cause: An attempt to disable media recovery found that an online backup is still in progress. Action: End the backup of the offending tablespace and retry this command. ORA-01126, 00000, "database must be mounted EXCLUSIVE and not open for this operation" Cause: Obvious Action: ORA-01127, 00000, "database name '%s' exceeds size limit of %s characters" Cause: Obvious Action: ORA-01128, 00000, "cannot start online backup - file %s is offline" Cause: An attempt to start an online backup found that one of the files is offline. Action: Bring the offending files online and retry this command or do a cold backup. ORA-01129, 00000, "user's default or temporary tablespace does not exist" Cause: The user's default or temporary tablespace was dropped. Action: Reassign the default or temporary tablespace. ORA-01130, 00000, "database file version %s incompatible with ORACLE version %s" Cause: Action: ORA-01131, 00000, "DB_FILES system parameter value %s exceeds limit of %s" Cause: Action: ORA-01132, 00000, "length of database file name '%s' exceeds limit of %s characters" Cause: Action: ORA-01133, 00000, "length of log file name '%s' exceeds limit of %s characters" Cause: Action: ORA-01134, 00000, "database mounted exclusive by another instance" Cause: Action: ORA-01135, 00000, "file %s accessed for DML/query is offline" Cause: Attempted to access a data file that is offline Action: Bring the data file back online ORA-01136, 00000, "specified size of file %s (%s blocks) is less than original size of %s blocks" Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed Action: Create the file with a larger size. ORA-01137, 00000, "data file %s is still in the middle of going offline" Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline. Action: Wait a bit and try to online the file again. ORA-01138, 00000, "database must either be open in this instance or not at all" Cause: The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open. Action: Execute the operation in an open instance, open the datbase in this instance, or close the database in the other instances. ORA-01139, 00000, "RESETLOGS option only valid after an incomplete database recovery" Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session. Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS ORA-01140, 00000, "cannot end online backup - all files are offline" Cause: All the files were found to be offline when attempting to end an online backup. Action: None. Online backup does not need to be ended for this tablespace. ORA-01141, 00000, "error renaming data file %s - new file '%s' not found" Cause: An attempt to change a data file's name in the controlfile failed because no file was found with the new name. Action: Make sure that the data file has been properly renamed by the operating system and retry. ORA-01142, 00000, "cannot end online backup - none of the files are in backup" Cause: None of the files were found to be in online backup when attempting to end an online backup. Action: None. Online backup does not need to be ended for this tablespace. ORA-01143, 00000, "cannot disable media recovery - file %s needs media recovery" Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled. Action: Recover the offending file or drop the tablespace it belongs to and retry this command. ORA-01144, 00000, "File size (%s blocks) exceeds maximum of %s blocks" Cause: Specified file size is larger than maximum allowable size value. Action: Specify a smaller size. ORA-01145, 00000, "offline immediate disallowed unless media recovery enabled" Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode. Action:Take tablespace offline normally or shutdown abort. Reconsider your backup strategy. You could do this if you were archiving your logs. ORA-01146, 00000, "cannot start online backup - file %s is already in backup" Cause: When starting an online backup it was noticed that an online backup was already started for one of the data files. Action:End the first backup before beginning another. ORA-01147, 00000, "SYSTEM tablespace file %s is offline" Cause: A file belonging to the SYSTEM tablespace has been marked offline by the DBA. The database cannot be started until all SYSTEM tablespace files are online and openable. Action: Bring the file online. /1148 Reserved ORA-01149, 00000, "cannot shutdown - file %s has online backup set" Cause: An attempt to shutdown normally found that an online backup is still in progress. Action: End the backup of the offending tablespace and retry this command. ORA-01150, 00000, "cannot prevent writes - file %s has online backup set" Cause: An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. It will be necessary to write the file header to end the backup, but that would not be allowed if this command succeeded. Action: End the backup of the offending tablespace and retry this command. ORA-01151, 00000, "use media recovery to recover block, restore backup if needed" Cause: Error 1172 occurred. Action: This is additional information for error 1172. ORA-01152, 00000, "file %s was not restored from a sufficiently old backup " Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. Action: Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery. ORA-01153, 00000, "an incompatible media recovery is active" Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs Action: Complete or cancel the other media recovery session or RMAN backup ORA-01154, 00000, "database busy. Open, close, mount, and dismount not allowed now" Cause: Some operation is in progress that expects the opened/mounted state of this instance to remain the same. Action: Wait for the operation to complete then retry. If attempting to do a shutdown, SHUTDOWN ABORT will work. ORA-01155, 00000, "the database is being opened, closed, mounted or dismounted" Cause: The requested operation needs the instance to be in a particular state but the state is being changed. Action: Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work. ORA-01156, 00000, "recovery in progress may need access to files" Cause: Either media recovery or instance recovery is in progress. It may need the files this operation is being applied to. Action: Wait for recovery to complete. ORA-01157, 00000, "cannot identify/lock data file %s - see DBWR trace file" Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified. Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES. ORA-01158, 00000, "database %s already mounted" Cause: Another instance has a database by this name mounted. Action: Find which instance is still running. Perhaps you have not lost the controlfiles after all. ORA-01159, 00000, "file is not from same database as previous files - wrong database id" Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified. Action: Please double check the list of files provided to the CREATE ORA-01160, 00000, "file is not a %s" Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated. Action: Please double check the mentioned file. ORA-01161, 00000, "database name %s in file header does not match given name of %s" Cause: The database name given at the command line does not match the database name found in the file header. Action: Chance are good that the database name specified at the command line is incorrect. Resolve the descepency, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option. ORA-01162, 00000, "block size %s in file header does not match configured block sizes" Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file. Action:Configure the appropriate cache for this block size using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters. ORA-01163, 00000, "SIZE clause indicates %s (blocks), but should match header %s" Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header. Action: Specify the correct filename and size ( in bytes ). ORA-01164, 00000, "MAXLOGFILES may not exceed %s" Cause: MAXLOGFILES specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGFILES ORA-01165, 00000, "MAXDATAFILES may not exceed %s" Cause: MAXDATAFILES specified on the command line too large. Action: Resubmit the command with a smaller MAXDATAFILES ORA-01166, 00000, "file number %s is larger than %s (%s)" Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES. Action: Increase the maximum specified on the command line. ORA-01167, 00000, "two files are the same file/group number or the same file" Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same controlfile appears more than once in the control_files p parameter in the init.ora file. If this happens, check for additional error messages. Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate controlfile, check the control_files parameter in the init.ora file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual controlfiles themselves are unique. For example, in UNIX check for a symbolic or a hard link to another controlfile in the list. ORA-01168, 00000, "physical block size %s does not match size %s of other members" Cause: The file is located on a device with a different physical block size than the other members in the group Action: Use a physical device with matching block size. ORA-01169, 00000, "DATAFILE number 1 not found. Must be present" Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command. Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command. ORA-01170, 00000, "file not found '%s'" Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE. Action: The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit. ORA-01171, 00000, "datafile %s going offline due to error advancing checkpoint" Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block. Action: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online. ORA-01172, 00000, "recovery of thread %s stuck at block %s of file %s" Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. Action: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem then restore the file from a backup and recover it. ORA-01173, 00000, "data dictionary indicates missing data file from system tablespace" Cause: Either the database has been recovered to a point in time in the future of the controlfile or a datafile from the system tablespace was omitted from the create controlfile command previously issued. Action: For the former problem you need to recover the database from a more recent controlfile. For the latter problem, simply recreate the controlfile checking to be sure that you include all the datafiles in the system tablespace. ORA-01174, 00000, "DB_FILES is %s buts needs to be %s to be compatible" Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. Action: Change the value of the DB_FILES parameter to be compatible ORA-01175, 00000, "data dictionary has more than the %s files allowed by the instance" Cause: The data dictionary is found to have more files than that which can be supported by this instance. Action: Shutdown the instance and restart with a larger number of db_files ORA-01176, 00000, "data dictionary has more than the %s files allowed by the controlfie" Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the controlfile. Action: Recreate the controlfile with a larger MAXDATAFILES. ORA-01177, 00000, "data file does not match dictionary - probably old incarnation" Cause: When comparing the controlfile with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile. Action: Do a CREATE CONTROLFILE with the correct file or none at all. ORA-01178, 00000, "file %s created before last CREATE CONTROLFILE, cannot recreate" Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROL file command. The information needed to recreate the file was lost with the controlfile that existed when the file was added to the database. Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. ORA-01179, 00000, "file %s does not exist" Cause: During datafile recovery, a file was listed which was not part for the database. Action: Recheck the datafile name. Remember to use double quotes at the SQLDBA command line and remember that the file name is translated in the environment of the SQLDBA. ORA-01180, 00000, "can not create datafile 1" Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE. Action: Recover file from a backup or recreate database. ORA-01181, 00000, "file %s created before last RESETLOGS, cannot recreate" Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last RESETLOGS database open. Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. ORA-01182, 00000, "cannot create database file %s - file is in use or recovery" Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered. Action: Close database in all instances and end all recovery sessions ORA-01183, 00000, "cannot mount database in SHARED mode" Cause: Some other instance has the database mounted exclusive. Action: Shutdown other instance then mount shared. ORA-01184, 00000, "logfile group %s already exists" Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use. Action: Specify a different logfile number, or let the database choose an unused value. ORA-01185, 00000, "logfile group number %s is invalid" Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is too large. Action: Specify a correct logfile number. ORA-01186, 00000, "file %s failed verification tests" Cause: The data file did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01187, 00000, "cannot read from file %s because it failed verification tests" Cause: The data file did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01188, 00000, "Block size %s in header does not match physical block size %s" Cause: A log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the log. Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE. ORA-01189, 00000, "file is from a different RESETLOGS than previous files" Cause: In a CREATE CONTROLFILE command either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS. Action: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command. ORA-01190, 00000, "controlfile or data file %s is from before the last RESETLOGS" Cause: Attempting to use a data file when the log reset information in the file does not match the controlfile. Either the data file or the controlfile is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS. Action: Restore file from a more recent backup. ORA-01191, 00000, "file %s is already offline - cannot do a normal offline" Cause: When attempting to do a normal tablespace offline it was discovered that one of the files in the tablespace was already offline. Action: Either bring the datafile online first, or use another tablespace offline option. ORA-01192, 00000, "must have at least one enabled thread" Cause: You must specify at least two logfiles from at least one thread at the create contolfile command line. Action: Find the missing logfiles and resubmit the command with the newly found logfiles included in the command line. ORA-01193, 00000, "file %s is not the same file seen at start of recovery" Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery. Action:Ensure the correct file is available, then retry recovery. ORA-01194, 00000, "file %s needs more recovery to be consistent" Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. Action: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery. ORA-01195, 00000, "online backup of file %s needs more recovery to be consistent" Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended. Action: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery. ORA-01196, 00000, "file %s is inconsistent due to a failed media recovery session" Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file. Action:Either apply more logs until the file is consistent or restore the backup again and repeat recovery. ORA-01197, 00000, "thread %s only contains one log" Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs. Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE. ORA-01198, 00000, "must specify size for log file if RESETLOGS" Cause: File sizes must be given for all logfiles if doing a CREATE CONTROLFILE with the RESETLOGS option. Action: Resubmit the command with the appropriate logfile size. ORA-01199, 00000, "file %s is not in online backup mode" Cause: Attempting to end an online backup for a file that is not in online backup. Action: Do not enter command since it is not needed. ORA-01200, 00000, "actual file size of %s is smaller than correct size of %s blocks" Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the controlfile. Somehow the file has been truncated. Maybe it is the result of a half completed copy. Action: Restore a good copy of the data file and do recovery as needed. ORA-01201, 00000, "file %s header failed to write correctly" Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made. Action: The file probably will require recovery. Further error messages will indicate what is needed. ORA-01202, 00000, "wrong incarnation of this file - wrong creation time" Cause: The creation time in the file header is not the same as the creation time in the controlfile. This is probably a copy of a file that was dropped. Action: Restore a current copy of the data file and do recovery as needed. ORA-01203, 00000, "wrong incarnation of this file - wrong creation SCN" Cause: The creation SCN in the file header is not the same as the creation SCN in the controlfile. This is probably a copy of a file that was dropped. Action: Restore a current copy of the data file and do recovery as needed. ORA-01204, 00000, "file number is %s rather than %s - wrong file" Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01205, 00000, "not a data file - type number in header is %s" Cause: The file type in the header is not correct for a data file. This is probably a log file or controlfile. If the type is not a small non-zero positive number then the header is corrupted. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01206, 00000, "file is not part of this database - wrong database id" Cause: The database ID in the file header does not match the database id in the controlfile. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01207, 00000, "file is more recent than controlfile - old controlfile" Cause: The controlfile change sequence number in the data file is greater than the number in the controlfile. This implies that the wrong controlfile is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the controlfile change sequence number until it is great enough. Action: Use the current controlfile or do backup controlfile recovery to make the controlfile current. Be sure to follow all restrictions on doing a backup controlfile recovery. ORA-01208, 00000, "data file is an old version - not accessing current version" Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01209, 00000, "data file is from before the last RESETLOGS" Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01210, 00000, "data file header is media corrupt" Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database. Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery. ORA-01211, 00000, "Oracle7 data file is not from migration to Oracle8" Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8. Action: Have operating system make correct data file available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run. ORA-01212, 00000, "MAXLOGMEMBERS may not exceed %s" Cause: MAXLOGMEMBERS specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGMEMBERS ORA-01213, 00000, "MAXINSTANCES may not exceed %s" Cause: MAXINSTANCES specified on the command line too large. Action: Resubmit the command with a smaller MAXINSTANCES ORA-01214, 00000, "MAXLOGHISTORY may not exceed %s" Cause: MAXLOGHISTORY specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGHISTORY ORA-01215, 00000, "enabled thread %s is missing after CREATE CONTROLFILE" Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database. Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads. ORA-01216, 00000, "thread %s is expected to be disabled after CREATE CONTROLFILE" Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread). Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be recreated after the database is open. ORA-01217, 00000, "logfile member belongs to a different logfile group" Cause: A member of a multiple-member logfile group specified in a CREATE CONTROLFILE is not part of the same group as previous members. Action: Group together the correct members for the CREATE CONTROLFILE command. ORA-01218, 00000, "logfile member is not from the same point-in-time" Cause: A member of a multiple-member logfile group is from a different point in time. One of the members specified may be an older (backup) copy of the log. Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command. ORA-01219, 00000, "database not open: queries allowed on fixed tables/views only" Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened. Action: Re-phrase the query to include only fixed objects, or open the database. ORA-01220, 00000, "file based sort illegal before database is open" Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open. Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory. ORA-01221, 00000, "data file %s is not the same file to a background process" Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all. Action: Look in the DBWR trace file for the error it recieved when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process. ORA-01222, 00000, "MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s" Cause: Attemping to create a database or controlfile that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs. Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES. ORA-01223, 00000, "RESETLOGS must be specified to set a new database name" Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS. Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE. ORA-01224, 00000, "group number in header %s does not match GROUP %s" Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong. Action: Omit the GROUP option or give the correct one. ORA-01225, 00000, "thread number %s is greater than MAXINSTANCES %s" Cause: The log is for a thread greater than the MAXINSTANCES argument. Action:Increase the value for MAXINSTANCES and resubmit the command. ORA-01226, 00000, "file header of log member is inconsistent with other members" Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log. *Action: Find the correct log member or omit this member from the command. ORA-01227, 00000, "log %s is inconsistent with other logs" Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistancy. All log files listed in the command must be the current versions of the online logs. *Action: Find the correct online logs or use the RESETLOGS option. ORA-01228, 00000, "SET DATABASE option required to install seed database" Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the controlfile for this database. *Action: Resubmit command with the SET DATABASE and RESETLOGS options. ORA-01229, 00000, "data file %s is inconsistent with logs" Cause: The data file in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs. *Action: Find the correct online logs or use the RESETLOGS option. ORA-01230, 00000, "cannot make read only - file %s is offline" Cause: An attempt to make a tablespace read only found that one of its files is offline. Action: Bring the file online and retry this command. ORA-01231, 00000, "cannot make read write - file %s is offline" Cause: An attempt to make a tablespace read write found that one of its files is offline. Action: Bring the file online and retry this command. ORA-01232, 00000, "cannot start online backup - file %s is read only" Cause: An attempt to start an online backup found that one of the files is marked read only. Read only files do not need to be set into online backup mode. Action: Make the backup without the begin backup command. ORA-01233, 00000, "file %s is read only - cannot recover using backup controlfile" Cause: An attempt to do media recovery using a backup controlfile found that one of the files is marked read only. Read only files do not normally need to be recovered, but recovery with a backup controlfile must recover all online files. Action: If the file really is read only, take it offline before the recovery, and bring the read only tablespace online after the database is open. If the file does need recovery use a controlfile from the time the file was read-write. If the correct controlfile is not available, use CREATE CONTROLFILE to make one. ORA-01234, 00000, "cannot end backup of file %s - file is in use or recovery" Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online. Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation. ORA-01235, 00000, "END BACKUP failed for %s file(s) and succeeded for %s" Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded. Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful. ORA-01236, 00000, "Error %s occurred during initialization of file header access" Cause: The indicated error occurred while doing initialization processing of file headers. Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm. ORA-01237, 00000, "cannot extend datafile %s" Cause: An operating system error occurred during the resize. Action: Fix the cause of the operating system error and retry the command. ORA-01238, 00000, "cannot shrink datafile %s" Cause: An operating system error occurred during the resize. Action: The error is ignored, operation continues normally. ORA-01239, 00000, "database must be in ARCHIVELOG mode to use external cache" Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this can not be allowed. Action: Change database to be in ARCHIVELOG mode or do not use an external cache. ORA-01240, 00000, "too many data files to add in one command" Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large. Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands. ORA-01241, 00000, "an external cache has died" Cause: The external cache may have been restarted. Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all data files through consistent external caches. ORA-01242, 00000, "data file suffered media failure: database in NOARCHIVELOG mode" Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01243, 00000, "system tablespace file suffered media failure" Cause: A system tablespace file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01244, 00000, "unnamed datafile(s) added to controlfile by media recovery" Cause: Media recovery with a backup controlfile or a controlfile that was rebuilt, encountered the creation of a datafile that was not in the controlfile. An entry has been added to the controlfile for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files. Action: Rename the files to valid file names and resume recovery. If necessary the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option. ORA-01245, 00000, "offline file %s will be lost if RESETLOGS is done" Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option. Action: Either bring the file online and recover it, or take it offline with the FOR DROP option. ORA-01246, 00000, "recovering files through TSPITR of tablespace %s" Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery. Action: Restore more recent backups and recover them. ORA-01247, 00000, "database recovery through TSPITR of tablespace %s" Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done. Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery. ORA-01248, 00000, "file %s was created in the future of incomplete recovery" Cause: Attempting to do a RESETLOGS open with a file entry in the controlfile that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed. Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different controlfile is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a controlfile can be created via CREATE CONTROLFILE. ORA-01249, 00000, "archiving not allowed in a clone database" Cause: Attempting to archive an online redo log or enable archiving for a clone database. Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed then recreate database as not a clone. ORA-01250, 00000, "Error %s occurred during termination of file header access" Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error. Action: The indicated error should be corrected. ORA-01251, 00000, "Unknown File Header Version read for file number %s" Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file. Action: Have the operating system make the correct file available to the database, or recover the file. ORA-01252, 00000, "cannot prevent writes - file %s in recovery manager backup" Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read-only, then the file header cannot be updated when the backup is complete. Action: Wait for the Recovery Manager backup to complete and retry this command. ORA-01253, 00000, "cannot start online backup - file %s in recovery manager backup" Cause: The specified file is being backed up by Recovery Manager. Action: Wait for the Recovery Manager proxy backup to complete before starting another backup. ORA-01254, 00000, "cannot end online backup - file %s in recovery manager backup" Cause: The specified file is being backed up by Recovery Manager. Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually. ORA-01255, 00000, "cannot shutdown - file %s in recovery manager backup" Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress. Action: Wait for the Recovery Manager proxy backup to complete and retry this command. ORA-01256, 00000, "error in locking database file %s" Cause: The file is in use by another database instance. Action: Determine which database instance legitimately owns the file. ORA-01257, 00000, "cannot reuse database file %s, unknown file size" Cause: The size of the raw partion cannot be determined Action: Add the datafile/logfile by specifying the size parameter. ORA-01258, 00000, "unable to delete temporary file %s" Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database. Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file. ORA-01259, 00000, "unable to delete datafile %s" Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace. Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file. ORA-01260, 00000, "may not issue ALTER DATABASE END BACKUP when database is open" Cause: ALTER DATABASE END BACKUP was issued while the database was open. Action: Either use ALTER DATABASE DATAFILE END BACKUP to end backup for specific files, or ALTER TABLESPACE END BACKUP if backup is complete for all files in a tablespace. ORA-01261, 00000, "Parameter %s destination string cannot be translated" Cause: The value for the specified parameter contained a destination string that could not be translated. Action: Use a valid destination string in the specified parameter. ORA-01262, 00000, "Stat failed on a file destination directory" Cause: Unable to get information about an Oracle managed files destination directory. Action: Check the permissions on the directory or use a different directory name. ORA-01263, 00000, "Name given for file destination directory is invalid" Cause: The name given for an Oracle managed files destination does not correspond to a directory. Action: Use a different name. ORA-01264, 00000, "Unable to create %s file name" Cause: Unable to create an Oracle managed file name for a datafile, logfile or control file. Action: Check previous error messages for the reason Oracle was unable to create the file name. Take corrective action, if possible, and retry the command. ORA-01265, 00000, "Unable to delete file %s" Cause: An error prevented the file from being deleted. Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file. ORA-01266, 00000, "Unable to create unique file name" Cause: Unable to create a unique file name for an Oracle managed datafile, logfile, or control file. Oracle tried several names but each file name was already in use in the default destination directory for the file type. Action: Retry the operation. If that fails, also, it may be necessary to change the default destination directory for the file type and then retry. ORA-01267, 00000, "Failure getting date/time" Cause: Could not get date/time when trying to create unique file name. Action: Internal error - contact Oracle Customer Support. ORA-01268, 00000, "invalid TEMPFILE clause for alter of permanent TABLESPACE" Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace. Action: Retry with a DATAFILE clause. ORA-01269, 00000, "Destination parameter string is too long" Cause: The value for DB_CREATE_FILE_DEST or DB_CREATE_ONLINE_LOG_DEST_n parameter is too long. Action: Replace the destination value for the specified parameter with a shorter character string. ORA-01270, 00000, "%s operation is not allowed if STANDBY_PRESERVES_NAMES is true" Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true. Action: Set STANDBY_PRESERVES_NAMES false if the operation must be performed. ORA-01271, 00000, "Unable to create new file name for file %s" Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file. Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery. ORA-01272, 00000, "REUSE only allowed when a file name is provided." Cause: The REUSE parameter was specified in a command without a file name. Action: Either supply a file name or remove the REUSE parameter. ORA-01273, 00000, "STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = %s or higher" Cause: The COMPATIBLE initialization parameter was not set to the correct value for setting STANDBY_FILE_MANAGEMENT to AUTO. Action: Restart the instance with COMPATIBLE set to the correct release. ORA-01274, 0000, "cannot add datafile '%s' - file could not be created" Cause: Automated standby file management was enabled but an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The controlfile file entry for the file will be 'UNNAMEDnnnnn'. Action: Temporarily set STANDBY_FILE_MANAGEMENT to MANUAL and use the ALTER DATABASE CREATE DATAFILE statement to create the file. Then set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery. ORA-01275, 00000, "Operation %s is not allowed if standby file management is automatic." Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO. Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed. ORA-01276, 00000, "Cannot add a file with an Oracle Managed Files file name." Cause: An attempt was made to add to the database a datafile, log file, or control file with an Oracle Managed Files file name. Action: Retry the operation with a new file name. / / 1280-1399 LogMiner errors / ORA-01280, 00000, "Fatal LogMiner Error." Cause: An internal error has occurred inside LogMiner. Action: ORA-01281, 00000, "SCN range specified is invalid" Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid. Action: Specify a valid SCN range. ORA-01282, 00000, "date range specified is invalid" Cause: StartDate may be greater than EndDate. Alternatively, there may be no logfile that is compatible with the date range specified with StartDate and EndDate. Action: Specify a valid date range. ORA-01283, 00000, "Options specified is invalid" Cause: The specified options parameter is invalid for the procedure. Action: Specify valid Options parameter. ORA-01284, 00000, "file %s cannot be opened" Cause: The file or directory may not exist or may be inaccessible. Action: Ensure that the file and the directory exist and are accessible. ORA-01285, 00000, "error reading file %s" Cause: The file or directory may not exist or is inaccessible. Action: Specify valid file or directory. Make sure that file and directory are accessible. ORA-01286, 00000, "cannot add file %s due to DB_ID mismatch" Cause: The logfile is produced by a different database than other logfiles already added to the list. Action: Specify a logfile produced by the same database. ORA-01287, 00000, "file %s is from a different database incarnation" Cause: The logfile is produced by a different incarnation of the database. Action: Add a logfile that is produced by the same incarnation. ORA-01289, 00000, "cannot add duplicate logfile %s" Cause: The logfile specified has already been added to the list of logfiles. Action: Specify a different logfile. ORA-01290, 00000, "cannot remove unlisted logfile %s" Cause: The user attempted to remove a logfile that is not present in the list. Action: Specify a valid logfile. ORA-01291, 00000, "missing logfile" Cause: Not all logfiles corresponding to the data or scn range specified have been added to the list. Action: Check the v$logmnr_logs view to determine the missing scn range, and add the relevant logfiles. ORA-01292, 00000, "no log file has been specified for the current LogMiner session" Cause: No logfile has been specified for the LogMiner session. Action: Specify atleast one log file. ORA-01293, 00000, "time or SCN range not fully contained in the listed logfiles" Cause: The input date/SCN range is not fully contained within the logfiles specified for the session. Action: select out of v$logmnr_logs view to check the date or SCN range covered by the logfiles specified for the LogMiner session, and reissue the procedure with appropriate date or SCN range. ORA-01294, 00000, "error occurred while processing information in dictionary file %s, possible corruption" Cause: The dictionary file is corrupt. Action: Get a new dictionary file. ORA-01295, 00000, "DB_ID mismatch between dictionary %s and logfiles" Cause: The dictionary file is produced by a database that is different from that produced the logfiles. Action: Specify a compatible dictionary file. ORA-01296, 00000, "character set mismatch between dictionary %s and logfiles" Cause: The character set of the database that produced the dictionary file is different from the charatcter set of the database that produced the logfiles. Action: Specify a dictionary file with the same character set. ORA-01297, 00000, "redo version mismatch between dictionary %s and logfiles" Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles. Action: ORA-01298, 00000, "dictionary %s and the earliest logfile are not SCN-compatible" Cause: The dictionary snapshot was taken at a SCN that does not correspond to the creation SCN of the earliest logfile. Action: Get a correct dictionary snapshot. ORA-01299, 00000, "dictionary %s corresponds to a different database incarnation" Cause: The dictionary file was extracted from a different incarnation of the database. Action: Specify a dictionary file extracted from the correct database incarnation. ORA-01300, 00000, "enabled thread bit vector mismatch between dictionary %s and the earliest logfile" Cause: Action: ORA-01301, 00000, "dbms_logmnr.USE_COLMAP can only be used with a valid dictionary" Cause: dbms_logmnr.USE_COLMAP can only be used with a valid dictionary. Action: Specify the dictionary file in dbms_logmnr.start_logmnr(). ORA-01302, 00000, "syntax error in logmnr.opt file" Cause: A syntax error was detected in the logmnr.opt file. Action: Use correct syntax. ORA-01303, 00000, "schema %s, specified in logmnr.opt file, does not exist" Cause: The schema specified does not exist. Action: Specify a correct schema or a compatible dictionary file. ORA-01304, 00000, "table %s, schema %s, specified in logmnr.opt file, does not exist" Cause: The table specified in the logmnr.opt file does not exist in the dictionary provided to LogMiner. Action: Make sure that the table specified is valid. ORA-01305, 00000, "column %s, specified in logmnr.opt file, does not exist in table %s, schema %s" Cause: The column specified in logmnr.opt file does not exist for the table definition in the dictionary provided for LogMiner. Action: Make sure that the column specified is valid. ORA-01306, 00000, "dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents" Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view. ORA-01307, 00000, "no LogMiner session is currently active" Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile() Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view. ORA-01308, 00000, "initialization parameter utl_file_dir is not set" Cause: utl_file_dir is not set in the initialization file. Action: Set utl_file_dir to the appropriate directory. ORA-01309, 00000, "invalid session" Cause: The specified Logminer session ID or session handle is invalid. Action: Use a valid Logminer session ID or session handle. ORA-01310, 00000, "requested return type not supported by the lcr_mine function" Cause: The return type requested by the user is not supported by lcr_mine" Action: Pick a return type supported by the lcr_mine function" ORA-01311, 00000, "Illegal invocation of the mine_value function" Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table/view. Action: Rewrite the SQL statement with a legal invocation of mine_value ORA-01312, 00000, "Specified table/column does not exist" Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly. Action: Create a LogMiner session at a start SCN at which the table definition is available. ORA-01313, 00000, "LogMiner dictionary column type different from specified type" Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column. Action: Rewrite the lcr_mine invocation with the right return type. ORA-01314, 00000, "Name of the column to be mined should be a string literal" Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal. Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in 'a.b.c.d'. ORA-01315, 00000, "Log file has been added or removed during select" Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view. Action: Re-issue the SQL select statement on the v$logmnr_logs view. ORA-01316, 00000, "Already attached to a Logminer session" Cause: A Logminer attach session was issued while already attached to a Logminer session. Action: Detach from the current Logminer session and attach to the requested session. ORA-01317, 00000, "Not attached to a Logminer session" Cause: A command or procedure was issued which requires an attached Logminer session. Action: Attach to a Logminer session before issuing the command or procedure. ORA-01318, 00000, "Logminer session not started" Cause: Logminer activate session was called before prepare session. Action: ORA-01319, 00000, "Invalid Logminer session attribute" Cause: A session attribute was supplied which is invalid. Action: Re-issue with valid session attribute. ORA-01320, 00000, "Invalid Logminer dictionar attribute" Cause: A Logminer dictionary attribute was supplied which is invalid. Action: Re-issue with valid dictionary attribute. ORA-01321, 00000, "SCN range not fully contained in the listed logfiles" Cause: The input date/SCN range is not fully contained within the logfiles specified for the session. Action: select out of v$logmnr_logs view to check the date or SCN range covered by the logfiles specified for the LogMiner session, and reissue the procedure with appropriate date or SCN range. ORA-01322, 00000, "No such table" Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table(). Action: Re-issue with valid table name. ORA-01323, 00000, "Invalid state" Cause: A Logminer routine was called from the wrong state. Action: ORA-01324, 00000, "cannot add file due to DB_ID mismatch" Cause: The logfile is produced by a different database than other logfiles already added to the list. Action: Specify a logfile produced by the same database. ORA-01325, 00000, "archive log mode must be enabled to build into the logstream" Cause: Database does not have archivelog mode enabled. Action: Ensure that init.ora parameters enabling archivelog mode are set. For example: log_archive_start=true log_archive_dest="/vobs/oracle/dbs" log_archive_format="arch%s.log" Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open ORA-01326, 00000, "compatability of 8.2 or greater required to build into the logstream" Cause: Compatibility mode set to some value less than 8.2 Action: Ensure that init.ora parameter establishing a compatability of 8.2 or greater is set. For example: compatible=8.2.0.0.0 ORA-01327, 00000, "failed to exclusively lock system dictionary as required by build" Cause: Other users are performing DDL operations. Action: ORA-01328, 00000, "only one build operation may occur at one time" Cause: Another processes is simultaneously attempting to run build(); Action: Wait until the other processes completes. ORA-01329, 00000, "unable to truncate require build table" Cause: The table may be missing, or locked by another user. Action: This error should not occur. If it does occur and there is reason to believe that required tables are missing then as a last resort the package dbmslmd.sql may be reinstalled. Doing so will delete all existing Logminer Dictionary data. ORA-01330, 00000, "problem loading a required build table" Cause: Action: ORA-01331, 00000, "general error while running build" Cause: Action: ORA-01332, 00000, "internal Logminer Dictionary error" Cause: Unexpected error condition Action: Check trace file ORA-01333, 00000, "failed to establish Logminer Dictionary" Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary. Action: If build() was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added. The following query, run on the system which build() was run, can be helpful in identifying the requried files. select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally a set of files beginning with one which has DICTIONARY_BEGIN = 'YES' and all following log files through one marked DICTIONARY_END = 'YES' must be added. ORA-01334, 00000, "invalid or missing logminer dictionary processes context" Cause: Unexpected internal error condition Action: ORA-01335, 00000, "feature not yet implemented" Cause: Action: ORA-01336, 00000, "specified dictionary file cannot be opened" Cause: The dictionary file or directory does not exist or is inaccessible. Action: Make sure that the dictionary file and directory exist and are accessible. ORA-01337, 00000, "log file has a different compatibility version" Cause: The logfile has a different compatibility version then the rest of the logfile in the session" Action: Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session. ORA-01341, 00000, "LogMiner out-of-memory" Cause: The logfiles to be analyzed in the current LogMiner session require more system resources than what is currently available. Action: Reduce the number of logfiles to be analyzed for a given LogMiner session and try again. ORA-01348, 00000, "LogMiner testing event" Cause: Action: ORA-01349, 00000, "LogMiner tracing event" Cause: Action: / / 1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE / 1349-1399 have been reserved for LogMiner / / 1400-1499 SQL execute phase errors / ORA-01400, 00000, "cannot insert NULL into (%s)" Cause: Action: ORA-01401, 00000, "inserted value too large for column" Cause: Action: ORA-01402, 00000, "view WITH CHECK OPTION where-clause violation" Cause: Action: ORA-01403, 00000, "no data found" Cause: Action: ORA-01404, 00000, "ALTER COLUMN will make an index too large" Cause: Action: ORA-01405, 00000, "fetched column value is NULL" Cause: Action: ORA-01406, 00000, "fetched column value was truncated" Cause: Action: ORA-01407, 00000, "cannot update (%s) to NULL" Cause: Action: ORA-01408, 00000, "such column list already indexed" Cause: Action: ORA-01409, 00000, "NOSORT option may not be used; rows are not in ascending order" Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail. Action: Create the index without the NOSORT option, or ensure table is stored in one extent. ORA-01410, 00000, "invalid ROWID" Cause: Action: ORA-01411, 00000, "cannot store the length of column in the indicator" Cause: Tried to fetch a column of size more than 64K and couldn't store the length of the column in the given indicator of size 2 bytes. Action: Use the new bind type with call backs to fetch the long column. ORA-01412, 00000, "zero length not allowed for this datatype" Cause: The length for type 97 is 0 Action: Specify the correct length. ORA-01413, 00000, "illegal value in packed decimal number buffer" Cause: The user buffer bound by the user as packed decimal number contained an illegal value. Action: Use a legal value. ORA-01414, 00000, "invalid array length when trying to bind array" Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length. Action: Sepcify a valid length. ORA-01415, 00000, "too many distinct aggregate functions" Cause: The query contains more distinct aggregates than can be processed. The current limit is 255. Action: Reduce the number of distinct aggregate functions in the query. ORA-01416, 00000, "two tables cannot be outer-joined to each other" Cause: Action: ORA-01417, 00000, "a table may be outer joined to at most one other table" Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed Action: Check that this is really what you want, then join b and c first in a view. ORA-01418, 00000, "specified index does not exist" Cause: Action: ORA-01419, 00000, "datdts: illegal format code" Cause: Action: ORA-01420, 00000, "datstd: illegal format code" Cause: Action: ORA-01421, 00000, "datrnd/dattrn: illegal precision specifier" Cause: Action: ORA-01422, 00000, "exact fetch returns more than requested number of rows" Cause: The number specified in exact fetch is less than the rows returned. Action: Rewrite the query or change number of rows requested ORA-01423, 00000, "error encountered while checking for extra rows in exact fetch" Cause: Action: See the following error and take appropriate action. ORA-01424, 00000, "missing or illegal character following the escape character" Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'. Action: Remove the escape character or specify the missing character. ORA-01425, 00000, "escape character must be character string of length 1" Cause: Given escape character for LIKE is not a character string of length 1. Action: Change it to a character string of length 1. ORA-01426, 00000, "numeric overflow" Cause: Evaluation of an value expression causes an overflow/underflow. Action: Reduce the operands. ORA-01427, 00000, "single-row subquery returns more than one row" Cause: Action: ORA-01428, 00000, "argument '%s' is out of range" Cause: Action: ORA-01429, 00000, "Index-Organized Table: no data segment to store overflow row-pieces" Cause: No overflow segment defined. Action: Add overflow segment. ORA-01430, 00000, "column being added already exists in table" Cause: Action: ORA-01431, 00000, "internal inconsistency in GRANT command" Cause: Action: ORA-01432, 00000, "public synonym to be dropped does not exist" Cause: Action: ORA-01433, 00000, "synonym to be created is already defined" Cause: Action: ORA-01434, 00000, "private synonym to be dropped does not exist" Cause: Action: ORA-01435, 00000, "user does not exist" Cause: Action: ORA-01436, 00000, "CONNECT BY loop in user data" Cause: Action: ORA-01437, 00000, "cannot have join with CONNECT BY" Cause: Action: ORA-01438, 00000, "value larger than specified precision allows for this column" Cause: Action: ORA-01439, 00000, "column to be modified must be empty to change datatype" Cause: Action: ORA-01440, 00000, "column to be modified must be empty to decrease precision or scale" Cause: Action: ORA-01441, 00000, "cannot decrease column length because some value is too big" Cause: Action: ORA-01442, 00000, "column to be modified to NOT NULL is already NOT NULL" Cause: Action: ORA-01443, 00000, "internal inconsistency; illegal datatype in resultant view column" Cause: Action: ORA-01444, 00000, "internal inconsistency; internal datatype maps to invalid external type" Cause: Action: ORA-01445, 00000, "cannot select ROWID from a join view without a key-preserved table" Cause: Action: ORA-01446, 00000, "cannot select ROWID from view with DISTINCT, GROUP BY, etc." Cause: Action: ORA-01447, 00000, "ALTER TABLE does not operate on clustered columns" Cause: Action: ORA-01448, 00000, "index must be dropped before changing to desired type" Cause: Action: ORA-01449, 00000, "column contains NULL values; cannot alter to NOT NULL" Cause: Action: ORA-01450, 00000, "maximum key length (%s) exceeded" Cause: Action: ORA-01451, 00000, "column to be modified to NULL cannot be modified to NULL" Cause: the column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint. Action: if a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint. ORA-01452, 00000, "cannot CREATE UNIQUE INDEX; duplicate keys found" Cause: Action: ORA-01453, 00000, "SET TRANSACTION must be first statement of transaction" Cause: self-evident Action: commit (or rollback) transaction, and re-execute ORA-01454, 00000, "cannot convert column into numeric datatype" Cause: Action: ORA-01455, 00000, "converting column overflows integer datatype" Cause: Action: ORA-01456, 00000, "may not perform insert/delete/update operation inside a READ ONLY transaction" Cause: A non-DDL insert/delete/update or select for update operation was attempted Action: commit (or rollback) transaction, and re-execute ORA-01457, 00000, "converting column overflows decimal datatype" Cause: Action: ORA-01458, 00000, "invalid length inside variable character string" Cause: Action: ORA-01459, 00000, "invalid length for variable character string" Cause: Action: ORA-01460, 00000, "unimplemented or unreasonable conversion requested" Cause: Action: ORA-01461, 00000, "can bind a LONG value only for insert into a LONG column" Cause: Action: ORA-01462, 00000, "cannot insert string literals longer than 4000 characters" Cause: Action: ORA-01463, 00000, "cannot modify column datatype with current constraint(s)" Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa. Action: Remove the constraint(s) or do not perform the offending operation. ORA-01464, 00000, "circular grant (granting to grant ancestor) of table or view" Cause: Action: ORA-01465, 00000, "invalid hex number" Cause: Action: ORA-01466, 00000, "unable to read data - table definition has changed" Cause: Query parsed after tbl (or index) change, and executed w/old snapshot Action: commit (or rollback) transaction, and re-execute ORA-01467, 00000, "sort key too long" Cause: Action: ORA-01468, 00000, "a predicate may reference only one outer-joined table" Cause: Action: ORA-01469, 00000, "PRIOR can only be followed by a column name" Cause: Attempting to specify "PRIOR" where is not a column name. Action: Only a column name can follow PRIOR. Replace with a column name. ORA-01470, 00000, "In-list iteration does not support mixed operators" Cause: Constants of different types are specified in an in-list. Action: Use constants of same type for in-lists. ORA-01471, 00000, "cannot create a synonym with same name as object" Cause: Action: ORA-01472, 00000, "cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc." Cause: Action: ORA-01473, 00000, "cannot have subqueries in CONNECT BY clause" Cause: Action: ORA-01474, 00000, "cannot have START WITH or PRIOR without CONNECT BY" Cause: Action: ORA-01475, 00000, "must reparse cursor to change bind variable datatype" Cause: Action: ORA-01476, 00000, "divisor is equal to zero" Cause: Action: ORA-01477, 00000, "user data area descriptor is too large" Cause: Action: ORA-01478, 00000, "array bind may not include any LONG columns" Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes. Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead. ORA-01479, 00000, "last character in the buffer is not Null" Cause: A bind variable of type 97 does not contain null at the last position Action: Make the last character null ORA-01480, 00000, "trailing null missing from STR bind value" Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer. Action: Terminate the string with a null character ORA-01481, 00000, "invalid number format model" Cause: The user is attempting to either convert a number to a string via TO_CHAR or a string to a number via TO_NUMBER and has supplied an invalid number format model parameter. Action: Consult your manual. ORA-01482, 00000, "unsupported character set" Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set. Action: Use one of the supported character sets. ORA-01483, 00000, "invalid length for DATE or NUMBER bind variable" Cause: A bind variable of type DATE or NUMBER is too long. Action: Consult your manual for the maximum allowable length. ORA-01484, 00000, "arrays can only be bound to PL/SQL statements" Cause: You tried to bind an array to a non-PL/SQL statement. Action: ORA-01485, 00000, "compile bind length different from execute bind length" Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length (given in the bind call). The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array. Action: ORA-01486, 00000, "size of array element is too large" Cause: You tried to bind a data value which was either too large for the datatype (for example, NUMBER) or was greater than 4000 bytes (for example, VARCHAR or LONG). Action: ORA-01487, 00000, "packed decimal number too large for supplied buffer" Cause: An impossible request for decimal to oracle number conversion was made Action: This conversion cannot be performed ORA-01488, 00000, "invalid nibble or byte in the input data" Cause: An impossible request for decimal to oracle number conversion was made Action: This conversion cannot be performed ORA-01489, 00000, "result of string concatenation is too long" Cause: String concatenation result is more than the maximum size. Action: Make sure that the result is less than the maximum size. / / 1490 - 1499 Analyze Parse and Execution Errors / ORA-01490, 00000, "invalid ANALYZE command" Cause: Incorrect syntax specified Action: Retry the command ORA-01491, 00000, "CASCADE option not valid" Cause: The CASCADE option is only valid for tables or clusters. Action: Do not specify CASCADE ORA-01492, 00000, "LIST option not valid" Cause: The LIST option is only valid for tables or clusters. Action: Do not specify LIST ORA-01493, 00000, "invalid SAMPLE size specified" Cause: The specified SAMPLE size is out of range Action: Specify a value within the proper range. ORA-01494, 00000, "invalid SIZE specified" Cause: The specified histogram SIZE value was out of range. Action: Specify a value within the proper range. ORA-01495, 00000, "specified chain row table not found" Cause: The specified table either does not exist or user does not have the proper privleges. Action: Specify the correct table to use. ORA-01496, 00000, "specified chain row table form incorrect" Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. ORA-01497, 000000, "illegal option for ANALYZE CLUSTER" Cause: The FOR COLUMNS clause may not be used with ANALYZE CLUSTER. Action: Retry with a legal syntax. ORA-01498, 00000, "block check failure - see trace file" Cause: Action: ORA-01499, 00000, "table/index cross reference failure - see trace file" Cause: Action: / / 1500 - 1699 V6 Execution errors / ORA-01500, 00000, "failure in getting date/time" Cause: During create database or alter tablespace, there was a failure in getting the date and time. Action: Contact your customer support representative. ORA-01501, 00000, "CREATE DATABASE failed" Cause: An error occurred during create database Action: See accompanying errors. ORA-01502, 00000, "index '%s.%s' or partition of such index is in unusable state" MERGE: 1489 RENUMBERED TO 1502 Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition ORA-01503, 00000, "CREATE CONTROLFILE failed" Cause: An error occurred during CREATE CONTROLFILE Action: See accompanying errors. ORA-01504, 00000, "database name '%s' does not match parameter db_name '%s'" Cause: The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name. Action: correct or omit one of the two names. ORA-01505, 00000, "error in adding log files" Cause: During create or alter database, error(s) occurred when adding new log files. Action: Check error stack for detailed error information. ORA-01506, 00000, "missing or illegal database name" Cause: No database name was specified in the CREATE/ALTER DATABASE statement, and no db_name INIT.ORA parameter was specified. Action: Either the database name must be given in the statement or in the db_name INIT.ORA parameter. Note that the SQLDBA STARTUP command issues an ALTER DATABASE statement using the database name specified as part of STARTUP (if any). ORA-01507, 00000, "database not mounted" Cause: A command was attempted that requires the database to be mounted. Action: If you are using the ALTER DATABASE statement via the SQLDBA startup command, specify the MOUNT option to startup; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database. ORA-01508, 00000, "cannot create database; error in file '%s' at line %s" Cause: CREATE DATABASE was unable to process the specified file. Action: Check the offending line in the specified file. ORA-01509, 00000, "specified name '%s' does not match actual '%s'" Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database. Action: Correct the database name spelling or DISMOUNT the mounted database. ORA-01510, 00000, "error in deleting log files" Cause: During ALTER DATABASE, an error occurred while dropping log files. Action: Check the error stack for detailed error information. ORA-01511, 00000, "error in renaming log/data files" Cause: During ALTER DATABASE, an error occurred while renaming log or data files. Action: Check the error stack for detailed error information. ORA-01512, 00000, "error renaming log file %s - new file %s not found" Cause: An attempt to change a log file's name in the controlfile failed because no file was found with the new name. Action: Make sure that the log file has been properly renamed by the operating system and retry. ORA-01513, 00000, "invalid current time returned by operating system" Cause: The operating system returned a time that was not between 1988 and 2121. Action: Correct the time kept by the operating system. ORA-01514, 00000, "error in log specification: no such log" Cause: A log file name, or list of member names, did not correspond to an existing log. Action: Specify an existing log file. ORA-01515, 00000, "error dropping log group %s: no such log" Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database controlfile. Action: Specify the name of an existing log file. ORA-01516, 00000, "nonexistent log file, datafile or tempfile '%s'" Cause: An attempt was made to use ALTER DATABASE to either rename a log file or datafile, or change attributes of a datafile or tempfile. The attempt failed because the specified file is not known to the database's control file or is not a type supported for the request. Action: Specify the name of an existing file of the correct type. ORA-01517, 00000, "log member: '%s'" Cause: Used to print member names Action: See top level error for information ORA-01518, 00000, "CREATE DATABASE must specify more than one log file" Cause: Only one log file was specified in the CREATE DATABASE statement. Action: Specify at least two log files. ORA-01519, 00000, "error while processing file '%s' near line %s" Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad. Action: Retry your system installation procedure or contact your customer support representative. ORA-01520, 00000, "number of data files to add (%s) exceeds limit of %s" Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database. Action: Use fewer files or re-create the database with a larger value of MAXDATAFILES. ORA-01521, 00000, "error in adding data files" Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files. Action: Check the error stack for detailed error information. ORA-01522, 00000, "file '%s' to be renamed does not exist" Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database controlfile. Action: Specify the correct file name. ORA-01523, 00000, "cannot rename data file to '%s' - file already part of database" Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the controlfile. Action: Rename the file to a name not already being used as part of the database. ORA-01524, 00000, "cannot create data file as '%s' - file already part of database" Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the controlfile. Action: Create the file as a name not already being used as part of the database. ORA-01525, 00000, "error in renaming data files" Cause: An error occurred when renaming files as part of ALTER TABLESPACE. Action: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack. ORA-01526, 00000, "error in opening file '%s'" Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error. Action: Retry your system installation procedure or contact your customer support representative. ORA-01527, 00000, "error while reading file" Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error. Action: Retry your system installation procedure or contact your customer support representative. ORA-01528, 00000, "EOF while processing SQL statement" Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad. Action: Retry your system installation procedure or contact your customer support representative. ORA-01529, 00000, "error closing file '%s'" Cause: CREATE DATABASE was not able to close the specified file. Action: Retry your system installation procedure or contact your customer support representative. ORA-01530, 00000, "a database already mounted by the instance" Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted. Action: If you wish to mount the database, shutdown the instance and then startup the instance and retry the operation. ORA-01531, 00000, "a database already open by the instance" Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database. Action: If you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation. ORA-01532, 00000, "cannot create database; instance being started elsewhere" Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance. Action: Make sure no one else is simultaneously altering the instance. If no one is, contact your customer support representative; otherwise, retry the operation. ORA-01533, 00000, "cannot rename file '%s'; file does not belong to tablespace" Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace. Action: Specify the correct file name or the correct tablespace name. ORA-01534, 00000, "rollback segment '%s' doesn't exist" Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown. Action: Use the correct rollback segment name. ORA-01535, 00000, "rollback segment '%s' already exists" Cause: Specified rollback segment already exists. Action: Use a different name. ORA-01536, 00000, "space quota exceeded for tablespace '%s'" Cause: The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace. Action: Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner. ORA-01537, 00000, "cannot add data file '%s' - file already part of database" Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database. Action: Use a different file name. ORA-01538, 00000, "failed to acquire any rollback segment" Cause: Failed to acquire any rollback segment during startup in shared mode Action: Startup in exclusive mode to create one more public segment or specify available private segments in the INIT.ORA parameter rollback_segments_required, then startup in shared mode ORA-01539, 00000, "tablespace '%s' is not online" Cause: Failed to either make a tablespace read only or offline because it is not online. A tblespace must be online before it can become read only or offline normal. Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read only. ORA-01540, 00000, "tablespace '%s' is not offline" Cause: Failed to bring a tablespace online because it is not offline Action: Check the status of the tablespace ORA-01541, 00000, "system tablespace cannot be brought offline; shut down if necessary" Cause: Tried to bring system tablespace offline Action: Shutdown if necessary to do recovery ORA-01542, 00000, "tablespace '%s' is offline, cannot allocate space in it" Cause: Tried to allocate space in an offline tablespace Action: Bring the tablespace online or create the object in other tablespace ORA-01543, 00000, "tablespace '%s' already exists" Cause: Tried to create a tablespace which already exists Action: Use a different name for the new tablespace ORA-01544, 00000, "cannot drop system rollback segment" Cause: Tried to drop system rollback segment Action: None ORA-01545, 00000, "rollback segment '%s' specified not available" Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. Action: Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). ORA-01546, 00000, "tablespace contains active rollback segment '%s'" Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read only Action: Shutdown instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only ORA-01547, 00000, "warning: RECOVER succeeded but OPEN RESETLOGS would get error below" Cause: Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery. Action: Rerun the incomplete media recovery using different datafile backups, a different controlfile, or different stop criteria. ORA-01548, 00000, "active rollback segment '%s' found, terminate dropping tablespace" Cause: Tried to drop a tablespace that contains active rollback segment(s) Action: Shutdown instances that use the active rollback segments in the tablespace and then drop the tablespace ORA-01549, 00000, "tablespace not empty, use INCLUDING CONTENTS option" Cause: Tried to drop a non-empty tablespace Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option ORA-01550, 00000, "cannot drop system tablespace" Cause: Tried to drop system tablespace Action: None ORA-01551, 00000, "extended rollback segment, pinned blocks released" Cause: Doing recursive extent of rollback segment, trapped internally by the system Action: None ORA-01552, 00000, "cannot use system rollback segment for non-system tablespace '%s'" Cause: Tried to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database. Action: Create one or more private/public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. ORA-01553, 00000, "MAXEXTENTS must be no smaller than the %s extents currently allocated" Cause: The number of extents allocated is greater than the MAXEXTENTS specified. Action: Specify a larger MAXEXTENTS value. ORA-01554, 00000, "out of transaction slots in transaction tables" Cause: Too many concurrent transactions Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again ORA-01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small" Cause: rollback records needed by a reader for consistent read are overwritten by other writers Action: If in Automatic Undo Management mode, increase undo_retention setting. Otherwise, use larger rollback segments ORA-01556, 00000, "MINEXTENTS for rollback segment must be greater than 1" Cause: Specified MINEXTENTS of less than 2 for rollback segment Action: Specify larger MINEXTENTS ORA-01557, 00000, "rollback segment extents must be at least %s blocks" Cause: Specified extent of less than minimum size for rollback segment Action: Specify larger extents ORA-01558, 00000, "out of transaction ID's in rollback segment %s" Cause: All the available transaction id's have been used Action: Shutdown the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction id's. ORA-01559, 00000, "MAXEXTENTS for rollback segment must be greater than 1" Cause: Specified MAXEXTENTS of less than 2 for rollback segment Action: Specify larger MAXEXTENTS ORA-01561, 00000, "failed to remove all objects in the tablespace specified" Cause: Failed to remove all objects when dropping a tablespace Action: Retry the drop tablespace until all objects are dropped ORA-01562, 00000, "failed to extend rollback segment number %s" Cause: Failure occurred when trying to extend rollback segment Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command to take the rollback segment offline. ORA-01563, 00000, "rollback segment is PUBLIC, need to use the keyword PUBLIC" Cause: Did not use the keyword PUBLIC to identified public rollback segment Action: Use the keyword PUBLIC when identifying public rollback segment ORA-01564, 00000, "rollback segment is not PUBLIC" Cause: The rollback segment segment identified is not public Action: Do not use the keyword PUBLIC when identifying private rollback segment ORA-01565, 00000, "error in identifying file '%s'" Cause: An error occurred while trying to identify a file. Action: Check the error stack for detailed information. ORA-01566, 00000, "file specified more than once in DROP LOGFILE" Cause: The list of files supplied to DROP LOGFILE contains at least one duplicate. Action: Remove the duplicate file specification and retry. ORA-01567, 00000, "dropping log %s would leave less than 2 log files in thread %s" Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread. Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it. ORA-01568, 00000, "cannot set space quota on PUBLIC" MERGE: 1568 PROBABLY OBSOLETE Cause: Trying to set space quota on a tablespace for PUBLIC. Action: If trying to grant system-wide or tablespace-wide space priviledges to all users, use GRANT RESOURCE [ON] TO PUBLIC. ORA-01569, 00000, "data file too small for system dictionary tables" Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables. Action: Recreate the database by specifying a larger file or more files. ORA-01570, 00000, "MINEXTENTS must be no larger than the %s extents currently allocated" Cause: The number of extents allocated is smaller than the MINEXTENTS specified. Action: Specify a smaller MINEXTENTS value. ORA-01571, 00000, "redo version %s incompatible with ORACLE version %s" Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery. Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check. ORA-01572, 00000, "rollback segment '%s' cannot be brought online, %s extents exceeded" Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing. Action: Drop and recreate the rollback segment. ORA-01573, 00000, "shutting down instance, no further change allowed" Cause: Some process tries to make changes while the db is being shutdown Action: None ORA-01574, 00000, "maximum number of concurrent transactions exceeded" Cause: the limit on the number of concurrent transactions has been hit Action: shutdown the system, increase the INIT.ORA parameter 'transactions' , and then restart the system. ORA-01575, 00000, "timeout waiting for space management resource" Cause: failed to acquire necessary resource to do space management. Action: Retry the operation. ORA-01576, 00000, "instance locking protocol version %s incompatible with ORACLE version %s" Cause: Current software uses incompatible locking protocol. Action: Upgrade software used to start up instances so that they use compatible locking protocol. ORA-01577, 00000, "cannot add log file '%s' - file already part of database" Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database. Action: Use a different file name. ORA-01578, 00000, "ORACLE data block corrupted (file # %s, block # %s)" Cause: The data block indicated was corrupted, mostly due to software errors. Action: Try to restore the segment containing the block indicated. This may involve dropping the segment and recreating it. If there is a trace file, report the errors in it to your ORACLE representative. ORA-01579, 00000, "write error occurred during recovery" Cause: A write error occurred during recovery Action: Consult trace files for the nature of the write error, and correct error. ORA-01580, 00000, "error creating control backup file %s" Cause: An operating system error occurred while attempting to create a controlfile backup. Action: Check the error stack for more detailed information ORA-01581, 00000, "attempt to use rollback segment (%s) new extent (%s) which is being allocated" Cause: Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated. Action: The rollback segment extending will be rollbacked by the system, no more extension will be possible untill the next extent is freed up by rolling back or committing other transactions. ORA-01582, 00000, "unable to open controlfile for backup" Cause: An operating system error occurred while attempting to open a controlfile for backup. Action: Check the error stack for more detailed information ORA-01583, 00000, "unable to get block size of controlfile to be backed up" Cause: An operating system error occurred while attempting to get the block size of a controlfile for backup. Action: Check the error stack for more detailed information ORA-01584, 00000, "unable to get file size of controlfile to be backed up" Cause: An operating system error occurred while attempting to get the file size of a controlfile for backup. Action: Check the error stack for more detailed information ORA-01585, 00000, "error identifying backup file %s" Cause: An operating system error occurred when attempting to identify the file to be used for controlfile backup. Action: Check the error stack for more detailed information ORA-01586, 00000, "unable to open destination file %s for backup" Cause: An operating system error occurred while attempting to open a controlfile for backup. Action: Check the error stack for more detailed information ORA-01587, 00000, "error during controlfile backup file copy" Cause: Action: ORA-01588, 00000, "must use RESETLOGS option for database open" Cause: An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a controlfile backup. Action: Use the RESETLOGS option when opening the database. ORA-01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open" Cause: Either incomplete or backup controlfile recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database. Action: Specify the appropriate option. ORA-01590, 00000, "number of segment free list (%s) exceeds maximum of %s" Cause: storage parameter FREELIST GROUPS is too large. Action: Reduce storage parameters FREELIST GROUPS ORA-01591, 00000, "lock held by in-doubt distributed transaction %s" Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state. Action: DBA should query the pending_trans$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, DBA should contact DBA at commit point if known or end user for correct outcome, or use heuristic default if given to issue a heuristic commit or abort command to finalize the local portion of the distributed transaction. ORA-01592, 00000, "error converting Version 7 rollback segment (%s) to Oracle 8 format" Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly. Action: Investigate the internal error; may have to reload the Version 7 Action: Investigate the internal error; may have to reload the Version 7 database (from backup) and shutdown the database cleanly. ORA-01593, 00000, "rollback segment optimal size (%s blks) is smaller than the computed initial size (%s blks)" Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment. Action: Specify a larger OPTIMAL size. ORA-01594, 00000, "attempt to wrap into rollback segment (%s) extent (%s) which is being freed" Cause: Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or too many extents to free Action: The rollback segment shrinking will be rollbacked by the system; increase the optimal size of the rollback segment. ORA-01595, 00000, "error freeing extent (%s) of rollback segment (%s))" Cause: Some error occurred while freeing inactive rollback segment extents. Action: Investigate the accompanying error. ORA-01596, 00000, "cannot specify system in %s parameter" Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message Action: change the INIT.ORA parameter ORA-01597, 00000, "cannot alter system rollback segment online or offline" Cause: Tried to online or offline the system rollback segment Action: None ORA-01598, 00000, "rollback segment '%s' is not online" Cause: Could have been taken offline before by DBA or cleaned up by SMON. Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online. ORA-01599, 00000, "failed to acquire rollback segment (%s), cache space is full" Cause: the amount statically allocated is not enough based on max_rollback_segments parameter. Action: For now take another rollback segment offline or increase the parameter max_rollback_segments ORA-01600, 00000, "at most one \"%s\" in clause \"%s\" of %s" Cause: The INIT.ORA parameter was mis-specified. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01601, 00000, "illegal bucket size in clause \"%s\" of %s" Cause: The bucket size was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01603, 00000, "illegal grouping size in clause \"%s\" of %s" Cause: The grouping size was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01604, 00000, "illegal number range in clause \"%s\" of %s" Cause: The number range was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01605, 00000, "missing numbers in clause \"%s\" of %s" Cause: The numbers were missing for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01606, 00000, "gc_files_to_locks not identical to that of another mounted instance" Cause: The gc_files_to_locks parameters were different on two instances. Action: Modify the INIT.ORA parameter gc_files_to_locks and restart. ORA-01608, 00000, "cannot bring rollback segment '%s' online, its status is (%s)" Cause: Could have been brought online before by DBA or left as a result of process crash. Action: Check the status of rollback segment in undo$ or dba_rollback_segs ORA-01609, 00000, "log %s is the current log for thread %s - cannot drop members" Cause: A member of the current log for a thread cannot be dropped. Action: If the thread is opened, request a log switch by the instance that is using it. If it is not open, disable the thread, manually archive the log, or clear it. ORA-01610, 00000, "recovery using the BACKUP CONTROLFILE option must be done" Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the controlfile was recreated with the RESETLOGS option, or the controlfile being used is a backup controlfile. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open. Action: Perform recovery using the BACKUP CONTROFILE option. ORA-01611, 00000, "thread number %s is invalid - must be between 1 and %s" Cause: A thread number in a command is greater than the number of threads supported by the controlfile. Action: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the controlfile. ORA-01612, 00000, "thread %s is already enabled" Cause: An attempt was made to enable a thread that is already enabled. Action: Either use this thread or enable another thread. ORA-01613, 00000, "thread %s only has %s logs - at least 2 logs required to enable" Cause: The thread cannot be enabled because it only has two online log files associated with it. Action: Add logs to the thread or pick another thread to enable ORA-01614, 00000, "thread %s is busy - cannot enable" Cause: The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread. Action: Wait and try again, or find another thread to enable. ORA-01615, 00000, "thread %s is mounted - cannot disable" Cause: Some instance, possibly this one, has allocated the thread for its use. The thread may not be disabled while in use. Action: Shutdown cleanly the instance using the thread. ORA-01616, 00000, "thread %s is open - cannot disable" Cause: The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery. Action: If the database is open, instance recovery should close the thread soon - wait a few minutes. Otherwise open the database - crash recovery will close the thread. ORA-01617, 00000, "cannot mount: %s is not a valid thread number" Cause: The INIT.ORA parameter "thread" is not between 1 and the number of threads allowed by the controlfile. Action: Shutdown the instance, change the INIT.ORA parameter and startup, or resize the thread record and/or checkpoint progress record sections of the controlfile. ORA-01618, 00000, "thread %s is not enabled - cannot mount" Cause: The INIT.ORA parameter "thread" requests a thread that is not enabled. A thread must be enabled before it can be mounted. Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread. If the database is open in another instance then the thread may be enabled. ORA-01619, 00000, "thread %s is mounted by another instance" Cause: The INIT.ORA parameter "thread" requests a thread that has been mounted by another instance. Only one instance may use a thread. Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread. ORA-01620, 00000, "no public threads are available for mounting" Cause: The INIT.ORA parameter "thread" is zero, its default value. There are no threads which have been publicly enabled, and not mounted. Action: Shutdown the instance, change the INIT.ORA parameter to a thread which is privately enabled and not mounted. If the database is open in another instance, then a thread may be publicly enabled. ORA-01621, 00000, "cannot rename member of current log if database is open" Cause: This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done. Action: Wait until the log is not current, or mount the database exclusively. ORA-01622, 00000, "thread number must be specified - default not specific" Cause: The thread was not specified when adding a log, and the currently mounted thread was chosen by default at mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to. Action: Explicitly specify the thread number either in the INIT.ORA parameter "thread", or in the add command. ORA-01623, 00000, "log %s is current log for thread %s - cannot drop" Cause: A thread's current log cannot be dropped even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again. Action: If the database is not open then disable the thread. If the database is open and an instance has the thread open, then the instance can be requested to switch logs. If the database is closed the log can be archived or cleared to force a switch. ORA-01624, 00000, "log %s needed for crash recovery of thread %s" Cause: A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log. Action: If the database is not open then open it. Crash recovery will advance the checkpoint. If the database is open force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do incomplete recovery until cancel at this log. ORA-01625, 00000, "rollback segment '%s' does not belong to this instance" Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance. Action: ORA-01626, 00000, "rollback segment number '%s' cannot handle more transactions" Cause: Too many transactions in this segment. Action: Choose a different rollback segment, or reduce the number of concurrent transactions. ORA-01627, 00000, "rollback segment number '%s' is not online" Cause: Could have been taken offline before by DBA or cleaned up by SMON. Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online. ORA-01628, 00000, "max # extents (%s) reached for rollback segment %s" Cause: An attempt was made to extend a rollback segment that was already at the MAXEXTENTS value. Action: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value. ORA-01629, 00000, "max # extents (%s) reached saving undo for tablespace %s" Cause: Save undo for the offline tablespace at max extents Action: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied . ORA-01630, 00000, "max # extents (%s) reached in temp segment in tablespace %s" Cause: A temp segment tried to extend past max extents. Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace ORA-01631, 00000, "max # extents (%s) reached in table %s.%s" Cause: A table tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01632, 00000, "max # extents (%s) reached in index %s.%s" Cause: An index tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01633, 00000, "Real Application Clusters Option needed for this operation" Cause: System doesn't have Real Application Clusters configured Action: Obtain Real Application Clusters option ORA-01634, 00000, "rollback segment number '%s' is about to go offline" Cause: The rollback segment specified was marked to go offline by DBA. Action: Bring the rollback segment online first. ORA-01635, 00000, "rollback segment #%s specified not available" Cause: (same as 1545) Action: (same as 1545) ORA-01636, 00000, "rollback segment '%s' is already online" Cause: The instance is trying to online an already online RS Action: ORA-01637, 00000, "rollback segment '%s' is being used by another instance (#%s)" Cause: The instance is trying to online a RS already in use by another instance Action: ORA-01638, 00000, "parameter %s does not allow ORACLE version %s to mount cluster database" Cause: The recovery compatible parameter is set too low to allow this software version to mount in cluster database mode. Action:Either use an earlier software release or advance the recovery_compatible parameter. If this happens when no recovery_compatible parameter has been specified then set it to the current software release. ORA-01640, 00000, "cannot make tablespace read only with active transactions" Cause: Attempting to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions. Action: Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved. ORA-01641, 00000, "tablespace '%s' is not online - cannot add data file" Cause: Attempting to add a datafile to a tablespace that has been set to read only or offline. Action: Make the tablespace online and read write then add the datafile. ORA-01642, 00000, "begin backup not needed for read only tablespace '%s'" Cause: Attempting to begin or end a backup for a tablespace that has been set to read only. Action: Take the backup without any begin or end commands. The files are not being modified so the backup will be consistent. ORA-01643, 00000, "system tablespace can not be made read only" Cause: Attempting to set the system tablespace to read only. The system tablespace must remain read write for database operation. Action: Leave system tablespace read write. ORA-01644, 00000, "tablespace '%s' is already read only" Cause: Attempting to make tablespace read only that is already read only. Action: Leave tablespace read only, or make read write then make read only again. ORA-01645, 00000, "previous attempt to make read write is half complete" Cause: A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be useable after a resetlogs if its files are offline. Action: Repeat the command to make the tablespace read write. ORA-01646, 00000, "tablespace '%s' is not read only - cannot make read write" Cause: Attempting to make a tablespace read write that is not read only. It may be either online or offline. Action: Leave tablespace read write. ORA-01647, 00000, "tablespace '%s' is read only, cannot allocate space in it" Cause: Tried to allocate space in a read only tablespace Action: Create the object in another tablespace ORA-01648, 00000, "log %s is the current log of disabled thread %s" *Casue: An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log can not be cleared or archived. Action:Complete the thread enable by issuing the enable command again. ORA-01649, 00000, "operation not allowed with a backup controlfile" Cause: An attempt is being made to perform a command that does not make sense when the controlfile is a restored backup. Action:Wait until after the database has been opened and try again. ORA-01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s" Cause: Failed to allocate an extent for rollback segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01651, 00000, "unable to extend save undo segment by %s for tablespace %s" Cause: Failed to allocate an extent for saving undo entries for the indicated offline tablespace. Action: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied. ORA-01652, 00000, "unable to extend temp segment by %s in tablespace %s" Cause: Failed to allocate an extent for temp segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01653, 00000, "unable to extend table %s.%s by %s in tablespace %s" Cause: Failed to allocate an extent for table segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01654, 00000, "unable to extend index %s.%s by %s in tablespace %s" Cause: Failed to allocate an extent for index segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01655, 00000, "unable to extend cluster %s.%s by %s in tablespace %s" Cause: Failed to allocate an extent for cluster segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01656, 00000, "max # extents (%s) reached in cluster %s.%s" Cause: A cluster tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01657, 00000, "invalid SHRINK option value" Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-01658, 00000, "unable to create INITIAL extent for segment in tablespace %s" Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created. Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL ORA-01659, 00000, "unable to allocate MINEXTENTS beyond %s in tablespace %s" Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created. Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE ORA-01660, 00000, "tablespace '%s' is already permanent" Cause: Attempting to make tablespace permanent that is already permanent. Action: Leave tablespace permanent. ORA-01661, 00000, "tablespace '%s' is already temporary" Cause: Attempting to make tablespace temporary that is already temporary. Action: Leave tablespace permanent. ORA-01662, 00000, "tablespace '%s' is non-empty and cannot be made temporary" Cause: Tried to convert a non-empty tablespace to a temporary tablespace Action: To drop all the objects in the tablespace. ORA-01663, 00000, "the contents of tablespace '%s' is constantly changing" Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY. Action: To decide what the tablespace contents should be and stay with it. ORA-01664, 00000, "Transaction which has expanded the Sort Segment has aborted" Cause: Internal Error. Action: Contact Oracle Support. ORA-01665, 00000, "controlfile is not a standby controlfile" Cause: Attempting to mount, recover or activate a standby database without a standby controlfile. Action: Create a standby controlfile before attempting to use the database as a standby database. ORA-01666, 00000, "controlfile is for a standby database" Cause: Attempting to mount, recover, or open a standby database without the appropriate command option to designate a standby database. Action: Use the standby option or appropriate commands, or mount with the primary controlfile. ORA-01667, 00000, "cannot add any more tablespaces: limit of %s exceeded" Cause: There is no more room in the controlfile for adding tablespaces. Action: Resize the controlfile or drop other tablespaces. ORA-01668, 00000, "standby database requires DROP option for offline of data file" Cause: Attempting to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later. Action: Specify the DROP option or leave the file online. ORA-01669, 00000, "standby database controlfile not consistent" Cause: Attempting to activate a standby database with a controlfile that has not been recovered to the same point as the data files. Most likely the controlfile was just copied from the primary database and has not been used for recovery. Action: Recover the standby database until all the files are consistent. ORA-01670, 00000, "new datafile %s needed for standby database recovery" Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby. Action: Either copy the file from the primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover. ORA-01671, 00000, "controlfile is a backup, cannot make a standby controlfile" Cause: The currently mounted controlfile is a backup controlfile, and attempting to create a controlfile for a standby database. Action: Complete any needed recovery and open the database with the resetlogs option. ORA-01672, 00000, "controlfile may be missing files or have extra ones" Cause: Attempting to create a standby controlfile, but the controlfile was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the controlfile and the ones in the data dictionary may not match. Action: Open the database, then retry the operation. ORA-01673, 00000, "data file %s has not been identified" Cause: This data file was not in the controlfile after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we can not create a standby controlfile. Action: Find the file and bring it online. If desired it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error. ORA-01674, 00000, "data file %s is an old incarnation rather than current file" Cause: Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file. Action: Rebuild the controlfile using CREATE CONTROLFILE, and give the correct file. ORA-01675, 00000, "max_commit_propagation_delay inconsistent with other instances" Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent with those in other instances. Action: Make sure all instances have the same max_commit_propagation_delay. ORA-01676, 00000, "standby file name convert of '%s' exceeds maximum length of %s" Cause: When the given file name is converted to the name used for the standby database, the converted name is bigger than the maximum allowed file name. Action: Change initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name. ORA-01677, 00000, "standby file name convert parameters differ from other instance" Cause: The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT initialization parameters are not the same as in other instances that already have the database mounted. Action: Change initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances. ORA-01678, 00000, "parameter %s must be pairs of pattern and replacement strings" Cause: The initialization parameter does not have even number of strings for its value. The odd numbered strings are patterns to be found in file names. The even numbered strings are used to replace the corresponding patterns when found in file names. Action:Specify even number of strings for the parameter, or omit the parameter. ORA-01679, 00000, "database must be mounted EXCLUSIVE and not open to activate" Cause: An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open. Action: Mount the database EXCLUSIVE and retry the ACTIVATE command. ORA-01680, 00000, "unable to extend LOB segment by %s in tablespace %s" Cause: Failed to allocate an extent for a LOB segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01681, 00000, "max # extents (%s) reached in LOB segment in tablespace %s" Cause: A LOB segment tried to extend past max extents. Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace ORA-01682, 00000, "read-only DB cannot allocate temporary space in tablespace %s" Cause: Temporary space (usually for sorting) could not be allocated in either main storage or a tempfile. An attempt was made to allocate the space from the tablespace named, but the database is opened read-only. The database open requires a sort work space. Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE initialization parameter), or create a temporary tablespace before making the database read-only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace. ORA-01683, 00000, "unable to extend index %s.%s partition %s by %s in tablespace %s" Cause: Failed to allocate an extent for index segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01684, 00000, "max # extents (%s) reached in table %s.%s partition %s" Cause: A table tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01685, 00000, "max # extents (%s) reached in index %s.%s partition %s" Cause: An index tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01686, 00000, "max # files (%s) reached for the tablespace %s" Cause: The number of files for a given tablespace has reached its maximum value Action: Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace. ORA-01687, 00000, "specified logging attribute for tablespace '%s' is same as the existing" Cause: Attempting to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute Action: Change the specified logging attribute ORA-01688, 00000, "unable to extend table %s.%s partition %s by %s in tablespace %s" Cause: Failed to allocate an extent for table segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01689, 00000, "syntax error in clause \"%s\" of %s" Cause: There was a syntax in the INIT.ORA parameter. Action: Fix the syntax error and restart the instance. ORA-01690, 00000, "sort area size too small" Cause: sort area size too small to fit two records in memory Action: increase sort_area_size ORA-01691, 00000, "unable to extend lob segment %s.%s by %s in tablespace %s" Cause: Failed to allocate an extent for lob segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01692, 00000, "unable to extend lob segment %s.%s partition %s by %s in tablespace %s" Cause: Failed to allocate an extent for lob segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01693, 00000, "max # extents (%s) reached in lob segment %s.%s" Cause: A lob segment tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01694, 00000, "max # extents (%s) reached in lob segment %s.%s partition %s" Cause: A lob segment tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01695, 00000, "error converting rollback segment %s to version 8.0.2" Cause: Version 8.0.1 database may not have shutdown cleanly Action: May have to reload the 8.0.1 database and shutdown cleanly ORA-01696, 00000, "controlfile is not a clone controlfile" Cause: Attempting to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current controlfile for a clone. Action: Mount without the clone option or use a backup controlfile and shutdown the other instances before mounting as a clone. ORA-01697, 00000, "controlfile is for a clone database" Cause: Attempting to mount a clone database without the appropriate command option to designate a clone database. Action: Use the clone option or appropriate commands, or mount with the primary controlfile. ORA-01698, 00000, "a clone database may only have SYSTEM rollback segment online" Cause: Attempting to online a rollback segment in a clone database. Action: Do not use this command. ORA-01699, 00000, "tablespace '%s' is being imported for point in time recovery" Cause: Attempting to online a tablespace or begin another point in time import while a point in time import is already in progress Action: Wait until the import complets / / 1700 - 1799 Parse errors continued from 900 - 999 / ORA-01700, 00000, "duplicate username in list" Cause: Action: ORA-01701, 00000, "a cluster is not appropriate here" Cause: Action: ORA-01702, 00000, "a view is not appropriate here" Cause: Action: ORA-01703, 00000, "missing SYNONYM keyword" Cause: Action: ORA-01704, 00000, "string literal too long" Cause: The string literal is longer than 4000 characters. Action: Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables. ORA-01705, 00000, "an outer join cannot be specified on a correlation column" Cause: Action: ORA-01706, 00000, "user function result value was too large" Cause: Action: ORA-01707, 00000, "missing LIST keyword" Cause: Action: ORA-01708, 00000, "ACCESS or SESSION expected" Cause: Action: ORA-01709, 00000, "program does not exist" Cause: Action: ORA-01710, 00000, "missing OF keyword" Cause: Action: ORA-01711, 00000, "duplicate privilege listed" Cause: Action: ORA-01712, 00000, "you cannot grant a privilege which you do not have" Cause: Action: ORA-01713, 00000, "GRANT OPTION does not exist for that privilege" Cause: Action: ORA-01714, 00000, "error in execution of user function" Cause: Action: ORA-01715, 00000, "UNIQUE may not be used with a cluster index" Cause: An attempt was made to create a cluster index with the UNIQUE attribute. Action: Remove UNIQUE from the CREATE INDEX statement. ORA-01716, 00000, "NOSORT may not be used with a cluster index" Cause: An attempt was made to create a cluster index using the NOSORT option. Action: Remove NOSORT from the CREATE INDEX statement. ORA-01717, 00000, "seccta: invalid access mode token passed" Cause: Action: ORA-01718, 00000, "BY ACCESS | SESSION clause not allowed for NOAUDIT" Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement. Action: Remove BY ACCESS | SESSION. ORA-01719, 00000, "outer join operator (+) not allowed in operand of OR or IN" Cause: An outer join appears in an or clause. Action: If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)). ORA-01720, 00000, "grant option does not exist for '%s.%s'" Cause: A grant was being performed on a view and the grant option was not present for an underlying object. Action: Obtain the grant option on all underlying objects of the view. ORA-01721, 00000, "USERENV(COMMITSCN) invoked more than once in a transaction" Cause: The USERENV('COMMITSCN') function can only be used once in a transaction. Action: Re-write the transactioin to use USERENV('COMMITSCN') only once ORA-01722, 00000, "invalid number" Cause: Action: ORA-01723, 00000, "zero-length columns are not allowed" Cause: Action: ORA-01724, 00000, "floating point precision is out of range (1 to 126)" Cause: Self-evident. Action: Self-evident. ORA-01725, 00000, "USERENV('COMMITSCN') not allowed here" Cause: The function USERNEV('COMMMITSCN') is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement. Action: Correct the use of the function. ORA-01726, 00000, "a table is not appropriate here" Cause: Action: ORA-01727, 00000, "numeric precision specifier is out of range (1 to 38)" Cause: Action: ORA-01728, 00000, "numeric scale specifier is out of range (-84 to 127)" Cause: Action: ORA-01729, 00000, "database link name expected" Cause: Action: ORA-01730, 00000, "invalid number of column names specified" Cause: Action: ORA-01731, 00000, "circular view definition encountered" Cause: Action: ORA-01732, 00000, "data manipulation operation not legal on this view" Cause: Action: ORA-01733, 00000, "virtual column not allowed here" Cause: Action: ORA-01734, 00000, "illegal parameters - EXTENT MIN higher than EXTENT MAX" Cause: A wrong value is specified for the parameter. Action: Correct the parameter and reissue the statement. ORA-01735, 00000, "invalid ALTER TABLE option" Cause: Action: ORA-01736, 00000, "[NOT] SUCCESSFUL expected" Cause: Action: ORA-01737, 00000, "valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE" Cause: Action: Valid lock modes are SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, SHARE ROW EXCLUSIVE, and SHARE UPDATE. ORA-01738, 00000, "missing IN keyword" Cause: Action: ORA-01739, 00000, "missing MODE keyword" Cause: Action: ORA-01740, 00000, "missing double quote in identifier" Cause: Action: ORA-01741, 00000, "illegal zero-length identifier" Cause: Action: ORA-01742, 00000, "comment not terminated properly" Cause: The indicated comment or hint begun with the /* token did not have the terminating */. Action: Properly terminate the comment or hint with a */. ORA-01743, 00000, "only pure functions can be indexed" Cause: The indexed function uses SYSDATE or the user environment. Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK. ORA-01744, 00000, "inappropriate INTO" Cause: Action: ORA-01745, 00000, "invalid host/bind variable name" Cause: Action: ORA-01746, 00000, "indicator variable not permitted here" Cause: Action: ORA-01747, 00000, "invalid user.table.column, table.column, or column specification" Cause: Action: ORA-01748, 00000, "only simple column names allowed here" Cause: Action: ORA-01749, 00000, "you may not GRANT/REVOKE privileges to/from yourself" Cause: Action: ORA-01750, 00000, "UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column" Cause: Action: ORA-01751, 00000, "Invalid dump undo option" Cause: An invalid option is specified in the ALTER DUMP UNDO command. Action: Correct and reissue the command. ORA-01752, 00000, "cannot delete from view without exactly one key-preserved table" Cause: The deleted table either had no key perserved tables, had more than one key-preserved table, or the key-preserved table was an unmerged view or a table from a read-only view. Action: Redefine the view or delete it from the underlying base tables. ORA-01753, 00000, "column definition incompatible with clustered column definition" Cause: Action: ORA-01754, 00000, "a table may contain only one column of type LONG" Cause: An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped. Action: Remove the LONG column currently in the table by using the ALTER TABLE command. ORA-01755, 00000, "Must specify an extent number or block number" Cause: Expecting an extent or block number but something else was specified. Action: Correct the error and reissue the command. ORA-01756, 00000, "quoted string not properly terminated" Cause: Action: ORA-01757, 00000, "Must specify an object number" Cause: Expecting an object number but something else was specified. Action: Correct the error and reissue the command. ORA-01758, 00000, "table must be empty to add mandatory (NOT NULL) column" Cause: Action: ORA-01759, 00000, "user function is incorrectly defined" Cause: Action: ORA-01760, 00000, "illegal argument for function" Cause: Action: ORA-01761, 00000, "DML operation does not map to a unique table in the join" Cause: The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table. Action: Change the join specification. ORA-01762, 00000, "vopdrv: view query block not in FROM" Cause: Action: ORA-01763, 00000, "update or delete involves outer joined table" Cause: For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table. Action: Change the join specification. ORA-01764, 00000, "new update value of join is not guaranteed to be unique" Cause: A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated. Action: Change the join specification. ORA-01765, 00000, "specifying table's owner name is not allowed" Cause: Action: ORA-01766, 00000, "dictionary table not allowed in this context" Cause: Action: ORA-01767, 00000, "UPDATE ... SET expression must be a subquery" Cause: Action: ORA-01768, 00000, "number string too long" Cause: Action: ORA-01769, 00000, "duplicate CLUSTER option specifications" Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option. Action: Remove the extra CLUSTER option. ORA-01770, 00000, "CLUSTER option not allowed in CREATE CLUSTER command" Cause: Action: ORA-01771, 00000, "illegal option for a clustered table" Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself. Action: Remove the illegal option(s). ORA-01772, 00000, "Must specify a value for LEVEL" Cause: Expecting the value of LEVEL but something else was specified. Action: Correct the error and reissue the command. ORA-01773, 00000, "may not specify column datatypes in this CREATE TABLE" Cause: Action: ORA-01774, 00000, "Dump undo option specified more than once" Cause: The same option for ALTER DUMP UNDO was specified twice. Action: Remove the redundant options and reissue the command. ORA-01775, 00000, "looping chain of synonyms" Cause: Action: ORA-01776, 00000, "cannot modify more than one base table through a join view" Cause: Columns belonging to more than one underlying table were either inserted into or updated. Action: Phrase the statement as two or more separate statements. ORA-01777, 00000, "WITH GRANT OPTION not allowed in this system" Cause: Action: ORA-01778, 00000, "maximum subquery nesting level exceeded" Cause: Action: ORA-01779, 00000, "cannot modify a column which maps to a non key-preserved table" Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table. Action: Modify the underlying base tables directly. ORA-01780, 00000, "string literal required" Cause: Action: / ORA-01781, 00000, "UNRECOVERABLE cannot be specified without AS SELECT" Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause. Action: Do not specify UNRECOVERABLE. / ORA-01782, 00000, "UNRECOVERABLE cannot be specified for a cluster or clustered table" Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE. Action: Do not specify UNRECOVERABLE. / ORA-01783, 00000, "only one RECOVERABLE or UNRECOVERABLE clause may be specified" Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement. Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement. / ORA-01784, 00000, "RECOVERABLE cannot be specified with database media recovery disabled" Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created. Action: Do not specify RECOVERABLE, or restart the database with media recovery enabled. / ORA-01785, 00000, "ORDER BY item must be the number of a SELECT-list expression" Cause: Action: ORA-01786, 00000, "FOR UPDATE of this query expression is not allowed" Cause: Action: ORA-01787, 00000, "only one clause allowed per query block" Cause: Action: ORA-01788, 00000, "CONNECT BY clause required in this query block" Cause: Action: ORA-01789, 00000, "query block has incorrect number of result columns" Cause: Action: ORA-01790, 00000, "expression must have same datatype as corresponding expression" Cause: Action: ORA-01791, 00000, "not a SELECTed expression" Cause: Action: ORA-01792, 00000, "maximum number of columns in a table or view is 1000" Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit. Action: If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit. ORA-01793, 00000, "maximum number of index columns is 32" Cause: Action: ORA-01794, 00000, "maximum number of cluster columns is 32" Cause: Action: ORA-01795, 00000, "maximum number of expressions in a list is 1000" Cause: Action: ORA-01796, 00000, "this operator cannot be used with lists" Cause: Action: ORA-01797, 00000, "this operator must be followed by ANY or ALL" Cause: Action: ORA-01798, 00000, "missing EXCEPTION keyword" Cause: Action: ORA-01799, 00000, "a column may not be outer-joined to a subquery" Cause:(+) () is not allowed. Action: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case. / / parse errors continued at 2000 / / 1800 - 1899 Date function errors / 1800 - 1809 Overflow conditions / ORA-01800, 00000, "a literal in the date format was too large to process" Cause: Action: ORA-01801, 00000, "date format is too long for internal buffer" Cause: Action: ORA-01802, 00000, "Julian date is out of range" Cause: Action: ORA-01803, 00000, "failure in getting date/time" Cause: Action: ORA-01804, 00000, "failure to initialize timezone information" Cause: The timezone information file was not properly read. Action: Please contact Oracle Customer Support. / / 1810 - 1829 Conflicting date input format / ORA-01810, 00000, "format code appears twice" Cause: Action: ORA-01811, 00000, "Julian date precludes use of day of year" Cause: Action: ORA-01812, 00000, "year may only be specified once" Cause: Action: ORA-01813, 00000, "hour may only be specified once" Cause: Action: ORA-01814, 00000, "AM/PM conflicts with use of A.M./P.M." Cause: Action: ORA-01815, 00000, "BC/AD conflicts with use of B.C./A.D." Cause: Action: ORA-01816, 00000, "month may only be specified once" Cause: Action: ORA-01817, 00000, "day of week may only be specified once" Cause: Action: ORA-01818, 00000, "'HH24' precludes use of meridian indicator" Cause: Action: ORA-01819, 00000, "signed year precludes use of BC/AD" Cause: Action: ORA-01820, 00000, "format code cannot appear in date input format" Cause: Action: ORA-01821, 00000, "date format not recognized" Cause: Action: ORA-01822, 00000, "era format code is not valid with this calendar" Cause: Action: / / 1830 - 1899 Failed input conversions / ORA-01830, 00000, "date format picture ends before converting entire input string" Cause: Action: ORA-01831, 00000, "year conflicts with Julian date" Cause: Action: ORA-01832, 00000, "day of year conflicts with Julian date" Cause: Action: ORA-01833, 00000, "month conflicts with Julian date" Cause: Action: ORA-01834, 00000, "day of month conflicts with Julian date" Cause: Action: ORA-01835, 00000, "day of week conflicts with Julian date" Cause: Action: ORA-01836, 00000, "hour conflicts with seconds in day" Cause: Action: ORA-01837, 00000, "minutes of hour conflicts with seconds in day" Cause: Action: ORA-01838, 00000, "seconds of minute conflicts with seconds in day" Cause: Action: ORA-01839, 00000, "date not valid for month specified" Cause: Action: ORA-01840, 00000, "input value not long enough for date format" Cause: Action: ORA-01841, 00000, "(full) year must be between -4713 and +9999, and not be 0" Cause: Illegal year entered Action: Input year in the specified range ORA-01842, 00000, "quarter must be between 1 and 4" Cause: Action: ORA-01843, 00000, "not a valid month" Cause: Action: ORA-01844, 00000, "week of year must be between 1 and 52" Cause: Action: ORA-01845, 00000, "week of month must be between 1 and 5" Cause: Action: ORA-01846, 00000, "not a valid day of the week" Cause: Action: ORA-01847, 00000, "day of month must be between 1 and last day of month" Cause: Action: ORA-01848, 00000, "day of year must be between 1 and 365 (366 for leap year)" Cause: Action: ORA-01849, 00000, "hour must be between 1 and 12" Cause: Action: ORA-01850, 00000, "hour must be between 0 and 23" Cause: Action: ORA-01851, 00000, "minutes must be between 0 and 59" Cause: Action: ORA-01852, 00000, "seconds must be between 0 and 59" Cause: Action: ORA-01853, 00000, "seconds in day must be between 0 and 86399" Cause: Action: ORA-01854, 00000, "julian date must be between 1 and 5373484" Cause: An invalid Julian date was entered. Action: Enter a valid Julian date between 1 and 5373484. ORA-01855, 00000, "AM/A.M. or PM/P.M. required" Cause: Action: ORA-01856, 00000, "BC/B.C. or AD/A.D. required" Cause: Action: ORA-01857, 00000, "not a valid time zone" Cause: Action: ORA-01858, 00000, "a non-numeric character was found where a numeric was expected" Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model. Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. ORA-01859, 00000, "a non-alphabetic character was found where an alphabetic was expected" Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model. Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. ORA-01860, 00000, "week of year must be between 1 and 53" Cause: Action: ORA-01861, 00000, "literal does not match format string" Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace. Action: Correct the format string to match the literal. ORA-01862, 00000, "the numeric value does not match the length of the format item" Cause: When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will. Action: Correct the input date or turn off the FX or FM format specifier in the format string. ORA-01863, 00000, "the year is not supported for the current calendar" Cause: The year is not supported for the current calendar. Action: Please check the documentation to find out what years are supported for the current calendar. ORA-01864, 00000, "the date is out of range for the current calendar" Cause: Your calendar doesn't extend to the specified date. Action: Specify a date which is legal for this calendar. ORA-01865, 00000, "not a valid era" Cause: Era input does not match a known era. Action: Provide a valid era on input. ORA-01866, 00000, "the datetime class is invalid" Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. ORA-01867, 00000, "the interval is invalid" Cause: The character string you specified is not a valid interval. Action: Please specify a valid interval. ORA-01868, 00000, "the leading precision of the interval is too small" Cause: The leading precision of the interval is too small to store the specified interval. Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision. ORA-01869, 00000, "reserved for future use" Cause: Action: ORA-01870, 00000, "the intervals or datetimes are not mutually comparable" Cause: The intervals or datetimes are not mutually comparable. Action: Specify a pair of intervals or datetimes that are mutually comparable. ORA-01871, 00000, "the number of seconds must be less than 60" Cause: The number of seconds specified was greater than 59. Action: Specify a value for seconds that is 59 or smaller. ORA-01872, 00000, "reserved for future use" Cause: Action: ORA-01873, 00000, "the leading precision of the interval is too small" Cause: The leading precision of the interval is too small to store the specified interval. Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision. ORA-01874, 00000, "time zone hour must be between -12 and 13" Cause: The time zone hour specified was not in the valid range. Action: Specify a time zone hour between -12 and 13. ORA-01875, 00000, "time zone minute must be between -59 and 59" Cause: The time zone minute specified was not in the valid range. Action: Specify a time zone minute between -59 and 59. ORA-01876, 00000, "year must be at least -4713" Cause: The specified year was not in range. Action: Specify a year that is greater than or equal to -4713. ORA-01877, 00000, "string is too long for internal buffer" Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. ORA-01878, 00000, "specified field not found in datetime or interval" Cause: The specified field was not found in the datetime or interval. Action: Make sure that the specified field is in the datetime or interval. ORA-01879, 00000, "the hh25 field must be between 0 and 24" Cause: The specified hh25 field was not in the valid range. Action: Specify an hh25 field between 0 and 24. ORA-01880, 00000, "the fractional seconds must be between 0 and 999999999" Cause: The specified fractional seconds were not in the valid range. Action: Specify a value for fractional seconds between 0 and 999999999. ORA-01881, 00000, "timezone region id %d is invalid" Cause: The region id referenced an invalid region. Action: Please contact Oracle Customer Support. ORA-01882, 00000, "timezone region %s not found" Cause: The specified region name was not found. Action: Please contact Oracle Customer Support. ORA-01883, 00000, "overlap was disabled during a region transition" Cause: The region was changing state and the overlap flag was disabled. Action: Please contact Oracle Customer Support. ORA-01890, 00000, "NLS error detected" Cause: An NLS error was detected. Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support. ORA-01891, 00000, "Datetime/Interval internal error" Cause: Internal error. Action: Please contact Oracle Worldwide Support. ORA-01898, 00000, "too many precision specifiers" Cause: While trying to truncate or round dates, extra data was found in the date format picture Action: Check the syntax of the date format picture and retry. ORA-01899, 00000, "bad precision specifier" Cause: Action: / / 1900 - 1999 V6 parse errors / ORA-01900, 00000, "LOGFILE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01901, 00000, "ROLLBACK keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01902, 00000, "SEGMENT keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01903, 00000, "EVENTS keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01904, 00000, "DATAFILE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01905, 00000, "STORAGE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01906, 00000, "BACKUP keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01907, 00000, "TABLESPACE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01908, 00000, "EXISTS keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01909, 00000, "REUSE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01910, 00000, "TABLES keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01911, 00000, "CONTENTS keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01912, 00000, "ROW keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01913, 00000, "EXCLUSIVE keyword expected" Cause: keyword missing Action: supply missing keyword ORA-01914, 00000, "invalid auditing option for sequence numbers" Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers. Action: The following options may not be used for sequence numbers and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE ORA-01915, 00000, "invalid auditing option for views" Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views. Action: The following options may not be used for views and should be removed: ALTER, INDEX, REFERENCES, EXECUTE ORA-01916, 00000, "keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected" Cause: An expected keyword was not used for datafile/tempfile clause Action: Use correct syntax. ORA-01917, 00000, "user or role '%s' does not exist" Cause: There is not a user or role by that name. Action: Re-specify the name. ORA-01918, 00000, "user '%s' does not exist" Cause: User does not exist in the system. Action: Verify the user name is correct. ORA-01919, 00000, "role '%s' does not exist" Cause: Role by that name does not exist. Action: Verify you are using the correct role name. ORA-01920, 00000, "user name '%s' conflicts with another user or role name" Cause: There is already a user or role with that name. Action: Specify a different user name. ORA-01921, 00000, "role name '%s' conflicts with another user or role name" Cause: There is already a user or role with that name. Action: Specify a different role name. ORA-01922, 00000, "CASCADE must be specified to drop '%s'" Cause: Cascade is required to remove this user from the system. The user own's object which will need to be dropped. Action: Specify cascade. ORA-01923, 00000, "CASCADE aborted, objects locked by another user" Cause: Cannot drop the user's objects; someone has them locked. Action: Use the lock monitor to determine who has the objects locked. ORA-01924, 00000, "role '%s' not granted or does not exist" Cause: Set role can only be performed with roles granted directly to your account. (e.g. a sub-role cannot be enabled) Action: Don't try to set the role. ORA-01925, 00000, "maximum of %s enabled roles exceeded" Cause: The INIT.ORA parameter "max_enabled_roles" has been exceeded. Action: Increase max_enabled_roles and warm start the database. ORA-01926, 00000, "cannot GRANT to a role WITH GRANT OPTION" Cause: Role cannot have a privilege with the grant option. Action: Perform the grant without the grant option. ORA-01927, 00000, "cannot REVOKE privileges you did not grant" Cause: You can only revoke privileges you granted. Action: Don't revoke these privileges. ORA-01928, 00000, "GRANT option not granted for all privileges" Cause: In order to grant a privilege, you must first have the privilege with the grant option. Action: Obtain the privilege with the grant option and try again. ORA-01929, 00000, "no privileges to GRANT" Cause: "ALL" was specified but the user doesn't have any privileges with the grant option. Action: Don't grant privileges on that object. ORA-01930, 00000, "auditing the object is not supported" Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited. Action: Don't attempt to AUDIT the object. ORA-01931, 00000, "cannot grant %s to a role" Cause: UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER privilege cannot be granted to a role. Action: Grant privilege directly to the user. ORA-01932, 00000, "ADMIN option not granted for role '%s'" Cause: The operation requires the admin option on the role. Action: Obtain the grant option and re-try. ORA-01933, 00000, "cannot create a stored object using privileges from a role" Cause: An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles. Action: Grant the privileges required to the user directly. ORA-01934, 00000, "circular role grant detected" Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself. Action: Do not perform the grant. ORA-01935, 00000, "missing user or role name" Cause: A user or role name was expected. Action: Specify a user or role name. ORA-01936, 00000, "cannot specify owner when creating users or roles" Cause: Users and roles do not have owners. Action: Don't specify an owner. ORA-01937, 00000, "missing or invalid role name" Cause: A valid role name was expected. Action: Specify a valid role name. ORA-01938, 00000, "IDENTIFIED BY must be specified for CREATE USER" Cause: Cannot create a user without specifying a password or "IDENTIFIED EXTERNALLY". Action: Specify one of the password clauses. ORA-01939, 00000, "only the ADMIN OPTION can be specified" Cause: System privileges and Roles can only be granted with the admin option. The grant option cannot be used with these privileges. Action: Specify the admin option. ORA-01940, 00000, "cannot drop a user that is currently connected" Cause: Attempt was made to drop a user that is currently logged in. Action: Make sure user is logged off, then repeat command. ORA-01941, 00000, "SEQUENCE keyword expected" MERGE: 1917 RENUMBERED TO 1941 Cause: keyword missing Action: supply missing keyword ORA-01942, 00000, "IDENTIFIED BY and EXTERNALLY cannot both be specified" Cause: A user cannot be specified to have and not have a password. Action: Specify only one of the options. ORA-01943, 00000, "IDENTIFIED BY already specified" Cause: The identified clause has been given twice. Action: Use only one identified by clause. ORA-01944, 00000, "IDENTIFIED EXTERNALLY already specified" Cause: The identified externaly clause has been given twice. Action: Use only one identified clause. ORA-01945, 00000, "DEFAULT ROLE[S] already specified" Cause: The default roles clause has been given twice. Action: Use only on default role clause. ORA-01946, 00000, "DEFAULT TABLESPACE already specified" Cause: The default tablespace clause has been given twice. Action: Use only one default tablespace clause. ORA-01947, 00000, "TEMPORARY TABLESPACE already specified" Cause: The temporary tablespace clause has been given twice. Action: Use only one temporary tablespace clause. ORA-01948, 00000, "identifier's name length (%s) exceeds maximum (%s)" Cause: A name has been specified that is too long. For example, dbms_session.is_role_enabled() specifies a role name that is too long. Action: Change the application or command to use a correct identifier. ORA-01949, 00000, "ROLE keyword expected" Cause: The role keyword is required here. Action: Specify the role keyword. ORA-01950, 00000, "no privileges on tablespace '%s'" Cause: User does not have privileges to allocate an extent in the specified tablespace. Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace. ORA-01951, 00000, "ROLE '%s' not granted to '%s'" Cause: The role you tried to revoke was not granted to the user. Action: Don't try to revoke a privilege which is not granted. ORA-01952, 00000, "system privileges not granted to '%s'" Cause: A system privilege you tried to revoke was not granted to the user. Action: Make sure the privileges you are trying to revoke are granted. ORA-01953, 00000, "command no longer valid, see ALTER USER" Cause: The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality Action: Use the alter user command instead. ORA-01954, 00000, "DEFAULT ROLE clause not valid for CREATE USER" Cause: Default roles cannot be specified for create user. Action: Grant and alter the user's default roles after creating the user. ORA-01955, 00000, "DEFAULT ROLE '%s' not granted to user" Cause: The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the default role clause. Action: Grant the role to the user. ORA-01956, 00000, "invalid command when OS_ROLES are being used" Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is TRUE. Action: Grant the role to the user in the operating system. ORA-01957, 00000, "Keyword MIN or MAX expected, not found" Cause: Action: ORA-01958, 00000, "Must supply an integer for the LAYER option" Cause: Action: ORA-01959, 00000, "Must supply an integer for the OPCODE option" Cause: Action: ORA-01960, 00000, "Invalid dump logfile option" Cause: Action: ORA-01961, 00000, "Invalid dump option" Cause: Action: ORA-01962, 00000, "Must specify a file number or log sequence number" Cause: Action: ORA-01963, 00000, "Must specify a block number" Cause: Action: ORA-01964, 00000, "Must specify a time for the TIME option" Cause: Action: ORA-01965, 00000, "Must specify a PERIOD" Cause: Action: ORA-01967, 00000, "invalid option for CREATE CONTROLFILE" Cause: An invalid CREATE CONTROLFILE option is present. Action: Specify only valid CREATE CONTROLFILE options. ORA-01968, 00000, "Only specify RESETLOGS or NORESETLOGS once" Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. ORA-01969, 00000, "You must specify RESETLOGS or NORESETLOGS" Cause: Missing a RESETLOGS or a NORESETLOGS Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. ORA-01970, 00000, "You must specify a database name for CREATE CONTROLFILE" Cause: Missing a database name Action: Retype CREATE CONTROLFILE command with the DATABASE keyword. ORA-01971, 00000, "Illegal ALTER TRACING option" Cause: Action: ORA-01972, 00000, "Must specify a string for ALTER TRACING ENABLE or DISABLE" Cause: Action: ORA-01973, 00000, "Missing change number" Cause: Keyword "CHANGE" found but change number not specified. Action: Fix command line and resubmit ORA-01974, 00000, "Illegal archive option" Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command Action: ORA-01975, 00000, "Illegal character in change number %s" Cause: Action: ORA-01976, 00000, "Missing change number" Cause: Action: ORA-01977, 00000, "Missing thread number" Cause: Keyword "THREAD" found but thread number not specified. Action: Fix command line and resubmit ORA-01978, 00000, "Missing sequence number" Cause: Keyword "SEQUENCE" found but sequence number not specified. Action: Fix command line and resubmit ORA-01979, 00000, "missing or invalid password for role '%s'" Cause: An attempt was made to enable a role without giving / the proper password. Action: Use the "identified by" clause in set role to specify the correct password. ORA-01980, 00000, "error during OS ROLE initialization" Cause: An OS error occurred while loading a users OS ROLES. Action: Check the OS error. ORA-01981, 00000, "CASCADE CONSTRAINTS must be specified to perform this revoke" Cause: During this revoke some foreign key contraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified. Action: Remove the constraints or specify CASCADE CONSTRAINTS. ORA-01982, 00000, "invalid auditing option for tables" Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables. Action: The following options may not be used for tables and should be removed: REFERENCES, EXECUTE ORA-01983, 00000, "invalid auditing option for DEFAULT" Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT. Action: The following options may not be used for DEFAULT and should be removed: REFERENCES ORA-01984, 00000, "invalid auditing option for procedures/packages/functions" Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions. Action: The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE ORA-01985, 00000, "cannot create user as LICENSE_MAX_USERS parameter exceeded" Cause: Maximum users in the database license limit exceeded. Action: Increase license limit. ORA-01986, 00000, "invalid option for OPTIMIZER_GOAL" Cause: An invalid OPTIMIZER_GOAL option is present. Action: Check the syntax for OPTIMIZER_GOAL, specify a valid option and re-execute the statement. ORA-01987, 00000, "client os username is too long" Cause: A client's os username is too long for the os logon to succeed. Action: Use a shorter os username. ORA-01988, 00000, "remote os logon is not allowed" Cause: Remote os login attempted when not allowed. Action: Use a local client, or use the remote_os_authent system parameter to turn on remote os logon. ORA-01989, 00000, "role '%s' not authorized by operating system" Cause: The os role does not exist, is not granted to you, or you did not provide the correct password. Action: Re-attempt the SET ROLE with a valid os role and password, if necessary. ORA-01990, 00000, "error opening password file '%s'" Cause: Action: ORA-01991, 00000, "invalid password file '%s'" Cause: Action: ORA-01992, 00000, "error closing password file '%s'" Cause: Action: ORA-01993, 00000, "error writing password file '%s'" Cause: Action: ORA-01994, 00000, "GRANT failed: cannot add users to public password file" Cause: Action: ORA-01995, 00000, "error reading password file '%s'" Cause: Action: ORA-01996, 00000, "GRANT failed: password file '%s' is full" Cause: Action: ORA-01997, 00000, "GRANT failed: user '%s' is identified externally" Cause: Action: ORA-01998, 00000, "REVOKE failed: user SYS always has SYSOPER and SYSDBA" Cause: Action: ORA-01999, 00000, "password file mode has changed from '%s' to '%s'" Cause: Action: / / 2000 - 2099 Parse errors continued from 1700 - 1799 / ORA-02000, 00000, "missing %s keyword" ORA-02001, 00000, "user SYS is not permitted to create indexes with freelist groups" Cause: user tried to create an index while running with sys authorization. Action: ORA-02002, 00000, "error while writing to audit trail" Cause: Action: ORA-02003, 00000, "invalid USERENV parameter" Cause: Action: ORA-02004, 00000, "security violation" Cause: This error code is never returned to a user. It is used as a value for column, audit_trail.returncode, to signal that a security violation occurred. Action: None. ORA-02005, 00000, "implicit (-1) length not valid for this bind or define datatype" Cause: Action: ORA-02006, 00000, "invalid packed decimal format string" Cause: Action: ORA-02007, 00000, "can't use ALLOCATE or DEALLOCATE options with REBUILD" Cause: Allocate or deallocate storage and rebuild index are not compatible. Action: Choose one or the other. ORA-02008, 00000, "non-zero scale specified for nonnumeric column" Cause: Action: ORA-02009, 00000, "the size specified for a file must not be zero" Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification. Action: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause. ORA-02010, 00000, "missing host connect string" Cause: Action: ORA-02011, 00000, "duplicate database link name" Cause: Action: ORA-02012, 00000, "missing USING keyword" Cause: Action: ORA-02013, 00000, "missing CONNECT keyword" Cause: Action: ORA-02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc." ORA-02015, 00000, "cannot select FOR UPDATE from remote table" Cause: Action: ORA-02016, 00000, "cannot use a subquery in a START WITH on a remote database" Cause: Action: ORA-02017, 00000, "integer value required" Cause: Action: ORA-02018, 00000, "database link of same name has an open connection" Cause: Action: ORA-02019, 00000, "connection description for remote database not found" Cause: Action: ORA-02020, 00000, "too many database links in use" Cause: The current session has exceeded the INIT.ORA open_links maximum. Action: Increase the open_links limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases. ORA-02021, 00000, "DDL operations are not allowed on a remote database" Cause: An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname ...". Action: To alter the remote database structure, you must connect to the remote database with the appropriate privileges. ORA-02022, 00000, "remote statement has unoptimized view with remote object" Cause: The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database. Action: Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote. ORA-02023, 00000, "START WITH or CONNECT BY predicate cannot be evaluated by remote data base" Cause: Action: ORA-02024, 00000, "database link not found" Cause: Database link to be dropped is not found in dictionary Action: Correct the database link name ORA-02025, 00000, "all tables in the SQL statement must be at the remote database" Cause: The user's SQL statement references tables from multiple databases. The remote database is not Oracle V7 or above, and can perform updates only if it can reference all tables in the SQL statement. Action: ORA-02026, 00000, "missing LINK keyword" Cause: keyword missing Action: supply missing keyword ORA-02027, 00000, "multi-row UPDATE of LONG column is not supported" Cause: A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row. Action: You may only update a single row with such a bind variable. ORA-02028, 00000, "fetching an exact number of rows is not supported by the server" Cause: The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side. Action: Connect to a valid server or do not use an exact fetch. ORA-02029, 00000, "missing FILE keyword" Cause: keyword missing Action: supply missing keyword ORA-02030, 00000, "can only select from fixed tables/views" Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view. Action: You may only select rows from fixed tables/views. ORA-02031, 00000, "no ROWID for fixed tables or for external-organized tables" Cause: An attempt is being made to access rowid from a fixed table or from a external-organized table. Action: Do not access ROWID from a fixed table or from a external-organized table. ORA-02032, 00000, "clustered tables cannot be used before the cluster index is built" Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created. Action: Create the cluster index. ORA-02033, 00000, "a cluster index for this cluster already exists" Cause: A cluster index already exists for the cluster. Action: None. ORA-02034, 00000, "speed bind not permitted" Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system. Action: none ORA-02035, 00000, "illegal bundled operation combination" Cause: User requested that the UPI bundled execution call perform an an illegal combination of operations. Action: See documentation for legal operation combinations. ORA-02036, 00000, "too many variables to describe with automatic cursor open" Cause: User requested that the UPI bundled execution call perform automatic cursor open and close on a describe operation. There were too many select-list items or bind variables to do this. Action: open and close cursor explicitly ORA-02037, 00000, "uninitialized speed bind storage" Cause: User attempted a UPI bundled execution call containing a standalone execute operation without first performing a UPI bundled execution call containing a bind operation. Action: perform a UPI bundled execution call with bind before performing a bundled execution call with execute ORA-02038, 00000, "define is not allowed for array type " Cause: User attempted to define a select list variable of type "array". Arrays may only serve as host bind variables. Action: ORA-02039, 00000, "bind by value is not allowed for array type " Cause: User attempted to bind an array host variable by value. Arrays may only be bound by reference. Action: / / 2040 .. 2099 - Reserved for distributed update / (Message range continued at 160) / ORA-02040, 00000, "remote database %s does not support two-phase commit" Cause: the database was potentially updated but does not support prepare to commit (as determined by its logon transaction traits). The transaction was rolled back. Action: Do not attempt to update the remote database unless it is the only database updated in one transaction. ORA-02041, 00000, "client database did not begin a transaction" Cause: internal error Action: contact support ORA-02042, 00000, "too many distributed transactions" Cause: the distributed transaction table is full, because too many distributed transactions are active. Action: increase the INIT.ORA "distributed_transactions" or run fewer transactions. If you are sure you don't have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown/restart would be a work-around. ORA-02043, 00000, "must end current transaction before executing %s" Cause: a transaction is in progress and one of the following commands commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. Action: COMMIT or ROLLBACK the current transaction and resubmit command. ORA-02044, 00000, "transaction manager login denied: transaction in progress" Cause: a remote transaction manager tried to log in while a distributed transaction is in progress. Action: end the current transaction (this is a protocol error from a remote transaction manager) ORA-02045, 00000, "too many local sessions participating in global transaction" Cause: too many sessions at this site for this transaction. Action: use an existing link so another session need not be created. ORA-02046, 00000, "distributed transaction already begun" Cause: internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran. ORA-02047, 00000, "cannot join the distributed transaction in progress" Cause: Either a transaction is in progress against a remote database that does not fully support two phase commit, and an update is attempted on another database, or updates are pending and and an attempt is made to update a different database that does not fully support two phase commit. Action: complete the current transaction and then resubmit the update request. ORA-02048, 00000, "attempt to begin distributed transaction without logging on" Cause: client program must issue a distributed transaction login. Action: contact support. ORA-02049, 00000, "timeout: distributed transaction waiting for lock" Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock. Action: treat as a deadlock ORA-02050, 00000, "transaction %s rolled back, some remote DBs may be in-doubt" Cause: network or remote failure in 2PC. Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired. ORA-02051, 00000, "another session in same transaction failed" Cause: a session at the same site with same global transaction ID failed. Action: none necessary, transaction automatically recovered. ORA-02052, 00000, "remote transaction failure at %s" Cause: error in remote transaction at given DBLINK Action: retry ORA-02053, 00000, "transaction %s committed, some remote DBs may be in-doubt" Cause: network or remote failure in 2PC. Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired. ORA-02054, 00000, "transaction %s in-doubt" Cause: network or remote failure in 2PC. Action: Notify operations; DBs will automatically re-sync when the failure is repaired. Monitor pending_trans$ for final outcome. ORA-02055, 00000, "distributed update operation failed; rollback required" Cause: a failure during distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent, the transaction must roll back to a savepoint or entirely Action: rollback to a savepoint or rollback transaction and resubmit ORA-02056, 00000, "2PC: %s: bad two-phase command number %s from %s" Cause: two-phase commit protocol error. Action: recovery of transaction attempted. Monitor pending_trans$ table to ensure correct resolution. Contact support. ORA-02057, 00000, "2PC: %s: bad two-phase recovery state number %s from %s" Cause: internal error in two-phase recovery protocol Action: contact support ORA-02058, 00000, "no prepared transaction found with ID %s" Cause: no transaction with local_tran_id or global_tran_id found in the pending_trans$ table in prepared state. Action: check the pending_trans$ table. ORA-02059, 00000, "ORA-2PC-CRASH-TEST-%s in commit comment" Cause: This is a special comment used to test the two phase commit. Action: Don't use this special comment (%s a number 1-10) ORA-02060, 00000, "select for update specified a join of distributed tables" Cause: tables in a join with the for update clause must reside at the same DB. ORA-02061, 00000, "lock table specified list of distributed tables" Cause: tables in a lock table statement must reside at the same DB. Action: issue multiple lock table commands. ORA-02062, 00000, "distributed recovery received DBID %s, expected %s" Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted. Action: restore link definition or remote database. ORA-02063, 00000, "preceding %s%s from %s%s" Cause: an Oracle error was received from a remote database link. Action: refer to the preceding error message(s) ORA-02064, 00000, "distributed operation not supported" Cause: One of the following unsupported operations was attempted: 1. array execute of a remote update with a subquery that references a dblink, or 2. an update of a long column with bind variable and an update of a second column with a subquery that both references a dblink and a bind variable, or 3. a commit is issued in a coordinated session from an RPC with OUT parameters. Action: simplify remote update statement ORA-02065, 00000, "illegal option for ALTER SYSTEM" Cause: The option specified for ALTER SYSTEM is not supported Action: refer to the user manual for option supported ORA-02066, 00000, "missing or invalid DISPATCHERS text" Cause: A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS Action: place the string literal containing the dispatcher's specification after ALTER SYSTEM SET DISPATCHERS ORA-02067, 00000, "transaction or savepoint rollback required" Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed. Action: rollback to a previous savepoint or rollback the transaction and resubmit. ORA-02068, 00000, "following severe error from %s%s" Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text. Action: Contact the remote system administrator. ORA-02069, 00000, "global_names parameter must be set to TRUE for this operation" Cause: A remote mapping of the statement is required but cannot be achieved because global_names should be set to TRUE for it to be achieved Action: Issue alter session set global_names = true if possible ORA-02070, 00000, "database %s%s does not support %s in this context" Cause: The remote database does not support the named capability in the context in which it is used. Action: Simplify the SQL statement. ORA-02071, 00000, "error initializing capabilities for remote database %s" Cause: Could not load a remote-specified capability table. Action: Contact support for the remote SQL*Connect product. ORA-02072, 00000, "distributed database network protocol mismatch" Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example. Action: Upgrade the older release. ORA-02073, 00000, "sequence numbers not supported in remote updates" Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables. Action: ORA-02074, 00000, "cannot %s in a distributed transaction" Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction. Action: Only commit or rollback from the parent session. ORA-02075, 00000, "another instance changed state of transaction %s" Cause: A commit force or rollback force was issued from a session in another instance. Action: Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction. ORA-02076, 00000, "sequence not co-located with updated table or long column" Cause: all referenced sequences must be co-located with the table with the long column. ORA-02077, 00000, "selects of long columns must be from co-located tables" Cause: if a select returns long columns from multiple tables, all the tables must be co-located ORA-02078, 00000, "invalid setting for ALTER SYSTEM FIXED_DATE" Cause: Action: ORA-02079, 00000, "no new sessions may join a committing distributed transaction" Cause: A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch; that is, a call to upi2en was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager. Action: Contact support. ORA-02080, 00000, "database link is in use" Cause: a transaction is active or a cursor is open on the database link given in the alter session close database link command. Action: commit or rollback, and close all cursors ORA-02081, 00000, "database link is not open" Cause: dblink given is not currently open. ORA-02082, 00000, "a loopback database link must have a connection qualifier" Cause: attempt to create a database link with the same name as the current database. Action: a loopback database link needs a trailing qualifier, e.g. MYDB.DEV.US.ORACLE.COM@INST1 - the '@INST1' is the qualifier ORA-02083, 00000, "database name has illegal character '%s'" Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters. ORA-02084, 00000, "database name is missing a component" Cause: supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row. ORA-02085, 00000, "database link %s connects to %s" Cause: a database link connected to a database with a different name. The connection is rejected. Action: create a database link with the same name as the database it connects to, or set global_names=false. ORA-02086, 00000, "database (link) name is too long" Cause: database/database link name can have at most 128 characters. ORA-02087, 00000, "object locked by another process in same transaction" Cause: A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session. Action: Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or, simply use the same session to access the object. ORA-02088, 00000, "distributed database option not installed" Cause: Remote and distributed updates and transactions are a separately priced option in ORACLE V7. ORA-02089, 00000, "COMMIT is not allowed in a subordinate session" Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator. Action: Issue commit at the global coordinator only. ORA-02090, 00000, "network error: attempted callback+passthru" Cause: internal error. ORA-02091, 00000, "transaction rolled back" Cause: Also see error 2092. If the transaction is aborted at a remote site then you will only see 2091; if aborted at host then you will see 2092 and 2091. Action: Add rollback segment and retry the transaction. ORA-02092, 00000, "out of transaction table slots for distributed transaction" Cause: The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back. Action: Add a rollback segment and retry the transaction. ORA-02093, 00000, "TRANSACTIONS_PER_ROLLBACK_SEGMENT(%s) more than maximum possible(%s)" Cause: Value of parameter specified is greater than allowed on this port. Action: Use default or reduce it to less than max. ORA-02094, 00000, "replication option not installed" Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable. Action: Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased. ORA-02095, 00000, "specified initialization parameter cannot be modified" Cause: The specified initialization parameter is not modifiable ORA-02096, 00000, "specified initialization parameter is not modifiable with this option" Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command. Action: Check the DBA guide for information about under what scope the parameter may be modified ORA-02097, 00000, "parameter cannot be modified because specified value is invalid" Cause: Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter. Action: Check the DBA guide for range of acceptable values for this parameter. ORA-02098, 00000, "error parsing index-table reference (:I)" Cause: An incorrect index-table (:I) syntax was encountered. Action: This syntax is for oracle internal use only. ORA-02099, 00000, "used for internal purposes, should never be printed" / / / MODIFIED / smuthuli 01/12/01 - add 3249 / vshukla 01/17/01 - Fix error message 2262. / gtarora 01/16/01 - add 2348 / dalpern 11/28/00 - privileges for kga debugger / smukkama 10/11/00 - add 3221 (disallow non-std block size temp segments) / bhirano 09/03/00 - add out-of-memory error for pool growth / preilly 08/14/00 - Update description to fix bug 1164753 / lsheng 07/27/00 - update error message ORA-02204 / preilly 07/31/00 - Update error message for bug 1164753 / skaluska 06/23/00 - add 3119, 3132. / mjstewar 06/13/00 - OMF / bdagevil 04/18/00 - add error msg for memory management / nireland 03/20/00 - Amend ORA-3219 message. #1152302 / rmurthy 03/31/00 - inheritance related changes / apadmana 01/06/00 - change SNAPSHOT to MATERIALIZED VIEW / skray 12/13/99 - modified alter tracing messages 2480-2489 / smuthuli 04/28/99 - add 3247 / lcprice 07/01/99 - 746805 modify 3211 message / mjungerm 03/23/99 - fix comment in 04044 / weiwang 02/02/99 - add schema name to error 4098 / akruglik 06/30/98 - incorporate Randy's comments / akruglik 06/30/98 - define msgs 3238 and 3239 / ansriniv 04/13/98 - add OER(4047) - dbms_shared_pool / atsukerm 03/03/98 - add subpartition messages to DBMS_SPACE package. / tnbui 12/03/97 - Change error messages for validating a constraint / bgoyal 12/17/97 - error 2327 change column to expression / bhimatsi 03/03/98 - bitmapped ts - add error messages / atsukerm 02/06/98 - add dbms_space_admin errors. / mkcyee 11/03/97 - #(568232): add error 3206 / lcprice 08/19/97 - Merge of bug fix 461293 / jwlee 08/04/97 - Add error 4018 / akruglik 07/29/97 - add msgs 3233-3236 / mluong 06/24/97 - merge from 803 / nireland 06/24/97 - Add error message 2475. (#324089) / anolan 05/21/97 - checkout / mjaganna 06/11/97 - Change message 02160 / mluong 05/27/97 - fix merge problem / anolan 05/14/97 - Demo. / jbellemo 04/11/97 - remove 2343 / jbellemo 04/08/97 - undo 2303, add types to 2344 / thajek 03/24/97 - del 2346, modify 2303, readd 2344 / rjenkins 03/18/97 - changing 2256 / usundara 01/03/97 - add error 2311 for bug 434240 / usundara 12/31/96 - incomplete and mutually-dependent types (add ora-4055) / bcchang 12/20/96 - error.msg split / / 2100 .. 2139 - Reserved for precompiler runtime (SQLLIB) / ORA-02100, 00000, "PCC: out of memory (i.e., could not allocate)" ORA-02101, 00000, "PCC: inconsistent cursor cache (uce/cuc mismatch)" ORA-02102, 00000, "PCC: inconsistent cursor cache (no cuc entry for this uce)" ORA-02103, 00000, "PCC: inconsistent cursor cache (out-of-range cuc ref)" ORA-02104, 00000, "PCC: inconsistent host cache (no cuc available)" ORA-02105, 00000, "PCC: inconsistent cursor cache (no cuc entry in cache)" ORA-02106, 00000, "PCC: inconsistent cursor cache (OraCursor nr is bad)" ORA-02107, 00000, "PCC: this pgm too old for run-time library: please re-PCC it" ORA-02108, 00000, "PCC: invalid descriptor passed to run-time library" ORA-02109, 00000, "PCC: inconsistent host cache (out-of-range sit ref)" ORA-02110, 00000, "PCC: inconsistent host cache (invalid sqi type)" ORA-02111, 00000, "PCC: heap consistency error" ORA-02112, 00000, "PCC: SELECT..INTO returns too many rows" / / 2140 .. 2499 - V6 parser errors continued / parser errors continued at 25000 / ORA-02140, 00000, "invalid tablespace name" Cause: An identifier does not follow ALTER TABLESPACE. Action: Specify a tablespace name following ALTER TABLESPACE. ORA-02141, 00000, "invalid OFFLINE option" Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE. Action: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE. ORA-02142, 00000, "missing or invalid ALTER TABLESPACE option" Cause: A valid option is not present. Action: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, and end. ORA-02143, 00000, "invalid STORAGE option" Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause. Action: Specify only valid options. ORA-02144, 00000, "no option specified for ALTER CLUSTER" Cause: No ALTER CLUSTER options are specified. Action: Specify one or more of the following options: pctfree, pctused, size, storage. ORA-02145, 00000, "missing STORAGE option" Cause: No STORAGE options were specified following STORAGE ( Action: Specify one or more STORAGE option between the parentheses. ORA-02146, 00000, "SHARED specified multiple times" Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times. Action: Only specify the SHARED option once. ORA-02147, 00000, "conflicting SHARED/EXCLUSIVE options" Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement. Action: Specify SHARED or EXCLUSIVE, but not both. ORA-02148, 00000, "EXCLUSIVE specified multiple times" Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times. Action: Only specify the EXCLUSIVE option once. ORA-02149, 00000, "Specified partition does not exist" Cause: Partition not found for the object. Action: Retry with correct partition name. ORA-02153, 00000, "invalid VALUES password string" Cause: An encoded password string does not follow the VALUES clause. Action: Place a proper encoded password string after the VALUES clause. ORA-02155, 00000, "invalid DEFAULT tablespace identifier" Cause: An identifier does not follow DEFAULT TABLESPACE. Action: Place a tablespace name after DEFAULT TABLESPACE. ORA-02156, 00000, "invalid TEMPORARY tablespace identifier" Cause: An identifier does not follow TEMPORARY TABLESPACE. Action: Place a tablespace name after TEMPORARY TABLESPACE. ORA-02157, 00000, "no options specified for ALTER USER" Cause: No options were specified. Action: Specify at least one ALTER USER option. ORA-02158, 00000, "invalid CREATE INDEX option" Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified. Action: Choose one of the valid CREATE INDEX options. ORA-02159, 00000, "installed DLM does not support releasable locking mode" Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available. Action: Specify configuration parameters that do not require the additional function. ORA-02160, 00000, "index-organized table can not contain columns of type LONG" Cause: A column of type LONG defined for index-organized table. Action: Do not use columns of type LONG in index-organized tables. ORA-02161, 00000, "invalid value for MAXLOGFILES" Cause: A number does not follow MAXLOGFILES. Action: Specify a number after MAXLOGFILES. ORA-02162, 00000, "invalid value for MAXDATAFILES" Cause: A number does not follow MAXDATAFILES. Action: Specify a number after MAXDATAFILES. ORA-02163, 00000, "invalid value for FREELIST GROUPS" Cause: A number does not follow FREELIST GROUPS. Action: Specify a number after FREELIST GROUPS. ORA-02164, 00000, "DATAFILE clause specified more than once" Cause: The CREATE DATABASE command contains more than one DATAFILE clause. Action: Specify at most one DATAFILE clause. ORA-02165, 00000, "invalid option for CREATE DATABASE" Cause: An invalid CREATE DATABASE option is present. Action: Specify only valid CREATE DATABASE options. ORA-02166, 00000, "ARCHIVELOG and NOARCHIVELOG specified" Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement. Action: Specify at most one of these two options. ORA-02167, 00000, "LOGFILE clause specified more than once" Cause: The CREATE DATABASE command contains more than one LOGFILE clause. Action: Specify at most one LOGFILE clause. ORA-02168, 00000, "invalid value for FREELISTS" Cause: A number does not follow FREELISTS Action: Specify a number after FREELISTS ORA-02169, 00000, "FREELISTS storage option not allowed" Cause: The user attempted to specify the FREELISTS storage option. This option may only be specified during create table or create index. Action: Remove these options and retry the statement. ORA-02170, 00000, "FREELIST GROUPS storage option not allowed" Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified. Action: Remove this option and retry the statement or set the allow_freelist_groups INIT.ORA parameter. ORA-02171, 00000, "invalid value for MAXLOGHISTORY" Cause: A number does not follow MAXLOGHISTORY Action: Specify a number after MAXLOGHISTORY ORA-02172, 00000, "The PUBLIC keyword is not appropriate for a disable thread" Cause: The PUBLIC keyword was specified for a disable. Action: Remove the keyword and resubmit. ORA-02173, 00000, "invalid option for DROP TABLESPACE" Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS. Action: Place nothing or only INCLUDING CONTENTS after the tablespace name. ORA-02174, 00000, "Missing required thread number" Cause: Must specify thread number after THREAD keyword Action: ORA-02175, 00000, "invalid rollback segment name" Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT. Action: Place the segment name following ROLLBACK SEGMENT. ORA-02176, 00000, "invalid option for CREATE ROLLBACK SEGMENT" Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. Action: Specify one of the valid options: TABLESPACE and STORAGE. ORA-02177, 00000, "Missing required group number" Cause: Must specify group number after GROUP keyword Action: ORA-02178, 00000, "correct syntax is: SET TRANSACTION READ { ONLY | WRITE }" Cause: There is a syntax error in the user's statement. Action: Correct the syntax as indicated. ORA-02179, 00000, "valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }" Cause: There is a syntax error in the user's statement. Action: Correct the syntax as indicated. ORA-02180, 00000, "invalid option for CREATE TABLESPACE" Cause: An invalid option appears. Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE. ORA-02181, 00000, "invalid option to ROLLBACK WORK" Cause: A token other than TO follows ROLLBACK [WORK]. Action: Place nothing or TO SAVEPOINT after ROLLBACK [WORK]. ORA-02182, 00000, "savepoint name expected" Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. Action: Place a savepoint name following TO [SAVEPOINT]. ORA-02183, 00000, "valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }" Cause: There is a syntax error in the user's statement. Action: Correct the syntax as indicated. ORA-02184, 00000, "resource quotas are not allowed in REVOKE" Cause: In a revoke statement, a resource quota was specified. Action: Specify resource privilege without the quota. ORA-02185, 00000, "a token other than WORK follows COMMIT" Cause: A token other than WORK follows COMMIT. Action: Place either nothing or WORK after COMMIT. ORA-02186, 00000, "tablespace resource privilege may not appear with other privileges" Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked. Action: Use a separate grant or revoke statement for the resource quota privilege. ORA-02187, 00000, "invalid quota specification" Cause: In a grant or revoke statement, the user attempted to grant a tablespace quota above the upper limit. Action: Grant a smaller tablespace quota. ORA-02189, 00000, "ON required" Cause: In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON clause. Action: Specify the tablespace on which the quota is to be applied with the ON clause. ORA-02190, 00000, "keyword TABLES expected" Cause: The keyword TABLES is expected following DROP CLUSTER INCLUDING. Action: Place TABLES after INCLUDING. ORA-02191, 00000, "correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT" Cause: There is a syntax error in the user's statement. Action: Correct the syntax as indicated. ORA-02192, 00000, "PCTINCREASE not allowed for rollback segment storage clauses" Cause: pctincrease was specified in a create or alter rollback segment Action: reissue statement without the pctincrease clause ORA-02194, 00000, "event specification syntax error %s (minor error %s) near '%s'" Cause: There is a syntax error in an event specification. Action: Fix the error. ORA-02195, 00000, "Attempt to create %s object in a %s tablespace" Cause: The object type is inconsistent with a tablespace contents. Action: Create an object in a different tablespace, or change the user defaults. ORA-02196, 00000, "PERMANENT/TEMPORARY option already specified" Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once. ORA-02197, 00000, "file list already specified" Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified. Action: Merge the DATAFILE/TEMPFILE clauses into a single clause. ORA-02198, 00000, "ONLINE/OFFLINE option already specified" Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once. Action: Specify at most one of ONLINE or OFFLINE. ORA-02199, 00000, "missing DATAFILE/TEMPFILE clause" Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause. Action: Specify a DATAFILE/TEMPFILE clause. ORA-02200, 00000, "WITH GRANT OPTION not allowed for PUBLIC" Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION. Action: Remove the WITH GRANT OPTION clause. ORA-02201, 00000, "sequence not allowed here" Cause: An attempt was made to reference a sequence in a from-list. Action: A sequence can only be referenced in a select-list. ORA-02202, 00000, "no more tables permitted in this cluster" Cause: An attempt was made to create a table in a cluster which already contains 32 tables. Action: Up to 32 tables may be stored per cluster. ORA-02203, 00000, "INITIAL storage options not allowed" Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created. Action: Remove these options and retry the statement. ORA-02204, 00000, "ALTER, INDEX and EXECUTE not allowed for views" Cause: An attempt was made to grant or revoke an invalid privilege on a view. Action: Do not attempt to grant or revoke any of ALTER, INDEX, or EXECUTE privileges on views. ORA-02205, 00000, "only SELECT and ALTER privileges are valid for sequences" Cause: An attempt was made to grant or revoke an invalid privilege on a sequence. Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES or EXECUTE privilege on sequences. ORA-02206, 00000, "duplicate INITRANS option specification" Cause: INITRANS is specified more than once. Action: Specify INITRANS at most once. ORA-02207, 00000, "invalid INITRANS option value" Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value. Action: Choose a valid INITRANS value. ORA-02208, 00000, "duplicate MAXTRANS option specification" Cause: MAXTRANS is specified more than once. Action: Specify MAXTRANS at most once. ORA-02209, 00000, "invalid MAXTRANS option value" Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value. Action: Choose a valid MAXTRANS value. ORA-02210, 00000, "no options specified for ALTER TABLE" Cause: No ALTER TABLE option was specified. Action: Specify at least one alter table option. ORA-02211, 00000, "invalid value for PCTFREE or PCTUSED" Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100. Action: Choose an appropriate value for the option. ORA-02212, 00000, "duplicate PCTFREE option specification" Cause: PCTFREE option specified more than once. Action: Specify PCTFREE at most once. ORA-02213, 00000, "duplicate PCTUSED option specification" Cause: PCTUSED option specified more than once. Action: Specify PCTUSED at most once. ORA-02214, 00000, "duplicate BACKUP option specification" Cause: The BACKUP option to ALTER TABLE is specified more than once. Action: Specify the option at most once. ORA-02215, 00000, "duplicate tablespace name clause" Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement. Action: Specify at most one TABLESPACE clause. ORA-02216, 00000, "tablespace name expected" Cause: A tablespace name is not present where required by the syntax for one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT. Action: Specify a tablespace name where required by the syntax. ORA-02217, 00000, "duplicate storage option specification" Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once. Action: Specify all storage options at most once. ORA-02218, 00000, "invalid INITIAL storage option value" Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02219, 00000, "invalid NEXT storage option value" Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02220, 00000, "invalid MINEXTENTS storage option value" Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS. Action: Specify an appropriate value. ORA-02221, 00000, "invalid MAXEXTENTS storage option value" Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS. Action: Specify an appropriate value. ORA-02222, 00000, "invalid PCTINCREASE storage option value" Cause: The specified value must be a positive integer. Action: Specify an appropriate value. ORA-02223, 00000, "invalid OPTIMAL storage option value" Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02224, 00000, "EXECUTE privilege not allowed for tables" Cause: An attempt was made to grant or revoke an invalid privilege on a table. Action: Do not attempt to grant or revoke EXECUTE privilege on tables. ORA-02225, 00000, "only EXECUTE and DEBUG privileges are valid for procedures" Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function or package. Action: Do not attempt to grant or revoke any privilege besides EXECUTE or DEBUG on procedures, functions or packages. ORA-02226, 00000, "invalid MAXEXTENTS value (max allowed: %s)" Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment. Action: Specify a smaller value. ORA-02227, 00000, "invalid cluster name" Cause: A cluster name of the form [ . ] is expected but not present. Action: Enter an appropriate cluster name. ORA-02228, 00000, "duplicate SIZE specification" Cause: The SIZE option is specified more than once. Action: Specify the SIZE option at most once. ORA-02229, 00000, "invalid SIZE option value" Cause: The specified value must be an integer number of bytes. Action: Specify an appropriate value. ORA-02230, 00000, "invalid ALTER CLUSTER option" Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement. Action: Specify only legal options. ORA-02231, 00000, "missing or invalid option to ALTER DATABASE" Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement. Action: Specify only legal options. ORA-02232, 00000, "invalid MOUNT mode" Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement. Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT. ORA-02233, 00000, "invalid CLOSE mode" Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement. Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE. ORA-02234, 00000, "changes to this table are already logged" MERGE: 2292 RENUMBERED TO 2234 Cause: the log table to be added is a duplicate of another Action: Don't add this change log to the system; check that the replication product's system tables are consistent ORA-02235, 00000, "this table logs changes to another table already" MERGE: 2293 RENUMBERED TO 2235 Cause: the table to be altered is already a change log for another table Action: Don't log changes to the specified base table to this table; check that the replication product's system tables are consistent ORA-02236, 00000, "invalid file name" Cause: A character string literal was not used in the filename list of a LOGFILE, DATAFILE, or RENAME clause. Action: Use correct syntax. ORA-02237, 00000, "invalid file size" Cause: A non-integer value was specified in the SIZE or RESIZE clause. Action: Use correct syntax. ORA-02238, 00000, "filename lists have different numbers of files" Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the the number of existing filenames does not equal the number of new filenames. Action: Make sure there is a new filename to correspond to each existing filename. ORA-02239, 00000, "there are objects which reference this sequence" MERGE: 2290 RENUMBERED TO 2239 Cause: the sequence to be dropped is still referenced Action: Make sure the sequence name is correct, or drop the referencing constraint/object ORA-02240, 00000, "invalid value for OBJNO or TABNO" Cause: A number does not follow either OBJNO or TABNO. Action: Specify a number after OBJNO or TABNO. ORA-02241, 00000, "must of form EXTENTS (FILE BLOCK SIZE, ...)" Cause: bad extent storage clause Action: respecify ORA-02242, 00000, "no options specified for ALTER INDEX" Cause: No options specified. Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. ORA-02243, 00000, "invalid ALTER INDEX or ALTER MATERIALIZED VIEW option" Cause: An option other than INITRANS, MAXTRANS,or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER MATERIALIZED VIEW statement. Action: Specify only legal options. ORA-02244, 00000, "invalid ALTER ROLLBACK SEGMENT option" Cause: The STORAGE option is expected but not found. Action: Specify the STORAGE option. ORA-02245, 00000, "invalid ROLLBACK SEGMENT name" Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT. Action: Place a rollback segment name following SEGMENT. ORA-02246, 00000, "missing EVENTS text" Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS. Action: Place the string literal containing the events text after EVENTS. ORA-02247, 00000, "no option specified for ALTER SESSION" Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION. Action: Place the SET EVENTS option after ALTER SESSION. ORA-02248, 00000, "invalid option for ALTER SESSION" Cause: Obvious. Action: see SQL Language Manual for legal options. ORA-02249, 00000, "missing or invalid value for MAXLOGMEMBERS" Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members. Action: Specify a valid number after MAXLOGMEMBERS. ORA-02250, 00000, "missing or invalid constraint name" Cause: The constraint name is missing or invalid. Action: Specify a valid identifier name for the constraint name. ORA-02251, 00000, "subquery not allowed here" Cause: Subquery is not allowed here in the statement. Action: Remove the subquery from the statement. ORA-02252, 00000, "check constraint condition not properly ended" Cause: The specified search condition for the check constraint is not properly ended. Action: End the condition properly. ORA-02253, 00000, "constraint specification not allowed here" Cause: Constraint specification is not allowed here in the statement. Action: Remove the constraint specification from the statement. ORA-02254, 00000, "DEFAULT not allowed here" Cause: Default value expression is not allowed for the column here in the statement. Action: Remove the default value expression from the statement. ORA-02255, 00000, "obsolete 7.1.5" Cause: Was that defaults must not conflict with not null constraints Action: ORA-02256, 00000, "number of referencing columns must match referenced columns" Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list. Action: Make sure that the referencing columns match the referenced columns. ORA-02257, 00000, "maximum number of columns exceeded" Cause: The number of columns in the key list exceeds the maximum number. Action: Reduce the number columns in the list. ORA-02258, 00000, "duplicate or conflicting NULL and/or NOT NULL specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02259, 00000, "duplicate UNIQUE/PRIMARY KEY specifications" Cause: Self-evident. Action: Remove the duplicate specification. ORA-02260, 00000, "table can have only one primary key" Cause: Self-evident. Action: Remove the extra primary key. ORA-02261, 00000, "such unique or primary key already exists in the table" Cause: Self-evident. Action: Remove the extra key. ORA-02262, 00000, "ORA-%s occurs while type-checking column default value expression" Cause: New column datatype causes type-checking error for existing column default value expression. Action: Remove the default value expression or don't alter the column datatype. ORA-02263, 00000, "need to specify the datatype for this column" Cause: The required datatype for the column is missing. Action: Specify the required datatype. ORA-02264, 00000, "name already used by an existing constraint" Cause: The specified constraint name has to be unique. Action: Specify a unique constraint name for the constraint. ORA-02265, 00000, "cannot derive the datatype of the referencing column" Cause: The datatype of the referenced column is not defined as yet. Action: Make sure that the datatype of the referenced column is defined before referencing it. ORA-02266, 00000, "unique/primary keys in table referenced by enabled foreign keys" Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION. Action: Before performing the above operations the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; ORA-02267, 00000, "column type incompatible with referenced column type" Cause: The datatype of the referencing column is incompatible with the / datatype of the referenced column. Action: Select a compatible datatype for the referencing column. ORA-02268, 00000, "referenced table does not have a primary key" Cause: The referenced table does not have a primary key. Action: Specify explicitly the referenced table unique key. ORA-02269, 00000, "key column cannot be of LONG datatype" Cause: Self-evident. Action: Change the datatype of the column, or remove the column from the key. ORA-02270, 00000, "no matching unique or primary key for this column-list" Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table. Action: Find the correct column names using the ALL_CONS_COLUMNS catalog view ORA-02271, 00000, "table does not have such constraint" Cause: Self-evident. Action: Make sure the specified constraint name is correct. ORA-02272, 00000, "constrained column cannot be of LONG datatype" Cause: Self-evident. Action: Change the datatype of the column, or remove the constraint on the column. ORA-02273, 00000, "this unique/primary key is referenced by some foreign keys" Cause: Self-evident. Action: Remove all references to the key before the key is to be dropped. ORA-02274, 00000, "duplicate referential constraint specifications" Cause: Self-evident. Action: Remove the duplicate specification. ORA-02275, 00000, "such a referential constraint already exists in the table" Cause: Self-evident. Action: Remove the extra constraint. ORA-02276, 00000, "default value type incompatible with column type" Cause: The type of the evaluated default expression is incompatible with the datatype of the column. Action: Change the type of the column, or modify the default expression. ORA-02277, 00000, "invalid sequence name" Cause: The specified sequence name is not a valid identifier name. Action: Specify a valid identifier name for the sequence name. ORA-02278, 00000, "duplicate or conflicting MAXVALUE/NOMAXVALUE specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02279, 00000, "duplicate or conflicting MINVALUE/NOMINVALUE specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02280, 00000, "duplicate or conflicting CYCLE/NOCYCLE specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02281, 00000, "duplicate or conflicting CACHE/NOCACHE specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02282, 00000, "duplicate or conflicting ORDER/NOORDER specifications" Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02283, 00000, "cannot alter starting sequence number" Cause: Self-evident. Action: Don't alter it. ORA-02284, 00000, "duplicate INCREMENT BY specifications" Cause: Self-evident. Action: Remove the duplicate specification. ORA-02285, 00000, "duplicate START WITH specifications" Cause: Self-evident. Action: Remove the duplicate specification. ORA-02286, 00000, "no options specified for ALTER SEQUENCE" Cause: Self-evident. Action: The statement is meaningless without any options. ORA-02287, 00000, "sequence number not allowed here" Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate here in the statement. Action: Remove the sequence number. ORA-02288, 00000, "invalid OPEN mode" Cause: A token other than RESETLOGS appears following ALTER DATABASE OPEN. Action: Either nothing or RESETLOGS should be placed following OPEN. ORA-02289, 00000, "sequence does not exist" Cause: The specified sequence does not exist, or the user does not have the required privilege to perform this operation. Action: Make sure the sequence name is correct, and that you have the right to perform the desired operation on this sequence. ORA-02290, 00000, "check constraint (%s.%s) violated" Cause: The values being inserted do not satisfy the named check constraint. Action: do not insert values that violate the constraint. ORA-02291, 00000,"integrity constraint (%s.%s) violated - parent key not found" Cause: A foreign key value has no matching primary key value. Action: Delete the foreign key or add a matching primary key. ORA-02292, 00000,"integrity constraint (%s.%s) violated - child record found" Cause: attempted to delete a parent key value that had a foreign key dependency. Action: delete dependencies first then parent or disable constraint. ORA-02293, 00000,"cannot validate (%s.%s) - check constraint violated" Cause: an alter table operation tried to validate a check constraint to a populated table that had nocomplying values. Action: Obvious ORA-02294, 00000,"cannot enable (%s.%s) - constraint changed during validation" Cause: While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint. Action: Try again, with only one DDL changing the constraint this time. ORA-02295, 00000,"found more than one enable/disable clause for constraint" Cause: a create or alter table specified more than one enable and/or disable clause for a given constraint. Action: only one enable or disable may be specified for a given constraint. ORA-02296, 00000,"cannot enable (%s.%s) - null values found" Cause: an alter table enable constraint failed because the table contains values that do not satisfy the constraint. Action: Obvious ORA-02297, 00000,"cannot disable constraint (%s.%s) - dependencies exist" Cause: an alter table disable constraint failed becuase the table has foriegn keys that are dpendent on this constraint. Action: Either disable the foreign key constraints or use disable cascade ORA-02298, 00000,"cannot validate (%s.%s) - parent keys not found" Cause: an alter table validating constraint failed because the table has orphaned child records. Action: Obvious ORA-02299, 00000,"cannot validate (%s.%s) - duplicate keys found" Cause: an alter table validating constraint failed because the table has duplicate key values. Action: Obvious / / / 2300 - 2350 Object extensions to SQL / - 2310 - 2319 - Object columns and Object Tables / - 2320 - 2329 - Nested Table columns / ORA-02300, 00000, "invalid value for OIDGENERATORS" Cause: A number was not specified for the value of OIDGENERATORS. Action: Specify a number for OIDGENERATORS. ORA-02301, 00000, "maximum number of OIDGENERATORS is 255" Cause: A number greater than 255 was specified for the value of OIDGENERATORS. Action: Make sure the number specified for OIDGENERATORS does not exceed 255. ORA-02302, 00000, "invalid or missing type name" Cause: An invalid or missing type name was entered in a statement. Action: Enter a valid type name in the statement and retry the operation. ORA-02303, 00000, "cannot drop or replace a type with type or table dependents" Cause: An attempt was made to drop or replace a type that has dependents. There could be a substitutable column of a supertype of the type being dropped. Action: Drop all type(s) and table(s) depending on the type, then retry the operation using the VALIDATE option, or use the FORCE option. ORA-02304, 00000, "invalid object identifier literal" Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either: - not a string of 32 hexadecimal characters - an object identifier that already identifies an existing object - an object identifier different from the original object identifier already assigned to the type Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation. ORA-02305, 00000, "only EXECUTE, DEBUG, and UNDER privileges are valid for types" Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE, DEBUG, or UNDER) on a type. Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on types. ORA-02306, 00000, "cannot create a type that already has valid dependent(s)" Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist). Action: Drop the dependents first before creating the type, or do not create the type. ORA-02307, 00000, "cannot alter with REPLACE option a type that is not valid" Cause: An attempt was made to ALTER with REPLACE option a type that is not valid. Action: Use the CREATE OR REPLACE TYPE command to modify the type. ORA-02308, 00000, "invalid option %s for object type column" Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column. Action: Remove the invalid option from column specification and retry the operation. ORA-02309, 00000, "atomic NULL violation" Cause: An attempt was made to acess the attributes of a NULL object instance. Action: Ensure that the object instance is non-NULL before accessing. ORA-02310, 00000, "exceeded maximum number of allowable columns in table" Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table. Action: Specify fewer attributes for the object type and retry the operation. ORA-02311, 00000, "cannot alter with COMPILE option a valid type with type or table dependents" Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents. Action: No need to perform this operation. 02312, 00000, "cannot create extent table for VALUE ADT" Cause: attempt to create extent table for VALUE ADT. Action: specify object type when creating extent table. ORA-02313, 00000, "object type contains non-queryable type %s attribute" Cause: The specified object type contains a nested attribute whose type is non-queryable. Action: Use an object type with queryable attribute types. 02314, 00000, "cannot create index on object type column or attribute" Cause: An attempt was made to create an index on an object type column. Cause: attempt to create an index on an object type column Action: index can only be created on simple, scalar columns or attributes. ORA-02315, 00000, "incorrect number of arguments for default constructor" Cause: The number of arguments specified for the default constructor doesn't match the number of attributes of the object type. Action: Specify the correct number of arguments for the default constructor and retry the operation. 02316, 00000, "incorrect number of attributes in object type column" Cause: number of attributes in object type operand doesn't match number of attributes in object type column to be updated. Action: ensure both object type attributes match. 02317, 00000, "invalid operation for object type operands" Cause: specified an invalid operation on object type operands Action: ensure correct operation to be performed on object type operands. 02318, 00000, "invalid REF function on non-object table" Cause: specified REF operator is invalid on a non-object table Action: REF operator can only be specified on an object table. 02319, 00000, "invalid column argument to REF operator" Cause: specified an invalid REF column argument Action: argument to REF operator can only be the object type column of the object table. Action: The argument to a REF operator can only be the object type column of the object table. ORA-02320, 00000, "failure in creating storage table for nested table column %s" Cause: An error occurred while creating the storage table for the specified nested table column. Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support. 02321, 00000, "object type's default constructor expected" Cause: Action: specify an ADT default constructor. ORA-02322, 00000, "failure in accessing storage table of the nested table column" Cause: An error occured while performing DML on the storage table of the nested table column. Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support. 02323, 00000, "fail in %s inner table for column %s" Cause: An error occured while performing DML on the nested table column. Cause: an error occurs while performing DML on the nested table column. Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. ORA-02324, 00000, "more than one column in the SELECT list of THE subquery" Cause: More than one column was selected in the THE subquery. Action: Specify only one column in the SELECT list of the THE subquery and retry the operation. 02325, 00000, "zero rows returned by THE subquery" Cause: THE subquery evaluation returns no rows whereas it is supposed to return a single row. Action: change subquery within THE operator to return exactly one row. 02326, 00000, "missing THE keyword" Cause: subquery used to return an inner nested table is enclosed by THE operator Action: Put THE operator around the subquery, e.g. THE(subquery). ORA-02327, 00000, "cannot create index on expression with datatype %s" Cause: An attempt was made to create an index on a non-indexable expression. Action: Change the column datatype or do not create the index on an expression whose datatype is one of VARRAY, nested table, object, LOB, or REF. 02328, 00000, "REF column cannot be specified on VALUE ADT" Cause: attempt to create REF column of VALUE ADT Action: remove REF specifier from column specification ORA-02329, 00000, "column of datatype %s cannot be unique or a primary key" Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF. Action: Change the column datatype or remove the constraint. Then retry the operation. ORA-02330, 00000, "datatype specification not allowed" Cause: An attempt was made to specify the data type in the column constraint specification of an object table. Action: Remove data type specification and retry the operation. ORA-02331, 00000, "cannot create constraint on column of datatype %s" Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF. Action: Change the column datatype, or remove the constraint. ORA-02332, 00000, "cannot create index on attributes of this column" Cause: An attempt was made to create an index on an attributes of an object type column. Action: Do not specify the index on the attribute. ORA-02333, 00000, "cannot create constraints on attributes of this column" Cause: An attempt was made to create a constraint on an attribute of an object type column. Action: Remove the constraint or change the object type. ORA-02334, 00000, "cannot infer type for column" Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column. Action: Declare a datatype for the column. ORA-02335, 00000, "invalid datatype for cluster column" Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE. Action: Remove the CLUSTER column or change the datatype of the column. ORA-02336, 00000, "column attribute cannot be accessed" Cause: An attempt was made to extract an attribute of an object type column. Action: Change the object type for the column and retry the operation. ORA-02337, 00000, "not an object type column" Cause: An attempt was made to use dotted notation on a non-ADT column; that is, "a.b.c" where "a" is not an object type. Action: Either change the column type to an object type or do not perform this operation. ORA-02338, 00000, "missing or invalid column constraint specification" Cause: A column constraint was not specified. Action: Remove the column specification or specify a column constraint. Then retry the operation. ORA-02339, 00000, "invalid column specification" Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column. Action: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation. ORA-02340, 00000, "invalid column specification" Cause: An attempt was made to specify an UNPACKED column within a packed table. Action: Remove the UNPACKED keyword in the column specification. 02341, 00000, "cannot refer to non-queryable type %s in SQL" Cause: attempt to refer to an object type attribute that is of a non-queryable type in SQL Action: change attribute type to a SQL-queryable type, or reference the attribute through a 3GL ORA-02342, 00000, "replacement type has compilation errors" Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error. Action: Use the ALTER...REPLACE statement to replace the type with a valid type which does not cause compilation errors. ORA-02344, 00000, "cannot revoke execute on a type with table dependents" Cause: An attempt was made to revoke execute on a type that has dependents. Action: Drop all table(s) depending on the type, then retry the operation, or use the FORCE option. ORA-02345, 00000, "cannot create a view with column based on CURSOR operator" Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. Action: Remove the CURSOR operator and replace it with the CAST operator. ORA-02347, 00000, "cannot grant privileges on columns of an object table" Cause: An attempt was made to grant privileges on the columns of an object table. Action: ORA-02348, 00000, "cannot create VARRAY column with embedded LOB" Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY's element. Action: Remove offending attribute from type. If it is a subtype attribute then declare the VARRAY column NOT SUBSTITUTABLE. ORA-02349, 00000, "invalid user-defined type - type is incomplete" Cause: An attempt was made to use an incomplete type definition as a column or table datatype. Action: Complete the type definition and retry the operation. 02350, 00000, "cannot insert into attributes of a packed typed table" Cause: specifying a column list in an insert statement Action: drop the column list specification statement. / / / / 2351 - 2375 Direct Loader errors / see also range 2476 - 2479 for Parallel Direct Loader errors / and range 26000 - 26999 for additional Direct Loader errors / ORA-02351, 00000, "Record %s: Rejected - Error on table %s, column %s" Cause: The record indicated caused an oracle error on insert. Action: Determine the oracle error and correct the record. ORA-02352, 00000, "Direct path connection must be homogeneous" Cause: The user-side to kernel-side connection is heterogenous. Action: In versions prior to 8.2, the connection must be between identical hardware and O/S's. Also, the SQL*Loader and RDBMS versions must be the same. ORA-02353, 00000, "Multibyte character error" Cause: Text specified by POSITION or terminated by newlines is invalid. Action: Edit the controlfile or the data file to fix alignment of column. ORA-02354, 00000, "Conversion initialization error occurred on field %s" Cause: An error occurred during conversion initialization for a field. Action: Internal error. Contact customer supprt. ORA-02355, 00000, "Conversion error occurred on CONSTANT field %s" Cause: A CONSTANT field caused an oracle error; all rows will be rejected. Action: Determine the oracle error and correct the record. ORA-02356, 00000, "The database is out of space. The load cannot continue" Cause: The load was discontinued due to space exhaustion in the database. Action: Add space for the specified table. ORA-02357, 00000, "Packed Decimal conversion error" Cause: The column could not be converted from packed decimal to character. Action: Check the column and make it conform to packed decimal format. ORA-02358, 00000, "Zoned Decimal conversion error" Cause: The column could not be converted from packed decimal to character. Action: Check the column and make it conform to packed decimal format. ORA-02359, 00000, "Field in data file exceeded maximum specified length" Cause: The field is too long for the specified column. Action: Shorten the field so that its length is =< the column length. ORA-02360, 00000, "Column not found before end of logical record (use TRAILING NULLCOLS)" Cause: A column started after the end of the logical record had been reached. Action: Use the TRAILING NULLCOLS option or supply data for the column. ORA-02361, 00000, "Initial enclosing character not found" Cause: The initial enclosing character of an enclosed field was not found. Action: Supply the character before the start of the field. ORA-02362, 00000, "Logical record ended - second enclosing character not present" Cause: The second enclosing character of an enclosed field was not found. Action: Supply the character after the end of the field. ORA-02363, 00000, "No terminator found after TERMINATED and ENCLOSED field" Cause: No terminator was found after a terminated and enclosed field. Action: Supply the character after the end of the field. ORA-02364, 00000, "Record %s: Discarded - failed all WHEN clauses" Cause: The record was not loaded because it failed all tables' WHEN clauses. Action: none. ORA-02365, 00000, "Index %s was made Index Unusable due to" Cause: The index was not loaded because of the error specified. Action: Correct the error, then reload. ORA-02366, 00000, "The following index(es) on table %s were processed:" Cause: The table had some indexes which were loaded if there were no errors. Action: none. ORA-02367, 00000, "Index %s was loaded." Cause: The index was loaded. Action: none. ORA-02368, 00000, "Record %s: Discarded - all columns null." Cause: The record was not loaded because all tables' columns were null. Action: none. ORA-02369, 00000, "Warning: Variable length field was truncated." Cause: A variable length field was truncated by the end of the logical record. Action: This is just a warning, but since a variable length field has the length embedded in the data for each row, you may want to check your data. ORA-02370, 00000, "Record %s - Warning on table %s, column %s" Cause: The record indicated caused an warning. Action: Determine the warning and correct the record if necessary. ORA-02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path" Cause: The loader being used is incompatible with this version of the kernel. Action: Upgrade your loader to at least the specified version or use the conventional path. ORA-02372, 00000, "Relative start position > absolute field end position." Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y. Action: Check that you are not missing a delimiter and that the values of n and y are correct. ORA-02373, 00000, "Error parsing insert statement for table %s." Cause: self-evident. Action: Check the error given below this one. ORA-02374, 00000, "No more slots for read buffer queue." Cause: There are no free read buffers. Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers. ORA-02375, 00000, "Record %s: Rejected - Error on table %s" Cause: The record indicated caused an ORACLE error on insert. Action: Determine the ORACLE error and correct the record. The offending column(s) are not known. / / 2376 - 2399 Resource limit errors / ORA-02376, 00000, "invalid or redundant resource" Cause: a create, or alter profile command which names a resource not yet defined, or try to specify same resource twice. Action: define resource first ORA-02377, 00000, "invalid resource limit" Cause: specifying limit of 0 Action: specify limit > 0 ORA-02378, 00000, "duplicate resource name %s" Cause: Action: ORA-02379, 00000, "profile %s already exists" Cause: Try to create a profile which already exist Action: ORA-02380, 00000, "profile %s does not exist" Cause: Try to assign a user to a non-existant profile Action: ORA-02381, 00000, "cannot drop PUBLIC_DEFAULT profile" Cause: Try to drop PUBLIC_DEFAULT profile Action: ORA-02382, 00000, "profile %s has users assigned, cannot drop without CASCADE" Cause: Action: ORA-02383, 00000, "illegal cost factor" Cause: Negative or UNLIMITED cost for this resourc Action: ORA-02390, 00000, "exceeded COMPOSITE_LIMIT, you are being logged off" Cause: Action: ORA-02391, 00000, "exceeded simultaneous SESSIONS_PER_USER limit" Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user prfile. Action: End one or more concurrent sessions or ask the database administrator to increase the SESSION_PER_USER limit of the user profile. ORA-02392, 00000, "exceeded session limit on CPU usage, you are being logged off" Cause: Action: ORA-02393, 00000, "exceeded call limit on CPU usage" Cause: Action: ORA-02394, 00000, "exceeded session limit on IO usage, you are being logged off" Cause: Action: ORA-02395, 00000, "exceeded call limit on IO usage" Cause: Action: ORA-02396, 00000, "exceeded maximum idle time, please connect again" Cause: as stated Action: ORA-02397, 00000, "exceeded PRIVATE_SGA limit, you are being logged off" Cause: Only when using TP monitor Action: expand limit ORA-02398, 00000, "exceeded procedure space usage" Cause: Stored procedured used up too much space in SYSTEM Tablespace Action: Use less stored procedure ORA-02399, 00000, "exceeded maximum connect time, you are being logged off" Cause: As stated Action: / / 2400 - 2479 EXPLAIN facility errors / ORA-02401, 00000, "cannot EXPLAIN view owned by another user" Cause: The view specified in the SQL statement belongs to another user and cannot be explained. Action: Create a view with the same definition that belongs to current user. ORA-02402, 00000, "PLAN_TABLE not found" Cause: The table used by EXPLAIN to store row source information does not exist in the current schema. Action: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command in an existing plan table. ORA-02403, 00000, "plan table does not have correct format" Cause: The explicit plan table does not have the appropriate field definitions. Action: Redefine the plan table to have the appropriate field definitions. ORA-02404, 00000, "specified plan table not found" Cause: The specified plan table does cannot be found. Action: Create the specified plan table or use an existing plan table. / / 2420 - 2429 Schema errors / ORA-02420, 00000, "missing schema authorization clause" Cause: the AUTHORIZATION clause is missing from a create schema statement. Action: Preceed the schema authorization identifier with the AUTHORIZATION keyword. ORA-02421, 00000, "missing or invalid schema authorization identifier" Cause: the schema name is missing or is incorrect in an authorization clause of a create schema statement. Action: If the name is present, it must be the same as the current schema. ORA-02422, 00000, "missing or invalid schema element" Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement. Action: Self-evident. ORA-02423, 00000, "schema name does not match schema authorization identifier" Cause: a table definition with a schema name prepended to the table name does not match the schema name provided in the authorization clause of a create schema statement. Action: make sure the schema names match. ORA-02424, 00000, "potential circular view references or unknown referenced tables" Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables. Action: create the dependent views in a separate create schema statement and make sure all referenced tables are either defined in the create schema statement or exist outside the statement. ORA-02425, 00000, "create table failed" Cause: a create table statement failed in the create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02426, 00000, "privilege grant failed" Cause: a grant privilege statement failed inthe create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02427, 00000, "create view failed" Cause: a create view statement failed in the create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02428, 00000, "could not add foreign key reference" Cause: could not add a foreign key reference because of error in declaration. Either referenced table does not exist or table does not have an unique key. Action: make sure referenced table exists and/or has unique key ORA-02429, 00000, "cannot drop index used for enforcement of unique/primary key" Cause: user attempted to drop an index that is being used as the enforcement mechanism for unique or primary key. Action: drop the constraint instead of the index. / / 2430 - Enable/Disable Constraint Error Messages - continued / ORA-02430, 00000, "cannot enable constraint (%s) - no such constraint" Cause: the named constraint does not exist for this table. Action: Obvious ORA-02431, 00000, "cannot disable constraint (%s) - no such constraint" Cause: the named constraint does not exist for this table. Action: Obvious ORA-02432, 00000, "cannot enable primary key - primary key not defined for table" Cause: Attempted to enable a primary key that is not defined for the table. Action: Need to add a primary key definition for the table. ORA-02433, 00000, "cannot disable primary key - primary key not defined for table" Cause: Attempted to disable a primary key tht is not defined for the table. Action: None ORA-02434, 00000, "cannot enable unique(%s) - unique key not defined for table" Cause: attempted to enable a unique key that is not defined for the table. Action: None ORA-02435, 00000, "cannot disable unique(%s) - unique key not defined for table" Cause: attempted to disable a unique key that is not deined for the table. Action: None ORA-02436, 00000, "date or system variable wrongly specified in CHECK constraint" Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century. Action: Completely specify the date constant or system variable. Setting the event 10149 allows constraints like "a1 > '10-MAY-96'", which a bug permitted to be created before version 8. ORA-02437, 00000, "cannot validate (%s.%s) - primary key violated" Cause: attempted to validate a primary key with duplicate values or null values. Action: remove the duplicates and null values before enabling a primary key. ORA-02438, 00000, "Column check constraint cannot reference other columns" Cause: attempted to define a column check constraint that references another column. Action: define it as a table check constriant. ORA-02439, 00000, "Unique index on a deferrable constraint is not allowed" Cause: attempted to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns. Action: Drop the index on the constraint columns or make the constraint not deferrable. ORA-02440, 00000, "Create as select with referential constraints not allowed" Cause: create table foo (... ref. con. ...) as select ...; Action: Create the table as select, then alter the table to add the constraints afterwards. ORA-02441, 00000, "Cannot drop nonexistent primary key" Cause: alter table drop primary key - primary key does not exist. Action: None ORA-02442, 00000, "Cannot drop nonexistent unique key" Cause: alter table drop unique () - unique specification does not exist. Action: make sure column list for unique constraint is correct. ORA-02443, 00000, "Cannot drop constraint - nonexistent constraint" Cause: alter table drop constraint <constraint_name> Action: make sure you supply correct constraint name. ORA-02444, 00000, "Cannot resolve referenced object in referential constraints" Cause: attempted to define foreign key referencing an object which cannot be resolved to a base table reference Action: referential constraints can only be defined on objects which can be resolve to base table reference ORA-02445, 00000, "Exceptions table not found" Cause: the explicity or implicity declared exceptions table does not exist. Action: Create the table then issue the enable command again. ORA-02446, 00000, "CREATE TABLE ... AS SELECT failed - check constraint violated" Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints. Action: Do not select rows that violate constraints. ORA-02447, 00000, "cannot defer a constraint that is not deferrable" Cause: An attempt was made to defer a nondeferrable constraint Action: Drop the constraint and create a new one that is deferrable ORA-02448, 00000, "constraint does not exist" Cause: The named constraint does not exist Action: Stop trying to do something with a nonexistant constraint ORA-02449, 00000, "unique/primary keys in table referenced by foreign keys" Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table. Action: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; / / 2450 - 2475 Parse and execution errors for hashed clusters / ORA-02450, 00000, "Invalid hash option - missing keyword IS" Cause: Missing IS keyword. Action: Specify HASH IS option. ORA-02451, 00000, "duplicate HASHKEYS specification" Cause: The HASHKEYS option is specified more than once. Action: Only specify the HASHKEYS option once. ORA-02452, 00000, "invalid HASHKEYS option value" Cause: The specified HASHKEYS option must be an integer value. Action: Specify an appropriate value. ORA-02453, 00000, "duplicate HASH IS specification" Cause: The HASH IS option is specified more than once. Action: only specify the HASH IS option once. ORA-02454, 00000, "Number of hash keys per block (%s) exceeds maximum of %s" Cause: The SIZE argument is too small. Action: Increase the SIZE argument. ORA-02455, 00000, "The number of cluster key column must be 1" Cause: When specifing the HASH IS option, the number of key columns must be 1. Action: Either do not specify the HASH IS option or reduce the number of key columns. ORA-02456, 00000, "The HASH IS column specification must be NUMBER(*,0)" Cause: The column specification must specify an integer. Action: Specify the column definition as type NUMBER(precision, 0). ORA-02457, 00000, "The HASH IS option must specify a valid column" Cause: The HASH IS column name is not specified in the cluster definition. Action: Specify a valid column name. ORA-02458, 00000, "HASHKEYS must be specified for a HASH CLUSTER" Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER. Action: Specify the HASHKEYS option. ORA-02459, 00000, "Hashkey value must be a positive integer" Cause: The value of the hash key was not a positive number. Action: Specify a positive integer. ORA-02460, 00000, "Inappropriate index operation on a hash cluster" Cause: An attempt to create a cluster index was issued on a hash cluster. Action: Do not attempt to create such an index. ORA-02461, 00000, "Inappropriate use of the INDEX option" Cause: This option is only valid for non hash clusters. Action: Do not specify this option. ORA-02462, 00000, "Duplicate INDEX option specified" Cause: The INDEX option is specified more than once. Action: Only specify the INDEX option once. ORA-02463, 00000, "Duplicate HASH IS option specified" Cause: The HASH IS option is specified more than once. Action: Only specify the HASH IS option once. ORA-02464, 00000, "Cluster definition can not be both HASH and INDEX" Cause: The cluster can either be a hash or indexed cluster - not both. Action: Remove either the HASH IS or INDEX options. ORA-02465, 00000, "Inappropriate use of the HASH IS option" Cause: This option is only valid for clusters Action: Do not specify this option ORA-02466, 00000, "The SIZE option is not allow to be altered for HASH CLUSTERS" Cause: The SIZE can not be changed once the hash cluster has been created. Action: Do not specify this option. ORA-02467, 00000, "Column referenced in expression not found in cluster definition" Cause: A column in the hash is expression was not present in cluster definition. Action: Recreate the cluster and correct the error in hash expression. ORA-02468, 00000, "Constant or system variable wrongly specified in expression" Cause: A constant or system variable was specified in the hash expression. Action: Recreate the cluster and correct the error in hash expression. ORA-02469, 00000, "Hash expression does not return an Oracle Number." Cause: Result of evaluating hash expression is not an Oracle Number. Action: Recreate the cluster and correct the error in hash expression. ORA-02470, 00000, "TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression." Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions. Action: Recreate the cluster and correct the error in hash expression. ORA-02471, 00000, "SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion." Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s. Action: Recreate the cluster and remove the offending keywords. ORA-02472, 00000, "PL/SQL functions not allowed in hash expressions" Cause: A PL/SQL function was used in the hash expression. Action: Recreate the cluster and remove the PL/SQL function. ORA-02473, 00000, "Error while evaluating the cluster's hash expression." Cause: An error occurred while evaluating the clusters hash expression. Action: Correct the query and retry. ORA-02474, 00000, "Fixed hash area extents used (%s) exceeds maximum allowed (%s)" Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed. Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause. ORA-02475, 00000, "maximum cluster chain block count of %s has been exceeded" Cause: The number of blocks in a cluster chain exceeds the maximum number allowed. Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key. / / 2476 - 2479 Reserved for Parallel Direct Loader Errors ORA-02476, 00000, "can not create index due to parallel direct load on table" Cause: A parallel direct load is occurring to the specified table. Action: Retry statement after load is complete. ORA-02477, 00000, "can not perform parallel direct load on object %s" Cause: A parallel direct load is not possible because an index is is being created on the table. Action: Retry load after index creation is complete. ORA-02478, 00000, "merge into base segment would overflow MAXEXTENTS limit" Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger ORA-02479, 00000, "error while translating file name for parallel load" Cause: An invalid file name was specified to load data into. Action: Specify a valid database file. / / 2480 - 2489 Trace facility errors / ORA-02481, 00000, "Too many processes specified for events (max %s)" Cause: Too many processes specified than allowed per event. Action: Enter fewer processes by using ranges or wildcards if possible. ORA-02482, 00000, "Syntax error in event specification (%s)" Cause: Illegal event string Action: Enter a legal event string ORA-02483, 00000, "Syntax error in process specification (%s)" Cause: Illegal process string Action: Enter a legal process string ORA-02484, 00000, "Invalid _trace_buffers parameter specification (%s)" Cause: Bad process or size in _trace_buffers INIT.ORA parameter. Action: ORA-02485, 00000, "Invalid _trace_options parameter specification (%s)" Cause: Bad syntax for _trace_options INIT.ORA parameter. Action: ORA-02486, 00000, "Error in writing trace file %s" Cause: Error occurred in creating/writing the file. Action: Check file name and make sure it is constructed properly. Also, check permissions for directories. / / 2490 - 2499 Reserved for Resizeable Datafiles / ORA-02490, 00000, "missing required file size in RESIZE clause" Cause: No value was specified for the RESIZE clause. Action: Use correct syntax. ORA-02491, 00000, "missing required keyword ON or OFF in AUTOEXTEND clause" Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause. Action: Use correct syntax. ORA-02492, 00000, "missing required file block increment size in NEXT clause" Cause: No value was specified for the NEXT clause. Action: Use correct syntax. ORA-02493, 00000, "invalid file increment size in NEXT clause" Cause: A non-integer value was used for the NEXT clause of the DATAFILE list. Action: Use correct syntax. ORA-02494, 00000, "invalid or missing maximum file size in MAXSIZE clause" Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value. Action: Use correct syntax. ORA-02495, 00000, "cannot resize file %s, tablespace %s is read only" Cause: An attempt was made to resize a data file in a tablespace that is read only. Action: Change the tablespace to read/write and retry the resize operation. / / 2500 - 2699 Reserved for CTOS-specific errors / / 2700 - 2899 Reserved for UNIX two-task errors / ORA-02700, 00000, "osnoraenv: error translating ORACLE_SID" Cause: Two-task driver could not find the value of ORACLE_SID in the environment. Action: Make sure that the ORACLE_SID environment variable has been properly set and exported. ORA-02701, 00000, "osnoraenv: error translating oracle image name" Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-02702, 00000, "osnoraenv: error translating orapop image name" Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-02703, 00000, "osnpopipe: pipe creation failed" Cause: The pipe driver failed to create pipes for communications with the orapop process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. ORA-02704, 00000, "osndopop: fork failed" Cause: The two-task driver could not fork orapop. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02705, 00000, "osnpol: polling of communication channel failed" Cause: The pipe driver failed while polling the communications channel. Action: Contact your customer support representative. ORA-02706, 00000, "osnshs: host name too long" Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit. Action: Contact your customer support representative. ORA-02707, 00000, "osnacx: cannot allocate context area" Cause: The invoked Unix two-task driver could not allocate heap space for the context area. Action: Contact your customer support representative. ORA-02708, 00000, "osnrntab: connect to host failed, unknown ORACLE_SID" Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied. Action: First, check whether you have read access to oratab, and see if the desired sid is there. Add an entry to oratab for the desired sid, if necessary. ORA-02709, 00000, "osnpop: pipe creation failed" Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. ORA-02710, 00000, "osnpop: fork failed" Cause: The pipe driver could not fork the oracle shadow process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02711, 00000, "osnpvalid: write to validation channel failed" Cause: The pipe driver failed to write to the orapop process. Action: Contact your customer support representative. ORA-02712, 00000, "osnpop: malloc failed" Cause: The pipe driver failed to allocate enough heap space for its context area buffers. Action: Contact your customer support representative. ORA-02713, 00000, "osnprd: message receive failure" Cause: The pipe driver failed to read a message from the communications channel. Action: Contact your customer support representative. ORA-02714, 00000, "osnpwr: message send failure" Cause: The pipe driver failed to write a message to the communications channel. Action: Contact your customer support representative. ORA-02715, 00000, "osnpgetbrkmsg: message from host had incorrect message type" Cause: The pipe driver received a message having an unrecognizable message type. Action: Contact your customer support representative. ORA-02716, 00000, "osnpgetdatmsg: message from host had incorrect message type" Cause: The Pipe driver received a message having an unrecognizable message type. Action: Contact your customer support representative. ORA-02717, 00000, "osnpfs: incorrect number of bytes written" Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver. Action: Contact your customer support representative. ORA-02718, 00000, "osnprs: reset protocol error" Cause: The two-task driver could not reset the connection. Action: Contact your customer support representative. ORA-02719, 00000, "osnfop: fork failed" Cause: The fast driver could not fork the oracle shadow process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02720, 00000, "osnfop: shmat failed" Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer. Action: Try invoking the Fast driver later, or use the default attach address. ORA-02721, 00000, "osnseminit: cannot create semaphore set" Cause: The Fast driver failed to get a semaphore set. Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator. ORA-02722, 00000, "osnpui: cannot send break message to orapop" Cause: The Pipe driver could not send a break message to orapop. Action: Contact your customer support representative. ORA-02723, 00000, "osnpui: cannot send break signal" Cause: The Pipe driver could not send a break message to the ORACLE shadow process. Action: Contact your customer support representative. ORA-02724, 00000, "osnpbr: cannot send break message to orapop" Cause: The Pipe driver could not send a break message to orapop. Action: Contact your customer support representative. ORA-02725, 00000, "osnpbr: cannot send break signal" Cause: The Pipe driver could not send a break message to the ORACLE shadow process. Action: Kill system call failed. Check errno and contact customer support. ORA-02726, 00000, "osnpop: access error on oracle executable" Cause: The Pipe driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-02727, 00000, "osnpop: access error on orapop executable" Cause: The Pipe driver could not access the orapop executable. Action: Check the permissions on the orapop executable and each component of the ORACLE_HOME/bin path. ORA-02728, 00000, "osnfop: access error on oracle executable" Cause: The Fast driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-02729, 00000, "osncon: driver not in osntab" Cause: The driver you have specified is not supported. Action: Check with your database administrator which drivers are supported. ORA-02730, 00000, "osnrnf: cannot find user logon directory" Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file. Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your uid and home directory are correct in the /etc/passwd file. ORA-02731, 00000, "osnrnf: malloc of buffer failed" Cause: The specified driver could not find enough heap space to malloc a buffer. Action: Contact your customer support representative. ORA-02732, 00000, "osnrnf: cannot find a matching database alias" Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet. Action: Create the alias in a file called .sqlnet in your home directory for personal use or ask your system administrator to create the alias in /etc/sqlnet for system-wide use. ORA-02733, 00000, "osnsnf: database string too long" Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit. Action: Contact your customer support representative. ORA-02734, 00000, "osnftt: cannot reset shared memory permission" Cause: The Fast driver was unable to reset shared memory permissions. Action: Contact your customer support representative. ORA-02735, 00000, "osnfpm: cannot create shared memory segment" Cause: The Fast driver failed to create a shared memory segment for two-task communication. Action: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system. ORA-02736, 00000, "osnfpm: illegal default shared memory address" Cause: The Fast driver failed to establish a default shared memory address. Action: Contact your customer support representative. ORA-02737, 00000, "osnpcl: cannot tell orapop to exit" Cause: The Pipe driver failed to send orapop the command to exit. Action: Contact your customer support representative. ORA-02738, 00000, "osnpwrtbrkmsg: incorrect number of bytes written" Cause: The pipe driver apparently sent an imcomplete break message. Action: Contact your customer support representative. ORA-02739, 00000, "osncon: host alias is too long" Cause: The alias used for a sqlnet host is longer than 161 characters. Action: Use a shorter alias. ORA-02750, 00000, "osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf" Cause: The Fast driver failed to create a shared memory file for two-task communication. Action: Check the permissions on the directory ?/dbs ORA-02751, 00000, "osnfsmmap: cannot map shared memory file" Cause: The Fast driver failed to map a shared memory file for two-task communication. Action: Contact your customer support representative. ORA-02752, 00000, "osnfsmmap: illegal shared memory address" Cause: The Fast driver failed to attach shared memory at the expected location. Action: Contact your customer support representative. ORA-02753, 00000, "osnfsmmap: cannot close shared memory file" Cause: The Fast driver cannot close the shared memory file. Action: Contact your customer support representative. ORA-02754, 00000, "osnfsmmap: cannot change shared memory inheritence" Cause: The Fast driver could not alter the inheritence attributes of the shared memory. Action: Contact your customer support representative. ORA-02755, 00000, "osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf" Cause: The Fast driver failed to create a file for shared memory. Action: Check the permissions on the directory ?/dbs ORA-02756, 00000, "osnfsmnam: name translation failure" Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_.dbf. Action: Contact your customer support representative. ORA-02757, 00000, "osnfop: fork_and_bind failed" Cause: The Fast driver failed to fork a process onto the desired cluster and node number. Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact customer support. / / 2758 - 2899 Reserved for ORACLE asynchronous I/O. ORA-02758, 00000, "Allocation of internal array failed" Cause: The package was unable to allocate memory for an array because the system ran out of memory. Action: Either reclaim memory by killing other processes or reboot the machine with more memory. ORA-02759, 00000, "Not enough request descriptors available" Cause: All of the package's request descriptors are in use performing other requests. Action: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors. ORA-02760, 00000, "Client close of file failed." Cause: The client was unable to close a file after forking the servers. Action: This is a system problem - contact your System Administrator. ORA-02761, 00000, "File number to be canceled is negative." Cause: The file number contained with the sfiov structure is less than zero. Action: This may be a programming error. If it is not, contact ORACLE support. ORA-02762, 00000, "file number to be cancelled is greater than the maximum." Cause: The file number contained with the sfiov structure is greater than the maximum. Action: This may be a programming error. If it is not, contact ORACLE support. ORA-02763, 00000, "Unable to cancel at least one request" Cause: No requests were found that could be cancelled. Action: This error can occur if all the requests dealing with that file number have already been filled. ORA-02764, 00000, "Invalid package mode" Cause: The mode of the package can only be parallel or duplex. Action: See sfa.h for the correct values. ORA-02765, 00000, "Invalid maximum number of servers" Cause: The number of servers given was less than or equal to zero. Action: Use a number greater than zero. ORA-02766, 00000, "Invalid maximum of request descriptors" Cause: The number of request descriptors was less than or equal to zero. Action: Use a number greater than zero. ORA-02767, 00000, "Less than one request descriptor was allocated per server" Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used. Action: Use a higher number ORA-02768, 00000, "Maximum number of files is invalid" Cause: The maximum number of files to be used by the package was less than or equal to zero. Action: Use a positive number. ORA-02769, 00000, "Setting of handler for SIGTERM failed" Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error. Action: Contact ORACLE support. ORA-02770, 00000, "Total number of blocks is invalid" Cause: The total number of blocks to be allocated for use by the package was not greater than zero. Action: Use a positive number. ORA-02771, 00000, "Illegal request time out value" Cause: The number was not a positive number. Action: Use a positive number. ORA-02772, 00000, "Invalid maximum server idle time" Cause: The time given was not a positive number. Action: Use a positive number. ORA-02773, 00000, "Invalid maximum client wait time" Cause: The time given was not a positive number. Action: Use a positive number. ORA-02774, 00000, "Invalid request list latch time out value" Cause: The time given was not a positive number. Action: Use a positive number. ORA-02775, 00000, "Invalid request done signal" Cause: The signal number was not a positive number. Action: Use a positive number. ORA-02776, 00000, "Value for request done signal exceeds maximum" Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system. Action: ORA-02777, 00000, "Stat failed on log directory" Cause: The package was unable to get information about the directory in which the log files are to reside. Action: Check the permissions on the directory or use a different directory name. ORA-02778, 00000, "Name given for the log directory is invalid" Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory. Action: Use a different name. ORA-02779, 00000, "Stat failed on core dump directory" Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception. Action: Check the permissions on the directory or use a different directory name. ORA-02780, 00000, "Name given for the core dump directory is invalid" Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory. Action: Use a different name. ORA-02781, 00000, "Invalid value given for the timing wanted flag" Cause: The value given was not TRUE or FALSE. Action: ORA-02782, 00000, "Both read and write functions were not specified" Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given. Action: Either specify both functions or specify neither. The package will supply its own functions. ORA-02783, 00000, "Both post and wait functions were not specified" Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given. Action: Either specify both functions or specify neither. The package will supply its own functions. ORA-02784, 00000, "Invalid shared memory ID specified" Cause: The ID of the segment specified for use as the shared buffer region was invalid. Action: Use a different ID, or let the package specify its own. ORA-02785, 00000, "Invalid shared memory buffer size" Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero. Action: Use a positive number. ORA-02786, 00000, "Size needed for shared region is greater than segment size" Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment. Action: Use a larger size segment or let the package allocate its own. ORA-02787, 00000, "Unable to allocate memory for segment list" Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate. Action: ORA-02788, 00000, "Unable to find kernel process pointer in async process array" Cause: Internal error - Contact ORACLE support. Action: ORA-02789, 00000, "Maximum number of files reached" Cause: The maximum number of files that can be used for asynchronous I/O has been reached. Action: Shut down the servers and re-initialize the package with a higher number. ORA-02790, 00000, "File name is too long" Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length. Action: Use a shorter name. ORA-02791, 00000, "Unable to open file for use with asynchronous I/O" Cause: The package could not open file for some reason. Action: Check the file name. ORA-02792, 00000, "Unable to fstat() a file being used for asynchronous I/O." Cause: The fstat(2) call on a file being used for asynchronous I/O failed. Action: Check the file name. ORA-02793, 00000, "Close of asynchronous I/O failed." Cause: The client was unable to close a file being used for asynchronous I/O. Action: Contact ORACLE support - this should not happen. ORA-02794, 00000, "Client unable to get key for shared memory" Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory. Action: Contact ORACLE support - this is an internal error. ORA-02795, 00000, "Request list is empty" Cause: The client was signalled by a server that it was done with a request but the "done" list was empty. Action: Internal error - contact ORACLE support. ORA-02796, 00000, "Done request is not in correct state" Cause: A request is not in the right state. Action: Internal error - contact ORACLE support. ORA-02797, 00000, "No requests available" Cause: No free request descriptors are available. Action: Wait until some requests are filled and then retry the request, or shutdown the servers and initialize the package with a higher number of requests. ORA-02798, 00000, "Invalid number of requests" Cause: The number of operations sent to either sfard() or sfawrite() is less than zero. Action: This is a user programming error. ORA-02799, 00000, "Unable to arm signal handler" Cause: The arming of a signal handler for the "done" signal failed. Action: Internal error - contact ORACLE support. ORA-02800, 00000, "Requests timed out" Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time. Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with sfainit(). If the server processes are dying due to unexpected signals, this is an internal error, and ORACLE support should be contacted. ORA-02801, 00000, "Operations timed out" Cause: Some asynchronous operations timed out in kernel mode. Action: Internal error - contact ORACLE support. ORA-02802, 00000, "No idle servers available in parallel mode" Cause: Internal error. Action: Contact ORACLE support. ORA-02803, 00000, "Retrieval of current time failed" Cause: Internal error. Action: Contact ORACLE support. ORA-02804, 00000, "Allocation of memory failed for log file name" Cause: The client was unable to allocated a buffer for the name of the log file. Action: Contact your System Administrator. ORA-02805, 00000, "Unable to set handler for SIGTPA" Cause: Internal error. Action: Contact ORACLE support. ORA-02806, 00000, "Unable to set handler for SIGALRM" Cause: Internal error. Action: Contact ORACLE support. ORA-02807, 00000, "Allocation of memory for I/O vectors failed." Cause: The client was unable to allocate memory for the array of I/O vectors that the servers are to use. Action: Contact your System Administrator. ORA-02808, 00000, "Allocation of memory of open files array failed." Cause: The client was unable to allocate memory for an array of flags that the servers are to use. Action: Contact your System Administrator. ORA-02809, 00000, "Jump buffer not valid" Cause: Internal error. Action: Contact ORACLE support. ORA-02810, 00000, "Unable to make temporary file name for memory mapped file" Cause: Action: ORA-02811, 00000, "Unable to attach shared memory segment" Cause: Action: ORA-02812, 00000, "Bad attach address" Cause: Action: ORA-02813, 00000, "Unable to make temporary file name in order to get key" Cause: Internal error. Action: Contact ORACLE support. ORA-02814, 00000, "Unable to get shared memory" Cause: Shmget(2) failed. Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support. ORA-02815, 00000, "Unable to attach shared memory" Cause: Shmat(2) failed. Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support. ORA-02816, 00000, "Unable to kill a process" Cause: A server did not die after being sent a kill signal. Action: The process may be a runaway - contact ORACLE customer support. ORA-02817, 00000, "Read failed" Cause: A server could not read a requested amount of data. Action: Check the call to sfard(). An incorrect file descriptor may have been sent to sfard(). The number in the "additional information" field is the starting block number of the data segment being read in. ORA-02818, 00000, "Less than the number of blocks requested was read in" Cause: A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in. Action: This is a programming error. ORA-02819, 00000, "Write failed" Cause: A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up. Action: Check the UNIX error number. ORA-02820, 00000, "Unable to write the requested number of blocks" Cause: A server could not write the requested amount of data out to disk. The disk may have run out of space. Action: Check the UNIX error number. ORA-02821, 00000, "Unable to read the requested number of blocks." Cause: A server could not read the number of blocks that was requested. The end of the file may have been read. Action: Check the file on disk. ORA-02822, 00000, "Invalid block offset" Cause: A server was unable to seek to the designated block. Action: Check the UNIX error number. ORA-02823, 00000, "Buffer is not aligned." Cause: The buffer on which an I/O is being done is not on the correct boundary. Action: Check the calling program. ORA-02824, 00000, "Request free list is empty" Cause: The list from which the package allocates request descriptors is empty because all of the descriptors is in use. Action: Wait until some become free, or initialize the package with a higher number of request descriptors. ORA-02825, 00000, "Request on free list was not free" Cause: Internal error. Action: Contact ORACLE support. ORA-02826, 00000, "Illegal block size" Cause: A negative number was given for the I/O block size to be used by the asynchronous I/O package. Action: This is a programming error - use either a positive number or zero to get the default value. ORA-02827, 00000, "Invalid file number" Cause: The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open. Action: This is a programming error. Since the calling program should not touch this number, this is a programming error. ORA-02828, 00000, "Segment free list is empty" Cause: No segments are available to allocated. Action: Free some segments or shut down the package and re-initialize it with a higher number of segments. ORA-02829, 00000, "No segment of the proper size is available" Cause: No segment of the proper size is ready for use by the caller. Action: Free some segments and try again. ORA-02830, 00000, "Segment could not be split - no free segments available" Cause: A segment that is larger than that desired could not be split because no free segment was available. Action: Free some segments and try again. ORA-02831, 00000, "Segment deallocation failed - empty segment list" Cause: The caller attempted to deallocate a segment but the "in use" list was empty. This is a programming error. Action: Check the calling program. ORA-02832, 00000, "Segment deallocation failed - segment not on list" Cause: The caller attempted to deallocate a segment that was not on the "in use" list. This is a programming error. Action: Check the calling program. ORA-02833, 00000, "Server was unable to close file" Cause: A server was unable to close a file being used for asynchronous I/O. Action: See the UNIX error number for more information. ORA-02834, 00000, "Server unable to open file" Cause: The server was unable to open a file for use with asynchronous I/O. Action: Check the UNIX error number for more information. ORA-02835, 00000, "Server unable to send signal to client" Cause: Internal error. Action: Contact ORACLE support. ORA-02836, 00000, "Unable to create temporary key file" Cause: Internal error. Action: Contact ORACLE support. ORA-02837, 00000, "Unable to unlink temporary file" Cause: Internal error. Action: Contact ORACLE support. ORA-02838, 00000, "Unable to arm signal handler for the alarm signal" Cause: The arming of a signal handler for the alarmsignal failed. Action: Internal error - contact ORACLE support. ORA-02839, 00000, "Sync of blocks to disk failed." Cause: The server was unable to flush its writes out to disk. Action: Check the UNIX error number. ORA-02840, 00000, "Open of log file by client failed" Cause: The client process was unable to open its log file. Action: Check the UNIX error number for more information. ORA-02841, 00000, "Server died on start up" Cause: A server exited during its initialization process. Action: Check the servers' logs for more information. ORA-02842, 00000, "Client unable to fork a server" Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn. Action: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes. ORA-02843, 00000, "Invalid value for kernel flag" Cause: An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted. Action: This is a programming error - check the calling routine. ORA-02844, 00000, "Invalid value for the leave open flag" Cause: A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported. Action: This is a programming error - check the calling routine. ORA-02845, 00000, "Invalid value for the timing wanted flag" Cause: A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported. Action: This is a programming error - check the calling routine. ORA-02846, 00000, "Unkillable server" Cause: A server would not respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. Action: This is an operating system problem. ORA-02847, 00000, "Server did not terminate when posted" Cause: A server did not respond to a posted request to shutdown. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. Action: Contact ORACLE support. ORA-02848, 00000, "Asynchronous I/O package is not running" Cause: An operation using the asynchronous I/O package was attempted without first initializing the package using sfainit(). Action: Call sfainit() before using the package. ORA-02849, 00000, "Read failed because of an error" Cause: A server could not read the requested amount of data from disk. Action: Check the UNIX error number. ORA-02850, 00000, "File is closed" Cause: A file upon which an asynchronous I/O operation is to be performed has already been closed by the package. Action: This is a programming error. ORA-02851, 00000, "Request list is empty when it should not be" Cause: This is an internal problem. Action: Contact ORACLE support. ORA-02852, 00000, "Invalid critical-section time out value" Cause: The time given was not a positive number. Action: Use a positive number. ORA-02853, 00000, "Invalid server list latch time out value" Cause: The time given was not a positive number. Action: Use a positive number. ORA-02854, 00000, "Invalid number of request buffers" Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than 0. Action: Use a number that is greater than or equal to 0. ORA-002855, 00000, "Number of requests is less than the number of slaves" Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than the number specified for the number of slaves, "db_slaves." Action: Specify a number that is greater than that given for "db_slaves" Alternatively, specify 0. The kernel will supply the appropriate number. / 2875 - 2899 Reserved for IBM RS/6000 ORA-02875, 00000, "smpini: Unable to get shared memory for PGA" Cause: Stated in errno. Action: Resolve the problem. ORA-02876, 00000, "smpini: Unable to attach to shared memory for PGA" Cause: Stated in errno. Action: Resolve the problem. ORA-02877, 00000, "smpini: Unable to initialize memory protection" Cause: The adspcinit program has not been executed. Action: Execute the adscpinit program as shown in your Installation and Users' Guide. If the problem persists, try rebooting your computer. ORA-02878, 00000, "sou2o: Variable smpdidini overwritten" Cause: The variable smpdidini was overwritten, probably by client code. Action: Verify client code, e.g. Pro*C, for illegal memory access. If the problem occurs outside Single Task operation, contact your customer support representative. ORA-02879, 00000, "sou2o: Could not gain access to protected memory" Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02880, 00000, "smpini: Could not register PGA for protection" Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02881, 00000, "sou2o: Could not revoke access to protected memory" Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02882, 00000, "sou2o: Could not register SGA for protection" Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02899, 00000, "smscre: Cannot create SGA with Extended Shared Memory feature" Cause: The environment variable EXTSHM was set before starting oracle. Action: Unset the environment variable EXTSHM and startup oracle. / / 2900 - 2999 Reserved for licensing server errors / / 3000-3099 currently not implemented features / ORA-03001, 00000, "unimplemented feature" Cause: This feature is not implemented. Action: None. ORA-03002, 00000, "operator not implemented" Cause: This is an internal error. Action: Contact your customer support representative. ORA-03007, 00000, "obsolete feature" Cause: User attempted to use a feature which is no longer supported. Action: None. ORA-3008, 00000, "parameter COMPATIBLE >= %s needed for %s" Cause: An attempt was made to use a feature for a later Oracle version, than the setting of the initialization parameter, COMPATIBLE. Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options. / / 3100-3199 two task interface errors / some of these can eventually convert to internal ercs / ORA-03100, 00000, "communication area cannot be allocated; insufficient memory" Cause: Action: ORA-03105, 00000, "internal protocol error" Cause: Action: ORA-03106, 00000, "fatal two-task communication protocol error" Cause: Action: ORA-03107, 00000, "oranet buffer underflow" Cause: Action: ORA-03108, 00000, "oranet: ORACLE does not support this interface version" Cause: Action: ORA-03109, 00000, "oranet buffer overflow" Cause: Action: ORA-03110, 00000, "oranet: ORACLE does not support this SQL version" Cause: Action: ORA-03111, 00000, "break received on communication channel" Cause: Action: ORA-03112, 00000, "a server linked as single-task cannot use SQL*Net" Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement. Action: Do not use SQL*Net connect strings in a single-task environment. ORA-03113, 00000, "end-of-file on communication channel" Cause: Action: ORA-03114, 00000, "not connected to ORACLE" Cause: Action: ORA-03115, 00000, "unsupported network datatype or representation" Cause: Action: ORA-03116, 00000, "invalid buffer length passed to a conversion routine" Cause: Action: ORA-03117, 00000, "two-task save area overflow" Cause: Action: ORA-03118, 00000, "two-task coroutine has invalid state" Cause: Action: ORA-03119, 00000, "two-task detected inconsistent datatype specification" Cause: There was both a datatype, and an anonymous datatype declaration found. Action:Correct the specification. ORA-03120, 00000, "two-task conversion routine: integer overflow" Cause: Action: ORA-03121, 00000, "no interface driver connected - function not performed" Cause: Action: ORA-03122, 00000, "attempt to close ORACLE-side window on user side" Cause: This is an internal error. Action: Contact your customer support representative. ORA-03123, 00000, "operation would block" Cause: This is a status code that indicates that the operation cannot complete now. Action: None; this is not an error. The operation should be retried again for completion. ORA-03124, 00000, "two-task internal error" Cause: Internal error. Action: Contact your customer support representative. ORA-03125, 00000, "client-server protocol violation" Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code. Action: Contact your customer support representative. ORA-03126, 00000, "network driver does not support non-blocking operations" Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations. Action: Use default blocking operations or use a driver supporting non-blocking operations. ORA-03127, 00000, "no new operations allowed until the active operation ends" Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched. Action: Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched. ORA-03128, 00000, "connection is in blocking mode" Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode. Action: If non-blocking mode is required use appropriate OCI calls to change the mode. ORA-03129, 00000, "the next piece to be inserted is required" Cause: The application performed a piecewise bind on a column. Action: Provide the next piece of this bind variable. ORA-03130, 00000, "the buffer for the next piece to be fetched is required" Cause: The application performed a piecewise define on the column. Action: Provide the next buffer for the next piece to be retrieved. ORA-03131, 00000, "an invalid buffer was provided for the next piece" Cause: The application either provided the length of the buffer for the next piece to be zero or provided a null pointer. Action: Verify if the buffer pointer for the next piece is null or if the length is zero. ORA-03132, 00000, "two-task default value overflow" Cause: The default value specified for a record field was too large. Action: Change the default value to fit the field size. / / 3200 - 3289 Allocate Extent and other Space Management errors / ORA-03200, 00000, "the segment type specification is invalid" Cause: segment type is not TABLE, INDEX, or CLUSTER Action: use a correct segment type / ORA-03201, 00000, "the group number specification is invalid" Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment Action: use a correct group number / ORA-03202, 00000, "the scan limit specification is invalid" Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment Action: use a correct scan limit / ORA-03203, 00000, "concurrent update activity makes space analysis impossible" Cause: high volume of user updates interfere with the space analysis Action: retry the command or lock the underlying objects / ORA-03204, 00000, "the segment type specification should indicate partitioning" Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning Action: specify PARTITION in the segment type, if the object is partitioned, otherwise, omit the partition name / ORA-03205, 00000, "partition name is required when partitioned type is specified" Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning Action: specify partition name, if the object is partitioned, otherwise, specify a non-partitioned type / ORA-03206, 00000, "maximum file size of (%s) blocks in AUTOEXTEND clause is out of range" Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. Action: Reduce the size and retry. / ORA-03207, 00000, "subpartitioned type must be specified for composite object" Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning Action: specify subpartition name and subpartition type / ORA-03208, 00000, "partitioned type must be specified for a non-composite object" Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning Action: specify partition name and partition type / ORA-03209, 00000, "DBMS_ADMIN_PACKAGE invalid file/block specification" Cause: The value of file number or block number is outside of limits or inconsistent Action: Fix the file number/block number value / ORA-03210, 00000, "DBMS_ADMIN_PACKAGE invalid option specification" Cause: The value of one of the option parameters is incorrect Action: Fix the option value / ORA-03211, 00000, "The segment does not exist or is not in a valid state" Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation Action: Fix the segment specification, or put the segment in the appropriate state. / ORA-03212, 00000, "Temporary Segment cannot be created in locally-managed tablespace" Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace / ORA-03213, 00000, "Invalid Lob Segment Name for DBMS_SPACE package" Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist. Action: Fix the Segment Specification / ORA-03214, 00000, "File Size specified is smaller than minimum required" Cause: File Size specified for add/resize datafile/tempfile does not allow for the minimum required of one allocation unit. Action: Increase the specification for file size / ORA-03215, 00000, "File Size specified for resize is too small " Cause: File Size specified for resize datafile/tempfile causes bitmap control structures to overlap Action: Increase the specification for file size / ORA-03216, 00000, "Tablespace/Segment Verification cannot proceed" Cause: Corruptions detected during verification whch cannot be dealt with Action: Do manual verification / ORA-03217, 00000, "invalid option for alter of TEMPORARY TABLESPACE" Cause: invalid option for alter of temporary tablespace was specified Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE / ORA-03218, 00000, "invalid option for CREATE/ALTER TABLESPACE" Cause: invalid option for create/alter tablespace of type locally-managed Action: Specify one of the valid options. / ORA-03219, 00000, "Tablespace '%s' is dictionary-managed, offline or temporary" Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary Action: Reissue operation for a different tablespace, mount the tablespace or do not issue it at all, since it does not apply for the given tablespace / ORA-03220, 00000, "DBMS_ADMIN_PACKAGE required parameter is NULL or missing" Cause: Some of the procedures was called with missing or NULL parameters Action: Specify the missing parameter / ORA-03221, 00000, "Temporary tablespaces and temporary segments must have standard block size" Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size. Action: (1) If creating a temporary tablespace, do not specify a block size different from the standard block size. (2) If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size. (3) Ensure that the user's temporary tablespace is a tablespace having the standard block size. / ORA-03230, 00000, "segment only contains %s blocks of unused space above high water mark" Cause: Attempt to preserve too many blocks. Action: reduce the KEEP amount. / ORA-03231, 00000, "the INITIAL extent may not be deallocated" Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release. Action: increase the KEEP amount, or truncate the segment, and reissue the command. ORA-03232, 00000, "unable to allocate an extent of %s blocks from tablespace %s" Cause: An attempt was made to specify a HASH_MULTIBLOCK_IO_COUNT value that is greater than the tablespace's NEXT value Action: Increase the value of NEXT for the tablespace using ALTER TABLESPACE DEFAULT STORAGE or decrease the value of HASH_MULTIBLOCK_IO_COUNT. / ORA-03233, 00000, "unable to extend table %s.%s subpartition %s by %s in tablespace %s" Cause: Failed to allocate an extent for table subpartition segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03234, 00000, "unable to extend index %s.%s subpartition %s by %s in tablespace %s" Cause: Failed to allocate an extent for index subpartition segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03235, 00000, "max # extents (%s) reached in table %s.%s subpartition %s" Cause: A table subpartition tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-03236, 00000, "max # extents (%s) reached in index %s.%s subpartition %s" Cause: An index subpartition tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-03237, 00000, "Initial Extent of specified size cannot be allocated" Cause: Too large a size for an initial extent due to freelist group specification Action: Reduce number of freelist groups specified for segment ORA-03238, 00000, "unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s" Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03239, 00000, "maxextents (%s) reached in LOB segment %s.%s subpartition %s" Cause: A LOB subpartition segment tried to extend past maxextents. Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters. / / Errors 3240 - 3250 reserved for tablespace migration and bitmaps relocation / ORA-03240, 00000, "User's temporary tablespace same as tablespace being migrated" Cause: Users default temporary tablespace must be different from the tablespace being migrated. Action: alter users default temporary tablespace to be different. ORA-03241, 00000, "Invalid unit size" Cause: User specified an invalid unit size for the tablespace Action: Specify the correct unit size. To estimate unit size please refer to Oracle Server Administrator's Guide. ORA-03242, 00000, "Tablespace migration retried 500 times" Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration. Action: Avoid migrating the tablespace when there is heavy temporary segment creation going on as with object drops. ORA-03243, 00000, "destination dba overlaps with existing control information" Cause: Cannot overlap control information during relocation Action: Please chose another destination address ORA-03244, 00000, "No free space found to place the control information" Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination. Action: If during migration, add more space to the tablespace and retry migration. If during bitmaps relocation, specify a destination address where there is enough free space. ORA-03245, 00000, "Tablespace has to be dictionary managed, online and permanent to be able to migrate" Cause: Tablespace was not dictionary managed or online or permanent. Action: Make sure the tablespace is online, permanent and dictionary managed ORA-03246, 00000, "Invalid block number specified" Cause: Control information cannot be placed at the specified dba either because the block number specified is beyond the file end or the file is not large enough to accomodate the control information at that location Action: specify a correct block number ORA-03247, 00000, "Invalid block number specified" Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive Action: Choose another destination dba. ORA-03248, 00000, "Too much of segment creation activity during migration" Cause: Temporary segments were attempted to be created during migration Action: The error is signalled after retrying migration for 500 times. Run migration when there is less of segment creation activity is going on. ORA-03249, 00000, "Uniform size for auto segment space managed tablespace should have atleast %s blocks" Cause: For the given blocksize, uniform size specified is insufficient Action: Specify larger extent size and retry ORA-03274, 00000, "both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified" Cause: The DEALLOCATE option and the ALLOCATE option are specified in the same command. Action: Choose one of the options or issue two separate commands. ORA-03275, 00000, "duplicate DEALLOCATE option specification" Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once. Action: Specify the option at most once. ORA-03276, 00000, "duplicate ALLOCATE EXTENT option specification" MERGE: 2376 RENUMBERED TO 3276 Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once. Action: Specify the option at most once. ORA-03277, 00000, "invalid SIZE specified" MERGE: 2377 RENUMBERED TO 3277 Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-03278, 00000, "duplicate ALLOCATE EXTENT option specification" MERGE: 2378 RENUMBERED TO 3278 Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once. Action: Specify each option at most once. ORA-03279, 00000, "invalid INSTANCE specified" MERGE: 2379 RENUMBERED TO 3279 Cause: The specified value is not recognized as a valid instance name. Action: Use a valid name. ORA-03280, 00000, "invalid DATAFILE filename specified" MERGE: 2380 RENUMBERED TO 3280 Cause: A character string literal is expected, but not found. Action: Specify filenames using character string literals. ORA-03281, 00000, "invalid ALLOCATE EXTENT option" MERGE: 2381 RENUMBERED TO 3281 Cause: An option other than DATAFILE, SIZE or INSTANCE was specified. Action: Remove invalid option and retry the command. ORA-03282, 00000, "missing ALLOCATE EXTENT option" MERGE: 2382 RENUMBERED TO 3282 Cause: No ALLOCATE EXTENT options were specified. Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE. ORA-03283, 00000, "specified datafile %s does not exist" MERGE: 2383 RENUMBERED TO 3283 Cause: The datafile does not exist Action: Retry the option with the correct datafile ORA-03284, 00000, "datafile %s is not a member of tablespace %s" MERGE: 2384 RENUMBERED TO 3284 Cause: The specified datafile does not belong to the tablespace that the object resides in. Action: Retry the option with the correct datafile. ORA-03286, 00000, "ALLOCATE EXTENT not valid for HASH CLUSTERS" Cause: The cluster is a hash cluster, and can not use the allcoate extent option. Action: ORA-03287, 00000, "invalid FREELIST GROUP specified" Cause: The specified FREELIST GROUP number is invalid Action: Choose a number between 1 and # freelist groups for this object ORA-03288, 00000, "both FREELIST GROUP and INSTANCE parameters may not be specified" Cause: Both FREELIST GROUP and INSTANCE were specified in clause Action: Remove one of the two parameters / / 3290 - 3295 Truncate Parse and Execution Errors / ORA-03290, 00000, "Invalid truncate command - missing CLUSTER or TABLE keyword" Cause: Invalid object specification given. Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE ORA-03291, 00000, "Invalid truncate option - missing STORAGE keyword" Cause: Expected STORAGE keyword Action: Either specify DROP STORAGE or REUSE STORAGE ORA-03292, 00000, "Table to be truncated is part of a cluster" Cause: The table being truncated is a member of a cluster. Action: Either use TRUNCATE CLUSTER or DROP TABLE ORA-03293, 00000, "Cluster to be truncated is a HASH CLUSTER" Cause: Only INDEX CLUSTERS can be truncated. Action: Drop and recreate the HASH CLUSTER instead of using truncate. / / 3296 - 3299 Reserved for Resizeable Datafiles / ORA-03296, 00000, "cannot resize datafile - file %s not found" Cause: The specified datafile is not available for resizing. Action: Ensure that the datafile name is valid, and if so, ensure the file is accessible. ORA-03297, 00000, "file contains used data beyond requested RESIZE value" Cause: Some portion of the file in the region to be trimmed is currently in use by a database object Action: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed. ORA-03298, 00000, "cannot shrink datafile - file %s is under hot backup" Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed. Action: Retry shrinking the file after the hot backup completes. ORA-03299, 00000, "cannot create dictionary table %s" Cause: A dictionary table is created upon the first execution of the command 'alter database datafile autoextend on' for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace. Action: See action for next error message in error stack. / / 3300 - 3499 Reserved for Meiko / / 3500 - 3699 Reserved for Native Macintosh OS-specific errors / / 3700 - 3999 Reserved for DG AOS/VS specific errors / / 4000-4099 invalid parameter errors / ORA-04000, 00000, "the sum of PCTUSED and PCTFREE cannot exceed 100" Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100 Action: create the table/cluster specifying values whose sum is <= 100 ORA-04001, 00000, "sequence parameter %s must be an integer" Cause: %s (a sequence parameter) specified was not an integer Action: create the sequence, giving the specified parameter an integer value ORA-04002, 00000, "INCREMENT must be a non-zero integer" Cause: a sequence increment was specified to be zero Action: specify the increment to be a non-zero value ORA-04003, 00000, "sequence parameter %s exceeds maximum size allowed (%s digits)" Cause: %s (a sequencer parameter) had too many digits Action: specify the parameter with the allowed number of digits ORA-04004, 00000, "MINVALUE must be less than MAXVALUE" Cause: MINVALUE was specified to be greater than or equal to MAXVALUE Action: specify a MINVALUE that is less than MAXVALUE ORA-04005, 00000, "INCREMENT must be less than MAXVALUE minus MINVALUE" Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE Action: specify an INCREMENT that is < MAXVALUE-MINVALUE ORA-04006, 00000, "START WITH cannot be less than MINVALUE" Cause: the given starting value is less than MINVALUE Action: make sure that the starting value is >= MINVALUE ORA-04007, 00000, "MINVALUE cannot be made to exceed the current value" Cause: the given MINVALUE would be greater than the current value Action: always make sure that MINVALUE is <= the current value ORA-04008, 00000, "START WITH cannot be more than MAXVALUE" Cause: the starting value would be larger than MAXVALUE Action: make sure that the starting value is less than MAXVALUE ORA-04009, 00000, "MAXVALUE cannot be made to be less than the current value" Cause: the current value exceeds the given MAXVALUE Action: make sure that the new MAXVALUE is larger than the current value ORA-04010, 00000, "the number of values to CACHE must be greater than 1" Cause: the value in the CACHE clause was one Action: specify NOCACHE, or a value larger than one ORA-04011, 00000, "sequence %s must range between %s and %s" Cause: the value specified for one of the sequence parameters exceeds limits Action: specify parameter within these limits ORA-04012, 00000, "object is not a sequence" Cause: the object specified cannot have sequence ddl's performed on it Action: re-enter the statement being careful with the spelling of the name ORA-04013, 00000, "number to CACHE must be less than one cycle" Cause: number to CACHE given is larger than values in a cycle Action: enlarge the cycle, or cache fewer values ORA-04014, 00000, "descending sequences that CYCLE must specify MINVALUE" Cause: sequences that cycle must have their wrap-wrap specified Action: re-create the sequence, specifying its wrap-value ORA-04015, 00000, "ascending sequences that CYCLE must specify MAXVALUE" Cause: sequences that cycle must have their wrap-wrap specified Action: re-create the sequence, specifying its wrap-value ORA-04016, 00000, "sequence %s no longer exists" Cause: sequence was dropped while processing its next value. Action: re-create the sequence ORA-04017, 00000, "invalid value %s (length = %s) for parameter max_dump_file_size" Cause: neither did the string supplied for max_dump_file_size parameter match the "UNLIMITED" string value nor did it represent a base 10 integer. Action: reassign a proper value to this parameter. ORA-04018, 00000, "invalid value %s for parameter _scn_scheme" Cause: The value specified for init.ora parameter _scn_scheme is not recognized as one of the defined schemes. Action: reassign a proper value. ORA-04019, 00000, "SCN scheme incompatible with other instances" Cause: Either different instances are running incompatible Oracle releases or different values have been assigned to the _scn_scheme init.ora parameter on different instances. Action: Make sure the _scn_scheme init.ora parameter is set to the same value on all instances. / / 4020-4029 Reserved for Library Cache errors / ORA-04020, 00000, "deadlock detected while trying to lock object %s%s%s%s%s" Cause: While trying to lock a library object, a deadlock is detected. Action: Retry the operation later. ORA-04021, 00000, "timeout occurred while waiting to lock object %s%s%s%s%s" Cause: While waiting to lock a library object, a timeout is occurred. Action: Retry the operation later. ORA-04022, 00000, "nowait requested, but had to wait to lock dictionary object" Cause: Had to wait to lock a library object during a nowait request. Action: Retry the operation later. ORA-04028, 00000, "cannot generate diana for object %s%s%s%s%s" Cause: Cannot generate diana for an object because of lock conflict. Action: Please report this error to your support representative. ORA-04029, 00000, "error ORA-%s occurred when querying %s%s%s" Cause: The table or view being queried might be missing. The error number indicates the error. Action: Fix the error. / / 4030-4039 Reserved for Memory Manager errors / ORA-04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)" Cause: Operating system process private memory has been exhausted Action: ORA-04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")" Cause: More shared memory is needed than was allocated in the shared pool. Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserved_size" and "shared_pool_size". If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size". ORA-04032, 00000, "pga_aggregate_target must be set before switching to auto mode" Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified Action: before setting workarea_size_policy, set pga_aggregate_target to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (e.g. 500MB) ORA-04033, 00000, "Insufficient memory to grow pool" Cause: The system had insufficient memory to grow the pool to the specified size. Action: Specify a smaller value to grow the pool. / / 4040-4059 Reserved for Stored Procedure errors / ORA-04041, 00000, "package specification must be created first before creating package body" Cause: Attempt to create a package body before creating its package specification. Action: Create the package specification first before creating the package body. ORA-04042, 00000, "procedure, function, package, or package body does not exist" Cause: Attempt to access a procedure, function, package, or package body that does not exist. Action: Make sure the name is correct. ORA-04043, 00000, "object %s does not exist" Cause: An object name was specified that was not recognized by the system. There are several possible causes: - An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. - An attempt was made to rename an index or a cluster, or some other object that cannot be renamed. Action: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.) ORA-04044, 00000, "procedure, function, package, or type is not allowed here" Cause: A procedure, function, or package was specified in an inappropriate place in a statement. Action: Make sure the name is correct or remove it. ORA-04045, 00000, "errors during recompilation/revalidation of %s.%s" Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object. Action: Check the following errors for more information, and make the necessary corrections to the object. ORA-04046, 00000, "results of compilation are too large to support" Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store. Action: Reduce the size of the store procedure by splitting it into smaller stored procedures. ORA-04047, 00000, "object specified is incompatible with the flag specified" Cause: The object type implied by the flag does not match the type of object specified. Action: Specify the correct object, or use the appropriate flag ORA-04050, 00000, "invalid or missing procedure, function, or package name" Cause: The required procedure, function, or package name is invalid or missing. Action: Specify a valid name. ORA-04051, 00000, "user %s cannot use database link %s.%s" Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC. Action: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request. ORA-04052, 00000, "error occurred when looking up remote object %s%s%s%s%s" Cause: An error has occurred when trying to look up a remote object. Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. ORA-04053, 00000, "error occurred when validating remote object %s%s%s%s%s" Cause: An error has occurred when trying to validate a remote object. Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. ORA-04054, 00000, "database link %s does not exist" Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link. Action: Either use a different database link or create the database link. ORA-04055, 00000, "Aborted: \"%s\" formed a non-REF mutually-dependent cycle with \"%s\"." Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2); Action: Break the cycle (possibly by adding a REF or by using another type). / / 4060-4069 Reserved for Stored Procedure Execution errors / ORA-04060, 00000, "insufficient privileges to execute %s" Cause: Attempt to execute a stored procedure without sufficient privileges. Action: Get necessary privileges. ORA-04061, 00000, "existing state of %s has been invalidated" Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped. Action: Try again; this error should have caused the existing state of all packages to be re-initialized. ORA-04062, 00000, "%s of %s has been changed" Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure. Action: Recompile the caller in order to pick up the new timestamp. ORA-04063, 00000, "%s has errors" Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types. Action: Fix the errors and/or create referenced objects as necessary. ORA-04064, 00000, "not executed, invalidated %s" Cause: Attempt to execute a stored procedure that has been invalidated. Action: Recompile it. ORA-04065, 00000, "not executed, altered or dropped %s" Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure. Action: Recompile its dependents. ORA-04066, 00000, "non-executable object, %s" Cause: Attempt to execute a non-procedure. Action: Make sure that a correct name is given. ORA-04067, 00000, "not executed, %s does not exist" Cause: Attempt to execute a non-existent stored procedure. Action: Make sure that a correct name is given. ORA-04068, 00000, "existing state of packages%s%s%s has been discarded" Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure. Action: Try again after proper re-initialization of any application's state. / / 4070-4099 Reserved for Trigger errors / ORA-04070, 00000, "invalid trigger name" Cause: An invalid trigger name was specified. Action: Verify that trigger name is not a reserved keyword. ORA-04071, 00000, "missing BEFORE, AFTER or INSTEAD OF keyword" Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause. Action: Specify either BEFORE, AFTER or INSTEAD OF. ORA-04072, 00000, "invalid trigger type" Cause: An invalid trigger type was given. Action: Specify either INSERT, UPDATE or DELETE. ORA-04073, 00000, "column list not valid for this trigger type" Cause: A column list was specified for a non-update trigger type. Action: Remove the column list. ORA-04074, 00000, "invalid REFERENCING name" Cause: An invalid name was given in the referencing clause. Action: Verify the referencing name is not a reserved word. ORA-04075, 00000, "invalid trigger action" Cause: An statement was given for the trigger action. Action: Re-specify the trigger action. ORA-04076, 00000, "invalid NEW or OLD specification" Cause: An invalid NEW or OLD specification was given for a column. Action: Re-specify the column using the correct NEW or OLD specification. ORA-04077, 00000, "WHEN clause cannot be used with table level triggers" Cause: The when clause can only be specified for row level triggers. Action: Remove the when clause or specify for each row. ORA-04078, 00000, "OLD and NEW values cannot be identical" Cause: The referencing clause specifies identical values for NEW and OLD. Action: Re-specify either the OLD or NEW referencing value. ORA-04079, 00000, "invalid trigger specification" Cause: The create TRIGGER statement is invalid. Action: Check the statement for correct syntax. ORA-04080, 00000, "trigger '%s' does not exist" Cause: The TRIGGER name is invalid. Action: Check the trigger name. ORA-04081, 00000, "trigger '%s' already exists" Cause: The TRIGGER name or type already exists. Action: Use a different trigger name or drop the trigger which is of the same name. ORA-04082, 00000, "NEW or OLD references not allowed in table level triggers" Cause: The trigger is accessing "new" or "old" values in a table trigger. Action: Remove any new or old references. ORA-04083, 00000, "invalid trigger variable '%*.s'" Cause: The variable referenced in the trigger body is invalid. Action: See the manual for valid trigger variable types. ORA-04084, 00000, "cannot change NEW values for this trigger type" Cause: New trigger variables can only be changed in before row insert or update triggers. Action: Change the trigger type or remove the variable reference. ORA-04085, 00000, "cannot change the value of an OLD reference variable" Cause: Old values can only be read and not changed. Action: Do not attempt to change an old variable. ORA-04086, 00000, "trigger description too long, move comments into triggering code" Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the pl/sql code executed for the trigger. Action: If the trigger description contains a large comment, move that comment into the pl/sql code for the trigger. ORA-04087, 00000, "cannot change the value of ROWID reference variable" Cause: Rowid's can only be read and not changed. Action: Do not attempt to change an rowid value. ORA-04088, 00000, "error during execution of trigger '%s.%s'" Cause: A runtime error occurred during execution of a trigger. Action: Check the triggers which were involved in the operation. ORA-04089, 00000, "cannot create triggers on objects owned by SYS" Cause: An attempt was made to create a trigger on an object owned by SYS. Action: Do not create triggers on objects owned by SYS. ORA-04090, 00000, "'%s' specifies same table, event and trigger time as '%s'" Cause: Trigger is of duplicate event and trigger time. Action: Combine the triggering information into one trigger which is fired at the given time. ORA-04091, 00000, "table %s.%s is mutating, trigger/function may not see it" Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it. Action: Rewrite the trigger (or function) so it does not read that table. ORA-04092, 00000, "cannot %s in a trigger" Cause: A trigger attempted to commit or rollback. Action: Rewrite the trigger so it does not commit or rollback. ORA-04093, 00000, "references to columns of type LONG are not allowed in triggers" Cause: A trigger attempted to reference a long column in the triggering table. Action: Do not reference the long column. ORA-04094, 00000, "table %s.%s is constraining, trigger may not modify it" Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement. ORA-04095, 00000, "trigger '%s' already exists on another table, cannot replace it" Cause: Cannot replace a trigger which already exists on a different table than the one being replaced. Action: Drop the trigger with the same name and re-create it. ORA-04096, 00000, "trigger '%s' has a WHEN clause which is too large, limit 2K" Cause: A trigger's 'when' clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size. Action: Use a smaller 'when' clause. Note, the trigger body could be used to perform the same limiting action as the 'when' clause. ORA-04097, 00000, "DDL conflict while trying to drop or alter a trigger" Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table. Action: Investigate the new state of the trigger and retry the DDL operation, if still appropriate. ORA-04098, 00000, "trigger '%s.%s' is invalid and failed re-validation" Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger. Action: Options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger. ORA-04099, 00000, "trigger '%s' is valid but not stored in compiled form" Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release. Action: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done. / / MODIFIED / mvemulap 03/08/01 - bug 1554027 fix / mxyang 02/28/01 - update 6514 / kumamage 02/15/01 - / kumamage 02/08/01 - add message for sftdel / arhee 10/26/00 - add new error message for resmgr / mxyang 08/11/00 - 6592: CASE not found / mvemulap 07/19/00 - native compiler messages / asethi 06/23/00 - 6540: pipelined execution of PL/SQL functions / arhee 06/19/00 - add mesg for exceeded max est exec time / arhee 06/07/00 - fix error mesg 7454 / arhee 03/28/00 - add error msg 7454 / hbergh 03/28/00 - 993307: merge Compaq Tru64 message / nle 07/22/99 - swap error message number / nle 06/29/99 - dynamic returning clause / varora 07/06/99 - change 6576 error message / nle 06/01/99 - reserve message for runtime / nle 05/28/99 - bug 890206 / astocks 05/25/99 - PL/SQL profiler errors / kmuthukk 10/12/98 - raise err for OPEN on non-queries / rdecker 09/22/98 - add substitute character to 6502 for sub msgs / alui 08/28/98 - Reserved error range 04930-04999 for Digital Unix. / arhee 07/23/98 - fix resmgr error msgs / arhee 04/13/98 - add dbscheduling messages / nikeda 04/07/98 - Add plsql error message for Pro* external procedures / kmuthukk 04/07/98 - update purity error / rtaranto 04/07/98 - Add 6538 for purity violations / rtaranto 04/07/98 - Add errors 6536/6537 for in/out binds / kmuthukk 02/24/98 - null dynamic statement / mluong 03/20/98 - fix comp error / kmuthukk 03/30/98 - pending autonmous transaction rolled back / varora 03/28/98 - add duplicate bind error for CALL / arhee 03/17/98 - add message for database scheduling / kquinn 03/18/98 - Add message 7345 / jsarma 03/10/98 - Add OER 7451-55 / varora 02/01/98 - add errors for call method statement / agreenbl 10/30/97 - Rename 7302 --> 7305 to match 8.0.x / agreenbl 06/27/97 - Remove obsolete sm errors / mluong 06/24/97 - merge from 803 / anolan 05/21/97 - checkout / anolan 05/14/97 - Demo. / kmuthukk 04/14/97 - restrict access of SR pkgs in triggers (b496997) / usundara 12/31/96 - incomplete and mutually-dependent types / o add ora-6545 for pl/sql error handling) / bcchang 12/20/96 - error.msg split / / / Trigger errors continued at 25000-25099 / / 4100-4499 Reserved for MVS OSD errors / / 4500-4899 Reserved for CMS OSD errors / / 4900-4929 Reserved for ICL DRS6000 / / 4930-4999 Reserved for Digital Unix / / 5000-5899 Reserved for OEM OSD errors / / 5900-5999 Reserved for Wang OSD errors (OEM: GABA) / / 6000-6499 Reserved for SQL*Net errors / / NETASY: 6000-6029 SQL*Net ASYNC Driver errors / / / Digital Unix specific errors (04930 - 04999). / This error range is used, starting from release 8.0.6, and 8.1.5. / The DEC specific errors 08324-08329 in e7500.msg are now listed here / as 04930 - 04935,04940. / ORA-04930, 00000, "open sequence number failed or initial state is valid" Cause: Either Shared Sequence Number OS 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 OS command ps -ef|grep <instance_name>. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown 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. ORA-04931, 00000, "unable to set initial sequence number value" 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. ORA-04932, 00000, "increment or adjust of sequence number failed" 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. ORA-04933, 00000, "initial service identifier is non-zero" Cause: A valid service identifier existed before the sequence number service was opened. Action: Verify that the instance is completely shut down. ORA-04934, 00000, "unable to obtain the current sequence number" 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. ORA-04935, 00000, "unable to get/convert SCN recovery lock" 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. ORA-04940, 00000, "unsupported optimization of Oracle binary, check alert log for more info" 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 supported combination of options and restart the instance. ORA-06000, 00000, "NETASY: port open failure" Cause: Autologin unable to open port Action: Check log file for OS-specific error code ORA-06001, 00000, "NETASY: port set-up failure" Cause: Autologin unable to change port attributes Action: Check log file for OS-specific error code ORA-06002, 00000, "NETASY: port read failure" Cause: Autologin unable to read from port Action: Check log file for OS-specific error code ORA-06003, 00000, "NETASY: port write failure" Cause: Autologin unable to write to port Action: Check log file for OS-specific error code ORA-06004, 00000, "NETASY: dialogue file open failure" Cause: Autologin unable to open dialogue file Action: Check connect string for accuracy/typos ORA-06005, 00000, "NETASY: dialogue file read failure" Cause: Autologin unable to read dialogue file Action: Check log file for OS-specific error code ORA-06006, 00000, "NETASY: dialogue execute failure" Cause: Expected response never received Action: None ORA-06007, 00000, "NETASY: bad dialogue format" Cause: Dialogue file contains syntax error Action: Correct the dialogue file ORA-06009, 00000, "NETASY: dialogue filename too long" Cause: Full file spec for dialogue file exceeds 64 bytes Action: Amend connect string accordingly ORA-06010, 00000, "NETASY: dialogue file too long" Cause: Dialogue file exceeds 768 bytes in length Action: Simplify dialogue (e.g. remove comments, redundant white space), or split into two and link with "more" command ORA-06011, 00000, "NETASY: dialogue too long" Cause: One of two: 1. Dialogue contains more than 24 exchange blocks 2. Dialogue send string exceeds 84 bytes in length Action: Simplify dialogue or split into two and link with "more" command ORA-06017, 00000, "NETASY: message receive failure" Cause: Async driver gets I/O error while doing network read operation Action: Check log file for OS-specific error code and contact your customer support representative. ORA-06018, 00000, "NETASY: message send failure" Cause: Async driver gets I/O error while doing network write operation Action: Check log file for OS-specific error code and contact your customer support representative. ORA-06019, 00000, "NETASY: invalid login (connect) string" Cause: Syntax error in login string. Action: Resubmit with correct string. ORA-06020, 00000, "NETASY: initialisation failure" Cause: Async driver unable to complete initialisation Action: Check log file for OS-specific error code ORA-06021, 00000, "NETASY: connect failed" Cause: Async driver unable to establish connection with partner Action: Check log file for OS-specific error code ORA-06022, 00000, "NETASY: channel open failure" Cause: no free channel [should never happen] Action: Contact your customer support representative. ORA-06023, 00000, "NETASY: port open failure" Cause: Async driver unable to open port Action: Check log file for OS-specific error code ORA-06024, 00000, "NETASY: VTM error" Cause: Virtual Terminal Manager unable to read/write to port Action: Check log file for OS-specific error code ORA-06025, 00000, "NETASY: Configuration error" Cause: Async driver genned for server-only, but client service requested Action: Contact your customer support representative. ORA-06026, 00000, "NETASY: port close failure" Cause: Async driver unable to close port Action: Check log file for OS-specific error code ORA-06027, 00000, "NETASY: channel close failure" Cause: Async driver unable to close channel Action: Check log file for OS-specific error code ORA-06028, 00000, "NETASY: unable to intialise for logging" Cause: Async driver unable to initialise for logging I/O Action: Contact your customer support representative. ORA-06029, 00000, "NETASY: port assignment failure" Cause: Async driver unable to assign port to channel [should never happen] Action: Contact your customer support representative. / / NETDNT: 6030-6049 SQL*Net DECnet Driver errors / ORA-06030, 00000, "NETDNT: connect failed, unrecognized node name" Cause: Node name specified in host string is unknown (probably misspelled) Action: Retry with correct node name ORA-06031, 00000, "NETDNT: connect failed, unrecognized object name" Cause: Host string contains reference to object (which doesn't exist): @d:- => object is ORDN; when is VMS, the object is ORDN.COM when is UNIX, the object is ORDN @d:::"task=" => object is; when is VMS, the object is.COM when is UNIX, the object is Action: Retry with correct object name or create the required object on host node ORA-06032, 00000, "NETDNT: connect failed, access control data rejected" Cause: Host string contains invalid username/password Action: Retry with correct username/password ORA-06033, 00000, "NETDNT: connect failed, partner rejected connection" Cause: Connection with partner was made but was rejected. Action: Contact your network administrator. ORA-06034, 00000, "NETDNT: connect failed, partner exited unexpectedly" 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. ORA-06035, 00000, "NETDNT: connect failed, insufficient resources" Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use. Action: Contact your network administrator. ORA-06036, 00000, "NETDNT: connect failed, no response from object" Cause: Action: ORA-06037, 00000, "NETDNT: connect failed, node unreachable" Cause: Host node is down. Action: Contact your network administrator. ORA-06038, 00000, "NETDNT: connect failed, network driver not loaded" Cause: Action: ORA-06039, 00000, "NETDNT: connect failed" Cause: Connect failed for unexpected reason (see OSD error). Action: Contact your customer support representative. ORA-06040, 00000, "NETDNT: invalid login (connect) string" Cause: Syntax error in login string. Action: Resubmit with correct string. ORA-06041, 00000, "NETDNT: disconnect failed" Cause: Driver gets error while doing network close operation Action: Contact your customer support representative. ORA-06042, 00000, "NETDNT: message receive failure" Cause: Driver gets I/O error while doing network read operation Action: Contact your customer support representative. ORA-06043, 00000, "NETDNT: message send failure" Cause: Driver gets I/O error while doing network write operation Action: Contact your customer support representative. ORA-06044, 00000, "NETDNT: connect failed, byte count quota exceeded" Cause: Connect failed because of insufficient byte count quota. Action: Increase byte count quota. / / NETTCP: 06100 - 6149 SQL*Net TCP/IP driver errors / /6100-6101 Reserved. ORA-06102, 00000, "NETTCP: cannot allocate context area" Cause: Insufficient dynamic memory available for connection context area. Action: Contact your customer support representative. /6103-6104 Reserved. ORA-06105, 00000, "NETTCP: remote host is unknown" Cause: Host name specified in the login (connect) string is unknown. Action: Check spelling; make sure name is in the TCP/IP HOST file. ORA-06106, 00000, "NETTCP: socket creation failure" Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. ORA-06107, 00000, "NETTCP: ORACLE network server not found" Cause: No entry in SERVICES file for ORACLE server. Action: Add ("orasrv") entry to the TCP/IP SERVICES file. ORA-06108, 00000, "NETTCP: connect to host failed" 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. ORA-06109, 00000, "NETTCP: message receive failure" Cause: I/O error occurred while attempting network read operation. Action: Contact your customer support representative. ORA-06110, 00000, "NETTCP: message send failure" Cause: I/O error occurred while attempting network write operation. Action: Contact your customer support representative. ORA-06111, 00000, "NETTCP: disconnect failure" Cause: Error occurred while closing a socket. Action: Contact your customer support representative. ORA-06112, 00000, "NETTCP: invalid buffer size" Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096). Action: Re-submit with valid buffer size. ORA-06113, 00000, "NETTCP: Too many connections" Cause: The maximum no. of concurrently open connections has been reached. Action: Exit an application with an open connection which is no longer required. ORA-06114, 00000, "NETTCP: SID lookup failure" 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). ORA-06115, 00000, "NETTCP: unable to create ORACLE logicals" 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. Action: Contact your system administrator. ORA-06116, 00000, "NETTCP: unable to create ORASRV process" 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. ORA-06117, 00000, "NETTCP: unable to create ORASRV: quota exceeded" 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. ORA-06118, 00000, "NETTCP: unable to complete handshake with ORASRV" Cause: The ORACLE server process was started but failed to complete its initialization. Action: Contact your customer support representative. ORA-06119, 00000, "NETTCP: spurious client request" 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 your customer support representative. ORA-06120, 00000, "NETTCP: network driver not loaded" Cause: The TCP/IP network driver is not loaded. Action: Check that the TCP/IP driver is loaded correctly. ORA-06121, 00000, "NETTCP: access failure" 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 your customer support representative. ORA-06122, 00000, "NETTCP: setup failure" 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 your customer support representative. ORA-06123, 00000, "NETTCP: cannot set KEEPALIVE" 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 your customer support representative. ORA-06124, 00000, "NETTCP: timeout waiting for ORASRV" Cause: The ORACLE server process was started but failed to respond after N secs. 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. ORA-06125, 00000, "NETTCP: ORASRV exited unexpectedly" 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_.OUT Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative. ORA-06126, 00000, "NETTCP: ORASRV unable to open network connection" Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV. Action: Contact your customer support representative. ORA-06127, 00000, "NETTCP: unable to change username" 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). Action: Create new user account on host. ORA-06128, 00000, "NETTCP: unable to create mailbox" 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 your customer support representative. ORA-06129, 00000, "NETTCP: unable to transfer socket ownership to ORASRV" 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 your customer support representative. ORA-06130, 00000, "NETTCP: host access denied" 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. ORA-06131, 00000, "NETTCP: user access denied" 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. ORA-06132, 00000, "NETTCP: access denied, wrong password" 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. ORA-06133, 00000, "NETTCP: file not found" 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. ORA-06134, 00000, "NETTCP: file access privilege violation" 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. ORA-06135, 00000, "NETTCP: connection rejected; server is stopping" Cause: The host's SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping. Action: Re-start SQL*Net TCP/IP server. ORA-06136, 00000, "NETTCP: error during connection handshake" 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 your customer support representative. ORA-06137, 00000, "NETTCP: error during connection handshake" 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 your customer support representative. ORA-06138, 00000, "NETTCP: error during connection handshake" 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 your customer support representative. /6139 Reserved. ORA-06140, 00000, "NETTCP: no such user" Cause: A proxy login connect attempt failed because the client username has no counterpart on the host. Action: ORA-06141, 00000, "NETTCP: no privilege for user" 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 privilges. ORA-06142, 00000, "NETTCP: error getting user information" 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 your customer support representative. ORA-06143, 00000, "NETTCP: maximum connections exceeded" Cause: The connect failed because the maximum conncurrent connections supported by the host's SQL*Net TCP/IP server has already been reached. Action: Wait for a short period and re-try. ORA-06144, 00000, "NETTCP: SID (database) is unavailable" Cause: The database administrator on the host has varied the SID offline. Action: Wait for it to be varied back on-line. ORA-06145, 00000, "NETTCP: unable to start ORASRV: images not installed" 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. /6146-6149 Reserved. / / TWOTASK: 06200 - 06219 VMS Two-Task driver errors / ORA-06200, 00000, "TWOTASK: connect failed, can't create mailbox" Cause: Action: ORA-06201, 00000, "TWOTASK: connect failed, can't attach to mailbox" Cause: Action: ORA-06202, 00000, "TWOTASK: connect failed, can't spawn ORASRV process" Cause: Action: ORA-06203, 00000, "TWOTASK: connect failed, handshake failure" Cause: Action: ORA-06204, 00000, "TWOTASK: connect failed, can't access ORASRV2.COM" Cause: Action: ORA-06205, 00000, "TWOTASK: connect failed, can't create logical name" Cause: Action: ORA-06206, 00000, "TWOTASK: message receive failure" Cause: Action: ORA-06207, 00000, "TWOTASK: message send failure" Cause: Action: ORA-06208, 00000, "TWOTASK: invalid login (connect) string" Cause: Action: ORA-06209, 00000, "TWOTASK: connect failed, mailbox already exists" Cause: Action: ORA-06210, 00000, "TWOTASK: connect failed, ORASRV exited unexpectedly" Cause: Action: ORA-06211, 00000, "TWOTASK: connect failed, timeout waiting for ORASRV" Cause: Action: ORA-06212, 00000, "TWOTASK: connect failed, logical name table is full" Cause: Action: ORA-06213, 00000, "TWOTASK: connect failed" Cause: Action: ORA-06214, 00000, "TWOTASK: connect failed, insufficient quotas to create ORASRV" Cause: Action: ORA-06215, 00000, "TWOTASK: connect failed, ORASRV protected image not installed" Cause: Action: ORA-06216, 00000, "TWOTASK: connect failed, can't find ORASRV image file" Cause: Action: /6217-6219 Reserved. / / NETNTT: 6250 - 6274 SQL*Net nCUBE Two-Task errors / ORA-06250, 00000, "NETNTT: cannot allocate send and receive buffers" 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. ORA-06251, 00000, "NETNTT: cannot translate address file name" Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-06252, 00000, "NETNTT: cannot open address file" 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. ORA-06253, 00000, "NETNTT: cannot read arguments from address file" 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. ORA-06254, 00000, "NETNTT: cannot share connection to cube" 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. ORA-06255, 00000, "NETNTT: cannot read pid of remote process" Cause: An error occurred while reading the NTT communications link. Action: Contact your customer support representative. ORA-06256, 00000, "NETNTT: remote fork failed" 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 doesn't have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance. ORA-06257, 00000, "NETNTT: cannot send command line to shadow process" Cause: An error occurred while writing the NTT communications link. Action: Contact your customer support representative. ORA-06258, 00000, "NETNTT: cannot allocate context area" 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. ORA-06259, 00000, "NETNTT: cannot read from remote process" Cause: An error occurred while reading the NTT communications link. Action: Contact your customer support representative. ORA-06260, 00000, "NETNTT: cannot write to remote process" Cause: An error occurred while writing the NTT communications linke. Action: Contact your customer support representative. ORA-06261, 00000, "NETNTT: nrange() failed" Cause: The call to 'nrange()' failed while attempting to establish a connection. Action: Contact your customer support representative. ORA-06262, 00000, "NETNTT: nfconn() failed" Cause: The call to 'nfconn()' failed while attempting to establish a connection. Action: Contact your customer support representative. ORA-06263, 00000, "NETNTT: out of memory in pi_connect" 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. ORA-06264, 00000, "NETNTT: data protocol error" Cause: The NTT two-task driver received an unexpected message type." Action: Contact your customer support representative. ORA-06265, 00000, "NETNTT: break protocol error" Cause: The NTT two-task driver received an unexpected message type." Action: Contact your customer support representative. ORA-06266, 00000, "NETNTT: bad write length" Cause: The NTT two-task driver failed on an internal consistency check. Action: Contact your customer support representative. ORA-06267, 00000, "NETNTT: bad state" Cause: The NTT two-task driver failed on an internal consistency check. Action: Contact your customer support representative. ORA-06268, 00000, "NETNTT: cannot read /etc/oratab" 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. /6268-6274 Reserved / / IPA: 6300 - 6323 SQL*Net IPA errors / ORA-06300, 00000, "IPA: Disconnect failure" 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 your customer support representative. ORA-06301, 00000, "IPA: Cannot allocate driver context" Cause: The memory pool is exhausted. Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry. ORA-06302, 00000, "IPA: Cannot connect to remote host" 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 Action: Check sequentially for the above causes and eliminate the actual cause found. ORA-06303, 00000, "IPA: Message send error" 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. ORA-06304, 00000, "IPA: Message receive error" 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. ORA-06305, 00000, "IPA: Illegal message type" Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued. Action: Contact your customer support representative. ORA-06306, 00000, "IPA: Message write length error" Cause: The IPA driver tried to write a message in the queue that was too big for the queue. Action: Contact your customer support representative. ORA-06307, 00000, "IPA: Cannot reset connection" Cause: A fatal error occurred during the resetting of the connection. Action: Contact your customer support representative. ORA-06308, 00000, "IPA: No more connections available" Cause: You have exhausted all your connections. Action: Try again when some of the current users have logged off. ORA-06309, 00000, "IPA: No message queue available" Cause: The SQL*Net IPA servers have not been started. Action: Run ipactl. ORA-06310, 00000, "IPA: Environment variable(s) not set" Cause: Environment variable(s) not set correctly. Action: Check and correct. ORA-06311, 00000, "IPA: Maximum number of servers reached" Cause: Maximum number of servers reached. Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links. ORA-06312, 00000, "IPA: Incorrect outgoing service name supplied" Cause: Incorrect outgoing service name supplied. Action: Check and correct the service name. ORA-06313, 00000, "IPA: Shared memory failed to initialise" Cause: The shared memory has not been set up correctly. Action: Contact your system manager. ORA-06314, 00000, "IPA: Event set up failure" Cause: Fatal interprocess communication error. Action: Contact your system manager. ORA-06315, 00000, "IPA: Invalid connect string" Cause: The connect string is malformed. Action: Check and correct. ORA-06316, 00000, "IPA: Invalid database SID" 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. ORA-06317, 00000, "IPA: Local maximum number of users exceeded" 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 manager. ORA-06318, 00000, "IPA: Local maximum number of connections exceeded" 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 manager. ORA-06319, 00000, "IPA: Remote maximum number of users exceeded" 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 manager. ORA-06320, 00000, "IPA: Remote maximum number of connections exceeded" 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 manager. ORA-06321, 00000, "IPA: Cannot reach 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. Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied. ORA-06322, 00000, "IPA: Fatal shared memory error" Cause: An internal error has occurred in the shared memory handling. Action: Contact customer support. ORA-06323, 00000, "IPA: Cause event error" Cause: Fatal interprocess communication error. Action: Contact your system manager. / / NETCMN: 6400 - 6429 SQL*Net CoMmoN errors / ORA-06400, 00000, "NETCMN: No default host string specified" Cause: There was no default host string specified in the configuration and the user didn't specify any explicit connect string. Action: Either reconfigure the system specifying a default connect string or use an explicit connect string. ORA-06401, 00000, "NETCMN: invalid driver designator" Cause: The login (connect) string contains an invalid driver designator. Action: Correct the string and re-submit. ORA-06402, 00000, "NETCMN: error receiving break message" Cause: Error occurred while attempting to read a break message. Action: Contact your customer support representative. ORA-06403, 00000, "Unable to allocate memory." Cause: System unable to allocate needed virtual memory. Action: Configure more memory, reduce load, or simply try again. ORA-06404, 00000, "NETCMN: invalid login (connect) string" Cause: Syntax error in login string. Action: Correct string and re-submit. ORA-06405, 00000, "NETCMN: reset protocol error" Cause: Unable to reset out of break state. Action: Contact your customer support representative. ORA-06406, 00000, "NETCMN: error sending break message" Cause: Error occurred while attempting to send a break message. Action: Contact your customer support representative. ORA-06407, 00000, "NETCMN: unable to set up break handling environment" Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages. Action: Contact your customer support representative. ORA-06408, 00000, "NETCMN: incorrect message format" Cause: Message from partner contains bad header. Action: Contact your customer support representative. /6409-6412 Reserved. ORA-06413, 00000, "Connection not open." Cause: Unable to establish connection. Action: Use diagnostic procedures to ascertain exact problem. /6414-6415 Reserved. ORA-06416, 00000, "NETCMN: error on test" Cause: Error occurred while testing I/O status of the network connection. Action: Contact your customer support representative. /6417-6429 Reserved. /6418 Unused ORA-06419, 0000, "NETCMN: server can not start oracle" 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. ORA-06420, 0000, "NETCMN: SID lookup failure" 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). ORA-06421, 0000, "NETCMN: Error detected in the read-in data" Cause: Error found during recomputation of checksum or CRC. Action: Possible hardware failures of communication nodes. Contact system administrator immediately. ORA-06422, 0000, "NETCMN: Error in sending data" Cause: Unable to transmit data to remote host. Action: Try reconnect to remote host, and contact your system administrator. ORA-06423, 0000, "NETCMN: Error in receiving data" Cause: Unable to receive data from remote host. Action: Try reconnect to remote host, and contact your system administrator. / / 6430-6449 Reserved for NCR System 3000 / ORA-06430, 0000, "ssaio: Seals do not match" Cause: A function was called with an invalid argument. Action: Contact your Oracle Customer Support Representative. ORA-06431, 0000, "ssaio: Invalid Block number" 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 your Oracle Customer Support Representative. ORA-06432, 0000, "ssaio: Buffer Not Aligned" Cause: The I/O buffer was not aligned on a 2K boundary. Action: Contact your Oracle Customer Support Representative. ORA-06433, 0000, "ssaio: LSEEK error, unable to seek to requested block." 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. ORA-06434, 0000, "ssaio: read error, unable to read requested block from database file." 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. ORA-06435, 0000, "ssaio: write error, unable to write requested block to database file." 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. ORA-06436, 0000, "ssaio: asynchronous I/O failed due to incorrect parameters." 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. ORA-06437, 0000, "ssaio: the asynchronous write was unable to write to the database file." 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. ORA-06438, 0000, "ssaio: the asynchronous read was unable to read from the database file." 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. ORA-06439, 0000, "ssaio: the asynchronous write returned incorrect number of bytes" 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. ORA-06440, 0000, "ssaio: the asynchronous read returned incorrect number of bytes" 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. ORA-06441, 0000, "ssvwatev: Incorrect parameter passed to function call" 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. ORA-06442, 0000, "ssvwatev: Failed with unexpected error number." Cause: Some system problems may exists on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06443, 0000, "ssvpstev: Incorrect parameter passed to function call" Cause: An invalid event ID is passed in to this routine. Action: The additional information indicates the event id. ORA-06444, 0000, "ssvpstev: Failed with unexpected error number." Cause: Some system problems may exist on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06445, 0000, "ssvpstevrg: Incorrect parameters passed to function call" 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. ORA-06446, 0000, "ssvpstevrg: Failed with unexpected error number." Cause: Some system problems may exist on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06447, 0000, "ssvpstp: Incorrect parameter passed to function call" Cause: Invalid oracle process ID is passed in to this routine. Action: The additional information indicates the process id. ORA-06448, 0000, "ssvpstp: Failed with unexpected error number." Cause: Some system problems may exists on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06449, 0000, "The list IO or the sysvendor is not installed." 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 don't want to use this interface or link the UNIX kernel with this interface so that ORACLE can use it. / / 6500-6599 PL/SQL Errors / / 6500-6539 are signalled by PL/SQL and owned by PL/SQL's peiexc.h / file. 6540-6549 are signalled by PL/SQL and are used for PL/SQL / error handling and appear in pcmdef.h. 6550-6599 are used by the / RDBMS to signal PL/SQL related errors and do not appear in PL/SQL's / peiexc.h file. / ORA-06500, 00000, "PL/SQL: storage error" Cause: Action: ORA-06501, 00000, "PL/SQL: program error" Cause: Action: ORA-06502, 00000, "PL/SQL: numeric or value error%s" Cause: Action: ORA-06503, 00000, "PL/SQL: Function returned without value" 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. ORA-06504, 00000, "PL/SQL: Return types of Result Set variables or query do not match" 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. ORA-06505, 00000, "PL/SQL: variable requires more than 32767 bytes of contiguous memory" 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. ORA-06508, 00000, "PL/SQL: could not find program unit being called" Cause: Action: ORA-06509, 00000, "PL/SQL: ICD vector missing for this package" Cause: Action: ORA-06510, 00000, "PL/SQL: unhandled user-defined exception" 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 DBA. ORA-06511, 00000, "PL/SQL: cursor already open" Cause: An attempt was made to open a cursor that was already open. Action: Close cursor first before reopening. ORA-06512, 00000, "at %sline %s" 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 DBA. ORA-06513, 00000, "PL/SQL: index for PL/SQL table out of range for host language array" 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 don't use index values less than 1. ORA-06514, 00000, "PL/SQL: The remote call cannot be handled by the server" 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 version that supports this. ORA-06515, 00000, "PL/SQL: unhandled exception %s" 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 DBA. *Comment: The exception was created via a pragma exception_init with a value larger than MAX_OEN. This capability exists for backward compatibility with V1 PL/SQL. ORA-06516, 00000, "PL/SQL: the Probe packages do not exist or are invalid" 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. *Comment: catproc.sql should load Probe by default, but it did not do so in releases prior to 7.3.3. ORA-06517, 00000, "PL/SQL: Probe error - %s" Cause: An error occurred while passing a Probe operation to the server for execution. Action: Refer to the entry for the embedded error message. *Comment: The error is most likely a UPI or network problem. The Probe error is just to let the user know how the error arose. ORA-06518, 00000, "PL/SQL: Probe version %s incompatible with version %s" 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. *Comment: This error is not currently expected. It will only occur at a later time if incompatible Probe changes are introduced. ORA-06519, 00000, "active autonomous transaction detected and rolled back" 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. ----------------------------------------------------------------------- 06520 through 06529 reserved for Foreign function errors ORA-06520, 00000, "PL/SQL: Error loading external library" 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. ORA-06521, 00000, "PL/SQL: Error mapping function" 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. ORA-06522, 00000, "%s" Cause: ORA-06520 or ORA-065211 could stack this error with a system specific error string. Action: This error string should give the cause for errors ORA-06520 or ORA-065211 ORA-06523, 00000, "Maximum number of arguments exceeded" 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. ORA-06524, 00000, "Unsupported option : %s" Cause: The option specified is an unsupported feature for external procedures. Action: Correct the syntax in the external specification ORA-06525, 00000, "Length Mismatch for CHAR or RAW data" 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. Action: Correct the external procedure code and set the length variable correctly. ORA-06526, 00000, "Unable to load PL/SQL library" 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 customer support. ORA-06527, 00000, "External procedure SQLLIB error: %s" Cause: An error occurred in sqllib during execution of a Pro* external procedure. Action: The message text indicates the actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes manual for a complete description of the error message and follow the appropriate action. ORA-06528, 00000, "Error executing PL/SQL profiler" Cause: An error occurred in during execution of a PL/SQL profiler procedure. Action: Check the stacked errors for more details. ORA-06529, 00000, "Version mismatch - PL/SQL profiler" 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 ORA-06530, 00000, "Reference to uninitialized composite" 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. ORA-06531, 00000, "Reference to uninitialized collection" 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. ORA-06532, 00000, "Subscript outside of limit" 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. ORA-06533, 00000, "Subscript beyond count" 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. ORA-06534, 00000, "cannot access Serially Reusable package %s in the context of a trigger" 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. ORA-06535, 00000, "statement string in %s is NULL or 0 length" 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. ORA-06536, 00000, "IN bind variable bound to an OUT position" 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. ORA-06537, 00000, "OUT bind variable bound to an IN position" 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. ORA-06538, 00000, "statement violates %s RESTRICT_REFERENCES pragma" 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. ORA-06539, 00000, "target of OPEN must be a query" 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. -------------------------------------------------------- 06540 through 06549 reserved for pl/sql error handling ORA-06540, 00000, "PL/SQL: compilation error" 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. ORA-06541, 00000, "PL/SQL: compilation error - compilation aborted" 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. ORA-06542, 00000, "PL/SQL: execution error" Currently unused. Reserved for future use. ORA-06543, 00000, "PL/SQL: execution error - execution aborted" ORA-06544, 00000, "PL/SQL: internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" Cause: A pl/sql internal error occurred. Action:Report as a bug; the first argument is the internal error nuber. ORA-06545, 00000, "PL/SQL: compilation error - compilation aborted" 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. Action:See accompanying PLS-nnnnn error messages. ORA-06546, 00000, "DDL statement is executed in an illegal context" 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 Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement. ORA-06547, 00000, "RETURNING clause must be used with INSERT, UPDATE, or DELETE statements" Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only. Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use USING clause instead. ORA-06548, 00000, "no more rows needed" 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. ORA-06549, 00000, "PL/SQL: failed to dynamically open shared object (DLL): %s" Cause: One possible cause might be there are too many DLLs open at the same time. Action: -------------------------------------------------------- ORA-06550, 00000, "line %s, column %s:\n%s" Cause: Usually a PL/SQL compilation error. Action: ORA-06551, 00000, "PL/SQL: Unhandled exception" Cause: Action: ORA-06552, 00000, "PL/SQL: %s" Cause: Action: ORA-06553, 00000, "PLS-%s: %s" Cause: Action: ORA-06554, 00000, "package DBMS_STANDARD must be created before using PL/SQL" 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. ORA-06555, 00000, "this name is currently reserved for use by user SYS" Cause: You tried 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. ORA-06556, 00000, "the pipe is empty, cannot fulfill the unpack_message request" 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. ORA-06557, 00000, "null values are not allowed for any parameters to pipe icd's" Cause: Internal error from the dbms_pipe package. Action: ORA-06558, 00000, "buffer in dbms_pipe package is full. No more items allowed" Cause: The pipe buffer size has been exceeded. Action: ORA-06559, 00000, "wrong datatype requested, %s, actual datatype is %s" 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. Action: Check that the sender and receiver agree on the number and types of items placed on the pipe. ORA-06560, 00000, "pos, %s, is negative or larger than the buffer size, %s" Cause: Internal error from the dbms_pipe package. Action: ORA-06561, 00000, "given statement is not supported by package DBMS_SQL" Cause: Attempting 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. ORA-06562, 00000, "type of out argument must match type of column or bind variable" 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. 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. ORA-06563, 00000, "top level procedure/function specified, cannot have subparts" 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 don't 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. ORA-06564, 00000, "object %s does not exist" 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. ORA-06565, 00000, "cannot execute %s from within stored procedure" 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. ORA-06566, 00000, "invalid number of rows specified" 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. ORA-06567, 00000, "invalid number of values specified" 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. Action: Make sure that the same number of values have been bound for all of the bind variables. ORA-06568, 00000, "obsolete ICD procedure called" 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. 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. ORA-06569, 00000, "Collection bound by bind_array contains no elements" 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. Action: Fill the collection with the elements you want to bind and try the bind call again. / / ORA-06570, 00000, "shared pool object does not exist, cannot be pinned" 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) Action: Remove the procedure from the calling stored procedure. / / 6571-6579 Reserved for Plsql functions called from Sql / ORA-06571, 00000, "Function %s does not guarantee not to update database" 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. Action: If the referenced function is a packaged, PL/SQL function: Recreate 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 a stand-alone, PL/SQL function: Do not use the function. ORA-06572, 00000, "Function %s has out arguments" 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. Action: Recreate the PL/SQL function without the OUT parameter in the argument list. ORA-06573, 00000, "Function %s modifies package state, cannot be used here" 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. Action: If the function is a packaged, PL/SQL function: Recreate the function and include a pragma containing the 'Write no Package State' (WNPS). If the function is a stand-alone, PL/SQL function: Delete the function from the SQL statement. ORA-06574, 00000, "Function %s references package state, cannot execute remotely" 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. Action: If the function is a packaged function: Recreate 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 stand-alone function: Do not call the function. ORA-06575, 00000, "Package or function %s is in an invalid 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. Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object. ORA-06576, 00000, "not a valid function or procedure name" 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 ORA-06577, 00000, "output parameter not a bind variable" 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 ORA-06578, 00000, "output parameter cannot be a duplicate bind" 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 / ORA-06580, 00000, "Hash Join ran out of memory while keeping large rows in memory" 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. Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increaed. / / 6581-6591 Reserved for European OEM Ports (contact: egroenen.nl) / ORA-06592, 00000, "CASE not found while executing CASE statement" Cause: A CASE statement must either list all possible cases or have an else clause. Action: Add all missing cases or an else clause. / / 6600-6699 Reserved for more SQL*Net errors / / 6700-6899 Reserved for TLI SQL*NET driver errors / / 6900-6999 Reserved for more SQL*Net errors / / / 6600 - 6622: SQL*Net LU6.2 driver errors / ORA-06600, 00000, "LU6.2 Driver: SNA software is not loaded" Cause: The SNA software is not running. Action: Start the SNA software and try again. ORA-06601, 00000, "LU6.2 Driver: Invalid database ID string" Cause: The database string in the connect was invalid. Action: Provide a valid database string, as defined in documentation. ORA-06602, 00000, "LU6.2 Driver: Error allocating context area" Cause: Context area failure. Action: Contact your local service representative. ORA-06603, 00000, "LU6.2 Driver: Error allocating memory" Cause: Operating system refused request for memory. Action: Contact you local service representative. ORA-06604, 00000, "LU6.2 Driver: Unable to allocate session with remote LU" 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. ORA-06605, 00000, "LU6.2 Driver: Unexpected line turnaround" Cause: SNA software switched from send to receive unexpectedly. Action: Check the SNA configuration data, particularly parameters associated with a session. ORA-06606, 00000, "LU6.2 Driver: Unexpected response from SNA" 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. ORA-06607, 00000, "LU6.2 Driver: Reset occurred in send state" Cause: A reset was issued whilst in send state. Action: Check the SNA LOG data, if relevent, for further information. ORA-06608, 00000, "LU6.2 Driver: Reset occurred in receive state" Cause: A reset was received from the partner whilst in receive state. This may be because the partner deallocated. Action: Check the SNA LOG data, if relevent, for further information. / / 06609 is not used by the LU6.2 Driver. / ORA-06610, 00000, "LU6.2 Driver: Failed during deallocation" Cause: LU6.2 driver was unable to deallocate gracefully. Action: Check the reason for deallocation. Consult the SNA LOG data. ORA-06611, 00000, "LU6.2 Driver: Request to send error" Cause: Action: ORA-06612, 00000, "LU6.2 Driver: Send data error" Cause: Action: ORA-06613, 00000, "LU6.2 Driver: Receive and wait error" Cause: Action: ORA-06614, 00000, "LU6.2 Driver: Receive Immediate error" Cause: Action: ORA-06615, 00000, "LU6.2 Driver: Send error" Cause: Action: ORA-06616, 00000, "LU6.2 Driver: Attach to LU failed" 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. ORA-06617, 00000, "LU6.2 Driver: Attach to PU failed" Cause: Action: ORA-06618, 00000, "LU6.2 Driver: Activation of subnetwork failed" Cause: Action: ORA-06619, 00000, "LU6.2 Driver: Unable to activate remote partner" Cause: Action: ORA-06620, 00000, "LU6.2 Driver: Invalid remote partner" Cause: Action: ORA-06621, 00000, "LU6.2 Driver: Allocation error" Cause: Action: ORA-06622, 00000, "LU6.2 Driver: Unable to attach to SNA" 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. / / 6700-6899 Reserved for TLI SQL*NET driver errors / ORA-06700, 00000, "TLI Driver: incorrect message type from host" Cause: TLI received a message with an unrecognizable message type. Action: Contact your customer support representative. ORA-06701, 00000, "TLI Driver: incorrect number of bytes written" 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 your customer support representative. ORA-06702, 00000, "TLI Driver: cannot allocate context area" Cause: TLI could not allocate heap space for the context area. Action: Contact your customer support representative. ORA-06703, 00000, "TLI Driver: send break message failed" Cause: TLI failed to send a break message across the connection. Action: Contact your customer support representative. ORA-06704, 00000, "TLI Driver: receive break message failed" Cause: TLI failed to receive an expected break message. Action: Contact your customer support representative. ORA-06705, 00000, "TLI Driver: remote node is unknown" Cause: TLI could not find your remote host information. Action: Make sure you specified the hostname correctly on the command line. (Also, check your capitalization and spelling.) ORA-06706, 00000, "TLI Driver: service not found" 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 adminstrator to add it. ORA-06707, 00000, "TLI Driver: connection failed" 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 section "orasrv Messages" for the specific cause and action. ORA-06708, 00000, "TLI Driver: message receive failure" Cause: TLI encountered an error receiving a message from the communication channel. Action: Contact your customer support representative. ORA-06709, 00000, "TLI Driver: message send failure" Cause: TLI encountered an error sending a message across the communication channel. Action: Contact your customer support representative. ORA-06710, 00000, "TLI Driver: send interrupt break message failed" Cause: TLI failed to send a break message while handling an interrupt signal from the user. Action: Contact your customer support representative. ORA-06711, 00000, "TLI Driver: error on bind" Cause: TLI failed to assign a network address to the communication channel. Action: Contact your customer support representative. ORA-06712, 00000, "TLI Driver: error on accept" Cause: TLI failed to accept a connection request from the client. Action: Contact your customer support representative. ORA-06713, 00000, "TLI Driver: error on connect" 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. ORA-06720, 00000, "TLI Driver: SID lookup failure" 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. ORA-06721, 00000, "TLI Driver: spurious client req" Cause: The remote TLI server received an undefined request. Action: Contact your customer support representative. ORA-06722, 00000, "TLI Driver: connection setup failure" Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message. Action: Contact your customer support representative. ORA-06730, 00000, "TLI Driver: unable to open clone device" Cause: TLI failed to open the Streams clone device associated with the transport provider. Action: Contact your customer support representative. ORA-06731, 00000, "TLI Driver: cannot alloc t_call" Cause: TLI cannot allocate space for the client's connection information. Action: Contact your customer support representative. ORA-06732, 00000, "TLI Driver: cannot alloc t_discon" Cause: TLI cannot allocate space for the client's disconnection information. Action: Contact your customer support representative. ORA-06733, 00000, "TLI Driver: failed to receive disconnect" Cause: TLI failed to receive an expected disconnection message during connection release. Action: Contact your customer support representative. ORA-06734, 00000, "TLI Driver: cannot connect" Cause: TLI failed to connect the client to the remote server. Action: Check that the remote TLI server is running. ORA-06735, 00000, "TLI Driver: client failed to close error conn" Cause: TLI failed to properly close a connection after an error was received. Action: Contact your customer support representative. ORA-06736, 00000, "TLI Driver: server not running" 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 adminstrator to start it. ORA-06737, 00000, "TLI Driver: connection failed" 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. ORA-06741, 00000, "TLI Driver: unable to open protocol device" Cause: The TLI server failed to open the Streams device associated with the transport provider. Action: Contact your customer support representative. ORA-06742, 00000, "TLI Driver: cannot alloc t_bind" Cause: The TLI server cannot allocate space for its requested network address. Action: Contact your customer support representative. ORA-06743, 00000, "TLI Driver: cannot alloc t_bind" Cause: The TLI server cannot allocate space for its actual network address. Action: Contact your customer support representative. ORA-06744, 00000, "TLI Driver: listener cannot bind" Cause: The TLI server failed to assign the correct network address on which to listen for connections. Action: Contact your customer support representative. ORA-06745, 00000, "TLI Driver: listener already running" 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 your customer support representative. ORA-06746, 00000, "TLI Driver: cannot alloc t_call" Cause: TLI cannot allocate space for the TLI server's connection information. Action: Contact your customer support representative. ORA-06747, 00000, "TLI Driver: error in listen" Cause: The TLI server encountered an error while listening for connection requests. Action: Contact your customer support representative. ORA-06748, 00000, "TLI Driver: cannot allocate t_discon" Cause: TLI cannot allocate space for the TLI server's disconnection information. Action: Contact your customer support representative. ORA-06749, 00000, "TLI Driver: option not allowed across network" 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. ORA-06750, 00000, "TLI Driver: sync failed" Cause: The ORACLE process started by the TLI server was unable to synchronize its inherited connection. Action: Contact your customer support representative. ORA-06751, 00000, "TLI Driver: bound addresses unequal" Cause: The osn check server address failed. The bound server address was not the same as the requested binding address. Action: Contact your customer support representative. ORA-06752, 00000, "TLI: error in signal setup" Cause: A call to sigaction() returned with a system error. Action: Contact your customer support representative. ORA-06753, 00000, "TLI Driver: name-to-address mapping failed" Cause: For SVR4, the netdir_getbyname() call failed for some unknown reason. Action: Contact your custumer service representative. ORA-06754, 00000, "TLI Driver: unable to get local host address" 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. ORA-06755, 00000, "TLI Driver: cannot close transport endpoint" Cause: The TLI server was unable to close a connection after passing it to an ORACLE process. Action: Contact your customer support representative. ORA-06756, 00000, "TLI Driver: cannot open oratab" 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. ORA-06757, 00000, "TLI Driver: server got bad command" Cause: The TLI server received an invalid command. Action: Contact your customer support representative. ORA-06760, 00000, "TLI Driver: timeout reading orderly release" Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06761, 00000, "TLI Driver: error sending orderly release" Cause: TLI encountered an error sending a disconnect message closing the communication channel. Action: Contact your customer support representative. ORA-06762, 00000, "TLI Driver: error reading orderly release" Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06763, 00000, "TLI Driver: error sending disconnect" Cause: TLI encountered an error sending a disconnect message closing the communication channel. Action: Contact your customer support representative. ORA-06764, 00000, "TLI Driver: error reading disconnect" Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06765, 00000, "TLI Driver: error awaiting orderly release" Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06766, 00000, "TLI Driver: close failed during release" Cause: TLI failed to close the communication channel after receiving a disconnect message. Action: Contact your customer support representative. ORA-06767, 00000, "TLI Driver: alloc failed during release" Cause: TLI cannot allocate space for disconnection information while closing the communication channel. Action: Contact your customer support representative. ORA-06770, 00000, "TLI Driver: error sending version" Cause: TLI encountered an error while sending its version information during connection establishment. Action: Contact your customer support representative. ORA-06771, 00000, "TLI Driver: error reading version" Cause: TLI encountered an error while awaiting the expected version information during connection establishment. Action: Contact your customer support representative. ORA-06772, 00000, "TLI Driver: error sending command" Cause: TLI encountered an error while sending a command message during connection establishment. Action: Contact your customer support representative. ORA-06773, 00000, "TLI Driver: error reading command" Cause: TLI encountered an error while awaiting the expected command message during connection establishment. Action: Contact your customer support representative. ORA-06774, 00000, "TLI Driver: error sending break mode" Cause: TLI encountered an error while sending break-mode message during connection establishment. Action: Contact your customer support representative. ORA-06775, 00000, "TLI Driver: error reading break mode" Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment. Action: Contact your customer support representative. ORA-06776, 00000, "TLI Driver: error sending parms" Cause: TLI encountered an error while sending the connection parameters during connection establishment. Action: Contact your customer support representative. ORA-06777, 00000, "TLI Driver: error reading parms" Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment. Action: Contact your customer support representative. ORA-06778, 00000, "TLI Driver: error sending ccode" Cause: TLI encountered an error while sending the completion status message during connection establishment. Action: Contact your customer support representative. ORA-06779, 00000, "TLI Driver: error reading ccode" Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment. Action: Contact your customer support representative. ORA-06780, 00000, "TLI Driver: recv error code failed" Cause: TLI encountered an error while awaiting an expected error message during connection establishment. Action: Contact your customer support representative. ORA-06781, 00000, "TLI Driver: error reading negotation string" Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment. Action: Contact your customer support representative. ORA-06790, 00000, "TLI Driver: poll failed" Cause: TLI was unable to poll the communication channel for possible incoming messages. Action: Contact your customer support representative. ORA-06791, 00000, "TLI Driver: poll returned error event" Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages. Action: Contact your customer support representative. ORA-06792, 00000, "TLI Driver: server cannot exec oracle" 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 adminstrator. The permissions on the remote ORACLE program may be set incorrectly. ORA-06793, 00000, "TLI Driver: server cannot create new process" 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 adminstrator. The remote host may be unable to create any new processes due to a full process table. ORA-06794, 00000, "TLI Driver: shadow process could not retrieve protocol info" 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 your customer support representative. ORA-06800, 00000, "TLI Driver: SQL*Net SPX client went away during reconnect" 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 cause of client exit, and reattempt connection. ORA-06801, 00000, "TLI Driver: listen for SPX server reconnect failed" Cause: An unknown event occurred on the client's listening socket. Action: Contact your customer support representative. ORA-06802, 00000, "TLI Driver: could not open the /etc/netware/yellowpages file" 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. ORA-06803, 00000, "TLI Driver: the IPX device file could not be opened" 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 your customer support representative. ORA-06804, 00000, "TLI Driver: could not bind an IPX address at initialization" Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06805, 00000, "TLI Driver: could not send datagram SAP packet for SPX" Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason. Action: Contact your customer support representative. ORA-06806, 00000, "TLI Driver: could not complete protocol initialization for SPX" Cause: A step in the SPX/IPX protocol initialization failed. Action: Check the previous error reported, and follow corrective action. ORA-06807, 00000, "TLI Driver: could not open ethernet device driver file" 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 your customer support representative for a list of supported ethernet drivers. ORA-06808, 00000, "TLI Driver: could not link IPX and ethernet streams" 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 your customer support representative for a list of supported ethernet drivers. ORA-06809, 00000, "TLI Driver: could not clear the IPX ethernet SAP at init" Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06810, 00000, "TLI Driver: could not set the IPX ethernet SAP at init" Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06811, 00000, "TLI Driver: could not set the IPX network number at init" 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 your customer support representative. ORA-06812, 00000, "TLI Driver: could not read the ethernet driver's node address" Cause: The ethernet driver is not installed correctly, or does not support this operation. Action: Contact your customer support representative for a list of supported ethernet drivers. ORA-06813, 00000, "TLI Driver: the configured ethernet address is incorrect" 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. ORA-06814, 00000, "TLI Driver: the SPX device file could not be opened" 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 your customer support representative. ORA-06815, 00000, "TLI Driver: could not link SPX and IPX streams" Cause: The SPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06816, 00000, "TLI Driver: could not set the SPX SAP address" Cause: The SPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06817, 00000, "TLI Driver: could not read the Novell network address" 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 unintentially deleted, run spxctl (net option) to reset the configured Novell network number for SQL*Net SPX. / / 6900-6999 Reserved for more SQL*Net errors / / 6900-6939 CMX errors / ORA-06900, 00000, "CMX: cannot read tns directory" Cause: CMX is not started on your system. Action: Install and/or start CMX on your system. ORA-06901, 00000, "CMX: no local name assigned to local application" Cause: Local application oracmx has no local name assigned Action: Enter unique local name for oracmx in the tns directory ORA-06902, 00000, "CMX: cannot attach to cmx subsystem" Cause: ccp-xxxx is not started Action: start your ccp software on the communication controller ORA-06903, 00000, "CMX: cannot read transport address of remote application" Cause: remote application not entered in tns directory Action: enter remote application in tns directory ORA-06904, 00000, "CMX: no transport address available for remote application" Cause: no local name assigned to remote application Action: assign local name to remote application ORA-06905, 00000, "CMX: connect error" Cause: remote partner not listening Action: make sure remote node has CMX installed and running make sure oracmx is running on remote host ORA-06906, 00000, "CMX: cannot get maximum packet size from CMX" Cause: internal error in CMX Action: contact your customer support representative ORA-06907, 00000, "CMX: error during connect confirmation" Cause: remote partner aborted Action: contact your customer support representative ORA-06908, 00000, "CMX: error during transfer of ORACLE_SID" Cause: remote partner aborted Action: contact your customer support representative ORA-06909, 00000, "CMX: error during acknowledge of ORACLE_SID" Cause: remote partner aborted Action: contact your customer support representative ORA-06910, 00000, "CMX: Cannot start oracle process on remote machine" Cause: oracle process not found or wrong mode (should be 4751) Action: change /etc/oratab or set mode to 4751 ORA-06911, 00000, "CMX: t_event returns ERROR" Cause: internal error in CMX Action: contact your customer support representative ORA-06912, 00000, "CMX: write error in datarq" Cause: internal error in CMX Action: contact your customer support representative ORA-06913, 00000, "CMX: error during redirection of connection" Cause: oracmx has been stopped, or user process has been aborted Action: contact your customer support representative ORA-06914, 00000, "CMX: unexepected event during start of oracle" Cause: connect sequence out of sync Action: contact your customer support representative ORA-06915, 00000, "CMX: unknown t_event in datarq" Cause: internal error in CMX Action: contact your customer support representative ORA-06916, 00000, "CMX: error in data read (t_datain)" Cause: remote partner aborted Action: contact your customer support representative ORA-06917, 00000, "CMX: error in data read (too many bytes read)" Cause: internal error in CMX Action: contact your customer support representative ORA-06918, 00000, "CMX: T_NOEVENT during wait for read event" Cause: internal error in CMX Action: contact your customer support representative ORA-06919, 00000, "CMX: error during write request (unknown event)" Cause: internal error in CMX Action: contact your customer support representative ORA-06920, 00000, "CMX: getbrkmsg illegal datatype" Cause: received packets are corrupted Action: contact your customer support representative ORA-06921, 00000, "CMX: getdatmsg illegal datatype" Cause: received packets are corrupted Action: contact your customer support representative ORA-06922, 00000, "CMX: bad write length" Cause: internal error in CMX Action: contact your customer support representative ORA-06923, 00000, "CMX: illegal break condition" Cause: break handling out of sync Action: contact your customer support representative ORA-06924, 00000, "CMX: wrong break message length" Cause: received packets are corrupted Action: contact your customer support representative ORA-06925, 00000, "CMX: disconnect during connect request" Cause: partner is not responding Action: make sure partner is up and running and reachable ORA-06926, 00000, "CMX: T_ERROR during read data" Cause: internal error in CMX Action: contact your customer support representative ORA-06927, 00000, "CMX: T_DATAIN received before all data written" Cause: internal error in CMX Action: contact your customer support representative ORA-06928, 00000, "CMX: wrong ORACLE_SID" Cause: ORACLE_SID is not entered in remote oratab Action: add ORACLE_SID to remote oratab ORA-06929, 00000, "CMX: error when sending ORACLE_SID" Cause: internal error in CMX Action: contact your customer support representative ORA-06930, 00000, "CMX: error when checking ORACLE_SID" Cause: internal error in CMX Action: contact your customer support representative ORA-06931, 00000, "CMX: error during read_properties for server" Cause: internal error in CMX Action: contact your customer support representative ORA-06932, 00000, "CMX: error in local name" Cause: internal error in CMX Action: contact your customer support representative ORA-06933, 00000, "CMX: error during attach" Cause: internal error in CMX Action: contact your customer support representative / 6950 - 6999 Reserved for SQL*Net Appletalk errors / ORA-06950, 00000, "No error" Cause: SQL*Net AppleTalk error codes base. This is not an error. Action: None. ORA-06951, 00000, "Operating system call error" Cause: AppleTalk API received error in VMS system service. Action: Contact Oracle Customer Support representative. ORA-06952, 00000, "Remote end of the communication issued a forward-reset packet. " Cause: Peer program may have aborted Action: Investigate network problems and try again. ORA-06953, 00000, "Not enough virtual memory" Cause: Not enough memory available. Action: Check VMS process quotas and/or sysgen parameters ORA-06954, 00000, "Illegal file name" Cause: Erroneous file name Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols. ORA-06955, 00000, "Number of database servers exceed limit" Cause: Too many database connections. Action: Check ATKSRV_MAXCONparameter in configuration file. ORA-06956, 00000, "Failed to get local host name" Cause: Unable to get Appletalk host name. Action: Check Appletalk configuration. ORA-06957, 00000, "No SID is currently available" Cause: Incoming SQL*Net connection specified invalid SID name. Action: Specify correct SID in connect string and retry. ORA-06958, 00000, "Failed to access configuration file" Cause: Unable to access CONFIG.ATK Action: Check file protections. ORA-06959, 00000, "Buffer I/O quota is too small" Cause: Buffered I/O quota exceeded. Action: Increase BIOlm using AUTHORIZE utility and retry. ORA-06960, 00000, "Failed to access log file" Cause: SQL*Net Appletalk listener could not create log file. Action: Check directory path and protections. ORA-06961, 00000, "Insufficient privilege for attempted operation" Cause: Action: Check process privileges and retry. / / 6970 - 6989 X.25 Driver Errors / ORA-06970, 00000, "X.25 Driver: remote host is unknown" Cause: Host name specified in the login (connect string) is unknown. Action: Check spelling; make sure name is in the X.25 HOST file. ORA-06971, 00000, "X.25 Driver: error while receiving data" Cause: Action: ORA-06972, 00000, "X.25 Driver: error while sending data" Cause: Action: ORA-06973, 00000, "X.25 Driver: invalid buffer size" Cause: The buffer size specified in the login string must be between 5 and 4096. Action: Re-submit with valid buffer size. ORA-06974, 00000, "X.25 Driver: SID lookup failure" 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). ORA-06975, 00000, "X.25 Driver: connect to host failed" 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. ORA-06976, 00000, "X.25 Driver: endpoint creation failure" Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. ORA-06977, 00000, "X.25 Driver: X.25 Level 2 failure" 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. ORA-06978, 00000, "X.25 Driver: Too many callback tries" Cause: Call back address probably same as called address. Action: Verify that callback address and called address are different. ORA-06979, 00000, "X.25 Driver: server cannot start oracle" 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. / / 7000-7099 Reserved for SQL*CONNECT/DB2 errors / / 7100-7199 Reserved for SQL*CONNECT/IMS errors / / 7200 - 7499 Reserved for UNIX OSD errors / ORA-07200, 00000, "slsid: oracle_sid not set." Cause: The environment variable $(ORACLE_SID) is not set. Action: Set ORACLE_SID environment variable. ORA-07201, 00000, "slhom: oracle_home variable not set in environment." Cause: $(ORACLE_HOME) environment variable not set. Action: Set ORACLE_HOME. ORA-07202, 00000, "sltln: invalid parameter to sltln." 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 customer support. ORA-07203, 00000, "sltln: attempt to translate a long environment variable." 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. ORA-07204, 00000, "sltln: name translation failed due to lack of output buffer space." 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]. Pathnames are limited to 255 characters. ORA-07205, 00000, "slgtd: time error, unable to obtain time." Cause: Time() system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07206, 00000, "slgtd: gettimeofday error, unable to obtain time." Cause: Gettimeofday() system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07207, 00000, "sigpidu: process ID string overflows internal buffer." Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. Action: Internal error. Contact customer support. ORA-07208, 00000, "sfwfb: failed to flush dirty buffers to disk." Cause: The fsync system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07209, 00000, "sfofi: file size limit was exceeded." Cause: The size of the file to be opened exceeded the OS limit imposed on this process. Action: Run osh to increase the file size limit. ORA-07210, 00000, "slcpu: getrusage error, unable to get cpu time." Cause: Getrusage system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07211, 00000, "slgcs: gettimeofday error, unable to get wall clock." Cause: Gettimeofday system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07212, 00000, "slcpu: times error, unable to get cpu time." Cause: times system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07213, 00000, "slgcs: times error, unable to get wall clock." Cause: times system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07214, 00000, "slgunm: uname error, unable to get system information." Cause: uname system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07215, 00000, "slsget: getrusage error." Cause: Getrusage system call returned an error. Possible OS error. Action: Check additional information returned. Look for information in OS reference. Contact customer support. ORA-07216, 00000, "slghst: gethostname error, unable to get name of current host." Cause: gethostname system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07217, 00000, "sltln: environment variable cannot be evaluated." Cause: getenv call returned a null pointer. Action: Set the environment variable and try again. ORA-07218, 00000, "slkhst: could not perform host operation" Cause: Unix system() call failed Action: Examine system error message ORA-07219, 00000, "slspool: unable to allocate spooler argument buffer." Cause: Malloc failed to allocate space to hold spooler arguments. Action: Check additional information returned in OS reference manual. The process may have run out of heap space. Contact customer support. ORA-07220, 00000, "slspool: wait error." Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error. Action: Check additional information returned. Refer to OS reference manual. Contact customer support. ORA-07221, 00000, "slspool: exec error, unable to start spooler program." 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. ORA-07222, 00000, "slspool: line printer spooler command exited with an error." 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 informatin. ORA-07223, 00000, "slspool: fork error, unable to spawn spool process." Cause: Fork system call failed to create additional process. Probable resource limit reached. Action: Check additional information returned. Retry operation. Contact system administrator. ORA-07224, 00000, "sfnfy: failed to obtain file size limit; errno = %s." Cause: The ulimit system call returned an error. Action: Check errno and contact customer support. ORA-07225, 00000, "sldext: translation error, unable to expand file name." Cause: Additional information returned is error returned from sltln. Action: Check additional information. ORA-07226, 00000, "rtneco: unable to get terminal mode." Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07227, 00000, "rtneco: unable to set noecho mode." Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07228, 00000, "rtecho: unable to restore terminal to echo mode." Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07229, 0000, "slcpuc: error in getting number of CPUs." Cause: error in mpcntl system call Action: check errno and contact system administrator ORA-07230, 00000, "slemcr: fopen error, unable to open error file." Cause: Fopen failed to open file. Action: Try to determine which file was not opened. Check that file exists and is accessible. ORA-07231, 00000, "slemcc: invalid file handle, seals do not match." Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr. Action: Internal error. Contact customer support. ORA-07232, 00000, "slemcc: fclose error." Cause: An error was encountered when closing the file. Possible OS error. Action: Contact system administator. ORA-07233, 00000, "slemcw: invalid file handle, seals do not match." Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr. Action: Internal error. Contact customer support. ORA-07234, 00000, "slemcw: fseek error." Cause: Unable to seek to desired position in file. Possible OS error. Possible internal error. Action: Verify that error message file is intact. Try to regenerate error message file. Contact customer support. ORA-07235, 00000, "slemcw: fwrite error." Cause: Unable to write item to file. Possible OS error. Possible permissions problem. Action: Retry operation. ORA-07236, 00000, "slemop: open error." Cause: Unable to open error file. Possible permissions problem. Action: Verify permission on error message file. Check additional information for errno. ORA-07237, 00000, "slemcl: invalid file handle, seals do not match." Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop. Action: Internal error. ORA-07238, 00000, "slemcl: close error." Cause: Unable to close file. Possible OS error. Action: Contact system administator. Check additional information for errno. ORA-07239, 00000, "slemrd: invalid file handle, seals do not match." Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop. Action: Internal error. Contact customer support. ORA-07240, 00000, "slemrd: seek error." Cause: Unable to seek to desired position in file. Possible OS error. Action: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno. ORA-07241, 00000, "slemrd: read error." Cause: Unable to read file. Possible OS error. Action: Verify that error file is intact. Regenerate error message file. Contact customer support. Check additional information for errno. ORA-07242, 00000, "slembfn: translation error, unable to translate error file name." Cause: Additional information indicates error returned from sltln. Action: Check additional information. ORA-07243, 00000, "supplied buffer not big enough to hold entire line" Cause: supplied buffer was not big enough Action: Internal error. Contact customer support. Additional information indicates how big the supplied buffer was. ORA-07244, 00000, "ssfccf: create file failed, file size limit reached." 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. ORA-07245, 00000, "sfccf: unable to lseek and write the last block." Cause: An attempt was made to move and write to a bad device address. Action: Check errno. Possible lack of space on device. ORA-07246, 00000, "sfofi: open error, unable to open database file." Cause: sfofi returns an error. Action: This is an oracle internal error. ORA-07247, 00000, "sfrfb: read error, unable to read requested block from database file." Cause: sfrfb returns an error. Action: This is an oracle internal error. ORA-07248, 00000, "sfwfb: write error, unable to write database block." Cause: sfwfb returns an error. Action: This is an oracle internal error. ORA-07249, 00000, "slsget: open error, unable to open /proc/pid." Cause: open() returns an error. Action: Check that /proc has the right permissions. ORA-07250, 00000, "spcre: semget error, unable to get first semaphore set." 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. ORA-07251, 00000, "spcre: semget error, could not allocate any semaphores." 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. ORA-07252, 00000, "spcre: semget error, could not allocate semaphores." 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. ORA-07253, 00000, "spdes: semctl error, unable to destroy semaphore set." Cause: Semctl system call returned an error. Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult OS reference manual. ORA-07254, 00000, "spdcr: translation error while expanding ?/bin/oracle." 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. ORA-07255, 00000, "spini: cannot set up signal handler." Cause: System failed to set up signal handler. Action: Check errno and sercose[0] for the signal number that failed. ORA-07256, 00000, "sptrap: cannot set up signal handler to catch exceptions." Cause: System failed to set up signal handler to catch exceptions. Action: Check errno and sercose[0] for the signal number that failed. ORA-07257, 00000, "spdcr: translation error expanding program name." Cause: Error ocurred 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]. ORA-07258, 00000, "spdcr: fork error, unable to create process." Cause: An error occurred when creating a new process. Action: Check errno. Perhaps a system limit on the number of processes has been exceeded. ORA-07259, 00000, "spdcr: exec error, detached process failed in startup." 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. ORA-07260, 00000, "spdcr: wait error." Cause: Wait system call returned an error. Action: Check errno. ORA-07261, 00000, "spdde: kill error, unable to send signal to process." Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process. Action: Check errno. ORA-07262, 00000, "sptpa: sptpa called with invalid process id." Cause: This is an internal error. Action: This is an oracle internal error. ORA-07263, 00000, "sptpa: kill error." Cause: Kill system call returned an error. Possible OS error. Action: Check errno. Additional information indicates the process ID tested. ORA-07264, 00000, "spwat: semop error, unable to decrement semaphore." 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. ORA-07265, 00000, "sppst: semop error, unable to increment semaphore." 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. ORA-07266, 00000, "sppst: invalid process number passed to sppst." Cause: Function was passed an invalid oracle process id. Action: Internal error. ORA-07267, 00000, "spwat: invalid process number." Cause: Function was passed an invalid oracle process id. Action: Internal error. Additional information indicates the invalid process id. ORA-07268, 00000, "szguns: getpwuid error." 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. ORA-07269, 00000, "spdcr: detached process died after exec." Cause: Detached process succesfully execed, 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. ORA-07270, 00000, "spalck: setitimer error, unable to set interval timer." Cause: An error occurred while trying to set an interval timer. Probable porting problem. Action: Check errno. ORA-07271, 00000, "spwat: invalid oracle process number." Cause: Function was called with an invalid oracle process number (0). Action: Internal oracle error. ORA-07272, 00000, "spwat: invalid semaphore set id." Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number. Action: Oracle internal error. Check semaphore set index. Check oracle process number. ORA-07273, 00000, "sppst: invalid semaphore id." Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and oracle process number. Action: Oracle internal error. Check semaphore set index. Check oracle process number. ORA-07274, 00000, "spdcr: access error, access to oracle denied." Cause: Unable to access "oracle" program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable. Action: Check errno returned. ORA-07275, 00000, "unable to send signal to process" Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist. Action: Check errno. ORA-07276, 00000, "no dba group in /etc/group." Cause: A group has not been set up for dba users. Action: Contact system administrator. Set up dba group in /etc/group. ORA-07277, 00000, "spdde: illegal pid passed as argument." Cause: A 0 pid was passed to spdde. Action: Internal error. . ORA-07278, 00000, "splon: ops$username exceeds buffer length." Cause: Splon constructed an ops$username logon which exceeded the alloted buffer space. Action: Use a shorter Unix username, or use an oracle username. Contact customer support. ORA-07279, 00000, "spcre: semget error, unable to get first semaphore set." 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. ORA-07280, 00000, "slsget: unable to get process information." Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07281, 00000, "slsget: times error, unable to get cpu time." Cause: times system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07282, 00000, "sksaprd: string overflow." Cause: The internal buffer is not big enough to hold the archive control string. Action: Internal restriction. Try a shorter archive control string. ORA-07283, 00000, "sksaprd: invalid volume size for archive destination." Cause: An invalid volume size was specified. Action: Specify a valid volume size in archive control string. ORA-07284, 00000, "sksaprd: volume size specification not terminated properly." Cause: Some non-numeric text follows the volume size specification. Action: Enter a correct archive control string. ORA-07285, 00000, "sksaprd: volume size should not be specified for a disk file." Cause: Volume size was specified for a disk file. Action: If you are archiving to a disk file, do not specify its volume size. ORA-07286, 00000, "sksagdi: cannot obtain device information." Cause: Stat on the log archiving device failed. Action: Check the returned OSD error for the reason of failure. ORA-07287, 00000, "sksagdi: unsupported device for log archiving." Cause: Log archiving to this device is unsupported. Action: Try log archiving to a supported device. ORA-07290, 00000, "sksagdi: specified directory for archiving does not exist." Cause: The specified pathname is not a directory. Action: Verify that the archive destination directory exists. ORA-07303, 00000, "ksmcsg: illegal database buffer size." 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 parameter is correct in INIT.ORA. ORA-07304, 00000, "ksmcsg: illegal redo buffer size." Cause: The redo buffer size must be a multiple of machine block size. Action: Verify that the log_buffer INIT.ORA parameter is correctly set. ORA-07305, 00000, "ksmcsg: illegal database buffer size." 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 parameter is correct in INIT.ORA, or disable the use_indirect_data_buffers parameter. ORA-07324, 00000, "smpall: malloc error while allocating pga." Cause: Malloc library routine returned an error. Action: Check errno. Possibly out of swap space. ORA-07327, 00000, "smpdal: attempt to destroy pga when it was not mapped." Cause: Smpdal was called when the PGA had not been previously created. Action: Internal error. ORA-07339, 00000, "spcre: maximum number of semaphore sets exceeded." Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested. Action: Reconfigure OS to have more semaphores per set. ORA-07345, 00000, "The datafile name must not contain the string '..'." Cause: The specified datafile name contains '..'. Action: Correct the datafile name and retry the operation. ORA-07390, 00000, "sftopn: translate error, unable to translate file name." Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine. Action: Lookup additional error code for further information. ORA-07391, 00000, "sftopn: fopen error, unable to open text file." Cause: Fopen library routine returned an error. Action: Verify existence and permissions. ORA-07392, 00000, "sftcls: fclose error, unable to close text file." Cause: Fclose library routine returned an error. Action: Possible internal oracle error. ORA-07393, 00000, "unable to delete text file" Cause: An error occurred while deleting a text file. Action: Verify that the file exists and check additional errors. ORA-07394, 00000, "unable to append string to text file" Cause: An error occurred while performing a string put operation. Action: This is an internal error. Check additional information. ORA-07400, 00000, "slemtr: translated name for the message file is too long." 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. ORA-07401, 00000, "sptrap: cannot restore user exception handlers." Cause: The system failed to restore user exception handlers. Action: Check errno and sercose[0] for the signal number that failed. ORA-07402, 00000, "sprst: cannot restore user signal handler." Cause: The system failed to restore user signal handlers. Action: Check errno and sercose[0] for the signal number that failed. ORA-07403, 00000, "sfanfy: db_writers parameter not valid." Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0. Action: Change the db_writers parameter in INIT.ORA. ORA-07404, 00000, "sfareq: Timeout occurred waiting for request to complete." 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. ORA-07406, 00000, "slbtpd: invalid number." Cause: An impossible request for binary to decimal conversion was made. Action: This conversion cannot be performed. ORA-07407, 00000, "slbtpd: invalid exponent." Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed. ORA-07408, 00000, "slbtpd: overflow while converting to packed decimal." Cause: An impossible request for binary to decimal conversion was made. Action: This conversion cannot be performed. ORA-07409, 00000, "slpdtb: invalid packed decimal nibble." Cause: An impossible request for decimal to binary conversion was made. Action: This conversion cannot be performed. ORA-07410, 00000, "slpdtb: number too large for supplied buffer." Cause: An impossible request for decimal to binary conversion was made. Action: This conversion cannot be performed. ORA-07411, 00000, "slgfn: full path name too big for supplied buffer." 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. ORA-07412, 00000, "sfaslv: Error getting entry in asynchronous write array." Cause: One of the database writer processes could not locate its entry in the SGA. Action: Contact customer support. ORA-07415, 00000, "slpath: allocation of memory buffer failed." Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. Action: System has run out of heap space. Additional information indicates errno. ORA-07416, 00000, "slpath: pathname construction failed; lack of output buffer space." Cause: The slpath 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] and constructed pathname length in sercose[1]. ORA-07417, 00000, "sfareq: One or more database writers not active." 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. ORA-07418, 00000, "sfareq: Database writer got error in timing function." Cause: An error occurred when the database writer called the system timing function. Action: Check the database writer trace file. Shut down database and try to warm start. ORA-07419, 00000, "sfareq: Database writer got error in timing function." Cause: An error occurred when the database writer called the system timing function. Action: Check the database writer trace file. Shut down database and try to warm start. ORA-07425, 00000, "sdpri: error %s in translating dump file location." Cause: An oracle error occurred when translating the location of the dump file. Action: Check the oracle error code. ORA-07426, 00000, "spstp: cannot obtain the location of dbs directory." Cause: An oracle error occurred when translating the location of the dbs directory. Action: Check additional information for the error returned from sltln. ORA-07427, 00000, "spstp: cannot change directory to dbs." Cause: Chdir system call returned an error. Possible permission problems. Action: Check additional information for the OS error code. ORA-07431, 00000, "fork failed" 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. ORA-07432, 00000, "unable to perform nested sleep" 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. ORA-07440, 00000, "WMON process terminated with error" Cause: The wakeup monitor process died. Action: Warm start instance. ORA-07441, 00000, "function address must be aligned on %s byte boundary" Cause: An improperly aligned function address was specified. Action: Use a properly aligned function address. ORA-07442, 00000, "function address must be in the range %s to %s" Cause: An invalid function address was specified. Action: Use a valid function address. ORA-07443, 00000, "function %s not found" Cause: An invalid function name was specified. Action: Use a valid function name. ORA-07444, 00000, "function address %s is not readable" Cause: An invalid function name/address was specified. Action: Use a valid function name/address. ORA-07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]" Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error. Action: Contact your customer support representative. ORA-07446, 00000, "sdnfy: bad value '%s' for parameter %s." 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. ORA-07447, 00000, "ssarena: usinit failed." Cause: Oracle failed to create a shared arena file. Action: Use sercerrno field to determine cause of failure. ORA-07448, 00000, "ssarena: maximum number of shared arenas exceeded." Cause: Oracle attempted to create more shared arena files than permitted. Action: Raise the value for max_arena in INIT.ORA. ORA-07449, 00000, "sc: usnewlock failed." Cause: Oracle failed to acquire a shared arena lock. Action: Check result code in sercerrno to determine the cause of failure. ORA-07451, 00000, "slskstat: unable to obtain load information." Cause: kstat library returned an error. Possible OS failure Action: Check result code in sercose[0] for more information. ORA-07452, 00000, "specified resource manager plan does not exist in the data dictionary" 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. ORA-07453, 00000, "requested resource manager plan schema does not contain OTHER_GROUPS" 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. ORA-07454, 00000, "queue timeout, %s second(s), exceeded" Cause: User session queued for longer than maximum specified queue queue duration time for consumer group. Action: Re-submit job at a later time or increase queue timeout. ORA-07455, 00000, "estimated execution time (%s secs), exceeds limit (%s secs)" 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 limit. ORA-07456, 00000, "cannot set RESOURCE_MANAGER_PLAN when database is closed" Cause: An attempt was made to turn on the Resource Manager when the database was closed. Action: Open the database and try again. ORA-07468, 00000, "spwat: mset error, unable to set semaphore." Cause: The mset routine returned an error. Semaphore may not exist. Action: Check result code in sercerrno. Semaphore number returned in sercose[0]. ORA-07469, 00000, "sppst: mclear error, unable to clear semaphore." Cause: The mclear routine returned an error. Semaphore may not exist. Action: Check result code in sercerrno. Semaphore number returned in sercose[0]. ORA-07470, 00000, "snclget: cannot get cluster number." 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. ORA-07471, 00000, "snclrd: name translation error of sgadef.dbf file name." 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]. ORA-07472, 00000, "snclrd: open error when opening sgadef.dbf file." Cause: open failed when opening the file ?/dbs/sgadef@.dbf Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists. ORA-07473, 00000, "snclrd: read error when trying to read sgadef.dbf file." Cause: Read had an error when reading sgadef.dbf file. Action: Check errno. Verify file exists, and is correct size. ORA-07474, 00000, "snclrd: close error, unable to close sgadef.dbf file." Cause: An error occurred in close, while closing the file "?/dbs/sgadef@.dbf" Action: Check errno. Possible operating system error. ORA-07475, 00000, "slsget: cannot get vm statistics." Cause: The vm_statistics system call failed to get virtual memory statistics. Action: Check result code in sercerrno. Possible operating system failure. ORA-07476, 00000, "slsget: cannot get mapped memory statistics." Cause: The vm_mapmem system call failed to get mapped memory statistics. Action: Check result code in sercerrno. Possible operating system failure. ORA-07477, 00000, "scgcmn: lock manager not initialized." Cause: Lock manager must be initialized before converting locks. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07478, 00000, "scgcmn: cannot get lock status." Cause: lm_stat_lock failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07479, 00000, "scgcmn: cannot open or convert lock." Cause: lm_open or lm_open_convert failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07480, 00000, "snchmod: cannot change permissions on ?/dbs/sgalm.dbf." Cause: When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf Action: Contact your customer support representative. ORA-07481, 00000, "snlmatt: cannot attach to lock manager instance." Cause: lm_attach failed to attach to lock manager instance. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07482, 00000, "snlmini: cannot create lock manager instance." Cause: lm_create failed to create lock manager instance. Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry. ORA-07483, 00000, "snlkget: cannot convert(get) lock." Cause: lm_convert failed to convert(get) lock. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07484, 00000, "snlkput: cannot convert(put) lock." Cause: lm_convert failed to put lock value. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07485, 00000, "scg_get_inst: cannot open instance number lock." Cause: lm_open failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07486, 00000, "scg_get_inst: cannot convert(get) instance number lock." Cause: lm_convert failed to get lock value. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07487, 00000, "scg_init_lm: cannot create lock manager instance." Cause: lm_create failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07488, 00000, "scgrcl: lock manager not initialized." Cause: Lock manager must be initialized before releasing locks. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07489, 00000, "scgrcl: cannot get lock status." Cause: lm_stat_lock failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07490, 00000, "scgrcl: cannot convert lock." Cause: lm_convert failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07491, 00000, "scgrcl: cannot cancel lock request." Cause: lm_cancel failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07492, 00000, "scgrcl: cannot close lock." Cause: lm_close failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07493, 00000, "scgrcl: lock manager error." Cause: An error was encountered releasing the lock. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07494, 00000, "scgcm: unexpected error." Cause: Unknown or unexpected error code. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07495, 00000, "spwat: lm_wait failed." Cause: lm_wait failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07496, 00000, "sppst: lm_post failed." Cause: lm_post failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07497, 00000, "sdpri: cannot create trace file '%s'; errno = %s." Cause: The trace file cannot be created for writing. Action: Check if the dump directory exists and whether it is writable. ORA-07498, 00000, "spstp: Unable to open /dev/resched." 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. ORA-07499, 00000, "spglk: Cannot reschedule." Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur. Action: Contact your customer support representative. / / 7500-7999 VMS OSD ERRORS / ORA-07500, 00000, "scglaa: $cantim unexpected return" Cause: VMS system service $CANTIM returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07501, 00000, "scgtoa: $deq unexpected return" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07502, 00000, "scgcmn: $enq unexpected return" Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07503, 00000, "scgcmn: $setimr unexpected return" Cause: VMS system service $SETIMR returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07504, 00000, "scgcmn: $hiber unexpected return" Cause: VMS system service $HIBER returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07505, 00000, "scggt: $enq parent lock unexpected return" Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07506, 00000, "scgrl: $deq unexpected return on lockid %s" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07507, 00000, "scgcm: unexpected lock status condition" Cause: A global locking system service returned an unexpected value. Action: Check for system error message (if any) and refer to VMS documentation, or contact your customer support representative. ORA-07508, 00000, "scgfal: $deq all unexpected return" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07509, 00000, "scgfal: $deq parent lock unexpected return" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07510, 00000, "scgbrm: $getlki unexpected return on lockid %s" Cause: VMS system service $GETLKI returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07511, 00000, "sscggtl: $enq unexpected return for master termination lock" Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07512, 00000, "sscggtl: $enq unexpected return for client termination lock" Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07513, 00000, "sscgctl: $deq unexpected return on cancel of term. lock" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07514, 00000, "scgcan: $deq unexpected return while canceling lock" Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation / ORA-07534, 00000, "scginq: $getlki unexpected return on lockid %s" Cause: VMS system service $GETLKI returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07548, 00000, "sftopn: Maximum number of files already open" Cause: Too many test files open Action: This is an internal error, please report to Oracle ORA-07549, 00000, "sftopn: $OPEN failure" Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07550, 00000, "sftopn: $CONNECT failure" Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07551, 00000, "sftcls: $CLOSE failure" Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation ORA-07552, 00000, "sftget: $GET failure" Cause: VMS system service $GET failed Action: Examine system error message and refer to VMS documentation ORA-07561, 00000, "szprv: $IDTOASC failure" Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation ORA-07562, 00000, "sldext: extension must be 3 characters" Cause: An extension was found but it is of improper length Action: This is an internal error, please report to Oracle ORA-07563, 00000, "sldext: $PARSE failure" Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07564, 00000, "sldext: wildcard in filename or extension" Cause: A wildcard was used in the file name Action: Reenter the file name completely ORA-07565, 00000, "sldext: $SEARCH failure" Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation ORA-07568, 00000, "slspool: $OPEN failure" Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07569, 00000, "slspool: $CLOSE failure" Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation ORA-07570, 00000, "szrfc: $IDTOASC failure" Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation ORA-07571, 00000, "szrfc: $FIND_HELD failure" Cause: VMS system service $FIND_HELD failed Action: Examine system error message and refer to VMS documentation ORA-07572, 00000, "szrfc: insufficient rolename buffer space" Cause: An OS role name was too long. Action: Re-define the role name to be of correct length. ORA-07573, 00000, "slkhst: could not perform host operation" Cause: VMS system service LIB$SPAWN failed Action: Examine system error message and refer to VMS documentation ORA-07574, 00000, "szrfc: $GETUAI failure" Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07576, 00000, "sspexst: $GETJPIW failure on process ID %s" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07577, 00000, "no such user in authorization file" Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA__DBA or ORA__OPER) hasn't been created yet. Action: Add a VMS account for ORA__DBA and/or ORA__OPER before trying to set a password for them. ORA-07578, 00000, "szprv: $FIND_HELD failure" Cause: VMS system service $FIND_HELD failed Action: Examine system error message and refer to VMS documentation ORA-07579, 00000, "spini: $DCLEXH failure" Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07580, 00000, "spstp: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07581, 00000, "spstp: cannot derive SID from unexpected process name" Cause: A background process did not have name of correct form Action: If the job name was changed, restore it, otherwise this is an internal error, please report to Oracle. ORA-07582, 00000, "spstp: ORA_SID has illegal value" Cause: The ORA_SID must exist and be less than 6 characters Action: Consult the VMS Installation guide for information on setting the SID. ORA-07584, 00000, "spdcr: invalid value for ORA_sid_(proc_)PQL$_item" Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric). Action: Examine the values of these logical names, correct the one in error, and retry. ORA-07585, 00000, "spdcr: $PARSE failure" Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07586, 00000, "spdcr: $SEARCH failure" Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation ORA-07587, 00000, "spdcr: $CREPRC failure" Cause: VMS system service $CREPRC failed Action: Examine system error message and refer to VMS documentation ORA-07588, 00000, "spdcr: $GETJPIW get image name failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07589, 00000, "spdde: system ID not set" Cause: The logical name ORA_SID doesn't translate to a valid value. Action: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly. ORA-07590, 00000, "spdde: $DELPRC failure" Cause: VMS system service $DELPRC failed Action: Examine system error message and refer to VMS documentation ORA-07591, 00000, "spdde: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07592, 00000, "sspgprv: Error obtaining required privileges" Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. Action: This is an internal error. Please report to Oracle ORA-07593, 00000, "ssprprv: Error release privileges" Cause: While releasing privileges, an error was returned from SYS$SETPRV. Action: This is an internal error. Please report to Oracle ORA-07594, 00000, "spiip: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07595, 00000, "sppid: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07596, 00000, "sptpa: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07597, 00000, "spguns: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07598, 00000, "spwat: $SETIMR failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07599, 00000, "spwat: $SCHDWK failure" Cause: VMS system service $SCHDWK failed Action: Examine system error message and refer to VMS documentation ORA-07600, 00000, "slkmnm: $GETSYIW failure" Cause: VMS system service $GETSYIW failed Action: Examine system error message and refer to VMS documentation ORA-07601, 00000, "spguno: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07602, 00000, "spgto: $GETJPIW failure" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07605, 00000, "szprv: $ASCTOID failure" Cause: VMS system service $ASCTOID failed Action: Examine system error message and refer to VMS documentation ORA-07606, 00000, "szprv: $CHKPRO failure" Cause: VMS system service $CHKPRO failed Action: Examine system error message and refer to VMS documentation ORA-07607, 00000, "szaud: $SNDOPR failure" Cause: VMS system service $SNDOPR failed Action: Examine system error message and refer to VMS documentation ORA-07608, 00000, "szprv: $GETUAI failure" Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07609, 00000, "szprv: $HASH_PASSWORD failure" Cause: VMS system service $HASH_PASSWORD failed Action: Examine system error message and refer to VMS documentation ORA-07610, 00000, "$GETJPIW failed in retrieving the user's MAC priviledges" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07612, 00000, "$GETUAI failed in retrieving the user's clearance level" Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07613, 00000, "$GETJPIW failed in retrieving the user's process label" Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07614, 00000, "$CHANGE_CLASS failed in retrieving the user's process label" Cause: VMS system service $CHANGE_CLASS failed Action: Examine system error message and refer to SEVMS documentation ORA-07615, 00000, "$CHANGE_CLASS failed in retrieving the specified file label" Cause: VMS system service $CHANGE_CLASSS failed Action: Examine system error message and refer to SEVMS documentation ORA-07616, 00000, "$CHANGE_CLASS failed in retrieving the specified device label" Cause: VMS system service $CHANGE_CLASS failed Action: Examine system error message and refer to SEVMS documentation ORA-07617, 00000, "$FORMAT_CLASS failed translating the binary label to a string" Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid. Action: Examine system error message and refer to SEVMS documentation ORA-07618, 00000, "$IDTOASC failed translating a secrecy level" Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level. Action: Define the entry in the rights database which the binary label you specified references. ORA-07619, 00000, "$IDTOASC failed translating an integrity level" Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level. Action: Define the entry in the rights database which the binary label you specified references. ORA-07620, 00000, "smscre: illegal database block size" Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size. Action: Change db_block_size in the parameter file to conform to these limits. ORA-07621, 00000, "smscre: illegal redo block size" Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512. Action: Change log_buffer in the parameter file to conform to these limits. ORA-07622, 00000, "smscre: $CREATE failure" Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed. Action: Examine the system error message and refer to VMS documentation. ORA-07623, 00000, "smscre: $CRMPSC failure" Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed. Action: Examine the system error message and refer to VMS documentation. ORA-07624, 00000, "smsdes: $DGBLSC failure" Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed. Action: Examine the system error message and refer to VMS documentation. ORA-07625, 00000, "smsget: $MGBLSC failure" Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that ORACLE has not been started up. Action: Examine the system error message and refer to VMS documentation. Start up ORACLE if it is not already started. ORA-07626, 00000, "smsget: sga already mapped" Cause: An attempt to map the SGA during logon failed because it was already mapped. This is an internal error. Action: Exit your program and try again, and report this to your customer support representative. ORA-07627, 00000, "smsfre: $CRETVA failure" Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07628, 00000, "smsfre: sga not mapped" Cause: An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error. Action: Exit your program and try again, and report this to your customer support representative. ORA-07629, 00000, "smpall: $EXPREG failure" Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. Action: Examine the system error message and refer to VMS documentation. ORA-07630, 00000, "smpdal: $DELTVA failure" Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07631, 00000, "smcacx: $EXPREG failure" Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. Action: Examine the system error message and refer to VMS documentation. ORA-07632, 00000, "smsrcx: $DELTVA failure" Cause: While deleting a context area, VMS system service $DELTVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07633, 00000, "smsdbp: illegal protection value" Cause: The buffer debug function was called with an illegal value. This is an internal error. Action: Contact your customer support representative. ORA-07634, 00000, "smsdbp: $CRETVA failure" Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed. Action: Contact your customer support representative. ORA-07635, 00000, "smsdbp: $SETPRT failure" Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed. Action: Contact your customer support representative. ORA-07636, 00000, "smsdbp: $MGBLSC failure" Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed. Action: Contact your customer support representative. ORA-07637, 00000, "smsdbp: buffer protect option not specified when sga created" Cause: Trying to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error. Action: Contact your customer support representative. ORA-07638, 00000, "smsget: SGA pad area not large enough for created SGA" Cause: An attempt was made to map an SGA with software in which the SGA pad area isn't large enough. Action: Create a smaller SGA, or relink the software with a larger pad. ORA-07639, 00000, "smscre: SGA pad area not large enough (%s bytes required)" Cause: An attempt was made to create an SGA with software in which the SGA pad area isn't large enough. Action: Create a smaller SGA, or relink the software with a larger pad. ORA-07640, 00000, "smsget: SGA not yet valid. Initialization in progress" Cause: An attempt was made to map to the SGA while it was being initialized. Action: Wait until initialization is complete, and try again. ORA-07641, 00000, "smscre: Unable to use the system pagefile for the SGA" Cause: The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded. Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file. ORA-07642, 00000, "smprtset: $CMKRNL failure" Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service. Action: Examine the system error message and refer to VMS documentation. ORA-07643, 00000, "smsalo: SMSVAR is invalid" Cause: an internal error Action: Report this error to ORACLE customer support, provide your INIT.ORA file. ORA-07645, 00000, "sszfsl: $CHANGE_CLASS failure" Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed. Action: Examine the system message and refer to SEVMS system documentation. ORA-07646, 00000, "sszfck: $CREATE failure" Cause: While attempting to create a file, VMS system service $CREATE failed. Action: Examine the system message and refer to VMS system documentation. ORA-07647, 00000, "sszfck: $OPEN failure" Cause: While attempting to reopen a file, VMS system service $OPEN failed. Action: Examine the system message and refer to VMS system documentation. ORA-07650, 00000, "sigunc: $GETJPIW failure" Cause: While attempting to get the user's terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed. Action: Examine the system error message and refer to VMS documentation. ORA-07655, 00000, "slsprom:$TRNLOG failure" Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed. Action: Examine the system error message and refer to VMS documentation. ORA-07656, 00000, "slsprom:$GETDVI failure" Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed. Action: Examine the system error message and refer to VMS documentation. ORA-07657, 00000, "slsprom:$ASSIGN failure" Cause: While prompting for a password, VMS system service $ASSIGN failed. Action: Examine the system error message and refer to VMS documentation. ORA-07658, 00000, "slsprom:$QIOW read failure" Cause: While prompting for a password, VMS system service $QIOW failed. Action: Examine the system error message and refer to VMS documentation. ORA-07665, 00000, "ssrexhd: recursive exception encountered %s %s %s %s %s %s" Cause: A VMS exception occurred while executing in the ORACLE exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error. Action: Contact your customer support representative. ORA-07670, 00000, "$IDTOASC failed translating a secrecy category" Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category. Action: Define the entry in the rights database which the binary label you specified references. ORA-07671, 00000, "$IDTOASC failed translating an integrity category" Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category. Action: Define the entry in the rights database which the binary label you specified references. ORA-07672, 00000, "$PARSE_CLASS failed translating the string into a binary label" Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification. Action: Examine system error message and refer to SEVMS documentation. ORA-07680, 00000, "sou2os: another call to ORACLE currently executing" Cause: A call to the ORACLE shared image entry point occurred from within the shared image. This is an internal error. Action: Contact your customer support representative. ORA-07681, 00000, "sou2os: An error occurred while initializing Oracle" Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error. Action: Contact your customer support representative. ORA-07682, 00000, "sou2os: set kernel dispatch fail err" Cause: During ORACLE shared image entry, a dispatch to kernel mode failed. Action: Make sure that your shared image is installed with the CMKRNL privilege, then contact your customer support representative. ORA-07683, 00000, "sou2os: $SETPRV reset error" Cause: During an attempt to restore user privileges at ORACLE shared image exit, VMS system service $SETPRV failed. This is an internal error. Action: Contact your customer support representative. ORA-07684, 00000, "sou2os: supervisor stack reset error" Cause: During an attempt to restore the supervisor-mode stack at ORACLE shared image exit, VMS system service $SETSTK failed. This is an internal error. Action: Contact your customer support representative. ORA-07685, 00000, "sou2os: supervisor stack set error" Cause: During an attempt to set the ORACLE supervisor-mode stack at ORACLE shared image entry, VMS system service $SETSTK failed. This is an internal error. Action: Contact your customer support representative. / / 7700 - 7720: sksarch errors / ORA-07700, 00000, "sksarch: interrupt received" Cause: An interrupt was received while archiving the logs Action: Retry operation ORA-07701, 00000, "sksatln: internal exception: output buffer too small" Cause: Overflow of buffer for parsing archive control text string Action: This is an internal error, please report to Oracle ORA-07702, 00000, "unrecognized device type in archive text" Cause: Unrecognized device type in archive text Action: This is an internal error, please report to Oracle ORA-07703, 00000, "error in archive text: need '/' after device type" Cause: The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a '/'. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07704, 00000, "error in archive text: need ':' after device name" Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ':'. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07705, 00000, "sksaprs: device name buffer too small" Cause: The buffer supplied for the device name is too small. This is an internal error. Action: Contact your customer support representative. ORA-07706, 00000, "error in archive text: need disk file name" Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07707, 00000, "error in archive text: need tape label name" Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07708, 00000, "sksaprs: tape label name buffer too small" Cause: The buffer supplied for the tape label is too small. This is an internal error. Action: Contact your customer support representative. ORA-07709, 00000, "sksaprs: archiving to a remote host is not allowed" Cause: The user specified a remote disk for archiving via DECnet. Action: Archive to a disk on the local host. ORA-07710, 00000, "sksaprs: file name buffer too small" Cause: The buffer supplied for the file name is too small. This is an internal error. Action: Contact your customer support representative. ORA-07713, 00000, "sksamtd: could not mount archival device (SYS$MOUNT failure)" Cause: VMS system service SYS$MOUNT failed Action: Examine system error message and refer to VMS documentation ORA-07715, 00000, "sksadtd: could not dismount archival device (SYS$DISMNT failure)" Cause: VMS system service SYS$DISMNT failed Action: Examine system error message and refer to VMS documentation ORA-07716, 00000, "sksachk: invalid device specification for ARCHIVE" Cause: VMS system service SYS$GETDVI failed" Action: Specify a valid device in ARCHIVE control string ORA-07717, 00000, "sksaalo: error allocating memory" Cause: VMS system service LIB$GET_VM failed" Action: Examine system error message and refer to VMS documentation ORA-07718, 00000, "sksafre: error freeing memory" Cause: VMS system service LIB$FREE_VM failed Action: Examine system error message and refer to VMS documentation / / 7721-7729 scg overflow errors / ORA-07721, 00000, "scgcm: not enough OS resource to obtain system enqueue" Cause: A call to sys$enq returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM. Action: Free up some of the required resource to allow the creation of the required lock. / / 7740 - 7760 error message file errors ORA-07740, 00000, "slemop: incorrect handle size (programming error)" Cause: structures used for reading error message files do not match Action: this is an internal error, please report to Oracle ORA-07741, 00000, "slemop: $OPEN failure" Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07742, 00000, "slemop: $CONNECT failure" Cause: VMS system service $CONNECT failed Action: Examine system error message and refer to VMS documentation ORA-07743, 00000, "slemop: incorrect error file attributes" Cause: An error message file is of incorrect format Action: Unless an error file has been changed, report this to Oracle ORA-07744, 00000, "slemcl: invalid error message file handle" Cause: seal in passed in handle does not match correct value Action: this is an internal error, please report to Oracle ORA-07745, 00000, "slemcl: $CLOSE failure" Cause: VMS system service $CLOSE failed Action: Check system error and refer to VMS documentation ORA-07746, 00000, "slemrd: invalid error message file handle" Cause: seal in passed in handle does not match correct value Action: this is an internal error, please report to Oracle ORA-07747, 00000, "slemrd: $READ failure" Cause: VMS system service $READ failed Action: Check system error and refer to VMS documentation ORA-07750, 00000, "slemcr: fopen failure" Cause: An attempt to create a message file failed. This is an internal error. Action: Contact your customer support representative. ORA-07751, 00000, "slemcr: malloc failure" Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error. Action: Contact your customer support representative. ORA-07753, 00000, "slemcf: fseek before write failure" Cause: An attempt to seek before writing a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07754, 00000, "slemcf: fwrite failure" Cause: An attempt to write a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07755, 00000, "slemcf: fseek before read failure" Cause: An attempt to seek before reading a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07756, 00000, "slemcf: fread failure" Cause: An attempt to read a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07757, 00000, "slemcc: invalid handle" Cause: The seal in a passed-in handle does not match correct value. This is an internal error. Action: Contact your customer support representative. ORA-07758, 00000, "slemcw: invalid handle" Cause: The seal in a passed-in handle does not match correct value. This is an internal error. Action: Contact your customer support representative. ORA-07759, 00000, "slemtr: invalid destination" Cause: The destination string provided to the function is too short This is an internal error. Action: Contact your customer support representative. ORA-07760, 00000, "slemtr: $open failure" Cause: the $open service failed. This is an internal error Action: Contact your customer support representative. ORA-07800, 00000, "slbtpd: invalid number" Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07801, 00000, "slbtpd: invalid exponent" Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07802, 00000, "slbtpd: overflow while converting to packed decimal" Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07803, 00000, "slpdtb: invalid packed decimal nibble" Cause: An impossible request for decimal to binary conversion was made Action: This conversion cannot be performed ORA-07804, 00000, "slpdtb: number too large for supplied buffer" Cause: An impossible request for decimal to binary conversion was made Action: This conversion cannot be performed / / 7820-7839 SSP error messages / ORA-07820, 0000, "sspscn: SYS$CRELNM failure" Cause: An error was returned from the SYS$CRELNM function Action: Check system error and refer to VMS documentation ORA-07821, 0000, "sspsdn: SYS$DELLNM failure" Cause: An error was returned from the SYS$DELLNM function Action: Check system error and refer to VMS documentation ORA-07822, 0000, "sspscm: SYS$CREMBX failure" Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07823, 0000, "sspsqr: $QIO failure" Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07824, 0000, "sspain: $SETIMR failure" Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer. Action: Check system error and refer to VMS documentation ORA-07825, 0000, "sspsck: $QIO failure at AST level" Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07826, 0000, "sspscm: SYS$GETDVIW failure" Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox. Action: Check system error and refer to VMS documentation / / 7840-7859 SLLF error messages / ORA-07840, 0000, "sllfop: LIB$GET_VM failure" Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an i/o vector. Action: Check system error and refer to VMS documentation ORA-07841, 0000, "sllfop: SYS$OPEN failure" Cause: An error was returned from SYS$OPEN while attempting to open the data file for reading Action: Check system error and refer to VMS documentation ORA-07842, 0000, "sllfcl: SYS$CLOSE failure" Cause: An error was returned from SYS$CLOSE while attempting to close the input data file Action: Check system error and refer to VMS documentation ORA-07843, 0000, "sllfcl: LIB$FREE_VM failure" Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the i/o vector Action: Check system error and refer to VMS documentation ORA-07844, 0000, "sllfop: LIB$GET_VM failure" Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers Action: Check system error and refer to VMS documentation ORA-07845, 0000, "sllfcl: LIB$FREE_VM failue" Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers Action: Check system error and refer to VMS documentation ORA-07846, 0000, "sllfop: %s byte record too big for %s byte user buffer" Cause: The longest record in the file will not fit into the largest data buffer that can be allocated Action: Modify the RMS file to have smaller records ORA-07847, 0000, "sllfop: $CONNECT failure" Cause: An error was returned by SYS$CONNECT while attempting to open the data file Action: Check system error and refer to VMS documentation ORA-07848, 0000, "sllfrb: $GET failure" Cause: An error was returned by SYS$GET while attempting to read the data file Action: Check system error and refer to VMS documentation ORA-07849, 0000, "sllfsk: $GET failure" Cause: An error was returned by SYS$GET while attempting to skip records in the input file Action: Check system error and refer to VMS documentation ORA-07850, 0000, "sllfop: bad option" Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others. Action: Check documentation ORA-07860, 0000, "osnsoi: error setting up interrupt handler" Cause: An error occurred while setting up the control interrupt handler Action: This is an internal error. Contact your Oracle representative. / / / 7880 - 7889 Error message for sd / ORA-07880, 0000, "sdopnf: internal error" Cause: A list of all files open by this process could not be obtained. Action: This is an internal error. Contact your customer support representative. / / 8000 - 8174 Data layer error messages / ORA-08000, 00000, "maximum number of session sequence lists exceeded" Cause: the sequence parent state objects for this session are all used Action: an internal error; quit the session and begin a new one ORA-08001, 00000, "maximum number of sequences per session exceeded" Cause: the limit on the number of sequences usable by session has been hit Action: increase INIT.ORA parameter user_sequences to get more ORA-08002, 00000, "sequence %s.CURRVAL is not yet defined in this session" Cause: sequence CURRVAL has been selected before sequence NEXTVAL Action: select NEXTVAL from the sequence before selecting CURRVAL ORA-08003, 00000, "sequence %s.NEXTVAL exceeds internal limits" Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal represention size. Action: Alter or recreate the sequence number with legal limits. ORA-08004, 00000, "sequence %s.NEXTVAL %s %sVALUE and cannot be instantiated" Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE Action: alter the sequence so that a new value can be requested ORA-08005, 00000, "specified row does not exist" Cause: A row with the given rowid does not exist in any of the tables given Action: check the query for misspellings of table names and the rowid ORA-08006, 00000, "specified row no longer exists" Cause: the row has been deleted by another user since the operation began Action: re-try the operation ORA-08008, 00000, "another instance is mounted with USE_ROW_ENQUEUES = %s" Cause: the shared instance being started does not have the same value for use_row_enqueues as already running instances Action: ensure that all instances' INIT.ORA files specify the same value for the parameter 'use_row_enqueues' ORA-08100, 00000, "index is not valid - see trace file for diagnostics" Cause: Validate Index detected an inconsistency in its argument index Action: Send trace file to your customer support representative ORA-08101, 00000, "index key does not exist root dba %s, dba %s (%s)" Cause: Internal error: possible inconsistency in index Action: Send trace file to your customer support representative, along with information on reproducing the error ORA-08102, 00000, "index key not found, obj# %s, dba %s (%s)" Cause: Internal error: possible inconsistency in index Action: Send trace file to your customer support representative, along with information on reproducing the error ORA-08103, 00000, "object no longer exists" Cause: the object has been deleted by another user since the operation began Action: ORA-08104, 00000, "this index object %s is being online built or rebuilt" Cause: the index is being created or rebuild or waited for recovering from the online (re)build Action: wait the online index build or recovery to complete ORA-08105, 00000, "Oracle event to turn off smon cleanup for online index build" Cause: set this event only under the supervision of Oracle development Action: debugging only ORA-08106, 00000, "can not create journal table %s.%s" Cause: online index builder can not create its journal table Action: rename your table in conflict ORA-08108, 00000, "may not build or rebuild this type of index online " Cause: only support normal index or IOT top-level index Action: change your index type ORA-08109, 00000, "nosort is not a supported option for online index build " Cause: may not specify nosort for online index build Action: get rid of nosort in the index creation command ORA-08110, 00000, "Oracle event to test SMON cleanup for online index build " Cause: Oracle Kernel test only Action: Donot set this event(for test only) ORA-08111, 00000, "a partitioned index may not be coalesced as a whole" Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE) ORA-08112, 00000, "a composite partition may not be coalesced as a whole" Cause: User attempted to coalesce a composite partition Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE) ORA-08113, 00000, "composite partition index may not be compressed" Cause: User attempted to compress a composite partition index Action: create uncompressed composite partition index ORA-08114, 00000, "can not alter a fake index" Cause: User attempted to alter a fake index Action: drop fake index ORA-08115, 00000, "can not online create/rebuild this index type" Cause: User attempted to create index type that online doesnot support Action: use offline index create/rebuild command ORA-08116, 00000, "can not acquire dml enough lock(S mode) for online index build" Cause: User attempted to create index online without allowing DML Share lock Action: allow DML share lock on the base table ORA-08117, 00000, "Index Organized Table operation released its block pin" Cause: Block maintenance forced the release of a block pin Action: Contact your customer support representative / / / 8175 - 8190 Discrete transaction error messages / ORA-08175, 00000, "discrete transaction restriction violated (%s)" Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction. Action: Rollback the transaction, and retry it as a normal transaction. / ORA-08176, 00000, "consistent read failure; rollback data not available" Cause: Encountered data changed by an operation that does not generate rollback data : create index, direct load or discrete transaction. Action: In read/write transactions, retry the intended operation. Read only transactions must be restarted. ORA-08177, 00000, "can't serialize access for this transaction" Cause: Encountered data changed by an operation that occurred after the start of this serializable transaction. Action: In read/write transactions, retry the intended operation or transaction. ORA-08178, 00000, "illegal SERIALIZABLE clause specified for user INTERNAL" Cause: Serializable mode is not supported for user INTERNAL. Action: Reconnect as another user and retry the SET TRANSACTION command. ORA-08179, 00000, "concurrency check failed" Cause: Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a datablock is stale. This is used for internal use for now. Action: refresh the cached copy of the datablock and retry operation. ORA-08180, 00000, "no snapshot found based on specified time" Cause: Could not match the time to an SCN from the mapping table. Action: try using a larger time. ORA-08181, 00000, "specified number is not a valid system change number" Cause: supplied scn was beyond the bounds of a valid scn. Action: use a valid scn. ORA-08182, 00000, "operation not supported while in Flashback mode" Cause: user tried to do dml or ddl while in Flashback mode Action: disable Flashback and re-attempt the operation ORA-08183, 00000, "Flashback cannot be enabled in the middle of a transaction" Cause: user tried to do Flashback in the middle of a transaction Action: do a commit ORA-08184, 00000, "attempting to re-enable Flashback while in Flashback mode" Cause: as stated above Action: disable first before re-enabling ORA-08185, 00000, "Flashback not supported for user SYS" Cause: user logged on as SYS Action: logon as a different (non SYS) user. ORA-08186, 00000, "invalid timestamp specified" Cause: as stated above Action: enter a valid timestamp / 8200 - 8399 Reserved for NCUBE OSD errors / /8200 - 8204 Reserved ORA-08205, 00000, "ora_addr: $ORACLE_SID not set in environment" Cause: The environment variable ORACLE_SID is not set. Action: Set the ORACLE_SID environment variable. ORA-08206, 00000, "ora_addr: cannot translate address file name" Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf. Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set. ORA-08207, 00000, "ora_addr: cannot open address file" Cause: The address file could not be opened. Action: Check that ORACLE is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions. ORA-08208, 00000, "ora_addr: cannot read from address file" Cause: The address file could not be read. Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text. ORA-08209, 00000, "scngrs: SCN not yet initialized" Cause: The System Commit Number has not yet been initialized. Action: Contact your customer support representative. ORA-08210, 00000, "Requested I/O error" Cause: Oracle requested that an I/O error be returned for this operation. Action: This should not occur in normal Oracle operation. Contact support. / ORA-08230, 00000, "smscre: failed to allocate SGA" Cause: The n_core system call failed, maybe due to insufficient memory. Action: Specify a smaller number of buffers. Check INIT.ORA parameters. ORA-08231, 00000, "smscre: unable to attach to SGA" Cause: The process cannot attach to the SGA. This can happen if either the listener can't attach, or the process cannot communicate with the listener. Action: Verify that the instance is up and running. Contact your customer support representative. ORA-08232, 00000, "smsdes: cannot detach from SGA" Cause: Probably, the listener process has died. Action: Contact your customer support representative. ORA-08233, 00000, "smsdes: cannot unmap SGA" Cause: The n_core system call failed while detaching from the SGA. Action: Note nCX error returned; contact your customer support representative. ORA-08234, 00000, "smsget: cannot get instance listener address" Cause: The instance listener address cannot be read from the sgadef file. Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ora_addr. ORA-08235, 00000, "smsget: listener not on this node" Cause: A process wishing to attach to the SGA is on a different node from its instance's listener. Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact your customer support representative. ORA-08236, 00000, "smsget: cannot share subcube with listener" Cause: The n_share call failed, probably because the listener has died. Action: Check if the listener is running, and contact your customer support representative. ORA-08237, 00000, "smsget: SGA region not yet created" Cause: Attempting to attach to an SGA which has not yet been created. Action: Verify that the instance is running. Contact your customer support representative. ORA-08238, 00000, "smsfre: cannot detach from SGA" Cause: The n_core system call failed while detaching from the SGA. Action: Check nCX error, and contact your customer support representative. /8239 - 8242 Reserved /8252 - 8260 Reserved ORA-08260, 00000, "ora_addr: cannot open nameserver" Cause: A process could not connect to the nameserver. Action: Make sure the nameserver is up and running. Additional information gives nameserver's returned status. ORA-08261, 00000, "ora_addr: cannot find name in nameserver" Cause: The listener nameserver entry for an instance could not be found. Action: Make sure the nameserver is up and running. Additional information gives nameserver's returned status. /8262 Reserved ORA-08263, 00000, "ora_addr: cannot free listener address" Cause: The listener nameserver entry could not be freed Action: Additional information gives nameserver's returned status. Contact your customer support representative. ORA-08264, 00000, "ora_addr: cannot close nameserver" Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver's returned status. Contact your customer support representative. ORA-08265, 00000, "create_ora_addr: cannot open nameserver" Cause: A process could not connect to the nameserver. Action: Make sure the nameserver is up and running. Additional information gives nameserver's returned status. ORA-08266, 00000, "create_ora_addr: cannot register name in nameserver" Cause: The listener's addressing information could not be registered. Action: Make sure the nameserver is up and running. Additional information gives nameserver's returned status. ORA-08267, 00000, "destroy_ora_addr: cannot close nameserver" Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver's returned status. Contact your customer support representative. ORA-08268, 00000, "create_ora_addr: cannot close nameserver" Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver's returned status. Contact your customer support representative. ORA-08269, 00000, "destroy_ora_addr: cannot destroy name" Cause: The listener's addressing information could not be removed. Action: Additional information gives nameserver's returned status. Contact your customer support representative. / 8270 - 8273 Reserved nCUBE archival ORA-08270, 00000, "sksachk: Illegal archival control string" Cause: Archive files cannot be created with the given archival control string. Action: Check that the volume exists ORA-08271, 00000, "sksabln: Buffer size not large enough for archive control string" Cause: The given archival control string expands into too many characters. Action: Reduce archive control string length. / 8273 - reserved nCUBE archival ORA-08274, 00000, "Out of memory for environment variable" Cause: There is insufficient memory to return the requested value Action: Reduce memory usage and retry. ORA-08275, 00000, "Environment variable unset" Cause: The requested environment variable is not set Action: Ensure that the variable name requested is correct. ORA-08276, 00000, "No room in nameserver for pid" Cause: There is no room to record the pid for a background process Action: Shutdown abort and restart the database. ORA-08277, 00000, "Cannot set environment variable" Cause: There is insufficient memory to expand the environment. Action: Reduce memory usage and retry. ORA-08278, 00000, "Cannot get CPU statistics" Cause: Could not retrieve CPU times because n_stat failed. Action: Contact customer support. ORA-08308, 00000, "sllfop: Cannot open file" Cause: Oracle could not open a file. Action: Check the Unix errno returned as additional information. ORA-08309, 00000, "sllfop: Cannot fstat file" Cause: Oracle could not obtain information about an open file. Action: Check the Unix errno returned as additional information. ORA-08310, 00000, "sllfop: Bad value for recsize" Cause: An illegal value for the record size was specified. Action: Specify a value for the recsize option that is greater than 0. ORA-08311, 00000, "sllfop: bad value for maxrecsize" Cause: An illegal value for the maximum record size was specified. Action: Specify a value for the maxrecsize option that is greater than 0. ORA-08312, 00000, "sllfop: unrecognized processing option" Cause: An unrecognized processing option was specified. Action: Check the Oracle for nCUBE 2 User's Guide for valid options. ORA-08313, 00000, "sllfop: could not allocate buffers" Cause: Memory for the load buffers could not be allocated. Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again. ORA-08314, 00000, "sllfcf: Error closing file" Cause: An error occurred trying to close a file. Action: Check the Unix errno returned as additional information. ORA-08315, 00000, "sllfrb: Error reading file" Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. ORA-08316, 00000, "sllfsk: Error seeking in file." Cause: The lseek system call returned an error. Action: Check the Unix errno returned as additional information. ORA-08317, 00000, "sllfsk: Error seeking in file." Cause: The lseek system call returned an error. Action: Check the Unix errno returned as additional information. ORA-08318, 00000, "sllfsk: Error reading file" Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. ORA-08319, 00000, "sllfsk: Error reading file" Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. / / 8320 - 8329 Reserved for scn.c ORA-08320, 00000, "scnget: Call to scnget before scnset or scnfnd." Cause: An internal error Action: Contact your customer support representative. ORA-08321, 00000, "scnmin: NOT IMPLEMENTED YET" Cause: An internal error Action: Contact your customer support representative. ORA-08322, 00000, "scnmin: open/convert of bias lock failed" Cause: A call to the lkmgr failed to open and convert the bias lock Action: Check to make sure the lkmgr is up. ORA-08323, 00000, "scnmin: close of bias lock failed" Cause: A call to the lkmgr failed to close the bias lock Action: Check to make sure the lkmgr is up. ORA-08330, 00000, "Printing not supported" Cause: An attempt was made to automatically spool a file to the printer Action: none ORA-08331, 00000, "Wait operation timed out" Cause: Oracle timed out waiting for an event Action: Contact your Oracle support representative ORA-08332, 00000, "rollback segment #%s specified not available" Cause: (same as 1545) Action: (same as 1545). Also, make sure you have created enough rollback segments for the number of instances you are trying to start. / / 8340-8359 Reserved for nCUBE redo server errors / ORA-08340, 00000, "This command not allowed on nCUBE, only one thread is ever used." Cause: An illegal command was executed for the nCUBE platform. Action: There is no need to issue this command. ORA-08341, 00000, "On nCUBE, this command can only be executed from instance 1." Cause: A command that can only be issued on instance 1 was issued elsewhere. Action: Log on to instance 1 and repeat the command. ORA-08342, 00000, "sropen: failed to open a redo server connection" Cause: An error occurred trying to connect to the redo server. Action: The OS specific error message should tell you what to do. ORA-08343, 00000, "srclose: failed to close a redo server connection" Cause: An error occurred trying to close the redo server connection. Action: The OS specific error message should tell you what to do. ORA-08344, 00000, "srapp: failed to send redo data to the redo server" Cause: An error occurred trying to send redo to the redo server. Action: The OS specific error message should tell you what to do. / / 8363 - 8399 Reserved for nCUBE sosd errors (unassigned) / /8362 Reserved / / 8400 UTL_RAW and UTL_PG error and warning messages / / Start UTL_RAW and UTL_PG messages / / / / / CONTENTS: / Generic Base Messages for: / Procedural Gateway for APPC Administration Utility: Release 3.3.0 / / NOTES: / / These messages are include in ORAUS.MSG and translated message files / / rherwadk 04/09/96 - add error message for max_dump_file_size parameter / hasun 04/01/96 - Add message #12028 / aroy 03/14/96 - reserve subrange for lob calls / dchatter 03/13/96 - Fix 24307 error / rxgovind 03/06/96 - add error 22929 / slari 03/05/96 - add kpu error 243xxx / gngai 02/15/96 - PDML: change PDML error 12827 to 12828 / gngai 02/15/96 - PDML: added itl deadlock error / gngai 02/13/96 - PDML: added errors for parallel txns / ashgupta 02/08/96 - Add 12023, 12024 (missing index, missing PK info) / ashgupta 02/08/96 - Add 12022, 12025 (altering snapshot log) / ltan 02/08/96 - add 1687 / akruglik 02/07/96 - add messages for LOGGING/NOLOGGING / akruglik 02/01/96 - add msg 14101 / sdas 02/01/96 - non-key overflow / hasun 01/31/96 - Add 12021: snapshot is corrupt / akruglik 01/31/96 - add msg 14100 / akruglik 01/31/96 - shorten message 14052 / hasun 01/22/96 - Add 12019: master table is a remote object / ssamu 01/22/96 - remove unused error message / jwlee 01/18/96 - tablespace-relative DBAs / hasun 01/17/96 - Add 12018: can not create a complex, pk snapshots / akruglik 01/14/96 - merge up to RDBMS_PTI_SUN4_960112 / akruglik 01/11/96 - get rid of msg 14087 / ashgupta 01/10/96 - Adding error 12017 (alter snapshot) / gswart 01/10/96 - Add event to indicate presence of a debugger / ssamu 01/09/96 - modify partition / ssamu 01/09/96 - support validate INTO