Complete list of ALL ORA errors
Though it is easy to find any Oracle error through google, ORA Training presents complete list of all ORA errors in single downloadable file for handy reference in situations where you may not have internet access. Save it for your reference.
List of ALL ORA- Errors:
| ORA-00001 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. |
| ORA-00017 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 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 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 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 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 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 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 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 ORA-00025, 00000, “failed to allocate %s” Cause: Out of memory. Action: Restart with larger sga heap. |
| ORA-00026 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 ORA-00027, 00000, “cannot kill current session” Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session. Action: None. |
| ORA-00028 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 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 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 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 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 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 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 ORA-00035, 00000, “LICENSE_MAX_USERS cannot be less than current number of users” Cause: Action: |
| ORA-00036 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 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 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-00039 ORA-00039, 00000, “error during periodic action” Cause: An unexpected error occurred while executing a periodically invoked action. Action: Check the error stack for detailed error information. |
| ORA-00040 ORA-00040, 00000, “active time limit exceeded – call aborted” Cause: The Resource Manager SWITCH_TIME limit was exceeded. Action: Reduce the complexity of the update or query, or contact your database administrator for more information. |
| ORA-00041 ORA-00041, 00000, “active time limit exceeded – session terminated” Cause: The Resource Manager SWITCH_TIME limit was exceeded. Action: Reduce the complexity of the update or query, or contact your database administrator for more information. |
| ORA-00042 ORA-00042, 0000, “Unknown Service name %s” Cause: An attempt was made to use an invalid application service. Action: Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package. |
| ORA-00043 ORA-00043, 00000, “remote operation failed” Cause: Execution of the inter-instance operation failed. Action: Check the status of the target instance. The operation may have partially executed. Verify the result of the intended operation. |
| ORA-00044 ORA-00044, 00000, “timed_statistics must be TRUE when statistics_level is not BASIC” Cause: The user attempted to set timed_statistics to FALSE when statistics_level was not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics when statistics_level is set to TYPICAL or ALL. Action: Either set timed_statistics to TRUE or set statistics_level to BASIC. |
| ORA-00050 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 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 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 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 ORA-00054, 00000, “resource busy and acquire with NOWAIT specified or timeout expired” Cause: Interested resource is busy. Action: Retry if necessary or increase timeout. |
| ORA-00055 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 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 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 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 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 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 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 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 ORA-00063, 00000, “maximum number of log files exceeded %s” Cause: The number of log files specificied exceeded the maximum number of log files supported in this release. Action: Re-create the control file with the highest number of log files no greater than the maximum supported in this release. |
| ORA-00064 ORA-00064, 00000, “object is too large to allocate on this O/S (%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 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 ORA-00066, 00000, “SID %s contains an illegal character” Cause: The specified SID contains an illegal character which cannot occur in an SPFILE setting. Illegal characters include ,#”‘=() and whitespace. Action: Use a SID that does not contain a special character or whitespace. |
| ORA-00067 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 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 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. |
| ORA-00070 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 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 ORA-00072, 00000, “process \”%s\” is not active” Cause: An invalid process was specified. Action: Specify a valid process. |
| ORA-00073 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 ORA-00074, 00000, “no process has been specified” Cause: No debug process has been specified. Action: Specify a valid process. |
| ORA-00075 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 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 ORA-00077, 00000, “dump %s is not valid” Cause: An attempt was made to invoke an invalid dump. Action: Try another dump. |
| ORA-00078 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 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 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 <extra + level> to dump global area <level> as well as <extra> bytes for every pointer; <extra> must be a multiple of 4. |
| ORA-00081 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 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 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 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 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 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 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 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 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 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. |
| ORA-00091 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 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 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 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 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 ORA-00097, 00000, “use of Oracle SQL feature not in SQL92 %s Level” Cause: Usage of Oracle’s SQL extensions. Action: |
| ORA-00098 ORA-00098, 00000, “creating or mounting the database requires a parameter file” Cause: An attempt was made to create or mount the database when the instance was started without a parameter file. Action: Restart the instance with a parameter file. |
| ORA-00099 ORA-00099, 00000, “warning: no parameter file was specified” Cause: Even though no parameter file was specified, the instance was started. Action: None. |
| ORA-00100 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. |
| ORA-00101 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 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 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 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 ORA-00105, 00000, “too many dispatcher configurations” Cause: Too many dispatcher configurations have been specified. No more can be added. Action: Consolidate the dispatcher configurations if possible. |
| ORA-00106 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 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 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-00109 ORA-00109, 00000, “invalid value for attribute %s: %s” Cause: The value specified for the attribute was incorrect. Action: Refer to the manual for the proper values. |
| ORA-00110 ORA-00110, 00000, “invalid value %s for attribute %s, must be between %s and %s” Cause: The value specified for the attribute was incorrect. Action: Specify a value within the range allowed. |
| ORA-00111 ORA-00111, 00000, “invalid attribute %s” Cause: The specified attribute was not recognized. Action: Refer to the manual for the proper keyword to use to specify a dispatcher attribute. |
| ORA-00112 ORA-00112, 00000, “value of %s is null” Cause: The attribute was specified with no value. Action: Specify a non-null value. |
| ORA-00113 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 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 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 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 ORA-00117, 00000, “PROTOCOL, ADDRESS or DESCRIPTION must be specified” Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified. Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers. |
| ORA-00118 ORA-00118, 00000, “Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified” Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified. Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers. |
| ORA-00119 ORA-00119, 00000, “invalid specification for system parameter %s” Cause: The syntax for the specified parameter is incorrect. Action: Refer to the Oracle Reference Manual for the correct syntax. |
| ORA-00122 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 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-00125 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 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 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 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’ |
| ORA-00129 ORA-00129, 00000, “listener address validation failed ‘%s’” Cause: An error was encountered while validating the listener address. Action: Resolve error or contact your ORACLE representative. |
| ORA-00130 ORA-00130, 00000, “invalid listener address ‘%s’” Cause: The listener address specification is not valid. Action: Make sure that all fields in the listener address (protocol, port, host, key, …) are correct. |
| ORA-00131 ORA-00131, 00000, “network protocol does not support registration ‘%s’” Cause: The specified protocol does not support async notification. Action: Refer to the manual for information on supported network protocols. |
| ORA-00132 ORA-00132, 00000, “syntax error or unresolved network name ‘%s’” Cause: Listener address has syntax error or cannot be resolved. Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct. |
| ORA-00133 ORA-00133, 00000, “value of %s is too long” Cause: The value specified for the attribute was too long. Action: Use shorter names and keywords or remove unneeded blanks. |
| ORA-00134 ORA-00134, 00000, “invalid DISPATCHERS specification #%s” Cause: The syntax for the n-th DISPATCHERS specification was incorrect. Action: Refer to the Oracle Reference Manual for the correct syntax. |
| ORA-00150 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 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 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 ORA-00153, 00000, “internal error in XA library” Cause: The XA library could not access thread-specific pointers. Action: Contact customer support. |
| ORA-00154 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 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. |
| ORA-00160 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 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 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 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 ORA-00164, 00000, “distributed autonomous transaction disallowed within migratable distributed transaction” Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction. Action: Roll back or commit the current distributed transaction first. |
| ORA-00165 ORA-00165, 00000, “migratable distributed autonomous transaction with remote operation is not allowed” Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation. Action: |
| ORA-00166 ORA-00166, 00000, “remote/local nesting level is too deep” Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table. Action: Rearrange the query or co-locate the functions with the tables. |
| ORA-00200 ORA-00200, 00000, “control file could not be created” Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again. |
| ORA-00201 ORA-00201, 00000, “control file version %s incompatible with ORACLE version %s” Cause: The control file was created by incompatible software. Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. |
| ORA-00202 ORA-00202, 00000, “control file: ‘%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 ORA-00203, 00000, “using the wrong control files” Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. Action: Check that the correct control files were specified. |
| ORA-00204 ORA-00204, 00000, “error in reading (block %s, # blocks %s) of control file” Cause: A disk I/O failure was detected on reading the control file. 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 ORA-00205, 00000, “error in identifying control file, check alert log for more info” Cause: The system could not find a control file of the specified name and // size. Action: Check that ALL control files are online and that they are the same files that the system created at cold start time. |
| ORA-00206 ORA-00206, 00000, “error in writing (block %s, # blocks %s) of control file” Cause: A disk I/O failure was detected on writing the control file. 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 ORA-00207, 00000, “control files are not for the same database” Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name. Action: Check that the control file is for the correct database and is not an old version. |
| ORA-00208 ORA-00208, 00000, “number of control file names exceeds limit of %s” Cause: An attempt was made to use more control files than Oracle supports. Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files. |
| ORA-00209 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 ORA-00210, 00000, “cannot open the specified control file” Cause: Cannot open the control file. Action: Check to make sure the control file exists and is not locked by // some other program. |
| ORA-00211 ORA-00211, 00000, “control file does not match previous control files” Cause: A control file was specified that belongs to another database. Action: Find and install the correct control file. |
| ORA-00212 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 ORA-00213, 00000, “cannot reuse control file; old file size %s, %s required” Cause: To reuse a control file, 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 ORA-00214, 00000, “control file ‘%s’ version %s inconsistent with file ‘%s’ version %s” Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used. Action: Use a consistant set of control files, 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 ORA-00215, 00000, “must be at least one control file” Cause: No control file is specified or the control file specified does not exist. Action: Specify at least one valid control file and retry the operation. |
| ORA-00216 ORA-00216, 00000, “control file could not be resized for migration from 8.0.2″ Cause: The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed. Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. |
| ORA-00217 ORA-00217, 00000, “control file could not be resized for new record types” Cause: The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed. Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. |
| ORA-00218 ORA-00218, 00000, “block size %s of control file ‘%s’ does not match DB_BLOCK_SIZE (%s)” Cause: The block size as stored in the control file 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 control file has either been corrupted or belongs to a different database. Action: Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value. |
| ORA-00219 ORA-00219, 00000, “required control file size (%s logical blocks) exceeds maximum allowable size (%s logical blocks)” Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file 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. |
| ORA-00220 ORA-00220, 00000, “control file not mounted by first instance, check alert log for more info” Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file. Action: Find and install the correct control file. |
| ORA-00221 ORA-00221, 00000, “error on write to control file” Cause: An error occurred when writing to one or more of the control files. Action: See accompanying messages. |
| ORA-00222 ORA-00222, 00000, “operation would reuse name of a currently mounted control file” 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 control file. Action: Retry the operation with a different filename. |
| ORA-00223 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 ORA-00224, 00000, “control file resize attempted with illegal record type (%s)” Cause: An attempt was made to expand or shrink the control file 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 ORA-00225, 00000, “expected size %s of control file differs from actual size %s” Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. // This usually indicates that the control file was corrupted. Action: Restore a good copy of the control file. |
| ORA-00226 ORA-00226, 00000, “operation disallowed while alternate control file open” Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access. Action: Retry the operation after calling cfileUseCurrent. |
| ORA-00227 ORA-00227, 00000, “corrupt block detected in control file: (block %s, # blocks %s)” Cause: A block header corruption or checksum error was detected on reading the control file. Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command. |
| ORA-00228 ORA-00228, 00000, “length of alternate control file 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 ORA-00229, 00000, “operation disallowed: already hold snapshot control file enqueue” Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue. Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue. |
| ORA-00230 ORA-00230, 00000, “operation disallowed: snapshot control file enqueue unavailable” Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue. Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates. |
| ORA-00231 ORA-00231, 00000, “snapshot control file has not been named” Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified. Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName. |
| ORA-00232 ORA-00232, 00000, “snapshot control file is nonexistent, corrupt, or unreadable” Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time). |
| ORA-00233 ORA-00233, 00000, “copy control file is corrupt or unreadable” Cause: The specified copy control file 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 ORA-00234, 00000, “error in identifying or opening snapshot or copy control file” Cause: A snapshot or copy control file 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 control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively. |
| ORA-00235 ORA-00235, 00000, “control file read without a lock inconsistent due to concurrent update” Cause: Concurrent update activity on a control file caused a process // to read inconsistent information from the control file without a lock. Action: Retry the operation. |
| ORA-00236 ORA-00236, 00000, “snapshot operation disallowed: mounted control file is a backup” Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. Action: Mount a current control file and retry the operation. |
| ORA-00237 ORA-00237, 00000, “snapshot operation disallowed: control file newly created” Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. Action: Mount a current control file and retry the operation. |
| ORA-00238 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. |
| ORA-00239 ORA-00239, 00000, “timeout waiting for control file enqueue: held by ‘%s’ for more than %s seconds” Cause: The specified process waited the maximum allowed time for the control file enqueue. Action: Restart the blocking instance indicated in the incident trace file or reboot the blocking node. |
| ORA-00240 ORA-00240, 00000, “control file enqueue held for more than %s seconds” Cause: The current process did not release the control file enqueue within the maximum allowed time. Action: Reissue any commands that failed and contact Oracle Support Services with the incident information. |
| ORA-00250 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 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 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 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 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 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 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 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 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 ORA-00259, 00000, “log %s of open instance %s (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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-00277, 00000, “illegal option to the UNTIL recovery flag %s” Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the UNTIL keyword. Action: Correct the syntax. |
| ORA-00278 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-00293, 00000, “control file out of sync with redo log” Cause: The redo log file and control file 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 control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause. |
| ORA-00294 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 ORA-00295, 00000, “datafile/tempfile number %s is invalid, must be between 1 and %s” Cause: An invalid file number was specified. Action: Specify a valid datafile or tempfile number and retry the operation. |
| ORA-00296 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 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 ORA-00298, 00000, “Missing or invalid attribute value” Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT Action: Correct the syntax and retry the command. |
| ORA-00299 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. |
| ORA-00300 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 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 ORA-00302, 00000, “limit of %s logs exceeded” Cause: The maximum number of redo log files has been exceeded. Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES if the compatibility is lower than 10.2.0. // Otherwise, allocate more storage space for the control file. |
| ORA-00303 ORA-00303, 00000, “cannot process Parallel Redo” Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo. Action: Use a later release that supports Parallel Redo. to process this log. |
| ORA-00304 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 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 control file. This redo log file is not from the current database. Action: Specify the correct redo log file, then retry the operation. |
| ORA-00306 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 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 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 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 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 |
| ORA-00311 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 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 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 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 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 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 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 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 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 control file. The log is probably an incorrectly restored backup. Action: Restore correct file or reset logs. |
| ORA-00320 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-00334, 00000, “archived log: ‘%s’” Cause: Reporting filename for details of another error Action: See associated error messages |
| ORA-00335 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 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 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 ORA-00338, 00000, “log %s of thread %s is more recent than control file” Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file 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 control file change sequence number until it is great enough. Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. |
| ORA-00339 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 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 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 control file. Action: Restore correct file or reset logs. |
| ORA-00342 ORA-00342, 00000, “archived log does not have expected resetlogs SCN %s” Cause: Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo. Action: Supply the correct log file. |
| ORA-00344 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 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 ORA-00346, 00000, “log member marked as STALE and closed” Cause: A log file member was no longer complete. Action: Correct the underlying problem by referring to the other error messages found with this one. |
| ORA-00347 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 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 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 ORA-00350, 00000, “log %s of instance %s (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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-00370 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 ORA-00371, 00000, “not enough shared pool memory, should be atleast %s bytes” Cause: Init.ora parameter shared_pool_size is too small Action: Increase the parameter value |
| ORA-00372 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 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 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 ORA-00375, 00000, “Cannot allocate buffer cache state object” Document: NO Cause: No state obeject elements on freelist Action: None. |
| ORA-00376 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 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 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 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 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 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), db_cache_advice } 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. Cache advisory can only be enabled with the new cache parameters. // |
| ORA-00382 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 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_<n>K_cache_size to zero while there were still online tablespaces with blocksize <n>K. 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 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. |
| ORA-00385 ORA-00385, 00000, “cannot enable Very Large Memory with new buffer cache parameters” 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 use_indirect_data_buffers is set to TRUE. This is illegal. Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters. |
| ORA-00386 ORA-00386, 00000, “use_indirect_data_buffers not supported” 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. // |
| ORA-00390 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 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 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 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 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 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 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 two-pass algorithm. This usually requires making more main memory available to the recovery process. |
| ORA-00397 ORA-00397, 00000, “instance recovery process terminated with error” Cause: The foreground process doing instance recovery died. Action: Check the foreground trace file for the cause of recovery failure. |
| ORA-00398 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 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. |
| ORA-00400 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 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 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 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 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 ORA-00405, 00000, “compatibility type \”%s\”" Cause: Reporting a type associated with another error. Action: See accompanying error |
| ORA-00406 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 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 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. |
| ORA-00409 ORA-00409, 00000, “COMPATIBLE needs to be %s or higher to use AUTO SEGMENT SPACE MANAGEMENT” Cause: This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value. Action: Shutdown and startup with the specified compatibility setting. |
| ORA-00436 ORA-00436, 00000, “ORACLE is not licensed. Contact Oracle Corp. for assistance” Cause: Action: |
| ORA-00437 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 ORA-00438, 00000, “%s Option not installed” Cause: The specified option is not installed. Action: Purchase and install the option. |
| ORA-00439 ORA-00439, 00000, “feature not enabled: %s” Cause: The specified feature is not enabled. Action: Do not attempt to use this feature. |
| ORA-00443 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 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 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 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 ORA-00447, 00000, “fatal error in background process” Cause: One of the background processes died unexpectedly. Action: Warm start the system. |
| ORA-00448 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 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. |
| ORA-00450 ORA-00450, 00000, “background process ‘%s’ did not start” Cause: The specified process did not start. Action: Consult the error code, and the trace file for the process. |
| ORA-00451 ORA-00451, 00000, “foreground process died unexpectedly” Cause: The foreground process for the new connection did not start. Action: Reconnect to Oracle. |
| ORA-00452 ORA-00452, 00000, “foreground process unexpectedly terminated with error %s” Cause: The foreground process for the new connection did not start. Action: Reconnect to Oracle. |
| ORA-00453 ORA-00453, 00000, “backgroud process ‘%s’ is dead” Cause: The background process that was being messaged was dead or its incarnation was invalid. Action: Restart the background process. |
| ORA-00469 ORA-00469, 00000, “CKPT process terminated with error” Cause: The checkpoint process died Action: Warm start instance |
| ORA-00470 ORA-00470, 00000, “LGWR process terminated with error” Cause: The log writer process died Action: Warm start instance |
| ORA-00471 ORA-00471, 00000, “DBWR process terminated with error” Cause: The database writer process died Action: Warm start instance |
| ORA-00472 ORA-00472, 00000, “PMON process terminated with error” Cause: The process cleanup process died Action: Warm start instance |
| ORA-00473 ORA-00473, 00000, “ARCH process terminated with error” Cause: The archive process died Action: Warm start instance |
| ORA-00474 ORA-00474, 00000, “SMON process terminated with error” Cause: The system cleanup process died Action: Warm start instance |
| ORA-00475 ORA-00475, 00000, “TRWR process terminated with error” Cause: The system tracing process died Action: Warm start instance |
| ORA-00476 ORA-00476, 00000, “RECO process terminated with error” Cause: The distributed transaction (two-phase commit) recovery process died. Action: Warm start instance |
| ORA-00477 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-00478 ORA-00478, 00000, “SMON process terminated due to error %s” Cause: SMON was unable to service the requests due to error in cleanup of resources Action: Warm start instance |
| ORA-00479 ORA-00479, 00000, “RVWR process terminated with error %s” Cause: The RVWR process died Action: Warm start instance |
| ORA-00480 ORA-00480, 00000, “LCK* process terminated with error” Cause: A system lock process died Action: Warm start instance |
| ORA-00481 ORA-00481, 00000, “LMON process terminated with error” Cause: The global enqueue service monitor process died Action: Warm start instance |
| ORA-00482 ORA-00482, 00000, “LMD* process terminated with error” Cause: A global enqueue service daemon process died Action: Warm start instance |
| ORA-00483 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 ORA-00484, 00000, “LMS* process terminated with error” Cause: A global cache service process died Action: Warm start instance |
| ORA-00485 ORA-00485, 00000, “DIAG process terminated with error %s” Cause: A global diagnostic process died Action: Wait for process to restart |
| ORA-00486 ORA-00486, 00000, “ASMB process terminated with error” Cause: An ASM background process died. Action: Warm start instance. Also check that ASM Instance is running. |
| ORA-00487 ORA-00487, 00000, “CTWR process terminated with error” Cause: The change tracking process died Action: Warm start instance |
| ORA-00488 ORA-00488, 00000, “RBAL process terminated with error” Cause: The ASM rebalance coordinator process died. Action: Warm start instance. |
| ORA-00489 ORA-00489, 00000, “ARB* process terminated with error” Cause: An ASM rebalance worker process died. Action: Wait for process to restart. |
| ORA-00490 ORA-00490, 00000, “PSP process terminated with error” Cause: The process spawner died Action: Warm start instance |
| ORA-00491 ORA-00491, 00000, “RMS0 process terminated with error” Cause: The RAC Management Process died |
| ORA-00492 ORA-00492, 00000, “GTX* process terminated with error” Cause: A global transaction background process died. Action: Warm start instance |
| ORA-00493 ORA-00493, 00000, “GMON process terminated with error” Cause: The ASM disk group monitor process died Action: Warm start instance |
| ORA-00494 ORA-00494, 00000, “enqueue%s held for too long%s by ‘%s’” Cause: The specified process did not release the enqueue within the maximum allowed time. Action: Reissue any commands that failed and contact Oracle Support Services with the incident information. |
| ORA-00566 ORA-00566, 00000, “cannot request processor group – NUMA not enabled” Cause: Cannot start process in a requested processor group when the NUMA feature is disabled. Action: Start the process without requesting a NUMA processor group. |
| ORA-00567 ORA-00567, 00000, “Requested processor group %s is too large (maximum %s)” Cause: The process could not be started in the requested processor group. Action: Start the process in another processor group. |
| ORA-00568 ORA-00568, 00000, “Maximum number of interrupt handlers exceeded” Cause: User specified too many ^c handlers Action: Remove some old handlers. |
| ORA-00569 ORA-00569, 00000, “Failed to acquire global enqueue.” Cause: A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention. Action: Check for and resolve prior errors on all instances in the cluster. If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization parameters. |
| ORA-00574 ORA-00574, 00000, “osndnt: $CANCEL failure (break)” Cause: Action: |
| ORA-00575 ORA-00575, 00000, “osndnt: $QIO failure (send out-of-band break)” Cause: Action: |
| ORA-00576 ORA-00576, 00000, “in-band break protocol error” Cause: Action: |
| ORA-00577 ORA-00577, 00000, “out-of-band break protocol error” Cause: Action: |
| ORA-00578 ORA-00578, 00000, “reset protocol error” Cause: Action: |
| ORA-00579 ORA-00579, 00000, “osndnt: server received malformed connection request” Cause: Action: |
| ORA-00580 ORA-00580, 00000, “protocol versions do not match” Cause: Action: |
| ORA-00581 ORA-00581, 00000, “osndnt: cannot allocate context area” Cause: Action: |
| ORA-00582 ORA-00582, 00000, “osndnt: cannot deallocate context area” Cause: Action: |
| ORA-00583 ORA-00583, 00000, “osndnt: $TRNLOG failure” Cause: Action: |
| ORA-00584 ORA-00584, 00000, “cannot close connection” Cause: Action: |
| ORA-00585 ORA-00585, 00000, “host name has incorrect form” Cause: Action: |
| ORA-00586 ORA-00586, 00000, “osndnt: LIB$ASN_WTH_MBX failure” Cause: Action: |
| ORA-00587 ORA-00587, 00000, “cannot connect to remote host” Cause: Action: |
| ORA-00588 ORA-00588, 00000, “message from host was too short” Cause: Action: |
| ORA-00589 ORA-00589, 00000, “message from host had incorrect data length” Cause: Action: |
| ORA-00590 ORA-00590, 00000, “message from host had incorrect message type” Cause: Action: |
| ORA-00591 ORA-00591, 00000, “incorrect number of bytes written” Cause: Action: |
| ORA-00592 ORA-00592, 00000, “osndnt: $QIO failure (mailbox queue)” Cause: Action: |
| ORA-00593 ORA-00593, 00000, “osndnt: $DASSGN failure (network device)” Cause: Action: |
| ORA-00594 ORA-00594, 00000, “osndnt: $DASSGN failure (mailbox)” Cause: Action: |
| ORA-00595 ORA-00595, 00000, “osndnt: $QIO failure (receive)” Cause: Action: |
| ORA-00596 ORA-00596, 00000, “osndnt: $QIO failure (send)” Cause: Action: |
| ORA-00597 ORA-00597, 00000, “osndnt: $QIO failure (mailbox requeue)” Cause: Action: |
| ORA-00598 ORA-00598, 00000, “osndnt: $QIO failure (mailbox read)” Cause: Action: |
| ORA-00600 ORA-00600, 00000, “internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]” Cause: This is the generic internal error number for Oracle program // exceptions. This indicated that a process encountered an // exceptional condition. Action: Report as a bug – the first argument is the internal error number. |
| ORA-00601 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 ORA-00602, 00000, “internal programming exception” Cause: Internal programming exception Action: Report as bug |
| ORA-00603 ORA-00603, 00000, “ORACLE server session terminated by fatal error” Cause: An ORACLE server session was in an unrecoverable state. Action: Login to ORACLE again so a new server session will be created |
| ORA-00604 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. |
| ORA-00606 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 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-00608 ORA-00608, 00000, “testing error [%s] [%s] [%s] [%s] [%s]” Cause: Internal error reserved for testing. Action: call Oracle Support |
| ORA-00609 ORA-00609, 00000, “could not attach to incoming connection” Cause: Oracle process could not answer incoming connection Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. |
| ORA-00610 ORA-00610, 00000, “Internal error code” Cause: Oracle process started too late Action: This error should never be seen by the customer. Contact Oraclce Support |
| ORA-00700 ORA-00700, 00000, “soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]” Cause: Internal inconsitency that will not crash a process Action: Report as a bug – the first argument is the internal error. |
| ORA-00701 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 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 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 ORA-00704, 00000, “bootstrap process failure” Cause: Failure in processing bootstrap data – see accompanying error. Action: Contact your customer support representative. |
| ORA-00705 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-00706 ORA-00706, 00000, “error changing format of file ‘%s’” Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline. Action: Make the file read-write or bring the file online and set the BLK0_FMTCHG event. |
| ORA-00710 ORA-00710, 00000, “new tablespace name is the same as the old tablespace name” Cause: An attempt to rename a tablespace failed because the new name is the same as the old name. Action: No action required. |
| ORA-00711 ORA-00711, 00000, “new tablespace name is invalid” Cause: An attempt to rename a tablespace failed because the new name is invalid. Action: Choose a valid new name and retry the command. |
| ORA-00712 ORA-00712, 00000, “cannot rename system tablespace” Cause: An attempt to rename the system tablespace failed. Action: No action required. |
| ORA-00720 ORA-00720, 00000, “ALTER DATABASE RESET COMPATIBILITY command has been de-supported” Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i. Action: No action required. |
| ORA-00721 ORA-00721, 00000, “changes by release %s cannot be used by release %s” Cause: An attempt to import a tablespace failed because the tablespace contains changes 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 initialization parameter file. |
| ORA-00722 ORA-00722, 00000, “Feature \”%s\”" Cause: Reporting name of the feature for details of another error. Action: See associated error message. |
| ORA-00723 ORA-00723, 00000, “Initialization parameter COMPATIBLE must be explicitly set” Cause: Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user. Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used. |
| ORA-00724 ORA-00724, 00000, “ALTER DATABASE CONVERT command has been de-supported” Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle 10i. Action: No action required. |
| ORA-00725 ORA-00725, 00000, “Desupported ALTER DATABASE SET STANDBY clause specified: %s” Cause: A deprecated ALTER DATABASE SET STANDBY was specified. Action: No action required. |
| ORA-00740 ORA-00740, 00000, “datafile size of (%s) blocks exceeds maximum file size” Cause: The user specified datafile size exceeded maximum file size. Action: Please check REFERENCE for maximum size. Reduce the size and retry. |
| ORA-00741 ORA-00741, 00000, “logfile size of (%s) blocks exceeds maximum logfile size” Cause: The user specified logfile size exceeded maximum logfile size. Action: Please check REFERENCE for maximum size. Reduce the size and retry. |
| ORA-00750 ORA-00750, 00000, “database has been previously mounted and dismounted” Cause: The instance has already mounted and dismounted the database, which is only allowed once in its lifetime. Action: Shut down the database. |
| ORA-00751 ORA-00751, 00000, “could not obtain resilvering status for file” Cause: An error occurred while obtaining the mirror resilvering status of a file. Action: Refer to other error messages shown for additional details of the problem. |
| ORA-00752 ORA-00752, 00000, “recovery detected a lost write of a data block” Cause: A write of a data block to the storage are was lost during normal database operation or on the primary database. Action: Flashback or restore from backup the database as described in the Backup and Recovery Manual. |
| ORA-00816 ORA-00816, 00000, “error message translation failed” Cause: Action: |
| ORA-00820 ORA-00820, 00000, “Specified value of sga_max_size is too small, needs to be at least %sM” Cause: The specified value of sga_max_size is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc. Action: Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified. |
| ORA-00821 ORA-00821, 00000, “Specified value of sga_target %sM is too small, needs to be at least %sM” Cause: The specified value of sga_target is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc. Action: Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified. |
| ORA-00822 ORA-00822, 00000, “MMAN process terminated with error” Cause: The Memory Management process died. Action: Warm start instance |
| ORA-00823 ORA-00823, 00000, “Specified value of sga_target greater than sga_max_size” Cause: The specified value of sga_target is greater than sga_max_size. Action: Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize. |
| ORA-00824 ORA-00824, 00000, “cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings” Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings. Action: Check the other error messages for additional information. |
| ORA-00825 ORA-00825, 00000, “cannot set DB_BLOCK_BUFFERS if SGA_TARGET or MEMORY_TARGET is set” Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set. Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters, and do not use DB_BLOCK_BUFFERS which is an old cache parameter. |
| ORA-00826 ORA-00826, 00000, “cannot set SGA_TARGET or MEMORY_TARGET for an ASM instance” Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance. Action: Do not set SGA_TARGET or MEMORY_TARGET. |
| ORA-00827 ORA-00827, 00000, “could not shrink sga_target to specified value” Cause: Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes. Action: Do not set sga_target to a value below the current value without first shrinking the individual SGA components. |
| ORA-00828 ORA-00828, 00000, “specified value of shared_pool_reserved_size inconsistent with internal settings” Cause: Unable to set shared_pool_reserved_size to specified value if SGA_TARGET set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log. Action: If possible, do not set shared_pool_reserved_size without setting shared_pool_size if SGA_TARGET set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size. |
| ORA-00829 ORA-00829, 00000, “event to stress test self tuning SGA feature by forcing partial granules transfers” Document: NO Cause: Action: |
| ORA-00830 ORA-00830, 00000, “cannot set statistics_level to BASIC with auto-tune SGA enabled” Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC. Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again. |
| ORA-00831 ORA-00831, 00000, “event to stress test self tuning SGA feature by doing random memory broker resizes” Document: NO Cause: Action: |
| ORA-00832 ORA-00832, 00000, “no streams pool created and cannot automatically create one” Cause: A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache. Action: Please set the parameter streams_pool_size or set SGA_TARGET. |
| ORA-00833 ORA-00833, 00000, “event to test cancellation and cache protection by pinning buffers for deferred mode requests” Document: NO Cause: Action: |
| ORA-00834 ORA-00834, 00000, “Simulate 4031 during an immediate mode request in auto-sga” Document: NO Cause: Action: Set _memory_management_tracing=23 to track this event. |
| ORA-00835 ORA-00835, 00000, “Simulate memory broker disabling for code coverage” Document: NO Cause: Action: It will be reenabled on next SGA_TARGET resize |
| ORA-00836 ORA-00836, 00000, “Simulate memory transfer from system memory for startup request” Document: NO Cause: For code coverage. Action: None. |
| ORA-00837 ORA-00837, 00000, “Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET” Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET. Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET. |
| ORA-00838 ORA-00838, 00000, “Specified value of MEMORY_TARGET is too small, needs to be at least %sM” Cause: The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET. Action: Set MEMORY_TARGET to at least the recommended value. |
| ORA-00839 ORA-00839, 00000, “SGA_TARGET cannot be modified to the specified value” Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET. Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low. |
| ORA-00840 ORA-00840, 00000, “PGA_AGGREGATE_TARGET cannot be modified to the specified value” Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET. Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET. |
| ORA-00841 ORA-00841, 00000, “MEMORY_TARGET not supported on this system” Cause: MEMORY_TARGET parameter was not supported on this system as shmfs was disabled. Action: Refer to documentation for a list of supported systems. |
| ORA-00842 ORA-00842, 00000, “DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or MEMORY_TARGET” Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET. Action: Remove the incompatible parameter setting. |
| ORA-00843 ORA-00843, 00000, “Parameter not taking MEMORY_MAX_TARGET into account” Cause: The parameter was larger than MEMORY_MAX_TARGET. Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET. |
| ORA-00844 ORA-00844, 00000, “Parameter not taking MEMORY_TARGET into account” Cause: The parameter was larger than MEMORY_TARGET. Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_TARGET. |
| ORA-00845 ORA-00845, 00000, “MEMORY_TARGET not supported on this system” Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux. Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system. |
| ORA-00846 ORA-00846, 00000, “could not shrink MEMORY_TARGET to specified value” Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not succeed because the PGA and SGA components could not be shrunk. Action: Do not set MEMORY_TARGET to a value below the current value without first shrinking the individual memory components. |
| ORA-00847 ORA-00847, 00000, “MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA cannot be set together” Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set Action:Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to TRUE. |
| ORA-00848 ORA-00848, 00000, “STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET” Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET. Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL or ALL to use SGA_TARGET or MEMORY_TARGET. |
| ORA-00849 ORA-00849, 00000, “SGA_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s.” Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value. Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET. |
| ORA-00850 ORA-00850, 00000, “PGA_AGGREGATE_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s.” Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value. Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET. |
| ORA-00851 ORA-00851, 00000, “SGA_MAX_SIZE %s cannot be set to more than MEMORY_TARGET %s.” Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value. Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET. |
| ORA-00900 ORA-00900, 00000, “invalid SQL statement” Cause: Action: |
| ORA-00901 ORA-00901, 00000, “invalid CREATE command” Cause: Action: |
| ORA-00902 ORA-00902, 00000, “invalid datatype” Cause: Action: |
| ORA-00903 ORA-00903, 00000, “invalid table name” Cause: Action: |
| ORA-00904 ORA-00904, 00000, “%s: invalid identifier” Cause: Action: |
| ORA-00905 ORA-00905, 00000, “missing keyword” Cause: Action: |
| ORA-00906 ORA-00906, 00000, “missing left parenthesis” Cause: Action: |
| ORA-00907 ORA-00907, 00000, “missing right parenthesis” Cause: Action: |
| ORA-00908 ORA-00908, 00000, “missing NULL keyword” Cause: Action: |
| ORA-00909 ORA-00909, 00000, “invalid number of arguments” Cause: Action: |
| ORA-00910 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 ORA-00911, 00000, “invalid character” Cause: identifiers may not start with any ASCII character other than letters and numbers. $#_ are also allowed after the first character. Identifiers enclosed by doublequotes may contain any character other than a doublequote. Alternative quotes (q’#…#’) cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual. Action: |
| ORA-00912 ORA-00912, 00000, “input parameter too long” Cause: one of your input strings was too long Action:shorten the input parameter length |
| ORA-00913 ORA-00913, 00000, “too many values” Cause: Action: |
| ORA-00914 ORA-00914, 00000, “missing ADD keyword” Cause: Action: |
| ORA-00915 ORA-00915, 00000, “network access of dictionary table not currently allowed” Cause: Action: |
| ORA-00917 ORA-00917, 00000, “missing comma” Cause: Action: |
| ORA-00918 ORA-00918, 00000, “column ambiguously defined” Cause: Action: |
| ORA-00919 ORA-00919, 00000, “invalid function” Cause: Action: |
| ORA-00920 ORA-00920, 00000, “invalid relational operator” Cause: Action: |
| ORA-00921 ORA-00921, 00000, “unexpected end of SQL command” Cause: Action: |
| ORA-00922 ORA-00922, 00000, “missing or invalid option” Cause: Action: |
| ORA-00923 ORA-00923, 00000, “FROM keyword not found where expected” Cause: Action: |
| ORA-00924 ORA-00924, 00000, “missing BY keyword” Cause: Action: |
| ORA-00925 ORA-00925, 00000, “missing INTO keyword” Cause: Action: |
| ORA-00926 ORA-00926, 00000, “missing VALUES keyword” Cause: Action: |
| ORA-00927 ORA-00927, 00000, “missing equal sign” Cause: Action: |
| ORA-00928 ORA-00928, 00000, “missing SELECT keyword” Cause: Action: |
| ORA-00929 ORA-00929, 00000, “missing period” Cause: Action: |
| ORA-00930 ORA-00930, 00000, “missing asterisk” Cause: Action: |
| ORA-00931 ORA-00931, 00000, “missing identifier” Cause: Action: |
| ORA-00932 ORA-00932, 00000, “inconsistent datatypes: expected %s got %s” Cause: Action: |
| ORA-00933 ORA-00933, 00000, “SQL command not properly ended” Cause: Action: |
| ORA-00934 ORA-00934, 00000, “group function is not allowed here” Cause: Action: |
| ORA-00935 ORA-00935, 00000, “group function is nested too deeply” Cause: Action: |
| ORA-00936 ORA-00936, 00000, “missing expression” Cause: Action: |
| ORA-00937 ORA-00937, 00000, “not a single-group group function” Cause: Action: |
| ORA-00938 ORA-00938, 00000, “not enough arguments for function” Cause: Action: |
| ORA-00939 ORA-00939, 00000, “too many arguments for function” Cause: Action: |
| ORA-00940 ORA-00940, 00000, “invalid ALTER command” Cause: Action: |
| ORA-00941 ORA-00941, 00000, “missing cluster name” Cause: Action: |
| ORA-00942 ORA-00942, 00000, “table or view does not exist” Cause: Action: |
| ORA-00943 ORA-00943, 00000, “cluster does not exist” Cause: Action: |
| ORA-00944 ORA-00944, 00000, “insufficient number of clustered columns” Cause: Action: |
| ORA-00945 ORA-00945, 00000, “specified clustered column does not exist” Cause: Action: |
| ORA-00946 ORA-00946, 00000, “missing TO keyword” Cause: Action: |
| ORA-00947 ORA-00947, 00000, “not enough values” Cause: Action: |
| ORA-00948 ORA-00948, 00000, “ALTER CLUSTER statement no longer supported” Cause: Action: |
| ORA-00949 ORA-00949, 00000, “illegal reference to remote database” Cause: Action: |
| ORA-00950 ORA-00950, 00000, “invalid DROP option” Cause: Action: |
| ORA-00951 ORA-00951, 00000, “cluster not empty” Cause: Action: |
| ORA-00952 ORA-00952, 00000, “missing GROUP keyword” Cause: Action: |
| ORA-00953 ORA-00953, 00000, “missing or invalid index name” Cause: An index name of the form [ <identifier> . ] <identifier> is // expected but not present. If OIDINDEX clause, index name must be <identifier> Action: Enter an appropriate index name. |
| ORA-00954 ORA-00954, 00000, “missing IDENTIFIED keyword” Cause: Action: |
| ORA-00955 ORA-00955, 00000, “name is already used by an existing object” Cause: Action: |
| ORA-00956 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 ORA-00957, 00000, “duplicate column name” Cause: Action: |
| ORA-00958 ORA-00958, 00000, “missing CHECK keyword” Cause: Action: |
| ORA-00959 ORA-00959, 00000, “tablespace ‘%s’ does not exist” Cause: Action: |
| ORA-00960 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 ORA-00961, 00000, “bad datetime/interval value” Cause: Action: |
| ORA-00962 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 ORA-00963, 00000, “unsupported interval type” Cause: Action: |
| ORA-00964 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 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 ORA-00966, 00000, “missing TABLE keyword” Cause: Action: |
| ORA-00967 ORA-00967, 00000, “missing WHERE keyword” Cause: Action: |
| ORA-00968 ORA-00968, 00000, “missing INDEX keyword” Cause: Action: |
| ORA-00969 ORA-00969, 00000, “missing ON keyword” Cause: Action: |
| ORA-00970 ORA-00970, 00000, “missing WITH keyword” Cause: Action: |
| ORA-00971 ORA-00971, 00000, “missing SET keyword” Cause: Action: |
| ORA-00972 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 ORA-00973, 00000, “invalid row count estimate” Cause: Action: |
| ORA-00974 ORA-00974, 00000, “invalid PCTFREE value (percentage)” Cause: Action: |
| ORA-00975 ORA-00975, 00000, “date + date not allowed” Cause: Action: |
| ORA-00976 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 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 ORA-00978, 00000, “nested group function without GROUP BY” Cause: Action: |
| ORA-00979 ORA-00979, 00000, “not a GROUP BY expression” Cause: Action: |
| ORA-00980 ORA-00980, 00000, “synonym translation is no longer valid” Cause: A synonym did not translate to a legal target object. This could happen for one of the following reasons: 1. The target schema does not exist. 2. The target object does not exist. 3. The synonym specifies an incorrect database link. 4. The synonym is not versioned but specifies a versioned target object. Action: Change the synonym definition so that the synonym points at a legal target object. |
| ORA-00981 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 ORA-00982, 00000, “missing plus sign” Cause: Action: |
| ORA-00983 ORA-00983, 00000, “cannot audit or noaudit SYS user actions” Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions. Action: Execute the statement again with a valid user. |
| ORA-00984 ORA-00984, 00000, “column not allowed here” Cause: Action: |
| ORA-00985 ORA-00985, 00000, “invalid program name” Cause: Action: |
| ORA-00986 ORA-00986, 00000, “missing or invalid group name(s)” Cause: Action: |
| ORA-00987 ORA-00987, 00000, “missing or invalid username(s)” Cause: Action: |
| ORA-00988 ORA-00988, 00000, “missing or invalid password(s)” Cause: Action: |
| ORA-00989 ORA-00989, 00000, “too many passwords for usernames given” Cause: Action: |
| ORA-00990 ORA-00990, 00000, “missing or invalid privilege” Cause: Action: |
| ORA-00991 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 ORA-00992, 00000, “invalid format for REVOKE command” Cause: Action: |
| ORA-00993 ORA-00993, 00000, “missing GRANT keyword” Cause: Action: |
| ORA-00994 ORA-00994, 00000, “missing OPTION keyword” Cause: Action: |
| ORA-00995 ORA-00995, 00000, “missing or invalid synonym identifier” Cause: Action: |
| ORA-00996 ORA-00996, 00000, “the concatenate operator is ||, not |” Cause: Action: |
| ORA-00997 ORA-00997, 00000, “illegal use of LONG datatype” Cause: Action: |
| ORA-00998 ORA-00998, 00000, “must name this expression with a column alias” Cause: Action: |
| ORA-00999 ORA-00999, 00000, “invalid view name” Cause: Action: |
| ORA-01000 ORA-01000, 00000, “maximum open cursors exceeded” Cause: Action: |
| ORA-01001 ORA-01001, 00000, “invalid cursor” Cause: Action: |
| ORA-01002 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 ORA-01003, 00000, “no statement parsed” Cause: Action: |
| ORA-01004 ORA-01004, 00000, “default username feature not supported; logon denied” Cause: Action: |
| ORA-01005 ORA-01005, 00000, “null password given; logon denied” Cause: Action: |
| ORA-01006 ORA-01006, 00000, “bind variable does not exist” Cause: Action: |
| ORA-01007 ORA-01007, 00000, “variable not in select list” Cause: Action: |
| ORA-01008 ORA-01008, 00000, “not all variables bound” Cause: Action: |
| ORA-01009 ORA-01009, 00000, “missing mandatory parameter” Cause: Action: |
| ORA-01010 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. 4) You are connected to a version 9.0.2(or higher) Oracle Server and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous transaction. 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). 4) Do not attempt distributed autonomous transaction on version 9.0.1(or lower) Oracle Server. |
| ORA-01011 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 ORA-01012, 00000, “not logged on” Cause: Action: |
| ORA-01013 ORA-01013, 00000, “user requested cancel of current operation” Cause: Action: |
| ORA-01014 ORA-01014, 00000, “ORACLE shutdown in progress” Cause: Action: |
| ORA-01015 ORA-01015, 00000, “logon called recursively” Cause: Action: |
| ORA-01016 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 ORA-01017, 00000, “invalid username/password; logon denied” Cause: Action: |
| ORA-01018 ORA-01018, 00000, “column does not have a LONG datatype” Cause: Action: |
| ORA-01019 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 ORA-01020, 00000, “unknown context state” Cause: Action: |
| ORA-01021 ORA-01021, 00000, “invalid context size specified” Cause: Action: |
| ORA-01022 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 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 ORA-01024, 00000, “invalid datatype in OCI call” Cause: Action: |
| ORA-01025 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 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 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 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 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 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 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 ORA-01032, 00000, “no such userid” Cause: This is an internal error message related to Export/Import. Action: Contact customer support. |
| ORA-01033 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-01046, 00000, “cannot acquire space to extend context area” Cause: Action: |
| ORA-01047 ORA-01047, 00000, “The above error occurred in schema=%s, package=%s, procedure=%s” Cause: Action: Informational message |
| ORA-01048 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 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 ORA-01050, 00000, “cannot acquire space to open context area” Cause: Action: |
| ORA-01051 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 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 ORA-01053, 00000, “user storage address cannot be read” Cause: Action: |
| ORA-01054 ORA-01054, 00000, “user storage address cannot be written” Cause: Action: |
| ORA-01055 ORA-01055, 00000, “Object datatypes not supported for bind or define in this mode” Cause: Bind or Define used for objects with an invalid mode Action: Change the mode. |
| ORA-01057 ORA-01057, 00000, “invalid or ambiguous block.field reference in user exit” Cause: Action: |
| ORA-01058 ORA-01058, 00000, “internal New Upi interface error” Cause: Attempt to delete non existant hstdef extension. Action: Report as a bug. |
| ORA-01059 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 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 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 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 |
| ORA-01070 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 ORA-01071, 00000, “cannot perform operation without starting up ORACLE” Cause: Obvious Action: |
| ORA-01072 ORA-01072, 00000, “cannot stop ORACLE; ORACLE not running” Cause: Obvious Action: |
| ORA-01073 ORA-01073, 00000, “fatal connection error: unrecognized call type” Cause: An illegal internal operation was attempted. Action: Contact your customer support representative. |
| ORA-01074 ORA-01074, 00000, “cannot shut down ORACLE; inside a login session – log off first” Cause: Obvious Action: |
| ORA-01075 ORA-01075, 00000, “you are currently logged on” Cause: Attempt to login while logged in. Action: |
| ORA-01076 ORA-01076, 00000, “multiple logons per process not yet supported” Cause: Obvious Action: |
| ORA-01077 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 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 ORA-01079, 00000, “ORACLE database was not properly created, operation aborted” Cause: There was an error when the database or control file was created. Action: Check what error was signaled when the database was first // created or when the control file was recreated. Take appropriate actions to recreate the database or a new control file. |
| ORA-01080 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 ORA-01081, 00000, “cannot start already-running ORACLE – shut it down first” Cause: Obvious Action: |
| ORA-01082 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 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 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 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 ORA-01086, 00000, “savepoint ‘%s’ never established” Cause: Trying to roll back to a save point that was never established. Action: |
| ORA-01087 ORA-01087, 00000, “cannot start up ORACLE – currently logged on” Cause: Action: Logoff and then issue the STARTUP command. |
| ORA-01088 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 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 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 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 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 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 ORA-01094, 00000, “ALTER DATABASE CLOSE in progress. Connections not permitted” Cause: Action: |
| ORA-01095 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 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 ORA-01097, 00000, “cannot shutdown while in a transaction – commit or rollback first” Cause: Obvious Action: |
| ORA-01098 ORA-01098, 00000, “program Interface error during Long Insert” Cause: Action: |
| ORA-01099 ORA-01099, 00000, “cannot mount database in SHARED mode if started in single process mode” Cause: Obvious Action: |
| ORA-01100 ORA-01100, 00000, “database already mounted” Cause: A database is already mounted in this instance. Action: |
| ORA-01101 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 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 ORA-01103, 00000, “database name ‘%s’ in control file is not ‘%s’” Cause: The database name in the control file does not match your // database name. Action: Either find the correct control file or change your database name. |
| ORA-01104 ORA-01104, 00000, “number of control files (%s) does not equal %s” Cause: The number of control files used by this instance disagrees with // the number of control files in an existing instance. Action: Check to make sure that all control files are listed. |
| ORA-01105 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 ORA-01106, 00000, “database must be closed before dismounting” Cause: Obvious Action: |
| ORA-01107 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 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 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 ORA-01110, 00000, “data file %s: ‘%s’” Cause: Reporting file name for details of another error Action: See associated error message |
| ORA-01111 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 control file recovery was done with a control file that was saved before the file was created. Action: Rename the MISSING file to the name of the real file. |
| ORA-01112 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 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 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 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 ORA-01116, 00000, “error in opening database file %s” Cause: Usually the file is not accessible. Action: Restore the database file. |
| ORA-01117 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 ORA-01118, 00000, “cannot add any more database files: limit of %s exceeded” Cause: There is no more room in the control file for adding database files. Action: Resize the control file or drop other tablespaces. |
| ORA-01119 ORA-01119, 00000, “error in creating database file ‘%s’” Cause: Usually due to not having enough space on the device. Action: |
| ORA-01120 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 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 ORA-01122, 00000, “database file %s failed verification check” Cause: The information in this file is inconsistent with information // from the control file. See accompanying message for reason. Action: Make certain that the db files and control files are the correct // files for this database. |
| ORA-01123 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 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 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 ORA-01126, 00000, “database must be mounted in this instance and not open in any instance” Cause: Obvious Action: |
| ORA-01127 ORA-01127, 00000, “database name ‘%s’ exceeds size limit of %s characters” Cause: Obvious Action: |
| ORA-01128 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 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 ORA-01130, 00000, “database file version %s incompatible with ORACLE version %s” Cause: Action: |
| ORA-01131 ORA-01131, 00000, “DB_FILES system parameter value %s exceeds limit of %s” Cause: Action: |
| ORA-01132 ORA-01132, 00000, “length of database file name ‘%s’ exceeds limit of %s characters” Cause: Action: |
| ORA-01133 ORA-01133, 00000, “length of log file name ‘%s’ exceeds limit of %s characters” Cause: Action: |
| ORA-01134 ORA-01134, 00000, “database mounted exclusive by another instance” Cause: Action: |
| ORA-01135 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 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 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 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 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 ORA-01140, 00000, “cannot end online backup – all files are offline or readonly” Cause: All the files were found to be offline or readonly when attempting to end an online backup. Action: None. Online backup does not need to be ended for this tablespace. |
| ORA-01141 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 control file // 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 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 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 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 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 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 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. |
| ORA-01148 ORA-01148, 00000, “cannot refresh file size for datafile %s” Cause: An operating system or device error occurred when retrieving the file’s size. The device on which the file resides may have been offline. Action: Restore access to the device. |
| ORA-01149 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 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 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 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 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 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. If this is a shutdown of a standby database that is operating in NO DATA LOSS mode, you must shutdown the primary database first. |
| ORA-01155 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 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 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 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 control files after all. |
| ORA-01159 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 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 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 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 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 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 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 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 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 control file appears more than once in the control_files 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 control file, 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 control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list. |
| ORA-01168 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 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 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 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 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 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 control file or a datafile from the system tablespace was omitted from the create control file command previously issued. Action: For the former problem you need to recover the database from a more recent control file. For the latter problem, simply recreate the control file checking to be sure that you include all the datafiles in the system tablespace. |
| ORA-01174 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 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 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 control file. Action: Recreate the control file with a larger MAXDATAFILES. |
| ORA-01177 ORA-01177, 00000, “data file does not match dictionary – probably old incarnation” Cause: When comparing the control file 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 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 CONTROLFILE command. The information needed to recreate the file was lost with the control file 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 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 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 ORA-01181, 00000, “file %s created before last known RESETLOGS, cannot recreate” Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS. Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. |
| ORA-01182 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 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 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 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 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 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 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 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 ORA-01190, 00000, “control file 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 control file. Either the data file or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS. Action: Restore file from a more recent backup. |
| ORA-01191 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 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 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 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 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 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 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 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 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 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 control file. 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 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 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 control file. 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 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 control file. 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 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 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 control file. 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 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 control file. 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 ORA-01207, 00000, “file is more recent than control file – old control file” Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file 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 control file change sequence number until it is great enough. Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. |
| ORA-01208 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-01222, 00000, “MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s” Cause: Attemping to create a database or control file 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 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 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 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 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 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 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 control file for this database. Action: Resubmit command with the SET DATABASE and RESETLOGS options. |
| ORA-01229 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 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 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 ORA-01232, 00000, “cannot start online backup – file %s is being made read-only” Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode. Action: Wait for the transition to complete and then retry the command, if this is an ALTER DATABASE BEGIN BACKUP command, or take the backup without any begin or end commands, if this is an ALTER TABLESPACE BEGIN BACKUP command. |
| ORA-01233 ORA-01233, 00000, “file %s is read only – cannot recover using backup control file” Cause: An attempt to do media recovery using a backup control file 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 control file 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 control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one. |
| ORA-01234 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 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 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 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 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 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 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 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 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 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 ORA-01244, 00000, “unnamed datafile(s) added to control file by media recovery” Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file 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 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 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 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 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 control file 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 control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE. |
| ORA-01249 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 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 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 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 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 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 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 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 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 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 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 ORA-01260, 00000, “warning: END BACKUP succeeded but some files found not to be in backup mode” Cause: END BACKUP completed successfully for all files that were in online backup mode. However one or more modifiable files were found not to be in online backup mode. Backup of those files (if it was done) can be invalid and, if restored, can result in an inconsistent database. Action: Check the alert log for a list of the files that were found not to be in backup mode. If there is a possibility that those files have been modified during online backup, then replace their backups with new ones. |
| ORA-01261 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 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 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 ORA-01264, 00000, “Unable to create %s file name” Cause: Unable to create an Oracle managed file name. 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 ORA-01265, 00000, “Unable to delete %s %s” Cause: An error prevented the file from being deleted. Action: See the subsequent error messsages that describe the operating system error that prevented the file from being deleted. If possible, fix the problem and manually delete the file. |
| ORA-01266 ORA-01266, 00000, “Unable to create unique file name” Cause: Unable to create a unique file name for an Oracle managed 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 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 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 ORA-01269, 00000, “Destination parameter string is too long” Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long. Action: Replace the destination value for the specified parameter with a shorter character string. |
| ORA-01270 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 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 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 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. Cause: Automated standby file management was disabled, so an added file |
| ORA-01274 ORA-01274, 0000, “cannot add datafile ‘%s’ – file could not be created” Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is ‘UNNAMEDnnnnn’. Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery. |
| ORA-01275 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 ORA-01276, 00000, “Cannot add file %s. File has an Oracle Managed Files file name.” Cause: An attempt was made to add to the database a datafile, log file, control file, snapshot control file, backup control file, datafile copy, control file copy or backuppiece with an Oracle Managed Files file name. Action: Retry the operation with a new file name. |
| ORA-01277 ORA-01277, 00000, “file ‘%s’ already exists” Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS ‘filename’ command specified a file name which is already in use. Action: Either specify a different file name, or add the REUSE parameter to the command to overwrite the existing file. |
| ORA-01278 ORA-01278, 00000, “error creating file ‘%s’” Cause: An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS ‘filename’. Action: Check the error stack for more detailed information. |
| ORA-01279 ORA-01279, 00000, “db_files too large” Cause: db_files has been set too high to be supported by the system. Action: Decrease the number of db_files. |
| ORA-01280 ORA-01280, 00000, “Fatal LogMiner Error.” Cause: An internal error has occurred inside LogMiner. Action: |
| ORA-01281 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 ORA-01282, 00000, “date range specified is invalid” Cause: startTime may be greater than endTime. startTime or endTime may be greater than year 2110. startTime may be less than year 1988. Action: Specify a valid date range. |
| ORA-01283 ORA-01283, 00000, “Options specified is invalid” Cause: The specified options parameter is invalid for the procedure. Action: Specify valid Options parameter. |
| ORA-01284 ORA-01284, 00000, “file %s cannot be opened” Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds 256 characters. Action: Ensure that the file and the directory exist and are accessible. |
| ORA-01285 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 ORA-01286, 00000, “start interval required” Cause: Options were supplied which require a starting time or starting SCN Action: Specify a starting interval (time or SCN). |
| ORA-01287 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-01288 ORA-01288, 00000, “cannot apply this DDL to the Logminer Dictionary” Cause: A command that is not supported by Logminer was present in a logfile. Commands that change the character set of the database are not supported by Logminer. “ALTER DATABASE SET TIME_ZONE” is not supported by Logminer. Action: Do not execute unsupported commands when using Streams, Logical Standby, or Logminer. Turn off DDL tracking in order for Logminer to skip unsupported commands. |
| ORA-01289 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 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 ORA-01291, 00000, “missing logfile” Cause: Not all logfiles corresponding to the time 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 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 ORA-01293, 00000, “mounted database required for specified LogMiner options” Cause: Options were specified which required the database to be mounted Action: Specify different options or mount the database. |
| ORA-01294 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 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 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 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 ORA-01298, 00000, “conflicting dictionary option” Cause: More than one dictionary source was specified or DDL_DICT_TRACKING was specified with DICT_FROM_ONLINE_CATALOG. Action: |
| ORA-01299 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 ORA-01300, 00000, “writable database required for specified LogMiner options” Cause: Options were specified which required the database to be writable. Action: Specify different options or open the database for write access. |
| ORA-01301 ORA-01301, 00000, “error writing to file during flat file build” Cause: Error writing to file during flat file build Action: |
| ORA-01302 ORA-01302, 00000, “dictionary build options missing or incorrect” Cause: Missing dictionary build options or incorrectly specified options Action: Specify either a build to redo log or to flat file. If build to // flat file, specify filename and directory. |
| ORA-01303 ORA-01303, 00000, “subordinate process error: %u. Check alert and trace logs” Cause: A process subordinate to this Logminer process has exited with this error status. Action: Search for this error in the alert log and trace files for // additional information. |
| ORA-01304 ORA-01304, 00000, “subordinate process error. Check alert and trace logs” Cause: A process subordinate to this Logminer process has exited with an error condition. Action: Look in the alert log and trace files for additional information. |
| ORA-01306 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 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 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 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 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 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 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 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 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 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 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 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-01319 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 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 ORA-01321, 00000, “No Logminer Dictionary for requested start SCN” Cause: The requested session start SCN is less than the SCN of any available Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the requested start SCN. Action: Re-issue the start_logminer request with a start SCN for which a Logminer Dictionary is available. |
| ORA-01322 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 ORA-01323, 00000, “Invalid state” Cause: A Logminer routine was called from the wrong state. Action: |
| ORA-01324 ORA-01324, 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-01325 ORA-01325, 00000, “archive log mode must be enabled to build into the logstream” Cause: Database does not have archivelog mode enabled. Action: Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open |
| ORA-01326 ORA-01326, 00000, “compatability of 9.0 or greater required to build into the logstream” Cause: Compatibility mode set to some value less than 9.0 Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0 |
| ORA-01327 ORA-01327, 00000, “failed to exclusively lock system dictionary as required by build” Cause: Other users are performing DDL operations. Action: |
| ORA-01328 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 ORA-01329, 00000, “unable to truncate required build table” Cause: The table may be missing, or locked by another user. Action: |
| ORA-01330 ORA-01330, 00000, “problem loading a required build table” Cause: Action: |
| ORA-01331 ORA-01331, 00000, “general error while running build” Cause: Action: |
| ORA-01332 ORA-01332, 00000, “internal Logminer Dictionary error” Cause: Unexpected error condition Action: Check trace and/or alert logs |
| ORA-01333 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 ORA-01334, 00000, “invalid or missing logminer dictionary processes context” Cause: Unexpected internal error condition Action: |
| ORA-01335 ORA-01335, 00000, “feature not yet implemented” Cause: Action: |
| ORA-01336 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 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-01338 ORA-01338, 00000, “Other process is attached to LogMiner session” Cause: Can not do this when other process is attached to LogMiner session. Action: |
| ORA-01339 ORA-01339, 0000, “LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary” Cause: Unexpected result while accessing system catalog metadata. Action: Check the alert log. |
| ORA-01340 ORA-01340, 00000, “NLS error” Cause: Could not load NLS package. Action: |
| ORA-01341 ORA-01341, 00000, “LogMiner out-of-memory” Cause: The LogMiner session requires more system resources than is currently available. Action: Allocate more SGA for LogMiner. |
| ORA-01342 ORA-01342, 00000, “LogMiner can not resume session due to inability of staging checkpointed data” Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery. Action: Specify a bigger max_sga for the given LogMiner session and try again. |
| ORA-01343 ORA-01343, 00000, “LogMiner encountered corruption in the logstream” Cause: Log file is missing a range of scn values. Action: Verify the contiguity of the scn range reprented by the log files added to LogMiner. |
| ORA-01344 ORA-01344, 00000, “LogMiner coordinator already attached” Cause: A coordinator process is already attached to the specified logminer context. Action: Detach from the active coordinator session and retry the attach. |
| ORA-01345 ORA-01345, 00000, “Must be a LogMiner coordinator process” Cause: A LogMiner client attempted to perform a privileged operation. Action: Issue the operation from the coordinator process. |
| ORA-01346 ORA-01346, 00000, “LogMiner processed redo beyond specified reset log scn” Cause: LogMiner has detected a new branch with resetlogs scn information prior to redo already mined. Action: Contact your customer support representative. |
| ORA-01347 ORA-01347, 00000, “Supplemental log data no longer found” Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data. Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session. |
| ORA-01348 ORA-01348, 00000, “LogMiner testing event” Cause: Action: |
| ORA-01349 ORA-01349, 00000, “LogMiner tracing event” Cause: Action: |
| ORA-01350 ORA-01350, 00000, “must specify a tablespace name” Cause: Invocation failed to specify a valid tablespace Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of a valid tablespace. |
| ORA-01351 ORA-01351, 00000, “tablespace given for Logminer dictionary does not exist” Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist. Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. |
| ORA-01352 ORA-01352, 00000, “tablespace given for Logminer spill does not exist” Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist. Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. |
| ORA-01353 ORA-01353, 00000, “existing Logminer session” Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active. Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE. |
| ORA-01354 ORA-01354, 00000, “Supplemental log data must be added to run this command” Cause: An attempt was made to perform an operation that required that supplemental log data be enabled. Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error. |
| ORA-01355 ORA-01355, 00000, “logminer tablespace change in progress” Cause: The tables used by logminer are in the process of being moved to another tablespace. Action: Wait until the move is complete and try again. |
| ORA-01356 ORA-01356, 00000, “active logminer sessions found” Cause: Logminer sessions are currently active. Action: End all logminer sessions and retry. |
| ORA-01358 ORA-01358, 00000, “LogMiner version is less than mined dictionary version” Cause: An attempt was made to mine a LogMiner dictionary from redo logs. The version of the Oracle database that created the logs was higher than the Oracle database version that attempted to mine the logs. Action: Mine the logs using a newer version of the Oracle database having a version number that is equal to or greater than the dictionary version. |
| ORA-01360 ORA-01360, 00000, “invalid token” Cause: Action: |
| ORA-01361 ORA-01361, 00000, “global name mismatch” *Cause : The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process. Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file. |
| ORA-01370 ORA-01370, 00000, “Specified restart SCN is too old” Cause: specified restart scn is too old, logmnr could not find a proper checkpoint. Action: Specify a bigger restart SCN to try again |
| ORA-01371 ORA-01371, 00000, “Complete LogMiner dictionary not found” Cause: One or more log files containing the LogMiner dictionary was not found. Action: Add into LogMiner all log files containing the dictionary. |
| ORA-01372 ORA-01372, 00000, “Insufficient processes for specified LogMiner operation” Cause: The number of processes requested by the caller can not be allocated Action: Increase number of parallel servers allocated to the instance |
| ORA-01373 ORA-01373, 00000, “insufficient memory for staging persistent LogMiner session” Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session. Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance. |
| ORA-01374 ORA-01374, 00000, “_log_parallelism_max greater than 1 not supported in this release” Cause: LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1. Action: |
| ORA-01375 ORA-01375, 00000, “Corrupt logfile %s recovered” Cause: A corrupt logfile has been recovered by RFS Action: None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby. // |
| ORA-01376 ORA-01376, 00000, “LogMiner testing event” Cause: Action: |
| ORA-01399 ORA-01399, 00000, “LogMiner public event” Cause: Action: |
| ORA-01400 ORA-01400, 00000, “cannot insert NULL into (%s)” Cause: Action: |
| ORA-01401 ORA-01401, 00000, “inserted value too large for column” Cause: Action: |
| ORA-01402 ORA-01402, 00000, “view WITH CHECK OPTION where-clause violation” Cause: Action: |
| ORA-01403 ORA-01403, 00000, “no data found” Cause: Action: |
| ORA-01404 ORA-01404, 00000, “ALTER COLUMN will make an index too large” Cause: Action: |
| ORA-01405 ORA-01405, 00000, “fetched column value is NULL” Cause: Action: |
| ORA-01406 ORA-01406, 00000, “fetched column value was truncated” Cause: Action: |
| ORA-01407 ORA-01407, 00000, “cannot update (%s) to NULL” Cause: Action: |
| ORA-01408 ORA-01408, 00000, “such column list already indexed” Cause: Action: |
| ORA-01409 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 ORA-01410, 00000, “invalid ROWID” Cause: Action: |
| ORA-01411 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 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 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 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 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 ORA-01416, 00000, “two tables cannot be outer-joined to each other” Cause: Action: |
| ORA-01417 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 ORA-01418, 00000, “specified index does not exist” Cause: Action: |
| ORA-01419 ORA-01419, 00000, “datdts: illegal format code” Cause: Action: |
| ORA-01420 ORA-01420, 00000, “datstd: illegal format code” Cause: Action: |
| ORA-01421 ORA-01421, 00000, “datrnd/dattrn: illegal precision specifier” Cause: Action: |
| ORA-01422 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 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 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 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 ORA-01426, 00000, “numeric overflow” Cause: Evaluation of an value expression causes an overflow/underflow. Action: Reduce the operands. |
| ORA-01427 ORA-01427, 00000, “single-row subquery returns more than one row” Cause: Action: |
| ORA-01428 ORA-01428, 00000, “argument ‘%s’ is out of range” Cause: Action: |
| ORA-01429 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 ORA-01430, 00000, “column being added already exists in table” Cause: Action: |
| ORA-01431 ORA-01431, 00000, “internal inconsistency in GRANT command” Cause: Action: |
| ORA-01432 ORA-01432, 00000, “public synonym to be dropped does not exist” Cause: Action: |
| ORA-01433 ORA-01433, 00000, “synonym to be created is already defined” Cause: Action: |
| ORA-01434 ORA-01434, 00000, “private synonym to be dropped does not exist” Cause: Action: |
| ORA-01435 ORA-01435, 00000, “user does not exist” Cause: Action: |
| ORA-01436 ORA-01436, 00000, “CONNECT BY loop in user data” Cause: Action: |
| ORA-01437 ORA-01437, 00000, “cannot have join with CONNECT BY” Cause: Action: |
| ORA-01438 ORA-01438, 00000, “value larger than specified precision allowed for this column” Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column. Action: Enter a value that complies with the numeric column’s precision, or use the MODIFY option with the ALTER TABLE command to expand the precision. |
| ORA-01439 ORA-01439, 00000, “column to be modified must be empty to change datatype” Cause: Action: |
| ORA-01440 ORA-01440, 00000, “column to be modified must be empty to decrease precision or scale” Cause: Action: |
| ORA-01441 ORA-01441, 00000, “cannot decrease column length because some value is too big” Cause: Action: |
| ORA-01442 ORA-01442, 00000, “column to be modified to NOT NULL is already NOT NULL” Cause: Action: |
| ORA-01443 ORA-01443, 00000, “internal inconsistency; illegal datatype in resultant view column” Cause: Action: |
| ORA-01444 ORA-01444, 00000, “internal inconsistency; internal datatype maps to invalid external type” Cause: Action: |
| ORA-01445 ORA-01445, 00000, “cannot select ROWID from, or sample, a join view without a key-preserved table” Cause: Action: |
| ORA-01446 ORA-01446, 00000, “cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.” Cause: Action: |
| ORA-01447 ORA-01447, 00000, “ALTER TABLE does not operate on clustered columns” Cause: Action: |
| ORA-01448 ORA-01448, 00000, “index must be dropped before changing to desired type” Cause: Action: |
| ORA-01449 ORA-01449, 00000, “column contains NULL values; cannot alter to NOT NULL” Cause: Action: |
| ORA-01450 ORA-01450, 00000, “maximum key length (%s) exceeded” Cause: Action: |
| ORA-01451 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 ORA-01452, 00000, “cannot CREATE UNIQUE INDEX; duplicate keys found” Cause: Action: |
| ORA-01453 ORA-01453, 00000, “SET TRANSACTION must be first statement of transaction” Cause: self-evident Action: commit (or rollback) transaction, and re-execute |
| ORA-01454 ORA-01454, 00000, “cannot convert column into numeric datatype” Cause: Action: |
| ORA-01455 ORA-01455, 00000, “converting column overflows integer datatype” Cause: Action: |
| ORA-01456 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 ORA-01457, 00000, “converting column overflows decimal datatype” Cause: Action: |
| ORA-01458 ORA-01458, 00000, “invalid length inside variable character string” Cause: Action: |
| ORA-01459 ORA-01459, 00000, “invalid length for variable character string” Cause: Action: |
| ORA-01460 ORA-01460, 00000, “unimplemented or unreasonable conversion requested” Cause: Action: |
| ORA-01461 ORA-01461, 00000, “can bind a LONG value only for insert into a LONG column” Cause: Action: |
| ORA-01462 ORA-01462, 00000, “cannot insert string literals longer than 4000 characters” Cause: Action: |
| ORA-01463 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 ORA-01464, 00000, “circular grant (granting to grant ancestor) of table or view” Cause: Action: |
| ORA-01465 ORA-01465, 00000, “invalid hex number” Cause: Action: |
| ORA-01466 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 ORA-01467, 00000, “sort key too long” Cause: Action: |
| ORA-01468 ORA-01468, 00000, “a predicate may reference only one outer-joined table” Cause: Action: |
| ORA-01469 ORA-01469, 00000, “PRIOR can only be followed by a column name” Cause: Attempting to specify “PRIOR <something>” where <something> is not // a column name. Action: Only a column name can follow PRIOR. Replace with a column name. |
| ORA-01470 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 ORA-01471, 00000, “cannot create a synonym with same name as object” Cause: Action: |
| ORA-01472 ORA-01472, 00000, “cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.” Cause: Action: |
| ORA-01473 ORA-01473, 00000, “cannot have subqueries in CONNECT BY clause” Cause: Action: |
| ORA-01474 ORA-01474, 00000, “cannot have START WITH or PRIOR without CONNECT BY” Cause: Action: |
| ORA-01475 ORA-01475, 00000, “must reparse cursor to change bind variable datatype” Cause: Action: |
| ORA-01476 ORA-01476, 00000, “divisor is equal to zero” Cause: Action: |
| ORA-01477 ORA-01477, 00000, “user data area descriptor is too large” Cause: Action: |
| ORA-01478 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-01490 ORA-01490, 00000, “invalid ANALYZE command” Cause: Incorrect syntax specified Action: Retry the command |
| ORA-01491 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 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 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 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 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 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 ORA-01497, 000000, “illegal option for ANALYZE CLUSTER” Cause: The FOR COLUMNS <column-list> clause may not be used with ANALYZE CLUSTER. Action: Retry with a legal syntax. |
| ORA-01498 ORA-01498, 00000, “block check failure – see trace file” Cause: Action: |
| ORA-01499 ORA-01499, 00000, “table/index cross reference failure – see trace file” Cause: Action: |
| ORA-01500 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 ORA-01501, 00000, “CREATE DATABASE failed” Cause: An error occurred during create database Action: See accompanying errors. |
| ORA-01502 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 ORA-01503, 00000, “CREATE CONTROLFILE failed” Cause: An error occurred during CREATE CONTROLFILE Action: See accompanying errors. |
| ORA-01504 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 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 ORA-01506, 00000, “missing or illegal database name” Cause: No db_name INIT.ORA aprameter was specified. Action: The database name must be given in the db_name // INIT.ORA parameter. |
| ORA-01507 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. If you are doing a FLASHBACK DATABASE, you must first mount the desired database. |
| ORA-01508 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 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 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 ORA-01511, 00000, “error in renaming log/data files” Cause: An error occurred during the ALTER DATABASE RENAME FILE command. Action: Check the error stack for detailed error information. |
| ORA-01512 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 control file // 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 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 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 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 control file. Action: Specify the name of an existing log file. |
| ORA-01516 ORA-01516, 00000, “nonexistent log file, datafile, or tempfile \”%s\”" Cause: An attempt was made to use ALTER DATABASE to rename a log file, datafile, or tempfile; or to change attributes of a datafile or tempfile (e.g., resize, autoextend, online/offline, etc.); or to re-create a datafile. The attempt failed because the specified file is not known to the database’s control file or is not of a type supported by the request. Action: Specify the name or number of an existing file of the correct type, as appropriate. Check the relevant V$ table for a list of possible files. |
| ORA-01517 ORA-01517, 00000, “log member: ‘%s’” Cause: Used to print member names Action: See top level error for information |
| ORA-01518 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 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 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 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 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 control file. Action: Specify the correct file name. |
| ORA-01523 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 control file. Action: Rename the file to a name not already being used as part of // the database. |
| ORA-01524 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 control file. Action: Create the file as a name not already being used as part of // the database. |
| ORA-01525 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 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 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 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 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 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 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 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 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 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 ORA-01535, 00000, “rollback segment ‘%s’ already exists or given name has prefix _SYSSMU” Cause: Specified rollback segment already exists or given name starts with _SYSSMU. Action: Use a different name. Note that _SYSSMU is an illegal prefix to an RBU segment. |
| ORA-01536 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 ORA-01537, 00000, “cannot add 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 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 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 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 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 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 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 ORA-01544, 00000, “cannot drop system rollback segment” Cause: Tried to drop system rollback segment Action: None |
| ORA-01545 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. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file. 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). 5) Remove the name from the _corrupted_rollback_segments parameter. |
| ORA-01546 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 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 control file, or different stop criteria. |
| ORA-01548 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 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 ORA-01550, 00000, “cannot drop system tablespace” Cause: Tried to drop system tablespace Action: None |
| ORA-01551 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 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. If the non-system tablespace has AUTO segment space management, then create an undo tablespace. |
| ORA-01553 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 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 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 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 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 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 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-01560 ORA-01560, 00000, “LIKE pattern contains partial or illegal character” Cause: like pattern is not formed correctly Action: make sure like pattern is specified correctly |
| ORA-01561 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 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 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 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 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 ORA-01566, 00000, “file specified more than once in ALTER DATABASE” Cause: The list of files supplied to the command contained at least one // duplicate. Action: Remove the duplicate file specification and retry. |
| ORA-01567 ORA-01567, 00000, “dropping log %s would leave less than 2 log files for instance %s (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 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 <tablespace>] TO PUBLIC. |
| ORA-01569 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 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 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 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 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 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 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 ORA-01576, 00000, “The instance %s is not enabled” Cause: The thread associated with instance is not enabled. Action: Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command. |
| ORA-01577 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 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 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 ORA-01580, 00000, “error creating control backup file %s” Cause: An operating system error occurred while attempting to create a // control file backup. Action: Check the error stack for more detailed information |
| ORA-01581 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 ORA-01582, 00000, “unable to open control file for backup” Cause: An operating system error occurred while attempting to open a // control file for backup. Action: Check the error stack for more detailed information |
| ORA-01583 ORA-01583, 00000, “unable to get block size of control file to be backed up” Cause: An operating system error occurred while attempting to // get the block size of a control file for backup. Action: Check the error stack for more detailed information |
| ORA-01584 ORA-01584, 00000, “unable to get file size of control file to be backed up” Cause: An operating system error occurred while attempting to // get the file size of a control file for backup. Action: Check the error stack for more detailed information |
| ORA-01585 ORA-01585, 00000, “error identifying backup file %s” Cause: An operating system error occurred when attempting to identify // the file to be used for control file backup. Action: Check the error stack for more detailed information |
| ORA-01586 ORA-01586, 00000, “database must be mounted EXCLUSIVE and not open for this operation” Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE. Action: Mount the database in EXCLUSIVE mode. |
| ORA-01587 ORA-01587, 00000, “error during control file backup file copy” Cause: // Action: |
| ORA-01588 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 control file backup, or a FLASHBACK DATABASE was done. Action: Use the RESETLOGS option when opening the database. |
| ORA-01589 ORA-01589, 00000, “must use RESETLOGS or NORESETLOGS option for database open” Cause: Either incomplete or backup control file 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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-01607 ORA-01607, 00000, “cannot add logfile to the specified instance” Cause: The limit on the number of instances supported by the control file has been reached. Action: Use an instance name supported by the control file, or resize the thread record and/or checkpoint progress record secions of the control file. |
| ORA-01608 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 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 ORA-01610, 00000, “recovery using the BACKUP CONTROLFILE option must be done” Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was recreated with the RESETLOGS option, or the control file being used is a backup control file. // 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 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 control file. Action: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file. |
| ORA-01612 ORA-01612, 00000, “instance %s (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 ORA-01613, 00000, “instance %s (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 ORA-01614, 00000, “instance %s (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 ORA-01615, 00000, “instance %s (thread %s) is mounted – cannot disable” Cause: Some instance, possibly this one, has allocated the thread for its use. The thread can not be disabled while in use. Action: Shut the instance down cleany using the thread. |
| ORA-01616 ORA-01616, 00000, “instance %s (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 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 control file. Action: Shut down the instance, change the INIT.ORA parameter and startup, or resize the thread record and/or checkpoint progress record sections of the control file. |
| ORA-01618 ORA-01618, 00000, “redo 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 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 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 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 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 ORA-01623, 00000, “log %s is current log for instance %s (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 ORA-01624, 00000, “log %s needed for crash recovery of instance %s (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 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 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 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 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 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 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 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 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 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 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 ORA-01635, 00000, “rollback segment #%s specified not available” Cause: (same as 1545) Action: (same as 1545) |
| ORA-01636 ORA-01636, 00000, “rollback segment ‘%s’ is already online” Cause: The instance is trying to online an already online RS Action: |
| ORA-01637 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 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-01639 ORA-01639, 00000, ” instance %s has no thread assigned to it” Cause: There is no mapping from instance to thread for this instance in the control file. Action:Make sure that this instance has a thread assigned to it by adding logfiles to this instance or by starting the instance with an existing thread which will automatically create a mapping. |
| ORA-01640 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 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 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 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 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 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 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 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 ORA-01648, 00000, “log %s is the current log of disabled instance %s (thread %s)” Cause: 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 ORA-01649, 00000, “operation not allowed with a backup control file” Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup. Action:Wait until after the database has been opened and try again. |
| ORA-01650 ORA-01650, 00000, “unable to extend rollback segment %s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01651 ORA-01651, 00000, “unable to extend save undo segment by %s for tablespace %s” Cause: Failed to allocate an extent of the required number of blocks 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 ORA-01652, 00000, “unable to extend temp segment by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01653 ORA-01653, 00000, “unable to extend table %s.%s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01654 ORA-01654, 00000, “unable to extend index %s.%s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01655 ORA-01655, 00000, “unable to extend cluster %s.%s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01656 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 ORA-01657, 00000, “invalid SHRINK option value” Cause: The specified value must be an integer. Action: Choose an appropriate integer value. |
| ORA-01658 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 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 ORA-01660, 00000, “tablespace ‘%s’ is already permanent” Cause: Attempting to make tablespace permanent that is already permanent. Action: Leave tablespace permanent. |
| ORA-01661 ORA-01661, 00000, “tablespace ‘%s’ is already temporary” Cause: Attempting to make tablespace temporary that is already temporary. Action: Leave tablespace permanent. |
| ORA-01662 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 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 ORA-01664, 00000, “Transaction which has expanded the Sort Segment has aborted” Cause: Internal Error. Action: Contact Oracle Support. |
| ORA-01665 ORA-01665, 00000, “control file is not a standby control file” Cause: Attempting to mount, recover or activate a standby database without a standby control file. Action: Create a standby control file before attempting to use the database as a standby database. |
| ORA-01666 ORA-01666, 00000, “control file 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 control file. |
| ORA-01667 ORA-01667, 00000, “cannot add any more tablespaces: limit of %s exceeded” Cause: There is no more room in the control file for adding tablespaces. Action: Resize the control file or drop other tablespaces. |
| ORA-01668 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 ORA-01669, 00000, “standby database control file not consistent” Cause: Attempting to activate a standby database with a control file that has not been recovered to the same point as the data files. Most likely the control file 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 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 ORA-01671, 00000, “control file is a backup, cannot make a standby control file” Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database. Action: Complete any needed recovery and open the database with the resetlogs option. |
| ORA-01672 ORA-01672, 00000, “control file may be missing files or have extra ones” Cause: Attempting to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match. Action: Open the database, then retry the operation. |
| ORA-01673 ORA-01673, 00000, “data file %s has not been identified” Cause: This data file was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we can not create a standby control file. 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 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 control file using CREATE CONTROLFILE, and give the correct file. |
| ORA-01675 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 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 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 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 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 ORA-01680, 00000, “unable to extend LOB segment by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for a LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01681 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 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 ORA-01683, 00000, “unable to extend index %s.%s partition %s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01684 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 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 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 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 ORA-01688, 00000, “unable to extend table %s.%s partition %s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01689 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 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 ORA-01691, 00000, “unable to extend lob segment %s.%s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01692 ORA-01692, 00000, “unable to extend lob segment %s.%s partition %s by %s in tablespace %s” Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| ORA-01693 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 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 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 ORA-01696, 00000, “control file is not a clone control file” 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 control file for a clone. Action: Mount without the clone option or use a backup control file and shutdown the other instances before mounting as a clone. |
| ORA-01697 ORA-01697, 00000, “control file 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 control file. |
| ORA-01698 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 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 // |
| ORA-01700 ORA-01700, 00000, “duplicate username in list” Cause: Action: |
| ORA-01701 ORA-01701, 00000, “a cluster is not appropriate here” Cause: Action: |
| ORA-01702 ORA-01702, 00000, “a view is not appropriate here” Cause: Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view. Action: An Editioning View may only be created over a base table. |
| ORA-01703 ORA-01703, 00000, “missing SYNONYM keyword” Cause: Action: |
| ORA-01704 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 ORA-01705, 00000, “an outer join cannot be specified on a correlation column” Cause: Action: |
| ORA-01706 ORA-01706, 00000, “user function result value was too large” Cause: Action: |
| ORA-01707 ORA-01707, 00000, “missing LIST keyword” Cause: Action: |
| ORA-01708 ORA-01708, 00000, “ACCESS or SESSION expected” Cause: Action: |
| ORA-01709 ORA-01709, 00000, “program does not exist” Cause: Action: |
| ORA-01710 ORA-01710, 00000, “missing OF keyword” Cause: Action: |
| ORA-01711 ORA-01711, 00000, “duplicate privilege listed” Cause: Action: |
| ORA-01712 ORA-01712, 00000, “you cannot grant a privilege which you do not have” Cause: Action: |
| ORA-01713 ORA-01713, 00000, “GRANT OPTION does not exist for that privilege” Cause: Action: |
| ORA-01714 ORA-01714, 00000, “error in execution of user function” Cause: Action: |
| ORA-01715 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 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 ORA-01717, 00000, “seccta: invalid access mode token passed” Cause: Action: |
| ORA-01718 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 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 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 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 ORA-01722, 00000, “invalid number” Cause: Action: |
| ORA-01723 ORA-01723, 00000, “zero-length columns are not allowed” Cause: Action: |
| ORA-01724 ORA-01724, 00000, “floating point precision is out of range (1 to 126)” Cause: Self-evident. Action: Self-evident. |
| ORA-01725 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 ORA-01726, 00000, “a table is not appropriate here” Cause: Action: |
| ORA-01727 ORA-01727, 00000, “numeric precision specifier is out of range (1 to 38)” Cause: Action: |
| ORA-01728 ORA-01728, 00000, “numeric scale specifier is out of range (-84 to 127)” Cause: Action: |
| ORA-01729 ORA-01729, 00000, “database link name expected” Cause: Action: |
| ORA-01730 ORA-01730, 00000, “invalid number of column names specified” Cause: Action: |
| ORA-01731 ORA-01731, 00000, “circular view definition encountered” Cause: Action: |
| ORA-01732 ORA-01732, 00000, “data manipulation operation not legal on this view” Cause: Action: |
| ORA-01733 ORA-01733, 00000, “virtual column not allowed here” Cause: Action: |
| ORA-01734 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 ORA-01735, 00000, “invalid ALTER TABLE option” Cause: Action: |
| ORA-01736 ORA-01736, 00000, “[NOT] SUCCESSFUL expected” Cause: Action: |
| ORA-01737 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 ORA-01738, 00000, “missing IN keyword” Cause: Action: |
| ORA-01739 ORA-01739, 00000, “missing MODE keyword” Cause: Action: |
| ORA-01740 ORA-01740, 00000, “missing double quote in identifier” Cause: Action: |
| ORA-01741 ORA-01741, 00000, “illegal zero-length identifier” Cause: Action: |
| ORA-01742 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 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 ORA-01744, 00000, “inappropriate INTO” Cause: Action: |
| ORA-01745 ORA-01745, 00000, “invalid host/bind variable name” Cause: Action: |
| ORA-01746 ORA-01746, 00000, “indicator variable not permitted here” Cause: Action: |
| ORA-01747 ORA-01747, 00000, “invalid user.table.column, table.column, or column specification” Cause: Action: |
| ORA-01748 ORA-01748, 00000, “only simple column names allowed here” Cause: Action: |
| ORA-01749 ORA-01749, 00000, “you may not GRANT/REVOKE privileges to/from yourself” Cause: Action: |
| ORA-01750 ORA-01750, 00000, “UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column” Cause: Action: |
| ORA-01751 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 ORA-01752, 00000, “cannot delete from view without exactly one key-preserved table” Cause: The deleted table had – no key-preserved tables, – more than one key-preserved table, or – the key-preserved table was an unmerged view. Action: Redefine the view or delete it from the underlying base tables. |
| ORA-01753 ORA-01753, 00000, “column definition incompatible with clustered column definition” Cause: Action: |
| ORA-01754 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 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 ORA-01756, 00000, “quoted string not properly terminated” Cause: Action: |
| ORA-01757 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 ORA-01758, 00000, “table must be empty to add mandatory (NOT NULL) column” Cause: Action: |
| ORA-01759 ORA-01759, 00000, “user function is incorrectly defined” Cause: Action: |
| ORA-01760 ORA-01760, 00000, “illegal argument for function” Cause: Action: |
| ORA-01761 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 ORA-01762, 00000, “vopdrv: view query block not in FROM” Cause: Action: |
| ORA-01763 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 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 ORA-01765, 00000, “specifying table’s owner name is not allowed” Cause: Action: |
| ORA-01766 ORA-01766, 00000, “dictionary table not allowed in this context” Cause: Action: |
| ORA-01767 ORA-01767, 00000, “UPDATE … SET expression must be a subquery” Cause: Action: |
| ORA-01768 ORA-01768, 00000, “number string too long” Cause: Action: |
| ORA-01769 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 ORA-01770, 00000, “CLUSTER option not allowed in CREATE CLUSTER command” Cause: Action: |
| ORA-01771 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 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 ORA-01773, 00000, “may not specify column datatypes in this CREATE TABLE” Cause: Action: |
| ORA-01774 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 ORA-01775, 00000, “looping chain of synonyms” Cause: Action: |
| ORA-01776 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 ORA-01777, 00000, “WITH GRANT OPTION not allowed in this system” Cause: Action: |
| ORA-01778 ORA-01778, 00000, “maximum subquery nesting level exceeded” Cause: Action: |
| ORA-01779 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 ORA-01780, 00000, “string literal required” Cause: Action: |
| ORA-01781 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 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 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 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 ORA-01785, 00000, “ORDER BY item must be the number of a SELECT-list expression” Cause: Action: |
| ORA-01786 ORA-01786, 00000, “FOR UPDATE of this query expression is not allowed” Cause: Action: |
| ORA-01787 ORA-01787, 00000, “only one clause allowed per query block” Cause: Action: |
| ORA-01788 ORA-01788, 00000, “CONNECT BY clause required in this query block” Cause: Action: |
| ORA-01789 ORA-01789, 00000, “query block has incorrect number of result columns” Cause: Action: |
| ORA-01790 ORA-01790, 00000, “expression must have same datatype as corresponding expression” Cause: Action: |
| ORA-01791 ORA-01791, 00000, “not a SELECTed expression” Cause: Action: |
| ORA-01792 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 ORA-01793, 00000, “maximum number of index columns is 32″ Cause: Action: |
| ORA-01794 ORA-01794, 00000, “maximum number of cluster columns is 32″ Cause: Action: |
| ORA-01795 ORA-01795, 00000, “maximum number of expressions in a list is 1000″ Cause: Action: |
| ORA-01796 ORA-01796, 00000, “this operator cannot be used with lists” Cause: Action: |
| ORA-01797 ORA-01797, 00000, “this operator must be followed by ANY or ALL” Cause: Action: |
| ORA-01798 ORA-01798, 00000, “missing EXCEPTION keyword” Cause: Action: |
| ORA-01799 ORA-01799, 00000, “a column may not be outer-joined to a subquery” Cause: <expression>(+) <relop> (<subquery>) 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. |
| ORA-01800 ORA-01800, 00000, “a literal in the date format was too large to process” Cause: Action: |
| ORA-01801 ORA-01801, 00000, “date format is too long for internal buffer” Cause: Action: |
| ORA-01802 ORA-01802, 00000, “Julian date is out of range” Cause: Action: |
| ORA-01803 ORA-01803, 00000, “failure in getting date/time” Cause: Action: |
| ORA-01804 ORA-01804, 00000, “failure to initialize timezone information” Cause: The timezone information file was not properly read. Action: Please contact Oracle Customer Support. |
| ORA-01810 ORA-01810, 00000, “format code appears twice” Cause: Action: |
| ORA-01811 ORA-01811, 00000, “Julian date precludes use of day of year” Cause: Action: |
| ORA-01812 ORA-01812, 00000, “year may only be specified once” Cause: Action: |
| ORA-01813 ORA-01813, 00000, “hour may only be specified once” Cause: Action: |
| ORA-01814 ORA-01814, 00000, “AM/PM conflicts with use of A.M./P.M.” Cause: Action: |
| ORA-01815 ORA-01815, 00000, “BC/AD conflicts with use of B.C./A.D.” Cause: Action: |
| ORA-01816 ORA-01816, 00000, “month may only be specified once” Cause: Action: |
| ORA-01817 ORA-01817, 00000, “day of week may only be specified once” Cause: Action: |
| ORA-01818 ORA-01818, 00000, “‘HH24′ precludes use of meridian indicator” Cause: Action: |
| ORA-01819 ORA-01819, 00000, “signed year precludes use of BC/AD” Cause: Action: |
| ORA-01820 ORA-01820, 00000, “format code cannot appear in date input format” Cause: Action: |
| ORA-01821 ORA-01821, 00000, “date format not recognized” Cause: Action: |
| ORA-01822 ORA-01822, 00000, “era format code is not valid with this calendar” Cause: Action: |
| ORA-01830 ORA-01830, 00000, “date format picture ends before converting entire input string” Cause: Action: |
| ORA-01831 ORA-01831, 00000, “year conflicts with Julian date” Cause: Action: |
| ORA-01832 ORA-01832, 00000, “day of year conflicts with Julian date” Cause: Action: |
| ORA-01833 ORA-01833, 00000, “month conflicts with Julian date” Cause: Action: |
| ORA-01834 ORA-01834, 00000, “day of month conflicts with Julian date” Cause: Action: |
| ORA-01835 ORA-01835, 00000, “day of week conflicts with Julian date” Cause: Action: |
| ORA-01836 ORA-01836, 00000, “hour conflicts with seconds in day” Cause: Action: |
| ORA-01837 ORA-01837, 00000, “minutes of hour conflicts with seconds in day” Cause: Action: |
| ORA-01838 ORA-01838, 00000, “seconds of minute conflicts with seconds in day” Cause: Action: |
| ORA-01839 ORA-01839, 00000, “date not valid for month specified” Cause: Action: |
| ORA-01840 ORA-01840, 00000, “input value not long enough for date format” Cause: Action: |
| ORA-01841 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 ORA-01842, 00000, “quarter must be between 1 and 4″ Cause: Action: |
| ORA-01843 ORA-01843, 00000, “not a valid month” Cause: Action: |
| ORA-01844 ORA-01844, 00000, “week of year must be between 1 and 52″ Cause: Action: |
| ORA-01845 ORA-01845, 00000, “week of month must be between 1 and 5″ Cause: Action: |
| ORA-01846 ORA-01846, 00000, “not a valid day of the week” Cause: Action: |
| ORA-01847 ORA-01847, 00000, “day of month must be between 1 and last day of month” Cause: Action: |
| ORA-01848 ORA-01848, 00000, “day of year must be between 1 and 365 (366 for leap year)” Cause: Action: |
| ORA-01849 ORA-01849, 00000, “hour must be between 1 and 12″ Cause: Action: |
| ORA-01850 ORA-01850, 00000, “hour must be between 0 and 23″ Cause: Action: |
| ORA-01851 ORA-01851, 00000, “minutes must be between 0 and 59″ Cause: Action: |
| ORA-01852 ORA-01852, 00000, “seconds must be between 0 and 59″ Cause: Action: |
| ORA-01853 ORA-01853, 00000, “seconds in day must be between 0 and 86399″ Cause: Action: |
| ORA-01854 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 ORA-01855, 00000, “AM/A.M. or PM/P.M. required” Cause: Action: |
| ORA-01856 ORA-01856, 00000, “BC/B.C. or AD/A.D. required” Cause: Action: |
| ORA-01857 ORA-01857, 00000, “not a valid time zone” Cause: Action: |
| ORA-01858 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 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 ORA-01860, 00000, “week of year must be between 1 and 53″ Cause: Action: |
| ORA-01861 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 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 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 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 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 ORA-01866, 00000, “the datetime class is invalid” Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. |
| ORA-01867 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 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 ORA-01869, 00000, “reserved for future use” Cause: Action: |
| ORA-01870 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 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 ORA-01872, 00000, “reserved for future use” Cause: Action: |
| ORA-01873 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 ORA-01874, 00000, “time zone hour must be between -12 and 14″ Cause: The time zone hour specified was not in the valid range. Action: Specify a time zone hour between -12 and 14. |
| ORA-01875 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 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 ORA-01877, 00000, “string is too long for internal buffer” Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. |
| ORA-01878 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 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 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 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 ORA-01882, 00000, “timezone region %s not found” Cause: The specified region name was not found. Action: Please contact Oracle Customer Support. |
| ORA-01883 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 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 ORA-01891, 00000, “Datetime/Interval internal error” Cause: Internal error. Action: Please contact Oracle Worldwide Support. |
| ORA-01898 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 ORA-01899, 00000, “bad precision specifier” Cause: Action: |
| ORA-01900 ORA-01900, 00000, “LOGFILE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01901 ORA-01901, 00000, “ROLLBACK keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01902 ORA-01902, 00000, “SEGMENT keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01903 ORA-01903, 00000, “EVENTS keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01904 ORA-01904, 00000, “DATAFILE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01905 ORA-01905, 00000, “STORAGE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01906 ORA-01906, 00000, “BACKUP keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01907 ORA-01907, 00000, “TABLESPACE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01908 ORA-01908, 00000, “EXISTS keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01909 ORA-01909, 00000, “REUSE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01910 ORA-01910, 00000, “TABLES keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01911 ORA-01911, 00000, “CONTENTS keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01912 ORA-01912, 00000, “ROW keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01913 ORA-01913, 00000, “EXCLUSIVE keyword expected” Cause: keyword missing Action: supply missing keyword |
| ORA-01914 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-01937, 00000, “missing or invalid role name” Cause: A valid role name was expected. Action: Specify a valid role name. |
| ORA-01938 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 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 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 ORA-01941, 00000, “SEQUENCE keyword expected” MERGE: 1917 RENUMBERED TO 1941 Cause: keyword missing Action: supply missing keyword |
| ORA-01942 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 ORA-01943, 00000, “IDENTIFIED BY already specified” Cause: The identified clause has been given twice. Action: Use only one identified by clause. |
| ORA-01944 ORA-01944, 00000, “IDENTIFIED EXTERNALLY already specified” Cause: The identified externaly clause has been given twice. Action: Use only one identified clause. |
| ORA-01945 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 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 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 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 ORA-01949, 00000, “ROLE keyword expected” Cause: The role keyword is required here. Action: Specify the role keyword. |
| ORA-01950 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 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 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 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 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 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 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 ORA-01957, 00000, “Keyword MIN or MAX expected, not found” Cause: Action: |
| ORA-01958 ORA-01958, 00000, “Must supply an integer for the LAYER option” Cause: Action: |
| ORA-01959 ORA-01959, 00000, “Must supply an integer for the OPCODE option” Cause: Action: |
| ORA-01960 ORA-01960, 00000, “Invalid dump logfile option” Cause: Action: |
| ORA-01961 ORA-01961, 00000, “Invalid dump option” Cause: Action: |
| ORA-01962 ORA-01962, 00000, “Must specify a file number or log sequence number” Cause: Action: |
| ORA-01963 ORA-01963, 00000, “Must specify a block number” Cause: Action: |
| ORA-01964 ORA-01964, 00000, “Must specify a time for the TIME option” Cause: Action: |
| ORA-01965 ORA-01965, 00000, “Must specify a PERIOD” Cause: Action: |
| ORA-01967 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 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 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 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 ORA-01971, 00000, “Illegal ALTER TRACING option” Cause: Action: |
| ORA-01972 ORA-01972, 00000, “Must specify a string for ALTER TRACING ENABLE or DISABLE” Cause: Action: |
| ORA-01973 ORA-01973, 00000, “Missing change number” Cause: Keyword “CHANGE” found but change number not specified. Action: Fix command line and resubmit |
| ORA-01974 ORA-01974, 00000, “Illegal archive option” Cause: Not a valid option to the “ALTER SYSTEM ARCHIVE” command Action: |
| ORA-01975 ORA-01975, 00000, “Illegal character in change number %s” Cause: Action: |
| ORA-01976 ORA-01976, 00000, “Missing change number” Cause: Action: |
| ORA-01977 ORA-01977, 00000, “Missing thread number” Cause: Keyword “THREAD” found but thread number not specified. Action: Fix command line and resubmit |
| ORA-01978 ORA-01978, 00000, “Missing sequence number” Cause: Keyword “SEQUENCE” found but sequence number not specified. Action: Fix command line and resubmit |
| ORA-01979 ORA-01979, 00000, “missing or invalid password for role ‘%s’” Cause: An attempt was made to enable a role without giving |
| ORA-01980 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 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 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 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 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 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 ORA-01986, 00000, “OPTIMIZER_GOAL is obsolete” Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced. Action: Use the OPTIMIZER_MODE parameter. |
| ORA-01987 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 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 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 ORA-01990, 00000, “error opening password file ‘%s’” Cause: Action: |
| ORA-01991 ORA-01991, 00000, “invalid password file ‘%s’” Cause: Action: |
| ORA-01992 ORA-01992, 00000, “error closing password file ‘%s’” Cause: Action: |
| ORA-01993 ORA-01993, 00000, “error writing password file ‘%s’” Cause: Action: |
| ORA-01994 ORA-01994, 00000, “GRANT failed: password file missing or disabled” Cause: The operation failed either because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the password file was missing. Action: Create the password file using the orapwd tool and set the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE. |
| ORA-01995 ORA-01995, 00000, “error reading password file ‘%s’” Cause: Action: |
| ORA-01996 ORA-01996, 00000, “GRANT failed: password file ‘%s’ is full” Cause: Action: |
| ORA-01997 ORA-01997, 00000, “GRANT failed: user ‘%s’ is identified externally” Cause: Action: |
| ORA-01998 ORA-01998, 00000, “REVOKE failed: user SYS always has SYSOPER and SYSDBA” Cause: Action: |
| ORA-01999 ORA-01999, 00000, “password file cannot be updated in SHARED mode” Cause: The operation failed because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to SHARED. Action: Set the INIT.ORA parameter to EXCLUSIVE. |
| ORA-02000 ORA-02000, 00000, “missing %s keyword” |
| ORA-02001 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 ORA-02002, 00000, “error while writing to audit trail” Cause: Action: |
| ORA-02003 ORA-02003, 00000, “invalid USERENV parameter” Cause: Action: |
| ORA-02004 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 ORA-02005, 00000, “implicit (-1) length not valid for this bind or define datatype” Cause: Action: |
| ORA-02006 ORA-02006, 00000, “invalid packed decimal format string” Cause: Action: |
| ORA-02007 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 ORA-02008, 00000, “non-zero scale specified for nonnumeric column” Cause: Action: |
| ORA-02009 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 ORA-02010, 00000, “missing host connect string” Cause: Action: |
| ORA-02011 ORA-02011, 00000, “duplicate database link name” Cause: Action: |
| ORA-02012 ORA-02012, 00000, “missing USING keyword” Cause: Action: |
| ORA-02013 ORA-02013, 00000, “missing CONNECT keyword” Cause: Action: |
| ORA-02014 ORA-02014, 00000, “cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.” |
| ORA-02015 ORA-02015, 00000, “cannot select FOR UPDATE from remote table” Cause: Action: |
| ORA-02016 ORA-02016, 00000, “cannot use a subquery in a START WITH on a remote database” Cause: Action: |
| ORA-02017 ORA-02017, 00000, “integer value required” Cause: Action: |
| ORA-02018 ORA-02018, 00000, “database link of same name has an open connection” Cause: Action: |
| ORA-02019 ORA-02019, 00000, “connection description for remote database not found” Cause: Action: |
| ORA-02020 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 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 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 ORA-02023, 00000, “START WITH or CONNECT BY predicate cannot be evaluated by remote data base” Cause: Action: |
| ORA-02024 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 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 ORA-02026, 00000, “missing LINK keyword” Cause: keyword missing Action: supply missing keyword |
| ORA-02027 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 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 ORA-02029, 00000, “missing FILE keyword” Cause: keyword missing Action: supply missing keyword |
| ORA-02030 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 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 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 ORA-02033, 00000, “a cluster index for this cluster already exists” Cause: A cluster index already exists for the cluster. Action: None. |
| ORA-02034 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 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 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 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 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 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: |
| ORA-02040 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 ORA-02041, 00000, “client database did not begin a transaction” Cause: internal error Action: contact support |
| ORA-02042 ORA-02042, 00000, “too many distributed transactions” Cause: the distributed transaction table was full because too many // distributed transactions were active. Action: 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 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 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 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 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 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 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 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 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 ORA-02051, 00000, “another session in same transaction failed” Cause: a session at the same site with same global transaction ID failed; It can also be caused by application error if an attempt was made to update database while another tightly coupled transaction branch with same global transaction ID has been finalized. Action: none necessary, transaction automatically recovered. In case of application error, make sure no more updates to database once transaction manager has started two-phase commit for tightly coupled distributed transaction. |
| ORA-02052 ORA-02052, 00000, “remote transaction failure at %s” Cause: error in remote transaction at given DBLINK Action: retry |
| ORA-02053 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 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 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 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 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 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 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 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 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 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 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 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 procedure call with OUT parameters or function call. Action: simplify remote update statement |
| ORA-02065 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02078, 00000, “invalid setting for ALTER SYSTEM FIXED_DATE” Cause: Action: // |
| ORA-02079 ORA-02079, 00000, “cannot join a committing distributed transaction” Cause: Once a transaction branch is prepared, no more new transaction branches are allowed to start, nor is the prepared transaction branch allowed to be joined. Action: Check the application code as this is an XA protocol violation. // |
| ORA-02080 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 <link> command. Action: commit or rollback, and close all cursors // |
| ORA-02081 ORA-02081, 00000, “database link is not open” Cause: dblink given is not currently open. // |
| ORA-02082 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 ORA-02083, 00000, “database name has illegal character ‘%s’” Cause: supplied database name can contain only A-Z, 0-9, ‘_’, ‘#’, ‘$’ ‘.’ and ‘@’ characters. // |
| ORA-02084 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 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 ORA-02086, 00000, “database (link) name is too long” Cause: database/database link name can have at most 128 characters. |
| ORA-02087 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 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 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 ORA-02090, 00000, “network error: attempted callback+passthru” Cause: internal error. // |
| ORA-02091 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 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 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 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 ORA-02095, 00000, “specified initialization parameter cannot be modified” Cause: The specified initialization parameter is not modifiable |
| ORA-02096 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 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 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 ORA-02099, 00000, “used for internal purposes, should never be printed” |
| ORA-02100 ORA-02100, 00000, “PCC: out of memory (i.e., could not allocate)” |
| ORA-02101 ORA-02101, 00000, “PCC: inconsistent cursor cache (uce/cuc mismatch)” |
| ORA-02102 ORA-02102, 00000, “PCC: inconsistent cursor cache (no cuc entry for this uce)” |
| ORA-02103 ORA-02103, 00000, “PCC: inconsistent cursor cache (out-of-range cuc ref)” |
| ORA-02104 ORA-02104, 00000, “PCC: inconsistent host cache (no cuc available)” |
| ORA-02105 ORA-02105, 00000, “PCC: inconsistent cursor cache (no cuc entry in cache)” |
| ORA-02106 ORA-02106, 00000, “PCC: inconsistent cursor cache (OraCursor nr is bad)” |
| ORA-02107 ORA-02107, 00000, “PCC: this pgm too old for run-time library: please re-PCC it” |
| ORA-02108 ORA-02108, 00000, “PCC: invalid descriptor passed to run-time library” |
| ORA-02109 ORA-02109, 00000, “PCC: inconsistent host cache (out-of-range sit ref)” |
| ORA-02110 ORA-02110, 00000, “PCC: inconsistent host cache (invalid sqi type)” |
| ORA-02111 ORA-02111, 00000, “PCC: heap consistency error” |
| ORA-02112 ORA-02112, 00000, “PCC: SELECT..INTO returns too many rows” |
| ORA-02140 ORA-02140, 00000, “invalid tablespace name” Cause: An identifier does not follow ALTER TABLESPACE. Action: Specify a tablespace name following ALTER TABLESPACE. |
| ORA-02141 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 ORA-02142, 00000, “missing or invalid ALTER TABLESPACE option” Cause: A valid option was not present. Action: Use one of the valid options: add, rename, default, online, // offline, read only, read write, begin, end, no, force, retention guarantee and retention noguarantee. |
| ORA-02143 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 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 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 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 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 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 ORA-02149, 00000, “Specified partition does not exist” Cause: Partition not found for the object. Action: Retry with correct partition name. |
| ORA-02150 ORA-02150, 00000, “invalid new tablespace name” Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO statement was invalid. Action: Retry with a valid new tablespace name. |
| ORA-02151 ORA-02151, 00000, “invalid tablespace name: %s” Cause: Oracle cannot create a tablespace whose name starts with ‘_$deleted$’. Action: Try a different tablespace name. |
| ORA-02152 ORA-02152, 00000, “Invalid ALTER TABLESPACE … RENAME option” Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE … RENAME. Action: The user must specify either DATAFILE or TO following ALTER TABLESPACE … RENAME. |
| ORA-02153 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-02154 ORA-02154, 00000, “a tablespace with the name ‘%s’ is found” Cause: An attempt to rename a tablespace to a new name failed because the new name is already used by some other tablespace. Action: Retry with a different new name. |
| ORA-02155 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 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 ORA-02157, 00000, “no options specified for ALTER USER” Cause: No options were specified. Action: Specify at least one ALTER USER option. |
| ORA-02158 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 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 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 ORA-02161, 00000, “invalid value for MAXLOGFILES” Cause: A number does not follow MAXLOGFILES. Action: Specify a number after MAXLOGFILES. |
| ORA-02162 ORA-02162, 00000, “invalid value for MAXDATAFILES” Cause: A number does not follow MAXDATAFILES. Action: Specify a number after MAXDATAFILES. |
| ORA-02163 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 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 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 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 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 ORA-02168, 00000, “invalid value for FREELISTS” Cause: A number does not follow FREELISTS Action: Specify a number after FREELISTS |
| ORA-02169 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 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 ORA-02171, 00000, “invalid value for MAXLOGHISTORY” Cause: A number does not follow MAXLOGHISTORY Action: Specify a number after MAXLOGHISTORY |
| ORA-02172 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 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 ORA-02174, 00000, “Missing required thread number” Cause: Must specify thread number after THREAD keyword Action: |
| ORA-02175 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 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 ORA-02177, 00000, “Missing required group number” Cause: Must specify group number after GROUP keyword Action: |
| ORA-02178 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 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 ORA-02180, 00000, “invalid option for CREATE TABLESPACE” Cause: An invalid option appeared. Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, // ONLINE, OFFLINE, FORCE, RETENTION. |
| ORA-02181 ORA-02181, 00000, “invalid option to ROLLBACK WORK” Cause: A token other than TO follows ROLLBACK [WORK]. Action: Place nothing or TO SAVEPOINT <NAME> after ROLLBACK [WORK]. |
| ORA-02182 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 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 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 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 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 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-02188 ORA-02188, 00000, “Cannot enable instance publicly” Cause: An attempt was made to publicly enable a thread associated with an instance. Action:Leave out the PUBLIC keyword. |
| ORA-02189 ORA-02189, 00000, “ON <tablespace> required” Cause: In a grant or revoke statement, the user specified a tablespace // quota but did not follow it with the ON <tablespace> clause. Action: Specify the tablespace on which the quota is to be applied // with the ON <tablespace> clause. |
| ORA-02190 ORA-02190, 00000, “keyword TABLES expected” Cause: The keyword TABLES is expected following DROP CLUSTER <NAME> // INCLUDING. Action: Place TABLES after INCLUDING. |
| ORA-02191 ORA-02191, 00000, “correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT <rbs>” Cause: There is a syntax error in the user’s statement. Action: Correct the syntax as indicated. |
| ORA-02192 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02206, 00000, “duplicate INITRANS option specification” Cause: INITRANS is specified more than once. Action: Specify INITRANS at most once. |
| ORA-02207 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 ORA-02208, 00000, “duplicate MAXTRANS option specification” Cause: MAXTRANS is specified more than once. Action: Specify MAXTRANS at most once. |
| ORA-02209 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 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 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 ORA-02212, 00000, “duplicate PCTFREE option specification” Cause: PCTFREE option specified more than once. Action: Specify PCTFREE at most once. |
| ORA-02213 ORA-02213, 00000, “duplicate PCTUSED option specification” Cause: PCTUSED option specified more than once. Action: Specify PCTUSED at most once. |
| ORA-02214 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 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 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 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 ORA-02218, 00000, “invalid INITIAL storage option value” Cause: The specified value must be an integer. Action: Choose an appropriate integer value. |
| ORA-02219 ORA-02219, 00000, “invalid NEXT storage option value” Cause: The specified value must be an integer. Action: Choose an appropriate integer value. |
| ORA-02220 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 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 ORA-02222, 00000, “invalid PCTINCREASE storage option value” Cause: The specified value must be a positive integer. Action: Specify an appropriate value. |
| ORA-02223 ORA-02223, 00000, “invalid OPTIMAL storage option value” Cause: The specified value must be an integer. Action: Choose an appropriate integer value. |
| ORA-02224 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 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 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 ORA-02227, 00000, “invalid cluster name” Cause: A cluster name of the form [ <identifier> . ] <identifier> is // expected but not present. Action: Enter an appropriate cluster name. |
| ORA-02228 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02241, 00000, “must of form EXTENTS (FILE <n> BLOCK <n> SIZE <n>, …)” Cause: bad extent storage clause Action: respecify |
| ORA-02242 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 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 ORA-02244, 00000, “invalid ALTER ROLLBACK SEGMENT option” Cause: The STORAGE option is expected but not found. Action: Specify the STORAGE option. |
| ORA-02245 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 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 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 ORA-02248, 00000, “invalid option for ALTER SESSION” Cause: Obvious. Action: see SQL Language Manual for legal options. |
| ORA-02249 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 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 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 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 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 ORA-02254, 00000, “DEFAULT <expression> 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 ORA-02255, 00000, “obsolete 7.1.5″ Cause: Was that defaults must not conflict with not null constraints Action: |
| ORA-02256 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 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 ORA-02258, 00000, “duplicate or conflicting NULL and/or NOT NULL specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02259 ORA-02259, 00000, “duplicate UNIQUE/PRIMARY KEY specifications” Cause: Self-evident. Action: Remove the duplicate specification. |
| ORA-02260 ORA-02260, 00000, “table can have only one primary key” Cause: Self-evident. Action: Remove the extra primary key. |
| ORA-02261 ORA-02261, 00000, “such unique or primary key already exists in the table” Cause: Self-evident. Action: Remove the extra key. |
| ORA-02262 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 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 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 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 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 ORA-02267, 00000, “column type incompatible with referenced column type” Cause: The datatype of the referencing column is incompatible with the |
| ORA-02268 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 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 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 ORA-02271, 00000, “table does not have such constraint” Cause: Self-evident. Action: Make sure the specified constraint name is correct. |
| ORA-02272 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 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 ORA-02274, 00000, “duplicate referential constraint specifications” Cause: Self-evident. Action: Remove the duplicate specification. |
| ORA-02275 ORA-02275, 00000, “such a referential constraint already exists in the table” Cause: Self-evident. Action: Remove the extra constraint. |
| ORA-02276 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 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 ORA-02278, 00000, “duplicate or conflicting MAXVALUE/NOMAXVALUE specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02279 ORA-02279, 00000, “duplicate or conflicting MINVALUE/NOMINVALUE specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02280 ORA-02280, 00000, “duplicate or conflicting CYCLE/NOCYCLE specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02281 ORA-02281, 00000, “duplicate or conflicting CACHE/NOCACHE specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02282 ORA-02282, 00000, “duplicate or conflicting ORDER/NOORDER specifications” Cause: Self-evident. Action: Remove the duplicate or conflicting specification. |
| ORA-02283 ORA-02283, 00000, “cannot alter starting sequence number” Cause: Self-evident. Action: Don’t alter it. |
| ORA-02284 ORA-02284, 00000, “duplicate INCREMENT BY specifications” Cause: Self-evident. Action: Remove the duplicate specification. |
| ORA-02285 ORA-02285, 00000, “duplicate START WITH specifications” Cause: Self-evident. Action: Remove the duplicate specification. |
| ORA-02286 ORA-02286, 00000, “no options specified for ALTER SEQUENCE” Cause: Self-evident. Action: The statement is meaningless without any options. |
| ORA-02287 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 ORA-02288, 00000, “invalid OPEN mode” Cause: A token other than RESETLOGS appears following // ALTER DATABASE <NAME> OPEN. Action: Either nothing or RESETLOGS should be placed following OPEN. |
| ORA-02289 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 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 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 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 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 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 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 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 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 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 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 |
| ORA-02300 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 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 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 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 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 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 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 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 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 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 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 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. // |
| ORA-02313 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. |
| ORA-02314 ORA-02314, 00000, “illegal use of type constructor” Cause: The statement contains an illegal use of a type constructor. Action: Refer to the SQL Reference manual for the correct statement syntax. |
| ORA-02315 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. |
| ORA-02320 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. |
| ORA-02321 ORA-02321, 00000, “event for nested table equipartition” Document: NO Cause: Action: |
| ORA-02322 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. |
| ORA-02324 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. |
| ORA-02327 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. |
| ORA-02329 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-02342 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 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 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 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 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 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. |
| ORA-02351 ORA-02351, 00000, “internal error: %s\n” Cause: An unexpected error condition was detected. Action: Make a note of the error number and message and contact Oracle Support Services. |
| ORA-02352 ORA-02352, 00000, “error setting an OCI attribute: %s\n” Cause: An OCI error has occurred. Action: The table or column referenced may not be accessible. Contact Oracle Support Services if the problem cannot be resolved. |
| ORA-02353 ORA-02353, 00000, “error fetching an OCI attribute: %s\n” Cause: An OCI error has occurred. Action: The table or column referenced may not be accessible. Contact Oracle Support Services if the problem cannot be resolved. |
| ORA-02354 ORA-02354, 00000, “error in exporting/importing data\n%s” Cause: An error has occurred in a stream export or import operation. This message will be followed by another message giving more details about this error. Action: See export/import documentation for an explanation of the second error message. |
| ORA-02355 ORA-02355, 00000, “error opening file: %s\n” Cause: An attempt to open the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. |
| ORA-02356 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 ORA-02357, 00000, “header in file %s may not contain correct information\n” Cause: The header may be corrupted. Action: Contact Oracle Support Services. |
| ORA-02358 ORA-02358, 00000, “error in exporting or importing data\n” Cause: An error has occurred in a stream export or import operation. Action: Contact Oracle Support Services. |
| ORA-02359 ORA-02359, 00000, “database version in file %s is not valid\n” Cause: The specified file could not be used for this load because its database version was not compatible with the database version in the other files in the DUMPFILE clause. Action: Verify all the files in the DUMPFILE clause are from the same unload operation. |
| ORA-02360 ORA-02360, 00000, “fatal error during data export/import initialization\n” Cause: An unexpected error occurred during initialization for data export/import. Action: Contact Oracle Support Services. |
| ORA-02361 ORA-02361, 00000, “error while attempting to allocate %d bytes of memory\n” Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory. Action: Reconnect to the instance and retry the operation. |
| ORA-02362 ORA-02362, 00000, “error closing file: %s\n” Cause: An attempt to close the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. |
| ORA-02363 ORA-02363, 00000, “error reading from file: %s\n” Cause: An attempt to read from the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. |
| ORA-02364 ORA-02364, 00000, “error writing to file: %s\n” Cause: An attempt to write to the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if |
| ORA-02365 ORA-02365, 00000, “error seeking in file: %s\n” Cause: An attempt to seek to the specified position in file failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if |
| ORA-02366 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 ORA-02367, 00000, “read ended but had expected more data from file %s\n” Cause: A truncated or incomplete file was used for the load operation. Action: Verify unload operation completed successfully and that the files had not been accidentally truncated. |
| ORA-02368 ORA-02368, 00000, “the following file is not valid for this load operation\n” Cause: A file could not be used for this load. See the following message for more information. Action: Verify all the files in the DUMPFILE clause are from the same unload operation and that the unload was successful. |
| ORA-02369 ORA-02369, 00000, “internal number in header in file %s is not valid\n” Cause: The specified file could not be used for this load because the internal number in the header was not valid. Action: If the dump files were transferred over, verify the transfer operation was done correctly. |
| ORA-02370 ORA-02370, 00000, “internal metadata in file %s is not valid\n” Cause: The specified file could not be used for this load because the internal metadata stored in this file does not match the metadata stored in the first file piece set. Action: Verify all the files in the DUMPFILE clause are from the same unload operation. |
| ORA-02371 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 ORA-02372, 00000, “data for row: %*.*s \n” Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error. Action: None. This is only an informational message. |
| ORA-02373 ORA-02373, 00000, “Error parsing insert statement for table %s.” Cause: self-evident. Action: Check the error given below this one. |
| ORA-02374 ORA-02374, 00000, “conversion error loading table %*.*s.%*.*s” Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row. Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported. |
| ORA-02375 ORA-02375, 0, “conversion error loading table %*.*s.%*.*s partition %*.*s” Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row. Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported. |
| ORA-02376 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 ORA-02377, 00000, “invalid resource limit” Cause: specifying limit of 0 Action: specify limit > 0 |
| ORA-02378 ORA-02378, 00000, “duplicate resource name %s” Cause: Action: |
| ORA-02379 ORA-02379, 00000, “profile %s already exists” Cause: Try to create a profile which already exist Action: |
| ORA-02380 ORA-02380, 00000, “profile %s does not exist” Cause: Try to assign a user to a non-existant profile Action: |
| ORA-02381 ORA-02381, 00000, “cannot drop PUBLIC_DEFAULT profile” Cause: Try to drop PUBLIC_DEFAULT profile Action: |
| ORA-02382 ORA-02382, 00000, “profile %s has users assigned, cannot drop without CASCADE” Cause: Action: |
| ORA-02383 ORA-02383, 00000, “illegal cost factor” Cause: Negative or UNLIMITED cost for this resourc Action: |
| ORA-02390 ORA-02390, 00000, “exceeded COMPOSITE_LIMIT, you are being logged off” Cause: Action: |
| ORA-02391 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 profile. 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 ORA-02392, 00000, “exceeded session limit on CPU usage, you are being logged off” Cause: Action: |
| ORA-02393 ORA-02393, 00000, “exceeded call limit on CPU usage” Cause: Action: |
| ORA-02394 ORA-02394, 00000, “exceeded session limit on IO usage, you are being logged off” Cause: Action: |
| ORA-02395 ORA-02395, 00000, “exceeded call limit on IO usage” Cause: Action: |
| ORA-02396 ORA-02396, 00000, “exceeded maximum idle time, please connect again” Cause: as stated Action: |
| ORA-02397 ORA-02397, 00000, “exceeded PRIVATE_SGA limit, you are being logged off” Cause: Only when using TP monitor Action: expand limit |
| ORA-02398 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 ORA-02399, 00000, “exceeded maximum connect time, you are being logged off” Cause: As stated Action: |
| ORA-02400 ORA-02400, 00000, “explain plan output buffer size limit exceeded” Cause: Internally this error is raised and caught to handle cases where // the plan output exceeds te buffer size. The output is truncated in // cases. Action: This error should never be seen externally. |
| ORA-02401 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 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 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 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. |
| ORA-02405 ORA-02405, 00000, “invalid sql plan object provided” Cause: The user provided a NULL, empty, or malformed object of type SQL_PLAN_TABLE_TYPE Action: Provide a new, properly formed object to the function |
| ORA-02420 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 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 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 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 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 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 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 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 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 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. |
| ORA-02430 ORA-02430, 00000, “cannot enable constraint (%s) – no such constraint” Cause: the named constraint does not exist for this table. Action: Obvious |
| ORA-02431 ORA-02431, 00000, “cannot disable constraint (%s) – no such constraint” Cause: the named constraint does not exist for this table. Action: Obvious |
| ORA-02432 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 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 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 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 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 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 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 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 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 ORA-02441, 00000, “Cannot drop nonexistent primary key” Cause: alter table drop primary key – primary key does not exist. Action: None |
| ORA-02442 ORA-02442, 00000, “Cannot drop nonexistent unique key” Cause: alter table drop unique (<col list>) – unique specification does not exist. Action: make sure column list for unique constraint is correct. |
| ORA-02443 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 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 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 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 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 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 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”; |
| ORA-02450 ORA-02450, 00000, “Invalid hash option – missing keyword IS” Cause: Missing IS keyword. Action: Specify HASH IS option. |
| ORA-02451 ORA-02451, 00000, “duplicate HASHKEYS specification” Cause: The HASHKEYS option is specified more than once. Action: Only specify the HASHKEYS option once. |
| ORA-02452 ORA-02452, 00000, “invalid HASHKEYS option value” Cause: The specified HASHKEYS option must be an integer value. Action: Specify an appropriate value. |
| ORA-02453 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02466, 00000, “The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.” Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created. Action: Do not specify this option. |
| ORA-02467 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 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 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 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 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 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 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 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 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. |
| ORA-02476 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 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 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 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. |
| ORA-02481 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 ORA-02482, 00000, “Syntax error in event specification (%s)” Cause: Illegal event string Action: Enter a legal event string |
| ORA-02483 ORA-02483, 00000, “Syntax error in process specification (%s)” Cause: Illegal process string Action: Enter a legal process string |
| ORA-02484 ORA-02484, 00000, “Invalid _trace_buffers parameter specification (%s)” Cause: Bad process or size in _trace_buffers INIT.ORA parameter. Action: |
| ORA-02485 ORA-02485, 00000, “Invalid _trace_options parameter specification (%s)” Cause: Bad syntax for _trace_options INIT.ORA parameter. Action: |
| ORA-02486 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. |
| ORA-02487 ORA-02487, 00000, “Error in converting trace data” Cause: Incompatible binary trace data was specified. Action: Check the format of the input data. |
| ORA-02488 ORA-02488, 00000, “Error encountered when accessing file [%s] for trace conversion” Cause: An attempt was made to open or access the trace file during a trace conversion. Action: Check the permissions for both input and output files. Also, check the file compatibility for the trace conversion. |
| ORA-02490 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 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 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 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 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 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. |
| ORA-02700 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02750, 00000, “osnfsmmap: cannot open shared memory file ?/dbs/ftt_<pid>.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 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 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 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 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 ORA-02755, 00000, “osnfsmcre: cannot create chared memory file ?/dbs/ftt_<pid>.dbf” Cause: The Fast driver failed to create a file for shared memory. Action: Check the permissions on the directory ?/dbs |
| ORA-02756 ORA-02756, 00000, “osnfsmnam: name translation failure” Cause: The Fast driver encountered an error translating the shared // memory filename ?/dbs/ftt_<pid>.dbf. Action: Contact your customer support representative. |
| ORA-02757 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. |
| ORA-02758 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02771, 00000, “Illegal request time out value” Cause: The number was not a positive number. Action: Use a positive number. |
| ORA-02772 ORA-02772, 00000, “Invalid maximum server idle time” Cause: The time given was not a positive number. Action: Use a positive number. |
| ORA-02773 ORA-02773, 00000, “Invalid maximum client wait time” Cause: The time given was not a positive number. Action: Use a positive number. |
| ORA-02774 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 ORA-02775, 00000, “Invalid request done signal” Cause: The signal number was not a positive number. Action: Use a positive number. |
| ORA-02776 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 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 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 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 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 ORA-02781, 00000, “Invalid value given for the timing wanted flag” Cause: The value given was not TRUE or FALSE. Action: |
| ORA-02782 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 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 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 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 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 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 ORA-02788, 00000, “Unable to find kernel process pointer in async process array” Cause: Internal error – Contact ORACLE support. Action: |
| ORA-02789 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02801, 00000, “Operations timed out” Cause: Some asynchronous operations timed out in kernel mode. Action: Internal error – contact ORACLE support. |
| ORA-02802 ORA-02802, 00000, “No idle servers available in parallel mode” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02803 ORA-02803, 00000, “Retrieval of current time failed” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02804 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 ORA-02805, 00000, “Unable to set handler for SIGTPA” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02806 ORA-02806, 00000, “Unable to set handler for SIGALRM” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02807 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 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 ORA-02809, 00000, “Jump buffer not valid” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02810 ORA-02810, 00000, “Unable to make temporary file name for memory mapped file” Cause: Action: |
| ORA-02811 ORA-02811, 00000, “Unable to attach shared memory segment” Cause: Action: |
| ORA-02812 ORA-02812, 00000, “Bad attach address” Cause: Action: |
| ORA-02813 ORA-02813, 00000, “Unable to make temporary file name in order to get key” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02814 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 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 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 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 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 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 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 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 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 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 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 ORA-02825, 00000, “Request on free list was not free” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02826 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 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 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 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 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 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 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 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 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 ORA-02835, 00000, “Server unable to send signal to client” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02836 ORA-02836, 00000, “Unable to create temporary key file” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02837 ORA-02837, 00000, “Unable to unlink temporary file” Cause: Internal error. Action: Contact ORACLE support. |
| ORA-02838 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-02851, 00000, “Request list is empty when it should not be” Cause: This is an internal problem. Action: Contact ORACLE support. |
| ORA-02852 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 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 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-02855 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. |
| ORA-02875 ORA-02875, 00000, “smpini: Unable to get shared memory for PGA” Cause: Stated in errno. Action: Resolve the problem. |
| ORA-02876 ORA-02876, 00000, “smpini: Unable to attach to shared memory for PGA” Cause: Stated in errno. Action: Resolve the problem. |
| ORA-02877 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 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 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 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 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 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 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. |
| ORA-03001 ORA-03001, 00000, “unimplemented feature” Cause: This feature is not implemented. Action: None. |
| ORA-03002 ORA-03002, 00000, “operator not implemented” Cause: This is an internal error. Action: Contact your customer support representative. |
| ORA-03007 ORA-03007, 00000, “obsolete feature” Cause: User attempted to use a feature which is no longer supported. Action: None. |
| ORA-03009 ORA-03009, 00000, “Incompatible OCI function call” Cause: An incompatible OCI function call was issued for new functionality. Action: Do not use V7 OCI calls for this functionality. |
| ORA-03100 ORA-03100, 00000, “communication area cannot be allocated; insufficient memory” Cause: Action: |
| ORA-03105 ORA-03105, 00000, “internal protocol error” Cause: Action: |
| ORA-03106 ORA-03106, 00000, “fatal two-task communication protocol error” Cause: Action: |
| ORA-03107 ORA-03107, 00000, “oranet buffer underflow” Cause: Action: |
| ORA-03108 ORA-03108, 00000, “oranet: ORACLE does not support this interface version” Cause: Action: |
| ORA-03109 ORA-03109, 00000, “oranet buffer overflow” Cause: Action: |
| ORA-03110 ORA-03110, 00000, “oranet: ORACLE does not support this SQL version” Cause: Action: |
| ORA-03111 ORA-03111, 00000, “break received on communication channel” Cause: Action: |
| ORA-03112 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 ORA-03113, 00000, “end-of-file on communication channel” Cause: The connection between Client and Server process was broken. Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time. |
| ORA-03114 ORA-03114, 00000, “not connected to ORACLE” Cause: Action: |
| ORA-03115 ORA-03115, 00000, “unsupported network datatype or representation” Cause: Action: |
| ORA-03116 ORA-03116, 00000, “invalid buffer length passed to a conversion routine” Cause: Action: |
| ORA-03117 ORA-03117, 00000, “two-task save area overflow” Cause: Action: |
| ORA-03118 ORA-03118, 00000, “two-task coroutine has invalid state” Cause: Action: |
| ORA-03119 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 ORA-03120, 00000, “two-task conversion routine: integer overflow” Cause: Action: |
| ORA-03121 ORA-03121, 00000, “no interface driver connected – function not performed” Cause: Action: |
| ORA-03122 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 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 ORA-03124, 00000, “two-task internal error” Cause: Internal error. Action: Contact your customer support representative. |
| ORA-03125 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 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 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 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 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 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 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 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. |
| ORA-03133 ORA-03133, 00000, “piggyback function error” Document: NO Cause: Piggyback function has returned an error. This is an internal error. Action: |
| ORA-03134 ORA-03134, 00000, “Connections to this server version are no longer supported.” Cause: An attempt was made to connect to an Oracle server of older version. Action: Please refer to documentation for more details. |
| ORA-03135 ORA-03135, 00000, “connection lost contact” Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection. Action: 1) Check if the server session was terminated. 2) Check if the timeout parameters are set properly in sqlnet.ora. |
| ORA-03136 ORA-03136, 00000, “inbound connection timed out” Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary. |
| ORA-03137 ORA-03137, 00000, “TTC protocol internal error : [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]” Cause: TTC protocol internal error. Action: Contact Oracle Support Services. |
| ORA-03138 ORA-03138, 00000, “Connection terminated due to security policy violation” Cause: Connection was terminated due to a security policy violation. Action: Contact the Database Administrator |
| ORA-03139 ORA-03139, 00000, “This OCI call has been disabled by the DBA” Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled. Action: Contact the Database Administrator |
| ORA-03140 ORA-03140, 00000, “I/O operation in progress” Cause: The current I/O operation was not complete. The error is typically returned from vectored and/or asynchronous I/O calls. Action: Perform the necessary operation to complete or abort the current I/O. |
| ORA-03141 ORA-03141, 00000, “I/O request queue full” Cause: The I/O request queue was full and no more requests could be queued. Action: Perform the proper operations to complete part or all of the current in-progress I/O requests. |
| ORA-03142 ORA-03142, 00000, “Session ID: %ld Serial number: %ld” Cause: Connection was lost for the specified session and serial number. This is either due to session being killed or network problems. Action: Reconnect and if error persists, contact Oracle Support Services. |
| ORA-03143 ORA-03143, 00000, “Process ID: %s Thread ID: %s” Cause: Connection was lost for the specified process ID and thread ID. This is either due to session being killed or network problems. Action: Reconnect and if error persists, contact Oracle Support Services. |
| ORA-03144 ORA-03144, 00000, “Process ID: %s” Cause: Connection was lost for the specified process ID. This is either due to session being killed or network problems. Action: Reconnect and if error persists, contact Oracle Support Services. |
| ORA-03145 ORA-03145, 00000, “I/O streaming direction error” Cause: Attempted to PUT data when GET streaming was in progress or attempted to GET data when PUT streaming was in progress. Action: Complete current stream read or write I/O before attempting I/O in reverse direction. |
| ORA-03146 ORA-03146, 00000, “Invalid buffer length for TTC field” Cause: A corrupt Two-Task Common (TTC) packet was received. Action: This is a internal protocol error. Contact Oracle Support Services. |
| ORA-03160 ORA-03160, 00000, “An invalid client operation was requested by the server” Cause: You are using an Oracle client application linked with libraries with lower version than the current server version. Action: Upgrade client libraries to be same as or higher than the server version. |
| ORA-03170 ORA-03170, 00000, “deadlocked on readable physical standby (undo segment %s)” Cause: A new undo segment was added. A query can occasionally deadlock when issued around the time an undo segment is added and used immediately on the primary. Action: Retry the query. Avoid creating new undo segments when using standby as a regular part of operation. |
| ORA-03171 ORA-03171, 00000, “Recovery was terminated during query execution” Cause: Recovery was terminated. A query can ocassionally deadlock when recovery is terminated because it needs a block with changes that are made after the point at which recovery was terminated. Action: Retry the query. Avoid cancelling recovery on standby. |
| ORA-03200 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-03216, 00000, “Tablespace/Segment Verification cannot proceed” Cause: Corruptions detected during verification whch cannot be dealt with Action: Do manual verification |
| ORA-03217 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 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 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 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 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-03222 ORA-03222, 00000, “average row size and row count must be greater than zero” Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information. Action: Check the row size parameter in dbms_space.create_table_cost(). For explain plan, make sure statistics have been computed for all source tables in the CREATE TABLE AS SELECT statement. |
| ORA-03230 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 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-03233 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 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 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 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 ORA-03237, 00000, “Initial Extent of specified size cannot be allocated in tablespace (%s)” 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 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 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. |
| ORA-03240 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 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 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 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 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 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 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 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 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 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-03250 ORA-03250, 00000, “Cannot mark this segment corrupt” Cause: This segment cannot be marked corrupt because it contains data dictionary objects Action: Check the segment information and reissue the command. |
| ORA-03251 ORA-03251, 00000, “Cannot issue this command on SYSTEM tablespace ” Cause: It is not permitted to migrate SYSTEM tablespace from locally managed format to dictionary managed format or relocate bitmaps. Action: Check the tablespace name and procedure name |
| ORA-03252 ORA-03252, 00000, “initial extent size not enough for LOB segment” Cause: Fatblock size of LOB segment is too big to fit into the initial extent. Action: Specify a smaller fatblock size or create the LOB segment in other tablespaces with bigger initial extent size. |
| ORA-03254 ORA-03254, 00000, “unable to execute the sql in read only database” Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only. Action: Open the database read write, allow dead transaction recovery to complete and then open the database read only. |
| ORA-03261 ORA-03261, 00000, “the tablespace %s has only one file” Cause: Dropping file from ts which has a single file extent. Action: Cannot make a tablespace fileless |
| ORA-03262 ORA-03262, 00000, “the file is non-empty” Cause: Trying to drop a non-empty datafile Action: Cannot drop a non empty datafile |
| ORA-03263 ORA-03263, 00000, “cannot drop the first file of tablespace %s” Cause: Trying to drop the first datafile with which ts is created Action: Cannot drop the first datafile with which ts is created |
| ORA-03264 ORA-03264, 00000, “cannot drop offline datafile of locally managed tablespace” Cause: Trying to drop offline datafile in lmts Action: Try to drop file afetr making it online |
| ORA-03274 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 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 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 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 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 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 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 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 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 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 ORA-03284, 00000, “datafile or tempfile %s is not a member of tablespace %s” MERGE: 2384 RENUMBERED TO 3284 Cause: The specified datafile or tempfile did not belong to the tablespace that the object resides in. Action: Retry the option with the correct datafile or tempfile. |
| ORA-03286 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 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 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 |
| ORA-03289 ORA-03289, 00000, “partition name and segment type do not match” Cause: Partition name and segment type specified for space analysis do not match Action: Specify type PARTITION if the object is partitioned, specify SUBPARTITION if the object is composite |
| ORA-03290 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 ORA-03291, 00000, “Invalid truncate option – missing STORAGE keyword” Cause: Expected STORAGE keyword Action: Either specify DROP STORAGE or REUSE STORAGE |
| ORA-03292 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 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. |
| ORA-03296 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 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 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 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. |
| ORA-04000 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-04016, 00000, “sequence %s no longer exists” Cause: sequence was dropped while processing its next value. Action: re-create the sequence |
| ORA-04017 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-04020 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 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 occurred. Action: Retry the operation later. |
| ORA-04022 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-04023 ORA-04023, 00000, “Object %s%s%s%s%s could not be validated or authorized” Cause: A number of attempts were made to validate or authorize an object but failed. Action: Please report this error to Oracle Support Services. |
| ORA-04024 ORA-04024, 00000, “self-deadlock detected while trying to mutex pin cursor %s” Cause: While trying to mutex pin a cursor, a self-deadlock is detected. Action: Retry the operation later. |
| ORA-04027 ORA-04027, 00000, “self-deadlock during automatic validation for object %s.%s” Cause: An attempt was made to validate an invalidated object but it failed because of a self-deadlock. Action: Identify the root cause of the self-deadlock and take corrective action, e.g. compile the invalidated object separately. |
| ORA-04028 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 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. |
| ORA-04030 ORA-04030, 00000, “out of process memory when trying to allocate %s bytes (%s,%s)” Cause: Operating system process private memory was exhausted. Action: |
| ORA-04031 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 initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE. |
| ORA-04032 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 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. |
| ORA-04034 ORA-04034, 00000, “unable to shrink pool to specified size” Cause: The pool could not shrink to the specified size as it could not free memory. Action: Specify a larger value to which to shrink the pool to. |
| ORA-04035 ORA-04035, 00000, “unable to allocate %s bytes of shared memory in shared object cache \”%s\” of size \”%s\”" Cause: More shared memory is needed than was allocated in the shared object cache. Action: |
| ORA-04041 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 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 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 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 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 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 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 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 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 ORA-04052, 00000, “error occurred when looking up remote object %s%s%s%s%s” Cause: An error occurred when trying to look up a remote object. Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to create necessary views used for querying or looking up objects stored in the database. |
| ORA-04053 ORA-04053, 00000, “error occurred when validating remote object %s%s%s%s%s” Cause: An error occurred when trying to validate a remote object. Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to create necessary views used for querying or looking up objects stored in the database. |
| ORA-04054 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 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). |
| ORA-04060 ORA-04060, 00000, “insufficient privileges to execute %s” Cause: Attempt to execute a stored procedure without sufficient privileges. Action: Get necessary privileges. |
| ORA-04061 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 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 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 ORA-04064, 00000, “not executed, invalidated %s” Cause: Attempt to execute a stored procedure that has been invalidated. Action: Recompile it. |
| ORA-04065 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 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 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 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. |
| ORA-04069 ORA-04069, 00000, “cannot drop or replace a library with table dependents” Cause: An attempt was made to drop or replace a library that has dependents. There could be a table which depends on type which depends on the library being dropped. Action: Drop all table(s) depending on the type, then retry. |
| ORA-04070 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 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 ORA-04072, 00000, “invalid trigger type” Cause: An invalid trigger type was given. Action: Specify either INSERT, UPDATE or DELETE. |
| ORA-04073 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 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 ORA-04075, 00000, “invalid trigger action” Cause: An statement was given for the trigger action. Action: Re-specify the trigger action. |
| ORA-04076 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 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 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 ORA-04079, 00000, “invalid trigger specification” Cause: The create TRIGGER statement is invalid. Action: Check the statement for correct syntax. |
| ORA-04080 ORA-04080, 00000, “trigger ‘%s’ does not exist” Cause: The TRIGGER name is invalid. Action: Check the trigger name. |
| ORA-04081 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-04930 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 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 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 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 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 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 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-04941 ORA-04941, 00000, “required operating system patch needs to be applied” Cause: The operating system could not return the start time of a process. Action: Check that the operating system kernel has been patched to return process start time. Apply the required operating system patch and restart the instance. |
| ORA-06000 ORA-06000, 00000, “NETASY: port open failure” Cause: Autologin unable to open port Action: Check log file for OS-specific error code |
| ORA-06001 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 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 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 ORA-06004, 00000, “NETASY: dialogue file open failure” Cause: Autologin unable to open dialogue file Action: Check connect string for accuracy/typos |
| ORA-06005 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 ORA-06006, 00000, “NETASY: dialogue execute failure” Cause: Expected response never received Action: None |
| ORA-06007 ORA-06007, 00000, “NETASY: bad dialogue format” Cause: Dialogue file contains syntax error Action: Correct the dialogue file |
| ORA-06009 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 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 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 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 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 ORA-06019, 00000, “NETASY: invalid login (connect) string” Cause: Syntax error in login string. Action: Resubmit with correct string. |
| ORA-06020 ORA-06020, 00000, “NETASY: initialisation failure” Cause: Async driver unable to complete initialisation Action: Check log file for OS-specific error code |
| ORA-06021 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 ORA-06022, 00000, “NETASY: channel open failure” Cause: no free channel [should never happen] Action: Contact your customer support representative. |
| ORA-06023 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 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 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 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 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 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 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. |
| ORA-06030 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 ORA-06031, 00000, “NETDNT: connect failed, unrecognized object name” Cause: Host string contains reference to object (which doesn’t exist): @d:<node>-<obj> => object is ORDN<obj>; when <node> is VMS, the object is ORDN<obj>.COM when <node> is UNIX, the object is ORDN<obj> @d:<node>::”task=<obj>” => object is <obj>; when <node> is VMS, the object is <obj>.COM when <node> is UNIX, the object is <obj> Action: Retry with correct object name or create the required object on host node |
| ORA-06032 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 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 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 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 ORA-06036, 00000, “NETDNT: connect failed, no response from object” Cause: Action: |
| ORA-06037 ORA-06037, 00000, “NETDNT: connect failed, node unreachable” Cause: Host node is down. Action: Contact your network administrator. |
| ORA-06038 ORA-06038, 00000, “NETDNT: connect failed, network driver not loaded” Cause: Action: |
| ORA-06039 ORA-06039, 00000, “NETDNT: connect failed” Cause: Connect failed for unexpected reason (see OSD error). Action: Contact your customer support representative. |
| ORA-06040 ORA-06040, 00000, “NETDNT: invalid login (connect) string” Cause: Syntax error in login string. Action: Resubmit with correct string. |
| ORA-06041 ORA-06041, 00000, “NETDNT: disconnect failed” Cause: Driver gets error while doing network close operation Action: Contact your customer support representative. |
| ORA-06042 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 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 ORA-06044, 00000, “NETDNT: connect failed, byte count quota exceeded” Cause: Connect failed because of insufficient byte count quota. Action: Increase byte count quota. |
| ORA-06102 ORA-06102, 00000, “NETTCP: cannot allocate context area” Cause: Insufficient dynamic memory available for connection context area. Action: Contact your customer support representative. |
| ORA-06105 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 ORA-06106, 00000, “NETTCP: socket creation failure” Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. |
| ORA-06107 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 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 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 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 ORA-06111, 00000, “NETTCP: disconnect failure” Cause: Error occurred while closing a socket. Action: Contact your customer support representative. |
| ORA-06112 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 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 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 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 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 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 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 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 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 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 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 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 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 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_<SID>.OUT Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative. |
| ORA-06126 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-06140 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 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 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 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 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 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. |
| ORA-06200 ORA-06200, 00000, “TWOTASK: connect failed, can’t create mailbox” Cause: Action: |
| ORA-06201 ORA-06201, 00000, “TWOTASK: connect failed, can’t attach to mailbox” Cause: Action: |
| ORA-06202 ORA-06202, 00000, “TWOTASK: connect failed, can’t spawn ORASRV process” Cause: Action: |
| ORA-06203 ORA-06203, 00000, “TWOTASK: connect failed, handshake failure” Cause: Action: |
| ORA-06204 ORA-06204, 00000, “TWOTASK: connect failed, can’t access ORASRV2.COM” Cause: Action: |
| ORA-06205 ORA-06205, 00000, “TWOTASK: connect failed, can’t create logical name” Cause: Action: |
| ORA-06206 ORA-06206, 00000, “TWOTASK: message receive failure” Cause: Action: |
| ORA-06207 ORA-06207, 00000, “TWOTASK: message send failure” Cause: Action: |
| ORA-06208 ORA-06208, 00000, “TWOTASK: invalid login (connect) string” Cause: Action: |
| ORA-06209 ORA-06209, 00000, “TWOTASK: connect failed, mailbox already exists” Cause: Action: |
| ORA-06210 ORA-06210, 00000, “TWOTASK: connect failed, ORASRV exited unexpectedly” Cause: Action: |
| ORA-06211 ORA-06211, 00000, “TWOTASK: connect failed, timeout waiting for ORASRV” Cause: Action: |
| ORA-06212 ORA-06212, 00000, “TWOTASK: connect failed, logical name table is full” Cause: Action: |
| ORA-06213 ORA-06213, 00000, “TWOTASK: connect failed” Cause: Action: |
| ORA-06214 ORA-06214, 00000, “TWOTASK: connect failed, insufficient quotas to create ORASRV” Cause: Action: |
| ORA-06215 ORA-06215, 00000, “TWOTASK: connect failed, ORASRV protected image not installed” Cause: Action: |
| ORA-06216 ORA-06216, 00000, “TWOTASK: connect failed, can’t find ORASRV image file” Cause: Action: |
| ORA-06250 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-06300 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 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 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 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 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 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 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 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 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 ORA-06309, 00000, “IPA: No message queue available” Cause: The SQL*Net IPA servers have not been started. Action: Run ipactl. |
| ORA-06310 ORA-06310, 00000, “IPA: Environment variable(s) not set” Cause: Environment variable(s) not set correctly. Action: Check and correct. |
| ORA-06311 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 ORA-06312, 00000, “IPA: Incorrect outgoing service name supplied” Cause: Incorrect outgoing service name supplied. Action: Check and correct the service name. |
| ORA-06313 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 ORA-06314, 00000, “IPA: Event set up failure” Cause: Fatal interprocess communication error. Action: Contact your system manager. |
| ORA-06315 ORA-06315, 00000, “IPA: Invalid connect string” Cause: The connect string is malformed. Action: Check and correct. |
| ORA-06316 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 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 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 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 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 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 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 ORA-06323, 00000, “IPA: Cause event error” Cause: Fatal interprocess communication error. Action: Contact your system manager. |
| ORA-06400 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 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 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 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 ORA-06404, 00000, “NETCMN: invalid login (connect) string” Cause: Syntax error in login string. Action: Correct string and re-submit. |
| ORA-06405 ORA-06405, 00000, “NETCMN: reset protocol error” Cause: Unable to reset out of break state. Action: Contact your customer support representative. |
| ORA-06406 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 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 ORA-06408, 00000, “NETCMN: incorrect message format” Cause: Message from partner contains bad header. Action: Contact your customer support representative. |
| ORA-06413 ORA-06413, 00000, “Connection not open.” Cause: Unable to establish connection. Action: Use diagnostic procedures to ascertain exact problem. |
| ORA-06416 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. |
| ORA-06419 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 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 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 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 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. |
| ORA-06430 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-06500 ORA-06500, 00000, “PL/SQL: storage error” Cause: PL/SQL was unable to allocate additional storage. This message normally appears with an ORA-4030 or ORA-4031 error which gives additional information. Sometimes this error can be caused by runaway programs. Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are causing excessive amounts of memory to be used. 2) Programmatically cause unused objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or process memory (as appropriate) available to you. |
| ORA-06501 ORA-06501, 00000, “PL/SQL: program error” Cause: This is an internal error message. An error has been detected in a PL/SQL program. Action: Contact Oracle Support Services. |
| ORA-06502 ORA-06502, 00000, “PL/SQL: numeric or value error%s” Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2). Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints. |
| ORA-06503 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 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 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 ORA-06508, 00000, “PL/SQL: could not find program unit being called%s” Cause: Action: |
| ORA-06509 ORA-06509, 00000, “PL/SQL: ICD vector missing for this package” Cause: Action: |
| ORA-06510 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-06534, 00000, “Cannot access Serially Reusable package %s” Cause: The program attempted to access a Serially Reusable package in PL/SQL called from SQL context (trigger or otherwise). Such an access is currently unsupported. Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in PL/SQL called from sql context (trigger or otherwise). // |
| ORA-06535 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 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 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 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 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 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 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 ORA-06542, 00000, “PL/SQL: execution error” Currently unused. Reserved for future use. // |
| ORA-06543 ORA-06543, 00000, “PL/SQL: execution error – execution aborted” // // |
| ORA-06544 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 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 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 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 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 ORA-06549, 00000, “PL/SQL: failed to dynamically open shared object (DLL): %s:%s” Cause: One possible cause might be there are too many DLLs open at the same time. Action: // //——————————————————– // |
| ORA-06550 ORA-06550, 00000, “line %s, column %s:\n%s” Cause: Usually a PL/SQL compilation error. Action: |
| ORA-06551 ORA-06551, 00000, “PL/SQL: Unhandled exception” Cause: Action: |
| ORA-06552 ORA-06552, 00000, “PL/SQL: %s” Cause: Action: |
| ORA-06553 ORA-06553, 00000, “PLS-%s: %s” Cause: Action: |
| ORA-06554 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-06570, 00000, “shared pool object does not exist, cannot be pinned/purged” Cause: The specified shared pool shared cursor could not be found, therefore it cannot be pinned/purged. 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. |
| ORA-06571 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 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 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 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 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 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 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 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-06579 ORA-06579, 00000, ” Bind variable not big enough to hold the output value” Cause: The bind variable specified by the user is not large enough to hold the output returned by the function or a procedure. Action: Specify a bind variable of larger size. |
| ORA-06580 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. |
| ORA-06592 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. |
| ORA-06593 ORA-06593, 00000, “%s is not supported with natively compiled PL/SQL modules” Cause: Specified feature is not yet supported for natively compiled PL/SQL modules yet. Action: Recompile the relevant PL/SQL modules in non-native mode by setting the parameter plsql_compiler_flags to INTERPRETED. |
| ORA-06594 ORA-06594, 00000, “ICD is unable to compute a result” Document: NO Cause: This exception is internal to PL/SQL, and should not be seen by customers. Action: Contact Oracle Support Services. |
| ORA-06595 ORA-06595, 00000, “REF CURSOR parameters are not supported in forwarded RPC calls” Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR parameter. Action: Either call the remote function directly (i.e., not by way of forwarding), or move the remote function to a database where it can be called directly. |
| ORA-06596 ORA-06596, 00000, “object cannot be purged, object is permanently kept in shared pool” Cause: The specified object was permanently kept, therefore, cannot be purged. Action: Use DBMS_SHARED_POOL.UNKEEP procedure to unkeep the object and then purge it. |
| ORA-06600 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 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 ORA-06602, 00000, “LU6.2 Driver: Error allocating context area” Cause: Context area failure. Action: Contact your local service representative. |
| ORA-06603 ORA-06603, 00000, “LU6.2 Driver: Error allocating memory” Cause: Operating system refused request for memory. Action: Contact you local service representative. |
| ORA-06604 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 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 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 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 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. |
| ORA-06610 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 ORA-06611, 00000, “LU6.2 Driver: Request to send error” Cause: Action: |
| ORA-06612 ORA-06612, 00000, “LU6.2 Driver: Send data error” Cause: Action: |
| ORA-06613 ORA-06613, 00000, “LU6.2 Driver: Receive and wait error” Cause: Action: |
| ORA-06614 ORA-06614, 00000, “LU6.2 Driver: Receive Immediate error” Cause: Action: |
| ORA-06615 ORA-06615, 00000, “LU6.2 Driver: Send error” Cause: Action: |
| ORA-06616 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 ORA-06617, 00000, “LU6.2 Driver: Attach to PU failed” Cause: Action: |
| ORA-06618 ORA-06618, 00000, “LU6.2 Driver: Activation of subnetwork failed” Cause: Action: |
| ORA-06619 ORA-06619, 00000, “LU6.2 Driver: Unable to activate remote partner” Cause: Action: |
| ORA-06620 ORA-06620, 00000, “LU6.2 Driver: Invalid remote partner” Cause: Action: |
| ORA-06621 ORA-06621, 00000, “LU6.2 Driver: Allocation error” Cause: Action: |
| ORA-06622 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. |
| ORA-06700 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-06900 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 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 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 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 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 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 ORA-06906, 00000, “CMX: cannot get maximum packet size from CMX” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06907 ORA-06907, 00000, “CMX: error during connect confirmation” Cause: remote partner aborted Action: contact your customer support representative |
| ORA-06908 ORA-06908, 00000, “CMX: error during transfer of ORACLE_SID” Cause: remote partner aborted Action: contact your customer support representative |
| ORA-06909 ORA-06909, 00000, “CMX: error during acknowledge of ORACLE_SID” Cause: remote partner aborted Action: contact your customer support representative |
| ORA-06910 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 ORA-06911, 00000, “CMX: t_event returns ERROR” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06912 ORA-06912, 00000, “CMX: write error in datarq” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06913 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 ORA-06914, 00000, “CMX: unexepected event during start of oracle” Cause: connect sequence out of sync Action: contact your customer support representative |
| ORA-06915 ORA-06915, 00000, “CMX: unknown t_event in datarq” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06916 ORA-06916, 00000, “CMX: error in data read (t_datain)” Cause: remote partner aborted Action: contact your customer support representative |
| ORA-06917 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 ORA-06918, 00000, “CMX: T_NOEVENT during wait for read event” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06919 ORA-06919, 00000, “CMX: error during write request (unknown event)” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06920 ORA-06920, 00000, “CMX: getbrkmsg illegal datatype” Cause: received packets are corrupted Action: contact your customer support representative |
| ORA-06921 ORA-06921, 00000, “CMX: getdatmsg illegal datatype” Cause: received packets are corrupted Action: contact your customer support representative |
| ORA-06922 ORA-06922, 00000, “CMX: bad write length” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06923 ORA-06923, 00000, “CMX: illegal break condition” Cause: break handling out of sync Action: contact your customer support representative |
| ORA-06924 ORA-06924, 00000, “CMX: wrong break message length” Cause: received packets are corrupted Action: contact your customer support representative |
| ORA-06925 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 ORA-06926, 00000, “CMX: T_ERROR during read data” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06927 ORA-06927, 00000, “CMX: T_DATAIN received before all data written” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06928 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 ORA-06929, 00000, “CMX: error when sending ORACLE_SID” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06930 ORA-06930, 00000, “CMX: error when checking ORACLE_SID” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06931 ORA-06931, 00000, “CMX: error during read_properties for server” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06932 ORA-06932, 00000, “CMX: error in local name” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06933 ORA-06933, 00000, “CMX: error during attach” Cause: internal error in CMX Action: contact your customer support representative |
| ORA-06950 ORA-06950, 00000, “No error” Cause: SQL*Net AppleTalk error codes base. This is not an error. Action: None. |
| ORA-06951 ORA-06951, 00000, “Operating system call error” Cause: AppleTalk API received error in VMS system service. Action: Contact Oracle Customer Support representative. |
| ORA-06952 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 ORA-06953, 00000, “Not enough virtual memory” Cause: Not enough memory available. Action: Check VMS process quotas and/or sysgen parameters |
| ORA-06954 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 ORA-06955, 00000, “Number of database servers exceed limit” Cause: Too many database connections. Action: Check ATKSRV_MAXCONparameter in configuration file. |
| ORA-06956 ORA-06956, 00000, “Failed to get local host name” Cause: Unable to get Appletalk host name. Action: Check Appletalk configuration. |
| ORA-06957 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 ORA-06958, 00000, “Failed to access configuration file” Cause: Unable to access CONFIG.ATK Action: Check file protections. |
| ORA-06959 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 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 ORA-06961, 00000, “Insufficient privilege for attempted operation” Cause: Action: Check process privileges and retry. |
| ORA-06970 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 ORA-06971, 00000, “X.25 Driver: error while receiving data” Cause: Action: |
| ORA-06972 ORA-06972, 00000, “X.25 Driver: error while sending data” Cause: Action: |
| ORA-06973 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 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 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 ORA-06976, 00000, “X.25 Driver: endpoint creation failure” Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. |
| ORA-06977 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 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 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. |
| ORA-07200 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 ORA-07201, 00000, “slhom: oracle_home variable not set in environment.” Cause: $(ORACLE_HOME) environment variable not set. Action: Set ORACLE_HOME. |
| ORA-07202 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07218, 00000, “slkhst: could not perform host operation” Cause: Unix system() call failed Action: Examine system error message |
| ORA-07219 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07232, 00000, “slemcc: fclose error.” Cause: An error was encountered when closing the file. Possible OS error. Action: Contact system administator. |
| ORA-07233 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 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 ORA-07235, 00000, “slemcw: fwrite error.” Cause: Unable to write item to file. Possible OS error. Possible permissions problem. Action: Retry operation. |
| ORA-07236 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 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 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 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 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 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 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 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 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 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 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 ORA-07247, 00000, “skgfrfms, skgfrnms: read error, unable to read block from database file” Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS. Action: Check errno. |
| ORA-07248 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 ORA-07249, 00000, “slsget: open error, unable to open /proc/pid.” Cause: The open() system call returned an error. Action: Check that /proc has the right permissions. |
| ORA-07250 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 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 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 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 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 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 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 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 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 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 ORA-07260, 00000, “spdcr: wait error.” Cause: Wait system call returned an error. Action: Check errno. |
| ORA-07261 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 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 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 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 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 ORA-07266, 00000, “sppst: invalid process number passed to sppst.” Cause: Function was passed an invalid oracle process id. Action: Internal error. |
| ORA-07267 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 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 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 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 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 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 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 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 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 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 ORA-07277, 00000, “spdde: illegal pid passed as argument.” Cause: A 0 pid was passed to spdde. Action: Internal error. . |
| ORA-07278 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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-07346 ORA-07346, 00000, “slnrm: normalized file name is too long” Cause: After normalizing the specified file name, the resulting file name was too long. Action: Specify the shorter file name and retry the operation. |
| ORA-07390 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 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 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 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 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 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 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 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 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 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-07405 ORA-07405, 00000, “sptrap: cannot setup alternate signal stack.” Cause: The system failed to setup an alternate signal stack. Action: Check errno and sercose[0] for the location where it failed. |
| ORA-07406 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07440, 00000, “WMON process terminated with error” Cause: The wakeup monitor process died. Action: Warm start instance. |
| ORA-07441 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 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 ORA-07443, 00000, “function %s not found” Cause: An invalid function name was specified. Action: Use a valid function name. |
| ORA-07444 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 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 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 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 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 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 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 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 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 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 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 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-07457 ORA-07457, 00000, “cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE” Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix. Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. |
| ORA-07458 ORA-07458, 00000, “cannot set the RESOURCE_MANAGER_PLAN parameter” Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was quiesced. Action: Unquiesce the database. |
| ORA-07459 ORA-07459, 00000, “cannot restore the RESOURCE_MANAGER_PLAN parameter” Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored. Action: No action needed. |
| ORA-07460 ORA-07460, 00000, “cannot set the RESOURCE_MANAGER_PLAN parameter” Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix. Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. |
| ORA-07468 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07494, 00000, “scgcm: unexpected error.” Cause: Unknown or unexpected error code. Action: Check result code in sercerrno. Possible lock manager failure. |
| ORA-07495 ORA-07495, 00000, “spwat: lm_wait failed.” Cause: lm_wait failed. Action: Check result code in sercerrno. Possible lock manager failure. |
| ORA-07496 ORA-07496, 00000, “sppst: lm_post failed.” Cause: lm_post failed. Action: Check result code in sercerrno. Possible lock manager failure. |
| ORA-07497 ORA-07497, 00000, “sdpri: cannot create trace file ‘%s’; errno = %s.” Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic link. Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the symbolic link. |
| ORA-07498 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 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. |
| ORA-07500 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07549, 00000, “sftopn: $OPEN failure” Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation |
| ORA-07550 ORA-07550, 00000, “sftopn: $CONNECT failure” Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation |
| ORA-07551 ORA-07551, 00000, “sftcls: $CLOSE failure” Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation |
| ORA-07552 ORA-07552, 00000, “sftget: $GET failure” Cause: VMS system service $GET failed Action: Examine system error message and refer to VMS documentation |
| ORA-07561 ORA-07561, 00000, “szprv: $IDTOASC failure” Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation |
| ORA-07562 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 ORA-07563, 00000, “sldext: $PARSE failure” Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation |
| ORA-07564 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 ORA-07565, 00000, “sldext: $SEARCH failure” Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation |
| ORA-07568 ORA-07568, 00000, “slspool: $OPEN failure” Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation |
| ORA-07569 ORA-07569, 00000, “slspool: $CLOSE failure” Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation |
| ORA-07570 ORA-07570, 00000, “szrfc: $IDTOASC failure” Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation |
| ORA-07571 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 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 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 ORA-07574, 00000, “szrfc: $GETUAI failure” Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation |
| ORA-07576 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 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_<SID>_DBA or ORA_<SID>_OPER) hasn’t been created yet. Action: Add a VMS account for ORA_<SID>_DBA and/or ORA_<SID>_OPER before trying to set a password for them. |
| ORA-07578 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 ORA-07579, 00000, “spini: $DCLEXH failure” Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation |
| ORA-07580 ORA-07580, 00000, “spstp: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07581 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 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 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 ORA-07585, 00000, “spdcr: $PARSE failure” Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation |
| ORA-07586 ORA-07586, 00000, “spdcr: $SEARCH failure” Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation |
| ORA-07587 ORA-07587, 00000, “spdcr: $CREPRC failure” Cause: VMS system service $CREPRC failed Action: Examine system error message and refer to VMS documentation |
| ORA-07588 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 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 ORA-07590, 00000, “spdde: $DELPRC failure” Cause: VMS system service $DELPRC failed Action: Examine system error message and refer to VMS documentation |
| ORA-07591 ORA-07591, 00000, “spdde: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07592 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 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 ORA-07594, 00000, “spiip: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07595 ORA-07595, 00000, “sppid: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07596 ORA-07596, 00000, “sptpa: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07597 ORA-07597, 00000, “spguns: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07598 ORA-07598, 00000, “spwat: $SETIMR failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07599 ORA-07599, 00000, “spwat: $SCHDWK failure” Cause: VMS system service $SCHDWK failed Action: Examine system error message and refer to VMS documentation |
| ORA-07600 ORA-07600, 00000, “slkmnm: $GETSYIW failure” Cause: VMS system service $GETSYIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07601 ORA-07601, 00000, “spguno: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07602 ORA-07602, 00000, “spgto: $GETJPIW failure” Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation |
| ORA-07605 ORA-07605, 00000, “szprv: $ASCTOID failure” Cause: VMS system service $ASCTOID failed Action: Examine system error message and refer to VMS documentation |
| ORA-07606 ORA-07606, 00000, “szprv: $CHKPRO failure” Cause: VMS system service $CHKPRO failed Action: Examine system error message and refer to VMS documentation |
| ORA-07607 ORA-07607, 00000, “szaud: $SNDOPR failure” Cause: VMS system service $SNDOPR failed Action: Examine system error message and refer to VMS documentation |
| ORA-07608 ORA-07608, 00000, “szprv: $GETUAI failure” Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation |
| ORA-07609 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ORA-07643, 00000, “smsalo: SMSVAR is invalid” Cause: an internal error Action: Report this error to Oracle Support Services, provide your INIT.ORA file. |
| ORA-07645 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-07700 ORA-07700, 00000, “sksarch: interrupt received” Cause: An interrupt was received while archiving the logs Action: Retry operation |
| ORA-07701 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 |
| ORA-07721 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. |
| ORA-07740 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 ORA-07741, 00000, “slemop: $OPEN failure” Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation |
| ORA-07742 ORA-07742, 00000, “slemop: $CONNECT failure” Cause: VMS system service $CONNECT failed Action: Examine system error message and refer to VMS documentation |
| ORA-07743 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 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 ORA-07745, 00000, “slemcl: $CLOSE failure” Cause: VMS system service $CLOSE failed Action: Check system error and refer to VMS documentation |
| ORA-07746 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 ORA-07747, 00000, “slemrd: $READ failure” Cause: VMS system service $READ failed Action: Check system error and refer to VMS documentation |
| ORA-07750 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 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 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 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 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 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 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 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 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 ORA-07760, 00000, “slemtr: $open failure” Cause: the $open service failed. This is an internal error Action: Contact your customer support representative. |
| ORA-07800 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 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 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 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 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 |
| ORA-07820 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 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 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 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 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 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 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 |
| ORA-07840 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-07880 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. |
| ORA-08000 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 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 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 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 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 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 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-08007 ORA-08007, 00000, “Further changes to this block by this transaction not allowed” Cause: Max locks have been reached for this transaction in this block Action: Commit changes |
| ORA-08008 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 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 ORA-08101, 00000, “index key does not exist file %s: (root %s, node %s) blocks (%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 ORA-08102, 00000, “index key not found, obj# %s, file %s, block %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 ORA-08103, 00000, “object no longer exists” Cause: The object has been deleted by another user since the operation began, or a prior incomplete recovery restored the database to a point in time during the deletion of the object. Action: Delete the object if this is the result of an incomplete recovery. |
| ORA-08104 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 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 ORA-08106, 00000, “cannot create journal table %s.%s” Cause: The online index builder could not create its journal table Action: Rename the conflicting table or rerun the SQL statement. There * may be a concurrent online index rebuild on the same object. Action: rename your table in conflict or rerun the SQL statement * there may be a concurrent online index rebuild on the same object. |
| ORA-08108 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 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 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 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 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 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 ORA-08114, 00000, “can not alter a fake index” Cause: User attempted to alter a fake index Action: drop fake index |
| ORA-08115 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 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 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 |
| ORA-08118 ORA-08118, 00000, “Deferred FK constraints cannot be enforced, index too big (%s)” Cause: Deferred Foreign Key constraints cannot be enforced due to the index key being too big and built on a non-default DB_BLOCK_SIZE. Action: First try to drop the Foreign Key and then the primary key. |
| ORA-08119 ORA-08119, 00000, “The new initrans will make the index too big” Cause: Specifying the initrans need additional space to hold the index key which might make the index too big Action: Try giving a smaller initrans value |
| ORA-08120 ORA-08120, 00000, “Need to create SYS.IND_ONLINE$ table in order to (re)build index” Cause: Alter index Build/Rebuild online require existing of SYS.IND_ONLINE$ table. Action: User/DBA needs to create sys.ind_online$ before alter the index /rdbms/admin/catcio.sql contains script to create ind_online$. |
| ORA-08121 ORA-08121, 00000, “Number of indexes need to be maintained offline exceeds limit for DML” Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes for each DML statement Action: Make sure the index maintainance is online. If indexes need to be maintained offline, drop some indexes. |
| ORA-08122 ORA-08122, 00000, “Online (re)build of index rolled back due to DML conflict” Cause: The online (re)build journal is inconsistent with ongoing DML and cannot be used successfully to complete the online index (re)build. Action: Reissue the online (re)build operation, after performing any cleanup, if needed. |
| ORA-08175 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 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 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 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 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 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 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 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 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 ORA-08184, 00000, “attempting to re-enable Flashback while in Flashback mode” Cause: as stated above Action: disable first before re-enabling |
| ORA-08185 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 ORA-08186, 00000, “invalid timestamp specified” Cause: as stated above Action: enter a valid timestamp |
| ORA-08187 ORA-08187, 00000, “snapshot expression not allowed here” Cause: A snapshot expression using AS OF was specified when not allowed. Action: Do not use the AS OF clause |
| ORA-08189 ORA-08189, 00000, “cannot flashback the table because row movement is not enabled” Cause: An attempt was made to perform Flashback Table operation on a table for which row movement has not been enabled. Because the Flashback Table does not preserve the rowids, it is necessary that row movement be enabled on the table. Action: Enable row movement on the table |
| ORA-08190 ORA-08190, 00000, “restore point %s is from a different incarnation of the database” Cause: An attempt was made to perform Flashback Table operation using a restore point from a different incarnation of the database Action: Provide a restore point from the current database incarnation |
| ORA-08191 ORA-08191, 00000, “Flashback Table operation is not supported on remote tables” Cause: An attempt was made to perform Flashback Table operation on a remote table. This is not permitted. Action: Do not perform a Flashback Table operation on remote tables. |
| ORA-08192 ORA-08192, 00000, “Flashback Table operation is not allowed on fixed tables” Cause: An attempt was made to perform Flashback Table operation on a fixed table. This is not permitted. Action: Do not perform a Flashback Table operation on fixed tables. |
| ORA-08193 ORA-08193, 00000, “Flashback Table operation is not allowed on temporary tables” Cause: An attempt was made to perform Flashback Table operation on a temporary table. This is not permitted. Action: Do not perform a Flashback Table operation on temporary tables. |
| ORA-08194 ORA-08194, 00000, “Flashback Table operation is not allowed on materialized views” Cause: An attempt was made to perform Flashback Table operation on a materialized view. This is not permitted. Action: Do not perform a Flashback Table operation on materialized views or snapshot logs. |
| ORA-08195 ORA-08195, 00000, “Flashback Table operation is not supported on partitions” Cause: An attempt was made to perform Flashback Table operation on a partition. This is not permitted. Action: Do not perform a Flashback Table operation on partitions. |
| ORA-08196 ORA-08196, 00000, “Flashback Table operation is not allowed on AQ tables” Cause: An attempt was made to perform Flashback Table operation on AQ tables. This is not permitted. Action: Do not perform a Flashback Table operation on AQ tables. |
| ORA-08197 ORA-08197, 00000, “Flashback Table operation is not supported on clustered tables” Cause: An attempt was made to perform Flashback Table operation on a clustered table. This is not permitted. Action: Do not perform a Flashback Table operation on clustered tables. |
| ORA-08198 ORA-08198, 00000, “Flashback Table is not supported on object tables, nested tables” Cause: An attempt was made to perform Flashback Table operation on a object table or a nested table or a table with nested table column. This is not permitted. Action: Do not perform a Flashback Table operation on such tables. |
| ORA-08199 ORA-08199, 00000, “Flashback Table operation is not supported on this object” Cause: An attempt was made to perform Flashback Table operation on an object on which the operation is not supported. Action: Do not perform a Flashback Table operation on such objects. |
| ORA-08205 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 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 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 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 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 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 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 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 ORA-08232, 00000, “smsdes: cannot detach from SGA” Cause: Probably, the listener process has died. Action: Contact your customer support representative. |
| ORA-08233 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 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 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 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 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 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. |
| ORA-08243 ORA-08243, 00000, “recursive audit operation attempted” Cause: A recursive operation requiring audit was attempted in the middle of an auditing operation. The most likely reason is space management operations needed to free up space in the audit tablespace. Action: Check space in the tablespace for SYS.AUD$ and correct the problem. |
| ORA-08260 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 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. |
| ORA-08263 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 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 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 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 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 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 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. |
| ORA-08270 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 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. |
| ORA-08274 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 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 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 ORA-08277, 00000, “Cannot set environment variable” Cause: There is insufficient memory to expand the environment. Action: Reduce memory usage and retry. |
| ORA-08278 ORA-08278, 00000, “Cannot get CPU statistics” Cause: Could not retrieve CPU times because n_stat failed. Action: Contact customer support. |
| ORA-08308 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 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 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 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 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 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 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 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 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 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 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 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. |
| ORA-08320 ORA-08320, 00000, “scnget: Call to scnget before scnset or scnfnd.” Cause: An internal error Action: Contact your customer support representative. |
| ORA-08321 ORA-08321, 00000, “scnmin: NOT IMPLEMENTED YET” Cause: An internal error Action: Contact your customer support representative. |
| ORA-08322 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 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 ORA-08330, 00000, “Printing not supported” Cause: An attempt was made to automatically spool a file to the printer Action: none |
| ORA-08331 ORA-08331, 00000, “Wait operation timed out” Cause: Oracle timed out waiting for an event Action: Contact your Oracle support representative |
| ORA-08332 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. |
| ORA-08340 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 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 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 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 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. |
| ORA-08401 ORA-08401, 00000, “invalid compiler name: %s” Cause: An invalid compiler name <compname> was passed to a UTL_PG conversion routine. Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine. |
| ORA-08412 ORA-08412, 00000, “error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message” Cause: The WMSGBSIZ is the maximun size for warning message block, it is recommanded to be 1024 bytes to 8 kbytes. Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK). |
| ORA-08413 ORA-08413, 00000, “invalid compiler type in FORMAT parameter at %s” Cause: An invalid compiler type is defined in format control block. The format control block is invalid. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| ORA-08414 ORA-08414, 00000, “error encountered in %s” Cause: The function <routine> returned an error. Where <routine> may be: RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take. |
| ORA-08429 ORA-08429, 00000, “raw data has invalid digit in display type data” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| ORA-08430 ORA-08430, 00000, “raw data missing leading sign” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. Action: Correct the input raw data or the mask options so that they match. |
| ORA-08431 ORA-08431, 00000, “raw data missing zero as defined in picture” Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| ORA-08432 ORA-08432, 00000, “raw data has invalid floating point data” Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data. Action: Correct the input raw data. |
| ORA-08433 ORA-08433, 00000, “invalid picture type in convert raw to number” Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type. Action: Correct the picture mask parameter. |
| ORA-08434 ORA-08434, 00000, “raw data has invalid trailing sign” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign. Action: Correct the input raw data or the mask options so that they match. |
| ORA-08435 ORA-08435, 00000, “PICTURE MASK missing the leading sign when SIGN IS LEADING specified” Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. Action: Correct the input raw data or the mask options so that they match. |
| ORA-08436 ORA-08436, 00000, “raw data has invalid sign digit” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign. Action: Correct the input raw data or the picture mask so that they match. |
| ORA-08437 ORA-08437, 00000, “invalid picture type in picture mask” Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type. Action: Correct the picture mask parameter. |
| ORA-08440 ORA-08440, 00000, “raw buffer is too short to hold converted data” Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask. Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion. |
| ORA-08441 ORA-08441, 00000, “closed parenthesis missing in picture mask” Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine. Action: Correct the picture mask. |
| ORA-08443 ORA-08443, 00000, “syntax error in BLANK WHEN ZERO clause in mask options” Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES Action: Correct the mask options parameter. |
| ORA-08444 ORA-08444, 00000, “syntax error in JUSTIFIED clause in mask options” Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST JUST RIGHT JUSTIFIED JUSTIFIED RIGHT Action: Correct the mask options parameter. |
| ORA-08445 ORA-08445, 00000, “syntax error in SIGN clause in mask options” Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN LEADING SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING SEPARATE CHARACTER Action: Correct the mask options parameter. |
| ORA-08446 ORA-08446, 00000, “syntax error in SYNCHRONIZED clause in mask options” Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT Action: Correct the mask options parameter. |
| ORA-08447 ORA-08447, 00000, “syntax error in USAGE clause in mask options” Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4 Action: Correct the mask options parameter. |
| ORA-08448 ORA-08448, 00000, “syntax error in DECIMAL-POINT environment clause” Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA Action: Correct the environment clause parameter. |
| ORA-08449 ORA-08449, 00000, “invalid numeric symbol found in picture mask” Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine. Action: Correct the picture mask parameter. |
| ORA-08450 ORA-08450, 00000, “invalid specification of CR in picture mask” Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask. Action: Correct the picture mask parameter. |
| ORA-08451 ORA-08451, 00000, “invalid specification of DB in picture mask” Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask. Action: Correct the picture mask parameter. |
| ORA-08452 ORA-08452, 00000, “specification of E in picture mask is unsupported” Cause: The floating point exponent symbol ‘E’ was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines. Action: Correct the picture mask parameter, and the data, if necessary. |
| ORA-08453 ORA-08453, 00000, “more than one V symbol specified in picture mask” Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator (‘V’). Only one decimal point indicator is allowed in the picture mask. Action: Correct the picture mask parameter. |
| ORA-08454 ORA-08454, 00000, “more than one S symbol specified in picture mask” Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator (‘S’). Only one operational sign indicator is allowed in the picture mask. Action: Correct the picture mask parameter. |
| ORA-08455 ORA-08455, 00000, “syntax error in CURRENCY SIGN environment clause” Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign Action: Correct the environment clause parameter. |
| ORA-08456 ORA-08456, 00000, “no sign in picture mask but SIGN clause in mask options” Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol (‘S’, ‘+’, or ‘-’), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause. Action: Correct the picture mask parameter or the mask options parameter. |
| ORA-08457 ORA-08457, 00000,”syntax error in SEPARATE CHARACTER option of SIGN clause” Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE SEPARATE CHARACTER Action: Correct the mask options parameter. |
| ORA-08458 ORA-08458, 00000, “invalid format parameter” Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| ORA-08459 ORA-08459, 00000, “invalid format parameter length” Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| ORA-08460 ORA-08460, 00000, “invalid environment clause in environment parameter” Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported. Action: Correct the environment parameter. |
| ORA-08462 ORA-08462, 00000, “raw buffer contains invalid decimal data” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data. Action: Correct the input data. |
| ORA-08463 ORA-08463, 00000, “overflow converting decimal number to Oracle number” Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number. Action: Be sure that the input decimal number is valid, and besure that the output variable is large enough to hold the Oracle number value. |
| ORA-08464 ORA-08464, 00000, “input raw decimal data contains more than 42 digits” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number. Action: Correct the raw input buffer. |
| ORA-08465 ORA-08465, 00000, “input mask contains more than 32 characters” Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters. Action: Correct the mask input buffer. |
| ORA-08466 ORA-08466, 00000, “raw buffer length %s is too short for %s” Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than %s bytes long, but the picture mask parameter specified that %s bytes of input data were to be converted. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| ORA-08467 ORA-08467, 00000, “error converting Oracle number to %s” Cause: An error occurred when converting an Oracle number to a COBOL DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format. Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable. |
| ORA-08468 ORA-08468, 00000, “mask option %s is not supported” Cause: The mask option <clause> was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The <clause> can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER Action: Remove the <clause> from the mask options parameter in the PL/SQL call to UTL_PG. |
| ORA-08469 ORA-08469, 00000, “must use the SIGN IS SEPARATE clause in mask options” Cause: A signed numeric entry with DISPLAY usage was converted using a non-defaulted character set and its PICTURE character-string contains an S. In these circumstances, a SIGN IS SEPARATE clause must be specified in the mask options. Action: Either specify a valid SIGN IS SEPARATE clause in the mask options, use the defaulted character set, or don’t specify an S in the PICTURE character-string. |
| ORA-08498 ORA-08498, 00000, “Warning: picture mask ‘%s’ overrides picture mask option ‘USAGE IS %s’ to ‘USAGE IS DISPLAY’” Cause: Picture mask USAGE option was overridden by the picture mask. Action: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask. |
| ORA-08499 ORA-08499, 00000, “Warning: picture mask options ‘%s’ ignored by UTL_PG ” Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines. Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine. |
| ORA-09200 ORA-09200, 00000, “sfccf: error creating file” Cause: Could be out of disk space Action: See OSD error accompanying this message |
| ORA-09201 ORA-09201, 00000, “sfcopy: error copying file” Cause: Block sizes may not match Action: See OSD error accompanying this message |
| ORA-09202 ORA-09202, 00000, “sfifi: error identifying file” Cause: db_block_size specified in init.ora could be incorrect Action: See OSD error accompanying this message |
| ORA-09203 ORA-09203, 00000, “sfofi: error opening file” Cause: File attributes may have changed Action: See OSD error accompanying this message |
| ORA-09204 ORA-09204, 00000, “sfotf: error opening temporary file” Cause: Incorrect path may have been specified for the file Action: See OSD error accompanying this message |
| ORA-09205 ORA-09205, 00000, “sfqio: error reading or writing to disk” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09206 ORA-09206, 00000, “sfrfb: error reading from file” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09207 ORA-09207, 00000, “sfsrd: error reading from file” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09208 ORA-09208, 00000, “sftcls: error closing file” Cause: File may have been corrupted Action: See OSD error accompanying this message |
| ORA-09209 ORA-09209, 00000, “sftget: error reading from file” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09210 ORA-09210, 00000, “sftopn: error opening file” Cause: Incorrect path may have been specified for the file Action: See OSD error accompanying this message |
| ORA-09211 ORA-09211, 00000, “sfwfb: error writing to file” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09212 ORA-09212, 00000, “sfwfbmt: error writing to file” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09213 ORA-09213, 00000, “slgfn: error fabricating file name” Cause: Filename may be too long Action: See OSD error accompanying this message |
| ORA-09214 ORA-09214, 00000, “sfdone: I/O error detected” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09215 ORA-09215, 00000, “sfqio: error detected in IOCompletionRoutine” Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message |
| ORA-09216 ORA-09216, 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-09217 ORA-09217, 00000, “sfsfs: failed to resize file” Cause: Could be out of disk space Action: See OSD error accompanying this message |
| ORA-09218 ORA-09218, 00000, “sfrfs: failed to refresh file size” Cause: File may be corrupted or truncated Action: See OSD error accompanying this message |
| ORA-09240 ORA-09240, 00000, “smpalo: error allocating PGA memory” Cause: Could be out of memory Action: See OSD error accompanying this message |
| ORA-09241 ORA-09241, 00000, “smsalo: error allocating SGA memory” Cause: Could be out of memory Action: See OSD error accompanying this message |
| ORA-09242 ORA-09242, 00000, “smscre: error creating SGA” Action: See OSD error accompanying this message |
| ORA-09243 ORA-09243, 00000, “smsget: error attaching to SGA” Cause: SGA may not have been created (database not started) Action: See OSD error accompanying this message |
| ORA-09244 ORA-09244, 00000, “smprset: error setting memory protections” Action: See OSD error accompanying this message |
| ORA-09245 ORA-09245, 00000, “smcstk: error switching stacks” Action: See OSD error accompanying this message |
| ORA-09246 ORA-09246, 00000, “sfsmap: unable to map SGA” Action: See OSD error accompanying this message |
| ORA-09247 ORA-09247, 00000, “smsdes: error destroying the SGA” Action: See OSD error accompanying this message |
| ORA-09260 ORA-09260, 00000, “sigpidu: error obtaining process id” Cause: May be out of resources Action: See OSD error accompanying this message |
| ORA-09261 ORA-09261, 00000, “spdcr: error creating detached (background) process” Cause: Could be out of resources Action: See OSD error accompanying this message |
| ORA-09262 ORA-09262, 00000, “spdde: error terminating detached (background) process” Cause: Could be out of resources Action: See OSD error accompanying this message |
| ORA-09263 ORA-09263, 00000, “spini: error initializing process” Cause: Could be out of memory Action: See OSD error accompanying this message |
| ORA-09264 ORA-09264, 00000, “sptpa: error flagging process” Cause: Could be out of resources Action: See OSD error accompanying this message |
| ORA-09265 ORA-09265, 00000, “spwat: error temporarily suspending process” Cause: Could be out of resources Action: See OSD error accompanying this message |
| ORA-09266 ORA-09266, 00000, “spawn: error starting an Oracle process” Cause: Could be out memory Action: See OSD error accompanying this message |
| ORA-09270 ORA-09270, 00000, “szalloc: error allocating memory for security” Cause: Could be out of memory Action: See OSD error accompanying this message |
| ORA-09271 ORA-09271, 00000, “szlon: error verifying user name” Cause: Username may be too long Action: See OSD error accompanying this message |
| ORA-09272 ORA-09272, 00000, “remote os logon is not allowed” Cause: Remote os login attempted when not allowed. Action: See OSD error accompanying this message |
| ORA-09273 ORA-09273, 00000, “szrfc: error verifying role name” Cause: An OS error was returned when verifying the role name. Action: See OSD error accompanying this message |
| ORA-09274 ORA-09274, 00000, “szrfc: insufficient role name buffer space” Cause: An OS role name was too long. Action: See OSD error accompanying this message |
| ORA-09275 ORA-09275, 00000, “CONNECT INTERNAL is not a valid DBA connection” Cause: CONNECT INTERNAL is no longer supported for DBA connections. Action: Please try to connect AS SYSDBA or AS SYSOPER. |
| ORA-09276 ORA-09276, 00000, “All bequeath database links must be loopback database links” Cause: A non-loopback bequeath connect string was supplied for a database link. Action: Please use a connect string with a different transport protocol, or specify a loopback connect string (one that points to the instance for the current session) using “(PROGRAM= optionally, “(ENVS=”ORACLE_SID= |
| ORA-09280 ORA-09280, 00000, “sllfcf: error closing file” Cause: File may be corrupted Action: See OSD error accompanying this message |
| ORA-09281 ORA-09281, 00000, “sllfop: error opening file” Cause: Possibly incorrect path specified to the file Action: See OSD error accompanying this message |
| ORA-09282 ORA-09282, 00000, “sllfrb: error reading records” Cause: File could be corrupted Action: See OSD error accompanying this message |
| ORA-09283 ORA-09283, 00000, “sllfsk: error skipping records” Cause: File could be corrupted Action: See OSD error accompanying this message |
| ORA-09284 ORA-09284, 00000, “sllfop: cannot allocate read buffer” Cause: malloc() system call returned an error. The system might have run out of heap space Action: Check additional information for the OS error. |
| ORA-09285 ORA-09285, 00000, “sllfop: unrecognizable processing option, incorrect format” Cause: Processing option passed is of incorrect format Action: Consult your IUG for permissible formats |
| ORA-09290 ORA-09290, 00000, “sksaalo: error allocating memory for archival” Cause: Could be out of memory Action: See OSD error accompanying this message |
| ORA-09291 ORA-09291, 00000, “sksachk: invalid device specified for archive destination” Cause: Unable to access directory Action: Specify a valid device in ARCHIVE control string |
| ORA-09292 ORA-09292, 00000, “sksabln: unable to build archive file name” Cause: Bad directory or format specified Action: Specify a valid directory in ‘log_archive_format’ and a valid // format string in ‘log_archive_format’ in init.ora |
| ORA-09293 ORA-09293, 00000, “sksasmo: unable to send message to console” Cause: An error was returned while attempting to send a message // to the console operator Action: See OSD error accompanying this message |
| ORA-09300 ORA-09300, 00000, “osncon: unable to connect, DPMI not available” Cause: Unable to detect the presence of DPMI Action: Restart Windows and retry |
| ORA-09301 ORA-09301, 00000, “osncon: local kernel only supported in standard mode” Cause: An attempt was made to connect to S: while in enhanced mode Action: Restart Windows in standard mode |
| ORA-09310 ORA-09310, 00000, “sclgt: error freeing latch” Cause: Internal error Action: See OSD error accompanying this message |
| ORA-09311 ORA-09311, 00000, “slsleep: error temporarily suspending process” Cause: May be out of resources Action: See OSD error accompanying this message |
| ORA-09312 ORA-09312, 00000, “slspool: error spooling file to printer” Cause: Could be out of resources Action: See OSD error accompanying this message |
| ORA-09313 ORA-09313, 00000, “slsprom: error prompting user” Cause: May be out of resources Action: See OSD error accompanying this message |
| ORA-09314 ORA-09314, 00000, “sltln: error translating logical name” Cause: Internal buffer may have overflowed Action: See OSD error accompanying this message |
| ORA-09315 ORA-09315, 00000, “sql2tt: two-task error translating ORACLE_EXECUTABLE” Cause: Internal error Action: See OSD error accompanying this message |
| ORA-09316 ORA-09316, 00000, “szrpc: unable to verify password for role” Cause: OS roles may not be supported for this platform Action: See OSD error accompanying this message |
| ORA-09317 ORA-09317, 00000, “szprv: insufficient privileges” Cause: The password specified is invalid Action: See OSD error accompanying this message |
| ORA-09318 ORA-09318, 00000, “slkhst: unable to host out to operating system” Cause: There might not be enough memory for the command or hosting out // may not be supported on this platform Action: See OSD error accompanying this message |
| ORA-09319 ORA-09319, 00000, “slgtd: unable to obtain the current date and time” Cause: The system time might be set incorrectly Action: See OSD error accompanying this message |
| ORA-09320 ORA-09320, 00000, “szrfc: unable to obtain the list of valid OS roles” Cause: OS roles may not be supported on this platform Action: See OSD error accompanying this message |
| ORA-09321 ORA-09321, 00000, “slzdtb: unable to convert zoned decimal to binary” Cause: internal error Action: See OSD error accompanying this message |
| ORA-09322 ORA-09322, 00000, “slpdtb: unable to convert packed decimal to binary” Cause: internal error Action: See OSD error accompanying this message |
| ORA-09330 ORA-09330, 00000, “Session terminated internally by Oracle or by an Oracle DBA” Cause: A client workstation that is abnormally disconnected would // cause Oracle to terminate that session after about a minute. // This message also appears in the trace file if a shutdown abort // is performed. |
| ORA-09340 ORA-09340, 00000, “Specified ORACLE_SID is either invalid or too long” Cause: ORACLE_SID must be at the most 4 alphanumeric characters. |
| ORA-09341 ORA-09341, 00000, “scumnt: unable to mount database” Cause: Another instance is currently mounting the database |
| ORA-09342 ORA-09342, 00000, “Detached process terminated by Oracle during shutdown abort” Cause: The user performed a shutdown abort. |
| ORA-09344 ORA-09344, 00000, “spsig: error signalling thread” Cause: This function may not be implemented. |
| ORA-09350 ORA-09350, 00000, “Windows 32-bit Two-Task driver unable to allocate context area” Cause: See OSD error accompanying this message |
| ORA-09351 ORA-09351, 00000, “Windows 32-bit Two-Task driver unable to allocate shared memory” Cause: See OSD error accompanying this message |
| ORA-09352 ORA-09352, 00000, “Windows 32-bit Two-Task driver unable to spawn new ORACLE task” Cause: See OSD error accompanying this message |
| ORA-09353 ORA-09353, 00000, “Windows 32-bit Two-Task driver unable to open event semaphore” Cause: See OSD error accompanying this message |
| ORA-09354 ORA-09354, 00000, “Windows 32-bit Two-Task driver: ORACLE task unexpectedly died” Cause: See OSD error accompanying this message |
| ORA-09360 ORA-09360, 00000, “Windows 3.1 Two-Task driver unable to allocate context area” Cause: See OSD error accompanying this message |
| ORA-09361 ORA-09361, 00000, “Windows 3.1 Two-Task driver unable to lock context area” Cause: See OSD error accompanying this message |
| ORA-09362 ORA-09362, 00000, “Windows 3.1 Two-Task driver unable to deallocate context area” Cause: See OSD error accompanying this message |
| ORA-09363 ORA-09363, 00000, “Windows 3.1 Two-Task driver invalid context area” Cause: See OSD error accompanying this message |
| ORA-09364 ORA-09364, 00000, “Windows 3.1 Two-Task driver unable to create hidden window” Cause: See OSD error accompanying this message |
| ORA-09365 ORA-09365, 00000, “Windows 3.1 Two-Task driver unable to destroy hidden window” Cause: See OSD error accompanying this message |
| ORA-09366 ORA-09366, 00000, “Windows 3.1 Two-Task driver unable to allocate shared memory” Cause: See OSD error accompanying this message |
| ORA-09367 ORA-09367, 00000, “Windows 3.1 Two-Task driver unable to deallocate shared memory” Cause: See OSD error accompanying this message |
| ORA-09368 ORA-09368, 00000, “Windows 3.1 Two-Task driver unable to spawn ORACLE” Cause: See OSD error accompanying this message |
| ORA-09369 ORA-09369, 00000, “Windows 3.1 Two-Task driver bad instance handle” Cause: See OSD error accompanying this message |
| ORA-09370 ORA-09370, 00000, “Windows 3.1 Two-Task driver ORACLE task timed out” Cause: See OSD error accompanying this message |
| ORA-09700 ORA-09700, 00000, “sclin: maximum number of latches exceeded” Cause: ORACLE wants to use more latches then available. Action: increase INIT.ORA parameter latch_pages or decrease the amount of shared memory you are using. |
| ORA-09701 ORA-09701, 00000, “scnfy: maximum number of processes exceeded” Cause: PROCESSES INIT.ORA parameter exceeded. Action: Decrease the PROCESSES parameter and restart. |
| ORA-09702 ORA-09702, 00000, “sem_acquire: cannot acquire latch semaphore” Cause: The semaphore used for accessing latches could not be seized Action: Send trace file to your customer support representative, // along with information on reproducing the error. |
| ORA-09703 ORA-09703, 00000, “sem_release: cannot release latch semaphore” Cause: The semaphore used for accessing latches could not be released Action: Send trace file to your customer support representative, // along with information on reproducing the error. |
| ORA-09704 ORA-09704, 00000, “sstascre: ftok error in creating test and set pages.” Cause: the ftok() library call failed in sstastcre(). Action: Verify that tasdef@.dbf file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled. |
| ORA-09705 ORA-09705, 00000, “spcre: cannot initialize latch semaphore” Cause: The semaphore used for accessing latches could not be initialized Action: Send trace file to your customer support representative, // along with information on reproducing the error. |
| ORA-09706 ORA-09706, 00000, “slsget: get_process_stats error.” Cause: get_process_stats system call returned an error. Possible OS error. Action: Check additional information returned. Look for information in OS reference. Contact customer support. |
| ORA-09708 ORA-09708, 00000, “soacon: failed to bind socket to port.” Cause: The bind system call failed on the socket. Action: Check additional information for OS error. Try connecting again. |
| ORA-09709 ORA-09709, 00000, “soacon: failed to accept a connection.” Cause: The accept system call failed on the socket. Action: Check additional information for OS error. Try connecting again. |
| ORA-09710 ORA-09710, 00000, “soarcv: buffer overflow.” Cause: The internal buffer is not big enough to hold the message read. Action: Internal error. Contact customer support representative. |
| ORA-09711 ORA-09711, 00000, “orasrv: archmon already connected.” Cause: An existing connection has already been made from archmon to orasrv. Action: Stop trying to connect. |
| ORA-09712 ORA-09712, 00000, “orasrv: log archiver already connected.” Cause: An existing connection has already been made from log archiver to orasrv. Action: Stop trying to connect. |
| ORA-09714 ORA-09714, 00000, “Two Task interface: cannot obtain puname” Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error) Action: Check if the PUs are named (consistend). |
| ORA-09715 ORA-09715, 00000, “orasrv: cannot obtain puname” Cause: Orasrv cannot obtain the name of the PU. (Possible OS error) Action: Check if the PUs are named (consistend). |
| ORA-09716 ORA-09716, 00000, “kslcll: Unable to fix in-flux lamport latch.” Cause: One Oracle process died while still holding a lamport latch. Action: Exit (kill) all Oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel. |
| ORA-09717 ORA-09717, 00000, “osnsui: maximum number of user interrupt handlers exceeded.” Cause: The internal limit on the number of user interrupt handlers has been exceeded. Action: Reduce the number of simulataneous logons or reduce the number of user interrupt handlers. |
| ORA-09718 ORA-09718, 00000, “osnsui: cannot set up user interrupt handler.” Cause: Malloc() failed to allocate space to hold user interrupt handler. Action: Possible memory resource shortage. |
| ORA-09719 ORA-09719, 00000, “osncui: invalid handle.” Cause: The handle passed to osncui is out of the valid range. Action: Use a valid handle. |
| ORA-09740 ORA-09740, 00000, “slsget: cannot get virtual memory region statistics.” Cause: The vm_region system call failed to get virual memory region statistics. Action: Check return code in sercerrno. Possible operating system failure. |
| ORA-09741 ORA-09741, 00000, “spwat: error waiting for a post.” Cause: Msg_receive system call returned an error. Internal error. Action: Check return code in sercerrno. Port name is returned in // sercose[0]. |
| ORA-09742 ORA-09742, 00000, “sppst: error during a post.” Cause: Msg_send system call returned an error. Internal error. Action: Check return code in sercerrno. Port name is returned in // sercose[0]. |
| ORA-09743 ORA-09743, 00000, “smscre: could not attach shared memory.” Cause: The mmap or write system call returned an error. Internal error. Action: Contact Oracle support. |
| ORA-09744 ORA-09744, 00000, “smsget: mmap returned an error.” Cause: The mmap system call returned an error. Internal error. Action: Contact Oracle support. |
| ORA-09745 ORA-09745, 00000, “smscre: vm_allocate error, unable to create shared memory.” Cause: Error in system call vm_allocate. Failed to create SGA as a // single shared memory segment. Action: Check result code returned in sercerrno. Verify that the SGA // attach address is valid. |
| ORA-09746 ORA-09746, 00000, “smscre: shared memory attach address incorrect.” Cause: The vm_allocate system call attached the SGA at an incorrect // location. Action: Verify that the SGA attach address is valid. |
| ORA-09747 ORA-09747, 00000, “pw_detachPorts: server call pws_detach failed.” Cause: The call pws_detach to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. |
| ORA-09748 ORA-09748, 00000, “pws_look_up: fork failed” Cause: The pws_look_up call could not fork the (Oracle helper) 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-09749 ORA-09749, 00000, “pws_look_up: port lookup failure” Cause: The pws_look_up could not find a port to (Oracle helper). Action: Make sure the (Oracle helper) server has been started correctly // by pws_look_up, and that the network name server is still running. |
| ORA-09750 ORA-09750, 00000, “pw_attachPorts: port_rename failed.” Cause: The port_rename system call failed; possible internal error. Action: Check return code in sercerrno, report to Oracle customer support. |
| ORA-09751 ORA-09751, 00000, “pw_attachPorts: server call pws_attach failed.” Cause: The call pws_attach to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. |
| ORA-09752 ORA-09752, 00000, “pw_attachPorts: port_allocate failed.” Cause: The port_allocate system call failed; possible resource exhaustion. Action: Check return code in sercerrno, report to Oracle customer support. |
| ORA-09753 ORA-09753, 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-09754 ORA-09754, 00000, “sppst: invalid process number passed to sppst.” Cause: Function was passed an invalid oracle process id. Action: Internal error. Contact Oracle support. |
| ORA-09755 ORA-09755, 00000, “osngpn: port allocation failure.” Cause: The port_allocate system call failed. Action: Possible system resource shortage; check the error code in // sercerrno. |
| ORA-09756 ORA-09756, 00000, “osnpns: no port in the name server.” Cause: osnpns could not find the given named port in the name server. Action: Check the error code in sercerrno. Make sure the shadow process // and network name server are still running. |
| ORA-09757 ORA-09757, 00000, “osnipn: port allocation failure.” Cause: The port_allocate system call failed. Action: Possible system resource shortage; check the error code in // sercerrno. |
| ORA-09758 ORA-09758, 00000, “osnipn: could not check port in name server.” Cause: The netname_check_in call failed. Action: Check the error code in sercerrno. Make sure the network name // server is running. |
| ORA-09759 ORA-09759, 00000, “osnsbt: bad message received.” Cause: The msg_receive system call failed, or received a bad message. Action: Internal error. Report the error code returned in sercerrno. |
| ORA-09760 ORA-09760, 00000, “osnpui: cannot send break message” Cause: The Pipe driver could not send a break message to the ORACLE // shadow process break thread. Action: Contact your customer support representative. |
| ORA-09761 ORA-09761, 00000, “pw_destroyPorts: server call pws_stop_instance failed.” Cause: The call pws_stop_instance to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. |
| ORA-09762 ORA-09762, 00000, “sNeXT_instanceName: translation error.” Cause: A failure was detected while translating the value of ORACLE_SID. Action: Make sure ORACLE_SID is defined, and that it is of legal length. |
| ORA-09763 ORA-09763, 00000, “osnmpx: send/receive error exchanging Mach ports.” Cause: The Mach driver failed to exchange port information with the // other side of the connection. Either msg_send (sercose[0] == 1) // or msg_receive (sercose[0] == 2) failed. Action: Check return code in sercerrno. Make sure both sides of the // connection are still running. |
| ORA-09764 ORA-09764, 00000, “osnmop: access error on oracle executable” Cause: The Mach 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-09765 ORA-09765, 00000, “osnmop: fork failed” Cause: The Mach 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-09766 ORA-09766, 00000, “osnmop: buffer allocation failure.” Cause: The Mach driver failed to allocate enough vm space for its // I/O buffers. Action: Decrease the value of buffer_size parameter in the Two-Task // driver hoststring. |
| ORA-09767 ORA-09767, 00000, “osnmfs: bad return code from msg_send.” Cause: The msg_send system call failed while flushing the Mach driver’s // send buffer. Action: Internal error. Contact your customer support representative. |
| ORA-09768 ORA-09768, 00000, “osnmgetmsg: could not read a message” Cause: The msg_receive system call returned a failure code while waiting // for a message in the Mach driver. Action: Internal error. Contact your customer support representative. |
| ORA-09769 ORA-09769, 00000, “osnmbr: cannot send break message” Cause: The Mach driver could not send a break message to the ORACLE // shadow process break thread. Action: Internal error. Contact your customer support representative. |
| ORA-09770 ORA-09770, 00000, “pws_look_up: translation failure.” Cause: The pws_look_up routine failed to translate the name of the // (Oracle helper) executable. Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. // Additional information gives the translation error code. |
| ORA-09771 ORA-09771, 00000, “osnmwrtbrkmsg: bad return code from msg_send.” Cause: The msg_send sytem call failed while sending a Mach driver break. Action: Internal error. Contact your customer support representative. |
| ORA-09772 ORA-09772, 00000, “osnpmetbrkmsg: message from host had incorrect message type” Cause: The Mach driver received a message having an unrecognizable // message type. Action: Internal error. Contact your customer support representative. |
| ORA-09773 ORA-09773, 00000, “osnmgetdatmsg: message from host had incorrect message type” Cause: The Mach driver received a message having an unrecognizable // message type. Action: Internal error. Contact your customer support representative. |
| ORA-09774 ORA-09774, 00000, “osnmui: cannot send break message” Cause: The Mach driver could not send a break message to the ORACLE // shadow process break thread. Action: Internal error. Contact your customer support representative. |
| ORA-09775 ORA-09775, 00000, “osnmrs: reset protocol error” Cause: The Mach two-task driver could not reset the connection. Action: Internal error. Contact your customer support representative. |
| ORA-09776 ORA-09776, 00000, “pws_look_up: access error on (Oracle helper) executable” Cause: The pws_look_up call could not access the (Oracle helper) // executable. Action: Check the permissions on the (Oracle helper) executable and each // component of the ORACLE_HOME/bin path. |
| ORA-09777 ORA-09777, 00000, “osnpbr: cannot send break message” Cause: The pipe driver could not send a break message to the ORACLE // shadow process break thread. Action: Internal error. Contact your customer support representative. |
| ORA-09778 ORA-09778, 00000, “snynfyport: failure allocating the notify port.” Cause: The routine failed to allocate or set the task’s notify port. Action: Possible operating system error. Contact Oracle support. |
| ORA-09779 ORA-09779, 00000, “snyGetPort: failure to allocate a port.” Cause: The port_allocate system call failed; system resources might be // exhausted. Action: Possible operating system error. Contact Oracle support. |
| ORA-09786 ORA-09786, 00000, “sllfop: open error, unable to open file.” Cause: Open system call returned an error. Action: Check errno. |
| ORA-09787 ORA-09787, 00000, “sllfop: unrecognizable processing option, incorrect format.” Cause: Processing option passed is of incorrect format. Action: Consult your IUG for permissible formats. |
| ORA-09788 ORA-09788, 00000, “sllfrb: unable to read file.” Cause: Read system call returned an error. Action: Check errno. Verify file exists. |
| ORA-09789 ORA-09789, 00000, “sllfsk: unable to read file.” Cause: Read system call returned an error. Action: Check errno. Verify file exists. |
| ORA-09790 ORA-09790, 00000, “sllfcf: unable to close file.” Cause: Close system call returned an error. Action: Check errno. |
| ORA-09791 ORA-09791, 00000, “slembdf: translation error, unable to translate error file name.” Cause: Additional information indicates error returned from sltln. Action: Check additional information. |
| ORA-09792 ORA-09792, 00000, “sllfop: cannot allocate read buffer.” Cause: Malloc system call returned an error. The system might have run out of heap space. Action: Check additional information for the OS error. |
| ORA-09793 ORA-09793, 00000, “szguns: length of user name is greater than buffer.” Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09794 ORA-09794, 00000, “szrbuild: length of role name is greater than buffer.” Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09795 ORA-09795, 00000, “szrbuild: malloc of role structure failed.” Cause: The allocation of memory for an internal structure used to hold a role descriptor failed. Action: Check the UNIX error number for a possible operating system failure. |
| ORA-09796 ORA-09796, 00000, “szrbuild: malloc of role name failed.” Cause: The allocation of memory for an internal buffer used to hold the name of a role failed. Action: Check the UNIX error number for a possible operating system failure. |
| ORA-09797 ORA-09797, 00000, “Failed to get O/S MAC privileges.” Cause: The operating system would not allow the retrieval of this process’ privileges. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09798 ORA-09798, 00000, “Label comparison failed.” Cause: The comparison of two binary labels failed. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09799 ORA-09799, 00000, “File label retrieval failed.” Cause: ORACLE was unable to get a label attached to a file. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09800 ORA-09800, 00000, “Process sensitivity label retrieval failed.” Cause: ORACLE was unable to get the sensitivity label for a process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09801 ORA-09801, 00000, “Unable to get user ID from connection” Cause: ORACLE was unable to retrieve the user’s ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services. |
| ORA-09802 ORA-09802, 00000, “Conversion of binary label to string failed.” Cause: ORACLE was unable to convert a binary label to a string. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09803 ORA-09803, 00000, “Allocation of string buffer failed.” Cause: a buffer used to hold the name of the file for which a label was to be obtained could not be allocated. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that ORACLE attempted to allocate is in the “Additional Information” field. |
| ORA-09804 ORA-09804, 00000, “Class conversion from binary to ORACLE failed.” Cause: ORACLE was unable to convert a class component from binary format to ORACLE format. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09805 ORA-09805, 00000, “conversion of category number to string failed.” Cause: ORACLE was unable to translate a category number to its corresponding string representation failed. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The category number is contained in the “Additional information” field. |
| ORA-09806 ORA-09806, 00000, “Allocation of label string buffer failed.” Cause: a temporary buffer used to hold a label could not be allocated. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that ORACLE attempted to allocate is in the “Additional Information” field. |
| ORA-09807 ORA-09807, 00000, “Conversion of label from string to binary failed.” Cause: ORACLE was unable to convert the string representation of a label to binary format. Action: Re-enter a valid label. |
| ORA-09808 ORA-09808, 00000, “Could not obtain user clearance.” Cause: ORACLE was unable to get a user’s clearance level. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. |
| ORA-09809 ORA-09809, 00000, “Unable to get user’s group ID from connection” Cause: ORACLE was unable to retrieve the user’s group ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services. |
| ORA-09810 ORA-09810, 00000, “Unable to get process ID from connection” Cause: ORACLE was unable to retrieve the user’s process ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services. |
| ORA-09811 ORA-09811, 00000, “Unable to initialize package.” Cause: ORACLE was unable to initialize the library used to obtain security information. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09812 ORA-09812, 00000, “Unable to get user clearance from connection” Cause: ORACLE was unable to retrieve the user’s operating system session clearance from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services. |
| ORA-09813 ORA-09813, 00000, “Unable to get directory status” Cause: ORACLE was unable to determine if a directory is multilevel. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. |
| ORA-09814 ORA-09814, 00000, “Unable to expand file name” Cause: ORACLE was unable to expand the name of a file that resides in multilevel directory. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. |
| ORA-09815 ORA-09815, 00000, “File name buffer overflow” Cause: The buffer that ORACLE uses to hold the expanded name of a too small. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09816 ORA-09816, 00000, “Unable to set effective privileges” Cause: Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09817 ORA-09817, 00000, “Write to audit file failed.” Cause: ORACLE was unable to write an entry to the file used as the audit trail. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. |
| ORA-09818 ORA-09818, 00000, “Number is too large” Cause: ORACLE was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum. Action: Correct the string and repeat the conversion. |
| ORA-09819 ORA-09819, 00000, “Number exceeds maximum legal value” Cause: the number specified for a component was greater than the maximum value allowed for that component. Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the “Additional information” field. |
| ORA-09820 ORA-09820, 00000, “Conversion of class string to numeric representation failed.” Cause: ORACLE was unable to convert a class string to a number because all of the characters in the string were not numeric. Action: Change the string to be either all numbers or all non-numeric characters and repeat the conversion. |
| ORA-09821 ORA-09821, 00000, “Numeric label is not valid” Cause: A label specified in ORACLE numeric format was found not to be valid. Action: Re-enter a valid label. Consult your system’s encodings for valid numeric component values. |
| ORA-09822 ORA-09822, 00000, “Translation of audit file name failed.” Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. |
| ORA-09823 ORA-09823, 00000, “device name is too long” Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09824 ORA-09824, 0000, “Unable to enable allowmacaccess privilege.” Cause: ORACLE was not able to turn on allowmacaccess privilege so that it could do a label comparison. Action: Check the UNIX error number. If it indicates that ORACLE does not have the allowmacaccess privilege, add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, contact Oracle Support Services. |
| ORA-09825 ORA-09825, 0000, “Unable to disable allowmacaccess privilege.” Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-09826 ORA-09826, 00000, “SCLIN: cannot initialize atomic latch.” Cause: System call atomic_op() return error. Action: Check additional information in the trace file. |
| ORA-09827 ORA-09827, 00000, “SCLGT: atomic latch return unknown error.” Cause: System call atomic_op() return unexpected error. Action: Check additional information in the trace file. |
| ORA-09828 ORA-09828, 00000, “SCLFR: atomic latch return error.” Cause: System call atomic_op() return unexpected error. Action: Check additional information in the trace file. |
| ORA-09829 ORA-09829, 00000, “pw_createPorts: server call pws_start_instance failed.” Cause: The call pws_start_instance to (Oracle helper) failed; system // resources might be exhausted. Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. |
| ORA-09830 ORA-09830, 00000, “snyAddPort: failed to perform a remote procedure call.” Cause: The msg_rpc system call returned an error. Action: Internal error. Contact Oracle support. |
| ORA-09831 ORA-09831, 00000, “snyStartThread: failed to build the server port set.” Cause: The routine failed to build a port set on which to listen for // requests. Action: Possible operating system failure. Contact Oracle support. |
| ORA-09832 ORA-09832, 00000, “infoCallback: bad message format.” Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. |
| ORA-09833 ORA-09833, 00000, “addCallback: bad message format.” Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. |
| ORA-09834 ORA-09834, 00000, “snyGetPortSet: failed to collect info on a port.” Cause: The port_status system called failed. Action: Possible operating system error. Contact Oracle support. |
| ORA-09835 ORA-09835, 00000, “addCallback: callback port is already in a set.” Cause: The port to be added to the callback list is already in a port set. Action: Internal error. Contact Oracle support. |
| ORA-09836 ORA-09836, 00000, “addCallback: could not add a port to the callback set.” Cause: The port_set_add system called failed. Action: Possible operating system error. Contact Oracle support. |
| ORA-09837 ORA-09837, 00000, “addCallback: could not add allocate a callback link.” Cause: The malloc library call failed to allocate space for a callback link. Action: Possible operating system error. Contact Oracle support. |
| ORA-09838 ORA-09838, 00000, “removeCallback: failure removing the callback port.” Cause: The port port_set_remove system call failed. Action: Possible operating system error. Contact Oracle support. |
| ORA-09839 ORA-09839, 00000, “removeCallback: callback port is not in the callback set.” Cause: The port to be removed to the callback list is not in the // callback port set. Action: Internal error. Contact Oracle support. |
| ORA-09840 ORA-09840, 00000, “soacon: Name translation failure.” Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@. Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct. |
| ORA-09841 ORA-09841, 00000, “soacon: Name translation failure.” Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@. Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct. |
| ORA-09842 ORA-09842, 00000, “soacon: Archmon unable to create named pipe.” Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@. Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab. |
| ORA-09843 ORA-09843, 00000, “soacon: Archmon unable to create named pipe.” Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@. Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab. |
| ORA-09844 ORA-09844, 00000, “soacon: Archmon unable to open named pipe.” Cause: open() failed to open named pipe ?/dbs/mon2arch_@. Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. |
| ORA-09845 ORA-09845, 00000, “soacon: Archmon unable to open named pipe.” Cause: open() failed to open named pipe ?/dbs/arch2mon_@. Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. |
| ORA-09846 ORA-09846, 00000, “soacon: ARCH unable to open named pipe.” Cause: open() failed to open named pipe ?/dbs/mon2arch_@. Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. |
| ORA-09847 ORA-09847, 00000, “soacon: ARCH unable to open named pipe.” Cause: open() failed to open named pipe ?/dbs/arch2mon_@. Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. |
| ORA-09848 ORA-09848, 00000, “soawrt: Unable to write to named pipe.” Cause: Action: |
| ORA-09849 ORA-09849, 00000, “soarcv: Unable to read from named pipe.” Cause: Action: |
| ORA-09850 ORA-09850, 00000, “soacon: Archmon unable to lock named pipe.” Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@. Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance. |
| ORA-09851 ORA-09851, 00000, “soacon: Archmon unable to lock named pipe.” Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@. Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance. |
| ORA-09853 ORA-09853, 00000, “snyRemovePort: bad return code from request.” Cause: The request to remove a port from the callback set returned a // failure code. Action: Possible operating system error. Contact Oracle support. |
| ORA-09854 ORA-09854, 00000, “snyPortInfo: bad return code from request.” Cause: The request to collect info on a port in the callback set returned // a failure code. Action: Possible operating system error. Contact Oracle support. |
| ORA-09855 ORA-09855, 00000, “removeCallback: bad message format.” Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. |
| ORA-09856 ORA-09856, 00000, “smpalo: vm_allocate error while allocating pga.” Cause: The vm_allocate system call returned an error. Action: Check returned error. Possibly out of system resources. |
| ORA-09857 ORA-09857, 00000, “smprset: vm_protect error while protecting pga.” Cause: The vm_protect system call returned an error. Action: Internal error. Contact Oracle support. |
| ORA-09858 ORA-09858, 00000, “sfngat: the input file name is not in the OMF format” Cause: The function sfngat() received a filename which is not an OMF file name. Action: Further diagnostic information should be in the error stack. |
| ORA-09859 ORA-09859, 00000, “sfngat: the input file name is not in the autobackup OMF format” Cause: The function sfngat() received a filename which is not an autobackup OMF file name. Action: Further diagnostic information should be in the error stack. |
| ORA-09870 ORA-09870, 00000, “spini: failure initializing maximum number of open files.” Cause: ulimit system call returned an error. Action: Check errno. |
| ORA-09871 ORA-09871, 00000, “TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.” Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages. Action: Check additional return error for more information. |
| ORA-09872 ORA-09872, 00000, “TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.” Cause: Create() failed when trying to create the tasdef file. Action: Verify permissions on $(ORACLE_HOME)/dbs directory. |
| ORA-09873 ORA-09873, 00000, “TASDEF_OPEN: open error when opening tasdef@.dbf file.” Cause: Unable to open tasdef@.dbf file. Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists. |
| ORA-09874 ORA-09874, 00000, “TASDEF_READ: read error, unable to read tasdef@.dbf file.” Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf. Action: Check errno returned. Sgadef file may be corrupted or incompatible with oracle version. |
| ORA-09875 ORA-09875, 00000, “TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.” Cause: Write call failed. Action: Check errno returned. Possibly out of space on device. |
| ORA-09876 ORA-09876, 00000, “TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.” Cause: Close system call returned an error. Action: Check errno returned. Possible operating system failure. |
| ORA-09877 ORA-09877, 00000, “sstascre: shmget error, unable to get a shared memory segment.” Cause: Error in shmget. Action: Check errno returned. Verify that enough shared memory is available on the system. |
| ORA-09878 ORA-09878, 00000, “sstascre/sstasat: shmat error, unable to attach tas write page” Cause: Error in shmat. Action: Check errno returned.Verify that enough shared memory is available on the system. |
| ORA-09879 ORA-09879, 00000, “sstascre/sstasat: shmat error, unable to attach tas read page” Cause: Error in shmat. Action: Check errno returned.Verify that enough shared memory is available on the system. |
| ORA-09880 ORA-09880, 00000, “sstasfre/sstasdel: shmdt error, unable to detach tas write page” Cause: Error in shmdt. Action: Check errno returned. |
| ORA-09881 ORA-09881, 00000, “sstasfre/sstasdel: shmdt error, unable to detach tas read page” Cause: Error in shmdt. Action: Check errno returned. |
| ORA-09882 ORA-09882, 00000, “sstasfre/sstasdel: shmctl error, unable to remove tas shm page” Cause: Error in shmctl. Action: Check errno returned. |
| ORA-09883 ORA-09883, 00000, “Two Task interface: oratab file does not exist” Cause: The oratab file does not exist. Action: Install oracle before you use it or recreate the oratab file. |
| ORA-09884 ORA-09884, 00000, “Two Task interface: SID doens’t match current PU” Cause: You are trying to start oracle on another PU than you configured oracle on or there is no entry for this SID in oratab file. Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID. |
| ORA-09885 ORA-09885, 00000, “osnTXtt: cannot create TXIPC channel” Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. |
| ORA-09886 ORA-09886, 00000, “osnTXtt: translation error while expanding txipc@.trc.” Cause: Failure of sltln(txipc@.trc) while creating debug channel. Action: Check additional return error for more information. |
| ORA-09887 ORA-09887, 00000, “osnTXtt: Failed to create/open debug channel.” Cause: Action: |
| ORA-09888 ORA-09888, 00000, “osnTXtt: txipc channel creation failed” Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator. |
| ORA-09889 ORA-09889, 00000, “osnTXtt: access error on oracle executable” Cause: The txipc driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. |
| ORA-09890 ORA-09890, 00000, “osnTXtt: malloc failed” Cause: The txipx driver failed to allocate enough heap space for its context area buffers. Action: Contact your customer support representative. |
| ORA-09908 ORA-09908, 00000, “slkmnm: gethostname returned error code.” Cause: The system call gethostname returned an error. Action: This is most likely an internal error. Make sure gethostname is successful in other contexts, and if so contact Oracle support. |
| ORA-09909 ORA-09909, 00000, “Malloc of scratch buffer failed.” Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that ORACLE attempted to allocate. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. |
| ORA-09910 ORA-09910, 00000, “Unable to find ORACLE password file entry for user.” Cause: No entry exists for the user in the ORACLE password file. Action: Have the database administrator install a password entry by running orapasswd. |
| ORA-09911 ORA-09911, 00000, “Incorrect user password.” Cause: The password entered by the user was incorrect. Action: Enter the correct password. |
| ORA-09912 ORA-09912, 00000, “Malloc of name buffer(s) failed.” Cause: ORACLE was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. |
| ORA-09913 ORA-09913, 00000, “Malloc of dummy name failed.” Cause: ORACLE was unable to allocate memory for the user name that is to to be used in the encryption of the user’s password. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. |
| ORA-09914 ORA-09914, 00000, “Unable to open the ORACLE password file.” Cause: ORACLE could not open the password file for reading. Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact ORACLE customer support. |
| ORA-09915 ORA-09915, 00000, “Password encryption failed.” Cause: ORACLE was unable to encrypt a password. Action: This is an internal error – contact ORACLE customer support. |
| ORA-09916 ORA-09916, 00000, “Required password was not specified.” Cause: A user attempted to connect as “internal,” but did not specify a password. Action: Connect as internal again and specify a password. |
| ORA-09918 ORA-09918, 00000, “Unable to get user privileges from SQL*Net” Cause: ORACLE was unable to retrieve the user’s privilege set from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support. |
| ORA-09919 ORA-09919, 00000, “Unable to set label of dedicated server” Cause: ORACLE was unable to set the label of the dedicated to server to the required value. Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the oracle executable. It should have at least “allowmacaccess” privilege. |
| ORA-09920 ORA-09920, 00000, “Unable to get sensitivity label from connection” Cause: ORACLE was unable to retrieve the user’s sensitivity label from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support. |
| ORA-09921 ORA-09921, 00000, “Unable to get information label from connection” Cause: ORACLE was unable to retrieve the user’s information label from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact ORACLE support. |
| ORA-09922 ORA-09922, 00000, “Can’t spawn process – background log directory not created properly” Cause: ORACLE was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly. Action: Examine the directory pointed to by the initialization parameter “background_dump_dest”. Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. |
| ORA-09923 ORA-09923, 00000, “Can’t spawn process – user log directory not created properly” Cause: ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly. Action: Examine the directory pointed to by the initialization parameter “user_dump_dest”. Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. |
| ORA-09924 ORA-09924, 00000, “Can’t spawn process – core dump directory not created properly” Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly. Action: Examine the directory pointed to by the initialization parameter “core_dump_dest”. Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. |
| ORA-09925 ORA-09925, 00000, “Unable to create audit trail file” Cause: ORACLE was not able to create the file being used to hold audit trail records. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support. |
| ORA-09926 ORA-09926, 00000, “Unable to set effective privilege set of the server” Cause: A dedicated server was unable to set it’s own privilege set. Action: Check the privileges granted to the ORACLE executable. It must have at least “allowmacacess” privilege. |
| ORA-09927 ORA-09927, 00000, “Unable to set label of server” Cause: ORACLE was not able to set the label of a server to a new value. Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has “allowmacaccess” privilege. |
| ORA-09928 ORA-09928, 00000, “Unable to restore the label of server” Cause: ORACLE was unable to restore the label of the server to the value that it had before raising it to database high. Action: This is an internal error – contact ORACLE support. |
| ORA-09929 ORA-09929, 00000, “GLB of two labels is invalid” Cause: The result of a greatest lower bound operation on two labels was not valid. Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. |
| ORA-09930 ORA-09930, 00000, “LUB of two labels is invalid” Cause: The result of a least upper bound operation on two labels was not valid. Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. |
| ORA-09931 ORA-09931, 00000, “Unable to open ORACLE password file for reading” Cause: An attempt to open a password file for reading failed. Action: Make sure that the permissions on the file have not been changed so that the ORACLE user cannot open it. |
| ORA-09932 ORA-09932, 00000, “Close of ORACLE password file failed.” Cause: An attempt to close a password file failed. Action: Check the UNIX error number for the specific reason. |
| ORA-09933 ORA-09933, 00000, “Deletion of old password file failed.” Cause: The removal of the old password file failed. Action: Check the UNIX error number for the specific reason. |
| ORA-09934 ORA-09934, 00000, “Link of current password file to old failed.” Cause: ORACLE was unable to create a link so that the old password file could be saved. Action: Check the UNIX error number for the specific reason. |
| ORA-09935 ORA-09935, 00000, “Unlink of current password file failed.” Cause: ORACLE was unable to complete the saving of the current password file. Action: Check the UNIX error number for the specific reason. |
| ORA-09936 ORA-09936, 00000, “Open of ORACLE password file for write failed.” Cause: ORACLE was unable to create a password file. Action: Check the UNIX error number for the specific reason. |
| ORA-09937 ORA-09937, 00000, “Chmod of ORACLE password file failed.” Cause: ORACLE was unable to change a password file to be readonly. Action: Check the UNIX error number for the specific reason. |
| ORA-09938 ORA-09938, 00000, “Save of signal handlers failed.” Cause: ORACLE was unable to save the previous values of selected signal handlers. Action: This is an internal error. Contact ORACLE support. |
| ORA-09939 ORA-09939, 00000, “Restoration of signal handlers failed.” Cause: ORACLE was unable to restore the previous values of selected signal handlers. Action: This is an internal error. Contact ORACLE support. |
| ORA-09940 ORA-09940, 00000, “ORACLE password file header is corrupt” Cause: The header of one of the password files was not in the format that ORACLE expected. Action: Check the headers of both files. The header should be in the format “FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N” where N is a number. Remove the corrupt file(s) and re-run “orapasswd”. |
| ORA-09941 ORA-09941, 00000, “Version of orapasswd or installer is older than file.” Cause: The version of orapasswd or installer that is being run is older than that of the ORACLE password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created. Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file. |
| ORA-09942 ORA-09942, 00000, “Write of ORACLE password file header failed.” Cause: The attempt to write out the header of the ORACLE password file failed. Action: Check the operating system error number. It is possible that the file system became full. |
| ORA-09943 ORA-09943, 00000, “Allocation of memory for password list component failed.” Cause: When it is building a list of password file entries, ORACLE allocates memory for various components. One of the allocations failed. Action: Check the operating system error number. The system has probably run out of memory. |
| ORA-09944 ORA-09944, 00000, “Password entry is corrupt.” Cause: An entry in an ORACLE password file was not in the format that ORACLE expected. Action: Removed the corrupt file(s) and re-run “orapasswd.” |
| ORA-09945 ORA-09945, 00000, “Unable to initialize the audit trail file” Cause: ORACLE unable to write header information to the file being used as the audit trail. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support. |
| ORA-09946 ORA-09946, 00000, “File name too long for buffer” Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters. Action: Use a shorter file name. |
| ORA-09947 ORA-09947, 00000, “Unable to allocate connection attributes structure” Cause: ORACLE was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The “Additional Information” field holds the number of bytes that ORACLE attempted to allocate. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE customer support. |
| ORA-09948 ORA-09948, 00000, “Process information label retrieval failed.” Cause: ORACLE was unable to get the information label for a process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. |
| ORA-09949 ORA-09949, 00000, “Unable to get client operating system privileges” Cause: ORACLE was unable to get the operating system privileges for the client process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. |
| ORA-09950 ORA-09950, 00000, “Unable to get server operating system privileges” Cause: ORACLE was unable to get its privileges from the operating system. Action: This is an error that should never happen. Contact ORACLE customer support. |
| ORA-09951 ORA-09951, 00000, “Unable to create file” Cause: ORACLE was unable to create a file. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. |
| ORA-09952 ORA-09952, 00000, “scgcmn: lk_open_convert unexpected return: open failed” Cause: The distributed lock manager returned an unexpected value Action: Check for system error message and refer to the distributed lock manager documentation or contact your customer support representative. |
| ORA-09953 ORA-09953, 00000, “scggc: unexpected return of a lock convert” Cause: The distributed lock manager returned an unexpected value Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. |
| ORA-09954 ORA-09954, 00000, “scgcc: unexpected return status to callback of lock close” Cause: The distributed lock manager returned an unexpected value Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. |
| ORA-09955 ORA-09955, 00000, “scgcan: unexpected return status when canceling a lock” Cause: DLM system service x returned an unexpected value Action: Check for system error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. |
| ORA-09956 ORA-09956, 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 refer to the distributed lock manager documentation or contact your customer support representative. |
| ORA-09957 ORA-09957, 00000, “Unable to send termination request to IMON” Cause: The attempt to send a termination signal to IMON failed. Action: This is an internal error, contact ORACLE support. |
| ORA-09958 ORA-09958, 00000, “IMON: two processes with the same ORACLE pid are active” Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot. Action: This is an internal error, contact ORACLE support. |
| ORA-09959 ORA-09959, 00000, “IMON: deletion of a process failed.” Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found. Action: This is an internal error, contact ORACLE support. |
| ORA-09960 ORA-09960, 00000, “Unable to establish signal handler for termination signal” Cause: ORACLE was unable to set up a handler for the signal used to notify it that the instance was shutting down. Action: This is an internal error, contact ORACLE support. |
| ORA-09961 ORA-09961, 00000, “Unable to restore termination signal handler” Cause: ORACLE failed to set the handler for the termination signal to its previous value. Action: This is an internal error, contact ORACLE support. |
| ORA-09962 ORA-09962, 00000, “lk_group_create error in scggrc” Cause: Action: |
| ORA-09963 ORA-09963, 00000, “lk_group_attach error in scggra” Cause: Action: |
| ORA-09964 ORA-09964, 00000, “lk_group_detach error in scggrd” Cause: Action: |
| ORA-09966 ORA-09966, 00000, “falure in translation while expanding ?/dbs/lk for lock file” Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the database mount lock or the instance startup/shutdown lock. Action: Check additional return errors for more information. |
| ORA-09967 ORA-09967, 00000, “unable to create or open lock file” Cause: Oracle failed, when making an open system call, inorder to acquire a file lock used by the database mount lock or the instance startup/shutdown lock. Action: Check errno for more information. |
| ORA-09968 ORA-09968, 00000, “unable to lock file” Cause: The system call for locking a file returned an error when trying to acquire a database mount lock or the instance startup/shutdown lock. Action: Check errno for more information. |
| ORA-09969 ORA-09969, 00000, “unable to close or remove lock file” Cause: The close system call or unlink system call returned an error. Action: Check errno for more information. |
| ORA-09974 ORA-09974, 00000, “skxfidini: Error Initializing SDI Channel” Cause: The process was unable to initialize the SDI channel properly. Action: Correct the operating system error and retry the operation. |
| ORA-09975 ORA-09975, 00000, “kxfspini: Error Initializing SDI Process” Cause: The process was unable to attach to the SDI channel. Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation. |
| ORA-09976 ORA-09976, 00000, “skxfqdini: Error Creating Port” Cause: The process was unable to create a communications endpoint. Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation. |
| ORA-09977 ORA-09977, 00000, “skxfqhini: Error Connecting” Cause: The process was unable to connect to another endpoint. Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation. |
| ORA-09978 ORA-09978, 00000, “skxfqhdel: Error Disconnecting from another endpoint.” Cause: The process was unable to disconnect cleanly from another endpoint. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| ORA-09979 ORA-09979, 00000, “skxfqhsnd: Error Sending a message to another endpoint” Cause: The process was unable to send a message to an existing endpoint. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| ORA-09980 ORA-09980, 00000, “skxfqdrcv: Error Receiving a message from another endpoint” Cause: The process encountered an error while trying to receive a message. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| ORA-09981 ORA-09981, 00000, “skxfqdreg: Error Adding a page to the SDI buffer pool” Cause: The process was unable to add a page to the SDI buffer pool. Action: Correct the operating system error and retry the operation. |
| ORA-09982 ORA-09982, 00000, “skxfqddrg: Error Removing a page from the SDI buffer pool” Cause: The process was unable to remove a page to the SDI buffer pool. Action: Correct the operating system error and retry the operation. |
| ORA-09983 ORA-09983, 00000, “skxfidsht: Error shutting down SDI channel” Cause: The process was unable shut down the SDI channel Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance. |
| ORA-09984 ORA-09984, 00000, “SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist” Cause: file does not exist or is not accessible Action: Restart the instance to create the SGA definition file. |
| ORA-09985 ORA-09985, 00000, “SGA definition file could not be read” Cause: UNIX read() operation failed Action: check errno and take appropriate action. |
| ORA-09986 ORA-09986, 00000, “wrong number of bytes read from SGA definition file” Cause: Struct skgmsdef size differs from no. of bytes read from SGA file Action: Compare the two struct definitions and ensure that they are identical in size and structure. |
| ORA-09987 ORA-09987, 00000, “unable to attach to SGA in READ-ONLY mode” Cause: The instance is not up, or SGA segments are not read-accessible Action: Verify that the instance is up and read permissions for the SGA segments are set. |
| ORA-09988 ORA-09988, 00000, “error while detaching SGA” Cause: skgmsdef struct is corrupted and/or segment addresses are modified Action: Safely shut down instance and mount SGA segments again. |
| ORA-09989 ORA-09989, 00000, “attempt to use invalid skgmsdef struct pointer” Cause: Pointer to skgmsdef struct used without validating it Action: Assign a valid address to the skgmsdef struct pointer before using it. |
| ORA-10000 ORA-10000, 00000, “control file debug event, name ‘control_file’” Document: NO Cause: Action: |
| ORA-10001 ORA-10001, 00000, “control file crash event1″ Document: NO Cause: Action: |
| ORA-10002 ORA-10002, 00000, “control file crash event2″ Document: NO Cause: Action: |
| ORA-10003 ORA-10003, 00000, “control file crash event3″ Document: NO Cause: Action: |
| ORA-10004 ORA-10004, 00000, “block recovery testing – internal error” Document: NO Cause: Action: |
| ORA-10005 ORA-10005, 00000, “trace latch operations for debugging” Document: NO Cause: Action: Enable tracing for various latch operations Comment: level 1 – trace latch gets and frees level 2 – protect/unprotect latch recovery areas level 4 – trace multiple posts by processes when latch is freed level 8 – signal error on bad latch waits // |
| ORA-10006 ORA-10006, 00000, “block recovery testing – external error” Document: NO Cause: Action: |
| ORA-10007 ORA-10007, 00000, “log switch debug crash after new log select, thread %s” Document: NO Cause: Action: level 1 – closed thread only level 2 – open thread only level 3 – open or closed thread |
| ORA-10008 ORA-10008, 00000, “log switch debug crash after new log header write, thread %s” Document: NO Cause: Action: level 1 – closed thread only level 2 – open thread only level 3 – open or closed thread |
| ORA-10009 ORA-10009, 00000, “log switch debug crash after old log header write, thread %s” Document: NO Cause: Action: level 1 – closed thread only level 2 – open thread only level 3 – open or closed thread |
| ORA-10010 ORA-10010, 00000, “Begin Transaction” Cause: Action: |
| ORA-10011 ORA-10011, 00000, “End Transaction” Cause: Action: |
| ORA-10012 ORA-10012, 00000, “Abort Transaction” Cause: Action: |
| ORA-10013 ORA-10013, 00000, “Instance Recovery” Cause: Action: |
| ORA-10014 ORA-10014, 00000, “Roll Back to Save Point” Cause: Action: |
| ORA-10015 ORA-10015, 00000, “Undo Segment Recovery” Cause: Action: |
| ORA-10016 ORA-10016, 00000, “Undo Segment extend” Cause: Action: |
| ORA-10017 ORA-10017, 00000, “Undo Segment Wrap” Cause: Action: |
| ORA-10018 ORA-10018, 00000, “Data Segment Create” Cause: Action: |
| ORA-10019 ORA-10019, 00000, “Turn off data/space search cache” Cause: Action: |
| ORA-10020 ORA-10020, 00000, “partial link restored to linked list (KSG)” Cause: Action: |
| ORA-10021 ORA-10021, 00000, “KST event to trace control file header writes and reads” Cause: Action: Not set by default. |
| ORA-10022 ORA-10022, 00000, “trace ktsgsp” Cause: Action: |
| ORA-10023 ORA-10023, 00000, “Create Save Undo Segment” Cause: Action: |
| ORA-10024 ORA-10024, 00000, “Write to Save Undo” Cause: Action: |
| ORA-10026 ORA-10026, 00000, “Apply Save Undo” Cause: Action: |
| ORA-10027 ORA-10027, 00000, “Specify Deadlock Trace Information to be Dumped” Cause: Action: The level is a bitmask that can be used as follows: 0×01 – Do NOT produce a processstate (default is to dump this) 0×02 – Dump a systemstate 0×04 – Dump short stacks of all processes // |
| ORA-10028 ORA-10028, 00000, “Dump trace information during lock / resource latch cleanup” Cause: Action: The level is a bitmask that can be used as follows: 0×01 – Dump information during resource cleanup 0×02 – Dump information during lock cleanup // |
| ORA-10029 ORA-10029, 00000, “session logon (KSU)” Cause: Action: |
| ORA-10030 ORA-10030, 00000, “session logoff (KSU)” Cause: Action: |
| ORA-10031 ORA-10031, 00000, “sort debug event (S*)” Cause: Document: NO Action: Set this event only under the supervision of Oracle development. Trace level is a bitfield. // LEVEL ACTION //————————————————————————— 0×0001 Trace sort auto memory management requirements 0×0002 Dump sort subheaps before freeing or resetting 0×0004 Trace use of new vs old sort 0×0008 Reserved for sort IO tracing // |
| ORA-10032 ORA-10032, 00000, “sort statistics (SOR*)” Cause: Action: |
| ORA-10033 ORA-10033, 00000, “sort run information (SRD*/SRS*)” Cause: Action: |
| ORA-10035 ORA-10035, 00000, “Write parse failures to alert log file” Cause: |
| ORA-10036 ORA-10036, 00000, “create remote row source (QKANET)” Cause: Action: |
| ORA-10037 ORA-10037, 00000, “allocate remote row source (QKARWS)” Cause: Action: |
| ORA-10038 ORA-10038, 00000, “dump row source tree (QBADRV)” Cause: Action: |
| ORA-10039 ORA-10039, 00000, “type checking (OPITCA)” Cause: Action: |
| ORA-10040 ORA-10040, 00000, “disable result-cache” Cause: Action: |
| ORA-10041 ORA-10041, 00000, “dump undo records skipped” Cause: Action: |
| ORA-10043 ORA-10043, 00000, “check consistency of owner/waiter/converter lists in KSQ” Cause: Action: |
| ORA-10044 ORA-10044, 00000, “free list undo operations” Cause: Action: |
| ORA-10045 ORA-10045, 00000, “free list update operations – ktsrsp, ktsunl” Cause: Action: |
| ORA-10046 ORA-10046, 00000, “enable SQL statement timing” Cause: Action: |
| ORA-10047 ORA-10047, 00000, “trace switching of sessions” Cause: Action: |
| ORA-10048 ORA-10048, 00000, “Undo segment shrink” Cause: Action: |
| ORA-10049 ORA-10049, 00000, “protect library cache memory heaps” Cause: Action: Use the OS memory protection (if available) to protect library cache memory heaps that are pinned. |
| ORA-10050 ORA-10050, 00000, “sniper trace” Cause: Action: |
| ORA-10051 ORA-10051, 00000, “trace OPI calls” Cause: Action: |
| ORA-10052 ORA-10052, 00000, “don’t clean up obj$” Cause: Action: |
| ORA-10053 ORA-10053, 00000, “CBO Enable optimizer trace” Cause: Action: |
| ORA-10054 ORA-10054, 00000, “CBO Enable optimizer trace for recursive statement (RPI)” Cause: Action: |
| ORA-10056 ORA-10056, 00000, “dump analyze stats (kdg)” Cause: Action: |
| ORA-10057 ORA-10057, 00000, “suppress file names in error messages” Cause: Action: |
| ORA-10058 ORA-10058, 00000, “use table scan cost in tab$.spare1″ Cause: Action: |
| ORA-10059 ORA-10059, 00000, “simulate error in logfile create/clear” Cause: Action: |
| ORA-10060 ORA-10060, 00000, “CBO Enable predicate dump” Cause: Action: |
| ORA-10061 ORA-10061, 00000, “disable SMON from cleaning temp segment” Cause: Action: |
| ORA-10062 ORA-10062, 00000, “disable usage of OS Roles in osds” Cause: Action: |
| ORA-10063 ORA-10063, 00000, “disable usage of DBA and OPER privileges in osds” Cause: Action: |
| ORA-10064 ORA-10064, 00000, “thread enable debug crash level %s, thread %s” Document: NO Cause: Action: level 1 – after new current log header written level 2 – after current log committed level 3 – after redo generation complete |
| ORA-10065 ORA-10065, 00000, “limit library cache dump information for state object dump” Document: NO Cause: Action: level 1 – minimal (only the address of state objects) level 2 – little more (no object details) level 3 – normal |
| ORA-10066 ORA-10066, 00000, “simulate failure to verify file” Document: NO Cause: Action: level is file number to fail verification |
| ORA-10067 ORA-10067, 00000, “force redo log checksum errors – block number” Document: NO Cause: Action: level is block number to corrupt |
| ORA-10068 ORA-10068, 00000, “force redo log checksum errors – file number” Document: NO Cause: Action: level is file number to corrupt |
| ORA-10070 ORA-10070, 00000, “force datafile checksum errors – block number” Document: NO Cause: Action: level is block number to corrupt |
| ORA-10071 ORA-10071, 00000, “force datafile checksum errors – file number” Document: NO Cause: Action: level is file number to corrupt |
| ORA-10073 ORA-10073, 00000, “latch cleanup tracing” Document: NO Cause: Action: Enable latch cleanup tracing. Comment: level 1 – PMON cleanup, in-flux latches only level 2 – PMON cleanup, all latches level 3 – all cleanup // |
| ORA-10074 ORA-10074, 00000, “default trace function mask for kst” Cause: Action: |
| ORA-10075 ORA-10075, 00000, “CBO Disable outer-join to regular join conversion” Cause: Action: |
| ORA-10076 ORA-10076, 00000, “CBO Enable cartesian product join costing” Cause: Action: |
| ORA-10077 ORA-10077, 00000, “CBO Disable view-merging optimization for outer-joins” Cause: Action: |
| ORA-10078 ORA-10078, 00000, “CBO Disable constant predicate elimination optimization” Cause: Action: |
| ORA-10079 ORA-10079, 00000, “trace data sent/received via SQL*Net” Cause: Action: level 1 – trace network ops to/from client level 2 – in addition to level 1, dump data level 4 – trace network ops to/from dblink level 8 – in addition to level 4, dump data |
| ORA-10080 ORA-10080, 00000, “dump a block on a segment list which cannot be exchanged” Cause: Action: |
| ORA-10081 ORA-10081, 00000, “segment High Water Mark has been advanced” Cause: Action: |
| ORA-10082 ORA-10082, 00000, “free list head block is the same as the last block” Cause: Action: |
| ORA-10084 ORA-10084, 00000, “free list becomes empty” Cause: Action: |
| ORA-10085 ORA-10085, 00000, “free lists have been merged” Cause: Action: |
| ORA-10086 ORA-10086, 00000, “CBO Enable error if kko and qka disagree on oby sort” Cause: Action: |
| ORA-10087 ORA-10087, 00000, “disable repair of media corrupt data blocks” Document: NO Cause: Action: |
| ORA-10088 ORA-10088, 00000, “CBO Disable new NOT IN optimization” Document: NO Cause: Action: |
| ORA-10089 ORA-10089, 00000, “CBO Disable index sorting” Document: NO Cause: Action: |
| ORA-10090 ORA-10090, 00000, “invoke other events before crash recovery” Document: NO Cause: Action: |
| ORA-10091 ORA-10091, 00000, “CBO Disable constant predicate merging” Cause: Action: |
| ORA-10092 ORA-10092, 00000, “CBO Disable hash join” Cause: Action: |
| ORA-10093 ORA-10093, 00000, “CBO Enable force hash joins” Cause: Action: |
| ORA-10094 ORA-10094, 00000, “before resizing a data file” Document: NO Cause: Action: |
| ORA-10095 ORA-10095, 00000, “dump debugger commands to trace file” Document: NO Cause: Action: |
| ORA-10096 ORA-10096, 00000, “after the cross instance call when resizing a data file” Document: NO Cause: Action: |
| ORA-10097 ORA-10097, 00000, “after generating redo when resizing a data file” Document: NO Cause: Action: |
| ORA-10098 ORA-10098, 00000, “after the OS has increased the size of a data file” Document: NO Cause: Action: |
| ORA-10099 ORA-10099, 00000, “after updating the file header with the new file size” Document: NO Cause: Action: |
| ORA-10100 ORA-10100, 00000, “after the OS has decreased the size of a data file” Document: NO Cause: Action: |
| ORA-10101 ORA-10101, 00000, “DBWR refresh fails on cross instance resize call” Document: NO Cause: Action: |
| ORA-10102 ORA-10102, 00000, “switch off anti-joins” Cause: Action: |
| ORA-10103 ORA-10103, 00000, “CBO Disable hash join swapping” Cause: Action: |
| ORA-10104 ORA-10104, 00000, “dump hash join statistics to trace file” Cause: Action: |
| ORA-10105 ORA-10105, 00000, “CBO Enable constant pred trans and MPs w WHERE-clause” Cause: Action: |
| ORA-10106 ORA-10106, 00000, “CBO Disable evaluating correlation pred last for NOT IN” Cause: Action: |
| ORA-10107 ORA-10107, 00000, “CBO Always use bitmap index” Cause: Action: |
| ORA-10108 ORA-10108, 00000, “CBO Don’t use bitmap index” Cause: Action: |
| ORA-10109 ORA-10109, 00000, “CBO Disable move of negated predicates” Cause: Action: |
| ORA-10110 ORA-10110, 00000, “CBO Try index rowid range scans” Cause: Action: |
| ORA-10111 ORA-10111, 00000, “Bitmap index creation switch” Cause: Action: |
| ORA-10112 ORA-10112, 00000, “Bitmap index creation switch” Cause: Action: |
| ORA-10113 ORA-10113, 00000, “Bitmap index creation switch” Cause: Action: |
| ORA-10114 ORA-10114, 00000, “Bitmap index creation switch” Cause: Action: |
| ORA-10115 ORA-10115, 00000, “CBO Bitmap optimization use maximal expression” Cause: Action: |
| ORA-10116 ORA-10116, 00000, “CBO Bitmap optimization switch” Cause: Action: |
| ORA-10117 ORA-10117, 00000, “CBO Disable new parallel cost model ” Cause: Action: |
| ORA-10118 ORA-10118, 00000, “CBO Enable hash join costing ” Cause: Action: |
| ORA-10119 ORA-10119, 00000, “QKA Disable GBY sort elimination” Cause: Action: |
| ORA-10120 ORA-10120, 00000, “generate relative file # different from absolute” Cause: Action: |
| ORA-10121 ORA-10121, 00000, “CBO Don’t sort bitmap chains” Cause: Action: |
| ORA-10122 ORA-10122, 00000, “Disable transformation of count(col) to count(*)” Cause: Action: |
| ORA-10124 ORA-10124, 00000, “Force creation of segmented arrays by kscsAllocate” Cause: Action: |
| ORA-10125 ORA-10125, 00000, “Disable remote sort elimination” Cause: Action: |
| ORA-10126 ORA-10126, 00000, “Debug oracle java xa” Cause: Action: |
| ORA-10127 ORA-10127, 00000, “Disable remote query block operation” Cause: Action: |
| ORA-10128 ORA-10128, 00000, “Dump Partition Pruning Information” Cause: Action: set this event only under the supervision of Oracle development // LEVEL ACTION //————————————————————————— 0×0001 dump pruning decriptor for each partitioned object 0×0002 dump partition iterators 0×0004 dump optimizer decisions about partition-wise join 0×0008 dump rowid range scan pruning information |
| ORA-10129 ORA-10129, 00000, “Alter histogram lookup for remote queries” Cause: Action: |
| ORA-10130 ORA-10130, 00000, “sort disable readaheads” Cause: Action: |
| ORA-10131 ORA-10131, 00000, “CONNECT BY debug event” Document: NO Cause: Action: Set this event only under the supervision of Oracle development. Trace level is a bit field. LEVEL ACTION |
| ORA-10132 ORA-10132, 00000, “dump plan after compilation” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10133 ORA-10133, 00000, “testing for SQL Memory Management” Cause: Action: never set this event // LEVEL ACTION //————————————————————————— 0×0001 do not unregister work areas at instance level |
| ORA-10134 ORA-10134, 00000, “tracing for SQL Memory Management for session” Cause: Action: never set this event // This event can be turned on globally by seting trace name sqlmem_tracing with the same set of levels with bit one set to 1 // LEVEL ACTION //————————————————————————— 0×0001 Not used (used for global setting) 0×0002 IMM level register/unregister |
| ORA-10135 ORA-10135, 00000, “CBO do not count 0 rows partitions” Cause: Action: |
| ORA-10136 ORA-10136, 00000, “CBO turn off fix for bug 1089848″ Cause: Action: |
| ORA-10137 ORA-10137, 00000, “CBO turn off fix for bug 1344111″ Cause: Action: |
| ORA-10138 ORA-10138, 00000, “CBO turn off fix for bug 1577003″ Cause: Action: |
| ORA-10139 ORA-10139, 00000, “CBO turn off fix for bug 1386119″ Cause: Action: |
| ORA-10140 ORA-10140, 00000, “CBO turn off fix for bug 1332980″ Cause: Action: |
| ORA-10141 ORA-10141, 00000, “CBO disable additional keys for inlist in bitmap optimization” Cause: Action: |
| ORA-10142 ORA-10142, 00000, “CBO turn off advanced OR-expansion checks” Cause: Action: |
| ORA-10143 ORA-10143, 00000, “CBO turn off hints” Cause: Action: |
| ORA-10144 ORA-10144, 00000, “CBO turn off cost based selection of bji over bsj subquery” Cause: Action: |
| ORA-10145 ORA-10145, 00000, “test auditing network errors” Cause: Action: |
| ORA-10146 ORA-10146, 00000, “enable Oracle TRACE collection” Cause: Action: Comment: This event is obsoleted, and can be reused for some other purpose although some customer applications which used to rely on Oracle Trace may still have it enabled by mistake |
| ORA-10147 ORA-10147, 00000, “enable join push through UNION view” Cause: Action: |
| ORA-10149 ORA-10149, 00000, “allow the creation of constraints with illegal date constants” Cause: Action: |
| ORA-10150 ORA-10150, 00000, “import exceptions” Document: NO Cause: Action: This should never be set by users. It is used by import to allow certain commands to succeed, when for normal users they would fail. An example is to allow grants on invalid views. |
| ORA-10152 ORA-10152, 00000, “CBO don’t consider function costs in plans” Cause: Action: |
| ORA-10153 ORA-10153, 00000, “Switch to use public synonym if private one does not translate” Cause: Action: |
| ORA-10154 ORA-10154, 00000, “Switch to disallow synonyms in DDL statements” Cause: Action: |
| ORA-10155 ORA-10155, 00000, “CBO disable generation of transitive OR-chains” Cause: Action: |
| ORA-10156 ORA-10156, 00000, “CBO disable index fast full scan” Cause: Action: |
| ORA-10157 ORA-10157, 00000, “CBO disable index access path for in-list” Cause: Action: |
| ORA-10158 ORA-10158, 00000, “CBO preserve predicate order in post-filters” Cause: Action: |
| ORA-10159 ORA-10159, 00000, “CBO disable order-by sort pushdown into domain indexes” Cause: Action: |
| ORA-10160 ORA-10160, 00000, “CBO disable use of join index” Cause: Action: |
| ORA-10161 ORA-10161, 00000, “CBO recursive semi-join on/off-switch” Cause: Action: |
| ORA-10162 ORA-10162, 00000, “CBO join-back elimination on/off-switch” Cause: Action: |
| ORA-10163 ORA-10163, 00000, “CBO join-back elimination on/off-switch” Cause: Action: |
| ORA-10164 ORA-10164, 00000, “CBO disable subquery-adjusted cardinality fix” Cause: Action: |
| ORA-10165 ORA-10165, 00000, “mark session to be aborted during shutdown normal” Cause: Action: Turn on this event in a session to mark the session as abortable so that it can be killed during a shutdown normal. It is provided for the Oracle Enterprise Manager. |
| ORA-10166 ORA-10166, 00000, “trace long operation statistics updates” Cause: Action: |
| ORA-10167 ORA-10167, 00000, “CBO use old index MIN/MAX optimization” Cause: Action: |
| ORA-10168 ORA-10168, 00000, “CBO disable single-table predicate predicate generation” Cause: Action: |
| ORA-10169 ORA-10169, 00000, “CBO disable histograms for multi partitions” Cause: Action: |
| ORA-10170 ORA-10170, 00000, “CBO use old bitmap costing” Cause: Action: |
| ORA-10171 ORA-10171, 00000, “CBO disable transitive join predicates” Cause: Action: |
| ORA-10172 ORA-10172, 00000, “CBO force hash join back” Cause: Action: |
| ORA-10173 ORA-10173, 00000, “Dynamic Sampling time-out error” Cause: Action: |
| ORA-10174 ORA-10174, 00000, “view join-back elimination switch” Cause: Action: |
| ORA-10175 ORA-10175, 00000, “CBO star transformation switch” Cause: Action: |
| ORA-10176 ORA-10176, 00000, “CBO colocated join switch” Cause: Action: |
| ORA-10177 ORA-10177, 00000, “CBO colocated join switch” Cause: Action: |
| ORA-10178 ORA-10178, 00000, “CBO turn off hash cluster filtering through memcmp” Cause: Action: |
| ORA-10179 ORA-10179, 00000, “CBO turn off transitive predicate replacement” Cause: Action: |
| ORA-10180 ORA-10180, 00000, “temp table transformation print error messages” Cause: Action: |
| ORA-10181 ORA-10181, 00000, “CBO disable multi-column in-list processing” Cause: Action: |
| ORA-10182 ORA-10182, 00000, “CBO disable generation of implied predicates” Cause: Action: |
| ORA-10183 ORA-10183, 00000, “CBO disable cost rounding” Cause: Action: |
| ORA-10184 ORA-10184, 00000, “CBO disable OR-exp if long inlist on bitmap column” Cause: Action: |
| ORA-10185 ORA-10185, 00000, “CBO force index joins” Cause: Action: |
| ORA-10186 ORA-10186, 00000, “CBO disable index join” Cause: Action: |
| ORA-10187 ORA-10187, 00000, “CBO additional index join switch” Cause: Action: |
| ORA-10188 ORA-10188, 00000, “CBO additional index join switch” Cause: Action: |
| ORA-10189 ORA-10189, 00000, “CBO turn off FFS null fix” Cause: Action: |
| ORA-10190 ORA-10190, 00000, “Analyze use old frequency histogram collection and density” Cause: Action: |
| ORA-10191 ORA-10191, 00000, “Avoid conversion of in-lists back to OR-expanded form” Cause: Action: |
| ORA-10192 ORA-10192, 00000, “nopushdown when number of groups exceed number of rows” Cause: Action: |
| ORA-10193 ORA-10193, 00000, “Force repeatable sampling with specified seed” Cause: Action: |
| ORA-10194 ORA-10194, 00000, “CBO disable new LIKE selectivity heuristic” Cause: Action: |
| ORA-10195 ORA-10195, 00000, “CBO don’t use check constraints for transitive predicates” Cause: Action: |
| ORA-10196 ORA-10196, 00000, “CBO disable index skip scan” Cause: Action: |
| ORA-10197 ORA-10197, 00000, “CBO force index skip scan” Cause: Action: |
| ORA-10199 ORA-10199, 00000, “set parameter in session” Cause: Action: |
| ORA-10200 ORA-10200, 00000, “consistent read buffer status” Cause: Action: |
| ORA-10201 ORA-10201, 00000, “consistent read undo application” Cause: Action: |
| ORA-10202 ORA-10202, 00000, “consistent read block header” Cause: Action: |
| ORA-10203 ORA-10203, 00000, “block cleanout” Cause: Action: |
| ORA-10204 ORA-10204, 00000, “signal recursive extend” Cause: Action: |
| ORA-10205 ORA-10205, 00000, “row cache debugging” Cause: Action: |
| ORA-10206 ORA-10206, 00000, “transaction table consistent read” Cause: Action: |
| ORA-10207 ORA-10207, 00000, “consistent read transactions’ status report” Cause: Action: |
| ORA-10208 ORA-10208, 00000, “consistent read loop check” Cause: Action: |
| ORA-10209 ORA-10209, 00000, “enable simulated error on control file” Cause: Action: |
| ORA-10210 ORA-10210, 00000, “check data block integrity” Cause: Action: |
| ORA-10212 ORA-10212, 00000, “check cluster integrity” Cause: Action: |
| ORA-10213 ORA-10213, 00000, “crash after control file write” Cause: Action: |
| ORA-10214 ORA-10214, 00000, “simulate write errors on control file” Cause: Action: |
| ORA-10215 ORA-10215, 00000, “simulate read errors on control file” Cause: Action: |
| ORA-10216 ORA-10216, 00000, “dump control file header” Cause: Action: |
| ORA-10217 ORA-10217, 00000, “debug sequence numbers” Cause: Action: |
| ORA-10218 ORA-10218, 00000, “dump uba of applied undo” Cause: Action: |
| ORA-10219 ORA-10219, 00000, “monitor multi-pass row locking” Cause: Action: |
| ORA-10220 ORA-10220, 00000, “show updates to the transaction table” Cause: Action: |
| ORA-10221 ORA-10221, 00000, “show changes done with undo” Cause: Action: |
| ORA-10222 ORA-10222, 00000, “row cache” Cause: Action: |
| ORA-10223 ORA-10223, 00000, “transaction layer – turn on verification codes” Cause: Action: |
| ORA-10224 ORA-10224, 00000, “index block split/delete trace” Cause: Action: |
| ORA-10225 ORA-10225, 00000, “free/used extent row cache” Cause: Action: |
| ORA-10226 ORA-10226, 00000, “trace CR applications of undo for data operations” Cause: Action: |
| ORA-10227 ORA-10227, 00000, “verify (multi-piece) row structure” Cause: Action: |
| ORA-10228 ORA-10228, 00000, “trace application of redo by kcocbk” Cause: Action: |
| ORA-10229 ORA-10229, 00000, “simulate I/O error against datafiles” Cause: Action: |
| ORA-10230 ORA-10230, 00000, “KSFD block repair test event” Cause: Action: Each level is dedicated to a particular ksfd client. When this event is set, clients corresponding to the level simulate block verification failure. |
| ORA-10231 ORA-10231, 00000, “skip corrupted blocks on _table_scans_” Cause: Action: such blocks are skipped in table scans, and listed in trace files |
| ORA-10232 ORA-10232, 00000, “dump corrupted blocks symbolically when kcbgotten” Cause: Action: puts corrupted block in trace file |
| ORA-10233 ORA-10233, 00000, “skip corrupted blocks on index operations” Cause: Action: skip corrupted data and/or index blocks during index scans. information is logged to a trace file. |
| ORA-10234 ORA-10234, 00000, “trigger event after calling kcrapc to do redo N times” Document: NO Cause: Action: creates a file named ‘crash’ |
| ORA-10235 ORA-10235, 00000, “check memory manager internal structures” Cause: Action: |
| ORA-10236 ORA-10236, 00000, “dump redo on object no. or block type mismatch errors 1410/8103″ Document: NO Cause: Action: |
| ORA-10237 ORA-10237, 00000, “simulate ^C (for testing purposes)” Cause: Action: |
| ORA-10238 ORA-10238, 00000, “instantiation manager” Cause: Action: |
| ORA-10239 ORA-10239, 00000, “multi-instance library cache manager” Cause: Action: |
| ORA-10240 ORA-10240, 00000, “dump dba’s of blocks that we wait for” Cause: Action: |
| ORA-10241 ORA-10241, 00000, “remote SQL execution tracing/validation” Cause: Action: Level > 0 dump SQL generated for remote execution (OPIX) Level > 1 validate RPCs in SELECT statements |
| ORA-10242 ORA-10242, 00000, “suppress OER 2063 (for testing distrib w/o different error log)” Cause: Action: |
| ORA-10243 ORA-10243, 00000, “simulated error for test %s of K2GTAB latch cleanup” Cause: levels 1..6 for insert, 7..11 for delete Action: |
| ORA-10244 ORA-10244, 00000, “make tranids in error msgs print as 0.0.0 (for testing)” Cause: also makes “alter system enable distributed recovery” synchronous Action: |
| ORA-10245 ORA-10245, 00000, “Testing event used by server I/O ksfd/ksfq module” Cause: Action: |
| ORA-10246 ORA-10246, 00000, “print trace of PMON actions to trace file” Cause: Action: |
| ORA-10247 ORA-10247, 00000, “Turn on scgcmn tracing. (VMS ONLY)” Cause: Action: |
| ORA-10248 ORA-10248, 00000, “turn on tracing for dispatchers” Cause: Action: |
| ORA-10249 ORA-10249, 00000, “turn on tracing for multi-stated servers” Cause: Action: |
| ORA-10250 ORA-10250, 00000, “Trace all allocate and free calls to the topmost SGA heap” Cause: Action: |
| ORA-10251 ORA-10251, 00000, “check consistency of transaction table and undo block” MERGE: 10235 RENUMBERED TO 10251 Cause: Action: |
| ORA-10252 ORA-10252, 00000, “shared IO pool error simulation” Cause: Action: level specifies number of IOs after which an error will be simulated |
| ORA-10254 ORA-10254, 00000, “trace cross-instance calls” Cause: Action: |
| ORA-10255 ORA-10255, 00000, “pl/sql parse checking” Cause: Action: sends all dml statements to pl/sql for parse and semantic check |
| ORA-10257 ORA-10257, 00000, “trace shared server load balancing” Cause: Action: |
| ORA-10258 ORA-10258, 00000, “force shared servers to be chosen round-robin” Cause: Action: |
| ORA-10259 ORA-10259, 00000, “get error message text from remote using explicit call” Cause: for npigem coverage testing (normally called only for V5 remote) Action: |
| ORA-10261 ORA-10261, 00000, “Limit the size of the PGA heap” Cause: the limit is one kilobyte times the level of the event. If the pga grows bigger than this signal an internal error. Action: |
| ORA-10262 ORA-10262, 00000, “Don’t check for memory leaks” Cause: Setting this event to level one causes memory leak checking to be disabled. Setting this event to any other non-zero number allows that number to be used as a threshold value when checking for memory leaks in the PGA, SGA, and UGA heaps. Action: |
| ORA-10263 ORA-10263, 00000, “Don’t free empty PGA heap extents” Cause: This is useful for debugging since watchpoints are lost on free Action: |
| ORA-10265 ORA-10265, 00000, “Keep random system generated output out of error messages” Cause: so test system files don’t diff Action: |
| ORA-10266 ORA-10266, 00000, “Trace OSD stack usage” Cause: Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk(). Action: |
| ORA-10267 ORA-10267, 00000, “Inhibit KSEDMP for testing” Cause: Some tests may generate internal or fatal errors on purpose. |
| ORA-10268 ORA-10268, 00000, “Don’t do forward coalesce when deleting extents” Cause: setting this event keeps kts from coalescing forward at each extent when dropping a temp segment. Action: |
| ORA-10269 ORA-10269, 00000, “Don’t do coalesces of free space in SMON” Cause: setting this event prevents SMON from doing free space coalesces |
| ORA-10270 ORA-10270, 00000, “Debug shared cursors” Cause: Enables debugging code in shared cursor management modules Action: |
| ORA-10271 ORA-10271, 00000, “distributed transaction after COLLECT” Cause: Action: |
| ORA-10272 ORA-10272, 00000, “distributed transaction before PREPARE” Cause: Action: |
| ORA-10273 ORA-10273, 00000, “distributed transaction after PREPARE” Cause: Action: |
| ORA-10274 ORA-10274, 00000, “distributed transaction before COMMIT” Cause: Action: |
| ORA-10275 ORA-10275, 00000, “distributed transaction after COMMIT” Cause: Action: |
| ORA-10276 ORA-10276, 00000, “distributed transaction before FORGET” Cause: Action: |
| ORA-10277 ORA-10277, 00000, “Cursor sharing (or not) related event (used for testing)” Cause: Action: |
| ORA-10278 ORA-10278, 00000, “Internal testing” Cause: Action: |
| ORA-10279 ORA-10279, 00000, “Simulate block corruption in kdb4chk” Cause: Action: |
| ORA-10280 ORA-10280, 00000, “Internal testing – segmentation fault during crash recovery” Cause: Action: |
| ORA-10281 ORA-10281, 00000, “maximum time to wait for process creation” Cause: used to override the default SPMXWAIT, level = timeout in sec. Action: |
| ORA-10282 ORA-10282, 00000, “Inhibit signalling of other backgrounds when one dies” Cause: Used in KSB Action: |
| ORA-10284 ORA-10284, 00000, “simulate zero/infinite asynch I/O buffering” Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green) Action: |
| ORA-10285 ORA-10285, 00000, “Simulate control file header corruption” Cause: Action: If set, will cause control file header verification to fail |
| ORA-10286 ORA-10286, 00000, “Simulate control file open error” Cause: Action: If set, will cause the next control file open to have an error |
| ORA-10287 ORA-10287, 00000, “Simulate archiver error” Cause: Action: If set, next archive log will generate error |
| ORA-10288 ORA-10288, 00000, “Do not check block type in ktrget” Cause: Action: If set, don’t do type check in ktrget. This is a work-around for databases that have 0 as block type in some data blocks. |
| ORA-10289 ORA-10289, 00000, “Do block dumps to trace file in hex rather than fromatted” Cause: Action: If set, don’t do formatted block dumps. This is a work-around for block dump routines that accvio when given badly corrupted blocks. It may also be useful for cases where the type is wrong. |
| ORA-10290 ORA-10290, 00000, “Internal sequence tracing event” Cause: Action: Internal Event – Should not be set unless directed by RDBMS DEV |
| ORA-10291 ORA-10291, 00000, “die in tbsdrv to test control file undo” Cause: Action: If this event is set, error OERI(10291) is signalled when issueing tablespace commands. The control file undo should be applied returning the control file to its previous state. |
| ORA-10292 ORA-10292, 00000, “hang analysis trace event” Document: NO Cause: Action: Enable validation of hang analysis callbacks Comment: The following levels may be combined: 0×1 – dump errors to trace file through ksdwrf 0×2 – dump errors to trace file as ORA-600 + 0×1 0×4 – check for involuntary events without callbacks |
| ORA-10293 ORA-10293, 0000, “trace log switch media recovery checkpoints” Document: NO Cause: Action: Print alert log timestamps for the start and end of each log switch checkpoint during media recovery. This timing may prove useful in debugging recovery performance problems. |
| ORA-10294 ORA-10294, 00000, “ksrpc tracing” Cause: Action: If this event is set then ksrpc module generates tracing on each remote transfer |
| ORA-10295 ORA-10295, 00000, “die after file header update durning cf xact” Document: NO Cause: Action: If this event is set then some file header updates will be followed by an error 10295 to abort the command before the control file xact commits. |
| ORA-10296 ORA-10296, 00000, “disable ORA-379″ Cause: Action: If this event is set then we will not signal ORA-379 for buffer cache deadlocks when all buffers in the cache are pinned. |
| ORA-10297 ORA-10297, 00000, “shared I/O pool tracing” Document: NO Cause: Action: If this event is set, then kcbi tracing is enabled. Internal use. |
| ORA-10298 ORA-10298, 00000, “ksfd i/o tracing” Cause: Action: If this event is set then ksfd module generates tracing for each i/o request |
| ORA-10299 ORA-10299, 00000, “Trace prefetch tracking decisions made by CKPT” |
| ORA-10300 ORA-10300, 00000, “Distributed transaction tracing” Document: NO Cause: Action: Set this event only under the supervision of Oracle development Comment: This event will trace the history of KTD actions level: 0 = always |
| ORA-10301 ORA-10301, 0000, “Enable LCK timeout table consistency check” Cause: Action: |
| ORA-10302 ORA-10302, 00000, “trace create or drop internal trigger” Document: NO Cause: Action: |
| ORA-10303 ORA-10303, 00000, “trace loading of library cache for internal triggers” Document: NO Cause: Action: |
| ORA-10304 ORA-10304, 00000, “trace replication trigger” Document: NO Cause: Action: |
| ORA-10305 ORA-10305, 00000, “trace updatable materialized view trigger” Document: NO Cause: Action: |
| ORA-10306 ORA-10306, 00000, “trace materialized view log trigger” Document: NO Cause: Action: |
| ORA-10307 ORA-10307, 00000, “trace RepCat execution” Document: NO Cause: Action: |
| ORA-10308 ORA-10308, 00000, “replication testing event” Document: NO Cause: Action: |
| ORA-10309 ORA-10309, 00000, “Trigger Debug event” Document: NO Cause: Action: Comment: This event replaces the earlier event number 10250 which had multiple definitions |
| ORA-10310 ORA-10310, 00000, “trace synchronous change table trigger” Document: NO Cause: Action: |
| ORA-10311 ORA-10311, 00000, “Disable Flashback Table Timestamp checking” Document: NO Cause: Action: |
| ORA-10312 ORA-10312, 00000, “Allow disable to log rows into the mapping table” Document: NO Cause: Action: |
| ORA-10314 ORA-10314, 00000, “Enable extra stats gathering for CR” Document: NO Cause: Action: |
| ORA-10316 ORA-10316, 00000, “Events for extensible txn header, non zero ext header size” Document: NO Cause: Action: |
| ORA-10317 ORA-10317, 00000, “Events for extensible txn header, zero ext header size” Document: NO Cause: Action: |
| ORA-10318 ORA-10318, 00000, “Trace extensible txn header movements” Document: NO Cause: Action: |
| ORA-10319 ORA-10319, 00000, “Trace PGA statistics maintenance” Cause: Action: set this event only under the supervision of Oracle development // LEVEL ACTION //————————————————————————— 0×0001 dump message in trace file when PGA stats are diverging 0×0002 trace top-level PGA allocation and deallocation 0×0004 always check if full/incremental stats are in sync // |
| ORA-10320 ORA-10320, 0000, “Enable data layer (kdtgrs) tracing of space management calls” Cause: Action: |
| ORA-10321 ORA-10321, 0000, “Datafile header verification debug failure.” Document: NO Cause: Action: For testing purposes only. Simulates a datafile header verification error. |
| ORA-10322 ORA-10322, 00000, “CBO don’t simplify inlist predicates” Cause: Action: |
| ORA-10323 ORA-10323, 0000, “before committing an add datafile command” Cause: Action: |
| ORA-10324 ORA-10324, 0000, “Enable better checking of redo logs errors” Cause: Action: Raises internal errors when there are redo log errors Comment: Raises internal errors when there are redo log errors |
| ORA-10325 ORA-10325, 0000, “Trace control file record section expand and shrink operations” Document: NO Cause: Action: trace control file record section expand and shrink operations to the alert file // |
| ORA-10326 ORA-10326, 00000, “clear logfile debug crash at %s, log %s” Document: NO Cause: Action: level 1 – after prepare, before clearing the log members level 2 – after clearing the log members, before final cf xaction level 3 – just before clearing member 1 level 4 – just before clearing member 2 |
| ORA-10327 ORA-10327, 00000, “simulate ORA-00235 error for testing” Document: NO Cause: Action: // |
| ORA-10328 ORA-10328, 00000, “disable first-to-mount split-brain error, for testing” Document: NO Cause: Action: for testing only. // |
| ORA-10329 ORA-10329, 00000, “simulate out-of-memory error during first pass of recovery” Document: NO Cause: Action: for testing only. // |
| ORA-10330 ORA-10330, 00000, “clear MTTR statistics in checkpoint progress record” Document: NO Cause: Action: clear MTTR statistics in this thread // |
| ORA-10331 ORA-10331, 00000, “simulate resilvering during recovery” Document: NO Cause: Action: for testing only. // |
| ORA-10332 ORA-10332, 00000, “force ALTER SYSTEM QUIESCE RESTRICTED command to fail” Document: NO Cause: Action: for testing only. // |
| ORA-10333 ORA-10333, 00000, “dump MTTR statistics each time it is updated” Document: NO Cause: Action: dump MTTR statistics in this thread each time it is updated // |
| ORA-10334 ORA-10334, 00000, “force FG to wait to be killed during MTTR advisory simulation” Document: NO Cause: Action: for testing only. // |
| ORA-10335 ORA-10335, 00000, “reserved for recovery layer for testing purpose” Document: NO Cause: Action: |
| ORA-10336 ORA-10336, 00000, “Do remote object transfer using remote SQL” Cause: Action: // |
| ORA-10337 ORA-10337, 00000, “enable padding owner name in slave sql” // Document: NO Cause: owner name is not padded by default in slave sql Action: pad owner name during generation of slave sql // Comment: applicable only for explain plan queries(for testing purposes) |
| ORA-10338 ORA-10338, 00000, “CBO don’t use inlist iterator with function-based indexes” Cause: Action: |
| ORA-10339 ORA-10339, 00000, “CBO disable DECODE simplification” Cause: Action: |
| ORA-10340 ORA-10340, 00000, “Buffer queues sanity check for corrupted buffers” // Document: NO // Cause: Action: Check all buffer queues for corrupted buffer every 5 minutes // |
| ORA-10341 ORA-10341, 00000, “Simulate out of PGA memory in DBWR during object reuse” Cause: Action: checks that DBWR can still perform invalidatino Comment: only used during testing |
| ORA-10342 ORA-10342, 00000, “Raise unknown exception in ACQ_ADD when checkpointing” Cause: Action: should cause process to dump trace file and die Comment: This event is obsoleted, and can be reused for another test. |
| ORA-10343 ORA-10343, 00000, “Raise an out of memory exception-OER 4031 in ACQ_ADD” Cause: Action: For Backgrounds, try to handle checkpoint using reserved entries Comment: Only enabled during testing |
| ORA-10344 ORA-10344, 00000, “reserved for simulating object hash reorganization” Document: NO Cause: Action: Set this to trigger obj hash table reorg to simulate large number of objects per hash buckets. Done by DBWR interrupt action. |
| ORA-10345 ORA-10345, 00000, “validate queue when linking or unlinking a buffer” Cause: Action: checks low RBA ordering of queue associated with latch Comment: Raises an error if low RBA ordering on queue is wrong |
| ORA-10346 ORA-10346, 00000, “check that all buffers for checkpoint have been written” Cause: Action: Scans the cache to see that all candidate buffers are written Comment: Usually only enabled for TESTING since it involves a cache scan |
| ORA-10347 ORA-10347, 00000, “dump active checkpoint entries and checkpoint buffers” Cause: Action: Prints the checkpoint queue and buffers to the trace file Comment: Usually only enabled for TESTING and code coverage |
| ORA-10348 ORA-10348, 00000, “test abnormal termination of process initiating file checkpoint” Document: NO Cause: Action: Causes abnormal termination of process starting a file checkpoint Comment: Only enabled for TESTING and code coverage |
| ORA-10349 ORA-10349, 00000, “do not allow ckpt to complete” Cause: Action: disables checkpoint completion Comment: only enabled for TESTING |
| ORA-10350 ORA-10350, 00000, “Simulate more than one object & tsn id in object reuse” Cause: Action: checks that DBWR can service multiple object id’s in reuse” Comment: only used during testing |
| ORA-10351 ORA-10351, 00000, “size of slots” Cause: Action: sets the size of slots to use Comment: a slot is a unit of I/O and this factor controls the size Comment: of the IO. |
| ORA-10352 ORA-10352, 00000, “report direct path statistics” Cause: Action: turns on direct path statistics Comment: reports statistics for direct path |
| ORA-10353 ORA-10353, 00000, “number of slots” Cause: Action: sets a given number of slots to use Comment: a slot is a unit of I/O and this factor controls the number Comment: of outstanding I/Os. |
| ORA-10354 ORA-10354, 00000, “turn on direct read path for parallel query” Cause: Action: enable direct read for parallel query |
| ORA-10355 ORA-10355, 00000, “turn on direct read path for scans” Cause: Action: enable direct async read for scans |
| ORA-10356 ORA-10356, 00000, “turn on hint usage for direct read” Cause: Action: enables using hint for direct async reads |
| ORA-10357 ORA-10357, 00000, “turn on debug information for direct path” Cause: Action: turn on debug information for direct path |
| ORA-10358 ORA-10358, 00000, “Simulate out of PGA memory in cache advisory reset” Cause: Action: checks that CKPT can set the simulation to OFF Comment: only used during testing |
| ORA-10359 ORA-10359, 00000, “turn off updates to control file for direct writes” Cause: Action: Control files won’t get updated for direct writes for LOBs when NOCACHE NOLOGGING is set. The only bad impact that it can have is that if you are using the recovery manager, it may affect a warning that says that the user should back everything up. Now the recovery manager won’t know to tell you that the files that were updated with unrecoverable events should be backed up. |
| ORA-10360 ORA-10360, 0000, “enable dbwr consistency checking” Cause: internal use only Action: enables consistency checking of buffers written by dbwriter and consistency checking of LRU working sets |
| ORA-10361 ORA-10361, 00000, “check buffer change vector count consistency” Document: No Cause: internal use only Action: invoke buffer change vector count consistency every 5 minutes |
| ORA-10362 ORA-10362, 00000, “simulate a write error to take a file offline” Document: No Cause: internal use only Action: Enables testing of DBWR taking a file offline because of a write error. The level is the absolute file number of the file to be taken offline when DBWR attemts to write to it. |
| ORA-10363 ORA-10363, 00000, “Simulate messaging error for fast object reuse/checkpoint” Document: No Cause: internal use only Action: Enables testing of fast object reuse/checkpoint fallback mechanism due to ksr message publishing issues. |
| ORA-10364 ORA-10364, 00000, “Do not clear GIMH_STC_SHUT_BEGIN state during shutdown” Document: No Cause: internal use only Action: Enables testing of shutdown begin event by not clearing GIMH_STC_SHUT_BEGIN state before shutdown completes. |
| ORA-10365 ORA-10365, 00000, “turn on debug information for adaptive direct reads” Cause: Action: turn on debug information for adaptive direct reads |
| ORA-10366 ORA-10366, 00000, “kgnfs tracing” Cause: Action: If this event is set then kgnfs module generates debug tracing. |
| ORA-10367 ORA-10367, 00000, “kgodm tracing” Cause: Action: If this event is set then kgodm module generates debug tracing. |
| ORA-10368 ORA-10368, 00000, “maximum number of internal errors a process will tolerate” Cause: Action: determines the maximum number of ORA-600s after which a process will commit suicide. |
| ORA-10369 ORA-10369, 00000, “test SQL monitoring feature” Cause: Action: crash tests |
| ORA-10370 ORA-10370, 00000, “parallel query server kill event” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to commit suicide, codes line |
| ORA-10371 ORA-10371, 00000, “disable TQ hint” Cause: internal use only Action: this event should never be set externally Comment: Stops the generation of the TQ hint (for testing purposes) |
| ORA-10372 ORA-10372, 00000, “parallel query server kill event proc” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to commit suicide, codes proc & weapon |
| ORA-10373 ORA-10373, 00000, “parallel query server kill event” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to commit suicide, code count & context |
| ORA-10375 ORA-10375, 00000, “turn on checks for statistics rollups” Cause: Action: enables checks for stat rollup in QC Comment: verify that the rollup is being done accurately |
| ORA-10378 ORA-10378, 00000, “force hard process/range affinity” Cause: Action: set this event only under the supervision of Oracle development Comment: for testing only |
| ORA-10380 ORA-10380, 00000, “kxfp latch cleanup testing event” Cause: Action: set this event only under the supervision of Oracle development Comment: for testing only–indicates the server to which the latch cleanup key applies (0 for QC) |
| ORA-10381 ORA-10381, 00000, “kxfp latch cleanup testing event” Cause: Action: set this event only under the supervision of Oracle development Comment: for testing only–the latch cleanup key (the number of the LCTEST() call on which to kill the process) |
| ORA-10382 ORA-10382, 00000, “parallel query server interrupt (reset)” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to clear its buffers and reset itself |
| ORA-10383 ORA-10383, 00000, “auto parallelization testing event” Cause: Action: Set this event only under the supervision of Oracle development Comment: For testing only. Trace level bits can be used in combination: 1: parallelize every full table scan (kkfd.c) 2: create every table/cluster parallel (prsc.c) 4: create every table/cluster cache 8: create every table/cluster cache partitions (overrides 4) |
| ORA-10384 ORA-10384, 00000, “parallel dataflow scheduler tracing” Cause: Action: set this event only under the supervision of Oracle development Comment: trace level is a bitfield (see kkrp.h) |
| ORA-10385 ORA-10385, 00000, “parallel table scan range sampling method” Cause: Action: set this event only under the supervision of Oracle development Comment: level: 0: (default) sample by random rowid 1: sample by first rows of partition ranges |
| ORA-10386 ORA-10386, 00000, “parallel SQL hash and range statistics” Cause: Action: set this event only under the supervision of Oracle development Comment: print kxfq hash and range statistics |
| ORA-10387 ORA-10387, 00000, “parallel query server interrupt (normal)” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to leave the server group normally |
| ORA-10388 ORA-10388, 00000, “parallel query server interrupt (failure)” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to leave the server group (query failed) |
| ORA-10389 ORA-10389, 00000, “parallel query server interrupt (cleanup)” Cause: internal use only Action: this event should never be set externally Comment: commands a slave to leave the server group (signaled by PMON, coordinator died) |
| ORA-10390 ORA-10390, 00000, “Trace parallel query slave execution” Cause: Action: set this event only under the supervision of Oracle development. trace level is a bitfield // LEVEL ACTION //————————————————————————— 0×0001 slave-side execution messages 0×0002 coordinator-side execution messages 0×0004 slave context state changes 0×0008 slave rowid range bind variables and xty // 0×0010 slave fetched rows as enqueued to TQ 0×0020 coordinator wait reply handling 0×0040 coordinator wait message buffering 0×0080 slave dump timing // 0×0100 coordinator dump timing 0×0200 slave dump allocation file numbers 0×0400 terse format for debug dumps 0×0800 Trace CRI random sampling // 0×1000 Trace signals 0×2000 Trace PX granule operations 0×4000 Force compilation by slave 0 |
| ORA-10391 ORA-10391, 00000, “trace PX granule allocation/assignment” Cause: Action: set this event only under the supervision of Oracle development // LEVEL ACTION //————————————————————————— 0×0001 dump summary of each object scanned in parallel 0×0002 full dump of each object except extent map 0×0004 full dump of each object including extent map // 0×0010 dump summary of each granule generators 0×0020 full dump of granule generators except granule instances 0×0040 full dump of granule generators including granule instances // 0×0080 dump system info 0×0100 dump reference object for the query 0×0200 gives timing in kxfralo 0×0400 trace affinity module 0×0800 trace granule allocation during query execution // 0×1000 trace object flush 0×2000 internal Comment: print details of PQ parallel granule allocation |
| ORA-10392 ORA-10392, 00000, “parallel query debugging bits” Cause: Action: set this event only under the supervision of Oracle development Comment: turn on/off various kxfp features (documentation in kxfp.c) |
| ORA-10393 ORA-10393, 00000, “print parallel query statistics” Cause: Action: set this event only under the supervision of Oracle development Comment: print kxfp statistics after each parallel query |
| ORA-10394 ORA-10394, 00000, “generate a fake load to test adaptive and load balancing” Cause: Action: set this event only under the supervision of Oracle development Comment: generates a fake load for testing purposes |
| ORA-10395 ORA-10395, 00000, “adjust sample size for range table queues” Cause: Action: set this event only under the supervision of Oracle development Comment: use reduced sample size for testing only |
| ORA-10397 ORA-10397, 00000, “suppress verbose parallel coordinator error reporting” Cause: Action: set this event only under the supervision of Oracle development Comment: disable the ORA-12801 message when a parallel query server gets a SQL error, instead report the slave’s actual error as if signaled in the foreground (for testing, to match sequential log files) |
| ORA-10398 ORA-10398, 00000, “enable timeouts in parallel query threads” Cause: Action: set this event only under the supervision of Oracle development Comment: level of this event indicates the number of seconds before timing out of a kxfpqdeq() call, after which an internal error will be signaled…for testing so that test suites don’t wedge. |
| ORA-10399 ORA-10399, 00000, “trace buffer allocation” Cause: Action: set this event only under the supervision of Oracle development Comment: level indicates verbosity of tracing Level1: Buffer leak checking Level2: trace buffer init, chunk alloc, free and recovery Level3: trace buffer alloc & free |
| ORA-10400 ORA-10400, 00000, “turn on system state dumps for shutdown debugging” Cause: Action: Enables debugging code for shutdown problems (e.g., hangs) |
| ORA-10401 ORA-10401, 00000, “turn on IPC (ksxp) debugging” Cause: Action: Enables debugging code for IPC service layer (ksxp) |
| ORA-10402 ORA-10402, 00000, “turn on IPC (skgxp) debugging” Cause: Action: Enables debugging code for IPC layer (skgxp) |
| ORA-10403 ORA-10403, 00000, “fake CPU number for default degree of parallelism” Cause: Action: set this event only under the supervision of Oracle development Comment: level of this event indicates the number of CPUs you want to set to |
| ORA-10404 ORA-10404, 00000, “crash dbwr after write” Cause: Action: set this event only to test mirror resilvering osds Comment: This event causes dbwr to crash after doing a write to a mirrored datafile. For use in tkbrmrt only. |
| ORA-10405 ORA-10405, 00000, “emulate broken mirrors” Cause: Action: set this event to cause mirror resilvering on startup Comment: This event is set when starting up after a crash caused by OER(10404). It is used to persuade the recovery layer that a mirror was broken. |
| ORA-10406 ORA-10406, 00000, “enable datetime TIMESTAMP, INTERVAL datatype creation” Cause: Action: set this event to enable datetime datatype creation Comment: This event is set when the user wants to create a datetime datatype column. The compatible=8.1.0.0.0 parameter must also be set. |
| ORA-10407 ORA-10407, 00000, “enable datetime TIME datatype creation” Cause: Action: set this event to enable datetime datatype creation Comment: This event is set when the user wants to create a datetime datatype column. The compatible=8.1.0.0.0 parameter must also be set. |
| ORA-10408 ORA-10408, 00000, “disable OLAP builtin window function usage” Cause: Action: set this event to disable new OLAP builtin window functions Comment: This event is set when the user has a name conflict with one of the OLAP window function names. This setting disables the builtin functions so that user functions work. |
| ORA-10409 ORA-10409, 00000, “enable granule memset and block invalidation at startup” Cause: Action: set this event to enable the memset and invalidation Comment: This event is created to be the safe valve for startup speedup transaction |
| ORA-10410 ORA-10410, 00000, “trigger simulated communications errors in KSXP” Document: NO Cause: Action: set this event to simulate communications errors to clients Comment: This event is set as 0xCIXXNNNN where C is the client id the the error will be generated to, I is the instance id the error will be generated for and NNNN is the minimum message sequence number for instance I. An initial event value of C=0 indicates dynamic check of event |
| ORA-10412 ORA-10412, 00000, “dump the call stack if an error is signaled” Document: NO Cause: For testing only. Action: None. For testing only. Should never be set by customers. |
| ORA-10413 ORA-10413, 00000, “force simulated error for testing purposes” Document: NO Cause: For testing only. Action: None. For testing only. Should never be set by customers. Comment: level 1: ALTER TABLESPACE…READ ONLY before kcftro level 2: ALTER TABLESPACE…READ ONLY after kcftro level 3: ALTER TABLESPACE…READ ONLY before kcfrdo, after waiting level 4: ALTER TABLESPACE…READ ONLY after kcfrdo level 5: ALTER TABLESPACE…READ ONLY after krcrtro level 6: ALTER TABLESPACE…READ ONLY after kqrpre to get lock on TS$ level 7: ALTER TABLESPACE…READ ONLY after kqrpup to update TS$ level 8: ALTER TABLESPACE…READ ONLY after ktucat to check other tx’s level 9: ALTER TABLESPACE…READ ONLY after ktccrb to commit level 10: ALTER TABLESPACE…READ ONLY in kcfrdo, before checkpoint // |
| ORA-10414 ORA-10414, 00000, “simulated error from event %s level %s” Document: NO Cause: For testing only. Action: None. For testing only. Should never be set by customers. Comment: // |
| ORA-10415 ORA-10415, 00000, “parallel degree specified is too large, max value allowed %s” Document: NO Cause: User specified parallel degree is greater than DEG_INST_MAXVAL Action: Comment: // |
| ORA-10416 ORA-10416, 00000, “disable fix for 2736734″ Document: NO Cause: Action: Disable the fix for bug 2736734 // |
| ORA-10417 ORA-10417, 00000, “limit 1 file per sbtinfo2() validation call” Document: NO Cause: Action: Prevent Oracle from passing multiple file handles to sbtinfo2(), in case the Media Management Software cannot properly support calls with multiple file names. |
| ORA-10418 ORA-10418, 00000, “disable re-creating tempfile” Document: NO Cause: Action: Prevent Oracle from automatically re-creating tempfile |
| ORA-10419 ORA-10419, 00000, “create tempfile without create_scn and time” Document: NO Cause: For testing only. Action: None. For testing only. Should never be set by customers. |
| ORA-10420 ORA-10420, 00000, “trace KSO OS-process operations” Document: NO Cause: Action: Trace KSO operations. |
| ORA-10421 ORA-10421, 00000, “enable dump from ksbwco if there is no reply” Document: NO Cause: Action: creates an error stack dump if ksbwco does not hear back. |
| ORA-10422 ORA-10422, 00000, “KSU debugging” Document: NO Cause: Action: Helps debug KSU issues (see ksu.h). |
| ORA-10423 ORA-10423, 00000, “dump the call stack if the specified error is cleared” Document: NO Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event=”10423 trace name context forever, level <your-err>” Example: event=”10423 trace name context forever, level 28″ Each time ORA-28 is cleared the stack will be dumped. Action: Creates a stack dump each time the specified error is cleared. |
| ORA-10424 ORA-10424, 00000, “KGE debugging” Document: NO Cause: Action: Helps debug KGE issues (see kge.c). |
| ORA-10425 ORA-10425, 00000, “enable global enqueue operations event trace” Document: NO Cause: Action: Dump trace for global enqueue operations. |
| ORA-10426 ORA-10426, 00000, “enable ges/gcs reconfiguration event trace” Document: NO Cause: Action: Dump trace for ges/gcs reconfiguration. |
| ORA-10427 ORA-10427, 00000, “enable global enqueue service traffic controller event trace” Document: NO Cause: Action: Dump trace for global enqueue service traffic controller. |
| ORA-10428 ORA-10428, 00000, “enable tracing of global enqueue service cached resource” Document: NO Cause: Action: Dump trace for global enqueue service cached resource activities. |
| ORA-10429 ORA-10429, 00000, “enable tracing of global enqueue service IPC calls” Document: NO Cause: Action: Dump trace for global enqueue service IPC calls. |
| ORA-10430 ORA-10430, 00000, “enable ges/gcs dynamic remastering event trace” Document: NO Cause: Action: Dump trace for ges/gcs dynamic remastering. |
| ORA-10431 ORA-10431, 00000, “enable verification messages on pi consistency” Document: NO Cause: Action: Send verification messages to check pi consistency |
| ORA-10432 ORA-10432, 00000, “enable tracing of global cache service fusion calls” Document: NO Cause: Action: Dump trace for global cache service fusion calls. |
| ORA-10433 ORA-10433, 00000, “global enqueue service testing event” Document: NO Cause: Action: Level: == 6 to return out-of-memory when getting message buffer Level: == 7 to suspend lmd for a short period of time Level: == 8 to suspend lms for a short period of time Level: == 9 to inject out-of-order dlm messages Level: == 10 to delay direct sends on send proxies and to force indirect sends on half of the direct send messages |
| ORA-10434 ORA-10434, 00000, “enable tracing of global enqueue service multiple LMS” Document: NO Cause: Action: Dump trace for global enqueue service muliple LMS. |
| ORA-10435 ORA-10435, 00000, “enable tracing of global enqueue service deadlock detetction” Document: NO Cause: Action: Dump trace for global enqueue service deadlock detetction. |
| ORA-10436 ORA-10436, 00000, “enable global cache service duplicate ping checking” Document: NO Cause: Action: Enable global cache service duplicate ping checking |
| ORA-10437 ORA-10437, 00000, “enable trace of global enqueue service S optimized resources” Document: NO Cause: Action: Dump global cache service S optimized resources |
| ORA-10438 ORA-10438, 00000, “force lowest node to be master of all gcs resources” Document: NO Cause: Action: enable affinity locks by forcing lowest node to be master |
| ORA-10439 ORA-10439, 00000, “enable tracing of global cache service fusion calls – part 2″ Document: NO Cause: Action: enable tracing of global cache service fusion calls – part 2 |
| ORA-10440 ORA-10440, 00000, “enable global enqueue service inquire resource modes trace” Document: NO Cause: Action: Dump trace for global enqueue service resource inquiry messages. |
| ORA-10441 ORA-10441, 00000, “enable diagnosibility daemon (DIAG) trace” Document: NO Cause: Action: Dump traces for DIAG. |
| ORA-10442 ORA-10442, 00000, “enable trace of kst for ORA-01555 diagnostics” Document: NO Cause: Action: Dump trace for ORA-01555 diagnostics |
| ORA-10449 ORA-10449, 00000, “enable trace of kst for undo manageability features diagnostics” Document: NO Cause: Action: Dump trace for undo manageability features diagnostics |
| ORA-10450 ORA-10450, 00000, “signal ctrl-c in kdddca (drop column) after n rows” Cause: Action: set this event only under the supervision of Oracle development Comment: Set the level number to the number of rows before the error is signalled. The error will be ORA-1013 (ctrl-c) |
| ORA-10451 ORA-10451, 00000, “Force heap segment compression bypassing compatibility checks” Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-10452 ORA-10452, 00000, “Cannot do block media recovery; media recovery session may be in progress” Cause: A media recovery, RMAN, or flashback database session may have been in progress when an attempt was made to perform block media recovery on the standby database. Action: Check for and cancel any conflicting recovery session and perform block media recovery on the standby database. // |
| ORA-10453 ORA-10453, 00000, “Dump compression statistics to trace file” Document: NO Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-10454 ORA-10454, 00000, “Disable column reordering during compression” Document: NO Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-10455 ORA-10455, 00000, “Do Compression Block Checking” Document: NO Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-10456 ORA-10456, 00000, “cannot open standby database; media recovery session may be in progress” Cause: A media recovery, RMAN, or flashback database session may have been in progress on a mounted instance of a standby database when an attempt was made to open the standby database. Action: Check for and cancel any conflicting recovery session and open the standby database. // |
| ORA-10457 ORA-10457, 00000, “cannot close standby database due to active media recovery” Cause: A media recovery session was in progress on a standby database when an attempt was made to close the standby database. Action: Cancel the media recovery session and close the standby database. // |
| ORA-10458 ORA-10458, 00000, “standby database requires recovery” Cause: A standby database was in a state requiring media recovery when an attempt was made to open the standby database. Action: Perform the necessary recovery and open the standby database. // |
| ORA-10459 ORA-10459, 00000, “cannot start media recovery on standby database; another instance may be open” Cause: An attempt was made to perform media recovery on a standby database while another instance performed recovery on the standby or had the standby open. Action: Close the standby on all other instances, cancel any conflicting recovery session, and perform manual recovery. // |
| ORA-10460 ORA-10460, 00000, “Perform backward tablescans for consistent read reduction” Cause: Action: // Events 10461 – 10489 reserved for recovery, incl debugging and tracing // |
| ORA-10461 ORA-10461, 00000, “Simulate control file corruption during write operation” Cause: Action: If set, will cause control file header verification to fail // |
| ORA-10462 ORA-10462, 00000, “enable recovery debug module” Cause: Action: Set this event to enable recovery debug module. Recovery debug module does extra sanity checks on redo generation and dumps interesting information to trace if certain errors occur. // |
| ORA-10463 ORA-10463, 00000, “enable controlfile test” Document: NO Cause: Action: Set this event to enable controlfile sequence number dump at instance shutdown (level 1) or future version controlfile compatibility test (level 2) // |
| ORA-10464 ORA-10464, 00000, “enable incremental checkpoint debug for split brain check” Document: NO Cause: Action: Set this event to enable checkpoint heartbeat tracing // |
| ORA-10465 ORA-10465, 00000, “force slave death during parallel crash recovery” Document: NO Cause: Action: // |
| ORA-10466 ORA-10466, 00000, “enable HARD check for block write” Document: NO Cause: Action: Set this event to enable HARD check for every block write. // |
| ORA-10467 ORA-10467, 00000, “amplify control file record expansion for testing” Document: NO Cause: Action: Set this event to amplify control file record expansion for testing // |
| ORA-10468 ORA-10468, 00000, “log writer debug module” Document: NO Cause: Action: Set this event to the appropriate level for log writer debugging. // |
| ORA-10469 ORA-10469, 00000, “error creating control file backup, no checkpoint” Cause: The control file being backed up did not contain a valid control file checkpoint. Therefore the control file could not be backed up, as such a backup would not be usable later for recovery. A common cause for this situation is that you executed CREATE CONTROLFILE, which mounts the database, but not ALTER DATABASE OPEN, to open the database. The latter operation generates a valid control file checkpoint. Action: Open the database with ALTER DATABASE OPEN …, which results in a valid control file checkpoint. Run the backup operation again. |
| ORA-10470 ORA-10470, 00000, “disable compatibility check for lost write detection” Document: NO Cause: Action: Set this event to run database with lost write detection enabled in compatibility mode below 11.0. Level 1: equivalent of “typical” setting Level 2: equivalent of “full” setting for the parameter db_lost_write_protect // |
| ORA-10471 ORA-10471, 00000, “PQ slave allocation timeout test” Document: NO Cause: Action: Set this event to enable the delay in PQ slave allocation. If the delay is longer than the preset threshold (currently 1 minute), parallel recovery should switch to serial recovery. // |
| ORA-10472 ORA-10472, 00000, “dump reading log buffer hit ratio histogram to lgwr trace file” Document: NO Cause: Action: Set this event to dump reading log buffer hit rate histogram to lgwr trace file. // |
| ORA-10473 ORA-10473, 00000, “enable BRR tracing” Document: NO Cause: Action: Set this event to enable tracing of Block Read Record generation. // |
| ORA-10474 ORA-10474, 00000, “controlfile time tracing” Document: NO Cause: Action: Set this event to enable additional tracing of the time spent in different controlfile operations. // |
| ORA-10475 ORA-10475, 00000, “readable standby debug event” Document: NO Cause: Action: Set this event to enable additional tracing of readable standby. // |
| ORA-10476 ORA-10476, 00000, “control file corruption range testing” Document: NO Cause: Action: Set this event to enable testing of control file corruption ranges. // |
| ORA-10477 ORA-10477, 00000, “simulated rollback error” Document: NO Cause: Action: Set this event to simulate a rollback failure. // |
| ORA-10478 ORA-10478, 00000, “DBW0 file identification trace event” Document: NO Cause: Action: Set this event to enable DBW0 file identification tracing. |
| ORA-10490 ORA-10490, 00000, “Trace OSM misc. events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10491 ORA-10491, 00000, “Trace OSM messaging (KFN) events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10492 ORA-10492, 00000, “Trace OSM metadata events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10493 ORA-10493, 00000, “Return empty define buffers on 1422″ *cause Action: On error 1422 instead of returning data in define buffers this mimics action of version 7 and doesn’t return data valid level = 1 // |
| ORA-10494 ORA-10494, 00000, “Trace OSM metadata events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10495 ORA-10495, 00000, “Trace OSM metadata events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10496 ORA-10496, 00000, “Turn off fix for bug 2554178″ *cause Action: Instead of checking the current schema against the owner of the db link revert to previous scheme // |
| ORA-10497 ORA-10497, 00000, “Trace OSM metadata events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10498 ORA-10498, 00000, “Trim blank characters including contol characters” Cause: Action: Comment: Set this event to any non-zero level to trim blank characters including control characters. Default behaviour: No control characters are trimmed. // |
| ORA-10499 ORA-10499, 00000, “Trace OSM metadata events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. // |
| ORA-10500 ORA-10500, 00000, “turn on traces for SMON” Document: NO Cause: Action: Level: <=5 trace instance recovery > 5 trace posting of SMON |
| ORA-10501 ORA-10501, 00000, “periodically check selected heap” Cause: Action: Level: 0×01 PGA 0×02 SGA 0×04 UGA 0×08 current call 0×10 user call 0×20 large allocation pool |
| ORA-10502 ORA-10502, 00000, “CBO disable the fix for bug 2098120″ Cause: Action: |
| ORA-10503 ORA-10503, 00000, “enable user-specified graduated bind lengths” Cause: Action: |
| ORA-10504 ORA-10504, 00000, “CBO disable the fix for bug 2607029″ Cause: Action: |
| ORA-10505 ORA-10505, 00000, “CBO enable dynamic sampling dump to table” Cause: Action: |
| ORA-10506 ORA-10506, 00000, “Disable fix for bug 2588217″ Cause: Action: |
| ORA-10507 ORA-10507, 00000, “Trace bind equivalence logic” Cause: Action: |
| ORA-10509 ORA-10509, 00000, “Check kghu subheaps at call boundaries” Cause: Action: Level: 0×01 Call heap 0×02 Session heap |
| ORA-10510 ORA-10510, 00000, “turn off SMON check to offline pending offline rollback segment” Cause: Action: |
| ORA-10511 ORA-10511, 00000, “turn off SMON check to cleanup undo dictionary” Cause: Action: |
| ORA-10512 ORA-10512, 00000, “turn off SMON check to shrink rollback segments” Cause: Action: |
| ORA-10515 ORA-10515, 00000, “turn on event to use physical cleanout” Cause: Action: |
| ORA-10519 ORA-10519, 00000, “enable ALTER TYPE RESET support” Cause: Action: |
| ORA-10520 ORA-10520, 00000, “recreate view only if definition has changed” Cause: Action: Set this event only under the supervision of Oracle development Comment: Changes behaviour of create or replace view, comparing the new definition to the old prior to recreating the object. Creation is skipped if old and new definitions match (ie. object has not changed). No level number required. |
| ORA-10521 ORA-10521, 00000, “CMON connection pool test event” Document: NO Cause: Action: Comment: |
| ORA-10522 ORA-10522, 00000, “turn off wrap source compression” Cause: Action: Set this event if you do not want source of wrapped PL/SQL objects to be concatenated and stored multiple lines to a row. Comment: This event should be set if you want the source of wrapped PL/SQL objects to be stored one line per source row. The default storage method is multiple lines per row, which improves load and compile performance. No level number required. |
| ORA-10523 ORA-10523, 00000, “force recreate package even if definition is unchanged” Cause: Action: Set this event only under the supervision of Oracle development Comment: Changes behaviour of create or replace package, procedure, function or type to force recreation of the object even if its new definition exactly matches the old definition. No level number required. |
| ORA-10524 ORA-10524, 00000, “CMON connection pool trace event” Document: NO Cause: Action: Comment: |
| ORA-10525 ORA-10525, 00000, “Disable automatic object validation for describe” Cause: Action: |
| ORA-10546 ORA-10546, 00000, “Cannot perform block media recovery; standby database does not have requisite redo.” Cause: An attempt was made to perform block media recovery on the standby database when the necessary redo was not available. Action: Wait until the necessary redo is available and reattempt block media recovery. |
| ORA-10547 ORA-10547, 00000, “Cannot perform block media recovery; standby database is not caught up with primary.” Cause: An attempt was made to perform block media recovery on the standby database up to scn %s, which is greater than the highest scn of %s yet applied at the standby. Action: Recover the standby up to scn %s and reattempt block media recovery. |
| ORA-10548 ORA-10548, 00000, “Cannot perform block media recovery on a read-only plugged-in datafile.” Cause: An attempt was made to perform block media recovery on a read-only plugged-in datafile. Action: Convert the plugged-in datafile to read/write and reattempt block media recovery. |
| ORA-10549 ORA-10549, 00000, “Cannot perform block media recovery using a read-only plugged-in backup datafile.” Cause: An attempt was made to perform block media recovery using a backup of a read-only plugged-in datafile. Action: Reattempt block media recovery using a backup taken after the plugged-in datafile has been converted to read/write. |
| ORA-10550 ORA-10550, 00000, “signal error during create as select/create index after n rows” Cause: Action: set this event only under the supervision of Oracle development Comment: Set the level number to the number of rows before the error is signalled. The error will be ORA-1013 (ctrl-c) // |
| ORA-10551 ORA-10551, 00000, “Internal testing for ORA-1551 error handling” Cause: Action: |
| ORA-10552 ORA-10552, 00000, “Inconsistent plug-in file %s encountered during standby recovery” Cause: Standby recovery in read-only mode stopped and the database was closed because recovery encountered a plug-in file that was already converted. Action: Try opening the database again or restart standby recovery. |
| ORA-10553 ORA-10553, 00000, “Incompatible UNTIL CONSISTENT clause” Cause: RECOVER UNTIL CONSISTENT required database-level recovery with a backup control file. Action: Omit the UNTIL CONSISTENT clause and retry recovery. |
| ORA-10554 ORA-10554, 00000, “Media recovery failed to bring datafile %s to a consistent point” Cause: Media recovery couldn’t recover database to a consistent point due to the specified datafile. Action: Restore a backup of the datafile. |
| ORA-10560 ORA-10560, 00000, “block type ‘%s’” Cause: Report block type for details of another error. Action: See associated error message. |
| ORA-10561 ORA-10561, 00000, “block type ‘%s’, data object# %s” Cause: Report block type and data object number for details of another error. Action: See associated error message. |
| ORA-10562 ORA-10562, 00000, “Error occurred while applying redo to data block (file# %s, block# %s)” Cause: See other errors on error stack. Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block. |
| ORA-10563 ORA-10563, 00000, “Test recovery had to corrupt data block (file# %s, block# %s) in order to proceed” Cause: Test recovery completed. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery. |
| ORA-10564 ORA-10564, 00000, “tablespace %s” Cause: Report tablespace name for details of another error. Action: See associated error message. |
| ORA-10565 ORA-10565, 00000, “Another test recovery session is active” Cause: There can only be one test recovery session at any time. Another test recovery session is active. Action: Wait till the other test recovery session completes. |
| ORA-10566 ORA-10566, 00000, “Test recovery has used all the memory it can use” Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery. |
| ORA-10567 ORA-10567, 00000, “Redo is inconsistent with data block (file# %s, block# %s)” Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error. Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block. |
| ORA-10568 ORA-10568, 00000, “Failed to allocate recovery state object: out of SGA memory” Cause: out of SGA memory Action: Restart the instance. If problem persists, call Oracle support. |
| ORA-10570 ORA-10570, 00000, “Test recovery complete” Cause: Test recovery completed. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery. |
| ORA-10571 ORA-10571, 00000, “Test recovery canceled” Cause: User canceled test recovery. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery. |
| ORA-10572 ORA-10572, 00000, “Test recovery canceled due to errors” Cause: See other errors on the error stack. Action: See other messages on error stack. It is possible that no action is needed. See other messages on error stack for a summary of the result of the test recovery so far. |
| ORA-10573 ORA-10573, 00000, “Test recovery tested redo from change %s to %s” Cause: This message show the range of test recovery have tested. Action: No action is needed. See other messages on error stack. |
| ORA-10574 ORA-10574, 00000, “Test recovery did not corrupt any data block” Cause: This message summarizes test recovery result. Action: No action is needed. See other messages on error stack. |
| ORA-10575 ORA-10575, 00000, “Give up restoring recovered datafiles to consistent state: out of memory” Cause: There were not enough memory to restore recovered datafiles to consistent state Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again. |
| ORA-10576 ORA-10576, 00000, “Give up restoring recovered datafiles to consistent state: some error occurred” Cause: See alert file or other errors on the stack for a cause of the problem. Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again. // |
| ORA-10577 ORA-10577, 00000, “Can not invoke test recovery for managed standby database recovery” Cause: Test recovery option is used for managed standby database recovery. Action: Either remove the test recovery option or invoke manual test standby database recovery. |
| ORA-10578 ORA-10578, 00000, “Can not allow corruption for managed standby database recovery” Cause: You used the allow corruption option for managed standby database recovery. Action: Either remove the allow corruption option or invoke manual standby database recovery. |
| ORA-10579 ORA-10579, 00000, “Can not modify control file during test recovery” Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. |
| ORA-10580 ORA-10580, 00000, “Can not modify datafile header during test recovery” Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. |
| ORA-10581 ORA-10581, 00000, “Can not modify redo log header during test recovery” Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. |
| ORA-10582 ORA-10582, 00000, “The control file is not a backup control file” Cause: User requested backup control file test recovery, but the control file is not a backup control file. Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE option. |
| ORA-10583 ORA-10583, 00000, “Can not recovery file %s renamed as missing during test recovery” Cause: One of the files to be recovered is renamed as missing. Action: Rename the file to the correct file or offline it. |
| ORA-10584 ORA-10584, 00000, “Can not invoke parallel recovery for test recovery” Cause: Both test recovery and parallel recovery are requested. Action: Drop either one of the two recovery options. |
| ORA-10585 ORA-10585, 00000, “Test recovery can not apply redo that may modify control file” Cause: Test recovery has encountered a special redo that may modify control file. Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point. |
| ORA-10586 ORA-10586, 00000, “Test recovery had to corrupt 1 data block in order to proceed” Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested. Action: See alert log for details of the problem. |
| ORA-10587 ORA-10587, 00000, “Invalid count for ALLOW n CORRUPTION option” Cause: The number specified in the ALLOW n CORRUPTION option is too big. Action: Use a smaller number. |
| ORA-10588 ORA-10588, 00000, “Can only allow 1 corruption for normal media/standby recovery” Cause: The number specified in the ALLOW n CORRUPTION option is too big. Action: change to allow zero or one corruption. |
| ORA-10589 ORA-10589, 00000, “Test recovery had to corrupt %s data blocks in order to proceed” Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested. Action: See alert log for details of the problems. |
| ORA-10590 ORA-10590, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10591 ORA-10591, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10592 ORA-10592, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10593 ORA-10593, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10594 ORA-10594, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10595 ORA-10595, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10596 ORA-10596, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10597 ORA-10597, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10598 ORA-10598, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10599 ORA-10599, 00000, “kga (argus debugger) test flags” Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-10600 ORA-10600, 00000, “check cursor frame allocation” Cause: Action: |
| ORA-10601 ORA-10601, 00000, “turn on debugging for cursor_sharing (literal replacement)” Cause: Action: |
| ORA-10603 ORA-10603, 00000, “cause an error to occur during truncate (for testing purposes)” Cause: Action: set this event only under the supervision of Oracle development Comment: this causes kdifrb to encounter an error during truncation of a table with an index. it is for testing purposes only. |
| ORA-10604 ORA-10604, 00000, “trace parallel create index” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of parallel create index |
| ORA-10605 ORA-10605, 00000, “enable parallel create index by default” Cause: Action: set this event only under the supervision of Oracle development Comment: this causes all create index statement to by default occur in parallel. it is for testing purposes only. the level set in the event is the degree of parallelism. Comment: enables analysis of parallel create index – query coordinator |
| ORA-10606 ORA-10606, 00000, “trace parallel create index” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of parallel create index – kkri slaves |
| ORA-10607 ORA-10607, 00000, “trace index rowid partition scan” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of rowid index scan – rix row source, and puts more trace on errors in range scans |
| ORA-10608 ORA-10608, 00000, “trace create bitmap index” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of create bitmap index – kkrb row source |
| ORA-10609 ORA-10609, 00000, “trace for array index insertion” Cause: Action: set this event to turn off the index array operation Comment: disable the index array operation |
| ORA-10610 ORA-10610, 00000, “trace create index pseudo optimizer” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10611 ORA-10611, 00000, “causes migration to fail – testing only” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10612 ORA-10612, 00000, “prints debug information for auto-space managed segments” Cause: Action: |
| ORA-10613 ORA-10613, 00000, “prints debug information for auto-space managed segments” Cause: Action: |
| ORA-10614 ORA-10614, 00000, “Operation not allowed on this segment” Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and type and re-issue the statement |
| ORA-10615 ORA-10615, 00000, “Invalid tablespace type for temporary tablespace” Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be used as a temporary tablespace Action: Recheck the tablespace name and re-issue the statement |
| ORA-10616 ORA-10616, 00000, “Operation not allowed on this tablespace” Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the tablespace name and re-issue the statement |
| ORA-10617 ORA-10617, 00000, “Cannot create rollback segment in dictionary managed tablespace” Cause: Rollback segments cannot be created in dictionary managed tablespaces when SYSTEM tablespace is locally managed Action: Recheck the tablespace name and re-issue the statement |
| ORA-10618 ORA-10618, 00000, “Operation not allowed on this segment” Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and type and re-issue the statement |
| ORA-10619 ORA-10619, 00000, “Avoid assertions when possible” Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc) Action: Event makes RDBMS skip assertions and patch up datastructures |
| ORA-10620 ORA-10620, 00000, “Operation not allowed on this segment” Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and re-issue the statement |
| ORA-10621 ORA-10621, 00000, “specify retry count for online index build cleanup DML lock get” Cause: Action: set this event only under the supervision of Oracle development Comment: Change the behaviour of online index build cleanup such that a failed DML lock get will be reattempted. The number of retries is dictated by the event level. Note that an event level of 1 means try forever. Any other event level specifies the number of attempts, and is internally increased to some minimum default. |
| ORA-10622 ORA-10622, 00000, “test/trace online index (re)build” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10624 ORA-10624, 00000, “Disable UJV invalidation on drop index” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10625 ORA-10625, 00000, “Turn off redo log dump for the index when OERI 12700″ Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10626 ORA-10626, 00000, “specify timeout for online index rebuild to wait for DML” Cause: Action: set this event only under the supervision of Oracle development Comment: Change the behaviour of an online index rebuild such that it will timeout, rather than wait indefinitely for existing DML to complete. The event level is the number of seconds the online index rebuild should wait. Values outside the legal range of 2 to 300 seconds will be adjusted automatically. |
| ORA-10627 ORA-10627, 00000, “Dump the content of the index leaf block” Cause: Generate a complete index tree dump, not just an overview during alter session set events immediate trace name treedump Action: This event is recommended only for small table/index since it |
| ORA-10628 ORA-10628, 00000, “Turn on sanity check for kdiss index skip scan state” Cause: Will do sanity checking on the kdiss state. Action: set this event only under the supervision of Oracle development |
| ORA-10629 ORA-10629, 00000, “force online index build to backoff and retry DML lock upgrade” Cause: Action: set this event only under the supervision of Oracle development Comment: Change the behaviour of an online index rebuild such that it will backoff and retry a failed DML lock upgrade. The event level is the number of retries the online index rebuild should wait. Level 1 means backoff and retry indefinitely. Any other value less than 32 will be adjusted automatically to be 32. |
| ORA-10630 ORA-10630, 00000, “Illegal syntax specified with SHRINK clause” Cause: An illegal option was specified with the SHRINK clause Action: Verify the SQL Reference Manual and reissue the command |
| ORA-10631 ORA-10631, 00000, “SHRINK clause should not be specified for this object” Cause: It is incorrect to issue shrink on the object Action: Verify the object name and type and reissue the command |
| ORA-10632 ORA-10632, 00000, “Invalid rowid” Cause: Segment Highwatermark was overwritten due to shrink and space reused Action: Reissue this command. |
| ORA-10633 ORA-10633, 00000, “No space found in the segment” Cause: Raised while trying to find space during segment shrink Action: This error should be trapped internally and treated. The user should not be able to see the error. |
| ORA-10634 ORA-10634, 00000, “Segment is already being shrunk” Cause: Only one invocation of shrink can be in progress on a segment at any time Action: Reissue the command after the first shrink is over |
| ORA-10635 ORA-10635, 00000, “Invalid segment or tablespace type” Cause: Cannot shrink the segment because it is not in auto segment space managed tablespace or it is not a data, index or lob segment. Action: Check the tablespace and segment type and reissue the statement |
| ORA-10636 ORA-10636, 00000, “ROW MOVEMENT is not enabled” Cause: To shrink a data segment, row movement must be enabled. Action: Enable row movement and reissue this command. |
| ORA-10637 ORA-10637, 00000, “The segment does not exist” Cause: Segment to be shrunk has been dropped Action: |
| ORA-10638 ORA-10638, 00000, “Index status is invalid” Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state. Action: |
| ORA-10639 ORA-10639, 00000, “Dump library cache during kksfbc-reparse-infinite-loop error” Cause: During this error a library cache dump is necessary , so enable librarycache dump if event is set. Action: Dump a library cache if this event is set when reparse error. // |
| ORA-10640 ORA-10640, 00000, “Operation not permitted during SYSTEM tablespace migration” Cause: SYSTEM tablespace is being migrated to locally managed format. Action: Reissue this command once SYSTEM tablespace migration is over. |
| ORA-10641 ORA-10641, 00000, “Cannot find a rollback segment to bind to” Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace. Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace and retry migration. |
| ORA-10642 ORA-10642, 00000, “Found rollback segments in dictionary managed tablespaces” Cause: When SYSTEM tablespace is migrated found rollback segments in dictionary managed tablespaces. Action: Drop the rollback segments in dictionary managed tablespaces and reissue the command |
| ORA-10643 ORA-10643, 00000, “Database should be mounted in restricted mode and Exclusive mode” Cause: When SYSTEM tablespace is being migrated database should be mounted in Exclusive mode and in Restricted mode. Action: Reissue this command after mounting the database in right mode. |
| ORA-10644 ORA-10644, 00000, “SYSTEM tablespace cannot be default temporary tablespace” Cause: When SYSTEM tablespace is being migrated no user should have SYSTEM as the default temporary tablespace. Action: Reissue this command after altering the default temporary tablespace setting for all users. |
| ORA-10645 ORA-10645, 00000, “Recursive Extension in SYSTEM tablespace during migration” Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively. Must be caught and processed internally. Should not be thrown to the user. Action: Report the error as a bug. |
| ORA-10646 ORA-10646, 00000, “Too many recursive extensions during SYSTEM tablespace migration” Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times. Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command. |
| ORA-10647 ORA-10647, 00000, “Tablespace other than SYSTEM, %s, %s not found in read only mode” Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only. Action: Alter the tablespace status to read only and retry migration. |
| ORA-10648 ORA-10648, 00000, “Tablespace SYSAUX is not offline” Cause: The SYSAUX tablespace was online while SYSTEM tablespace was being migrated. Action: Alter the SYSAUX tablespace status to offline and retry migration. |
| ORA-10649 ORA-10649, 00000, “Turn off/trace lob index freelist coalesce” Cause: Will turn off or trace lob index freelist coalescing Action: set this event only under the supervision of Oracle development |
| ORA-10650 ORA-10650, 00000, “disable cache-callback optimisation” Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10651 ORA-10651, 00000, “incorrect file number block number specified” Cause: The dba specified is not valid Action: Check if the dba specified belongs to the segment and is under the segment HWM and reissue the statement |
| ORA-10652 ORA-10652, 00000, “Object has on-commit materialized views” Cause: It is illegal to issue shrink on an object with on-commit materialized views Action: |
| ORA-10653 ORA-10653, 00000, “Table is in a cluster” Cause: It is illegal to shrink a table belonging to a cluster Action: |
| ORA-10654 ORA-10654, 00000, “Table is of type temporary or external” Cause: It is illegal to shrink a temporary table or an external table Action: |
| ORA-10655 ORA-10655, 00000, “Segment can be shrunk” Cause: Error message returned when called in probe mode by OEM Action: |
| ORA-10656 ORA-10656, 00000, “Table is in unusable state due to incomplete operation” Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable state because of previously failed/incomplete operation. Action: If the previous operation was – DROP COLUMN, resubmit DROP COLUMN CONTINUE – DROP TABLE, resubmit DROP TABLE <table> PURGE |
| ORA-10657 ORA-10657, 00000, “Lob column to be shrunk does not exist” Cause: Shrink was issued on a lob segment that did not exist Action: |
| ORA-10658 ORA-10658, 00000, “Lob column to be shrunk is marked unused” Cause: Shrink was issued on a lob segment that is marked as unused Action: |
| ORA-10659 ORA-10659, 00000, “Segment being shrunk is not a lob” Cause: Shrink was issued on a segment that should be a first class lob or other data type stored in lob Action: |
| ORA-10660 ORA-10660, 00000, “Segment is a shared lob segment” Cause: Shrink was issued on a segment that was being shared by multiple lob columns Action: |
| ORA-10661 ORA-10661, 00000, “Invalid option specified” Cause: Check option can be specified for one segment only Action: |
| ORA-10662 ORA-10662, 00000, “Segment has long columns” Cause: Shrink was issued on a segment with long columns. This is not supported. Action: |
| ORA-10663 ORA-10663, 00000, “Object has rowid based materialized views” Cause: Shrink was issued on an object with rowid based materialized views. Action: Drop the rowid based materialized views and issue shrink on the object |
| ORA-10664 ORA-10664, 00000, “Table has bitmap join indexes” Cause: SHRINK was issued on a table with bitmap join indexes. Action: Drop bitmap join indexes and reissue SHRINK on the object. |
| ORA-10665 ORA-10665, 00000, “Inject Evil Literals” Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all literals to be replaced by 2000 letter ‘A’s. A value of 1 does not corrupt anything. Action: never set this event |
| ORA-10666 ORA-10666, 00000, “Do not get database enqueue name” Cause: Action: |
| ORA-10667 ORA-10667, 00000, “Cause sppst to check for valid process ids” Cause: Action: |
| ORA-10668 ORA-10668, 00000, “Inject Evil Identifiers” Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to be replaced by a maximum amount of x’s. It is common for an identifier to be parsed once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be possible to inject such an identifier without the aid of this event. A value of 1 causes no identifiers to be corrupted. Action: never set this event |
| ORA-10690 ORA-10690, 00000, “Set shadow process core file dump type (Unix only)” Cause: Control core file size for shadow processes Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core |
| ORA-10691 ORA-10691, 00000, “Set background process core file type (Unix only)” Cause: Control core file size file for background processes Action: Level 1: Detach SGA before dumping core |
| ORA-10700 ORA-10700, 00000, “Alter access violation exception handler” Cause: Use this event to control what the VMS exception handler does when it encounters an access violation. Action: Level: >=10 Suspend current process on access violation *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** |
| ORA-10701 ORA-10701, 00000, “Dump direct loader index keys” Cause: Dumps index keys at various points in a direct load based on the value of this event. Action: Comment: This is bit mask, interpreted as follows: 0×01: dump all keys as they are being built (use judiciously, as this generates a lot of data!) 0×02: dump index keys which cause OER(1), OER(1409), OER(1452) errors. // |
| ORA-10704 ORA-10704, 00000, “Print out information about what enqueues are being obtained” Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the return values. Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9: also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line |
| ORA-10706 ORA-10706, 00000, “Print out information about global enqueue manipulation” Cause: When enabled, prints out activity in ksi routines. Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types. // Action: Level indicates details: 0-4: show args for each main call 5-9: also indicate callbacks 10+: also printout time for each line |
| ORA-10707 ORA-10707, 00000, “Simulate process death for instance registration” Cause: When enabled, process commits suicide to test instance registration recovery code. Action: Level indicates where the process will die |
| ORA-10708 ORA-10708, 00000, “print out trace information from the RAC buffer cache” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10709 ORA-10709, 00000, “enable parallel instances in create index by default” Cause: Action: set this event only under the supervision of Oracle development Comment: this causes all create index statement to by default use multiple instances. it is for testing purposes only. the level set in the event is the number of instances. Comment: enables analysis of parallel create index – query coordinator |
| ORA-10710 ORA-10710, 00000, “trace bitmap index access” Cause: Action: set this event only under the supervision of Oracle development Comment: display the start-rowid, end-rowid of each bitmap segment – kkrbx row source |
| ORA-10711 ORA-10711, 00000, “trace bitmap index merge” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index merge – kkrbu row source |
| ORA-10712 ORA-10712, 00000, “trace bitmap index or” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index or – kkrbo row source |
| ORA-10713 ORA-10713, 00000, “trace bitmap index and” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index and – kkrba row source |
| ORA-10714 ORA-10714, 00000, “trace bitmap index minus” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index minus – kkrbm row source |
| ORA-10715 ORA-10715, 00000, “trace bitmap index conversion to rowids” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index merge – kkrbt row source |
| ORA-10716 ORA-10716, 00000, “trace bitmap index compress/decompress” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index compression/decompression - modules kdibc, kdibci, kdibco, kdibc3 |
| ORA-10717 ORA-10717, 00000, “trace bitmap index compaction trace for index creation” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of bitmap index creation - modules kkrbc |
| ORA-10718 ORA-10718, 00000, “event to disable automatic compaction after index creation” Cause: Action: set this event only under the supervision of Oracle development Comment: enables isolation of index creation problems. ie compaction is an optional part of the index creation algorithem which improves query performance and shrinks index size modules kkrbc |
| ORA-10719 ORA-10719, 00000, “trace bitmap index dml” Cause: Action: set this event only under the supervision of Oracle development Comment: enables analysis of inserts update and deletes into tables with bitmap indexes modules kkrbc |
| ORA-10720 ORA-10720, 00000, “trace db scheduling” Cause: Action: set this event only under the supervision of Oracle development Comment: traces db scheduling |
| ORA-10721 ORA-10721, 00000, “Internal testing – temp table transformation” Cause: Action: |
| ORA-10722 ORA-10722, 00000, “set parameters for CPU frequency calculation (debug)” Cause: Action: set this event only under the supervision of Oracle development Comment: changes parameters for CPU frequency calculation |
| ORA-10723 ORA-10723, 00000, “Internal testing – release buffer for buffer cache shrink” Cause: Action: |
| ORA-10724 ORA-10724, 00000, “trace cross-instance broadcast” Cause: Action: set this event only under the supervision of Oracle development Comment: enables tracing of cross-instance broadcast (KSXR) |
| ORA-10725 ORA-10725, 00000, “bitmap index version control” Cause: Action: Set this event only under the supervision of Oracle development. The trace level is a bitfield, so use it as you would a flag. // LEVEL ACTION //————————————————————————— 0×0001 For bitmap indexes with version 0, DML on these bitmap indexes will be same as with 9i releases (that is, it simulates the bitmap index DML of previous releases). |
| ORA-10726 ORA-10726, 00000, “frequent itemset counting” Cause: Action: set this event only under the supervision of Oracle development Comment: enables tracing of internal execution of frequent itemset counting |
| ORA-10727 ORA-10727, 00000, “introduce failure events in IPC” Document: NO Cause: Action: Internal testing only. Comment: |
| ORA-10730 ORA-10730, 00000, “trace row level security policy predicates” Document: NO Cause: Action: Comment: |
| ORA-10731 ORA-10731, 00000, “dump SQL for CURSOR expressions” Cause: Action: set this event only under the supervision of Oracle development Comment: traces SQL statements generated to execute CURSOR expressions |
| ORA-10732 ORA-10732, 00000, “honor pctfree during insert into AQ IOTs” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: If set, then we will honor pctfree, during SQL INSERTs and direct kdiins0 calls from AQ, for IOTs that are used as AQ queue tables. |
| ORA-10733 ORA-10733, 00000, “test transient-IOT metadata during PMO cleanup” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: causes an internal error to be raised if inconsistent metadata is detected during cleanup of transient-IOTs which were left behind by failed Partition Maintenance Operations. Enable this event only during testing. |
| ORA-10734 ORA-10734, 00000, “reroute external procedures” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: execute external procedures using plsql |
| ORA-10735 ORA-10735, 00000, “debug ksws operations” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: Causes debug trace to be dumped for ksws routines |
| ORA-10736 ORA-10736, 00000, “buffer cache pin history dump” Cause: Action: Set this event only under the supervision of Oracle development. Trace level is a bitfield. // LEVEL ACTION //————————————————————————— 0×0001 Force redo dump during buffer pin history dump 0×0002 Disable redo dump during buffer pin history dump 0×0004 Print diagnostic text for the redo dump // |
| ORA-10737 ORA-10737, 00000, “test block checking” Document: NO Cause: Action: Set this event only under the supervision of Oracle development. Comment: Internal testing event for block checking. |
| ORA-10738 ORA-10738, 00000, “internal block testing” Document: NO Cause: Action: Set this event only under the supervision of Oracle development. |
| ORA-10739 ORA-10739, 00000, “debug WLM (kywm) operations” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: Causes debug trace to be dumped for kywm routines |
| ORA-10740 ORA-10740, 00000, “disables fix for bug 598861″ Cause: Action: set this event only under the supervision of Oracle development Comment: disables fix for bug 598861. The fix changes slightly the cost estimations for set queries in views, and thereby changes query plans from previous versions modules vop |
| ORA-10750 ORA-10750, 00000, “test rollback segment blksize guessing for index array insert” Cause: Action: set this event only under the supervision of Oracle development Comment: causes internal error to be raised if a transaction repeatedly (100 times) fails to bind to a rollback segment because block size is too small. (Default behaviour is to silently assume the minimum database block size possible after that many failures). Enable this event only during testing. |
| ORA-10751 ORA-10751, 00000, “override for remote row source maximum buffer size” Cause: Action: set this event only under the supervision of Oracle development Comment: To change the default value of 256000. |
| ORA-10752 ORA-10752, 00000, “override for the Exponential Moving Average factor” Cause: Action: set this event only under the supervision of Oracle development Comment: To change the default value of 50%. |
| ORA-10753 ORA-10753, 00000, “enforce deterministic behaviour for prefetching row source” Cause: Action: set this event only under the supervision of Oracle development. Comment: prefetch will disregard buffer cache state and be deterministic based on level set Trace level is a bitfield. // LEVEL ACTION //————————————————————————— 0×0001 Always enable prefetching 0×0002 Always disable prefetching 0×0004 Print diagnostic text for each of the above levels, ie use level 5 to trace enabling and level 6 to trace disabling. // |
| ORA-10780 ORA-10780, 00000, “LogMiner API trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst tracing of logminer internal api |
| ORA-10781 ORA-10781, 00000, “LogMiner reader trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst tracing of logminer reader process |
| ORA-10782 ORA-10782, 00000, “LogMiner preparer trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst tracing of logminer preparer process |
| ORA-10783 ORA-10783, 00000, “LogMiner builder trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst tracing of logminer builder process |
| ORA-10784 ORA-10784, 00000, “LogMiner dictionary trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst tracing of logminer dictionary |
| ORA-10785 ORA-10785, 00000, “LogMiner trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10786 ORA-10786, 00000, “call push/pop (KSU)” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables tracing of call push/pop operations |
| ORA-10787 ORA-10787, 00000, “trace intra-instance broadcast” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables tracing of intra-instance broadcast (KSR) |
| ORA-10788 ORA-10788, 00000, “trace call stacks” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables tracing of call stack info |
| ORA-10789 ORA-10789, 00000, “LogMiner test event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: changes logminer behavior for testing |
| ORA-10790 ORA-10790, 00000, “LogMiner trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10791 ORA-10791, 00000, “Logical Standby swithover/failover trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst trancing of switchover and failover in logical |
| ORA-10792 ORA-10792, 00000, “Logical Standby XDAT trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development Comment: enables kst trancing os XDAT usage |
| ORA-10793 ORA-10793, 00000, “Logical Standby trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10794 ORA-10794, 00000, “Logical Standby trace event” Document: NO Cause: Action: set this event only under the supervision of Oracle development |
| ORA-10795 ORA-10795, 00000, “VKTM Process trace event” Document: NO Cause: Action: Set this event only under the supervision of Oracle Support Services. Comment: enable ksd/kst tracing for VKTM process |
| ORA-10796 ORA-10796, 00000, “Elevate Scheduler Priority trace event” Document: NO Cause: Action: Set this event only under the supervision of Oracle development Comment: enable ksd tracing for elevate/revert process scheduler priority |
| ORA-10800 ORA-10800, 00000, “disable Smart Disk scan” Document: NO Cause: Action: |
| ORA-10804 ORA-10804, 00000, “reserved for ksxb” Cause: Action: |
| ORA-10806 ORA-10806, 00000, “Switch to 7.3 mode when detaching sessions” Cause: Action: |
| ORA-10807 ORA-10807, 00000, “Disable user id check when switching to a global transaction” Cause: Action: |
| ORA-10808 ORA-10808, 00000, “Enable assert when waiting without a reason” Cause: Action: Set this event only under the supervision of Oracle development Comment: This event will catch clients that call kslwait without providing any wait reason (see bug 1743159). |
| ORA-10809 ORA-10809, 00000, “Trace state object allocate / free history” Document: NO Cause: Action: Set this event only under the supervision of Oracle development Comment: This event will trace the history of KSS allocations / deletions. level: 0 = disabled, 1 = cleanup only, 2 = always |
| ORA-10810 ORA-10810, 00000, “Trace snapshot too old” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10811 ORA-10811, 00000, “Trace block cleanouts” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10812 ORA-10812, 00000, “Trace Consistent Reads” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10826 ORA-10826, 00000, “enable upgrade/downgrade error message trace” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10827 ORA-10827, 00000, “enable upgrade/downgrade diagnostics” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10828 ORA-10828, 00000, “memory allocator error” Cause: Error in the memory allocator Action: Check the trace files and other relevant output |
| ORA-10830 ORA-10830, 00000, “Trace group by sort row source” Cause: Action: set this event only under the supervision of Oracle development. trace level is a bitfield // LEVEL ACTION //————————————————————————— 0×0001 trace adaptive fetch usage 0×0002 trace exceptions during aggregation 0×0004 trace use of one comparison for all key columns // |
| ORA-10831 ORA-10831, 00000, “Trace group by rollup row source” Cause: Action: set this event only under the supervision of Oracle development. trace level is a bitfield // LEVEL ACTION //————————————————————————— 0×0001 trace use of one comparison for all key columns |
| ORA-10832 ORA-10832, 00000, “Trace approximate NDV row source” Cause: Action: set this event only under the supervision of Oracle development. trace level is a bitfield // LEVEL ACTION //————————————————————————— 0×0001 trace |
| ORA-10839 ORA-10839, 00000, “trace / debug caching module (qesca.c)” Cause: Document: NO Action: Set this event only under the supervision of Oracle Development. // LEVEL ACTION //————————————————————————— 0×0001 trace / debug caching 0×0002 dump probe / retrieve / insert cache values |
| ORA-10840 ORA-10840, 00000, “trace / debug pl/sql caching module (kkxmInitCache)” Cause: Document: NO Action: Set this event only under the supervision of Oracle Development. // LEVEL ACTION //————————————————————————— 0×0001 trace / debug pl/sql caching |
| ORA-10841 ORA-10841, 00000, “Default un-inintialized charact set form to SQLCS_IMPLICIT” Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form Action: This event sets charset form as SQLCS_IMPLICIT when it is 0 |
| ORA-10842 ORA-10842, 00000, “Event for OCI Tracing and Statistics Info” Cause: This event is meant for tracing OCI Calls and getting statistics Action: This event sets tracing OCI Calls and gets statistics info |
| ORA-10843 ORA-10843, 00000, “Event for client result cache tracing” Document: NO Cause: This is an internal event. Action: N/A |
| ORA-10844 ORA-10844, 00000, “turn on Native Net IPC debugging (skgxp)” Cause: Action: Enables debugging code for Native Net IPC (skgxp) |
| ORA-10845 ORA-10845, 00000, “Enable Director tracing” Cause: N/A Action: Enable tracing of director/workload manager packages |
| ORA-10846 ORA-10846, 00000, “Enable Director Single Node Testing” Document: NO Cause: N/A Action: Enable Single Node Testing |
| ORA-10847 ORA-10847, 00000, “OCI dump action is being invoked for an internal error” Document: NO Cause: An internal error was encountered or EVENT_10842 has been set to level 16 which will dump the OCI process state, current state and the stack trace. Action: Disable EVENT_10842 or check the cause of the internal error. |
| ORA-10848 ORA-10848, 00000, “OCI Non Blocking not supported with %s” Cause: Attempt made to set connection as non-blocking with another feature that does not support non-blocking. Action: Use blocking connection. |
| ORA-10849 ORA-10849, 00000, “Internal OCI event number” Cause: N/A Action: Set this event only under the supervision of Oracle Support or Development. This event enable compatible behavior with sending describe information when a cursor rebuilt. |
| ORA-10850 ORA-10850, 00000, “Enable time manager tracing” Cause: Action: |
| ORA-10851 ORA-10851, 00000, “Allow Drop command to drop queue tables” Document: NO Cause: re-enable SQL Drop DDL for queue tables. Action: last resort to drop queue table if all other options fail. The user have to manually cleanup AQ’s metadata after this operation. |
| ORA-10852 ORA-10852, 00000, “Enable tracing for Enqueue Dequeue Operations” Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10854 ORA-10854, 00000, “Sets poll count used for AQ listen code under RAC” Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10856 ORA-10856, 00000, “Disable AQ propagator from using streaming” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10857 ORA-10857, 00000, “Force AQ propagator to use two-phase commit” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10858 ORA-10858, 00000, “Crash the AQ propagator at different stages of commit” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10859 ORA-10859, 00000, “Disable updates of message retry count” Document: NO Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DISABLING THE RETRY FEATURE IN THE EVENT THAT IT CAUSES OTHER INTERNAL ERRORS. |
| ORA-10860 ORA-10860, 00000, “event for AQ admin disable new name parser” Document: NO Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. THIS EVENT IS NOT TO BE TURNED ON BY ANY CUSTOMER. DOING SO, MAY CAUSE AQ DICTIONARY CORRUPTION |
| ORA-10861 ORA-10861, 000000, “disable storing extended message properties” Document: NO Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY TO DISABLE STORING NEW MESSAGE PROPERTIES SUCH AS SENDER_ID AND ORIGINAL_MESSAGE_ID. // |
| ORA-10862 ORA-10862, 00000, “resolve default queue owner to current user in enqueue/dequeue” Cause: resolve default queue owner to current user in enqueue/dequeue. Action: turn on if client wish to resolve the default queue owner to the current user. If not turned on, the default queue owner will be resolved to the login user. |
| ORA-10863 ORA-10863, 00000, “Control behavior of buffered background operations” Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10864 ORA-10864, 00000, “event to enable AQ dedicated propagation” Document: NO Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, ONE JOB QUEUE PROCESS WILL PROPAGATE FOR ONLY ONE PROPAGATION SCHEDULE |
| ORA-10865 ORA-10865, 00000, “Control tracing of notification operations” Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10866 ORA-10866, 00000, “event to order dequeue by condition” Document: NO Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, THE DEQUEUE ORDER THE MESSAGES BASED ON CONDITION. // |
| ORA-10871 ORA-10871, 00000, “dump file open/close timestamp during media recovery” Document: No Cause: Action: For dumping purpose. |
| ORA-10872 ORA-10872, 00000, “Flashback Database fault insertion event #%s.” Document: NO Cause: Causes faults to be inserted into Flashback Database code. This should only be enabled for internal testing. Action: Level 1 – Die after restoring database, before shrinking fuzziness. Level 2 – Die after rstoring database and after shrinking fuzziness. Level 3 – Die after restoring control file. Level 4 – Die after set cf checkpoint during an undo of a cf change Level 5 – Die after restoring cf, before setting cf checkpoint Level 6 – Force a block checksum error on a flashback log block Level 7 – Force a file creation error during fb recovery Level 8 – Force an error after fb recovery file recreation |
| ORA-10873 ORA-10873, 00000, “file %s needs to be either taken out of backup mode or media recovered” Cause: An attempt was made to open a database after an instance failure or SHUTDOWN ABORT interrupted an online backup. Action: If the indicated file is not a restored backup, then issue the ALTER DATABASE END BACKUP command and open the database. If the file is a restored online backup, then apply media recovery to it and open the database. |
| ORA-10874 ORA-10874, 00000, “Change max logfiles in hashtable in krfbVerifyRedoAvailable” Document: No Cause: Action: For testing purposes // |
| ORA-10875 ORA-10875, 00000, “Require instance bounce after switchover to primary” Document: No Cause: Action: For testing purposes // |
| ORA-10876 ORA-10876, 00000, “IDR Test event” Document: No Cause: Action: Level 1 – x$ir_working_repair_set returns manual options. Should only be used when testing IR framework. 2 – force a failure revalidation timeout. 3 – force a failure in getAdviseID. // |
| ORA-10877 ORA-10877, 00000, “error signaled in parallel recovery slave %s” Cause: A parallel recovery slave reached an exception condition. Action: Check the following error message for the cause, and consult your error manual for the appropriate action. // |
| ORA-10878 ORA-10878, 00000, “parallel recovery slave died unexpectedly” Cause: A parallel recovery slave died unexpectedly, PMON cleaning up the process. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details. |
| ORA-10880 ORA-10880, 00000, “trace Java VM execution” Document: NO *Cause *Action // |
| ORA-10891 ORA-10891, 00000, “disable column pruning in ANSI join transformation” Document: NO Cause: N/A Action: Set this event only under the supervision of Oracle development. Comment: Not for general purpose use. LEVEL ACTION //————————————————————————— > 0 Do not attempt to automatically prune away unreferenced columns during ANSI join transformation when compiling SQL queries. |
| ORA-10900 ORA-10900, 00000, “extent manager fault insertion event #%s” Cause: causes faults to be generated in instrumented extent code Action: this should only be enabled for internal testing |
| ORA-10901 ORA-10901, 00000, “disable the fix for bug 1230798″ Cause: Action: |
| ORA-10902 ORA-10902, 00000, “disable seghdr conversion for ro operation” Cause: causes seghdr conversion to be turned off for ro ops(#555856) Action: this should be enabled only if determined that bug 555856 has occured. Table needs to be exported subsequently |
| ORA-10903 ORA-10903, 00000, “Force tablespaces to become locally managed” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. |
| ORA-10904 ORA-10904, 00000, “Allow locally managed tablespaces to have user allocation” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE. |
| ORA-10905 ORA-10905, 00000, “Do cache verification (kcbcxx) on extent allocation” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10906 ORA-10906, 00000, “Unable to extend segment after insert direct load” Cause: This is a restriction with insert direct load transactions. Action: When a segment has been insert direct loaded, avoid DMLs that could cause more space to be consumed. |
| ORA-10907 ORA-10907, 00000, “Trace extent management events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10908 ORA-10908, 00000, “Trace temp tablespace events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10909 ORA-10909, 00000, “Trace free list events” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10910 ORA-10910, 00000, “inject corner case events into the RAC buffer cache” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10911 ORA-10911, 00000, “Locally managed SYSTEM tablespace bitmaps can be modified only under the supervision of Oracle Support” Cause: N/A Action: |
| ORA-10912 ORA-10912, 00000, “Used to perform admin operations on locally managed SYSTEM tablespace” Cause: N/A Action: The event should be used only under the supervision of Oracle Support |
| ORA-10913 ORA-10913, 00000, “Create locally managed database if compatible > 920 by default” Cause: N/A Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. |
| ORA-10914 ORA-10914, 00000, “invalid TABLESPACE GROUP clause” Cause: An invalid option appears for TABLESPACE GROUP clause. Action: Specify a valid tablespace group name. |
| ORA-10915 ORA-10915, 00000, “TABLESPACE GROUP cannot be specified for this type of tablespace” Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was used while creating/altering a tablespace that is not TEMPORARY. Action: Remove the TABLESPACE GROUP clause. |
| ORA-10916 ORA-10916, 00000, “TABLESPACE GROUP already specified” Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was specified more than once. Action: Remove all but one of the TABLESPACE GROUP specifications. |
| ORA-10917 ORA-10917, 00000, “TABLESPACE GROUP cannot be specified” Cause: The tablespace name specified in the command is actually the name of a tablespace group. Action: Please specify an appropriate tablespace name. |
| ORA-10918 ORA-10918, 00000, “TABLESPACE GROUP name cannot be the same as tablespace name” Cause: The tablespace group name specified in the command is the same as the tablespace being CREATEd/ALTERed. Action: Please specify an appropriate tablespace group name. |
| ORA-10919 ORA-10919, 00000, “Default temporary tablespace group must have at least one tablespace” Cause: An attempt was made to move the only tablespace in the default database temporary tablespace group to another tablespace group. Action: Either change the database default temporary tablespace or add another tablespace to the group that this tablespace belongs to. |
| ORA-10920 ORA-10920, 00000, “Cannot offline tablespace belonging to default temporary tablespace group” Cause: An attempt was made to offline a tablespace in the default database temporary tablespace group. Action: Either change the database default temporary tablespace or change the tablespace group of this tablespace. |
| ORA-10921 ORA-10921, 00000, “Cannot drop tablespace belonging to default temporary tablespace group” Cause: An attempt was made to drop a tablespace in the default database temporary tablespace group. Action: Either change the database default temporary tablespace or change the tablespace group of this tablespace. |
| ORA-10922 ORA-10922, 00000, “Temporary tablespace group is empty” Cause: An attempt was made to allocate a temporary segment in a group, which now no longer has any members. Action: Either add some temporary tablespaces or change the temporary tablespace for this user. |
| ORA-10923 ORA-10923, 00000, “prints debug information for object space server manageability” Cause: Action: |
| ORA-10924 ORA-10924, 00000, “import storage parse error ignore event” Cause: causes server to ignore specific error associated with freelists and freelist groups when parsing Action: this should be enabled by import code only |
| ORA-10925 ORA-10925, 00000, “trace name context forever” Cause: When enabled, turns off bugfix 237911 Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10926 ORA-10926, 00000, “trace name context forever” Cause: When enabled, turns off bugfix 190119 Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10927 ORA-10927, 00000, “trace name context forever” Cause: When enabled, turns off bugfix 235190 Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10928 ORA-10928, 00000, “trace name context forever” * Cause: Action: Set this event only under the supervision of Oracle Development. * Comment: This event causes PL/SQL to dump out information to trace files. |
| ORA-10929 ORA-10929, 00000, “trace name context forever” Cause: When enabled, turns off bugfix 343966 Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10930 ORA-10930, 00000, “trace name context forever” Cause: When enabled, provides V7 behavior for fixed char binds Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10931 ORA-10931, 00000, “trace name context forever” Cause: When enabled, allows normal packages to be compiled with standard extensions like “<ADT_1>” Action: Set this event only for a short amount of time. Once the packages are compiled, this event should be turned off. Level 1 – Turn the event on Level > 1 – Turn the event off |
| ORA-10932 ORA-10932, 00000, “trace name context forever” Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10933 ORA-10933, 00000, “trace name context forever” Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10936 ORA-10936, 00000, “trace name context forever” Cause: When enabled, disables one or more features or bug fixes available in versions 7.x and 8.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10938 ORA-10938, 00000, “trace name context forever” * Cause: Action: When set, this event enables tracing of PL/SQL calls and exceptions. * Comment: Setting this event could result in some performance slowdown. |
| ORA-10939 ORA-10939, 00000, “trace name context forever” * Cause: Action: When set, this event turns on coverage for PL/SQL procedures and functions. * Comment: Setting this event could result in some performance slowdown. |
| ORA-10940 ORA-10940, 00000, “trace name context forever” Cause: Size of the PL/SQL tracing circular buffer, in kilobytes. Action: Set this event in concert with the 10938 event and the _PLSQL_DUMP_BUFFER_EVENTS init.ora parameter, under supervision of Oracle Support. |
| ORA-10941 ORA-10941, 00000, “trace name context forever” Cause: When enabled, turns on PL/SQL profiler Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10943 ORA-10943, 00000, “trace name context forever” Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10944 ORA-10944, 00000, “trace name context forever” Cause: When enabled, allows or controls PL/SQL OPT code gen project. available only in version 8.2+. Action: set this event ONLY for development of the OPT project. This is not for general use or deployment. |
| ORA-10945 ORA-10945, 00000, “trace name context forever” Cause: When enabled, disables the behaviour change introduced by the fix for bug 822764, which traps and handles invalidations of packages whereas the previous behaviour was to use stale invalidated instantiations of the stateful package body. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10946 ORA-10946, 00000, “trace name context forever” Cause: When enabled, disables one or more features or bug fixes available only in version 10.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10947 ORA-10947, 00000, “trace name context forever” Cause: When enabled, causes various PL/SQL warnings related debugging info to be written in a trace file. Useful for debugging varous Oracle processes. available only in version 10.x. Action: set this event ONLY if necessary – after reading the README for this release or under supervision of Oracle Support. |
| ORA-10948 ORA-10948, 00000, “trace name context forever” Cause: When enabled, inflate callout argument. available only in version 10.x. Action: internal use only. |
| ORA-10949 ORA-10949, 00000, “Disable autotune direct path read for full table scan” Cause: Action: Disable autotune direct path read for serial full table scan. |
| ORA-10960 ORA-10960, 00000, “AQ tracing event” // Document: NO Cause: Action: // |
| ORA-10970 ORA-10970, 00000, “backout event for bug 2133357″ Cause: 2133357 dynamically sets the varying width flag and character width. Lob data which is not migrated during migration from single byte to multibyte charater set will be displayed as special characters. Action: To help migrate lob data which was not migrated during migration by backing out 2133357, so lob data can be selected and moved to multibyte character set. |
| ORA-10971 ORA-10971, 00000, “prints debugging information for LOBs” Document: No Cause: Action: None |
| ORA-10972 ORA-10972, 00000, “raise a 1551 exception in kdu_array_flush” Document: No Cause: Action: None |
| ORA-10973 ORA-10973, 00000, “backout evet for 2619509″ Cause: 2619509 catches offsets when not reading/writing on full character boundary. To facilitate backward compatiblity event is being introduced. Action: To help upgrade/migrate issues which already have corrupt data |
| ORA-10974 ORA-10974, 00000, “Turn on LOB integrity verification” Document: No Cause: Action: None |
| ORA-10975 ORA-10975, 00000, “trace execution of parallel propagation” Document: NO Cause: Action: |
| ORA-10976 ORA-10976, 00000, “internal package related tracing” Document: NO Cause: Action: |
| ORA-10977 ORA-10977, 00000, “trace event for RepAPI” Document: NO Cause: N/A. Action: Set this event only under the supervision of Oracle development. Comment: Not for general purpose use. |
| ORA-10979 ORA-10979, 00000, “trace flags for join index implementation” Cause: This is an informational message. Action: Values are as follows: LEVEL ACTION //————————————————————————— > 1 Dump refresh expressions (SQL) to trace file. > 999 If a complete refresh is invoked, it will not be performed but the system will assume that a complete refresh was done, causing the view to be VALID and updating timestamps. This should be used only under Oracle Support supervision. |
| ORA-10980 ORA-10980, 00000, “prevent sharing of parsed query during Materialized View query generation” Document: NO Cause: N/A. Action: Set this event only under the supervision of Oracle development. Comment: Not for general purpose use. |
| ORA-10981 ORA-10981, 00000, “dscn computation-related event in replication” Document: NO Cause: N/A. Action: |
| ORA-10982 ORA-10982, 00000, “event to turn off CDC-format MV Logs” Document: NO Cause: N/A. Action: |
| ORA-10983 ORA-10983, 00000, “event to enable Create_Change_Table debugging” Document: NO Cause: N/A. Action: |
| ORA-10984 ORA-10984, 00000, “subquery materialized view-related event” Document: NO Cause: N/A Action: Set this event only under the supervision of Oracle development. Comment: Not for general purpose use. |
| ORA-10985 ORA-10985, 00000, “event for NULL refresh of materialized views” Document: NO Cause: N/A Action: Set this event only under the supervision of Oracle development. Comment: Not for general purpose use. |
| ORA-10986 ORA-10986, 00000, “donot use HASH_AJ in refresh” Document: NO Cause: N/A Action: Set this event while doing refresh if the delta snapshot is small Comment: Not for general purpose use. |
| ORA-10987 ORA-10987, 00000, “event for the support of caching table with object feature” Document: NO Cause: N/A Action: Set this event while caching tables with object features. Comment: Not for general purpose use. |
| ORA-10988 ORA-10988, 00000, “event to get exclusive lock during materialized view refresh in IAS” Document: NO Cause: N/A Action: Set this event if you want to get exclusive lock on the Updatable MV container table during refresh in IAS Comment: Not for general purpose use. LEVEL ACTION //————————————————————————— > 0 Get exclusive lock on the updatable MV container table during refresh in IAS |
| ORA-10989 ORA-10989, 00000, “event to internally create statistics MV” Document: NO Cause: N/A Action: The event is internally used to create statsMV Comment: Not for general purpose use. LEVEL ACTION //————————————————————————— > 0 |
| ORA-10990 ORA-10990, 00000, “dump spreadsheet info” Cause: Action: set this event only under the supervision of Oracle Development // LEVEL ACTION //————————————————————————— 0×0001 dump pruned rules during graph analysis 0×0002 dump level of the rules after ordering in graph analysis 0×0004 dump spreadsheet filter |
| ORA-10991 ORA-10991, 00000, “event for optimizing the online redefinition instantiation” |
| ORA-10992 ORA-10992, 00000, “event to enable dbms_job instead of dbms_scheduler” Cause: Action: enables dbms_job instead of dbms_scheduler Comment: set this event only under the supervision of Oracle Development LEVEL ACTION //————————————————————————— 0×0001 enable dbms_job instead of dbms_scheduler for MV refresh |
| ORA-10993 ORA-10993, 00000, “Runtime enable IOQ batching” Cause: Action: Comment: set this event only under the supervision of Oracle Development |
| ORA-10994 ORA-10994, 00000, “Compiletime enable IOQ batching” Cause: Action: Comment: set this event only under the supervision of Oracle Development |
| ORA-10995 ORA-10995, 00000, “general event for materialized views” Document: NO Cause: N/A Action: This internal event is used to enable various actions associated with MVs. The event level is interpreted as a bitmap of actions to enable. // Comment: Not for general purpose use. LEVEL ACTION //————————————————————————— 0×0001 enable callback-based refresh 0×0002 invalidate dependents for online redef 0×0004 allow PCT fast refresh after CONSIDER FRESH 0×0008 do not use an extended Merge statement during MAV fast refresh |
| ORA-10997 ORA-10997, 00000, “another startup/shutdown operation of this instance inprogress” Cause: An Oracle Instance startup or shutdown operation failed to procure the serialization primitive. Another foreground process may have attempted startup or shutdown operation in parallel. Action: Check additional error messages in the alert log and the process trace file. |
| ORA-10998 ORA-10998, 00000, “event to enable short stack dumps in system state dumps” Document: NO Cause: N/A Action: enables short stack dumps for every active process in a system state dump Comment: set this event only under the supervision of Oracle Support |
| ORA-10999 ORA-10999, 00000, “do not get database enqueue name” Cause: Action: |
| ORA-12000 ORA-12000, 00000, “a materialized view log already exists on table ‘%s’” Cause: Action: |
| ORA-12001 ORA-12001, 00000, “cannot create log: table ‘%s’ already has a trigger” Cause: Materialized view logs are filled by a trigger on the master table. That trigger cannot be created. Action: To create a materialized view log, drop the current trigger on the master. |
| ORA-12002 ORA-12002, 00000, “there is no materialized view log on table \”%s\”.\”%s\”" Cause: There was no materialized view log on the master table. Action: Create a materialized view log on the master table. |
| ORA-12003 ORA-12003, 00000, “materialized view \”%s\”.\”%s\” does not exist” Cause: The materialized view with the given owner and name does not exist. Action: Verify inputs and create a materialized view. |
| ORA-12004 ORA-12004, 00000, “REFRESH FAST cannot be used for materialized view \”%s\”.\”%s\”" Cause: The materialized view log does not exist or cannot be used. PCT refresh is also not enabled on the materialized view Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log or PCT refresh is possible after a given set of changes, REFRESH FAST will be available starting the next time the materialized view is refreshed. |
| ORA-12005 ORA-12005, 00000, “may not schedule automatic refresh for times in the past” Cause: An attempt was made to schedule an automated materialized view refresh for a time in the past. Action: Choose a time in the future instead. |
| ORA-12006 ORA-12006, 00000, “a materialized view with the same user.name already exists” Cause: Action: |
| ORA-12007 ORA-12007, 00000, “materialized view reuse parameters are inconsistent” Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. REUSE command was given inconsistent parameters immediately after the REUSE. Action: Examine the other messages on the stack to find the problem. |
| ORA-12008 ORA-12008, 00000, “error in materialized view refresh path” Cause: Table SNAP$_<mview_name> reads rows from the view MVIEW$_<mview_name>, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table <master_owner>.MLOG$_<master> is also referenced. Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_<mview_name>, MVIEW$_<mview_name>, <mowner>.<master>@<dblink>, <mowner>.MLOG$_<master>@<dblink> still exist. |
| ORA-12009 ORA-12009, 00000, “materialized views may not contain long columns” Cause: Action: |
| ORA-12010 ORA-12010, 00000, “cannot create materialized view log on table owned by SYS” Cause: An attempt was made to create a materialized view log on the table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables. Action: Do not create a materialized view log on SYS tables. |
| ORA-12011 ORA-12011, 00000, “execution of %s jobs failed” Cause: An error was caught in dbms_ijob.run from one or more jobs which were due to be run. Action: Look at the alert log for details on which jobs failed and why. |
| ORA-12012 ORA-12012, 00000, “error on auto execute of job %s” Cause: An error was caught while doing an automatic execution of a job. Action: Look at the accompanying errors for details on why the execute failed. |
| ORA-12013 ORA-12013, 00000, “updatable materialized views must be simple enough to do fast refresh” Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by caluse. Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them. |
| ORA-12014 ORA-12014, 00000, “table ‘%s’ does not contain a primary key constraint” Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH PRIMARY KEY option and the master table did not contain a primary key constraint or the constraint was disabled. Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint. |
| ORA-12015 ORA-12015, 00000, “cannot create a fast refresh materialized view from a complex query” Cause: Neither ROWIDs and nor primary key constraints are supported for complex queries. Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view. |
| ORA-12016 ORA-12016, 0000, “materialized view does not include all primary key columns” Cause: The query that instantiates the materialized view did not include all of the columns in the master’s primary key constraint. Action: Include all of the master’s primary key columns in the materialized view query or create a ROWID materialized view. |
| ORA-12017 ORA-12017, 0000, “cannot alter primary key mview ‘%s’ to a rowid mview” Cause: An attempt was made to convert the primary key of a materialized view to a ROWID materialized view. Action: Conversion of a primary key materialized view to a ROWID materialized view is not supported. Create a new materialized view with ROWIDs or drop and recreate the materialized view with ROWIDs. |
| ORA-12018 ORA-12018, 0000, “following error encountered during code generation for \”%s\”.\”%s\”" Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors. Action: Correct the problem indicated in the following error messages and repeat the operation. |
| ORA-12019 ORA-12019, 0000, “master table is a synonym to a remote object” Cause: An attempt was made to create a materialized view or a materialized view log on a remote synonym which is unsupported. Action: Do not create a materialized view or materialized view log on a remote synonym. |
| ORA-12020 ORA-12020, 00000, “materialized view %s is not registered” Cause: An attempt was made to unregister a materialized view that is not registered. Action: No action required. |
| ORA-12021 ORA-12021, 0000, “materialized view \”%s\”.\”%s\” is corrupt” Cause: The materialized view indicated is no longer valid. Action: Contact Oracle Customer Support. |
| ORA-12022 ORA-12022, 0000, “materialized view log on \”%s\”.\”%s\” already has rowid” Cause: Materialized view log on the indicated table already has ROWID information. Action: No action required. |
| ORA-12023 ORA-12023, 0000, “missing index on materialized view \”%s\”.\”%s\”" Cause: The specified ROWID materialized view did not have the required index on the ROWID column of its underlying table. Action: Drop and recreate the materialized view. |
| ORA-12024 ORA-12024, 0000, “materialized view log on \”%s\”.\”%s\” does not have primary key columns” Cause: Materialized view log on the indicated table does not have primary key information. Action: Add primary keys to the materialized view log using the ALTER MATERIALIZED VIEW command. |
| ORA-12025 ORA-12025, 0000, “materialized view log on \”%s\”.\”%s\” already has primary keys” Cause: Materialized view log on the indicated table already has primary key columns. Action: No action required. |
| ORA-12026 ORA-12026, 0000, “invalid filter column detected” Cause: One or more of the specified filter columns did not exist or was a primary key column or a primary key based object identifier. Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns or primary key based object identifiers are not included in the list of filter columns. |
| ORA-12027 ORA-12027, 0000, “duplicate filter column” Cause: One or more of the specified filter columns were already being recorded in the materialized view log. Action: Describe the materialized view log table and reissue the SQL command with the filter columns that are already being recorded in the materialized view log. |
| ORA-12028 ORA-12028, 0000, “materialized view type is not supported by master site %s” Cause: Pre-Oracle8 master sites are not able to support primary key or subquery materialized views that are able to perform a fast refresh. Action: Create a ROWID materialized view or use a master table from an Oracle8 site. |
| ORA-12029 ORA-12029, 0000, “LOB columns may not be used as filter columns” Cause: An attempt was made to use LOB columns as filter columns. Action: Remove LOB columns from the filter columns list and retry command. // |
| ORA-12030 ORA-12030, 0000, “cannot create a fast refresh materialized view” Cause: The materialized view log did not exist or did not log the information needed by the materialized view to perform a fast refresh. Action: Ensure that the materialized view log exists and logs the necessary information. – For ROWID materialized views, the master table’s ROWID must be logged. – For primary key materialized views, the master table’s primary key columns must be logged. – For subquery materialized views, the filter columns, primary key, and ROWID values must be logged. – For object materialized views, object id must be logged. // |
| ORA-12031 ORA-12031, 0000, “cannot use primary key columns from materialized view log on \”%s\”.\”%s\”" Cause: The materialized view log either did not have primary key columns logged, or the timestamp associated with the primary key columns was more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add primary key columns to the materialized view log, if required. // |
| ORA-12032 ORA-12032, 0000, “cannot use rowid column from materialized view log on \”%s\”.\”%s\”" Cause: The materialized view log either does not have ROWID columns logged, or the timestamp associated with the ROWID columns is more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required. // |
| ORA-12033 ORA-12033, 0000, “cannot use filter columns from materialized view log on \”%s\”.\”%s\”" Cause: The materialized view log either did not have filter columns logged, or the timestamp associated with the filter columns was more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add filter columns to the materialized view log, if required. // |
| ORA-12034 ORA-12034, 0000, “materialized view log on \”%s\”.\”%s\” younger than last refresh” Cause: The materialized view log was younger than the last refresh. Action: A complete refresh is required before the next fast refresh. // |
| ORA-12035 ORA-12035, 0000, “could not use materialized view log on \”%s\”.\”%s\”" Cause: The materialized view log did not exist or could not be used. Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed. // |
| ORA-12036 ORA-12036, 0000, “updatable materialized view log is not empty, refresh materialized view” Cause: The updatable materialized view log was not empty. The updatable materialized view log must be empty before an updatable rowid materialized view can be altered to a primary key materialized view. Action: Ensure that updatable materialized view log is empty by refreshing the materialized view before converting the updatable ROWID materialized view to a primary key materialized view. // |
| ORA-12037 ORA-12037, 0000, “unknown export format” Cause: An attempt was made to import a materialized view exported by an unknown export version (e.g., from a newer release than the importing site) Action: Re-export the file using a version of export known by the importing site. // |
| ORA-12038 ORA-12038, 00000, “string literal has unexpected length” Cause: Action: // |
| ORA-12039 ORA-12039, 00000, “unable to use local rollback segment \”%s\”" Cause: A local rollback segment was specified in the CREATE MATERIALIZED VIEW command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the materialized view and the local rollback segment can’t be registered for future use. Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment. // |
| ORA-12040 ORA-12040, 00000, “master rollback segment option not support by master site %s” Cause: An attempt was made to specify master rollback segment in the current operation. The master site of the current materialized view does not allow users to specify a rollback segment to be used for materialized view operations. This feature is only supported by Oracle8 or later master sites. Action: Do not specify a master rollback segment in the current operation or choose a new master site. // |
| ORA-12041 ORA-12041, 00000, “cannot record ROWIDs for index-organized table \”%s\”.\”%s\”" Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view log that records the ROWIDs of an index-organized table could not be created. Action: Do not include the WITH ROWID option when using the CREATE MATERIALIZED VIEW command and do not include the ADD ROWID option when using the ALTER MATERIALIZED VIEW command if the master table is index-organized. // |
| ORA-12042 ORA-12042, 00000, “cannot alter job_queue_processes in single process mode” Cause: An attempt was made to alter job_queue_processes in single process mode. Action: Do not attempt to set job_queue_processes in single process mode. // |
| ORA-12043 ORA-12043, 00000, “invalid CREATE MATERIALIZED VIEW option” Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement. Action: Specify only valid options. // |
| ORA-12044 ORA-12044, 00000, “invalid CREATE MATERIALIZED VIEW LOG option” Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement. Action: Specify only valid options. // |
| ORA-12045 ORA-12045, 00000, “invalid ALTER MATERIALIZED VIEW LOG option” Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement. Action: Specify only valid options. // |
| ORA-12046 ORA-12046, 00000, “cannot use trusted constraints for refreshing remote MV” Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER MATERIALIZED VIEW or CREATE MATERIALIZED VIEW of a remote materialized view Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL |
| ORA-12047 ORA-12047, 00000, “PCT FAST REFRESH cannot be used for materialized view \”%s\”.\”%s\”" Cause: PCT refresh is either not enabled on this materialized view or not possible after set of the base table changes since last refresh. Action: Use just REFRESH FORCE, which will reinstantiate the entire table and try to pick the best refresh method on the materialized view Do explain_mview to look at the cause why PCT refresh is not possible on this materialized view |
| ORA-12048 ORA-12048, 00000, “error encountered while refreshing materialized view \”%s\”.\”%s\”" Cause: Some problem occurs during refresh of multiple materialized views in atomic mode. The materialized view whose refresh failed has raised this error. Action: Examine the other messages on the stack to find the refresh problem. // |
| ORA-12051 ORA-12051, 00000, “ON COMMIT attribute is incompatible with other options” Cause: ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified. Action: Specify only valid options. // |
| ORA-12052 ORA-12052, 00000, “cannot fast refresh materialized view %s.%s” Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns. Action: Specify the FORCE or COMPLETE option. If this error is got during creation, the materialized view definition may have be changed. Refer to the documentation on materialized views. // |
| ORA-12053 ORA-12053, 00000, “this is not a valid nested materialized view” Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other. Action: Refer to the documentation to see which types of nesting are valid. // |
| ORA-12054 ORA-12054, 00000, “cannot set the ON COMMIT refresh attribute for the materialized view” Cause: The materialized view did not satisfy conditions for refresh at commit time. Action: Specify only valid options. // |
| ORA-12055 ORA-12055, 00000, “materialized view definition contains cyclic dependencies with existing materialized views” Cause: The materialized view query definition introduced a cyclic dependency with existing materialized view. Action: Modify the materialized view query definition. // |
| ORA-12056 ORA-12056, 00000, “invalid REFRESH method” Cause: The NEVER REFRESH option may not be used under the following conditions: * The materialized view is updatable * The materialized view refreshes ON COMMIT * Automatic refresh options are specified Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND. // |
| ORA-12057 ORA-12057, 00000, “materialized view \”%s\”.\”%s\” is INVALID and must complete refresh” Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view. Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh. // |
| ORA-12058 ORA-12058, 00000, “materialized view cannot use prebuilt table” Cause: An attempt was made to use the prebuilt tables. Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED. // |
| ORA-12059 ORA-12059, 00000, “prebuilt table \”%s\”.\”%s\” does not exist” Cause: The specified prebuilt table did not exist. Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists. // |
| ORA-12060 ORA-12060, 00000, “shape of prebuilt table does not match definition query” Cause: The number of columns or the type or the length semantics of a column in the prebuilt table did not match the materialized view definition query. Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the materialized view definition query. // |
| ORA-12061 ORA-12061, 00000, “invalid ALTER MATERIALIZED VIEW option” Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement. Action: Specify only valid options. // |
| ORA-12062 ORA-12062, 00000, “transaction %s received out of sequence from site %s” Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing. Action: Ensure that the transaction queue at the client site is valid and has not been corrupted. // |
| ORA-12063 ORA-12063, 00000, “unable to apply transaction from site %s” Cause: The current transaction from the client site could not be applied to the master site. Action: Ensure that the client site is still valid and that it has not been dropped from the master site. // |
| ORA-12064 ORA-12064, 00000, “invalid refresh sequence number: %s” Cause: The client site was attempting to perform a refresh with an invalid refresh sequence. Action: Perform a complete refresh to synchronize the refresh sequence number. // |
| ORA-12065 ORA-12065, 00000, “unknown refresh group identifier %s” Cause: The specified refresh group did not exist at the master site. Action: Ensure that the client site is still valid and that it has not been dropped from the master site. // |
| ORA-12066 ORA-12066, 00000, “invalid CREATE MATERIALIZED VIEW command” Cause: The Replication API does not support the following options and types of materialized view: o ROWID materialized views o REFRESH ON COMMIT o ON PREBUILT TABLE o BUILD DEFERRED o NEVER REFRESH o ENABLE QUERY REWRITE Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY KEY and/or remove the invalid options. // |
| ORA-12067 ORA-12067, 00000, “empty refresh groups are not allowed” Cause: The refresh group being instantiated did not contain any materialized views. Action: Modify the template to include at least one materialized view. // |
| ORA-12068 ORA-12068, 00000, “updatable mview log for mview \”%s\”.\”%s\” does not exist” Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view. Action: Create the updatable materialized view log. // |
| ORA-12069 ORA-12069, 00000, “invalid object for offline instantiation” Cause: Only materialized views can be offline instantiated. The object being offline instantiated was not a valid materialized view. Action: Remove the object from the template or replace the object with a valid materialized view. // |
| ORA-12070 ORA-12070, 00000, “cannot offline instantiate materialized view \”%s\”.\”%s\”" Cause: Offline instantiation does not support materialized views using the following options: o ON PREBUILT TABLE o BUILD DEFERRED Action: Remove the invalid options. // |
| ORA-12071 ORA-12071, 00000, “definition query of \”%s\”.\”%s\” is invalid for offline instantiation” Cause: Offline instantiation requires materialized view definition queries to observe the following constraints: o The database link that will be used by the materialized view site to connect to the master site must be included with each master table referenced in the query. o All master tables referenced must be located at the local site. References to other sites are not allowed. Action: Modify the materialized view definition query. // |
| ORA-12072 ORA-12072, 00000, “updatable materialized view log data for \”%s\”.\”%s\” cannot be created” Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view. Action: Create an updatable materialized view log. // |
| ORA-12073 ORA-12073, 00000, “request cannot be processed” Cause: An out-of-sequence request was made and it cannot be processed. Action: Try again with a valid request. // |
| ORA-12074 ORA-12074, 00000, “invalid memory address” Cause: An attempt was made to access an invalid memory region. Action: Reconnect and try the command again. // |
| ORA-12075 ORA-12075, 00000, “invalid object or field” Cause: An attempt was made to access an invalid field or object in the Java Virtual Memory. Action: Retry the request. // |
| ORA-12076 ORA-12076, 00000, “invalid threshold value” Cause: The result set threshold or LOB threshold value is not supported. Action: Specify a threshold value below 64K. // |
| ORA-12077 ORA-12077, 00000, “temporary updatable materialized view log does not exist” Cause: Temporary updatable materialized view log was not created or was dropped. Action: Re-create the temporary updatable materialized view log. Warning: This will cause a complete refresh of the materialized view. // |
| ORA-12078 ORA-12078, 00000, “fast refresh of refresh group ID %s failed” Cause: Refresh result set sent through client method REFRESH_REQ_RESULT returned an unknown value. Action: Re-issue the refresh request. // |
| ORA-12080 ORA-12080, 00000, “Buffer cache miss for IOQ batching” Cause: Action: Comment: never set this event // |
| ORA-12081 ORA-12081, 00000, “update operation not allowed on table \”%s\”.\”%s\”" Cause: An attempt was made to update a read-only materialized view. Action: No action required. Only Oracle is allowed to update a read-only materialized view. // |
| ORA-12082 ORA-12082, 00000, “\”%s\”.\”%s\” cannot be index organized” Cause: An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported. Action: Try to create the materialized view without the index organization clause. |
| ORA-12083 ORA-12083, 00000, “must use DROP MATERIALIZED VIEW to drop \”%s\”.\”%s\”" Cause: An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW. Action: Use the DROP MATERIALIZED VIEW command. // |
| ORA-12084 ORA-12084, 00000, “must use ALTER MATERIALIZED VIEW to alter \”%s\”.\”%s\”" Cause: An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW. Action: Use the ALTER MATERIALIZED VIEW command. |
| ORA-12085 ORA-12085, 0000, “materialized view log on \”%s\”.\”%s\” already has object id” Cause: Materialized view log on the indicated table already has object id information. Action: No action required. // |
| ORA-12086 ORA-12086, 00000, “table \”%s\”.\”%s\” is not an object table” Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH OBJECT ID option and the master table is not an object table. Action: Either specify the name of an object table, or remove the WITH OBJECT ID clause. // |
| ORA-12087 ORA-12087, 00000, “online redefinition not allowed on tables owned by \”%s\”" Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM. Action: Do not attempt to online redefine a table owned by SYS or SYSTEM. // |
| ORA-12088 ORA-12088, 00000, “cannot online redefine table \”%s\”.\”%s\” with unsupported datatype” Cause: An attempt was made to online redefine a table containing a LONG column, an ADT column, or a FILE column. Action: Do not attempt to online redefine a table containing a LONG column, an ADT column, or a FILE column. // |
| ORA-12089 ORA-12089, 00000, “cannot online redefine table \”%s\”.\”%s\” with no primary key” Cause: An attempt was made to online redefine a table that does not have a primary key defined on it. Action: Do not attempt to online redefine a table that does not have a primary key defined on it. |
| ORA-12090 ORA-12090, 00000, “cannot online redefine table \”%s\”.\”%s\”" Cause: An attempt was made to online redefine a table that is either a temporary table, an IOT overflow table, a table with fine-grained access control or row-level security enabled, a CDC change table, or a table with a CDC change table defined on it. Action: Do not attempt to online redefine a table that is not supported by online redefinition. |
| ORA-12091 ORA-12091, 00000, “cannot online redefine table \”%s\”.\”%s\” with materialized views” Cause: An attempt was made to online redefine a table that had materialized views defined on it or had a materialized view log defined on it or is a master. Action: Drop all materialized views and materialized view logs before attempting to online redefine the table. // |
| ORA-12092 ORA-12092, 00000, “cannot online redefine replicated table \”%s\”.\”%s\”" Cause: An attempt was made to online redefine a table that is either a materialized view or a replicated table. Action: Do not attempt to online redefine a table that is either a materialized view or a replicated table. // |
| ORA-12093 ORA-12093, 00000, “invalid interim table \”%s\”.\”%s\”" Cause: The table is not the interim table of the corresponding table to be online redefined. Action: Pass in the valid interim table. // |
| ORA-12094 ORA-12094, 00000, “error during online redefinition” Cause: There was an error during the online redefinition process. Action: Abort the online redefinition process. // |
| ORA-12096 ORA-12096, 00000, “error in materialized view log on \”%s\”.\”%s\”" Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than corresponding master column(s). Another possible cause is that there is a problem accessing the underlying materialized view log table. Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it. // |
| ORA-12097 ORA-12097, 00000, “changes in the master tables during refresh, try refresh again” Cause: There are some changes (i.e., conventional DML, direct load, partition maintenance operation) in the master tables during materialized view refresh. Action: Refresh the affected materialized views again. // |
| ORA-12098 ORA-12098, 00000, “cannot comment on the materialized view” Cause: An attempt was made to issue a COMMENT ON TABLE statement on a materialized view. Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead. // |
| ORA-12099 ORA-12099, 00000, “Don’t go into fast table scan (kdst) mode” Cause: Action: set this event only under the supervision of Oracle development // |
| ORA-12100 ORA-12100, 0000, “materialized view log on \”%s\”.\”%s\” already has sequence” Cause: Materialized view log on the indicated table already has sequence information. Action: No action required. // /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// |
| ORA-12150 ORA-12150, 00000, “TNS:unable to send data” Cause: Unable to send data. Connection probably disconnected. Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation. |
| ORA-12151 ORA-12151, 00000, “TNS:received bad packet type from network layer” Cause: Internal error. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12152 ORA-12152, 00000, “TNS:unable to send break message” Cause: Unable to send break message. Connection probably disconnected. Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation. |
| ORA-12153 ORA-12153, 00000, “TNS:not connected” Cause: Not currently connected to a remote host. Action: Reestablish connection. |
| ORA-12154 ORA-12154, 00000, “TNS:could not resolve the connect identifier specified” Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: – If you are using local naming (TNSNAMES.ORA file): – Make sure that “TNSNAMES” is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) – Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. – Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. – Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. – If you are using directory naming: – Verify that “LDAP” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). – Verify that the LDAP directory server is up and that it is accessible. – Verify that the net service name or database name used as the connect identifier is configured in the directory. – Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier – If you are using easy connect naming: – Verify that “EZCONNECT” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). – Make sure the host, port and service name specified are correct. – Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle |
| ORA-12155 ORA-12155, 00000, “TNS:received bad datatype in NSWMARKER packet” Cause: Internal error during break handling. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12156 ORA-12156, 00000, “TNS:tried to reset line from incorrect state” Cause: Internal error during break handling. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12157 ORA-12157, 00000, “TNS:internal network communication error” Cause: Internal error during network communication. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12158 ORA-12158, 00000, “TNS:could not initialize parameter subsystem” Cause: Unable to locate parameter file. Action: Verify that a valid parameter file exists, and is readable. |
| ORA-12159 ORA-12159, 00000, “TNS:trace file not writeable” Cause: The trace file to be generated is not writeable by this user. Action: If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to. |
| ORA-12160 ORA-12160, 00000, “TNS:internal error: Bad error number” Cause: Corrupt error reporting subsystem. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12161 ORA-12161, 00000, “TNS:internal error: partial data received” Cause: The connection may be terminated. Action: Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12162 ORA-12162, 00000, “TNS:net service name is incorrectly specified” Cause: The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified. Action: If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If using directory naming check the information provided through the administration used for directory naming. |
| ORA-12163 ORA-12163, 00000, “TNS:connect descriptor is too long” Cause: The connect descriptor corresponding to the net service name specified as the connect identifier is too long. The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded. Action: Check the net service name’s connect descriptor in the local naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support. |
| ORA-12164 ORA-12164, 00000, “TNS:Sqlnet.fdf file not present” Cause: The sqlnet.fdf file doesn’t exist in $ORACLE_HOME/network/admin. Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file. |
| ORA-12165 ORA-12165, 00000, “TNS:Trying to write trace file into swap space.” Cause: Oracle Trace doesn’t allow writing trace information into your swap space. Action: Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk. |
| ORA-12166 ORA-12166, 00000, “TNS:Client can not connect to HO agent.” Cause: NVstring contained DESCRIPTION/HO. Action: Call HO agent from integrating server. |
| ORA-12168 ORA-12168, 00000, “TNS:Unable to contact LDAP Directory Server” Cause: Cannot contact LDAP directory server to get Oracle Net configuration. Action: Verify that the directory server is up and accessible from the network. Verify that directory access configuration is correct. For more information see the Oracle Internet Directory Administrators Guide or the Oracle Net Administrators Guide. |
| ORA-12169 ORA-12169, 00000, “TNS:Net service name given as connect identifier is too long” Cause: The net service name you are attempting to resolve is too long. Action: The maximum length of a net service name is 255 bytes; this limit has been exceeded. Use a smaller net service name. If this is not possible, contact Worldwide Customer Support. |
| ORA-12170 ORA-12170, 00000, “TNS:Connect timeout occurred” Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server. Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP). |
| ORA-12171 ORA-12171, 00000, “TNS:could not resolve connect identifier: %s” Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: – If you are using local naming (TNSNAMES.ORA file): – Make sure that “TNSNAMES” is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) – Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. – Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. – Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. – If you are using directory naming: – Verify that “LDAP” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). – Verify that the LDAP directory server is up and that it is accessible. – Verify that the net service name or database name used as the connect identifier is configured in the directory. – Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier – If you are using easy connect naming: – Verify that “EZCONNECT” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). – Make sure the host, port and service name specified are correct. – Try enclosing the connect identifier in quote marks. // See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming. |
| ORA-12196 ORA-12196, 00000, “TNS:received an error from TNS” Cause: The navigation layer received an error from TNS. Action: See the error log file for the specific TNS error. |
| ORA-12197 ORA-12197, 00000, “TNS:keyword-value resolution error” Cause: The navigation layer received an error while trying to look up a value for a keyword. Action: Check the syntax of the connect descriptor. |
| ORA-12198 ORA-12198, 00000, “TNS:could not find path to destination” Cause: Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down. Action: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used. |
| ORA-12200 ORA-12200, 00000, “TNS:could not allocate memory” Cause: Out of memory on machine. Action: Reconfigure machine to have more storage or run fewer applications while the Interchange is running. |
| ORA-12201 ORA-12201, 00000, “TNS:encountered too small a connection buffer” Cause: TNS connection buffer supplied by the application was too small to retrieve the data sent back. Action: Supply a larger connection buffer. If problem persists, call Worldwide Customer Support. |
| ORA-12202 ORA-12202, 00000, “TNS:internal navigation error” Cause: Internal navigation error. Action: Not normally visible to the user. For further details contact Worldwide Customer Support. |
| ORA-12203 ORA-12203, 00000, “TNS:unable to connect to destination” Cause: Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems. Action: Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node. |
| ORA-12204 ORA-12204, 00000, “TNS:received data refused from an application” Cause: The application using Connection Manager refused the connection at the listener. Action: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support. |
| ORA-12205 ORA-12205, 00000, “TNS:could not get failed addresses” Cause: Internal navigation error. Action: Not normally visible to the user. For further details contact Worldwide Customer Support. |
| ORA-12206 ORA-12206, 00000, “TNS:received a TNS error during navigation” Cause: Internal navigation error because of an unexpected TNS error. Action: Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation. |
| ORA-12207 ORA-12207, 00000, “TNS:unable to perform navigation” Cause: Improperly configured navigation file TNSNAV.ORA. Action: Check the syntax of the TNSNAV.ORA file on the application`s machine, and verify that it lists the correct communities. |
| ORA-12208 ORA-12208, 00000, “TNS:could not find the TNSNAV.ORA file” Cause: Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA file is not present. Action: Ensure that the ORACLE environment is set up appropriately on your platform and that a TNSNAV.ORA file is present. |
| ORA-12209 ORA-12209, 00000, “TNS:encountered uninitialized global” Cause: Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| ORA-12210 ORA-12210, 00000, “TNS:error in finding Navigator data” Cause: Application calling navigation routine has not properly configured the TNSNAV.ORA file. Action: Check the syntax of the TNSNAV.ORA file. |
| ORA-12211 ORA-12211, 00000, “TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA” Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. |
| ORA-12212 ORA-12212, 00000, “TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA” Cause: The PREFERRED_CMANAGERS binding in the client’s TNSNAV.ORA file does not have a CMANAGER_NAME specified. Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error. |
| ORA-12213 ORA-12213, 00000, “TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA” Cause: The PREFERRED_CMANAGERS binding in the client’s TNSNAV.ORA file does not have an ADDRESS specified. Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. |
| ORA-12214 ORA-12214, 00000, “TNS:missing local communities entry in TNSNAV.ORA” Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file. |
| ORA-12215 ORA-12215, 00000, “TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA” Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry. Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA // |
| ORA-12216 ORA-12216, 00000, “TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA” Cause: Address binding for the PREFERRED_CMANAGERS entry in the client’s TNSNAV.ORA file is improperly entered. Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. |
| ORA-12217 ORA-12217, 00000, “TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA” Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable. Action: Check the PREFERRED_CMANAGERS entries in the client’s TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command. |
| ORA-12218 ORA-12218, 00000, “TNS:unacceptable network configuration data” Cause: Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client’s TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary. |
| ORA-12219 ORA-12219, 00000, “TNS:missing community name from address in ADDRESS_LIST” Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component. Action: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not. |
| ORA-12221 ORA-12221, 00000, “TNS:illegal ADDRESS parameters” Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA or in the directory. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation or the Oracle Net Administrator’s Guide. Protocols that resolve names at the transport layer are vulnerable to this error if not properly configured or names are misspelled. |
| ORA-12222 ORA-12222, 00000, “TNS:no support is available for the protocol indicated” Cause: The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed. Action: Install support for the protocol or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the net service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the directory server. |
| ORA-12223 ORA-12223, 00000, “TNS:internal limit restriction exceeded” Cause: Too many TNS connections open simultaneously. Action: Wait for connections to close and re-try. |
| ORA-12224 ORA-12224, 00000, “TNS:no listener” Cause: The connection request could not be completed because the listener is not running. Action: Ensure that the supplied destination address matches one of the addresses used by the listener – compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. |
| ORA-12225 ORA-12225, 00000, “TNS:destination host unreachable” Cause: Contact can not be made with remote party. Action: Make sure the network driver is functioning and the network is up. |
| ORA-12226 ORA-12226, 00000, “TNS:operating system resource quota exceeded” Cause: The current user has exceeded the allotted resource assigned in the operating system. Action: Acquire more operating system resource, or perform a different function. |
| ORA-12227 ORA-12227, 00000, “TNS:syntax error” Cause: The supplied connect descriptor contains illegal syntax. Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. |
| ORA-12228 ORA-12228, 00000, “TNS:protocol adapter not loadable” Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. |
| ORA-12229 ORA-12229, 00000, “TNS:Interchange has no more free connections” Cause: One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call. Action: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange. |
| ORA-12230 ORA-12230, 00000, “TNS:Severe Network error occurred in making this connection” Cause: This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination. Action: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem. |
| ORA-12231 ORA-12231, 00000, “TNS:No connection possible to destination” Cause: This error is reported by an interchange which fails to find a possible connection along the path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. |
| ORA-12232 ORA-12232, 00000, “TNS:No path available to destination” Cause: This error is reported by an interchange which fails to find a possible path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. |
| ORA-12233 ORA-12233, 00000, “TNS:Failure to accept a connection” Cause: This error is reported by an interchange which fails to accept a connection due to a redirect failure. Action: Report the problem to your Network Administrator so that he may isolate the interchange problem. |
| ORA-12234 ORA-12234, 00000, “TNS:Redirect to destination” Cause: This error is reported by an interchange which determines that this interchange is not the right gateway and needs to redirect the connection to another gateway along the path to the destination. Action: None. |
| ORA-12235 ORA-12235, 00000, “TNS:Failure to redirect to destination” Cause: This error is reported by an interchange which fails to redirect a connection to another interchange along the path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. |
| ORA-12236 ORA-12236, 00000, “TNS:protocol support not loaded” Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. |
| ORA-12315 ORA-12315, 00000, “database link type is invalid for the ALTER DATABASE statement” Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a // secondary database. Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to // the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to Security Features for more information about creating database links using // the ROM: link type. |
| ORA-12316 ORA-12316, 00000, “syntax error in database link’s connect string” Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error. Action: Drop the database link and recreate it using valid syntax. See // the SQL Language Reference Manual for more information about the // connect string portion of the CREATE DATABASE LINK statement. |
| ORA-12317 ORA-12317, 00000, “logon to database (link name %s) denied” Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the // secondary database are not identical // to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, // you can get this error if the username/password combination // specified in the connect string of the database link definition // is invalid (either not created or has an invalid password). Action: In the first case, ensure that the secondary database contains // a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system // authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS // Guide to Security Features for more information about the advantages of OS authentication). // In the second case, ensure that your username in the secondary database has been created. // In the third case, ensure that the username specified in the // connect string has been created in the secondary database. |
| ORA-12318 ORA-12318, 00000, “database (link name %s) is already mounted” Cause: You are attempting to mount a secondary database that has already // been mounted by your instance. Action: The database is already mounted, so you need not take additional // action to mount it. To establish access, use the // ALTER DATABASE <linkname> OPEN command to open the database. |
| ORA-12319 ORA-12319, 00000, “database (link name %s) is already open” Cause: You are attempting to open a secondary database that is already // open. Action: The database is open and you need not take additional action to establish access. |
| ORA-12321 ORA-12321, 00000, “database (link name %s) is not open and AUTO_MOUNTING=FALSE” Cause: The secondary database that your instance is attempting to mount // is not open and automatic mounting has not been enabled. Action: Manually mount and open the secondary database using // ALTER DATABASE <linkname> with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and // open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE. |
| ORA-12322 ORA-12322, 00000, “unable to mount database (link name %s)” Cause: This message should be accompanied by additional error messages // that indicate the cause of the problem. Action: Follow the steps outlined in the accompanying error messages to // resolve the problem. |
| ORA-12323 ORA-12323, 00000, “unable to open database (link name %s)” Cause: This message should be accompanied by additional error messages // that indicate the cause of the problem. Action: Follow the steps outlined in the accompanying error messages to // resolve the problem. |
| ORA-12324 ORA-12324, 00000, “cannot use the ROM: link type on a private database link” Cause: You can only specify the ROM: link type on a public, not a // private, database link. Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK // command. |
| ORA-12326 ORA-12326, 00000, “database %s is closing immediately; no operations are permitted” Cause: The database you attempted to access is closing, so your // operation has been terminated. Action: Wait until the database has been reopened, or contact the // database adminstrator. |
| ORA-12329 ORA-12329, 00000, “database %s is closed; no operations are permitted” Cause: The database you attempted to access is closed, so your // operation has been terminated. Action: Wait until the database is reopened, or contact the database // administrator. |
| ORA-12333 ORA-12333, 00000, “database (link name %s) is not mounted” Cause: You attempted to open a database that has not been mounted. Action: Mount the database with the ALTER DATABASE <linkname> MOUNT // command, then re-attempt to open the database. |
| ORA-12334 ORA-12334, 00000, “database (link name %s) is still open” Cause: You attempted to dismount a database that is still open. Action: Close the database with the ALTER DATABASE <linkname> CLOSE // command, then re-attempt to dismount the database. |
| ORA-12335 ORA-12335, 00000, “database (link name %s) is not open” Cause: You attempted to close a database that is not open. Action: The database is closed; you can proceed with dismounting it. |
| ORA-12336 ORA-12336, 00000, “cannot login to database (link name %s) ” Cause: You are tyring to login while another user is mounting or dismounting the same database. Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible. |
| ORA-12341 ORA-12341, 00000, “maximum number of open mounts exceeded” Cause: The number specified on the OPEN_MOUNTS parameter in the parameter // file exceeds the maximum allowed (255). Action: Change the value of this parameter so that it reflects the actual // number of possible open mounts to secondary databases. This must // be less than 255. |
| ORA-12342 ORA-12342, 00000, “open mounts exceeds limit set on the OPEN_MOUNTS parameter” Cause: The number of currently open mounts exceeds the value you // specified on the OPEN_MOUNTS parameter. Action: Increase the value of the OPEN_MOUNTS parameter so that it // accommodates the maximum possible number of open mounts to // secondary databases. |
| ORA-12345 ORA-12345, 00000, “user %s lacks CREATE SESSION privilege in database link (linkname %s)” Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege. Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database. |
| ORA-12350 ORA-12350, 00000, “database link being dropped is still mounted” Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened. Action: Close and dismount the database and then re-issue the drop statement. |
| ORA-12351 ORA-12351, 00000, “cannot create view using a remote object which has a remote object reference” Cause: You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database. Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database. |
| ORA-12352 ORA-12352, 00000, “object %s.%s@%s is invalid” Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database. Action: Manually recompile the invalid object in the secondary database. |
| ORA-12353 ORA-12353, 00000, “secondary stored object cannot reference remote object” Cause: You tried to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done. Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database. |
| ORA-12354 ORA-12354, 00000, “secondary object being dropped” Cause: You tried to access a object (for example, a table or view) on a secondary database that was in the process of being dropped. Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle WorldWide Technical Support. |
| ORA-12400 ORA-12400, 00000, “invalid argument to facility error handling” Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility. Action: Specify a valid facility error handling parameter value. |
| ORA-12401 ORA-12401, 00000, “invalid label string: %s” Cause: The policy could not convert the label string to a valid internal label. Action: Correct the syntax of the label string. |
| ORA-12402 ORA-12402, 00000, “invalid format string: %s” Cause: The format string is not supported by the policy. Action: Correct the syntax of the format string. |
| ORA-12403 ORA-12403, 00000, “invalid internal label” Cause: An internal label could not be converted to a valid label for the policy. Action: Analyze any additional messages on the error stack and consult the policy documentation. |
| ORA-12404 ORA-12404, 00000, “invalid privilege string: %s” Cause: The policy could not interpret the privilege string. Action: Specify a privilege string that is supported by the policy. |
| ORA-12405 ORA-12405, 00000, “invalid label list” Cause: The policy determined that the label list was invalid for its intended use. Action: Check the policy constraints on the specific list of labels. |
| ORA-12406 ORA-12406, 00000, “unauthorized SQL statement for policy %s” Cause: The policy did not authorize the database session to perform the requested SQL statement. Action: Grant the user or program unit the necessary policy privilege or additional authorizations. |
| ORA-12407 ORA-12407, 00000, “unauthorized operation for policy %s” Cause: The policy did not authorize the database session to perform the requested operation. Action: Grant the user or program unit the necessary policy privilege or additional authorizations. |
| ORA-12408 ORA-12408, 00000, “unsupported operation: %s” Cause: The specified policy does not support the requested operation. Action: Consult the policy documentation to determine the supported access mediation operations. |
| ORA-12409 ORA-12409, 00000, “policy startup failure for %s policy” Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited. Action: Check the alert log for additional information, correct the policy error, and restart the instance. |
| ORA-12410 ORA-12410, 00000, “internal policy error for policy: %s\n Error: %s” Cause: The policy enforcement encountered an internal error. Action: Consult the policy documentation for details. |
| ORA-12411 ORA-12411, 00000, “invalid label value” Cause: The specified label value does not exist. Action: Check the data dictionary views for the policy to identify valid labels. |
| ORA-12412 ORA-12412, 00000, “policy package %s is not installed” Cause: The policy package does not exist in the database. Action: Check that the policy package name is correct or install the required policy package. |
| ORA-12413 ORA-12413, 00000, “labels do not belong to the same policy” Cause: The labels being compared belong to different policies. Action: Only compare labels that belong to the same policy. |
| ORA-12414 ORA-12414, 00000, “internal LBAC error: %s\n Error: %s” Cause: An internal label policy framework error occurred. Action: Contact Oracle Customer Support. |
| ORA-12415 ORA-12415, 00000, “A column of another datatype exists on the specified table” Cause: The datatype of the column present in the table is different from the datatype set for the policy column. Action: Drop the column on the table or change the datatype for policy column. |
| ORA-12416 ORA-12416, 00000, “policy %s not found” Cause: The specified policy does not exist in the database. Action: Enter the correct policy name or create the policy. |
| ORA-12417 ORA-12417, 00000, “database object \”%s\” not found” Cause: The specified object was not in the database. Action: Enter the correct name for the database object. |
| ORA-12418 ORA-12418, 00000, “user %s not found” Cause: The specified user does not exist in the database. Action: Correct the user name or create the user. |
| ORA-12419 ORA-12419, 00000, “null binary label value” Cause: A null value was provided for a binary label operation. Action: Provide a valid binary label for the operation. |
| ORA-12420 ORA-12420, 00000, “required procedures and functions not in policy package \”%s\”" Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy. Action: Consult the label framework documentation for a list of required procedures and functions for a policy package. |
| ORA-12421 ORA-12421, 00000, “different size binary labels” Cause: The label sizes for the binary label operation were not equal. Action: Provide binary labels with the same lengths for the operation. |
| ORA-12422 ORA-12422, 00000, “max policies exceeded” Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created. Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server. |
| ORA-12423 ORA-12423, 00000, “invalid position specified” Cause: The position specified for a binary label operation was invalid. Action: Provide a position that is within the label size limits. |
| ORA-12424 ORA-12424, 00000, “length exceeds binary label size” Cause: The length specified for a binary label operation exceeded the the size of the binary label. Action: Provide a bit or byte length that is within the label size limits. |
| ORA-12425 ORA-12425, 00000, “cannot apply policies or set authorizations for system schemas” Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or to set user labels/privileges for the SYS, SYSTEM, or LBACSYS user. Action: Apply policies and set authorizations only for non-system users. |
| ORA-12426 ORA-12426, 00000, “invalid audit option” Cause: The option specified was not a valid audit option for the specified policy. Action: Enter a correct audit option. |
| ORA-12427 ORA-12427, 00000, “invalid input value for %s parameter” Cause: An input parameter was specified incorrectly. Action: Correct the parameter value. |
| ORA-12428 ORA-12428, 00000, “” Cause: Action: |
| ORA-12429 ORA-12429, 00000, “label list range exceeded” Cause: The specified index value was not between 1 and 6. Action: Correct the index value for the label list operation. |
| ORA-12430 ORA-12430, 00000, “invalid privilege number” Cause: The specified privilege number was not between 1 and 32. Action: Correct the privilege number. |
| ORA-12431 ORA-12431, 00000, “invalid audit action” Cause: The specified audit action was not a valid audit action. Action: Correct the audit action number. |
| ORA-12432 ORA-12432, 00000, “LBAC error: %s” Cause: LBAC enforcement resulted in an error. Action: Correct the problem identified in the error message. |
| ORA-12433 ORA-12433, 00000, “create trigger failed, policy not applied” Cause: The policy could not be applied due to errors during the creation of a DML trigger. Action: Correct the SQL syntax of the label function specification. |
| ORA-12434 ORA-12434, 00000, “invalid audit type: %s” Cause: The audit type must be BY ACCESS or BY SESSION. Action: Correct the audit type value. |
| ORA-12435 ORA-12435, 00000, “invalid audit success: %s” Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL. Action: Correct the audit success value. |
| ORA-12436 ORA-12436, 00000, “no policy options specified” Cause: A NULL option string was specified, but no default schema or policy option string was found. Action: Enter a valid option string, or alter the schema or policy to have a valid default option string. |
| ORA-12437 ORA-12437, 00000, “invalid policy option: %s” Cause: A value that was not a valid policy option was entered. Action: Correct the policy option value. |
| ORA-12438 ORA-12438, 00000, “repeated policy option: %s” Cause: A policy option was entered more than once in the option string. Action: Remove the duplicate policy option value. |
| ORA-12439 ORA-12439, 00000, “invalid combination of policy options” Cause: A set of contradictory policy options was entered. Action: Provide a set of compatible policy options. |
| ORA-12440 ORA-12440, 00000, “insufficient authorization for the SYSDBA package” Cause: The use of the SYSDBA package requires the LBAC_DBA role. Action: Grant the LBAC_DBA role to the database user. |
| ORA-12441 ORA-12441, 00000, “policy %s already exists” Cause: You tried to create a policy with the same name as an existing one. Action: Use a different name or drop the existing policy. |
| ORA-12442 ORA-12442, 00000, “policy column \”%s\” already used by an existing policy” Cause: You tried to create a policy with the same policy column name as an existing policy. Action: Use a different name for the policy column or drop the existing policy. |
| ORA-12443 ORA-12443, 00000, “policy not applied to some tables in schema” Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied. Action: No action necessary; the policy was applied to the remaining tables. |
| ORA-12444 ORA-12444, 00000, “policy already applied to table” Cause: You tried to apply a policy to a table that was already protected by the policy. Action: To change the policy options, predicate, or label function, remove the policy from the table and re-apply it. |
| ORA-12445 ORA-12445, 00000, “cannot change HIDDEN property of column” Cause: You tried to specify a different HIDE option for a table with an existing policy column. Action: Drop the column from the table and reapply the policy with the new HIDE option. |
| ORA-12446 ORA-12446, 00000, “Insufficient authorization for administration of policy %s” Cause: You tried to perform an administrative function for a policy, but you have not been granted the <policy>_DBA role. Action: Grant the user the <policy>_DBA role for the specified policy. |
| ORA-12447 ORA-12447, 00000, “policy role already exists for policy %s” Cause: The role named <policy>_DBA already exists. Action: Correct the policy name or delete the existing policy. |
| ORA-12448 ORA-12448, 00000, “policy %s not applied to schema %s” Cause: You tried to alter a schema policy that was not applied. Action: Correct the policy name or schema name. |
| ORA-12449 ORA-12449, 00000, “Labels specified for user must be of type USER” Cause: You tried to set labels for a user, but the labels in the list were not all designated as USER labels. Action: Alter the labels to be USER labels. |
| ORA-12450 ORA-12450, 00000, “LOB datatype disabled in LBAC initialization file” Cause: You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled. Action: Change the LBAC initialization file to allow the creation of LOB columns and attributes. |
| ORA-12451 ORA-12451, 00000, “label not designated as USER or DATA” Cause: A label is either a DATA label, a USER label, or both DATA and USER. Action: Enter TRUE for at least DATA or USER. |
| ORA-12452 ORA-12452, 00000, “label tag %s already exists” Cause: The label tag value you entered is already in use for another label. Action: Enter a different value for the label tag. |
| ORA-12453 ORA-12453, 00000, “label %s already exists” Cause: The label value you entered already exists. Action: No action necessary; alter the label to change its tag or type. |
| ORA-12454 ORA-12454, 00000, “label %s does not exist for policy %s” Cause: The label tag or value you entered did not identify a label for the policy. Action: Enter a label value or tag that is in use by the policy. |
| ORA-12455 ORA-12455, 00000, “internal error in Label Security MMON cleanup task” Cause: An internal error occurred in the Label Security MMON cleanup task. Action: Contact Oracle Customer Support. |
| ORA-12456 ORA-12456, 00000, “label security startup in progress” Cause: You attempted to connect to the database before the Oracle Label Security component was fully initialized. Action: Wait until the database is fully open before attempting to connect. |
| ORA-12457 ORA-12457, 00000, “security label exceeded maximum allowable length” Cause: An operation attempted to materialize a security label greater than 4000 bytes in length. Action: Consult the Oracle Label Security documentation for information on how the length of a security label is calculated. Re-submit the operation once the problem has been corrected. |
| ORA-12461 ORA-12461, 00000, “undefined level %s for policy %s” Cause: The specified level is not defined for the policy. Action: Correct the level identifier value. |
| ORA-12462 ORA-12462, 00000, “undefined compartment %s for policy %s” Cause: The specified compartment is not defined for the policy. Action: Correct the compartment identifier value. |
| ORA-12463 ORA-12463, 00000, “undefined group %s for policy %s” Cause: The specified group is not defined for the policy. Action: Correct the group identifier value. |
| ORA-12464 ORA-12464, 00000, “invalid characters in label component %s” Cause: Label components can contain only alphanumeric characters, blanks, and underscores. Action: Correct syntax of the label component. |
| ORA-12465 ORA-12465, 00000, “Not authorized for read or write on specified groups or compartments” Cause: You included groups or compartments that are not in the user’s list of groups and compartments authorized for read or write access. Action: Include read access when authorizing groups or compartments for write access. |
| ORA-12466 ORA-12466, 00000, “default level is greater than the user’s maximum” Cause: The default level cannot be greater than the user’s maximum. Action: Enter an authorized level. |
| ORA-12467 ORA-12467, 00000, “minimum label can contain a level only” Cause: You included compartments or groups in the minimum label. Action: Enter only an authorized minimum level as the label. |
| ORA-12468 ORA-12468, 00000, “max write level does not equal max read level” Cause: The level in the max write label must equal the level in the max read label. Action: Enter max read and max write labels with the same level component. |
| ORA-12469 ORA-12469, 00000, “no user levels found for user %s and policy %s” Cause: No levels have been specified for the user. Action: Enter the maximum and minimum labels for the user. |
| ORA-12470 ORA-12470, 00000, “NULL or invalid user label: %s” Cause: The label entered is NULL or not within the user’s authorizations. Action: Enter the authorized labels for the user. |
| ORA-12471 ORA-12471, 00000, “Specified compartment or group is not authorized for user” Cause: The specified compartment or group is not in user’s authorizations or the user does not have read on compartment or group specified for write. Action: Enter an authorized compartment or group. |
| ORA-12472 ORA-12472, 00000, “policy %s is being used” Cause: The policy which was being dropped due to event propagation from OID was applied to some table or schema. Action: Drop a policy in OID only if it is not used in any of the databases using the policy. |
| ORA-12473 ORA-12473, 00000, “The procedure is disabled when Label Security is used with OID.” Cause: Using Label Security with OID disabled this procedure. Action: Do not use OID with Label Security if this procedure is required to function. |
| ORA-12476 ORA-12476, 00000, “least upper bound resulted in an invalid OS label” Cause: You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system. Action: Consult your OS label management documentation for information on invalid label generation. |
| ORA-12477 ORA-12477, 00000, “greatest lower bound resulted in an invalid OS label” Cause: You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system. Action: Consult your OS label management documentation for information on invalid label generation. |
| ORA-12479 ORA-12479, 00000, “file label %s must equal DBHIGH %s” Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled. Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file. |
| ORA-12480 ORA-12480, 00000, “specified clearance labels not within the effective clearance” Cause: You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance. Action: Specify clearance labels that are within your own clearance range. |
| ORA-12481 ORA-12481, 00000, “effective label not within program unit clearance range” Cause: The effective label when the program unit was invoked was not within the range authorized for the program unit. Action: Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance. |
| ORA-12482 ORA-12482, 00000, “internal MLS error: %s\n Error: %s” Cause: An internal MLS policy error occurred. Action: Contact Oracle Customer Support. |
| ORA-12483 ORA-12483, 00000, “label not in OS system accreditation range” Cause: The specified label is above the OS maximum label or below the OS minimum label. Action: Use a label that is within the accreditation range for the host OS. |
| ORA-12484 ORA-12484, 00000, “invalid OS label” Cause: The specified label does not exist in the OS host’s label definition file. Action: Use the OS label management tools to define the label. |
| ORA-12485 ORA-12485, 00000, “new effective label not within effective clearance” Cause: You attempted to enter a value for an effective label that did not dominate the effective min label or was not dominated by the effective max label. Action: Enter a value between the min and the max labels. |
| ORA-12486 ORA-12486, 00000, “effective max labels and min labels cannot be changed” Cause: You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed. Action: Enter NULL values for the effective minimum and maximum labels. |
| ORA-12487 ORA-12487, 00000, “clearance labels not between DBHIGH and DBLOW” Cause: You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW. Action: Enter clearance label values between DBHIGH and DBLOW. |
| ORA-12488 ORA-12488, 00000, “maximum label does not dominate minimum label” Cause: You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels. Action: Enter label values that preserves the dominance relationship between the minimum and maximum. |
| ORA-12489 ORA-12489, 00000, “default label not within clearance range” Cause: You attempted to enter a value for a default label that did not dominate the minimum clearance or was not dominated by the maximum clearance. Action: Enter a default label value within the clearance range. |
| ORA-12490 ORA-12490, 00000, “DBHIGH cannot be lowered” Cause: You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH. Action: Enter a value for DBHIGH that dominates the old value. |
| ORA-12491 ORA-12491, 00000, “DBHIGH value does not dominate DBLOW” Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW. Action: Enter a value for DBHIGH that dominates DBLOW. |
| ORA-12492 ORA-12492, 00000, “DBLOW cannot be changed” Cause: You attempted to change the value of DBLOW after it had been set to any initial value. DBLOW can only be set once after initial database creation. Action: To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database. |
| ORA-12493 ORA-12493, 00000, “invalid MLS binary label” Cause: The MLS binary label contained an invalid value, was not the correct size, or contained a level, category, or release category that was not enabled. Action: Check the DBA_MLS_LABELS view for the valid MLS labels. |
| ORA-12494 ORA-12494, 00000, “cannot insert or delete a level, category, or release category” Cause: You attempted to insert or delete a level, category, or release category definition. Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used. |
| ORA-12495 ORA-12495, 00000, “cannot disable an enabled level, category, or release category” Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may be exist in some database label, so cannot be disabled. Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used. |
| ORA-12496 ORA-12496, 00000, “cannot change existing level, category, or release numbers” Cause: You attempted to change the number assigned to level, category or releasability category. Action: Change the character string representations, not the numbers. |
| ORA-12497 ORA-12497, 00000, “maximum combined categories exceeds %s” Cause: The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded. Action: Enter numbers that do not add up to more than the maximum. |
| ORA-12498 ORA-12498, 00000, “” Cause: Action: |
| ORA-12499 ORA-12499, 00000, “” Document: NO Cause: Action: |
| ORA-12500 ORA-12500, 00000, “TNS:listener failed to start a dedicated server process” Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support. |
| ORA-12502 ORA-12502, 00000, “TNS:listener received no CONNECT_DATA from client” Cause: No CONNECT_DATA was passed to the listener. Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor. |
| ORA-12504 ORA-12504, 00000, “TNS:listener was not given the SERVICE_NAME in CONNECT_DATA” Cause: The listener was not configured with a default service and SERVICE_NAME was missing from the CONNECT_DATA received by the listener. Action: Possible solutions are: – Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid service name. Reload the listener parameter file using reload [<listener_name>]. This should be done by the LISTENER administrator. – If using a service name, Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has a SERVICE_NAME or SID component in the CONNECT_DATA. |
| ORA-12505 ORA-12505, 00000, “TNS:listener does not currently know of SID given in connect descriptor” Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: – Wait a moment and try to connect a second time. – Check which instances are currently known by the listener by executing: lsnrctl services <listener name> – Check that the SID parameter in the connect descriptor specifies an instance known by the listener. – Check for an event in the listener.log file. |
| ORA-12508 ORA-12508, 00000, “TNS:listener could not resolve the COMMAND given” Cause: The COMMAND given to listener is not supported. Action: This is not seen in normal use of Oracle Net. Comment: Check the COMMAND given to listener. This error is probably caused by incompatible Oracle Net or Net8 versions. Do not include in error manual. |
| ORA-12509 ORA-12509, 00000, “TNS:listener failed to redirect client to service handler” Cause: The dispatcher terminated unexpectedly Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect. |
| ORA-12510 ORA-12510, 00000, “TNS:database temporarily lacks resources to handle the request” Cause: The dispatchers appear to be busy handling other requests. Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and/or dispatchers’ limit on number of connections/sessions that they can accept. |
| ORA-12511 ORA-12511, 00000, “TNS:service handler found but it is not accepting connections” Cause: The dispatchers notified the listener that they temporarily do not accept new connections. Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and/or ask him to increase the number of dispatchers. |
| ORA-12513 ORA-12513, 00000, “TNS:service handler found but it has registered for a different protocol” Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client. Action: Contact the DBA to register a dispatcher on your protocol. |
| ORA-12514 ORA-12514, 00000, “TNS:listener does not currently know of service requested in connect descriptor” Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: – Wait a moment and try to connect a second time. – Check which services are currently known by the listener by executing: lsnrctl services <listener name> – Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. – If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. – Check for an event in the listener.log file. |
| ORA-12515 ORA-12515, 00000, “TNS:listener could not find a handler for this presentation” Cause: None of the listener’s known service handlers are registered as supporting the presentation protocol required by the connecting client. Action: Check that the destination service is configured to accept the presentation protocol. |
| ORA-12516 ORA-12516, 00000, “TNS:listener could not find available handler with matching protocol stack” Cause: None of the known and available service handlers for the given SERVICE_NAME support the client’s protocol stack: transport, session, and presentation protocols. Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols. |
| ORA-12518 ORA-12518, 00000, “TNS:listener could not hand off client connection” Cause: The process of handing off a client connection to another process failed. Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support. Comment: The problem can be worked around by configuring dispatcher(s) to specifically handle the desired presentation(s), and connecting directly to the dispatcher, bypassing the listener. |
| ORA-12519 ORA-12519, 00000, “TNS:no appropriate service handler found” Cause: The listener could not find any available service handlers that are appropriate for the client connection. Action: Run “lsnrctl services” to ensure that the instance(s) have registered with the listener, and are accepting connections. |
| ORA-12520 ORA-12520, 00000, “TNS:listener could not find available handler for requested type of server” Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection. Action: Run “lsnrctl services” to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections. |
| ORA-12521 ORA-12521, 00000, “TNS:listener does not currently know of instance requested in connect descriptor” Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: – Wait a moment and try to connect a second time. – Check which instances are currently known by the listener by executing: lsnrctl services <listener name> – Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener. – Check for an event in the listener.log file. |
| ORA-12522 ORA-12522, 00000, “TNS:listener could not find available instance with given INSTANCE_ROLE” Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified). Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run “lsnrctl services” to ensure that the instance(s) have registered with the listener and that they are ready to accept connections. |
| ORA-12523 ORA-12523, 00000, “TNS:listener could not find instance appropriate for the client connection” Cause: The listener could not find any available (database) instances, that are appropriate for the client connection. Action: Run “lsnrctl services” to ensure that the instance(s) are registered with the listener, and have status READY. |
| ORA-12524 ORA-12524, 00000, “TNS:listener could not resolve HANDLER_NAME given in connect descriptor” Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener’s tables for the specified SERVICE_NAME and INSTANCE_NAME. Action: Check to make sure that the HANDLER_NAME specified is correct. Comment: This error will be returned if the database instance and/or its service handlers have not been registered with the listener or they have been registered for different service; the instance may need to be started. |
| ORA-12525 ORA-12525, 00000, “TNS:listener has not received client’s request in time allowed” Cause: The listener disconnected the client because the client failed to provide the necessary connect information within the allowed time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the listener. Action: If the error occurred because of a slow network or system, reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is suspected, use the address in listener.log to identify the source and restrict access. Turn on tracing for more information. Comment: The logged address in listener.ora may not be reliable as it can be forged at the lower networking layers (e.g. in the case of TCP/IP). |
| ORA-12526 ORA-12526, 00000, “TNS:listener: all appropriate instances are in restricted mode” Cause: Database instances supporting the service requested by the client were in restricted mode. The Listener does not allow connections to instances in restricted mode. This condition may be temporary, such as during periods when database administration is performed. Action: Attempt the connection again. If error persists, then contact the database administrator to change the mode of the instance, if appropriate. |
| ORA-12527 ORA-12527, 00000, “TNS:listener: all instances are in restricted mode or blocking new connections” Cause: All appropriate database instances supporting the service requested by the client reported that they either were in restricted mode or were blocking the new connections. The Listener does not allow connections to such instances. This condition may be temporary, such as at instance startup. Action: Attempt the connection again. If error persists, then contact the database administrator to check the status of the instances. |
| ORA-12528 ORA-12528, 00000, “TNS:listener: all appropriate instances are blocking new connections” Cause: All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup. Action: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances. |
| ORA-12529 ORA-12529, 00000, “TNS:connect request rejected based on current filtering rules” Cause: Connection Manager and its listener were configured with filtering rules specifying that the connect request be rejected. Action: If this connect request should be allowed, then contact the administrator to modify the filtering rules. |
| ORA-12531 ORA-12531, 00000, “TNS:cannot allocate memory” Cause: Sufficient memory could not be allocated to perform the desired activity. Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation. |
| ORA-12532 ORA-12532, 00000, “TNS:invalid argument” Cause: An internal function received an invalid parameter. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12533 ORA-12533, 00000, “TNS:illegal ADDRESS parameters” Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled. |
| ORA-12534 ORA-12534, 00000, “TNS:operation not supported” Cause: An internal function received a request to perform an operation that is not supported (on this machine). Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12535 ORA-12535, 00000, “TNS:operation timed out” Cause: The requested operation could not be completed within the time out period. Action: Look at the documentation on the secondary errors for possible remedy. See SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to gather more information. |
| ORA-12536 ORA-12536, 00000, “TNS:operation would block” Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking. Action: None needed; this is an information message. |
| ORA-12537 ORA-12537, 00000, “TNS:connection closed” Cause: “End of file” condition has been reached; partner has disconnected. Action: None needed; this is an information message. |
| ORA-12538 ORA-12538, 00000, “TNS:no such protocol adapter” Cause: The protocol adapter requested (by way of the “(PROTOCOL=..)” keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed. Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA). |
| ORA-12539 ORA-12539, 00000, “TNS:buffer over- or under-flow” Cause: Buffer too small for incoming data or too large for outgoing data. Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Oracle Customer Support. |
| ORA-12540 ORA-12540, 00000, “TNS:internal limit restriction exceeded” Cause: Too many TNS connections open simultaneously. Action: Wait for connections to close and re-try. |
| ORA-12541 ORA-12541, 00000, “TNS:no listener” Cause: The connection request could not be completed because the listener is not running. Action: Ensure that the supplied destination address matches one of the addresses used by the listener – compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. |
| ORA-12542 ORA-12542, 00000, “TNS:address already in use” Cause: Specified listener address is already being used. Action: Start your listener with a unique address. |
| ORA-12543 ORA-12543, 00000, “TNS:destination host unreachable” Cause: Contact can not be made with remote party. Action: Make sure the network driver is functioning and the network is up. |
| ORA-12544 ORA-12544, 00000, “TNS:contexts have different wait/test functions” Cause: Two protocol adapters have conflicting wait/test functions. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12545 ORA-12545, 00000, “Connect failed because target host or object does not exist” Cause: The address specified is not valid, or the program being connected to does not exist. Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps “oracle” is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again. |
| ORA-12546 ORA-12546, 00000, “TNS:permission denied” Cause: User has insufficient privileges to perform the requested operation. Action: Acquire necessary privileges and try again. |
| ORA-12547 ORA-12547, 00000, “TNS:lost contact” Cause: Partner has unexpectedly gone away, usually during process startup. Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded. |
| ORA-12548 ORA-12548, 00000, “TNS:incomplete read or write” Cause: A data send or receive failed. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12549 ORA-12549, 00000, “TNS:operating system resource quota exceeded” Cause: The current user has exceeded the allotted resource assigned in the operating system. Action: Acquire more operating system resource, or perform a different function. |
| ORA-12550 ORA-12550, 00000, “TNS:syntax error” Cause: The supplied connect descriptor contains illegal syntax. Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. |
| ORA-12551 ORA-12551, 00000, “TNS:missing keyword” Cause: The supplied connect descriptor is missing one or more TNS keywords. Action: Check the syntax, and ensure all required keywords are present. |
| ORA-12552 ORA-12552, 00000, “TNS:operation was interrupted” Cause: An internal operation was interrupted and could not complete. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12554 ORA-12554, 00000, “TNS:current operation is still in progress” Cause: An internal operation is still in progress. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12555 ORA-12555, 00000, “TNS:permission denied” Cause: User has insufficient privileges to perform the requested operation. Action: Acquire necessary privileges and try again. |
| ORA-12556 ORA-12556, 00000, “TNS:no caller” Cause: TNS detected an incoming connect request but there was no caller. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12557 ORA-12557, 00000, “TNS:protocol adapter not loadable” Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. |
| ORA-12558 ORA-12558, 00000, “TNS:protocol adapter not loaded” Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. |
| ORA-12560 ORA-12560, 00000, “TNS:protocol adapter error” Cause: A generic protocol adapter error occurred. Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete. |
| ORA-12561 ORA-12561, 00000, “TNS:unknown error” Cause: A generic protocol error occurred. Action: For further details, turn on tracing and reexecute the operation. |
| ORA-12562 ORA-12562, 00000, “TNS:bad global handle” Cause: Internal error – bad ‘gbh’ argument passed to TNS from caller. System may have been linked with old libraries. Action: Not normally visible to the user, contact Oracle Customer Support. |
| ORA-12564 ORA-12564, 00000, “TNS:connection refused” Cause: The connect request was denied by the remote user (or TNS software). Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. |
| ORA-12566 ORA-12566, 00000, “TNS:protocol error” Cause: An unexpected TNS protocol error has occurred. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12569 ORA-12569, 00000, “TNS:packet checksum failure” Cause: The data received is not the same as the data sent. Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation. |
| ORA-12570 ORA-12570, 00000, “TNS:packet reader failure” Cause: An error occurred during a data receive. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12571 ORA-12571, 00000, “TNS:packet writer failure” Cause: An error occurred during a data send. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12574 ORA-12574, 00000, “TNS:redirection denied” Cause: The connect request failed because it would have required redirection and the caller has requested no redirections. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12575 ORA-12575, 00000, “TNS:dhctx busy” Cause: The handoff over a dhctx failed as dhctx was already busy with an ongoing handoff. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12576 ORA-12576, 00000, “TNS:handoff not supported for this session” Cause: Handoff of a established session was attempted which either had tcps as its transport or NA options were enabled for this session. Action: Check the transport setting as well as NA options. If error persists, contact Oracle Customer Support. |
| ORA-12582 ORA-12582, 00000, “TNS:invalid operation” Cause: An internal function received an invalid request. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12583 ORA-12583, 00000, “TNS:no reader” Cause: A send operation has been requested but partner has already disconnected. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12585 ORA-12585, 00000, “TNS:data truncation” Cause: A receive operation has completed with insufficient data to satisfy the user’s request. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12589 ORA-12589, 00000, “TNS:connection not bequeathable” Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12590 ORA-12590, 00000, “TNS:no I/O buffer” Cause: An attempt to perform an I/O operation failed because no buffer was available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12591 ORA-12591, 00000, “TNS:event signal failure” Cause: The TNS software is unable to signal an event occurrence. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12592 ORA-12592, 00000, “TNS:bad packet” Cause: An ill-formed packet has been detected by the TNS software. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12593 ORA-12593, 00000, “TNS:no registered connection” Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12595 ORA-12595, 00000, “TNS:no confirmation” Cause: TNS is unable to get requested confirmation acknowledgment from remote partner. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12596 ORA-12596, 00000, “TNS:internal inconsistency” Cause: TNS has detected an internal inconsistency. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12597 ORA-12597, 00000, “TNS:connect descriptor already in use” Cause: Internal error – illegal use of connect descriptor. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12598 ORA-12598, 00000, “TNS:banner registration failed” Cause: The registration of a product banner with the Oracle server failed. Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. |
| ORA-12599 ORA-12599, 00000, “TNS:cryptographic checksum mismatch” Cause: The data received is not the same as the data sent. Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection. |
| ORA-12600 ORA-12600, 00000, “TNS: string open failed” Cause: The creation of a string in ORACLE NLS format failed. Action: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. |
| ORA-12601 ORA-12601, 00000, “TNS:information flags check failed” Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished. Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. |
| ORA-12602 ORA-12602, 00000, “TNS: Connection Pooling limit reached” Cause: The operation failed because maximum active current connections has been reached. It may not be a real error when the Connection Pooling feature is enabled. It is possible that the application later reissues the operation and successfully grabs the connection pool slot and proceeds. Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. |
| ORA-12606 ORA-12606, 00000, “TNS: Application timeout occurred” Cause: A network session did not reach an application-defined stage within the allowed time interval. Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description. |
| ORA-12607 ORA-12607, 00000, “TNS: Connect timeout occurred” Cause: A network session did not reach a predefined connect stage within the allowed time interval. Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description. |
| ORA-12608 ORA-12608, 00000, “TNS: Send timeout occurred” Cause: The send or write operation did not complete within the allowed time interval. Action: Check if the peer host is available. Increase the send timeout value if necessary. |
| ORA-12609 ORA-12609, 00000, “TNS: Receive timeout occurred” Cause: The receive or read operation did not complete within the allowed time interval. Action: Check if the peer host is available. Increase the receive timeout value if necessary. |
| ORA-12611 ORA-12611, 00000, “TNS:operation is not portable” Cause: Attempted operation is not portable. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12612 ORA-12612, 00000, “TNS:connection is busy” Cause: Attempted operation failed because it conflicts with an ongoing action or status of the connection. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12615 ORA-12615, 00000, “TNS:preempt error” Cause: A request to service an event failed because no event notification has yet been posted. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12616 ORA-12616, 00000, “TNS:no event signals” Cause: The TNS software is unable to enable event signals. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12618 ORA-12618, 00000, “TNS:versions are incompatible” Cause: The two machines are running incompatible versions of TNS. Action: Check the version numbers, and upgrade the machine with the smaller one. |
| ORA-12619 ORA-12619, 00000, “TNS:unable to grant requested service” Cause: The connect request failed because requested service could not be provided by the local TNS software. Action: If appropriate, reexecute with reduced service requirements. |
| ORA-12620 ORA-12620, 00000, “TNS:requested characteristic not available” Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software. Action: If appropriate, reexecute with reduced requirements. |
| ORA-12622 ORA-12622, 00000, “TNS:event notifications are not homogeneous” Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12623 ORA-12623, 00000, “TNS:operation is illegal in this state” Cause: Connection is half-duplex and a full-duplex operation was attempted. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. |
| ORA-12624 ORA-12624, 00000, “TNS:connection is already registered” Cause: An attempt to register a connection for event notification failed because the connection is already registered. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12625 ORA-12625, 00000, “TNS:missing argument” Cause: An operation failed because an argument was missing” Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12626 ORA-12626, 00000, “TNS:bad event type” Cause: An attempt to register a connection for event notification failed because the event type is unknown. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12628 ORA-12628, 00000, “TNS:no event callbacks” Cause: An attempt to register a connection for event notification failed because asynchronous callbacks are not available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12629 ORA-12629, 00000, “TNS:no event test” Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. |
| ORA-12630 ORA-12630, 00000, “Native service operation not supported” Cause: An operation requested by a user is not supported by the native services component. Action: This may be an internal error if the operation should have been supported. |
| ORA-12631 ORA-12631, 00000, “Username retrieval failed” Cause: The authentication service failed to retrieve the name of a user. Action: Enable tracing to determine which routine is failing. |
| ORA-12632 ORA-12632, 00000, “Role fetch failed” Cause: The authentication service failed to retrieve one of the user’s roles. Action: Enable tracing to determine which routine is failing. |
| ORA-12633 ORA-12633, 00000, “No shared authentication services” Cause: The list of authentication services specified by the user does not match those supported by the process. Action: Either specify another list or relink the executable with the desired services. |
| ORA-12634 ORA-12634, 00000, “Memory allocation failed” Cause: Process was unable to allocate memory. Action: Terminate other processes in order to reclaim needed memory. |
| ORA-12635 ORA-12635, 00000, “No authentication adapters available” Cause: The executable was not linked with any authentication service adapters but the sqlnet.ora parameter that determines whether or not authentication is required was set to true. Action: Either disable the parameter or relink the executable with service adapters. |
| ORA-12636 ORA-12636, 00000, “Packet send failed” Cause: A process was unable to send a packet to another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. Action: If the cause is not obvious, contact Oracle Customer Support. |
| ORA-12637 ORA-12637, 00000, “Packet receive failed” Cause: A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. Action: If the cause is not obvious, contact Oracle Customer Support. |
| ORA-12638 ORA-12638, 00000, “Credential retrieval failed” Cause: The authentication service failed to retrieve the credentials of a user. Action: Enable tracing to determine the exact error. |
| ORA-12639 ORA-12639, 00000, “Authentication service negotiation failed” Cause: No match was found between the types of authentication services that the client supports and those that the server is using. Action: Possible solutions: 1. Change the entry in sqlnet.ora that determines which services are to be used. 2. Relink the client with at least one of the authentication service adapters that the server supports. 3. Relink the server with at least one of the authentication service adapters that the client supports. 4. Disable authentication on both the client and server. |
| ORA-12640 ORA-12640, 00000, “Authentication adapter initialization failed” Cause: The function specified in the authentication table entry for the service failed. Action: Enable tracing to determine the exact error. |
| ORA-12641 ORA-12641, 00000, “Authentication service failed to initialize” Cause: The authentication service failed during initialization. Action: Enable tracing to determine the exact error. |
| ORA-12642 ORA-12642, 00000, “No session key” Cause: A process has no session key associated with it because the authentication service being used does not use one. Action: If a session key is required, use another authentication service. |
| ORA-12643 ORA-12643, 00000, “Client received internal error from server” Cause: The client process received an error from the server that indicated that an internal Oracle Net native services error had occurred. Action: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Oracle Customer Support. |
| ORA-12645 ORA-12645, 00000, “Parameter does not exist.” Cause: A sqlnet.ora parameter from which a value was needed does not exist. Action: Set the parameter in the parameter file. |
| ORA-12646 ORA-12646, 00000, “Invalid value specified for boolean parameter” Cause: The value specified for a parameter was set to a value other than true/false or on/off. Action: Correct the value of the parameter. |
| ORA-12647 ORA-12647, 00000, “Authentication required” Cause: The parameter that controls whether authentication is required was set to true, but the executable does not have an authentication service linked in. Action: Either re-link the executable with an authentication service adapter or disable the parameter. |
| ORA-12648 ORA-12648, 00000, “Encryption or data integrity algorithm list empty” Cause: An Oracle Advanced Security list-of-algorithms parameter was empty, e.g. “()”. Action: Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable. |
| ORA-12649 ORA-12649, 00000, “Unknown encryption or data integrity algorithm” Cause: An Oracle Advanced Security list-of-algorithms parameter included an algorithm name that was not recognized. Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm. |
| ORA-12650 ORA-12650, 00000, “No common encryption or data integrity algorithm” Cause: The client and server have no algorithm in common for either encryption or data integrity or both. Action: Choose sets of algorithms that overlap. In other words, add one of the client’s algorithm choices to the server’s list or vice versa. |
| ORA-12651 ORA-12651, 00000, “Encryption or data integrity algorithm unacceptable” Cause: The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data. Action: For further details, turn on tracing, re-execute the operation, and contact Oracle Customer Support. |
| ORA-12652 ORA-12652, 00000, “String truncated” Cause: Not enough memory was allocated for a string so it had to be truncated Action: If it is OK that the string is truncated, then it is not an error. Otherwise, call the routine that reported the error again with a larger string buffer. |
| ORA-12653 ORA-12653, 00000, “Authentication control function failed” Cause: The control function utilized by the authentication service driver failed. Action: Enable tracing to determine the exact error. |
| ORA-12654 ORA-12654, 00000, “Authentication conversion failed” Cause: The authentication service was unable to convert the credentials of a user from the format specific to the format into the ORACLE format. Action: Enable tracing to determine the exact error. |
| ORA-12655 ORA-12655, 00000, “Password check failed” Cause: The authentication service being used was unable to verify the provided password. Action: Enable tracing to determine the exact error. |
| ORA-12656 ORA-12656, 00000, “Cryptographic checksum mismatch” Cause: The cryptographic checksum received with a packet of incoming data didn’t match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit. Action: Look for sources of data corruption, perhaps including deliberate tampering. |
| ORA-12657 ORA-12657, 00000, “No algorithms installed” Cause: The near side of the connection required the use of a service (either encryption or checksumming) when no algorithms for that service were installed. Action: Remove the “ON” requirement for that service. |
| ORA-12658 ORA-12658, 00000, “ANO service required but TNS version is incompatible” Cause: A client process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that an ANO service (authentication, encryption, etc.) be used. Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side. |
| ORA-12659 ORA-12659, 00000, “Error received from other process” Cause: An error was received by one or more services from the process on the other side of the connection. Action: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa. |
| ORA-12660 ORA-12660, 00000, “Encryption or crypto-checksumming parameters incompatible” Cause: One side of the connection specified “REQUIRED” for encryption // or crypto-checksumming, while the other side specified “REJECTED”. Action: Change the “REQUIRED” side to “REQUESTED” if the // you want encryption or crypto-checksumming to be optional, or // change the “REJECTED” side to “ACCEPTED” if you do not // want the service to be optional. |
| ORA-12661 ORA-12661, 00000, “Protocol authentication to be used” Cause: The Oracle Advanced Security authentication service has determined that the Oracle Net transport protocol in use is to be utilized to authenticate a user’s identity. Action: This error is used solely to communicate information between the authentication service and the Oracle Net session layer and should not normally be visible. If the error is seen, contact Oracle Worldwide Support. |
| ORA-12662 ORA-12662, 00000, “proxy ticket retrieval failed” Cause: The authentication adapter used by Oracle Net failed to retrieve the credentials needed to authenticate a database link. Action: Enable tracing to determine the exact error. |
| ORA-12663 ORA-12663, 00000, “Services required by client not available on the server” Cause: Service(s) that was (were) required by the client process were not available on the server process. Action: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure). |
| ORA-12664 ORA-12664, 00000, “Services required by server not available on the client” Cause: Service(s) that was (were) required by the server process were not available on the client process. Action: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure). |
| ORA-12665 ORA-12665, 00000, “NLS string open failed” Cause: A native service was unable to make a string available for use by the National Language Support component. Action: Make sure the National Language Support component has been properly. If it has, enable tracing and report the problem to Customer Support. |
| ORA-12666 ORA-12666, 00000, “Dedicated server: outbound transport protocol different from inbound” Cause: The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server. Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection. |
| ORA-12667 ORA-12667, 00000, “Shared server: outbound transport protocol different from inbound” Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server. Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection |
| ORA-12668 ORA-12668, 00000, “Dedicated server: outbound protocol does not support proxies” Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections. Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. |
| ORA-12669 ORA-12669, 00000, “Shared server: outbound protocol does not support proxies” Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections. Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. |
| ORA-12670 ORA-12670, 00000, “Incorrect role password” Cause: A password supplied for a role could not be validated by the authentication service. Action: Supply the correct password. |
| ORA-12671 ORA-12671, 00000, “Shared server: adapter failed to save context” Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the shared server. Action: Enable tracing to determine the exact error. Contact Oracle Customer Support if the reason is not obvious. |
| ORA-12672 ORA-12672, 00000, “Database logon failure” Cause: The authentication service adapter in use encountered an error it attempted to validate the logon attempt of a user. Action: Enable tracing to determine the exact error encountered by the adapter. |
| ORA-12673 ORA-12673, 00000, “Dedicated server: context not saved” Cause: A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present. Action: This error should not normally be visible to the user. Contact Oracle Customer Support. |
| ORA-12674 ORA-12674, 00000, “Shared server: proxy context not saved” Cause: A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present. Action: This error should not normally be visible to the user. Contact Oracle Customer Support. |
| ORA-12675 ORA-12675, 00000, “External user name not available yet” Cause: The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet. Action: This is just an informational message and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support. |
| ORA-12676 ORA-12676, 00000, “Server received internal error from client” Cause: The server process received an error from the client which indicated that an internal Oracle Net native services error had occurred. Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Oracle Customer Support. |
| ORA-12677 ORA-12677, 00000, “Authentication service not supported by database link” Cause: The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms. Action: Specify an authentication adapter that is shared by the client and the server being used for the database link. |
| ORA-12678 ORA-12678, 00000, “Authentication disabled but required” Cause: The configuration parameters that control whether Oracle Advanced Security authentication is disabled or required were both set to TRUE. Action: Set one or both of the parameters to FALSE. |
| ORA-12679 ORA-12679, 00000, “Native services disabled by other process but required” Cause: The remote process has disabled native services but the local process requires them. Action: Enable native services on the remote process or disable them locally. |
| ORA-12680 ORA-12680, 00000, “Native services disabled but required” Cause: The process has disabled native services but at least one service is required. Action: Enable native services or change the configuration file so that none of the available services are required. |
| ORA-12681 ORA-12681, 00000, “Login failed: the SecurID card does not have a pincode yet” Cause: The SecurID card that is used to logon to Oracle, does not have a pincode assigned to it. Action: Use one of the programs supplied by Security Dynamics to assign a pincode to the card. |
| ORA-12682 ORA-12682, 00000, “Login failed: the SecurID card is in next PRN mode” Cause: The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to resynchronize the card. Action: Use one of the programs supplied by Security Dynamics to resynchronize the SecurID card. |
| ORA-12683 ORA-12683, 00000, “encryption/crypto-checksumming: no Diffie-Hellman seed” Cause: The “sqlnet.crypto_seed” parameter is missing from the SQLNET.ORA parameters file for Oracle Advanced Security. Action: Add this line to SQLNET.ORA: // sqlnet.crypto_seed = “randomly-chosen text” |
| ORA-12684 ORA-12684, 00000, “encryption/crypto-checksumming: Diffie-Hellman seed too small” Cause: The “sqlnet.crypto_seed” parameter in the SQLNET.ORA parameter file for Oracle Advanced Security is too small. Action: Add more randomly-chosen text to it, perhaps using Network Manager. |
| ORA-12685 ORA-12685, 00000, “Native service required remotely but disabled locally” Cause: A native service is required by the remote process but native services have been disabled locally. Action: Enable native services locally or change the configuration parameters on the remote host so that no native services are required. |
| ORA-12686 ORA-12686, 00000, “Invalid command specified for a service” Cause: An operation which does not exist was specified for a native service. Action: This is a programming error and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support. |
| ORA-12687 ORA-12687, 00000, “Credentials expired.” Cause: The credentials that are used to authenticate the user for the requested connection have expired. Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this. |
| ORA-12688 ORA-12688, 00000, “Login failed: the SecurID server rejected the new pincode” Cause: There are a number of reasons why the SecurID server would refuse a pincode: – The user might not have permission to make up his own pincode. – The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters. – The pincode contains any non alphanumeric characters. Action: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error. |
| ORA-12689 ORA-12689, 00000, “Server Authentication required, but not supported” Cause: Server Authentication is required for this connection, but not supported by both sides of the connection. Action: Make sure both sides of the connection have the correct version of Advanced Networking Option, and that the Authentication Adapter supports Server Authentication. |
| ORA-12690 ORA-12690, 00000, “Server Authentication failed, login cancelled” Cause: Server Authentication is required, but the server’s credentials were found invalid by the client. Action: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this. |
| ORA-12696 ORA-12696, 00000, “Double Encryption Turned On, login disallowed” Cause: The user is using a Secure Protocol Adapter that has Encryption turned ON as well as ANO Encryption. Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if possible. Refer to Oracle Advanced Security Administrator’s Guide on how to do this. |
| ORA-12699 ORA-12699, 00000, “Native service internal error” Cause: An internal error occurred in the native services component. Action: Enable tracing to determine the exact error. Contact Oracle Customer Support. |
| ORA-12700 ORA-12700, 00000, “invalid NLS parameter value (%s)” Cause: An invalid or unknown NLS configuration parameter was specified. Action: |
| ORA-12701 ORA-12701, 00000, “CREATE DATABASE character set is not known” Cause: The character set specified when creating the database is unknown. Action: |
| ORA-12702 ORA-12702, 00000, “invalid NLS parameter string used in SQL function” Cause: An unknown parameter name or invalid value is specified in a NLS parameter string. Action: |
| ORA-12703 ORA-12703, 00000, “this character set conversion is not supported” Cause: The requested conversion between two character sets in the CONVERT function is not implemented Action: |
| ORA-12704 ORA-12704, 00000, “character set mismatch” Cause: One of the following: – The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set. – An nlsparams operand is not in the database character set. – String data with character set other than the database character set is passed to a built-in function not expecting it. – The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. – A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. – A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column. – An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter. Action: |
| ORA-12705 ORA-12705, 00000, “Cannot access NLS data files or invalid environment specified” Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located. Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path/values in the environment variables. |
| ORA-12706 ORA-12706, 00000, “this CREATE DATABASE character set is not allowed” Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa. Action: |
| ORA-12707 ORA-12707, 00000, “error while getting create database NLS parameter %s” Cause: Internal error Action: |
| ORA-12708 ORA-12708, 00000, “error while loading create database NLS parameter %s” Cause: Internal error Action: |
| ORA-12709 ORA-12709, 00000, “error while loading create database character set” Cause: Internal error Action: |
| ORA-12710 ORA-12710, 00000, “CREATE CONTROLFILE character set is not known” Cause: The character set specified when creating the control file is unknown. Action: |
| ORA-12711 ORA-12711, 00000, “this CREATE CONTROLFILE character set is not allowed” Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa. |
| ORA-12712 ORA-12712, 00000, “new character set must be a superset of old character set” Cause: When you ALTER DATABASE … CHARACTER SET, the new // character set must be a superset of the old character set. // For example, WE8ISO8859P1 is not a superset of the WE8DEC. Action: Specify a superset character set. |
| ORA-12713 ORA-12713, 00000, “Character data loss in NCHAR/CHAR conversion” Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set. Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE. |
| ORA-12714 ORA-12714, 00000, “invalid national character set specified” Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set Action: Ensure that the specified national character set is valid |
| ORA-12715 ORA-12715, 00000, “invalid character set specified” Cause: The character set specified is not allowed for this operation or is invalid Action: Ensure that the specified character set is valid |
| ORA-12716 ORA-12716, 00000, “Cannot ALTER DATABASE CHARACTER SET when CLOB data exists” Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as import/export |
| ORA-12717 ORA-12717, 00000, “Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists” Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated. Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The above type data can be migrated by methods such as import/export. |
| ORA-12718 ORA-12718, 00000, “operation requires connection as SYS” Cause: This command can only be run when connecting as SYS Action: Connect as SYS to run this command |
| ORA-12719 ORA-12719, 00000, “operation requires database is in RESTRICTED mode” Cause: This command can only be run when the database is in RESTRICTED mode Action: Ensure that the system is in RESTRICTED mode |
| ORA-12720 ORA-12720, 00000, “operation requires database is in EXCLUSIVE mode” Cause: This command can only be run when the database is in EXCLUSIVE mode Action: Ensure that the system is in EXCLUSIVE mode |
| ORA-12721 ORA-12721, 00000, “operation cannot execute when other sessions are active” Cause: This command can only be run when there are no other sessions active Action: Ensure there are no other connections to the database |
| ORA-12722 ORA-12722, 00000, “regular expression internal error” Cause: A regular expression internal error occurred. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-12723 ORA-12723, 00000, “regular expression too complex” Cause: The regular expression was too complex and could not be parsed. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-12724 ORA-12724, 00000, “regular expression corrupt” Cause: The regular expression contained an incorrect sequence of metacharacters. Action: Ensure the metacharacters are correctly positioned. |
| ORA-12725 ORA-12725, 00000, “unmatched parentheses in regular expression” Cause: The regular expression did not have balanced parentheses. Action: Ensure the parentheses are correctly balanced. |
| ORA-12726 ORA-12726, 00000, “unmatched bracket in regular expression” Cause: The regular expression did not have balanced brackets. Action: Ensure the brackets are correctly balanced. |
| ORA-12727 ORA-12727, 00000, “invalid back reference in regular expression” Cause: A back references was found before a sub-expression. Action: Ensure a valid sub-expression is being referenced. |
| ORA-12728 ORA-12728, 00000, “invalid range in regular expression” Cause: An invalid range was found in the regular expression. Action: Ensure a valid range is being used. |
| ORA-12729 ORA-12729, 00000, “invalid character class in regular expression” Cause: An unknown character class was found in the regular expression. Action: Ensure a valid characters class is being used. |
| ORA-12730 ORA-12730, 00000, “invalid equivalence class in regular expression” Cause: An unknown equivalence class was found in the regular expression. Action: Ensure a valid equivalence class is being used. |
| ORA-12731 ORA-12731, 00000, “invalid collation class in regular expression” Cause: An unknown collation class was found in the regular expression. Action: Ensure a valid collation class is being used. |
| ORA-12732 ORA-12732, 00000, “invalid interval value in regular expression” Cause: An invalid interval value was found in the regular expression. Action: Ensure a valid interval value is being used. |
| ORA-12733 ORA-12733, 00000, “regular expression too long” Cause: The operation failed because the regular expression it used exceeds the maximum supported size. Action: Use a shorter regular expression. |
| ORA-12734 ORA-12734,00000,”Instant Client Light: unsupported client national character set %s” Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set |
| ORA-12735 ORA-12735, 00000, “Instant Client Light: unsupported client character set %s” Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set |
| ORA-12736 ORA-12736,00000,”Instant Client Light: unsupported server national character set %s” Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set |
| ORA-12737 ORA-12737, 00000, “Instant Client Light: unsupported server character set %s” Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set |
| ORA-12738 ORA-12738,00000,”Express Instant Client: unsupported client national character set %s” Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets. Action: Do not use Express Instant Client for this character set |
| ORA-12739 ORA-12739, 00000, “Express Instant Client: unsupported client character set %s” Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets. Action: Do not use Express Instant Client for this character set |
| ORA-12740 ORA-12740,00000,”Express Instant Client: unsupported server national character set %s” Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets. Action: Do not use Express Instant Client for this character set |
| ORA-12741 ORA-12741, 00000, “Express Instant Client: unsupported server character set %s” Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets. Action: Do not use Express Instant Light for this character set |
| ORA-12751 ORA-12751, 00000, “cpu time or run time policy violation” Document: NO Cause: A piece of code ran longer than it is supposed to Action: If this error persists, contact Oracle Support Services. |
| ORA-12760 ORA-12760,00000, “ACMS tracing event” Document: NO Cause: Action: |
| ORA-12761 ORA-12761,00000, “ACMS debug event” Document: NO Cause: Action: |
| ORA-12762 ORA-12762,00000, “ACMS service status is unknown” Document: NO Cause: This is an internal status. Action: None. |
| ORA-12763 ORA-12763,00000, “ACMS service is disabled” Document: NO Cause: The ACMS service failed to initialize because of either variances in the Oracle binaries or internal error. Action: Ensure all instances are using the same Oracle binary, and restart all instances. |
| ORA-12764 ORA-12764,00000, “ACMS service encountered inconsistent state” Document: NO Cause: An internal error occured. Action: Ensure all instances are using the same Oracle binary, and restart all instances. |
| ORA-12765 ORA-12765,00000, “ACMS operation is pending cleanup” Document: NO Cause: An attempt of the same operation previously failed and has yet to be cleaned up by PMON. Action: Wait and retry the operation. |
| ORA-12766 ORA-12766,00000, “ACMS failed to acquire share-mode mount lock” Document: NO Cause: An operation was not permitted because the mount lock could not be acquired. Action: Retry the operation. |
| ORA-12767 ORA-12767,00000, “ACMS memory allocation failure” Document: NO Cause: An operation was interrupted because an ACMS background failed to allocate the needed SGA to stage an operation. Action: Ensure the instance has sufficient memory resources. |
| ORA-12768 ORA-12768,00000, “ACMS maximum message size exceeded” Document: NO Cause: An operation failed to start because the requested client data exceeded the maximum supported size. Action: Reduce the size of the data. |
| ORA-12769 ORA-12769,00000, “ACMS message delivery or receipt failure” Document: NO Cause: An operation was interrupted because a failure occured during message delivery or reply processing. Action: This is expected if instances are leaving the cluster. Retry the operation. |
| ORA-12770 ORA-12770,00000, “ACMS operation failure with error context” Document: NO Cause: An operation was interrupted because a failure occured at one or more sites. Action: If supplied, check the status buffer for per-instance error context. |
| ORA-12771 ORA-12771,00000, “ACMS encountered client callback exception” Document: NO Cause: The ACMS server encountered an exception while performing the client callback operation. Action: If supplied, check the status buffer for the exception. |
| ORA-12772 ORA-12772,00000, “ACMS encountered client callback failure status” Document: NO Cause: The ACMS server encountered a failure status from the client callback operation. Action: If supplied, check the status buffer for the return value. |
| ORA-12800 ORA-12800, 00000, “system appears too busy for parallel query execution” Cause: load on system is too high to perform parallel queries. Action: re-execute serially or wait until system load is reduced. |
| ORA-12801 ORA-12801, 00000, “error signaled in parallel query server %s” Cause: A parallel query server reached an exception condition. Action: Check the following error message for the cause, and consult your error manual for the appropriate action. Comment: This error can be turned off with event 10397, in which case the server’s actual error is signaled instead. |
| ORA-12802 ORA-12802, 00000, “parallel query server lost contact with coordinator” Cause: A parallel query server lost contact with the foreground (coordinator) process/thread. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. |
| ORA-12803 ORA-12803, 00000, “parallel query server lost contact with another server” Cause: A parallel query server lost contact with another server. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. |
| ORA-12804 ORA-12804, 00000, “parallel query server appears to have died” Cause: Cannot find process information for a parallel query server thread. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. |
| ORA-12805 ORA-12805, 00000, “parallel query server died unexpectedly” Cause: A parallel query server died unexpectedly, PMON cleaning up the process. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details. |
| ORA-12806 ORA-12806, 00000, “could not get background process to hold enqueue” Cause: Internal error. Action: This error should not normally occur. If it persists, contact Oracle Support Services. |
| ORA-12807 ORA-12807, 00000, “process queue could not receive parallel query message” Cause: Internal error. Action: This error should not normally occur. If it persists, contact Oracle Support Services. |
| ORA-12808 ORA-12808, 00000, “cannot set %s_INSTANCES greater than number of instances %s” Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances. Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL. |
| ORA-12809 ORA-12809, 00000, “cannot set %s_INSTANCES when mounted in exclusive mode” Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode. Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle Real Application Clusters mounted in CLUSTER_DATABASE mode. |
| ORA-12810 ORA-12810, 00000, “PARALLEL_MAX_SERVERS must be less than or equal to %s” Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system. Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry. |
| ORA-12811 ORA-12811, 00000, “PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, %s” Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS. Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry. |
| ORA-12812 ORA-12812, 00000, “only one PARALLEL or NOPARALLEL clause may be specified” Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command. Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement. |
| ORA-12813 ORA-12813, 00000, “value for PARALLEL or DEGREE must be greater than 0″ Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement. Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause. |
| ORA-12814 ORA-12814, 00000, “only one CACHE or NOCACHE clause may be specified” Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement. Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement. |
| ORA-12815 ORA-12815, 00000, “value for INSTANCES must be greater than 0″ Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired. |
| ORA-12816 ORA-12816, 00000, “parallel create index fastpath operation” Cause: Action: set this event only under the supervision Oracle development Comment: this event permits fastpath index creation. it merges sub-index in a quick but suboptimal fashion wrto space usage. Level: the level indicates the number of rows in a branch block that we are willing to copy before attempting fastpath operation. |
| ORA-12817 ORA-12817, 00000, “parallel query option must be enabled” Cause: A parallel query option feature has been invoked but this option has not been enabled. Action: Enable the parallel query option. |
| ORA-12818 ORA-12818, 00000, “invalid option in PARALLEL clause” Cause: an unrecognized option was used within a PARALLEL clause. Action: specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES { <n> | DEFAULT } within the PARALLEL clause. |
| ORA-12819 ORA-12819, 00000, “missing options in PARALLEL clause” Cause: PARALLEL clause cannot be empty. Action: specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES { <n> | DEFAULT } within the PARALLEL clause. |
| ORA-12820 ORA-12820, 00000, “invalid value for DEGREE” Cause: invalid value for DEGREE was specified within a PARALLEL clause. Action: specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause. |
| ORA-12821 ORA-12821, 00000, “invalid value for INSTANCES” Cause: invalid value for INSTANCES was specified within a PARALLEL clause. Action: specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause. |
| ORA-12822 ORA-12822, 00000, “duplicate option in PARALLEL clause” Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause. Action: specify each desired PARALLEL clause option only once. |
| ORA-12823 ORA-12823, 00000, “default degree of parallelism may not be specified here” Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command. Action: respecify with an explicit degree of parallelism. |
| ORA-12824 ORA-12824, 00000, “INSTANCES DEFAULT may not be specified here” Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command Action: respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired. |
| ORA-12825 ORA-12825, 00000, “explicit degree of parallelism must be specified here” Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER command. Action: respecify with an explicit degree of parallelism. |
| ORA-12826 ORA-12826, 00000, “hung parallel query server was killed” Cause: parallel query server was hung and subsequently killed. Action: re-execute query and report suspicious events in trace file to Oracle Support Services if error persists. |
| ORA-12827 ORA-12827, 00000, “insufficient parallel query slaves available” Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired Action: either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves |
| ORA-12828 ORA-12828, 00000, “Can’t start parallel transaction at a remote site” Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction. Action: Do not use PDML at remote sites. |
| ORA-12829 ORA-12829, 00000, “Deadlock – itls occupied by siblings at block %s of file %s” Cause: parallel statement failed because all itls in the current block are occupied by siblings of the same transaction. Action: increase MAXTRANS of the block or reduce the degree of parallelism for the statement. Reexecute the statement. Report suspicious events in trace file to Oracle Support Services if error persists. |
| ORA-12830 ORA-12830, 00000, “Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE” Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued. Action: Execute COMMIT or ROLLBACK before issuing another SQL command. |
| ORA-12831 ORA-12831, 00000, “Must COMMIT or ROLLBACK after executing INSERT with APPEND hint” Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued. Action: Execute COMMIT or ROLLBACK before issuing another SQL command. |
| ORA-12832 ORA-12832, 00000, “Could not allocate slaves on all specified instances” Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances |
| ORA-12833 ORA-12833, 00000, “Coordinator’s instance not a member of parallel_instance_group” Cause: The coordinator’s instance must be a member of the parallel_instance_group in which this operation will be run. Action: Either add the coordinator’s instance to the current parallel_instance_group or change parallel_instance_group. |
| ORA-12834 ORA-12834, 00000, “Instance group name, ‘%s’, too long, must be less than %s characters” Cause: The instance group name is too long. Action: Either shorten the name or get rid of the instance group. |
| ORA-12835 ORA-12835, 00000, “No instances are active in the GLOBAL_VIEW_ADMIN_GROUP” Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP |
| ORA-12836 ORA-12836, 00000, “Control delayed index maintenance event” Document: NO Cause: Action: Control whether a given index will use delayed maintenance. |
| ORA-12837 ORA-12837, 00000, “Delayed index maintenance debugging event” Document: NO Cause: Action: Control dumping of debugging information for dealyed maintenance |
| ORA-12838 ORA-12838, 00000, “cannot read/modify an object after modifying it in parallel” Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted. Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation. |
| ORA-12839 ORA-12839, 00000, “cannot modify an object in parallel after modifying it” Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted. Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation. |
| ORA-12840 ORA-12840, 00000, “cannot access a remote table after parallel/insert direct load txn” Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued. Action: Commit/rollback the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction. |
| ORA-12841 ORA-12841, 00000, “Cannot alter the session parallel DML state within a transaction” Cause: Transaction in progress Action: Commit or rollback transaction and then re-execute |
| ORA-12842 ORA-12842, 00000, “Cursor invalidated during parallel execution” Cause: The cursor was invalidated during the parse phase of deferred parallel processing, e.g. when set operands are parallelized. Action: Depends on why the cursor was invalidated. Possible causes include DDL on a schema object and shared pool being flushed. |
| ORA-12843 ORA-12843, 00000, “pdml lock not held properly on the table” Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire currently. Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the pdml again. |
| ORA-12844 ORA-12844, 00000, “cluster reconfiguration in progress” Cause: Internal error Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR. |
| ORA-12845 ORA-12845, 00000, “failed to receive interinstance parallel execution message” Cause: OS or interconnect problem receiving interinstance message Action: Check OS specific diagnostics |
| ORA-12850 ORA-12850, 00000, “Could not allocate slaves on all specified instances: %s needed, %s allocated” Cause: When executing a query on a gv$ fixed view, one or more instances failed to allocate a slave to process query. Action:Check trace output for instances on which slaves failed to start. GV$ query can only proceed if slaves can be allocated on all instances. |
| ORA-12851 ORA-12851, 00000, “PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, %s” Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less than PARALLEL_MIN_SERVERS. Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to PARALLEL_MIN_SERVERS value specified in the accompanying message and retry. |
| ORA-12852 ORA-12852, 00000, “PARALLEL_MIN_SERVERS must be less than PROCESSES, %s” Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES. Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value specified in the accompanying message and retry. |
| ORA-12853 ORA-12853, 00000, “insufficient memory for PX buffers: current %sK, max needed %sK” Cause: Insufficient SGA memory for PX buffers Action: Reconfigure sga to include at least (max – current) bytes of additional memory |
| ORA-12854 ORA-12854, 00000, “Parallel query is not supported on temporary LOBs” Cause: The parallel query statement produced a temporary LOB. Action: Turn off parallelism for the query or underlying table |
| ORA-12855 ORA-12855, 00000, “cannot run parallel or insert direct load in a loopback” Cause: A loopback was created in the transaction before this operation. Action: Do not use loopback when using pdml or insert direct load. |
| ORA-12856 ORA-12856, 00000, “cannot run parallel query on a loopback connection” Cause: A table or index in a parallel query is referenced via a loopback connection. Action: Do not use loopback connection when running a query in parallel. |
| ORA-12872 ORA-12872, 00000, “First slave parse gave different plan” Cause: First hard parse on slave given QC-supplied environment and parameters gave different plan from QC. Try again with outline. Action: No external action. Internally used for outline-based reparse. |
| ORA-12899 ORA-12899, 00000, “value too large for column %s (actual: %s, maximum: %s)” Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column. The name of the column is given, along with the actual width of the value, and the maximum allowed width of the column. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes. Action: Examine the SQL statement for correctness. Check source and destination column data types. Either make the destination column wider, or use a subset of the source column (i.e. use substring). |
| ORA-12900 ORA-12900, 00000, “must specify a default temporary tablespace for a locally managed database” Cause: a locally managed database must have a temporary tablespace other than SYSTEM tablespace Action: specify the default temporary tablespace when creating a locally managed database |
| ORA-12901 ORA-12901, 00000, “default temporary tablespace must be of TEMPORARY type” Cause: in a locally managed database, default temporary tablespace must be TEMPORARY type Action: |
| ORA-12902 ORA-12902, 00000, “default temporary tablespace must be SYSTEM or of TEMPORARY type” Cause: in a dictionary managed database, default temporary tablespace must be SYSTEM or TEMPORARY type Action: |
| ORA-12903 ORA-12903, 00000, “default temporary tablespace must be an ONLINE tablespace” Cause: Action: |
| ORA-12904 ORA-12904, 00000, “default temporary tablespace cannot be altered to PERMANENT type” Cause: Action: |
| ORA-12905 ORA-12905, 00000, “default temporary tablespace cannot be brought OFFLINE” Cause: Action: |
| ORA-12906 ORA-12906, 00000, “cannot drop default temporary tablespace” Cause: Action: |
| ORA-12907 ORA-12907, 00000, “tablespace %s is already the default temporary tablespace” Cause: Action: |
| ORA-12908 ORA-12908, 00000, “cannot specify SYSTEM as default temporary tablespace when creating database” Cause: Action: |
| ORA-12909 ORA-12909, 00000, “TEMPORARY keyword expected” Cause: Action: |
| ORA-12910 ORA-12910, 00000, “cannot specify temporary tablespace as default tablespace” Cause: attempt to assign a temporary tablespace to be a user’s default tablespace Action: assign a permanent tablespace to be the default tablespace |
| ORA-12911 ORA-12911, 00000, “permanent tablespace cannot be temporary tablespace” Cause: attempt to assign a permanent tablespace to be a user’s temporary tablespace Action: assign a temporary tablespace to be user’s temporary tablespace |
| ORA-12912 ORA-12912, 00000, “Dictionary managed tablespace specified as temporary tablespace” Cause: attempt to assign a dictionary managed tablespace to be a user’s temporary tablespace Action: Assign a locally managed temporary tablespace to be user’s temporary tablespace |
| ORA-12913 ORA-12913, 00000, “Cannot create dictionary managed tablespace” Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed Action: Create a locally managed tablespace. |
| ORA-12914 ORA-12914, 00000, “Cannot migrate tablespace to dictionary managed type” Cause: Attemp to migrate locally managed tablespace to dictionary managed type when the database has locally managed system tablespace. Action: Command cannot be issued. |
| ORA-12915 ORA-12915, 00000, “Cannot alter dictionary managed tablespace to read write” Cause: Attemp to alter dictionary managed tablespace to read write in database which has system tablespace as locally managed. This tablespace can only be dropped. Action: Command cannot be issued. |
| ORA-12916 ORA-12916, 00000, “cannot shrink permanent or dictionary managed tablespace” Cause: An attempt was made to shrink a permanent tablespace or a dictionary managed tablespace. Action: Check the tablespace type and issue the statement only on locally managed temporary tablespaces. |
| ORA-12917 ORA-12917, 00000, “Invalid option specified for default permanent tablespace” Cause: Action: |
| ORA-12918 ORA-12918, 00000, “Invalid tablespace type for default permanent tablespace” Cause: The tablespace is either dropped, temporary or undo Action: Check the tablespace type and reissue the statement |
| ORA-12919 ORA-12919, 00000, “Can not drop the default permanent tablespace” Cause: An attemp was made to drop the default permanent tablespace Action: Make a different tablespace as the default permanent tablespace and reissue the drop |
| ORA-12920 ORA-12920, 00000, “database is already in force logging mode” Cause: ALTER DATABASE FORCE LOGGING command failed because the database is already in force logging mode. Action: |
| ORA-12921 ORA-12921, 00000, “database is not in force logging mode” Cause: ALTER DATABASE NO FORCE LOGGING command failed because the database is not in force logging mode. Action: |
| ORA-12922 ORA-12922, 00000, “concurrent ALTER DATABASE [NO] FORCE LOGGING command is running” Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING command running in the system. Action: Contact the database administrator who is responsible for the concurrent command. |
| ORA-12923 ORA-12923, 00000, “tablespace %s is in force logging mode” Cause: An attempt to alter the specified tablespace temporary failed because the tablespace is in force logging mode. Action: Put the tablespace out of force logging mode by ALTER TABLESPACE NO FORCE LOGGING command. |
| ORA-12924 ORA-12924, 00000, “tablespace %s is already in force logging mode” Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode. Action: |
| ORA-12925 ORA-12925, 00000, “tablespace %s is not in force logging mode” Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode. |
| ORA-12926 ORA-12926, 00000, “FORCE LOGGING option already specified” Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once. Action: Remove all but one of the FORCE LOGGING options. |
| ORA-12927 ORA-12927, 00000, “RETENTION option already specified” Cause: In CREATE TABLESPACE, the RETENTION option was specified more than once. Action: Remove all but one of the RETENTION options. |
| ORA-12928 ORA-12928, 00000, “ENCRYPTION option already specified” Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more than once. Action: Remove all but one of the ENCRYPTION options. |
| ORA-12940 ORA-12940, 00000, “Not enough space in DBVerify text buffer” Cause: DBVerify ran out of text buffer. The error was trapped internally by the system. DBVerify would return the result in text buffer and then resume checking. Action: None |
| ORA-12941 ORA-12941, 00000, “DBVerify exception” Cause: DBVerify encountered run-time error. The error signal was trapped internally by the system. Action: None |
| ORA-12950 ORA-12950, 00000, “SYSTEM tablespace specified as default permanent tablespace” Cause: SYSTEM tablespace was specified as the default permanent during database creation. Action: If default permanent tablespace is not specified,then SYSTEM will implicitly become the default permanent tablespace. Specify an alternate tablespace or omit the default tablespace clause and reissue the CREATE DATABASE statement |
| ORA-12951 ORA-12951, 00000, “Attempt to change default permanent tablespace to temporary” Cause: It is incorrect to alter the default permanent tablespace of a database to temporary type Action: |
| ORA-12952 ORA-12952, 00000, “Control space growth in ASSM segment under concurrency” Cause: Action: Set this event only under the supervision of Oracle Support Services. |
| ORA-12980 ORA-12980, 00000, “checkpoint option not allowed with SET UNUSED” Cause: An attempt was made to specify checkpoint option with SET UNUSED. Action: Remove checkpoint option. |
| ORA-12981 ORA-12981, 00000, “cannot drop column from an object type table” Cause: An attempt was made to drop a column from an object type table. Action: This action is not allowed. |
| ORA-12982 ORA-12982, 00000, “cannot drop column from a nested table” Cause: An attempt was made to drop a column from a nested table. Action: This action is not allowed. |
| ORA-12983 ORA-12983, 00000, “cannot drop all columns in a table” Cause: An attempt was made to drop all columns in a table. Action: Make sure at least one column remains in the table after the drop column operation. |
| ORA-12984 ORA-12984, 00000, “cannot drop partitioning column” Cause: An attempt was made to drop a column used as the partitioning key. Action: This action is not allowed. |
| ORA-12985 ORA-12985, 00000, “tablespace ‘%s’ is read only, cannot drop column” Cause: An attempt was made to drop column from a partition/subpartition on a read only tablespace. Action: Set the tablespace to read write and resubmit statement. |
| ORA-12986 ORA-12986, 00000, “columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE” Cause: An attempt was made to access a table with columns in partially dropped state (i.e., drop column operation was interrupted). Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table. |
| ORA-12987 ORA-12987, 00000, “cannot combine drop column with other operations” Cause: An attempt was made to combine drop column with other ALTER TABLE operations. Action: Ensure that drop column is the sole operation specified in ALTER TABLE. |
| ORA-12988 ORA-12988, 00000, “cannot drop column from table owned by SYS” Cause: An attempt was made to drop a column from a system table. Action: This action is not allowed |
| ORA-12989 ORA-12989, 00000, “invalid value for checkpoint interval” Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1). Action: Correct checkpoint interval and resubmit statement |
| ORA-12990 ORA-12990, 00000, “duplicate option specified” Cause: Duplicate option specified in statement. Action: Remove the duplicate option and resubmit statement. |
| ORA-12991 ORA-12991, 00000, “column is referenced in a multi-column constraint” Cause: An attempt was made to drop a column referenced by some constraints. Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement. |
| ORA-12992 ORA-12992, 00000, “cannot drop parent key column” Cause: An attempt was made to drop a parent key column. Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement. |
| ORA-12993 ORA-12993, 00000, “tablespace ‘%s’ is offline, cannot drop column” Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace. Action: Bring the tablespace online and resubmit statement. |
| ORA-12994 ORA-12994, 00000, “drop column option only allowed once in statement” Cause: An attempt was made to repeat the drop column option in a single statement. Action: Separate drop column options into different statements and resubmit statements. |
| ORA-12995 ORA-12995, 00000, “no columns in partially dropped state” Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns. Action: Cannot submit this statement. |
| ORA-12996 ORA-12996, 00000, “cannot drop system-generated virtual column” Cause: An attempt was made to drop a virtual column generated by the system. |
| ORA-12997 ORA-12997, 00000, “cannot drop primary key column from an index-organized table” Cause: An attempt was made to drop a primary key column from an index- organized table. Action: This action is not allowed. |
| ORA-12998 ORA-12998, 00000, “Ignore errors during drop column from atb.c” Cause: Action: |
| ORA-13000 ORA-13000, 00000, “dimension number is out of range” Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE. Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE. |
| ORA-13001 ORA-13001, 00000, “dimensions mismatch error” Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match. Action: Make sure that the number of dimensions in the HHCODEs match. |
| ORA-13002 ORA-13002, 00000, “specified level is out of range” Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE. Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE. |
| ORA-13003 ORA-13003, 00000, “the specified range for a dimension is invalid” Cause: The specified range for a dimension is invalid. Action: Make sure that the lower bound (lb) is less than the upper bound (ub). |
| ORA-13004 ORA-13004, 00000, “the specified buffer size is invalid” Cause: The buffer size for a function is not valid. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-13005 ORA-13005, 00000, “recursive HHCODE function error” Cause: An error occurred in a recursively called HHCODE function. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-13006 ORA-13006, 00000, “the specified cell number is invalid” Cause: The cell identifier is either less than 0 or greater than (2^ndim – 1). Action: Make sure that the cell identifier is between 0 and (2^ndim – 1). |
| ORA-13007 ORA-13007, 00000, “an invalid HEX character was detected” Cause: A character that is not in the range [0-9] or [A-F a-f] was detected. Action: Verify that all characters in a string are in [0-9] or [A-F a-f]. |
| ORA-13008 ORA-13008, 00000, “the specified date format has an invalid component” Cause: Part of specified date format is invalid. Action: Verify that the date format is valid. |
| ORA-13009 ORA-13009, 00000, “the specified date string is invalid” Cause: The specified date string has a bad component or does not match the specified format string. Action: Make sure that the components of the date string are valid and that the date and format strings match. |
| ORA-13010 ORA-13010, 00000, “an invalid number of arguments has been specified” Cause: An invalid number of arguments was specified for an SDO function. Action: Verify the syntax of the function call. |
| ORA-13011 ORA-13011, 00000, “value is out of range” Cause: A specified dimension value is outside the range defined for that dimension. Action: Make sure that all values to be encoded are within the defined dimension range. |
| ORA-13012 ORA-13012, 00000, “an invalid window type was specified” Cause: An invalid window type was specified. Action: Valid window types are RANGE, PROXIMITY, POLYGON. |
| ORA-13013 ORA-13013, 00000, “the specified topology was not INTERIOR or BOUNDARY” Cause: A topology was specified that was not INTERIOR or BOUNDARY. Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE’s topology. |
| ORA-13014 ORA-13014, 00000, “a topology identifier outside the range of 1 to 8 was specified” Cause: A topology identifier outside the range of 1 to 8 was specified. Action: Specify a topology in the range of 1 to 8. |
| ORA-13015 ORA-13015, 00000, “the window definition is not valid” Cause: The number of values used to define the window does not correspond to the window type. Action: Verify that the number of values used to defined the window is correct for the window type and number of dimensions. |
| ORA-13016 ORA-13016, 00000, ” specified topology [%s] is invalid” Cause: The specified topology did not exist in the database, or some components of the topology were missing from the database. Action: Check the specified topology by executing the SDO_TOPO.validate_topology function. |
| ORA-13017 ORA-13017, 00000, “unrecognized line partition shape” Cause: The shape of a 2-D line partition could not be determined. Action: This is an internal error. Contact Oracle Support Services. |
| ORA-13018 ORA-13018, 00000, “bad distance type” Cause: The specified distance type is invalid. Action: The only supported distance functions are EUCLID and MANHATTAN. |
| ORA-13019 ORA-13019, 00000, “coordinates out of bounds” Cause: Vertex coordinates lie outside the valid range for specified dimension. Action: Redefine vertex coordinates within specified boundaries. |
| ORA-13020 ORA-13020, 00000, “coordinate is NULL” Cause: A vertex coordinate has a NULL value. Action: Redefine vertex coordinate to have non-NULL value. |
| ORA-13021 ORA-13021, 00000, “element not continuous” Cause: The coordinates defining a geometric element are not connected. Action: Redefine coordinates for the geometric element. |
| ORA-13022 ORA-13022, 00000, “polygon crosses itself” Cause: The coordinates defining a polygonal geometric element represent crossing segments. Action: Redefine coordinates for the polygon. |
| ORA-13023 ORA-13023, 00000, “interior element interacts with exterior element” Cause: An interior element of a geometric object interacts with the exterior element of that object. Action: Redefine coordinates for the geometric elements. |
| ORA-13024 ORA-13024, 00000, “polygon has less than three segments” Cause: The coordinates defining a polygonal geometric element represent less than three segments. Action: Redefine the coordinates for the polygon. |
| ORA-13025 ORA-13025, 00000, “polygon does not close” Cause: The coordinates defining a polygonal geometric element represent an open polygon. Action: Redefine the coordinates of the polygon. |
| ORA-13026 ORA-13026, 00000, “unknown element type for element %s.%s.%s” Cause: The SDO_ETYPE column in the <layer>_SDOGEOM table contains an invalid geometric element type value. Action: Redefine the geometric element type in the <layer>_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial documentation for an explanation of SDO_ETYPE and its possible values. |
| ORA-13027 ORA-13027, 00000, “unable to read dimension definition from %s” Cause: There was a problem reading the dimension definition from the <layer>_SDODIM table. Action: Verify that the <layer>_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message. |
| ORA-13028 ORA-13028, 00000, “Invalid Gtype in the SDO_GEOMETRY object” Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object. Action: Verify that the geometries have valid gtypes. |
| ORA-13029 ORA-13029, 00000, “Invalid SRID in the SDO_GEOMETRY object” Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range. Action: Verify that the geometries have valid SRIDs. |
| ORA-13030 ORA-13030, 00000, “Invalid dimension for the SDO_GEOMETRY object” Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object. Action: Verify that the geometries have valid dimensionality. |
| ORA-13031 ORA-13031, 00000, “Invalid Gtype in the SDO_GEOMETRY object for point object” Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT. Action: Verify that the geometries have valid gtypes. |
| ORA-13032 ORA-13032, 00000, “Invalid NULL SDO_GEOMETRY object” Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object. Action: Verify that the geometries have valid fields. To specify a NULL geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL. |
| ORA-13033 ORA-13033, 00000, “Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object” Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry. Action: Verify that the geometries have valid data. |
| ORA-13034 ORA-13034, 00000, “Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object” Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X or Y or both. Action: Verify that the geometries have valid data. |
| ORA-13035 ORA-13035, 00000, “Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object” Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates. Action: Verify that the geometries have valid data. |
| ORA-13036 ORA-13036, 00000, “Operation [%s] not supported for Point Data” Cause: The specified geometry function is not supported for point data. Action: Make sure that the specified geometry function is not called on point data. |
| ORA-13037 ORA-13037, 00000, “SRIDs do not match for the two geometries” Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID. Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs. |
| ORA-13039 ORA-13039, 00000, “failed to update spatial index for element %s.%s.%s” Cause: Another error will accompany this message that will indicate the problem. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. |
| ORA-13040 ORA-13040, 00000, “failed to subdivide tile” Cause: This is an internal error. Action: Note any accompanying errors and contact Oracle Support Services. |
| ORA-13041 ORA-13041, 00000, “failed to compare tile with element %s.%s.%s” Cause: The spatial relationship between a generated tile and the specified element could not be determined. Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13041 and contact Oracle Support Services. |
| ORA-13042 ORA-13042, 00000, “invalid SDO_LEVEL and SDO_NUMTILES combination” Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the <layer>_SDOLAYER table. The most likely cause is that the columns are NULL. Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial documentation. Then retry the operation. |
| ORA-13043 ORA-13043, 00000, “failed to read metadata from the <layer>_SDOLAYER table” Cause: An error was encountered reading the layer metadata from the <layer>_SDOLAYER table. Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, contact Oracle Support Services. |
| ORA-13044 ORA-13044, 00000, “the specified tile size is smaller than the tolerance” Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata. Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a smaller tile size value than the current one. |
| ORA-13045 ORA-13045, 00000, “invalid compatibility flag” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13046 ORA-13046, 00000, “invalid number of arguments ” Cause: An invalid number of arguments were specified for an SDO_GEOM function. Action: See the Oracle Spatial documentation for a description of the syntax and semantics of the relevant SDO_GEOM function. |
| ORA-13047 ORA-13047, 00000, “unable to determine ordinate count from table <layer>_SDOLAYER” Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer <layer>. Action: Verify that the <layer>_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation. |
| ORA-13048 ORA-13048, 00000, “recursive SQL fetch error” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13049 ORA-13049, 00000, “unable to determine tolerance value from table <layer>_SDODIM” Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer <layer>. Action: Verify that the <layer>_SDODIM table has a valid value for the column SDO_TOLERANCE. |
| ORA-13050 ORA-13050, 00000, “unable to construct spatial object” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13051 ORA-13051, 00000, “failed to initialize spatial object” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13052 ORA-13052, 00000, “unsupported geometric type for geometry %s.%s” Cause: The geometry type for a specific instance in a <layer>_SDOGEOM table is not among the set of geometry types supported by Oracle Spatial. Action: Check the Oracle Spatial documentation for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema. |
| ORA-13053 ORA-13053, 00000, “maximum number of geometric elements in argument list exceeded” Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded. Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function. |
| ORA-13054 ORA-13054, 00000, “recursive SQL parse error” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13055 ORA-13055, 00000, “Oracle object %s does not exist in specified table” Cause: The requested object is not present in the specified table. Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation. |
| ORA-13060 ORA-13060, 00000, “topology with the name %s already exists” Cause: The specified topology name was not unique in the database. Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name and that the procedure is invoked from the correct schema. |
| ORA-13061 ORA-13061, 00000, “topology with the name %s does not exist” Cause: The specified topology did not exist in the database. Action: Verify that the current procedure/function call specifies the correct schema and topology name. |
| ORA-13062 ORA-13062, 00000, “topology IDs do not match in the feature table and the topology” Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata. Action: Verify that the specified topology ID matches the topology ID stored in the topology metadata. |
| ORA-13063 ORA-13063, 00000, “relationship information table is missing data for feature table [%s]” Cause: The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table. Action: Make sure the correct topology IDs and names are specified in the call to register the feature table with the topology. |
| ORA-13064 ORA-13064, 00000, “relationship information table has inconsistent data for feature table [%s]” Cause: The topology_id, tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$). Action: Make sure that the correct feature tables are specified in the call to register the feature table with the topology. |
| ORA-13065 ORA-13065, 00000, “cannot delete a child layer with a parent layer” Cause: A call was made to delete a feature layer which has a dependent layer defined on it. Action: Make sure that all dependent feature layers are deleted before deleting the current feature layer. |
| ORA-13066 ORA-13066, 00000, “wrong feature geometry or element type” Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type. Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY object. |
| ORA-13067 ORA-13067, 00000, “operator requires both parameters from the same topology” Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology. Action: Make sure both the parameters to the operator are from the same topology. If this is not possible, consider using a signature of the operator that does not use two SDO_TOPO_GEOMETRY parameters. |
| ORA-13068 ORA-13068, 00000, “wrong table or column name in SDO_TOPO_GEOMETRY constructor” Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name. Action: Fix the parameters in the call and try again. |
| ORA-13108 ORA-13108, 00000, “spatial table %s not found” Cause: The specified spatial table does not exist. Action: Check the Spatial data dictionary to make sure that the table is registered. |
| ORA-13109 ORA-13109, 00000, “spatial table %s exists” Cause: The specified spatial table is registered in the Spatial data dictionary. Action: Remove the existing table from the Spatial data dictionary or use a different name. |
| ORA-13110 ORA-13110, 00000, “cannot drop topology with associated topo_geometry tables” Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it. Action: Delete the topo_geometry layers from the topology before dropping the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry layers from the topology. |
| ORA-13111 ORA-13111, 00000, “cannot add topo_geometry layer [%s] to topology” Cause: It was not possible to add the specified topo_geometry layer to the topology. Action: Make sure the topo_geometry layer table exists in the database. |
| ORA-13112 ORA-13112, 00000, “cannot delete topo_geometry layer [%s] from topology” Cause: It was not possible to delete the specified topo_geometry layer from the topology. Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it. |
| ORA-13113 ORA-13113, 00000, “invalid tg_layer_id in sdo_topo_geometry constructor” Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor. Action: Valid layer_ids are obtained by adding a topo_geometry layer to the topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an existing topo_geometry layer. |
| ORA-13114 ORA-13114, 00000, “[%s]_NODE$ table does not exist” Cause: The NODE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. |
| ORA-13115 ORA-13115, 00000, “[%s]_EDGE$ table does not exist” Cause: The EDGE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. |
| ORA-13116 ORA-13116, 00000, “[%s]_FACE$ table does not exist” Cause: The FACE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. |
| ORA-13117 ORA-13117, 00000, “[%s]_RELATION$ table does not exist” Cause: The RELATION$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. |
| ORA-13118 ORA-13118, 00000, “invalid node_id [%s]” Cause: A topology node operation was invoked with an invalid node_id. Action: Check the topology node$ table to see if the specified node_id exists in the topology. |
| ORA-13119 ORA-13119, 00000, “invalid edge_id [%s]” Cause: A topology edge operation was invoked with an invalid edge_id. Action: Check the topology edge$ table to see if the specified edge_id exists in the topology. |
| ORA-13120 ORA-13120, 00000, “invalid face_id [%s]” Cause: A topology face operation was invoked with an invalid face_id. Action: Check the topology face$ table to see if the specified face_id exists in the topology. |
| ORA-13121 ORA-13121, 00000, “layer type type mismatch with topo_geometry layer type” Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer. Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the layer and use it in the constructor. |
| ORA-13122 ORA-13122, 00000, “invalid topo_geometry specified” Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid. Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object. |
| ORA-13123 ORA-13123, 00000, “invalid <TOPOLOGY> name specified” Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database. Action: Check to see if there is already an entry in the USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) with this topology name. |
| ORA-13124 ORA-13124, 00000, “unable to determine column id for column %s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13125 ORA-13125, 00000, “partition key is already set” Cause: A partition key is already set for the spatial table. Action: Only one partition key can be specified per spatial table. |
| ORA-13126 ORA-13126, 00000, “unable to determine class for spatial table %s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13127 ORA-13127, 00000, “failed to generate target partition” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13128 ORA-13128, 00000, “current tiling level exceeds user specified tiling level” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13129 ORA-13129, 00000, “HHCODE column %s not found” Cause: The specified spatial column does not exist. Action: Verify that the specified column is a spatial column by checking the Spatial data dictionary. |
| ORA-13135 ORA-13135, 00000, “failed to alter spatial table” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13136 ORA-13136, 00000, “null common code generated” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13137 ORA-13137, 0000, “failed to generate tablespace sequence number” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13138 ORA-13138, 00000, “could not determine name of object %s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13139 ORA-13139, 00000, “could not obtain column definition for %s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13140 ORA-13140, 00000, “invalid target type” Cause: The specified target type is not valid. Action: Substitute a valid target type. Valid target types are TABLE and VIEW. |
| ORA-13141 ORA-13141, 00000, “invalid RANGE window definition” Cause: The RANGE window specified is not correctly defined. Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,…). There should be an even number of values. |
| ORA-13142 ORA-13142, 00000, “invalid PROXIMITY window definition” Cause: The PROXIMITY window specified is not correctly defined. Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values. |
| ORA-13143 ORA-13143, 00000, “invalid POLYGON window definition” Cause: The POLYGON window specified is not correctly defined. Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values. |
| ORA-13144 ORA-13144, 00000, “target table %s not found” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13145 ORA-13145, 00000, “failed to generate range list” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13146 ORA-13146, 00000, “could not find table substitution variable %s” Cause: The partition name substitution variable %s was not found in the SQL filter. Action: The substitution variable %s must be in the SQL filter to indicate where that partition name should be placed. |
| ORA-13147 ORA-13147, 00000, “failed to generate MBR” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13148 ORA-13148, 00000, “failed to generate SQL filter” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13149 ORA-13149, 00000, “failed to generate next sequence number for spatial table %s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13150 ORA-13150, 00000, “failed to insert exception record” Cause: Operation failed to insert a record into the exception table. Action: Fix any other errors reported. |
| ORA-13151 ORA-13151, 00000, “failed to remove exception record” Cause: Operation failed to remove a record from the exception table. Action: Fix any other errors reported. |
| ORA-13152 ORA-13152, 00000, “invalid HHCODE type” Cause: Specified HHCODE type is not valid. Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE. |
| ORA-13153 ORA-13153, 00000, “invalid high water mark specified” Cause: The high water mark must be greater than or equal to zero. Action: Make sure that the high water mark is an integer greater than or equal to zero. |
| ORA-13154 ORA-13154, 00000, “invalid precision specified” Cause: The precision specified is out of range. Action: The precision must be an integer greater than or equal to zero. |
| ORA-13155 ORA-13155, 00000, “invalid number of dimensions specified” Cause: The number of dimensions specified is out of range. Action: The number of dimension must be between 1 and 32. |
| ORA-13156 ORA-13156, 00000, “table to be registered %s.%s is not empty” Cause: The specified table has rows in it. Action: Make sure that the table to be registered is empty. |
| ORA-13157 ORA-13157, 00000, “Oracle error ORA%s encountered while %s” Cause: The specified Oracle error was encountered. Action: Correct the Oracle error. |
| ORA-13158 ORA-13158, 00000, “Oracle object %s does not exist” Cause: The specified object does not exist. Action: Verify that the specified object exists. |
| ORA-13159 ORA-13159, 00000, “Oracle table %s already exists” Cause: The specified table already exists. Action: Drop the specified table. |
| ORA-13181 ORA-13181, 00000, “unable to determine length of column %s_SDOINDEX.SDO_CODE” Cause: The length of the SDO_CODE column in the <layer>_SDOINDEX table could not be determined. Action: Make sure that the <layer>_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation. |
| ORA-13182 ORA-13182, 00000, “failed to read element %s.%s.%s” Cause: The specified element could not be read from the <layer>_SDOGEOM table. Action: Verify that the specified element exists in the table. Then retry the operation. |
| ORA-13183 ORA-13183, 00000, “unsupported geometric type for geometry %s.%s” Cause: The geometry type in the <layer>_SDOGEOM table is unsupported. Action: Modify the geometry type to be one of the supported types. |
| ORA-13184 ORA-13184, 00000, “failed to initialize tessellation package ” Cause: Initialization of the tessellation package failed. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13185 ORA-13185, 00000, “failed to generate initial HHCODE” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13186 ORA-13186, 00000, “fixed tile size tessellation failed” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13187 ORA-13187, 00000, “subdivision failed” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13188 ORA-13188, 00000, “cell decode failed” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13189 ORA-13189, 00000, “recursive SQL parse failed” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13190 ORA-13190, 00000, “recursive SQL fetch failed” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13191 ORA-13191, 00000, “failed to read SDO_ORDCNT value” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13192 ORA-13192, 00000, “failed to read number of element rows” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13193 ORA-13193, 00000, “failed to allocate space for geometry” Cause: There was insufficient memory to read the geometry from the database. Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13194 ORA-13194, 00000, “failed to decode supercell” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13195 ORA-13195, 00000, “failed to generate maximum tile value” Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. |
| ORA-13196 ORA-13196, 00000, “failed to compute supercell for element %s.%s.%s” Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| ORA-13197 ORA-13197, 00000, “element %s.%s.%s is out of range” Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the <layer>_SDODIM table. Action: Verify that the geometry is valid and within the defined domain. |
| ORA-13198 ORA-13198, 00000, “Spatial error: %s” Cause: Internal error in some Oracle Spatial stored procedure. Action: Record the sequence of procedure calls or events that preceded this error, and contact Oracle Support Services if the error message text does not clearly specify the cause of the error. |
| ORA-13199 ORA-13199, 00000, “%s” Cause: This is an internal error. Action: Contact Oracle Support Services. |
| ORA-13200 ORA-13200, 00000, “internal error [%s] in spatial indexing.” Cause: This is an internal error. Action: Contact Oracle Support Services with the exact error text. |
| ORA-13201 ORA-13201, 00000, “invalid parameters supplied in CREATE INDEX statement” Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement. Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for spatial index creation. |
| ORA-13202 ORA-13202, 00000, “failed to create or insert into the SDO_INDEX_METADATA table” Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it. Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace. |
| ORA-13203 ORA-13203, 00000, “failed to read USER_SDO_GEOM_METADATA view” Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA view. Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table. |
| ORA-13204 ORA-13204, 00000, “failed to create spatial index table” Cause: An error was encountered while trying to create the index table. Action: Check that user has CREATE TABLE privilege in the current schema and that the user has sufficient quota in the default or specified tablespace. |
| ORA-13205 ORA-13205, 00000, “internal error while parsing spatial parameters” Cause: An internal error was encountered while parsing the spatial parameters. Action: Check that the parameters passed in the parameter string are all valid. |
| ORA-13206 ORA-13206, 00000, “internal error [%s] while creating the spatial index” Cause: An internal error was encountered while creating the spatial index. Action: Contact Oracle Support Services with the exact error text. |
| ORA-13207 ORA-13207, 00000, “incorrect use of the [%s] operator” Cause: An error was encountered while evaluating the specified operator. Action: Check the parameters and the return type of the specified operator. |
| ORA-13208 ORA-13208, 00000, “internal error while evaluating [%s] operator” Cause: An internal error was encountered. Action: Contact Oracle Support Services with the exact error text. |
| ORA-13209 ORA-13209, 00000, “internal error while reading SDO_INDEX_METADATA table” Cause: An internal error was encountered while trying to read the SDO_INDEX_METADATA table. Action: Contact Oracle Support Services. Note this and accompanying error numbers. |
| ORA-13210 ORA-13210, 00000, “error inserting data into the index table” Cause: An error was encountered while trying to insert data into the index table. Likely causes are: – Insufficient quota in the current tablespace – User does not appropriate privileges Action: Check the accompanying error messages. |
| ORA-13211 ORA-13211, 00000, “failed to tessellate the window object” Cause: An internal error was encountered while trying to tessellate the window object. Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. |
| ORA-13212 ORA-13212, 00000, “failed to compare tile with the window object ” Cause: The spatial relationship between a generated tile and the specified window object could not be determined. Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any accompanying errors and contact Oracle Support Services. |
| ORA-13213 ORA-13213, 00000, “failed to generate spatial index for window object” Cause: Another error, indicating the real cause of the problem, should accompany this error. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. |
| ORA-13214 ORA-13214, 00000, “failed to compute supercell for window object ” Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| ORA-13215 ORA-13215, 00000, “window object is out of range” Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view. Action: Verify that the geometry is valid and within the defined domain. |
| ORA-13216 ORA-13216, 00000, “failed to update spatial index” Cause: Another error will accompany this message that will indicate the problem. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. |
| ORA-13217 ORA-13217, 00000, “invalid parameters supplied in ALTER INDEX statement” Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement. Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for the spatial ALTER INDEX statement. |
| ORA-13218 ORA-13218, 00000, “max number of supported index tables reached for [%s] index” Cause: An add_index parameter was passed to ALTER INDEX when the number of existing index tables is already at maximum. Action: Delete one of the index tables before adding another index table. |
| ORA-13219 ORA-13219, 00000, “failed to create spatial index table [%s]” Cause: An error was encountered while trying to create the index table. Action: There is a table in the index’s schema with the specified name. The CREATE INDEX statement will try to create an index table with this name. Either rename this table or change the name of the index. |
| ORA-13220 ORA-13220, 00000, “failed to compare tile with the geometry” Cause: The spatial relationship between a generated tile and the specified geometry could not be determined. Action: This is an internal error. Validate the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13220 and contact Oracle Support Services. |
| ORA-13221 ORA-13221, 00000, “unknown geometry type in the geometry object” Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value Action: Redefine the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial documentation for an explanation of SDO_GTYPE and its possible values. |
| ORA-13222 ORA-13222, 00000, “failed to compute supercell for geometry in %s” Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| ORA-13223 ORA-13223, 00000, “duplicate entry for %s in SDO_GEOM_METADATA” Cause: There are duplicate entries for the given table and column value pair in the USER_SDO_GEOM_METADATA view. Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the USER_SDO_GEOM_METADATA view. |
| ORA-13224 ORA-13224, 00000, “zero tolerance specified for layer in USER_SDO_GEOM_METADATA” Cause: A tolerance of zero or NULL is supplied for a layer in USER_SDO_GEOM_METADATA view. Action: Check the tolerance specified to make sure it is a positive value. |
| ORA-13225 ORA-13225, 00000, “specified index table name is too long for a spatial index” Cause: An index table name is specified which is longer than the supported length of the spatial index table name. Action: Check the supported size of the index table name and reduce the size of the index name. |
| ORA-13226 ORA-13226, 00000, “interface not supported without a spatial index” Cause: The geometry table does not have a spatial index. Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it. |
| ORA-13227 ORA-13227, 00000, “SDO_LEVEL values for the two index tables do not match” Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match. Action: Verify that two compatible indexes are used for the spatial join operator. Quadtree indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values |
| ORA-13228 ORA-13228, 00000, “spatial index create failed due to invalid type” Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY. Action: Make sure that the index is created on a column of type SDO_GEOMETRY. |
| ORA-13230 ORA-13230, 00000, “failed to create temporary table [%s] during R-tree creation” Cause: The specified temporary table either already exists or there is not enough tablespace. Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. |
| ORA-13231 ORA-13231, 00000, “failed to create index table [%s] during R-tree creation” Cause: The specified index table either already exists or there is not enough tablespace. Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. If that fails to correct the problem, contact Oracle Support Services. |
| ORA-13232 ORA-13232, 00000, “failed to allocate memory during R-tree creation” Cause: This feature assumes a minimum of 64K memory for bulk creation. Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data. |
| ORA-13233 ORA-13233, 00000, “failed to create sequence number [%s] for R-tree” Cause: The specified sequence number exists. Action: Delete the sequence object, or contact Oracle Support Services. |
| ORA-13234 ORA-13234, 00000, “failed to access R-tree-index table [%s]” Cause: The index table is either deleted or corrupted. Action: Rebuild the index or contact Oracle Support Services with accompanying error messages. |
| ORA-13236 ORA-13236, 00000, “internal error in R-tree processing: [%s]” Cause: An internal error occurred in R-tree processing. Action: Contact Oracle Support Services with the message text. |
| ORA-13237 ORA-13237, 00000, “internal error during R-tree concurrent updates: [%s]” Cause: An inconsistency is encountered during concurrent updates, possibly due to the use of serializable isolation level. Action: Change the isolation level to “read committed” using the ALTER SESSION statement, or contact Oracle Support Services with the message text. |
| ORA-13239 ORA-13239, 00000, “sdo_dimensionality not specified during n-d R-tree creation” Cause: An error occurred in reading the dimensionality parameter Action: Check the documentation for a valid range, and specify the dimensionality as a parameter. |
| ORA-13240 ORA-13240, 00000, “specified dimensionality greater than that of the query mbr” Cause: An error occurred because of too few values in the query minimum bounding rectangle (MBR). Action: Omit the dimensionality, or use the dimensionality of the query. |
| ORA-13241 ORA-13241, 00000, “specified dimensionality does not match that of the data” Cause: An error occurred because the dimensionality specified in the CREATE INDEX statement does not match that of the data. Action: Change the statement to reflect the data dimensionality. |
| ORA-13243 ORA-13243, 00000, “specified operator is not supported for 3- or higher-dimensional R-tree” Cause: Currently, an R-tree index with three or more index dimensions can be used only with the SDO_FILTER operator. Action: Use the SDO_FILTER operator, and check the documentation for the querytype parameter for SDO_FILTER; or contact Oracle Support Services. |
| ORA-13249 ORA-13249, 00000, “%s” Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component. Action: Contact Oracle Support Services with the exact error text. |
| ORA-13250 ORA-13250, 00000, “insufficient privileges to modify metadata table entries” Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables. Action: Check that the specified feature and geometry table names are correct, and then verify that the current user has at least SELECT privilege on those tables. |
| ORA-13251 ORA-13251, 00000, “duplicate entry %s in metadata table” Cause: The specified entry already exists in the metadata table. Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once. |
| ORA-13260 ORA-13260, 00000, “layer table %s does not exist” Cause: Data migration source table <layer>_SDOGEOM does not exist. Action: Ensure that the specified layer name is correct and that the corresponding spatial layer tables exist in the current schema. |
| ORA-13261 ORA-13261, 00000, “geometry table %s does not exist” Cause: The specified geometry table does not exist in the current schema. Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values. |
| ORA-13262 ORA-13262, 00000, “geometry column %s does not exist in table %s” Cause: The specified table does not have a column of type SDO_GEOMETRY. Action: Alter or re-create the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER. |
| ORA-13263 ORA-13263, 00000, “column %s in table %s is not of type SDO_GEOMETRY” Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY. Action: Alter the column definition to be of type SDO_GEOMETRY. |
| ORA-13264 ORA-13264, 00000, “geometry identifier column %s does not exist in table %s” Cause: The specified table does not contain a GID column. Action: Confirm that the GID column name was correctly specified and that it exists in the specified table. |
| ORA-13265 ORA-13265, 00000, “geometry identifier column %s in table %s is not of type NUMBER” Cause: GID column is not of type NUMBER. Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER. |
| ORA-13266 ORA-13266, 00000, “error inserting data into table %s” Cause: An OCI error occurred, or the user has insufficient quota in the active tablespace, or the rollback segments are too small. Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem. |
| ORA-13267 ORA-13267, 00000, “error reading data from layer table %s” Cause: There was an error reading the geometry data from the <layer>_SDOGEOM table. Action: Verify that <layer>_SDOGEOM and <layer>_SDODIM exist. If they do exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer. |
| ORA-13268 ORA-13268, 00000, “error obtaining dimension from USER_SDO_GEOM_METADATA” Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified geometry table. Action: Insert an entry for the destination geometry table with the correct dimension information. |
| ORA-13269 ORA-13269, 00000, “internal error [%s] encountered when processing geometry table” Cause: An internal error occurred. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13270 ORA-13270, 00000, “OCI error \n%s” Cause: An OCI error occurred while processing the layer or geometry tables. Action: Take the appropriate steps to correct the OCI-specific error. |
| ORA-13271 ORA-13271, 00000, “error allocating memory for geometry object” Cause: Insufficient memory. Action: Make more memory available to the current session/process. |
| ORA-13272 ORA-13272, 00000, “geometric object %s in table %s is invalid” Cause: The specified object failed the geometric integrity checks performed by the validation function. Action: Check the Oracle Spatial documentation for information about the geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT and correct the geometry definition if required. |
| ORA-13273 ORA-13273, 00000, “dimension metadata table %s does not exist” Cause: The <layer>_SDODIM table does not exist. Action: Verify that the specified layer name is correct and that the <layer>_SDODIM table exists in the current schema. |
| ORA-13274 ORA-13274, 00000, “operator invoked with non-compatible SRIDs” Cause: A Spatial operator was invoked with a window geometry with an SRID but the layer has no SRID; or the window has no SRID but the layer has an SRID. Action: Make sure that the layer and window both have an SRID or that they both do not have an SRID. |
| ORA-13275 ORA-13275, 00000, “spatial index creation failure on unsupported type” Cause: An attempt was made to create a spatial index create on a column that is not of type SDO_GEOMETRY. Action: A spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column is of type SDO_GEOMETRY. |
| ORA-13276 ORA-13276, 00000, “internal error [%s] in coordinate transformation ” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13278 ORA-13278, 00000, “failure to convert SRID to native format” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13281 ORA-13281, 00000, “failure in execution of SQL statement to retrieve WKT” Cause: OCI internal error, or SRID does not match a table entry. Action: Check that a valid SRID is being used. |
| ORA-13282 ORA-13282, 00000, “failure on initialization of coordinate transformation” Cause: Parsing error on source or destination coordinate system WKT, or incompatible coordinate systems. Action: Check the validity of the WKT for table entries, and check if the requested transformation is valid. |
| ORA-13283 ORA-13283, 00000, “failure to get new geometry object for conversion in place” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13284 ORA-13284, 00000, “failure to copy geometry object for conversion in place” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13285 ORA-13285, 00000, “Geometry coordinate transformation error” Cause: A coordinate pair was out of valid range for a conversion/projection. Action: Check that data to be transformed is consistent with the desired conversion/projection. |
| ORA-13287 ORA-13287, 00000, “can’t transform unknown gtype” Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed. Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify a value whose last digit is 1 or higher. |
| ORA-13288 ORA-13288, 00000, “point coordinate transformation error” Cause: An internal error occurred while transforming points. Action: Check the accompanying error messages. |
| ORA-13290 ORA-13290, 00000, “the specified unit is not supported” Cause: An Oracle Spatial function was called with an unknown UNIT value. Action: Check Spatial documentation for the supported units, and call the function with the correct UNIT parameter. |
| ORA-13291 ORA-13291, 00000, “conversion error between the specified unit and standard unit” Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area. Action: Check the unit specification and respecify it. |
| ORA-13292 ORA-13292, 00000, “incorrect ARC_TOLERANCE specification” Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry. Action: Check ARC_TOLERANCE specification and make sure it is correct. |
| ORA-13293 ORA-13293, 00000, “cannot specify unit for geometry without a georeferenced SRID” Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID. Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs. |
| ORA-13294 ORA-13294, 00000, “cannot transform geometry containing circular arcs” Cause: It is impossible to transform a 3-point representation of a circular arc without distortion. Action: Make sure a geometry does not contain circular arcs. |
| ORA-13295 ORA-13295, 00000, “geometry objects are in different coordinate systems” Cause: An Oracle Spatial function was called with two geometries that have different SRIDs. Action: Transform geometry objects to be in the same coordinate system and call the spatial function. |
| ORA-13296 ORA-13296, 00000, “incorrect coordinate system specification” Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID. Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening. |
| ORA-13300 ORA-13300, 00000, “single point transform error” Cause: Low-level coordinate transformation error trap. Action: Check the accompanying error messages. |
| ORA-13303 ORA-13303, 00000, “failure to retrieve a geometry object from a table” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13304 ORA-13304, 00000, “failure to insert a transformed geometry object in a table” Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. |
| ORA-13330 ORA-13330, 00000, “invalid MASK” Cause: The MASK passed to the RELATE function is not valid. Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a list of supported masks. |
| ORA-13331 ORA-13331, 00000,”invalid LRS segment” Cause: The given LRS segment was not a valid line string. Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure) |
| ORA-13332 ORA-13332, 00000,”invalid LRS point” Cause: The specified LRS point was not a point geometry with measure information. Action: Check the given point geometry. A valid LRS point is a point geometry in Oracle Spatial with an additional dimension for measure. |
| ORA-13333 ORA-13333, 00000, “invalid LRS measure” Cause: The given measure for linear referencing was out of range. Action: Redefine the measure. |
| ORA-13334 ORA-13334, 00000, “LRS segments not connected” Cause: The specified geometric segments are not connected. Action: Check the start/end points of the given geometric segments. |
| ORA-13335 ORA-13335, 00000, “LRS measure information not defined” Cause: The measure information of a geometric segment was not assigned (IS NULL). Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null). |
| ORA-13336 ORA-13336, 00000, “failure in converting standard diminfo/geometry to LRS dim/geom” Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string. Action: Check if the diminfo dimensions are less than 3 or if the geometry type is point or line string. |
| ORA-13337 ORA-13337, 00000, “failure in concatenating LRS polygons” Cause: LRS concatenation involving LRS polygons is not supported. Action: Check the geometry and element types to make sure the concatenate operation is not called with a polygon type. |
| ORA-13338 ORA-13338, 00000, “failure in reversing LRS polygon/collection geometry” Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry. Action: Check the geometry type to make sure this operation is called on non-polygon geometries. |
| ORA-13339 ORA-13339, 00000, “LRS polygon clipping across multiple rings” Cause: Clipping (dynseg) a polygon across multiple rings is not allowed. Action: Polygon clipping is allowed only for a single ring. |
| ORA-13340 ORA-13340, 00000, “a point geometry has more than one coordinate” Cause: A geometry, specified as being a point, has more than one coordinate in its definition. Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition. |
| ORA-13341 ORA-13341, 00000, “a line geometry has fewer than two coordinates” Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition. Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| ORA-13342 ORA-13342, 00000, “an arc geometry has fewer than three coordinates” Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition. Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| ORA-13343 ORA-13343, 00000, “a polygon geometry has fewer than four coordinates” Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition. Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| ORA-13344 ORA-13344, 00000, “an arcpolygon geometry has fewer than five coordinates” Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition. Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| ORA-13345 ORA-13345, 00000, “a compound polygon geometry has fewer than five coordinates” Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition. Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| ORA-13346 ORA-13346, 00000, “the coordinates defining an arc are collinear” Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates. Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type. |
| ORA-13347 ORA-13347, 00000, “the coordinates defining an arc are not distinct” Cause: Two or more of the three points defining an arc are the same. Action: Alter the definition of the arc to ensure that three distinct coordinate values are used. |
| ORA-13348 ORA-13348, 00000, “polygon boundary is not closed” Cause: The boundary of a polygon does not close. Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry. |
| ORA-13349 ORA-13349, 00000, “polygon boundary crosses itself” Cause: The boundary of a polygon intersects itself. Action: Correct the geometric definition of the object. |
| ORA-13350 ORA-13350, 00000, “two or more rings of a complex polygon touch” Cause: The inner or outer rings of a complex polygon touch. Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object. |
| ORA-13351 ORA-13351, 00000, “two or more rings of a complex polygon overlap” Cause: The inner or outer rings of a complex polygon overlap. Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object. |
| ORA-13352 ORA-13352, 00000, “the coordinates do not describe a circle” Cause: The set of coordinates used to describe a circle are incorrect. Action: Confirm that the set of coordinates actually represent points on the circumference of a circle. |
| ORA-13353 ORA-13353, 00000, “ELEM_INFO_ARRAY not grouped in threes” Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected. Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3. |
| ORA-13354 ORA-13354, 00000, “incorrect offset in ELEM_INFO_ARRAY” Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY. Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY. |
| ORA-13355 ORA-13355, 00000, “SDO_ORDINATE_ARRAY not grouped by number of dimensions specified” Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user. Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY. |
| ORA-13356 ORA-13356, 00000, “adjacent points in a geometry are redundant” Cause: There are repeated points in the sequence of coordinates. Action: Remove the redundant point. |
| ORA-13357 ORA-13357, 00000, “extent type does not contain 2 points” Cause: Extent type should be represented by two points: lower left and upper right. Action: Confirm that there are only two points for an extent type. |
| ORA-13358 ORA-13358, 00000, “circle type does not contain 3 points” Cause: Circle type should be represented by three distinct points on the circumference. Action: Confirm that there are only three points for a circle type. |
| ORA-13359 ORA-13359, 00000, “extent does not have an area” Cause: The two points representing the extent are identical. Action: Confirm that the two points describing the extent type are distinct. |
| ORA-13360 ORA-13360, 00000, “invalid subtype in a compound type” Cause: This subtype is not allowed within the ETYPE specified. Action: Check the Oracle Spatial documentation for type definitions. |
| ORA-13361 ORA-13361, 00000, “not enough sub-elements within a compound ETYPE” Cause: The compound type declare more sub-elements than actually defined. Action: Confirm that the number of sub-elements is consistent with the compound type declaration. |
| ORA-13362 ORA-13362, 00000, “disjoint sub-element in a compound polygon” Cause: Compound polygon must describe an enclosed area. Action: Confirm that all sub-elements are connected. |
| ORA-13363 ORA-13363, 00000, “no valid ETYPE in the geometry” Cause: None of the ETYPEs within the geometry is supported. Action: Confirm that there is at least one valid ETYPE. |
| ORA-13364 ORA-13364, 00000, “layer dimensionality does not match geometry dimensions” Cause: The spatial layer has a geometry with a different dimensions than the dimensions specified for the layer. Action: Make sure that all geometries in a layer have the same dimensions and that they match the dimensions in the SDO_DIM_ARRAY object for the layer in the USER_SDO_GEOM_METADATA view. |
| ORA-13365 ORA-13365, 00000, “layer SRID does not match geometry SRID” Cause: The spatial layer has a geometry with a different SRID than the SRID specified for the layer. Action: Make sure that all geometries in a layer have the same SRID and that the SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view. |
| ORA-13366 ORA-13366, 00000, “invalid combination of interior exterior rings” Cause: In an Oracle Spatial geometry, interior and exterior rings are not used consistently. Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array. |
| ORA-13367 ORA-13367, 00000, “wrong orientation for interior/exterior rings” Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly. Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise. |
| ORA-13368 ORA-13368, 00000, “simple polygon type has more than one exterior ring” Cause: In a polygon geometry there is more than one exterior ring. Action: Set the type to be multipolygon if more than one exterior ring is present in the geometry. |
| ORA-13369 ORA-13369, 00000, “invalid value for etype in the 4-digit format” Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon. Action: Correct the geometry definition. |
| ORA-13370 ORA-13370, 00000, “failure in applying 3D LRS functions” Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions. Action: Check the geometry and element types and the SRID values. |
| ORA-13371 ORA-13371, 00000, “invalid position of measure dimension” Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array. Action: Check the geometry’s gtype and its position in the dim_info_array. |
| ORA-13372 ORA-13372, 00000, “failure in modifying metadata for a table with spatial index ” Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry’s gtype and diminfo. Action: Modify (or Prepare) metadata before creating an index on the SDO_GEOMETRY column. |
| ORA-13373 ORA-13373, 00000, “invalid line segment in geodetic data” Cause: A geodetic line segment was not less than half of a great circle. Action: Densify the line by adding points. |
| ORA-13374 ORA-13374, 00000, “SDO_MBR not supported for geodetic data” Cause: The SDO_MBR functionality is not supported for geodetic data. Action: Find an alternative function that can be used in this context. |
| ORA-13375 ORA-13375, 00000, “the layer is of type [%s] while geometry inserted has type [%s]” Cause: The layer has a type that is different or inconsistent with the type of the current geometry. Action: Change the geometry type to agree with the layer type, or change the layer type to agree with the geometry type. |
| ORA-13376 ORA-13376, 00000, “invalid type name specified for layer_gtype parameter” Cause: An invalid type name is specified for the layer_gtype constraint. Action: See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint. |
| ORA-13377 ORA-13377, 00000, “invalid combination of elements with orientation” Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4-digit etype). Action: Make sure all the polygon elements have orientation specified using the 4-digit etype notation. |
| ORA-13378 ORA-13378, 00000, “invalid index for element to be extracted” Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry. Action: Make sure the parameters to the extract function are in the valid range for the geometry. |
| ORA-13379 ORA-13379, 00000, “invalid index for sub-element to be extracted” Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry. Action: Make sure the parameters to the extract function are in the valid range for the geometry. |
| ORA-13380 ORA-13380, 00000, “network not found” Cause: The specified network was not found in the network metadata. Action: Insert the network information in the USER_SDO_NETWORK_METADATA view. |
| ORA-13381 ORA-13381, 00000, “table:%s not found in network:%s” Cause: The specified table was not found in the network metadata. Action: Insert the table information in the USER_SDO_NETWORK_METADATA view. |
| ORA-13382 ORA-13382, 00000, “geometry metadata (table:%s column:%s) not found in spatial network:%s” Cause: The specified geometry metadata was not found in the spatial network metadata. Action: Insert the spatial metadata information in the USER_SDO_NETWORK_METADATA view. |
| ORA-13383 ORA-13383, 00000, “inconsistent network metadata: %s” Cause: There was an inconsistency between the network metadata and the node/link information. Action: Check the network metadata and the node/link information. |
| ORA-13384 ORA-13384, 00000, “error in network schema: %s” Cause: The network table(s) did not have required column(s) Action: Check the network schema. |
| ORA-13385 ORA-13385, 00000, “error in network manager: [%s]” Cause: There was an internal error in network manager. Action: Contact Oracle Customer Support for more help. |
| ORA-13386 ORA-13386, 00000, “commit/rollback operation error: [%s]” Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation. Action: Correct the specified error and use the following statement: ALTER INDEX <index-name> PARAMETERS (‘index_status=synchronize’); |
| ORA-13387 ORA-13387, 00000, “sdo_batch_size for array inserts should be in the range [%d,%d]” Cause: The specified value for sdo_batch_size was too high or too low. Action: Change the value to be in the specified range. |
| ORA-13388 ORA-13388, 00000, “invalid value for dst_spec parameter” Cause: The dst_spec parameter was specified in the wrong format. Action: Check the documentation for this parameter. |
| ORA-13389 ORA-13389, 00000, “unable to compute buffers or intersections in analysis function” Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function. Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view before invoking the spatial analysis function. |
| ORA-13390 ORA-13390, 00000, “error in spatial analysis and mining function: [%s]” Cause: There was an internal error in the specified analysis function. Action: Contact Oracle Customer Support for more help. |
| ORA-13391 ORA-13391, 00000, “%s” Cause: An attempt was made to violate GeoRaster management restrictions. Action: Check the documentation for more detailed information. |
| ORA-13400 ORA-13400, 00000, “duplicate entry for %s in USER_SDO_GEOR_SYSDATA view” Cause: The current operation caused a duplicate RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view. Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view is unique. |
| ORA-13401 ORA-13401, 00000, “duplicate entry for %s in USER_SDO_GEOR_SYSDATA view” Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view. Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value pair is unique for each row. |
| ORA-13402 ORA-13402, 00000, “the rasterType is null or not supported” Cause: The specified rasterType was null or not supported. Action: Check the documentation for the rasterType number and/or formats supported by GeoRaster. |
| ORA-13403 ORA-13403, 00000, “invalid rasterDataTable specification: %s” Cause: Each GeoRaster object must have an associated raster data table whose name is unique among raster data table names in the database. If the GeoRaster object is not empty and not blank, the raster data table must exist, be visible in the current schema, be defined in the same schema as the GeoRaster data table, and be an object table of SDO_RASTER type. However, one or more of these requirements were not met. Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met. |
| ORA-13404 ORA-13404, 00000, “invalid ultCoordinate parameter” Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value. Action: Check the documentation, and make sure the ultCoordinate parameter is correct. |
| ORA-13405 ORA-13405, 00000, “null or invalid dimensionSize parameter” Cause: The dimensionSize array parameter was null, had the wrong length, or contained an invalid value. Action: Check the documentation, and make sure the dimensionSize parameter is correct. |
| ORA-13406 ORA-13406, 00000, “null or invalid GeoRaster object for output” Cause: The GeoRaster object for output was null or invalid. Action: Make sure the GeoRaster object for output has been initialized properly. |
| ORA-13407 ORA-13407, 00000, “invalid storage parameter%s” Cause: The storage parameter contained an invalid specification. Action: Check the documentation, and make sure the storage parameter is correct. |
| ORA-13408 ORA-13408, 00000, “invalid blockSize storage parameter” Cause: The blockSize storage parameter had the wrong length or contained invalid value. Action: Check the documentation, and make sure the blockSize storage parameter is correct. |
| ORA-13409 ORA-13409, 00000, “null or invalid pyramidLevel parameter” Cause: The specified pyramidLevel parameter was null or invalid. Action: Make sure the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object. |
| ORA-13410 ORA-13410, 00000, “invalid layerNumbers or bandNumbers parameter” Cause: The layerNumbers or bandNumbers parameter was invalid. Action: Check the documentation and make sure the layerNumbers or bandNumbers parameter is valid. |
| ORA-13411 ORA-13411, 00000, “subset results in null data set” Cause: The intersection of cropArea and source GeoRaster object was null. Action: Check the documentation, and make sure the cropArea parameter is correct. |
| ORA-13412 ORA-13412, 00000, “invalid scale parameter%s” Cause: The scale parameter contained an invalid specification. Action: Check the documentation, and make sure the scale parameter is correct. |
| ORA-13413 ORA-13413, 00000, “null or invalid resampling parameter” Cause: The resampling parameter was null or invalid. Action: Check the documentation, and make sure the resampling parameter is correct. |
| ORA-13414 ORA-13414, 00000, “invalid pyramid parameter” Cause: The pyramid parameter was invalid. Action: Check the documentation, and make sure the pyramid parameter is correct. |
| ORA-13415 ORA-13415, 00000, “invalid or out of scope point specification” Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber, colNumber, bandNumber> parameter combination was invalid or out of scope. Action: Make sure the parameter(s) specify a valid point that is or can be translated into a cell position inside the cell space of the GeoRaster object. |
| ORA-13416 ORA-13416, 00000, “invalid geometry parameter” Cause: The geometry parameter did not specify a valid single-point geometry. Action: Specify a valid single-point geometry. |
| ORA-13417 ORA-13417, 00000, “null or invalid layerNumber parameter” Cause: The layerNumber parameter was null or out of scope. Action: Specify a valid layerNumber parameter. |
| ORA-13418 ORA-13418, 00000, “null or invalid parameter(s) for set functions” Cause: A parameter for set metadata operations was null or invalid. Action: Check the documentation for information about the parameters. |
| ORA-13419 ORA-13419, 00000, “cannot perform mosaick operation on the specified table column” Cause: An attempt to perform a mosaick operation failed because the GeoRaster objects in the specified table column did not meet necessary conditions. Action: Check the documentation for SDO_GEOR.Mosaick for details. |
| ORA-13420 ORA-13420, 00000, “the SRID of the geometry parameter was not null” Cause: The input geometry must be in the GeoRaster cell space, which has a null SRID value. Action: Make sure the geometry parameter has a null SRID. |
| ORA-13421 ORA-13421, 00000, “NULL or invalid cell value” Cause: The cell value was NULL or out-of-scope. Action: Make sure the cell value is not NULL and is in the range as designated by the cellDepth definition of the specified GeoRaster object. |
| ORA-13422 ORA-13422, 00000, “invalid model coordinate parameter” Cause: The model coordinate array parameter had the wrong length or had null ordinate element(s). Action: Make sure the model coordinate parameter is valid. |
| ORA-13423 ORA-13423, 00000, “invalid cell coordinate parameter” Cause: The cell coordinate array parameter had the wrong length or had null ordinate element(s). Action: Make sure the cell coordinate parameter is valid. |
| ORA-13424 ORA-13424, 00000, “the GeoRaster object is not spatially referenced” Cause: The GeoRaster object was not spatially referenced. Action: Make sure the GeoRaster object is spatially referenced. |
| ORA-13425 ORA-13425, 00000, “invalid background filling value parameter” Cause: The background filling value parameter was invalid either because the array had the wrong size or because some of the element values were invalid. Action: Make sure the parameter that specifies the background filling value is valid. The size of the array must equal to either 1 (the value is for all bands) or the exact band dimension size. The element values must be valid cell values as determined by the cell depth. |
| ORA-13426 ORA-13426, 00000, “invalid window parameter” Cause: The specified window parameter was invalid. Action: Specify a valid window parameter. Check the documentation for details. |
| ORA-13427 ORA-13427, 00000, “invalid bitmap mask” Cause: The bitmap mask was not a valid 1BIT GeoRaster object, or it had the wrong dimension sizes. Action: Make sure the bitmap mask is a valid 1BIT GeoRaster object with only one band, and the row and column dimension sizes of the bitmap mask are the same as those of the target GeoRaster object. |
| ORA-13428 ORA-13428, 00000, “invalid modelCoordinateLocation” Cause: The program [or user] specified a modelCoordinateLocation that is not supported, or the modelCoordinateLocation of the GeoRaster object was wrong. Action: Set or specify the modelCoordinateLocation to be CENTER (0) or UPPERLEFT (1). |
| ORA-13429 ORA-13429, 00000, “invalid xCoefficients or yCoefficients parameter(s)” Cause: An attempt to perform a georeference operation failed. Possible reasons include xCoefficients or yCoefficients having the wrong number of coefficients or invalid coefficients. Action: Check the documentation for supported coefficient specifications. |
| ORA-13430 ORA-13430, 00000, “the GeoRaster object has null attribute(s)” Cause: The metadata or rasterType of the GeoRaster object was null. Action: This object may only be used as an output parameter of procedures or functions. It is not valid for other purposes. |
| ORA-13431 ORA-13431, 00000, “GeoRaster metadata rasterType error” Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute. Action: Make sure the rasterType in the metadata of the GeoRaster object and the GeoRaster rasterType attribute have the same value. |
| ORA-13432 ORA-13432, 00000, “NULL or invalid blankCellValue” Cause: The blankCellValue element could not be found in the metadata of a blank GeoRaster object, or the specified blankCellValue element value was NULL or invalid. Action: Call SDO_GEOR.setBlankCellValue to add blankCellValue to the metadata whenever the isBlank element value is TRUE, and make sure that the specified blankCellValue element value is not NULL and is in the range as designated by the cellDepth definition of the GeoRaster object. |
| ORA-13433 ORA-13433, 00000, “GeoRaster metadata default RGB error” Cause: At least one of the defaultRed, defaultGreen, and defaultBlue values (logical layer numbers) was zero, negative, or out of range. Action: Check the documentation for details. |
| ORA-13434 ORA-13434, 00000, “GeoRaster metadata cellRepresentation error” Cause: The cellRepresentation type was not supported. Action: Check the documentation for supported cellRepresentation types. |
| ORA-13435 ORA-13435, 00000, “GeoRaster metadata dimension inconsistent” Cause: The specification of dimensions or totalDimensions was inconsistent with rasterType, or vice versa. Action: Make sure dimension specifications are consistent. |
| ORA-13436 ORA-13436, 00000, “GeoRaster metadata dimensionSize error” Cause: Either the dimensionSize for each dimension was not specified, or an extraneous dimensionSize was specified. Action: Add a dimsenionSize for each dimension of the GeoRaster object and delete extra dimensionSize elements. |
| ORA-13437 ORA-13437, 00000, “GeoRaster metadata blocking error” Cause: Either the wrong block number(s) or block size(s) along dimensions were specified, or the block numbers and sizes when taken together were not consistent. Action: Check the documentation for details. |
| ORA-13438 ORA-13438, 00000, “GeoRaster metadata pyramid type error” Cause: The specified pyramid type was not supported. Action: Check the documentation for supported pyramid types. |
| ORA-13439 ORA-13439, 00000, “GeoRaster metadata pyramid maxLevel error” Cause: The specified maxLevel exceeded the maximum level allowed by the specified pyramid type. Action: Check the documentation for supported pyramid types and their total level limitations. |
| ORA-13440 ORA-13440, 00000, “GeoRaster metadata compression type error” Cause: The specified compression type was not supported. Action: Check the documentation for supported compression types. |
| ORA-13441 ORA-13441, 00000, “GeoRaster metadata SRS error: %s” Cause: The specified error relates to the polynomialModel element in the Spatial Reference System (SRS) metadata. Action: Check the documentation and make sure that a valid polynomial model is specified. |
| ORA-13442 ORA-13442, 00000, “GeoRaster object not registered: %s” Cause: There was no sysdata entry for the specified GeoRaster object. Action: Make sure that a sysdata entry has been inserted for the specified GeoRaster object. |
| ORA-13443 ORA-13443, 00000, “null or invalid values in %s” Cause: There were null or invalid component values in the specified metadata. Action: Check the documentation and make sure that all the component values are valid. |
| ORA-13444 ORA-13444, 00000, “cannot perform mergeLayers operation” Cause: The two GeoRaster objects whose layers are to be combined together either had different row or column dimension sizes, or their georeferencing information did not match. Action: Make sure the objects have the same row and column dimension sizes. If neither is georeferenced, their ULTCoordinate values must be the same. Otherwise, they must be both georeferenced and cover the same area in the model space. |
| ORA-13445 ORA-13445, 00000, “NULL or invalid NODATA value or value range” Cause: There was invalid NODATA value or value range in the metadata, or the specified NODATA value or value range was invalid. Action: Make sure the NODATA value or value range is not NULL and is completely contained in the range as designated by the cellDepth definition of the specified GeoRaster object. |
| ORA-13446 ORA-13446, 00000, “GeoRaster metadata TRS error” Cause: The GeoRaster Temporal Reference System was not supported. Action: Set isReferenced to FALSE. |
| ORA-13447 ORA-13447, 00000, “GeoRaster metadata BRS error” Cause: The GeoRaster Band Reference System was not supported. Action: Set isReferenced to FALSE. |
| ORA-13448 ORA-13448, 00000, “GeoRaster metadata BRS error” Cause: The GeoRaster spectral extent specification was incorrect. Action: The MIN value must be less than the MAX value in the spectralExtent element. |
| ORA-13449 ORA-13449, 00000, “GeoRaster metadata ULTCoordinate error” Cause: The GeoRaster rasterInfo ULTCoordinate was not correct. Action: Check the documentation for restrictions. |
| ORA-13450 ORA-13450, 00000, “GeoRaster metadata layerInfo error” Cause: The GeoRaster had more than one layerInfo element, or the layerDimension value was not supported. Action: The current release only supports one layerInfo element; layer can only be defined along one dimension, and this dimension must be BAND. |
| ORA-13451 ORA-13451, 00000, “GeoRaster metadata scaling function error” Cause: The scaling function had a zero denominator. Action: Make sure the scaling function denominator is not zero. |
| ORA-13452 ORA-13452, 00000, “GeoRaster metadata BIN function error” Cause: The bin function data did not match its type. Action: For EXPLICIT type, provide a binTableName element; otherwise, provide a binFunctionData element. |
| ORA-13453 ORA-13453, 00000, “GeoRaster metadata layer error” Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber or layerDimensionOrdinate was not assigned correctly. Action: The total number of logical layers cannot exceed the total number of physical layers, and each logical layer must be assigned a valid physical layer number following the same order. Check the documentation for more details. |
| ORA-13454 ORA-13454, 00000, “GeoRaster metadata is invalid” Cause: The GeoRaster metadata was invalid against its XML Schema. Action: Run the schemaValidate routine to find the errors. |
| ORA-13455 ORA-13455, 00000, “GeoRaster metadata TRS error” Cause: The beginDateTime value was later than the endDateTime value. Action: Make sure that the beginDateTime value is not later than the endDateTime value. |
| ORA-13456 ORA-13456, 00000, “GeoRaster cell data error: %s” Cause: There was an error in the original GeoRaster cell data or in the cell data of the pyramids. Action: If the error is related to the original GeoRaster cell data, the GeoRaster object is invalid and has to be deleted or manually repaired. If the error is related to pyramids, delete the pyramids and regenerate them. |
| ORA-13457 ORA-13457, 00000, “bitmap mask cell data error: %s” Cause: There was an error in the cell data of an original bitmap mask or in the cell data of the pyramids of a bitmap mask. Action: If the error is related to an original bitmap mask, remove the bitmap mask. If the error is related to the pyramids of a bitmap mask, delete the pyramids and regenerate them. |
| ORA-13458 ORA-13458, 00000, “GeoRaster metadata SRS error” Cause: The polynomial model did not match the requirements of a rectified GeoRaster object. Action: Check the documentation for the requirements of the polynomial model for a rectified GeoRaster object, or set isRectified to be false. |
| ORA-13459 ORA-13459, 00000, “GeoRaster metadata SRS error” Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid. Action: Check the documentation and make sure the polynomial model is a valid six-parameter affine transformation. |
| ORA-13460 ORA-13460, 00000, “GeoRaster metadata SRS error” Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero. Action: Set or specify the model space SRID to be a nonzero number. |
| ORA-13461 ORA-13461, 00000, “the interleaving type is not supported” Cause: The interleaving type of the GeoRaster object was not supported. Action: Check the documentation for the interleaving types supported by GeoRaster. Use SDO_GEOR.changeFormatCopy to transform the image to a supported interleaving type. |
| ORA-13462 ORA-13462, 00000, “invalid blocking specification” Cause: The specified blocking configuration was invalid. Action: Check the documentation for the blocking specification supported by GeoRaster. |
| ORA-13463 ORA-13463, 00000, “error retrieving GeoRaster data: %s” Cause: An internal error occurred while retrieving GeoRaster data from the database. Action: Check the error message for details. |
| ORA-13464 ORA-13464, 00000, “error loading GeoRaster data: %s” Cause: An internal error occurred while loading GeoRaster data into the database. Action: Check the error message for details. |
| ORA-13465 ORA-13465, 00000, “null or invalid table or column specification” Cause: The specified table or column did not exist, or the column was not a GeoRaster column. Action: Make sure the specified table exists and the specified column is a GeoRaster column. |
| ORA-13466 ORA-13466, 00000, “format not appropriate for specified compression method: %s” Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported for the specified compression. Action: Check the error message for details. Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormatCopy to transform the GeoRaster object to an appropriate format, or apply another compression method. |
| ORA-13467 ORA-13467, 00000, “unsupported GeoRaster metadata specification: %s” Cause: The GeoRaster metadata specification is not supported. Action: Check the documentation for the supported GeoRaster metadata specifications. |
| ORA-13468 ORA-13468, 00000, “invalid blockMBR” Cause: Invalid blockMBR geometries were stored in the raster data table. Action: Make sure the blockMBR geometries stored in the raster data table are valid, or call SDO_GEOR.generateBlockMBR() to regenerate the blockMBR geometries. |
| ORA-13469 ORA-13469, 00000, “cannot perform updateRaster operation” Cause: The data of the source GeoRaster object could not be used to update that of the target GeoRaster object. Action: Make sure the source and the target GeoRaster objects have the same cell depth, and that both objects are either georeferenced or not georeferenced at all. If both are georeferenced, they should be in the same coordinate system and have the same spatial resolutions. |
| ORA-13470 ORA-13470, 00000, “target and source layers or bands mismatched” Cause: The number of specified target layers or bands and source layers or bands did not match. Action: When updating layers or bands of a target GeoRaster object to reflect the associated layers or bands of the source GeoRaster object, specify the same number of layers or bands for both the source and the target objects. Check the documentation for details. |
| ORA-13471 ORA-13471, 00000, “unable to determine the owner of %s” Cause: The owner of the specified raster data table could not be determined. Action: Make sure the GeoRaster object that refers to the raster data table has been registered by inserting the object into a GeoRaster table. |
| ORA-13472 ORA-13472, 00000, “invalid geometry parameter” Cause: The geometry parameter did not specify a valid geometry. Action: Specify a valid 2D or 3D geometry. If the model SRID is null or indicates a 2D coordinate system, the geometry must be 2D. If the model SRID indicates a 3D coordinate system, the geometry must either be a 3D geometry or a 2D geometry that can be converted to 3D with the specified vertical axis (or vertical SRID) and ellipsoidal parameters. |
| ORA-13473 ORA-13473, 00000, “invalid rasterSpec parameter” Cause: The rasterSpec parameter contained an invalid specification. Action: Check the documentation and make sure the rasterSpec parameter contains only valid keywords and values. |
| ORA-13474 ORA-13474, 00000, “invalid rasterDataTable name: %s” Cause: The rasterDataTable name was not a valid nonquoted identifier, it contained a period separator, or not all of the alphanumeric characters were uppercase. Action: Ensure that the table name is a valid nonquoted identifier without any period separators, and that all the alphanumeric characters are uppercase. |
| ORA-13475 ORA-13475, 00000, “invalid GeoRaster object for output” Cause: The output GeoRaster object had the same RASTER_DATA_TABLE and RASTER_ID combination as that of an input GeoRaster object. Action: Ensure that the output GeoRaster object is different from any of the input GeoRaster objects. |
| ORA-13476 ORA-13476, 00000, “invalid or out of scope point specification” Cause: The point position specified by the point geometry parameter or the rowNumber/colNumber parameter combination was null or out of scope. Action: Ensure that the parameters specify a valid point that translates or can be translated into a cell position inside the cell space of the GeoRaster object. |
| ORA-13480 ORA-13480, 00000, “the Source Type is not supported” Cause: The specified source type was not supported. Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster. |
| ORA-13481 ORA-13481, 00000, “the destination type is not supported” Cause: The specified destination type was not supported. Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster. |
| ORA-13482 ORA-13482, 00000, “GeoRaster object is not initialized for the image” Cause: No GeoRaster object has been initialized for the specified image. Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details. |
| ORA-13483 ORA-13483, 00000, “insufficient memory for the specified GeoRaster data” Cause: There was insufficient memory to hold the specified GeoRaster data for this operation. Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details. |
| ORA-13484 ORA-13484, 00000, “the file format or compression type is not supported: %s” Cause: The file format or compression type was not supported. Action: Check the documentation for formats that are currently supported by GeoRaster. |
| ORA-13485 ORA-13485, 00000, “error occurred during compression or decompression: %s” Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details. Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation. |
| ORA-13486 ORA-13486, 00000, “invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: %s” Cause: The GeoTIFF metadata of the specified input image contained invalid or insufficient information to georeference the GeoRaster object. Action: Check the error message for details. |
| ORA-13487 ORA-13487, 00000, “SRID not found for source coordinate system metadata” Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the source coordinate system metadata. Action: Add a user-defined coordinate reference system for this coordinate system, as explained in the Oracle Spatial documentation. |
| ORA-13497 ORA-13497, 00000, “%s” Cause: This is an internal GeoRaster error. Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so. |
| ORA-13498 ORA-13498, 00000, “%s” Cause: An error related to an external plugin was encountered in the GeoRaster component. Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text. |
| ORA-13499 ORA-13499, 00000, “%s” Cause: This is an internal Spatial error. Action: Contact Oracle Support Services. |
| ORA-13500 ORA-13500, 00000, “SYSAUX DATAFILE clause specified more than once” Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause. Action: Specify at most one SYSAUX DATAFILE clause. |
| ORA-13501 ORA-13501, 00000, “Cannot drop SYSAUX tablespace” Cause: Tried to drop SYSAUX tablespace Action: None |
| ORA-13502 ORA-13502, 00000, “Cannot rename SYSAUX tablespace” Cause: An attempt to rename the SYSAUX tablespace failed. Action: No action required. |
| ORA-13503 ORA-13503, 00000, “Creating SYSAUX tablespace with invalid attributes” Cause: An attempt to create the SYSAUX tablespace with invalid attributes. Action: Create SYSAUX tablespace with ONLINE, PERMANENT, EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO attributes. |
| ORA-13504 ORA-13504, 00000, “No SYSAUX datafile clause specified” Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to be specified, unless using OMF. Action: Specify the SYSAUX datafile clause. |
| ORA-13505 ORA-13505, 00000, “SYSAUX tablespace can not be made read only” Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX tablespace must remain read write for database operation. Action: Leave SYSAUX tablespace read write. |
| ORA-13506 ORA-13506, 00000, “operation failed due to invalid snapshot range (%s, %s)” Cause: An attempt was made to perform operation with an invalid Start/End Snapshot Pair. Action: Choose a valid Start/End Snapshot Pair. |
| ORA-13507 ORA-13507, 00000, “Event for Testing SYSAUX occupant view” Document: NO Cause: Action: Display the test SYSAUX occupant in the V$SYSAUX_OCCUPANT view |
| ORA-13508 ORA-13508, 00000, “Event to update INTERVAL and RETENTION in number of seconds” Document: NO Cause: Action: |
| ORA-13509 ORA-13509, 00000, “error encountered during updates to a AWR table” Cause: An update error occurred during OCI operation due to an underlying error. Action: Check associated OCI error. Correct problem and retry the operation. |
| ORA-13510 ORA-13510, 00000, “invalid RETENTION %s, must be in the range (%s, %s)” Cause: The user has specified a RETENTION setting that is not in the supported range of (MIN, MAX). Action: Choose a valid RETENTION setting and retry the operation. |
| ORA-13511 ORA-13511, 00000, “invalid INTERVAL %s, must be in the range (%s, %s)” Cause: The user has specified a INTERVAL setting that is not in the supported range of (MIN, MAX). Action: Choose a valid INTERVAL setting and retry the operation. |
| ORA-13512 ORA-13512, 00000, “event #1 to test the top Segment Statistics” Document: NO Cause: Action: will compute the top 10 segments based on logical reads. |
| ORA-13513 ORA-13513, 00000, “event #2 to test the top Segment Statistics” Document: NO Cause: Action: will compute the top 5 segments for logical reads and wait count. |
| ORA-13514 ORA-13514, 00000, “Metric Capture too close to last capture, group %s” Cause: The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second). Action: add some delay and reissue command to retry. |
| ORA-13515 ORA-13515, 00000, “Error encountered during Database Usage Statistics capture” Cause: Error occurred during OCI operation due to underlying error. Action: Check associated OCI error. Correct problem and retry the operation. |
| ORA-13516 ORA-13516, 00000, “AWR Operation failed: %s” Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode. Action: check the above conditions and retry the operation. |
| ORA-13517 ORA-13517, 00000, “Baseline (id = %s) does not exist” Cause: The operation failed because the specified baseline ID does not exist in the Workload Repository. Action: check the baseline id and retry the operation. |
| ORA-13518 ORA-13518, 00000, “Invalid database id (%s)” Cause: The operation failed because the specified database ID does not exist in the Workload Repository. Action: check the database id and retry the operation. |
| ORA-13519 ORA-13519, 00000, “Database id (%s) exists in the workload repository” Cause: The operation failed because the specified database ID already exists in the Workload Repository. Action: check the database id and retry the operation. |
| ORA-13520 ORA-13520, 00000, “Database id (%s) not registered, Status = %s” Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly. Action: check the status of database id and retry the operation. |
| ORA-13521 ORA-13521, 00000, “Unregister operation on local Database id (%s) not allowed” Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository. Action: check the database id and retry the operation. |
| ORA-13522 ORA-13522, 00000, “event to toggle checking for duplicate sql id (num)” Document: NO Cause: Action: Event will determine whether to filter out duplicates for Top SQL selection. |
| ORA-13523 ORA-13523, 00000, “unable to allocate required space for return type” Cause: Out of memory to allocate the space for the return variable for an external procedure. Action: Try operation again. |
| ORA-13524 ORA-13524, 00000, “error encountered while retrieving baseline information” Cause: A read error occurred during the OCI operation to retrieve the baseline information Action: Check associated error. Correct problem and retry the operation. |
| ORA-13525 ORA-13525, 00000, “error with computing space usage for sysaux occupant” Cause: Error occurred during OCI operation due to underlying error. Action: Check associated OCI error. Correct problem and retry the operation. |
| ORA-13526 ORA-13526, 00000, “baseline (%s) does not exist” Cause: The operation failed because the specified baseline name does not exist in the Workload Repository. Action: check the baseline name and retry the operation. |
| ORA-13527 ORA-13527, 00000, “invalid baseline name” Cause: The operation failed because the specified baseline name is invalid. Action: check the baseline name and retry the operation. |
| ORA-13528 ORA-13528, 00000, “name (%s) is already used by an existing baseline” Cause: The operation failed because the specified baseline name already exists in the Workload Repository. Action: check the baseline name and retry the operation. |
| ORA-13529 ORA-13529, 00000, “Error occurred when flushing AWR table group” Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table. Action: Check the error associated with the table group. |
| ORA-13530 ORA-13530, 00000, “invalid TOPNSQL %s, must be in the range (%s, %s)” Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX). Action: Choose a valid TOPNSQL setting and retry the operation. |
| ORA-13531 ORA-13531, 00000, “SQL Text was purged from AWR before the operation completed” Cause: A SQL was purged from AWR before the operation completed. Action: Retry the operation. |
| ORA-13532 ORA-13532, 00000, “SQL ID [%s] already exists” Cause: The operation failed because the specified SQL ID already existed in the repository. Action: Check the SQL ID and retry the operation. |
| ORA-13533 ORA-13533, 00000, “invalid SQL ID” Cause: The operation failed because the specified SQL ID was invalid. Action: Check the SQL ID and retry the operation. |
| ORA-13534 ORA-13534, 00000, “Current SQL count(%s) reached maximum allowed (%s)” Cause: The operation failed because the maximum allowed colored SQL was exceeded. Action: Check the count for colored SQL. |
| ORA-13535 ORA-13535, 00000, “name (%s) is already used by an existing baseline template” Cause: The operation failed because the specified baseline template name already existed in the Workload Repository. Action: Check the baseline template name and retry the operation. |
| ORA-13536 ORA-13536, 00000, “baseline template (%s) does not exist” Cause: The operation failed because the specified baseline template name did not exist in the Workload Repository. Action: Check the baseline template name and retry the operation. |
| ORA-13537 ORA-13537, 00000, “invalid input for create baseline template (%s, %s)” Cause: Invalid input was specified for the create baseline template routine. Action: Check the argument displayed in the error message text. |
| ORA-13538 ORA-13538, 00000, “invalid value for baseline expiration (%s)” Cause: An invalid value was specified for the expiration of a baseline. The expiration is specified in number of days, and the expiration must be at least one day. Action: Check the value for expiration. |
| ORA-13539 ORA-13539, 00000, “invalid input for modify baseline window size (%s, %s)” Cause: Invalid input was specified for the modify baseline window size routine. Action: Check the argument displayed in the error message text. |
| ORA-13540 ORA-13540, 00000, “operation not allowed on system moving window baseline (%s)” Cause: The requested operation was not allowed on the system moving window baseline. Action: Retry the operation with another baseline name. |
| ORA-13541 ORA-13541, 00000, “system moving window baseline size (%s) greater than retention (%s)” Cause: The system moving window baseline size must be less than the retention setting. The specified window size or retention violate this. Action: Check the moving window baseline size or retention. |
| ORA-13542 ORA-13542, 00000, “baseline ID (%s) does not exist” Cause: The operation failed because the specified baseline ID did not exist in the Workload Repository. Action: Check the baseline ID and retry the operation. |
| ORA-13543 ORA-13543, 00000, “error encountered while retrieving baseline template information” Cause: A read error occurred during the OCI operation to retrieve the baseline template information. Action: Check associated error. Correct problem and retry the operation. |
| ORA-13544 ORA-13544, 00000, “error encountered while automatically generating a baseline” Cause: An error occurred while automatically generating a baseline based on the template information. Action: Look in the trace file for more error information. |
| ORA-13545 ORA-13545, 00000, “invalid baseline template name” Cause: The operation failed because the specified baseline template name was an invalid identifier. Action: Check the baseline template name and retry the operation. |
| ORA-13546 ORA-13546, 00000, “Error encountered during maintenance of Adaptive Thresholds” Cause: Error occurred during OCI operation due to underlying error. Action: Check associated OCI error. Correct problem and retry the operation. |
| ORA-13547 ORA-13547, 00000, “Unable to drop baseline since it is in use by %s” Cause: The system is not able to drop the baseline since the baseline is in use by a functionality that depends on its existence. Action: Note the name of the functionality using the baseline, and check if the functionality still needs the baseline. |
| ORA-13548 ORA-13548, 00000, “Unable to find valid snapshot IDs for the inputted baseline time range” Cause: The system is not able to find valid snapshot IDs for the inputted time range while attempting to create a baseline. Action: Check that the inputted time range has at least two valid snapshots. The dba_hist_snapshot displays the snapshot id and time information. |
| ORA-13549 ORA-13549, 00000, “invalid input for create baseline with time range (%s)” Cause: Invalid time input was specified for the create baseline routine. Action: Check the argument displayed in the error message text. |
| ORA-13600 ORA-13600, 00000, “error encountered in Advisor\n%s” Cause: An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error. Action: See the Advisor documentation for an explanation of the second error message. |
| ORA-13601 ORA-13601, 00000, “The specified Advisor %s does not exist.” Cause: The user specified an advisor name that has not be defined in the advisor repository. Action: Correct the advisor name and retry the operation. |
| ORA-13602 ORA-13602, 00000, “The specified parameter %s is not valid for task or object %s.” Cause: The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not supported by the particular advisor. Action: Validate the parameter name and retry the operation. |
| ORA-13603 ORA-13603, 00000, “The specified parameter %s cannot be fetched as a numeric value for task or object %s.” Cause: The user attempted to retrieve a string parameter as a numeric value. Action: Check the datatype for the task parameter and retry the operation. |
| ORA-13604 ORA-13604, 00000, “The specified parameter %s cannot be fetched as a SQL table.” Cause: The user attempted to retrieve a non-table parameter as a table name. Action: Check the datatype for the task parameter and retry the operation. |
| ORA-13605 ORA-13605, 00000, “The specified task or object %s does not exist for the current user.” Cause: The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository. Action: Adjust the name and retry the operation. |
| ORA-13606 ORA-13606, 00000, “the specified task parameter element %s is out of range for parameter %s.” Cause: The user attempted to reference an invalid parameter element. Action: Adjust the element offset and retry the operation. |
| ORA-13607 ORA-13607, 00000, “The specified task or object %s already exists” Cause: The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user. Action: Adjust the name and retry the operation. |
| ORA-13608 ORA-13608, 00000, “The specified name %s is invalid.” Cause: An attempt was made to specify a name for a task, object, execution or directive instance, which contained invalid characters or an invalid wildcard specifier. Action: Adjust the name and retry the operation. |
| ORA-13609 ORA-13609, 00000, “The specified task %s must be executing to be cancelled or interrupted.” Cause: The user attempted to cancel or interrupt a task that is not currently executing. Action: Check the status of the task and retry the operation. |
| ORA-13610 ORA-13610, 00000, “The directive %s does not exist for task %s.” Cause: The user attempted to access a task directive that does not exist. Action: Validate the directive and retry the operation. |
| ORA-13611 ORA-13611, 00000, “The command %s is not a valid advisor command.” Cause: The user attempted to specify a command that does not exist. Action: Validate the command and retry the operation. |
| ORA-13612 ORA-13612, 00000, “The recommendation action %s,%s is not valid for task %s.” Cause: The user attempted to access a recommendation action that does not exist in the task. Action: Validate the recommendation-action and retry the operation. |
| ORA-13613 ORA-13613, 00000, “The requested operation is not supported for this advisor object.” Cause: The user attempted to perform an operation that is not supported for the particular advisor or task type. Action: Validate the task or object and retry the operation. |
| ORA-13614 ORA-13614, 00000, “The template %s is not compatible with the current advisor.” Cause: The user attempted to create a new task or object using an existing task or object that was not created by the same advisor. Action: Validate the template and retry the operation. |
| ORA-13615 ORA-13615, 00000, “The task or object %s is greater than the maximum allowable length of 30 characters.” Cause: The user attempted to create a new task or object using a name that is too long. Action: Shorten the name and retry the operation. |
| ORA-13616 ORA-13616, 00000, “The current user %s has not been granted the ADVISOR privilege.” Cause: The user attempted an advisor operation that requires privilege. Action: Adjust the user’s privileges and retry the operation. |
| ORA-13617 ORA-13617, 00000, “The specified task %s already executing” Cause: The user attempted to execute a task that is currently executing. Action: Wait for the task to finish before attempting any further task activities. |
| ORA-13618 ORA-13618, 00000, “The specified value is not a valid value for procedure argument %s.” Cause: The user executed a procedure but failed to provide correct values for the argument. Action: Correct the procedure arguments and retry the operation. |
| ORA-13619 ORA-13619, 00000, “The procedure argument %s is greater than the maximum allowable length of %s characters.” Cause: The user attempted to pass a character argument that is too long. Action: Shorten the specified character argument and retry the operation. |
| ORA-13620 ORA-13620, 00000, “The task or object %s is read-only and cannot be deleted or modified.” Cause: The user attempted to perform an operation that will update or delete a read-only task or object. Action: Adjust the READ_ONLY property for the object and retry the operation. |
| ORA-13621 ORA-13621, 00000, “The task_or object %s is marked as a template and cannot perform the requested operation.” Cause: The user attempted perform an unsupported operation on a task or object that is identified as a template. Action: Choose a different object and retry the operation. |
| ORA-13622 ORA-13622, 00000, “invalid recommendation annotation” Cause: The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE. Action: Correct the action and retry the operation. |
| ORA-13623 ORA-13623, 00000, “The recommendation %s is not valid for task %s.” Cause: The user attempted to access a recommendation that does not exist in the task. Action: Validate the recommendation and retry the operation. |
| ORA-13624 ORA-13624, 00000, “The task %s is executing and cannot be deleted or modified.” Cause: The user attempted to access a task that currently executing. Action: Wait for the task to complete and retry the operation. |
| ORA-13625 ORA-13625, 00000, “%s is an invalid advisor object type.” Cause: The user has specified an invlaid object type. Action: Refre to dba_advisor_object_types for all valid object types |
| ORA-13626 ORA-13626, 00000, “The specified object %s is not valid for task %s.” Cause: The user specified an non-existent object for the task Action: Choose a different object and retry the operation. |
| ORA-13627 ORA-13627, 00000, “Setting of parameter %s is disallowed until the task is reset.” Cause: The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset. Action: Reset the task and retry the operation. |
| ORA-13628 ORA-13628, 00000, “Insufficient privileges to access the task belonging to the specified user” Cause: The user could not access dba_* views. Action: Retry operation as owner of the task or after granting new privileges. |
| ORA-13629 ORA-13629, 00000, “The task or object %s is being used by another operation.” Cause: The user attempted to access a task or object that is locked by another session. Action: Wait for the task or object activity to complete and retry the operation. |
| ORA-13630 ORA-13630, 00000, “The task %s contains execution results and cannot be executed.” Cause: The user attempted to execute a task that already contains execution results. Action: Reset the task to its initial state and retry the operation. |
| ORA-13631 ORA-13631, 00000, “The most recent execution of task %s contains no results.” Cause: The user attempted to create a report or script from a task that has not successfully completed an execution. Action: Execute the task and then retry the operation |
| ORA-13632 ORA-13632, 00000, “The user cancelled the current operation.” Cause: The user signaled a cancel during a task or object operation. Action: None |
| ORA-13633 ORA-13633, 00000, “The task %s was interrupted and needs to be resumed.” Cause: The user attempted to execute a task that was interrupted. Action: Resume the execution of the task via the RESUME_TASK API. |
| ORA-13634 ORA-13634, 00000, “The task %s needs to be reset before being re-executed.” Cause: The task must be in an inital state to be executed. Action: Reset the task to its initial state and retry the operation. |
| ORA-13635 ORA-13635, 00000, “The value provided for parameter %s cannot be converted to a number.” Cause: A numeric parameter was incorrectly supplied in string form. Action: Retry by supplying valid numeric value. |
| ORA-13636 ORA-13636, 00000, “The specified value provided for parameter %s is not valid for this advisor.” Cause: The user supplied an invalid parameter value. Action: Retry by supplying valid value. |
| ORA-13637 ORA-13637, 00000, “Executing or modifying task %s is disallowed until the task is reset to its initial state.” Cause: The user attempted to execute or modify the task that is in not in its INITIAL state. Action: Reset the task and retry the operation. |
| ORA-13638 ORA-13638, 00000, “The user interrupted the current operation.” Cause: The user signaled an interrupt during a task or object operation. Action: None |
| ORA-13639 ORA-13639, 00000, “The current operation was interrupted because it timed out.” Cause: The task or object operation timed out. Action: None |
| ORA-13640 ORA-13640, 00000, “The current operation was cancelled because it timed out, and was not in interruptible mode.” Cause: The task or object operation timed out. Action: None |
| ORA-13641 ORA-13641, 00000, “Task cannot be interrupted yet. You may cancel it instead.” Cause: The user attempted to interrupt a task that has not reached interruptible mode. Action: Wait until the task reaches interruptible mode, or cancel the task execution. |
| ORA-13642 ORA-13642, 00000, “The specified string %s provided for %s cannot be converted to a date. The acceptable date format is %s.” Cause: The user supplied a date value in an incorrect format. Action: Retry by supplying valid value. |
| ORA-13643 ORA-13643, 00000, “The task can not be interrupted or cancelled.” |
| ORA-13644 ORA-13644, 00000, “The user \”%s\” is invalid.” Cause: Invalid user name specified to advisor framework Action: User should specify a correct, case-sensitive, name |
| ORA-13645 ORA-13645, 00000, “The specified execution %s does not exist for this task.” Cause: You attempted to reference an advisor task execution using a name that did not exist. Action: Adjust the name and retry the operation. |
| ORA-13646 ORA-13646, 00000, “The specified execution %s already exists” Cause: You attempted to perform a new execution using a name that already exists for the specified task. Execution names must be unique within the same task. Action: Adjust the name and retry the operation. |
| ORA-13647 ORA-13647, 00000, “Setting of parameter %s is disallowed during task execution.” Cause: You attempted to set the value of a parameter while the task was being executed. This parameter cannot be changed until the task finishes its execution. Action: Verify the status of the task and retry the operation. |
| ORA-13648 ORA-13648, 00000, “The specified execution type does not exist for this advisor.” Cause: You attempted to use an advisor task execution type using a name that did not exist. Action: Adjust the name and retry the operation. |
| ORA-13649 ORA-13649, 00000, “The type of execution is not specified for this advisor or task.” Cause: You attempted to execute a task for a multi-execution task advisor without specifying the type of execution to perform. Action: Set the execution type and retry the operation. |
| ORA-13650 ORA-13650, 00000, “The specified object does not exist for this execution.” Cause: You attempted to associate an object to a task execution that id not contain the object. Action: Adjust the execution name and object ID, and then retry the operation. |
| ORA-13651 ORA-13651, 00000, “The specified list of execution parameters is invalid.” Cause: The list did not include pairs of (parameter_name, parameter_value) where every parameter is a valide task parameter. Duplicates are not allowed. Action: Adjust the content of the list, and then retry the operation. |
| ORA-13652 ORA-13652, 00000, “Cannot set execution parameters for this advisor” Cause: You attempted to set execution parameters for an advisor that did not support multiple executions of its tasks. Action: Adjust the property of the advisor, and then retry the operation. |
| ORA-13653 ORA-13653, 00000, “The directive with definition id %s was not found.” Cause: An invalid directive identifier was specified to advisor framework. Action: User should specify a correct identifier number and retry the operation. |
| ORA-13654 ORA-13654, 00000, “The directive with instance id of %s was not found.” Cause: An invalid instance identifier was specified to advisor framework. Action: User should specify a correct instance identifier number and retry the operation. |
| ORA-13655 ORA-13655, 00000, “The directive document contains a syntax error and cannot be loaded.” Cause: An attempt was made to load an XML-based directive that does not conform to the documented DTD. Action: Reformat the directive according the documented DTD. |
| ORA-13656 ORA-13656, 00000, “The parameter was not found in directive %s.” Cause: The specified parameter name could not be located within the directive XML document. Action: Verify the existence of the parameter in the specified directive. |
| ORA-13657 ORA-13657, 00000, “The filter Xpath specification has invalid syntax.” Cause: The specified filter could not be compiled within the directive XML document. Action: Verify the syntax of the filter and retry the operation. |
| ORA-13658 ORA-13658, 00000, “The specified directive already has an instance” Cause: An attempt was made to create multiple instances of a directive when not permitted Action: Verify the parent directive identifier and the instance name. |
| ORA-13659 ORA-13659, 00000, “A directive with domain \”%s\” and name \”%s\” already exists for advisor %s.” Cause: The specified directive is not unique among the directives. Action: Choose a directive name and domain that is distinct for the associated advisor. |
| ORA-13660 ORA-13660, 00000, “A directive instance with the name \”%s\” already exists.” Cause: The specified directive instance is not unique among instances for this directive. Action: Choose an instance name that is distinct for the associated directive. |
| ORA-13661 ORA-13661, 00000, “A directive instance with the name \”%s\” was not found.” Cause: An attempt was made to update or delete a non-existent directive instance. Action: Verify the parent directive identifier and the instance name. |
| ORA-13662 ORA-13662, 00000, “The specified value provided for parameter %s is not valid for this task.” Cause: The supplied parameter value was not valid for the current task configuration. Action: Retry by supplying valid value. Check the current task configuration. |
| ORA-13663 ORA-13663, 00000, “The task %s contains no results for execution %s.” Cause: An attempt was made to create a report or script from an execution that had not been successfully completed. Action: Run a new execution and then retry the operation. |
| ORA-13664 ORA-13664, 00000, “A task-managed \”SQL Tuning Set\” already exists for task \”%s\”.” Cause: An attempt was made to create a task-managed SQL Tuning Set for a task that already had one. Action: Create a new task to use a different SQL Tuning Set. |
| ORA-13665 ORA-13665, 00000, “Execution names are not correctly ordered.” Cause: The supplied execution names were not properly ordered by execution start date. Action: Retry by supplying a valid order. |
| ORA-13666 ORA-13666, 00000, “Task ID %s does not exist.” Cause: The supplied task ID was invalid. Action: Check the task ID and try again. |
| ORA-13667 ORA-13667, 00000, “Execution ID %s does not exist.” Cause: The supplied execution ID was invalid. Action: Check the execution ID and try again. |
| ORA-13668 ORA-13668, 00000, “The current operation was aborted because it was blocking another session.” Cause: The task or object operation interrupted itself when it detected that it was blocking some other session. Action: Retry the operation when the conflicting operations are not running. |
| ORA-13699 ORA-13699, 00000, “Advisor feature is not currently implemented.” Cause: An attempt was made to execute an unsupported advisor operation. Action: Verify the availability of the operation. // |
| ORA-13700 ORA-13700, 00000, “Reserved for ADDM tracing.” Cause: Action: |
| ORA-13701 ORA-13701, 00000, “Snapshot pair [%s, %s] seems to be specified in reverse order.” Cause: The start snapshot id was greater than the end snapshot id. Action: Swap the start and end snapshot ids. |
| ORA-13702 ORA-13702, 00000, “Snapshot IDs specified by the range [%s, %s] are equal.” Cause: The start snapshot id and end snapshot id were identical. Action: Provide different start and end snapshot ids. |
| ORA-13703 ORA-13703, 00000, “The snapshot pair [%s, %s] for database_id %s and instance_id %s are not found in the current repository.” Cause: The snapshot ids or the database id or the instance id was invalid or the specified snapshots have already been purged. Action: Set valid snapshot ids and retry. |
| ORA-13704 ORA-13704, 00000, “Invalid value \”%s\” specified for parameter \”%s\”.” Cause: The parameter was not set before executing the ADDM. Action: Set the parameter to a valid value and retry. |
| ORA-13705 ORA-13705, 00000, “There was a instance shutdown/startup between the snapshots in the range [%s, %s].” Cause: Instance was shut down and restarted between the two specified snapshots. Action: Specify start and end snapshot ids that does not have a shutdown/startup in between them. |
| ORA-13706 ORA-13706, 00000, “Invalid value \”%s\” specified for parameter \”%s\” in \”%s\” analysis mode.” Cause: The parameter was not set to an acceptable value for this particular mode of analysis. Action: Set the parameter to a valid value and retry. |
| ORA-13707 ORA-13707, 00000, “Either the start snapshot %s or the end snapshot %s is incomplete or missing key statistics.” Cause: Either the start or the end snaphots was missing or purged or had encountered errors while creating them. Action: Verify that AWR is done taking these two snapshots, or Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end snapshots. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that has valid start and end snapshots. |
| ORA-13708 ORA-13708, 00000, “Some snapshots in the range [%s, %s] were purged before the analysis was complete.” Cause: One or both of the snapshots have been purged from AWR. Action: Verify that the AWR auto purging is not trying to purge these snapshots and re-run ADDM. |
| ORA-13709 ORA-13709, 00000, “Required parameter \”%s\” must be set before execution.” Cause: The parameter needs to be set before running the ADDM Action: Set the parameter to a valid value and retry. |
| ORA-13710 ORA-13710, 00000, “Parameter \”%s\” must have a higher value than parameter \”%s\”. The values supplied were \”%s\” and \”%s\” respectively.” Cause: Invalid interaction between two parameter values. Action: Set at least one of the values so the value of the first parameter is higher than the value of the second parameter. |
| ORA-13711 ORA-13711, 00000, “Some snapshots in the range [%s, %s] are missing key statistics.” Cause: Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM analysis. Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the given snapshot range. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that does not include any incomplete snapshots. |
| ORA-13712 ORA-13712, 00000, “Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version \”%s\” do not match the database version \”%s\”.” Cause: ADDM analysis can only be performed on AWR snapshots taken in the current release. Action: One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them. |
| ORA-13713 ORA-13713, 00000, “Finding name \”%s\” does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values” Cause: Attempt to refer to an advisor’s finding name that does not exist. Action: Specify a valid value. The list of all valid values is in DBA_ADVISOR_FINDING_NAMES |
| ORA-13714 ORA-13714, 00000, “\”%s\” is not a valid SQL_ID value” Cause: The specified value of SQL_ID was not properly formatted. Action: Specify a valid value consisting of a 13 character string with characters from ’0′ to ’9′ and from ‘a’ to ‘z’. |
| ORA-13715 ORA-13715, 00000, “\”%s\” is not recognized by ADDM as a parameter name” Cause: The specified value for a system parameter was not recognized by ADDM. Action: Specify a value that appears in the NAME column of V$PARAMETER. |
| ORA-13716 ORA-13716, 00000, “Diagnostic Package License is needed for using this feature.” Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Diagnostic Package was disabled. Action: Modify the parameter value if the Diagnostic Package License was purchased. |
| ORA-13717 ORA-13717, 00000, “Tuning Package License is needed for using this feature.” Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Tuning Package was disabled. Action: Modify the parameter value if the Tuning Package License was purchased. |
| ORA-13718 ORA-13718, 00000, “Tuning Package License or Real Application Testing Option is needed for using this feature.” Cause: The specified package license and option were not installed. Action: Consider purchasing and installing either the missing package licence or option. If the tuning package license was purchased, then check the value of system parameter CONTROL_MANAGEMENT_PACK_ACCESS. |
| ORA-13750 ORA-13750, 00000, “User \”%s\” has not been granted the \”ADMINISTER SQL TUNING SET\” privilege.” Cause: The user attempted an SQL Tuning Set operation that requires a specific privilege. Action: Adjust the user’s privileges and retry the operation. |
| ORA-13751 ORA-13751, 00000, “\”SQL Tuning Set\” \”%s\” does not exist for owner \”%s\” or user \”%s\” does not have permission to access the \”SQL Tuning Set\”.” Cause: The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set Action: Check the existence of the \”SQL Tuning Set\” or adjust the user’s privileges and retry the operation. |
| ORA-13752 ORA-13752, 00000, “User \”%s\” must be SYS or must have the \”ADMINISTER ANY SQL TUNING SET\” privilege.” Cause: The attempted to create a SQL Tuning Set in another schema without having the right privilege. Action: Connect as SYS or adjust the user’s privilege and retry the operation. |
| ORA-13753 ORA-13753, 00000, “\”SQL Tuning Set\” \”%s\” already exists for user \”%s\”.” Cause: The user attempted to create a “\SQL Tuning”\ Set using a name that already exists for that owner. Action: Change the name of the SQL Tuning Set and retry the operation. |
| ORA-13754 ORA-13754, 00000, “\”SQL Tuning Set\” \”%s\” does not exist for user \”%s\”.” Cause: The user attempted to access a SQL Tuning Set that does not exist. Action: Check the speelling of the SQL Tuning Set name and retry the operation. |
| ORA-13755 ORA-13755, 00000, “invalid \”SQL Tuning Set\” name” Cause: The user attempted to specify a SQL Tuning Set name that is invalid. A name must not contain wildcards and its length must be less than 30 characters. Action: Adjust the name and retry the operation. |
| ORA-13756 ORA-13756, 00000, “Cannot update attribute \”%s\”.” Cause: The user attempted to update an attribute element that cannot be modified. The only string attributes that can be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER. Action: Adjust the attribute name and retry the operation. |
| ORA-13757 ORA-13757, 00000, “\”SQL Tuning Set\” \”%s\” owned by user \”%s\” is active.” Cause: The user attempted to update an active SQL Tuning Set. Action: Remove all reference to the SQL Tuning Set and retry the operation. |
| ORA-13758 ORA-13758, 00000, “\”SQL Tuning Set\” \”%s\” owned by user \”%s\” is in use.” Cause: The user attempted to modify a SQL Tuning Set or to add a reference to a SQL Tuning Set which is in use. Action: Wait until the end of the previous operation and retry. |
| ORA-13759 ORA-13759, 00000, “User \”%s\” cannot remove reference \”%s\”.” Cause: The user attempted to remove a SQL Tuning Set reference that does not exist. The user might not own the reference. Action: Check the reference ID and the reference owner and retry the operation. |
| ORA-13761 ORA-13761, 00000, “invalid filter” Cause: The user attempted to select data from a data source using an invalid filter. A filter is a WHERE clause on data source content. Action: Correct the filter and retry the operation. |
| ORA-13762 ORA-13762, 00000, “The %s ranking measure is invalid.” Cause: The user attempted to select data from a data source using an invlaid ranking measure. A ranking measure must represent a valid numerical expression. Action: Correct the ranking measure and retry the operation. |
| ORA-13763 ORA-13763, 00000, “illegal ranking attribute \”%s\”" Cause: The user attempted to use an attribute element that is not allowed in a ranking meseare. Action: Check the attribute in the ranking meseare and retry the operation. |
| ORA-13764 ORA-13764, 00000, “Value \”%s\” is illegal as a result percentage.” Cause: The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1. Action: Correct the result percentage value and retry the operation. |
| ORA-13765 ORA-13765, 00000, “Value \”%s\” is illegal for a result limit.” Cause: The user attempted to select data from a SQL Tuning Set using an invalid result limit. A result limit must be a positive interger. Action: Correct the result limit value and retry the operation. |
| ORA-13766 ORA-13766, 00000, “A ranking measure is required.” Cause: The user attempted to select data from a SQL Tuning Set using a percentage argument without specifying a ranking measure. Action: Add a ranking measure or remove the percentage argument and retry the operation. |
| ORA-13767 ORA-13767, 00000, “End snapshot ID must be greater than begin snapshot ID.” Cause: The user attempted to select data from the workload repository using an invalid snaphot ID range. Action: Adjust the snapshot ID range and retry the operation. |
| ORA-13768 ORA-13768, 00000, “Snapshot ID must be between %s and %s.” Cause: The user attempted to select data from the workload repository using a snaphot ID which does not exist. Action: Adjust the snapshot ID and retry the operation. |
| ORA-13769 ORA-13769, 00000, “Snapshots %s and %s do not exist.” Cause: The user attempted to select data from the workload repository using snapshots that do not exist. Action: Check the snapshot identifiers and retry the operation. |
| ORA-13770 ORA-13770, 00000, “Baseline \”%s\” does not exist.” Cause: The user attempted to access a baseline that does not exsit. Action: Check the speelling of the baseline name and retry the operation. |
| ORA-13771 ORA-13771, 00000, “cannot obtain exclusive lock %s on \”SQL Tuning Set\” \”%s\” owned by user \”%s\”" Cause: Unexpected error from DBMS_LOCK.REQUEST. Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services. |
| ORA-13772 ORA-13772, 00000, “unexpected deadlock on \”SQL Tuning Set\” \”%s\” owned by user \”%s\”" Cause: Unexpected error from DBMS_LOCK.REQUEST Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services. |
| ORA-13773 ORA-13773, 00000, “insufficient privileges to select data from the cursor cache” Cause: The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE. Action: Adjust the user’s privileges and retry the operation. |
| ORA-13774 ORA-13774, 00000, “insufficient privileges to select data from the workload repository” Cause: The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT. Action: Adjust the user’s privileges and retry the operation. |
| ORA-13775 ORA-13775, 00000, “inconsistent datatype in input cursor” Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW. Action: Check the rows type in the cursor and retry the operation. |
| ORA-13776 ORA-13776, 00000, “User \”%s\” has not been granted the \”SELECT\” privilege on the \”SQL tuning set\” DBA views.” Cause: The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views Action: User should be granted the privilege or only access his own STS |
| ORA-13777 ORA-13777, 00000, “invalid list of attribute names” Cause: The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN. Action: Adjust the attribute list and retry the operation. |
| ORA-13778 ORA-13778, 00000, “no new name or owner specified for \”SQL Tuning Set\”" Cause: The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner Action: Specify at least one or the other argument as non-NULL |
| ORA-13779 ORA-13779, 00000, “invalid load option” Cause: The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE. Action: Adjust the load option and retry the operation. |
| ORA-13780 ORA-13780, 00000, “SQL statement does not exist.” Cause: The user attempted to tune a SQL statement that does not exist. Action: Verify the sql_id and the plan hash value of the statement and retry the operation. |
| ORA-13781 ORA-13781, 00000, “cannot perform test-execute and explain plan operations on the automatic SQL tuning task” Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task. Action: Verify the name of the tuning task and retry the operation. |
| ORA-13783 ORA-13783, 00000, “invalid tuning scope” Cause: The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE. Action: Check the scope value and retry the operation. |
| ORA-13784 ORA-13784, 00000, “cannot accept SQL profiles for all statements in the \”%s\”" Cause: An attempt was made to accept SQL profiles for all statements in the input workload. Action: Provide the object identifier corresponding to a statement in the workload and retry the operation. |
| ORA-13785 ORA-13785, 00000, “missing target object for tuning task \”%s\”" Cause: The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier. Action: Check the identifier of the object and retry the operation. |
| ORA-13786 ORA-13786, 00000, “missing SQL text of statement object \”%s\” for tuning task \”%s\”" Cause: The user attempted to accept SQL profile for an object that has not a SQL text associated to it. Action: Check the identifier of the object and retry the operation. |
| ORA-13787 ORA-13787, 00000, “missing SQL profile for statement object \”%s\” for tuning task \”%s\”" Cause: The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it. Action: Check the identifier of the object and retry the operation. |
| ORA-13788 ORA-13788, 00000, “invalid recommendation type” Cause: The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS and INDEXES. Action: Check the rec_type arg and retry the operation. |
| ORA-13789 ORA-13789, 00000, “invalid process action” Cause: The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN. Action: Check the action argument and retry the operation. |
| ORA-13790 ORA-13790, 00000, “invalid value for time limit” Cause: The user passed an invalid value for the time limit argument. Action: Check the argument specified value and retry the operation. |
| ORA-13791 ORA-13791, 00000, “cannot resume a task created to process a single statement” Cause: An attempt was made to resume a task that was created for a single SQL statement. A task can be resumed only if it is used for a SQL Tuning Set. Action: No action required. |
| ORA-13793 ORA-13793, 00000, “invalid comparison metric” Cause: An invalid metric to compare SQL performance was specified. Action: Use execution statistics to compare the result of two executions and optimizer_cost to analyze performance of two explain plan actions. |
| ORA-13794 ORA-13794, 00000, “execution type mismatch” Cause: An attempt was made to analyze the performance of a SQL workload using two executions that were generated using two different actions. Action: check the name and type of task executions to analyze and retry the operation. |
| ORA-13795 ORA-13795, 00000, “missing task execution” Cause: An insufficient number of valid task executions to analyze the performance of a SQL workload were specified. Action: run the task to generate two executions of the same type and retry the operation. |
| ORA-13796 ORA-13796, 00000, “invalid value %s specified for problem type” Cause: An invalid problem type was specified to the SQL diagnosis advisor. Problem type should be one of the PROBLEM_TYPE_* defined in ‘admin/dbmsdiag.sql’. Action: Specify valid problem type. |
| ORA-13797 ORA-13797, 00000, “invalid SQL Id specified, %s” Cause: Invalid SQL Id specified for conversion. Action: Specify valid SQL Id. |
| ORA-13798 ORA-13798, 00000, “Parameter %s cannot be NULL.” Cause: A call to GET_THRESHOLD procedure was made without a required parameter. Action: Specify a valid value for this parameter. |
| ORA-13799 ORA-13799, 00000, “threshold not found” Cause: No threshold was found with the specified threshold key. Action: No action required. |
| ORA-13800 ORA-13800, 00000, “concurrent DDL failure on SQL repository objects” Cause: A SQL repository object was the target of two concurrent DDL operations. Action: Check the current state of the object and retry the operation that failed. |
| ORA-13801 ORA-13801, 00000, “invalid value for SQLTUNE_CATEGORY parameter” Cause: An invalid Oracle identifier was used as the value of the parameter. Action: Specify the parameter conforming to the rules for Oracle identifiers. |
| ORA-13802 ORA-13802, 00000, “failed to purge SQL Tuning Base entry from sql$” Cause: An error occured while try to delete a SQL Tuning Base object. Action: Look at the underlying error(s) on the error stack. |
| ORA-13825 ORA-13825, 00000, “missing SQL statement text for create SQL profile” Cause: No SQL text was provided to the create SQL profile operation. Action: Retry with properly specified SQL text. |
| ORA-13826 ORA-13826, 00000, “empty SQL profile not allowed for create or update SQL profile” Cause: No attributes were specified to the create SQL profile operation. Action: Retry with at least one hint specified. |
| ORA-13827 ORA-13827, 00000, “null or zero length attribute specified in SQL profile collection” Cause: One of the attributes within the SQL profile was not properly specified. Action: Retry with a fully specified SQL profile. |
| ORA-13828 ORA-13828, 00000, “generated SQL profile name %s already exists” Cause: A SQL profile already exists with the name generated by the system. Action: Retry the operation as the generated name is time sensitive. |
| ORA-13829 ORA-13829, 00000, “SQL profile named %s already exists” Cause: A SQL profile already exists with the name specified. Action: Specify a different name or drop the existing SQL profile. |
| ORA-13830 ORA-13830, 00000, “SQL profile with category %s already exists for this SQL statement” Cause: A SQL profile already exists for the given SQL statement and category. Action: Drop or update the existing SQL profile. |
| ORA-13831 ORA-13831, 00000, “SQL profile name specified is invalid” Cause: An invalid SQL profile name was specified. Action: Look for the underlying error on the error message stack. |
| ORA-13832 ORA-13832, 00000, “category name specified is invalid” Cause: An invalid category name swas pecified. Action: Look for the underlying error on the error message stack. |
| ORA-13833 ORA-13833, 00000, “SQL profile named %s doesn’t exist” Cause: A SQL profile name was specified that doesn’t exist. Action: Verify the name of the SQL profile. |
| ORA-13834 ORA-13834, 00000, “name of SQL profile to be cloned must be provided” Cause: A SQL profile name was not provided as the from target of a clone SQL profile operation. Action: Provide the name of the SQL profile being cloned. |
| ORA-13835 ORA-13835, 00000, “invalid attribute name specified” Cause: An invalid attribute name was specified for an alter SQL profile operation. Action: Verify the name of the attribute. |
| ORA-13836 ORA-13836, 00000, “invalid attribute value specified” Cause: An invalid attribute value was specified for an alter SQL profile operation. Action: Verify the attribute value. |
| ORA-13837 ORA-13837, 00000, “invalid HASH_VALUE” Cause: An invalid HASH_VALUE was passed to a create SQL profile operation Action: Verify the HASH_VALUE. |
| ORA-13838 ORA-13838, 00000, “invalid ADDRESS value” Cause: An invalid ADDRESS value was passed to a create SQL profile operation. Action: Verify the ADDRESS value. |
| ORA-13839 ORA-13839, 00000, “V$SQL row doesn’t exist with given HASH_VALUE and ADDRESS.” Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile operation doesn’t coorespond to an existing V$SQL entry. Action: Verify the HASH_VALUE and ADDRESS in V$SQL. |
| ORA-13840 ORA-13840, 00000, “Concurrent DDL Error in create SQL profile operation.” Cause: A concurrent DDL operation was performed during a create or replace sql profile operation. Action: Try operation again |
| ORA-13841 ORA-13841, 00000, “SQL profile named %s already exists for a different signature/category pair” Cause: A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified. Action: Specify a different name or drop the existing SQL profile. |
| ORA-13842 ORA-13842, 00000, “no SELECT privilege on DBA_SQL_PROFILES” Cause: A user has tried to perform an operation that requires SELECT privileges on the DBA_SQL_PROFILES view. Action: Either perform the operation as another user or get the privilege |
| ORA-13843 ORA-13843, 00000, “no SQL profile with name like \”%s\” exists for category like \”%s\”" Cause: A user tried to perform an operation by specifying a profile name/ category filter that did not target any profiles Action: Try a different filter after checking the profile name/category |
| ORA-13844 ORA-13844, 00000, “no new SQL profile name or category specified.” Cause: A user called remap_stgtab_sqlprof without specifying new values for the sql profile name or category. At least one is required. Action: Specify either a new profile name, or a new category, or both |
| ORA-13845 ORA-13845, 00000, “invalid SQL profile XML specification provided” Cause: The supplied XML specification for the SQL profile did not adhere to the proper schema. Action: Check the syntax and try again. |
| ORA-13850 ORA-13850, 00000, “Tracing for client identifier %s is not enabled” Cause: Attempt to disable a client identifier tracing which was never enabled Action: Supply correct client identifier |
| ORA-13851 ORA-13851, 00000, “Tracing for client identifier %s is already enabled” Cause: Attempt to enable a client identifier tracing which has been already enabled Action: Supply correct client identifier, or disable and re-enable tracing with different bind/wait options |
| ORA-13852 ORA-13852, 00000, “Tracing for service(module/action) %s is not enabled” Cause: Attempt to disable a service-level tracing which was never enabled Action: Supply correct service(module/action) name |
| ORA-13853 ORA-13853, 00000, “Tracing for service (module/action) %s is already enabled” Cause: Attempt to enable a service-level tracing which has been already enabled Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options |
| ORA-13854 ORA-13854, 00000, “Tracing for service(module/action) %s on instance %s is not enabled” Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance Action: Supply correct service(module/action) name |
| ORA-13855 ORA-13855, 00000, “Tracing for service (module/action) %s on instance %s is already enabled” Cause: Attempt to enable a service-level tracing which has been already enabled on a specific instance Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options |
| ORA-13856 ORA-13856, 00000, “Service name must be specified” Cause: Omitting service name while enabling/disabling tracing or aggregation Action: Supply the service name |
| ORA-13857 ORA-13857, 00000, “Invalid module name” Cause: Module name is too long (exceeding 48 characters) Action: Supply correct name |
| ORA-13858 ORA-13858, 00000, “Invalid action name” Cause: Action name is too long (exceeding 32 characters) Action: Supply correct name |
| ORA-13859 ORA-13859, 00000, “Action cannot be specified without the module specification” Cause: Action name is specified, but the module name is not Action: Supply the module name |
| ORA-13860 ORA-13860, 00000, “Invalid service name” Cause: Service name is too long (exceeding 64 characters) Action: Supply correct name |
| ORA-13861 ORA-13861, 00000, “Statistics aggregation for client identifier %s is already enabled” Cause: Attempt to enable a client identifier aggregation which has been already enabled Action: Supply correct client identifier |
| ORA-13862 ORA-13862, 00000, “Statistics aggregation for client identifier %s is not enabled” Cause: Attempt to disable a client identifier statistics aggregation which was never enabled Action: Supply correct client identifier |
| ORA-13863 ORA-13863, 00000, “Statistics aggregation for service(module/action) %s is not enabled” Cause: Attempt to disable a service-level statistics aggregation which was never enabled Action: Supply correct service(module/action) name |
| ORA-13864 ORA-13864, 00000, “Statistics aggregation for service (module/action) %s is already enabled” Cause: Attempt to enable a service-level statistics aggregation which has been already enabled Action: Supply correct service(module/action) |
| ORA-13865 ORA-13865, 00000, “Module name must be specified” Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification Action: Supply module name |
| ORA-13866 ORA-13866, 00000, “Client identifier must be specified” Cause: Omitting client identifier while enabling/disabling tracing or aggregation Action: Supply the client identifier |
| ORA-13867 ORA-13867, 00000, “Database-wide SQL tracing is already enabled” Cause: Attempt to enable a database-level tracing which has been already enabled Action: Disable and re-enable tracing with different bind/wait options |
| ORA-13868 ORA-13868, 00000, “Instance-wide SQL tracing on instance %s is not enabled” Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance Action: No action required |
| ORA-13869 ORA-13869, 00000, “Instance-wide SQL tracing on instance %s is already enabled” Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance Action: Disable and re-enable tracing with different bind/wait options |
| ORA-13870 ORA-13870, 00000, “Database-wide SQL tracing is not enabled” Cause: Attempt to disable a database-level tracing which was never enabled Action: No action required |
| ORA-13871 ORA-13871, 00000, “Invalid instance name” Cause: Instance name is too long (exceeding 16 characters) Action: Supply correct name |
| ORA-13900 ORA-13900, 00000, “missing or invalid parameter %s” Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid. Action: Specify a valid value for this parameter. |
| ORA-13901 ORA-13901, 00000, “Object %s was not found.” Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object. Action: Specify a valid object name. |
| ORA-13902 ORA-13902, 00000, “The specified file %s is not a data file.” Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file. Action: Specify a valid data file name. |
| ORA-13903 ORA-13903, 00000, “Invalid combination of %s threshold value and operator.” Cause: A non-positive number was used for “Blocked User Session Count” metrics while operator contains equal. Action: Use a positive number for the threshold value or use “greater than” operator. |
| ORA-13904 ORA-13904, 00000, “The file has been dropped and recreated during the procedure call.” Cause: The file on which threshold is specified was dropped and recreated during the procedure call. Action: Retry this operation. |
| ORA-13905 ORA-13905, 00000, “Critical or warning threshold have incorrect values” Cause: The tablespace threshold values can be in the range 0 to 100 only. Action: Check the threshold values |
| ORA-13906 ORA-13906, 00000, “The tablepace is not of the right type.” Cause: An attempt was made to set a threshold on dictionary-managed tablespaces. Action: Check the tablespace type and reissue the command. |
| ORA-13907 ORA-13907, 00000, “Threshold value is invalid.” Cause: An attempt was made to specify an invalid value for critical or warning thresholds. Action: Use non-negative integers only for threshold values. |
| ORA-13908 ORA-13908, 00000, “Invalid combination of metrics id and object type parameters.” Cause: An attempt was made to specify an invalid combination of metrics id and object type parameters. Action: Specify a valid combination of metrics id and object type parameters. |
| ORA-13909 ORA-13909, 00000, “Invalid combination of threshold value and operator.” Cause: An attempt was made to specify an invalid combination of threshold value and operator. Action: Check the operator and threshold values and reissue statement. |
| ORA-13910 ORA-13910, 00000, “Parameter %s cannot be NULL.” Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter. Action: Specify a valid value for this parameter. |
| ORA-13911 ORA-13911, 00000, “Threshold not found” Cause: The threshold did not exist with the specified threshold key. Action: No action required. |
| ORA-13912 ORA-13912, 00000, “Critical threshold value is less than warning threshold value.” Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value. Action: Check the threshold values and reissue the statement. |
| ORA-13913 ORA-13913, 00000, “The threshold cannot be set when SYSAUX is offline.” Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline. Action: Call SET_THRESHOLD procedure when SYSAUX is online. |
| ORA-13914 ORA-13914, 00000, “Threshold notification failed.” Cause: An error occurred when sending notification for this threshold. Action: Make sure you have enough space on SYSAUX tablespace and retry this operation. |
| ORA-13915 ORA-13915, 00000, “Critical byte based free space threshold value is greater than warning threshold value.” Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value. Action: Check the threshold values and reissue the statement. |
| ORA-13916 ORA-13916, 00000, “Invalid value \”%s\” specified for parameter \”%s\”" Cause: An invalid value was specified for the the given parameter. Action: Correct the value being specified for the parameter. |
| ORA-13917 ORA-13917, 0000, “Posting system alert with reason_id %s failed with code [%s] [%s]” Cause: Connection to the database is dead, or invalid parameter to alert routine. Action: If this condition repeats, please contact Oracle Support. |
| ORA-13918 ORA-13918, 0000, “Updating system alert with reason_id %s failed; previous alert not found” Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING. Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support. |
| ORA-13919 ORA-13919, 00000, “Cannot specify values for parameter \”%s\” and for parameter \”%s\”" Cause: Can only specify a value for one or the other. Action: Pass just one of the parameters. |
| ORA-13920 ORA-13920, 00000, “Threshold cannot be set when database is in read-only mode.” Cause: SET_THRESHOLD procedure was called when database was open in read-only mode. Action: Call SET_THRESHOLD procedure when database is open in read/write mode. |
| ORA-13950 ORA-13950, 00000, “MMON action time limit exceeded” Document: NO Cause: MMON action did not complete within the system specified time frame. Action: None. |
| ORA-13951 ORA-13951, 00000, “MMON sub-action time limit exceeded” Cause: MMON sub-action did not complete within the system specified time frame. Action: None. |
| ORA-13970 ORA-13970, 00000, “Invalid name of \”%s\” given” Cause: Passed an invalid component, report, or transformation name to the framework. Names must be alphanumeric and can contain the underscore (_) character. Action: Try again with a valid name |
| ORA-13971 ORA-13971, 00000, “%s \”%s\” unknown” Cause: Passed an unknown component, report, or transformation to the framework. Action: Give a different name |
| ORA-13972 ORA-13972, 00000, “%s \”%s\” unknown for %s \”%s\”" Cause: An object with the first name is unknown within the naming scope of the second name Action: Change the parameters passed in or register the proper object |
| ORA-13973 ORA-13973, 00000, “%s unknown for %s \”%s\”" Cause: An object is unknown within the given naming scope Action: Change the parameters passed in or register the proper object |
| ORA-13974 ORA-13974, 00000, “%s with name \”%s\” already exists” Cause: An object with the given name already exists Action: Give a different name |
| ORA-13975 ORA-13975, 00000, “%s with name \”%s\” already exists for %s \”%s\”" Cause: An object with the first name already exists within the naming scope of the second name Action: Give a different name |
| ORA-13976 ORA-13976, 00000, “Improperly-formed report tag” Cause: The top-level report tag was not built properly Action: Make sure that the report tag is built using the common tag library function |
| ORA-13977 ORA-13977, 00000, “Invalid content type” Cause: An invalid content type was passed to the register format API Action: Correct your code to use the values in dbmsrep.sql |
| ORA-13978 ORA-13978, 00000, “Invalid reference string parameter or value” Cause: An invalid parameter/value was passed to a dbms_report API Action: Ensure that the parameter names and values are alphanumeric. |
| ORA-13979 ORA-13979, 00000, “Filename too long” Cause: An invalid file name was passed to STORE_FILE Action: Ensure that the filename is less than 500 bytes |
| ORA-13980 ORA-13980, 00000, “Invalid file URL” Cause: A URL with invalid syntax was provided, either directly to the function or via an XML IMPORT or INCLUDE. Action: Check the URL. |
| ORA-13981 ORA-13981, 00000, “Invalid file URL or path prefix” Cause: Either a URL or path prefix with invalid syntax was provided. Action: Check the URL |
| ORA-13982 ORA-13982, 00000, “Could not find file at URL provided” Cause: The file requested could not be found in the given location. Action: Check the URL provided. |
| ORA-13983 ORA-13983, 00000, “Missing tag from HTML” Cause: An HTML document was passed to the function missing its tag. Action: Check the HTML source. |
| ORA-13984 ORA-13984, 00000, “Invalid reference string” Cause: The given reference string could not be parsed. Action: Check the reference string syntax. |
| ORA-13985 ORA-13985, 00000, “Invalid URL provided to servlet” Cause: An invalid URL was provided to the servlet. Action: Check the URL. |
| ORA-13986 ORA-13986, 00000, “Error \%s received from XPath engine” Cause: An error was received from the xpath library during an xpath operation. Action: Check xmlerr.h to understand the cause of the error. |
| ORA-13987 ORA-13987, 00000, “Invalid input to build common <%s> tag” Cause: Invalid input was given when attempting to build a common tag. Action: Check the function input to make sure all necessary information is given. |
| ORA-13988 ORA-13988, 00000, “Invalid input given to variable argument list report function.” Cause: An invalid parameter was provided to one of the report framework variable argument list functions. Action: Check the function input and try again. |
| ORA-13989 ORA-13989, 00000, “Invalid input given to structured argument list report function.” Cause: An invalid parameter was provided to one of the report framework structured argument list functions. Action: Check the function input and try again. |
| ORA-13990 ORA-13990, 00000, “Invalid tag name given to common tag callout function.” Cause: An invalid tag name was provided to the report framework common tag callout function. Action: Check the function input and try again. |
| ORA-14000 ORA-14000, 00000, “only one LOCAL clause may be specified” Cause: CREATE INDEX statement contained more than one LOCAL clause Action: Specify LOCAL option at most once |
| ORA-14001 ORA-14001, 00000, “LOCAL clause contradicts previosly specified GLOBAL clause” Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause Action: Specify LOCAL or GLOBAL clause, but not both |
| ORA-14002 ORA-14002, 00000, “only one GLOBAL clause may be specified” Cause: CREATE INDEX statement contained more than one GLOBAL clause Action: Specify GLOBAL option at most once |
| ORA-14003 ORA-14003, 00000, “GLOBAL clause contradicts previosly specified LOCAL clause” Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause Action: Specify GLOBAL or LOCAL clause, but not both |
| ORA-14004 ORA-14004, 00000, “missing PARTITION keyword” Cause: keyword PARTITION missing Action: supply missing keyword |
| ORA-14005 ORA-14005, 00000, “missing RANGE keyword” Cause: keyword RANGE missing Action: supply missing keyword |
| ORA-14006 ORA-14006, 00000, “invalid partition name” Cause: a partition name of the form <identifier> is // expected but not present. Action: enter an appropriate partition name. |
| ORA-14007 ORA-14007, 00000, “missing LESS keyword” Cause: keyword LESS missing Action: supply missing keyword |
| ORA-14008 ORA-14008, 00000, “missing THAN keyword” Cause: keyword THAN missing Action: supply missing keyword |
| ORA-14009 ORA-14009, 00000, “partition bound may not be specified for a LOCAL index partition” Cause: while parsing a CREATE INDEX statement to create a LOCAL partitioned index, <partition-description> of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions |
| ORA-14010 ORA-14010, 00000, “this physical attribute may not be specified for an index partition” Cause: unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions Action: remove invalid option(s) from the list of physical attributes of an index partition Comment: this error could have resulted from omission of a terminating (right) parenthesis following the list of partition descriptions |
| ORA-14011 ORA-14011, 00000, “names assigned to resulting partitions must be distinct” Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index |
| ORA-14012 ORA-14012, 00000, “resulting partition name conflicts with that of an existing partition” Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index |
| ORA-14013 ORA-14013, 00000, “duplicate partition name” Cause: Name of a partition of a table or index being created is not unique Action: rename partition(s) to ensure that their names are unique among partitions of the table or index being created |
| ORA-14014 ORA-14014, 00000, “maximum number of partitioning columns is 16″ Cause: number of columns in a partitioning column list exceeded the legal limit of 16 Action: modify partitioning column list so that it consists of at most 16 columns |
| ORA-14015 ORA-14015, 00000, “too many partition descriptions” Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 1048575 (1024K-1). Action: Reduce number of partitions to not exceed 1048575 (1024K -1). |
| ORA-14016 ORA-14016, 00000, “underlying table of a LOCAL partitioned index must be partitioned” Cause: User attempted to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table. Action: Correct the statement and reenter |
| ORA-14017 ORA-14017, 00000, “partition bound list contains too many elements” Cause: Partition bound list contained more elements than there are partitioning columns Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index |
| ORA-14018 ORA-14018, 00000, “partition bound list contains too few elements” Cause: Partition bound list contained fewer elements than there are partitioning columns Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index |
| ORA-14019 ORA-14019, 00000, “partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE” Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or MAXVALUE) Action: Ensure that all elements of partition bound list are of valid type |
| ORA-14020 ORA-14020, 00000, “this physical attribute may not be specified for a table partition” Cause: unexpected option was encountered while parsing physical attributes of a table partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for Hash partitions Action: remove invalid option(s) from the list of physical attributes of a table partition Comment: this error could have resulted from omission of a terminating (right) parenthesis following the list of partition descriptions |
| ORA-14021 ORA-14021, 00000, “MAXVALUE must be specified for all columns” Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns Action: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns |
| ORA-14022 ORA-14022, 00000, “creation of LOCAL partitioned cluster indices is not supported” Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal Action: Remove LOCAL along with <partition description>s, if any, from the CREATE INDEX statement. |
| ORA-14023 ORA-14023, 00000, “creation of GLOBAL partitioned cluster indices is not supported” Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal Action: Remove PARTITION BY RANGE clause along with <partition description>s from the CREATE INDEX statement. |
| ORA-14024 ORA-14024, 00000, “number of partitions of LOCAL index must equal that of the underlying table” Cause: User attempted to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table. Action: Correct the CREATE INDEX statement to specify a correct number of partitions |
| ORA-14025 ORA-14025, 00000, “PARTITION may not be specified for a materialized view or a materialized view log” Cause: PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid options |
| ORA-14026 ORA-14026, 00000, “PARTITION and CLUSTER clauses are mutually exclusive” Cause: definition of a table contained both PARTITION and CLUSTER clauses which is illegal Action: Remove one of the conflicting clauses |
| ORA-14027 ORA-14027, 00000, “only one PARTITION clause may be specified” Cause: CREATE TABLE statement contained more than one PARTITION clause Action: Specify PARTITION option at most once |
| ORA-14028 ORA-14028, 00000, “missing AT or VALUES keyword” Cause: keyword AT or VALUES missing Action: supply missing keyword |
| ORA-14029 ORA-14029, 00000, “GLOBAL partitioned index must be prefixed” Cause: partitioning columns of a global partitioned index must form a prefix of the index’ key columns Action: Ensure that the GLOBAL partitioned index being created is prefixed |
| ORA-14030 ORA-14030, 00000, “non-existent partitioning column in CREATE TABLE statement” Cause: Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created. Action: Ensure that all columns in the partitioning column list are columns of the table being created. |
| ORA-14031 ORA-14031, 00000, “partitioning column may not be of type LONG or LONG RAW” Cause: Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal. Action: Ensure that no partitioning column is of type LONG or LONG RAW. |
| ORA-14032 ORA-14032, 00000, “partition bound of partition number %s is too high” Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal. Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. |
| ORA-14033 ORA-14033, 00000, “ctchvl: unexpected strdef type” Document: NO Cause: opndef representation of an element of partition bound list had strtyp set to unexpected value (must be STRTCONS or STRTMAXV) Action: Ensure that prsott and prspstr agree on what constitutes a valid element of partition bound list |
| ORA-14034 ORA-14034, 00000, “ctchvl: unexpected operand type” Document: NO Cause: opndef representation of an element of partition bound list had opntyp set to unexpected value (must be OPNTSTR) Action: Ensure that prsott and prspstr agree on what constitutes a valid element of partition bound list |
| ORA-14035 ORA-14035, 00000, “ctchvl: unexpected string data type” Document: NO Cause: opndef representation of a string element of partition bound list had opndty set to unexpected value (must be OPNCHR or OPNNUM) Action: Ensure that prsott and prspstr agree on what constitutes a valid element of partition bound list |
| ORA-14036 ORA-14036, 00000, “partition bound value too large for column” Cause: Length of partition bound value is longer than that of the corresponding partitioning column. Action: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns |
| ORA-14037 ORA-14037, 00000, “partition bound of partition \”%s\” is too high” Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal. Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. |
| ORA-14038 ORA-14038, 00000, “GLOBAL partitioned index must be prefixed” Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is illegal Action: If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed |
| ORA-14039 ORA-14039, 00000, “partitioning columns must form a subset of key columns of a UNIQUE index” Cause: User attempted to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal Action: If the user, indeed, desired to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index’ partitioning columns form a subset of its key columns |
| ORA-14040 ORA-14040, 00000, “inadequate number of arguments passed to tbl$or$idx$part$num” Document: NO Cause: tbl$or$idx$part$num was supplied with fewer than 5 arguments which is illegal Action: Supply tbl$or$idx$part$num with table name, index dictionary object number or 0, dimension number, composite partition number (if dimension is 2) or 0, and as many expressions (e.g. column names) as there are partitioning columns in the table or index mapping into a partition of which is to be determined |
| ORA-14041 ORA-14041, 00000, “partition bound may not be specified for resulting partitions” Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, <partition-description> of a resulting partition was found to contain VALUES LESS THAN clause which is illegal Action: remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition |
| ORA-14042 ORA-14042, 00000, “partition bound may not be specified for a partition being moved, modified or rebuilt” Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal Action: remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt |
| ORA-14043 ORA-14043, 00000, “only one partition may be added” Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas |
| ORA-14044 ORA-14044, 00000, “only one partition may be moved” Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas |
| ORA-14045 ORA-14045, 00000, “only one partition may be modified” Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas |
| ORA-14046 ORA-14046, 00000, “a partition may be split into exactly two new partitions” Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split |
| ORA-14047 ORA-14047, 00000, “ALTER TABLE|INDEX RENAME may not be combined with other operations” Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; |
| ORA-14048 ORA-14048, 00000, “a partition maintenance operation may not be combined with other operations” Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g. ADD PARTITION or PCTFREE which is illegal Action: Ensure that a partition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will |
| ORA-14049 ORA-14049, 00000, “invalid ALTER TABLE MODIFY PARTITION option” Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, // STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a Range or Composite Range partition. Action: Specify only legal options. |
| ORA-14050 ORA-14050, 00000, “invalid ALTER INDEX MODIFY PARTITION option” Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement. Action: Specify only legal options. |
| ORA-14051 ORA-14051, 00000, “invalid ALTER MATERIALIZED VIEW option” Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement. Action: Specify only legal options. |
| ORA-14052 ORA-14052, 00000, “partition-extended table name syntax is disallowed in this context” Cause: User attempted to use partition-extended table name syntax in illegal context (i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement) Action: Avoid use of partition-extended table name in contexts other those mentioned above. |
| ORA-14053 ORA-14053, 00000, “illegal attempt to modify %s in %s statement” Cause: Certain attributes of objects (e.g. tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes. Action: Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created |
| ORA-14054 ORA-14054, 00000, “invalid ALTER TABLE TRUNCATE PARTITION option” Cause: Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION |
| ORA-14055 ORA-14055, 00000, “keyword REBUILD in ALTER INDEX REBUILD must immediately follow <index name>” Cause: ALTER INDEX statement contained REBUILD keyword following some index attributes (e.g. INITRANS.) Action: Ensure that keyword REBUILD immediately follows the name of the index being altered |
| ORA-14056 ORA-14056, 00000, “partition number %s: sum of PCTUSED and PCTFREE may not exceed 100″ Cause: the sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100 |
| ORA-14057 ORA-14057, 00000, “partition \”%s\”: sum of PCTUSED and PCTFREE may not exceed 100″ Cause: the sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100 |
| ORA-14058 ORA-14058, 00000, “partition number %s: INITRANS value must be less than MAXTRANS value” Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS |
| ORA-14059 ORA-14059, 00000, “partition \”%s\”: INITRANS value must be less than MAXTRANS value” Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS |
| ORA-14060 ORA-14060, 00000, “data type or length of a table partitioning column may not be changed” Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of table partitioning column(s) |
| ORA-14061 ORA-14061, 00000, “data type or length of an index partitioning column may not be changed” Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of index partitioning column(s) |
| ORA-14062 ORA-14062, 00000, “one or more of table’s partitions reside in a read-only tablespace” Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more partitions of which reside in read-only tablespaces, which is illegal Action: Avoid performing aformentioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces |
| ORA-14063 ORA-14063, 00000, “Unusable index exists on unique/primary constraint key” Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable. Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD |
| ORA-14064 ORA-14064, 00000, “Index with Unusable partition exists on unique/primary constraint key” Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index one or more partitions of which are marked Index Unusable. Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION |
| ORA-14065 ORA-14065, 00000, “ALLOCATE STORAGE may not be specified for a partitioned table” Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement. |
| ORA-14066 ORA-14066, 00000, “illegal option for a non-partitioned index-organized table” Cause: An attempt was made to issue a CREATE or ALTER TABLE command on a non-partitioned IOT, but the command contains an option that is legal only for partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT. Action: Remove the illegal option(s) from the command. |
| ORA-14067 ORA-14067, 00000, “duplicate TABLESPACE_NUMBER specification” Cause: TABLESPACE_NUMBER clause was specified more than once for an table, index or an index partition Action: Correct the code generating text of CREATE INDEX statement sent to the slaves |
| ORA-14068 ORA-14068, 00000, “TABLESPACE and TABLESPACE_NUMBER may not be both specified” Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, index or an index partition Action: Correct the code generating text of CREATE INDEX statement sent to the slaves |
| ORA-14069 ORA-14069, 00000, “invalid TABLESPACE_NUMBER value” Cause: The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF Action: Correct the code generating text of CREATE INDEX statement sent to the slaves |
| ORA-14070 ORA-14070, 00000, “option may be specified only for partitioned indices or with REBUILD” Cause: User issued ALTER INDEX statament containing an option which is legal only for partitioned indices or in conjunction // with REBUILD against a non-partitioned index. Such options are: // PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and // FREELIST GROUPS inside STORAGE clause Action: Remove illegal option(s). |
| ORA-14071 ORA-14071, 00000, “invalid option for an index used to enforce a constraint” Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, // MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint. Action: Choose one of the valid index options. |
| ORA-14072 ORA-14072, 00000, “fixed table may not be truncated” Cause: User attempted to truncate a fixed table which is illegal. Action: Ensure that the table being truncated is not a fixed table. |
| ORA-14073 ORA-14073, 00000, “bootstrap table or cluster may not be truncated” Cause: User attempted to truncate a bootstrap table or cluster which is illegal Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster) |
| ORA-14074 ORA-14074, 00000, “partition bound must collate higher than that of the last partition” Cause: Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table’s last partition, which is illegal. Action: Ensure that the partition bound of the partition to be added collates higher than that of the table’s last partition. |
| ORA-14075 ORA-14075, 00000, “partition maintenance operations may only be performed on partitioned indices” Cause: Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, // at best, meaningless Action: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned |
| ORA-14076 ORA-14076, 00000, “submitted alter index partition/subpartition operation is not valid for local partitioned index” Cause: User attempted to either drop, split, add or coalesce a partition or a subpartition of a local index which is illegal. Action: Ensure that the index named in such statement is a global partitioned index. |
| ORA-14078 ORA-14078, 00000, “you may not drop the highest partition of a GLOBAL index” Cause: User attempted to drop highest partition of a GLOBAL index, which is illegal. Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index. |
| ORA-14079 ORA-14079, 00000, “illegal option for a partition marked Index Unusable” Cause: ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal Action: Ensure that only valid optins are specified |
| ORA-14080 ORA-14080, 00000, “partition cannot be split along the specified high bound” Cause: User attempted to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that that of a partition immediately preceding the one to be split |
| ORA-14081 ORA-14081, 00000, “new partition name must differ from the old partition name” Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of the partition being renamed Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index |
| ORA-14082 ORA-14082, 00000, “new partition name must differ from that of any other partition of the object” Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of some existing partition of the object Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index |
| ORA-14083 ORA-14083, 00000, “cannot drop the only partition of a partitioned table” Cause: A drop partition command is being executed when there is only one partition in the table Action: Ensure that there is at least one partition. Drop table to remove all partitions |
| ORA-14084 ORA-14084, 00000, “you may specify TABLESPACE DEFAULT only for a LOCAL index” Cause: User attempted to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal. Action: Reenter the statement without TABLESPACE DEFAULT clause. |
| ORA-14085 ORA-14085, 00000, “partitioned table cannot have column with LONG datatype” Cause: User tried to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table. Action: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non partitioned table. |
| ORA-14086 ORA-14086, 00000, “a partitioned index may not be rebuilt as a whole” Cause: User attempted to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index |
| ORA-14087 ORA-14087, 00000, “use of <table-name> PARTITION (<partition-number>| Document: NO Cause: Action: // Level 1+ Allow use of aforementioned syntax |
| ORA-14088 ORA-14088, 00000, “second argument to tbl$or$idx$part$num must be an integer constant” Document: NO Cause: Second argument to tbl$or$idx$part$num (must be index object ID or 0) was found not to be an integer constant Action: Ensure that the second argument passed to tbl$or$idx$part$num is an integer constant representing object ID of an index if it is desired that that indes’ partition mapping descriptor be used or 0 otherwise |
| ORA-14089 ORA-14089, 00000, “base table does not have an index with a specified ID defined on it” Document: NO Cause: Second argument to tbl$or$idx$part$num was non-zero, implying that the partition mapping descriptor of an index defined on the table whose name was supplied as the first srgument is to be used, but that table does not have an index with the specified object ID defined on it. Action: Ensure that the object ID suplied as the second argument is that of an index defined on the table whose name was supplied as the first argument. |
| ORA-14090 ORA-14090, 00000, “index must be partitioned” Document: NO Cause: Index whose ID was supplied by the user as the second argument to tbl$or$idx$part$num was not partitioned Action: Second argument passed to tbl$or$idx$part$num must be an object ID of a partitioned index defined on the table whose name was supplied as the first argument if one desires to determine mapping into an index partition or 0 if one desires to determine mapping into a partition of the base table itself |
| ORA-14091 ORA-14091, 00000, “table must be partitioned” Document: NO Cause: Table whose name was supplied by the user as the first argument to tbl$or$idx$part$num was not partitioned Action: If one desires to determine mapping of rows into a partition of a base table, one must supply a name of a partitioned table as the first argument and 0 as the second argument. If, on the other hand, one desires to determine mapping of rows into a partition of an index defined on that table, one must supply that index’ object ID as the second argument |
| ORA-14092 ORA-14092, 00000, “number of expressions is not equal to the number of partitioning columns” Document: NO Cause: Number of expressions submitted to tbl$or$idx$part$num differs from the number of partitioning columns of the table or index mapping into partition(s) of which is to be determined Action: Supply a correct number of expressions to be used in determining mapping into partition(s) of a specified table or index |
| ORA-14093 ORA-14093, 00000, “data type of expression incompatible with that of partitioning column” Document: NO Cause: Data type of an expression was neiher equal to nor coercible into that of a corresponding partitioning column of a table or index mapping into partition(s) of which is of interest Action: Ensure that data types of expressions supplied to tbl$or$idx$part$num are compatible with those of corresponding partitioning columns of a table or index mapping into partition(s) of which is of interest |
| ORA-14094 ORA-14094, 00000, “invalid ALTER TABLE EXCHANGE PARTITION option” Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE PARTITION |
| ORA-14095 ORA-14095, 00000, “ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table” Cause: The table in the EXCHANGE operation is either clustered or partitioned Action: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered. |
| ORA-14096 ORA-14096, 00000, “tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns” Cause: The two tables specified in the EXCHANGE have different number of columns Action: Ensure that the two tables have the same number of columns with the same type and size. |
| ORA-14097 ORA-14097, 00000, “column type or size mismatch in ALTER TABLE EXCHANGE PARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size Action: Ensure that the two tables have the same number of columns with the same type and size. |
| ORA-14098 ORA-14098, 00000, “index mismatch for tables in ALTER TABLE EXCHANGE PARTITION” Cause: The two tables specified in the EXCHANGE have indexes which are not equivalent Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. |
| ORA-14099 ORA-14099, 00000, “all rows in table do not qualify for specified partition” Cause: There is at least one row in the non partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION Action: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them. |
| ORA-14100 ORA-14100, 00000, “partition extended table name cannot refer to a remote object” Cause: User attempted to use partition-extended table name syntax in conjunction with remote object name which is illegal Action: Correct the statement and reenter |
| ORA-14101 ORA-14101, 00000, “partition extended table name cannot refer to a synonym” Cause: User attempted to use partition-extended table name syntax in conjunction with synonym name which is illegal Action: Correct the statement and reenter |
| ORA-14102 ORA-14102, 00000, “only one LOGGING or NOLOGGING clause may be specified” Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified. Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement. |
| ORA-14103 ORA-14103, 00000, “LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE” Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed. Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| ORA-14104 ORA-14104, 00000, “RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices” Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| ORA-14105 ORA-14105, 00000, “RECOVERABLE/UNRECOVERABLE may not be specified in this context” Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context. Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| ORA-14106 ORA-14106, 00000, “LOGGING/NOLOGGING may not be specified for a clustered table” Cause: User attempted to specify LOGGING or NOLOGGING clausein CREATE TABLE or ALTER TABLE statement involving a clustered table Action: Remove offending clause. |
| ORA-14107 ORA-14107, 00000, “partition specification is required for a partitioned object” Cause: parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects. Action: supply missing parameter |
| ORA-14108 ORA-14108, 00000, “illegal partition-extended table name syntax” Cause: Partition to be accessed may only be specified using its name. User attempted to use a partition number or a bind variable. Action: Modify statement to refer to a partition using its name |
| ORA-14109 ORA-14109, 00000, “partition-extended object names may only be used with tables” Cause: User attempted to use a partition-extended object name with an object which is not a table. Action: Avoid using partition-extended name syntax with objects which are not tables |
| ORA-14110 ORA-14110, 00000, “partitioning column may not be of type ROWID” Cause: Partitioning column specified by the user was of type ROWID, which is illegal. Action: Ensure that no partitioning column is of type ROWID. |
| ORA-14111 ORA-14111, 00000, “creation of a GLOBAL partitioned index on clustered tables is not supported” Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal. Action: Remove PARTITION BY RANGE/HASH clause along with any partition descriptions to create a GLOBAL non-partitioned index on a clustered table |
| ORA-14112 ORA-14112, 00000, “RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition” Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal Action: Remove offending clause. Use LOGGING or NOLOGGING instead. |
| ORA-14113 ORA-14113, 00000, “partitioned table cannot have column with LOB datatype” Cause: User tried to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table. Action: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non partitioned table. |
| ORA-14114 ORA-14114, 00000, “partitioned table cannot have column with object, REF, nested table, array datatype” Cause: User tried to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table. Action: object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non partitioned table. |
| ORA-14115 ORA-14115, 00000, “partition bound of partition number %s is too long” Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. |
| ORA-14116 ORA-14116, 00000, “partition bound of partition \”%s\” is too long” Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. |
| ORA-14117 ORA-14117, 00000, “partition resides in offlined tablespace” Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. |
| ORA-14118 ORA-14118, 00000, “CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them. Action: Ensure that the two tables do not have CHECK constraint defined on any column |
| ORA-14119 ORA-14119, 00000, “specified partition bound is too long” Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. |
| ORA-14120 ORA-14120, 00000, “incompletely specified partition bound for a DATE column” Cause: An attempt was made to use a date expression whose format does not fully (i.e. day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT). Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (i.e. day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (i.e. including the century) specification of the year, use TO_DATE() (e.g. TO_DATE(’01-01-1999′, ‘MM-DD-YYYY’) to fully express the desired date. |
| ORA-14121 ORA-14121, 00000, “MODIFY DEFAULT ATTRIBUTES may not be combined with other operations” Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will |
| ORA-14122 ORA-14122, 00000, “only one REVERSE or NOREVERSE clause may be specified” Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement. Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement. |
| ORA-14123 ORA-14123, 00000, “duplicate NOREVERSE clause” Cause: NOREVERSE was specified more than once in ALTER INDEX statement. Action: Remove all but one of the NOREVERSE clauses and reissue the statement. |
| ORA-14124 ORA-14124, 00000, “duplicate REVERSE clause” Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements. Action: Remove all but one of the REVERSE clauses and reissue the statement. |
| ORA-14125 ORA-14125, 00000, “REVERSE/NOREVERSE may not be specified in this context” Cause: REVERSE/NOREVERSE clause is not allowed in this context. Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement. |
| ORA-14126 ORA-14126, 00000, “only a <parallel clause> may follow description(s) of resulting partitions” Cause: Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional <parallel clause> which applies to the entire statement and which, in turn, may not be followed by any other clause. Action: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement. |
| ORA-14127 ORA-14127, 00000, “illegal index-partition-extended table name syntax” Document: NO Cause: Index partition may be specified using IND_PARTITION( // or IND_PARTITION(<part#>). Internal user attempted to specify an index partition name. Action: Modify statement to refer to an index partition using its number |
| ORA-14128 ORA-14128, 00000, “FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints. Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. |
| ORA-14129 ORA-14129, 00000, “INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints” Cause: Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command. Action: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used. |
| ORA-14130 ORA-14130, 00000, “UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION” Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis // key columns) constraint is defined on the other table or // a matching constraint is defined on the other table, but it // differs from that defined on the first table vis-a-vis being // enabled and/or validated. Action: Ensure that for every UNIQUE constraint defined on one of the // tables named in the ALTER TABLE EXCHANGE PARTITION statement there // is a matching (vis-a-vis key columns and being enabled and/or // validated) UNIQUE constraint defined on the other table. // If UNIQUE constrains are enabled, UNIQUE constraints on the // partitioned table should be enforced using local indexes. |
| ORA-14131 ORA-14131, 00000, “enabled UNIQUE constraint exists on one of the tables” Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding. Action: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement. |
| ORA-14132 ORA-14132, 00000, “table cannot be used in EXCHANGE” Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply: – it is a typed table – it is a temporary table – it contains ADT columns – it contains nested-table columns – it contains REF columns – it contains array columns – it is an index-organized table – it contains LOB columns – it is a nested table – it is created with row dependency and the partitioned table is not – it is created without row dependency and the partitioned table is Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command. |
| ORA-14133 ORA-14133, 00000, “ALTER TABLE MOVE cannot be combined with other operations” Cause: An attempt was made to combine an ALTER TABLE MOVE statement // with another operation, such as MODIFY. Action: Make sure that MOVE is the only operation specified in ALTER TABLE // statement; |
| ORA-14134 ORA-14134, 00000, “indexes cannot use both DESC and REVERSE” Cause: An attempt was made to make a reverse index with some index columns marked DESC. Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC. |
| ORA-14135 ORA-14135, 00000, “a LOB column cannot serve as a partitioning column” Cause: An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column. Action: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB. |
| ORA-14136 ORA-14136, 00000, “ALTER TABLE EXCHANGE restricted by fine-grained security” Cause: User doing exchange does not have full table access due to VPD policies. Action: Grant exempt priviliges to this user. |
| ORA-14137 ORA-14137, 00000, “Table in partially dropped state, submit DROP TABLE PURGE” Cause: An attempt was made to access a partitioned table in a partially dropped state. Action: Submit DROP TABLE <table> PURGE to drop the table. |
| ORA-14138 ORA-14138, 00000, “An unexpected error encountered during drop table operation” Cause: Drop table encountered an unexpected error. Action: a. Submit drop table <table> purge, or b. If the situation described in the next error on the stack // can be corrected, do so. c. Contact Oracle Support. |
| ORA-14139 ORA-14139, 00000, “table %s.%s is already in read-only mode” Cause: an attempt was made to set a read-only table in read-only mode Action: this DDL can only be executed on a read/write table |
| ORA-14140 ORA-14140, 00000, “table %s.%s is already in read/write mode” Cause: an attempt was made to set a read/write table in read/write mode Action: this DDL can only be executed on a read-only table |
| ORA-14141 ORA-14141, 00000, “ALTER INDEX VISIBLE|INVISIBLE may not be combined with other operations” Cause: ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE operation with some other operation which is illegal Action: Ensure that VISIBLE|INVISIBLE operation is the sole operation specified in ALTER INDEX statement |
| ORA-14142 ORA-14142, 00000, “ALTER INDEX VISIBLE|INVISIBLE may not be used with certain types of index” Cause: Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types of indexes (IOT-TOP, Cluster indexes) is illegal. Action: Remove the option VISIBLE|INVISIBLE. |
| ORA-14143 ORA-14143, 00000, “CREATE INDEX INVISIBLE may not be used with this type of index” Cause: Certain types of indexes (IOT-TOP, Cluster indexes) cannot be created invisible. Action: Remove the option INVISIBLE |
| ORA-14144 ORA-14144, 00000, “arguments to tbl$or$idx$part$num must not be bind variables” Document: NO Cause: Second, third or fourth argument to tbl$or$idx$part$num was found to be a bind variable and not an integer constant. Action: Ensure that the argument passed to tbl$or$idx$part$num is an integer constant and not a bind variable. |
| ORA-14150 ORA-14150, 00000, “missing SUBPARTITION keyword” Cause: keyword SUBPARTITION missing Action: supply missing keyword |
| ORA-14151 ORA-14151, 00000, “invalid table partitioning method” Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, LIST, SYSTEM, or Composite Range-Hash/List/Range (R+H/L/R). Action: Specify one of valid partitioning methods |
| ORA-14152 ORA-14152, 00000, “invalid number of partitions specified in PARTITIONS clause” Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-1048575) Action: Specify a number between 1 and 1024K-1 in the number-of-partitions clause |
| ORA-14153 ORA-14153, 00000, “only one of STORE IN or <partition-description> clause may be specified” Cause: both STORE IN and <partition-description> clauses were specified in a CREATE TABLE|INDEX command Action: Remove one of offending clauses |
| ORA-14154 ORA-14154, 00000, “only one of STORE IN or <subpartition-description> clause may be specified” Cause: both STORE IN and <subpartition-description> clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a Composite Range partitioned object Action: Remove one of offending clauses |
| ORA-14155 ORA-14155, 00000, “missing PARTITION or SUBPARTITION keyword” Cause: expect either PARTITION or SUBPARTITION keyword but none was supplied Action: supply missing keyword |
| ORA-14156 ORA-14156, 00000, “invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause” Cause: number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-1048575) Action: Specify a number between 1 and 1024K-1 in the number-of-subpartitions clause |
| ORA-14157 ORA-14157, 00000, “invalid subpartition name” Cause: a subpartition name of the form <identifier> is expected but not present. Action: enter an appropriate subpartition name. |
| ORA-14158 ORA-14158, 00000, “too many subpartition descriptions” Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 1048575. Action: Reduce number of subpartitions to not exceed 1024K-1. |
| ORA-14159 ORA-14159, 00000, “duplicate subpartition name” Cause: Name of a subpartition of a table or index being created is not unique Action: rename subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created |
| ORA-14160 ORA-14160, 00000, “this physical attribute may not be specified for a table subpartition” Cause: unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option Action: remove invalid option(s) Comment: this error could have resulted from omission of a terminating (right) parenthesis following the list of subpartition descriptions |
| ORA-14161 ORA-14161, 00000, “subpartition number %s: sum of PCTUSED and PCTFREE may not exceed 100″ Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100 |
| ORA-14162 ORA-14162, 00000, “subpartition \”%s\”: sum of PCTUSED and PCTFREE may not exceed 100″ Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100 |
| ORA-14163 ORA-14163, 00000, “subpartition number %s: INITRANS value must be less than MAXTRANS value” Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS |
| ORA-14164 ORA-14164, 00000, “subpartition \”%s\”: INITRANS value must be less than MAXTRANS value” Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS |
| ORA-14165 ORA-14165, 00000, “MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations” Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will |
| ORA-14166 ORA-14166, 00000, “missing INTO keyword” Cause: keyword INTO missing Action: supply missing keyword |
| ORA-14167 ORA-14167, 00000, “only one subpartition may be moved” Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved Action: Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas |
| ORA-14168 ORA-14168, 00000, “only one subpartition may be modified” Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified Action: Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas |
| ORA-14169 ORA-14169, 00000, “invalid ALTER TABLE MODIFY SUBPARTITION option” Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, // STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement. Action: Specify only legal options. |
| ORA-14170 ORA-14170, 00000, “cannot specify <partition-description> clause in CREATE TABLE|INDEX” Cause: User requested to generate default partition description(s) (possibly via PARTITIONS <number-of-partitions>) while at the same time specified <partition-description> clause which is illegal Action: Remove one of offending clauses. |
| ORA-14171 ORA-14171, 00000, “cannot specify <subpartition-description> clause in CREATE|ALTER TABLE” Cause: User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified <subpartition-description> clause which is illegal Action: Remove one of offending clauses. |
| ORA-14172 ORA-14172, 00000, “invalid ALTER TABLE EXCHANGE SUBPARTITION option” Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION |
| ORA-14173 ORA-14173, 00000, “illegal subpartition-extended table name syntax” Cause: Subpartition to be accessed may only be specified using its name. User attempted to use a subpartition number or a bind variable. Action: Modify statement to refer to a subpartition using its name |
| ORA-14174 ORA-14174, 00000, “only a <parallel clause> may follow COALESCE PARTITION|SUBPARTITION” Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional <parallel clause>. No partition/subpartition attributes may be specified Action: Ensure that no partition/subpartition attribute was specified. |
| ORA-14175 ORA-14175, 00000, “a subpartition maintenance operation may not be combined with other operations” Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (e.g. MOVE SUBPARTITION) with some other operation (e.g. MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal Action: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will |
| ORA-14176 ORA-14176, 00000, “this attribute may not be specified for a hash partition” Cause: An invalid option was encountered while parsing physical attributes of a partition of an object partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions. Action: Remove the invalid option(s). |
| ORA-14177 ORA-14177, 00000, “STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table” Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a range/list/composite range list partitioned table Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range/list/composite range list partitioned table |
| ORA-14178 ORA-14178, 00000, “STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes” Cause: STORE IN (DEFAULT) is valid only for local indexes. Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN clause and specify tablespaces individually for each index partition. |
| ORA-14183 ORA-14183, 00000, “TABLESPACE DEFAULT can be specified only for Composite LOCAL index” Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash partitioned LOCAL index object, which is illegal. Action: Replace TABLESPACE DEFAULT with TABLESPACE |
| ORA-14184 ORA-14184, 00000, “cannot create an UNIQUE partitioned index on a SYSTEM partitioned table” Document: NO Cause: User attempted to create a UNIQUE partitioned index on a SYSTEM partitioned table Action: Remove UNIQUE keyword |
| ORA-14185 ORA-14185, 00000, “incorrect physical attribute specified for this index partition” Cause: unexpected option was encountered while parsing physical attributes of a local index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions // STORE IN () is also disallowed for all but Composite Range partitions Action: remove invalid option(s) from the list of physical attributes of an index partition |
| ORA-14186 ORA-14186, 0000, “number of sub-partitions of LOCAL index must equal that of the underlying table” Cause: User attempted to create a LOCAL partitioned index with a number of sub-partitions which is different from that of the underlying table. Action: Correct the CREATE INDEX statement to specify a correct number of sub-partitions |
| ORA-14187 ORA-14187, 0000, “partitioning method for LOCAL index is inconsistent with that of the underlying table” Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with the underlying table. The partitioning types are mismatched. Action: Correct the CREATE INDEX statement to ensure that the index partitionining method is consistent with that of the base table |
| ORA-14188 ORA-14188, 0000, “sub-partitioning columns must form a subset of key columns of a UNIQUE index” Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal Action: If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index’ subpartitioning columns form a subset of its key columns |
| ORA-14189 ORA-14189, 00000, “this physical attribute may not be specified for an index subpartition” Cause: unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option Action: remove invalid option(s) |
| ORA-14190 ORA-14190, 00000, “only one ENABLE/DISABLE ROW MOVEMENT clause can be specified” Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT was specified more than once. 2) DISABLE ROW MOVEMENT was specified more than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified. Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses; then, reissue the command. |
| ORA-14191 ORA-14191, 00000, “ALLOCATE STORAGE may not be specified for Composite Range partitioned object” Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. // |
| ORA-14192 ORA-14192, 00000, “cannot modify physical index attributes of a Hash index partition” Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a Hash partitioned index Action: Remove the physical attributes one is trying to modify // |
| ORA-14193 ORA-14193, 0000, “invalid ALTER INDEX MODIFY SUBPARTITION option” Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement. Action: Specify only legal options. |
| ORA-14194 ORA-14194, 00000, “only one subpartition may be rebuilt” Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas |
| ORA-14195 ORA-14195, 00000, “ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object” Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. |
| ORA-14196 ORA-14196, 00000, “Specified index cannot be used to enforce the constraint.” Cause: The index specified to enforce the constraint is unsuitable for the purpose. Action: Specify a suitable index or allow one to be built automatically. |
| ORA-14197 ORA-14197, 00000, “dimension values 3,4 cannot be used with domain indexes” Document: NO Cause: A dimension value of 3 or 4 was used in conjunction with a domain index Action: Do not use dimension value 3,4 for domain indexes in tbl$or$idx$part$num function |
| ORA-14198 ORA-14198, 00000, “rowid column must refer to table specified in 1st parameter” Document: NO Cause: The table name specified in the 1st parameter and the table that the rowid column belongs to are not the same Action: Make sure the table name in the 1st parameter is the same as the table that rowid column belongs to |
| ORA-14199 ORA-14199, 000000, “Disable fix for 4900129″ Document: NO Cause: Action: |
| ORA-14200 ORA-14200, 00000, “Only one parameter can be specified and it must be constant or bind” Document: NO Cause: When dimension value is 5, only 1 parameter can be specified and it must be a constant or bind variable. Action: Make sure the parameter is a constant or bind variable. |
| ORA-14201 ORA-14201, 00000, “specified subpartition bound is too long” Cause: Length of a linear key representation of a high bound of a table subpartition being added or along which an existing table or index subpartition is being split exceeded the legal limit (4K). Action: Change the representation of a subpartition high bound to bring its length within legal limit. |
| ORA-14202 ORA-14202, 00000, “subpartition bound of subpartition \”%s\” is too high” Cause: High bound of the specified subpartition displayed in this message did not collate lower than that of the subsequent subpartition. Action: Ensure that high bound of every subpartition (except for the last one) collates lower than that of a subsequent subpartition. |
| ORA-14203 ORA-14203, 00000, “subpartition bound of subpartition \”%s\” is too long” Cause: Length of linear key representation of a high bound of the specified subpartition displayed in this message exceeded the legal limit (4K). Action: Change the representation of a subpartition high bound to bring its length within legal limit. |
| ORA-14204 ORA-14204, 00000, “subpartition bound of subpartition number %s is too high” Cause: High bound of the specified subpartition displayed in this message did not collate lower than that of the subsequent subpartition. Action: Ensure that high bound of every subpartition (except for the last one) collates lower than that of a subsequent subpartition. |
| ORA-14205 ORA-14205, 00000, “subpartition bound of subpartition number %s is too long” Cause: Length of linear key representation of a high bound of the specified subpartition displayed in this message exceeded the legal limit (4K). Action: Change the representation of a subpartition high bound to bring its length within legal limit. |
| ORA-14206 ORA-14206, 00000, “table is not subpartitioned by List or Range methods” Cause: A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List or Range subpartitioned objects Action: Issue the command only against a List or Range subpartitioned object. |
| ORA-14207 ORA-14207, 00000, “maximum number of subpartitioning columns is 16″ Cause: number of columns in a subpartitioning column list exceeded the legal limit of 16 Action: modify subpartitioning column list so that it consists of at most 16 columns |
| ORA-14208 ORA-14208, 00000, “lower-bound subpartition must be specified first” Cause: A higher-bound subpartition was specified before the lower-bound subpartition in ALTER TABLE MERGE SUBPARTITIONS statement. Action: Specify lower-bound subpartition first and then higher-bound subpartition |
| ORA-14209 ORA-14209, 00000, “subpartitions being merged are not adjacent” Cause: Attempted to merge two subpartitions that are not adjacent to each other. Action: Specify two subpartitions that are adjacent |
| ORA-14210 ORA-14210, 00000, “cannot reuse lower-bound subpartition as resulting subpartition” Cause: Attempted to reuse the lower-bound subpartition of the subpartitions being merged. Action: Specify new resulting subpartition name or reuse the higher-bound subpartition only |
| ORA-14211 ORA-14211, 00000, “subpartition bound must collate higher than that of the last subpartition” Cause: Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD SUBPARTITION statement did not collate higher than that of the partition’s last subpartition. Action: Ensure that the subpartition bound of the subpartition to be added collates higher than that of the table partition’s last subpartition. |
| ORA-14212 ORA-14212, 00000, “subpartition cannot be split along the specified high bound” Cause: Attempted to split a subpartition along a bound which either collates higher than that of the subpartition to be split or lower than that of a subpartition immediately preceding the one to be split Action: Ensure that the bound along which a subpartition is to be split collates lower than that of the subpartition to be split and higher than that of a subpartition immediately preceding the one to be split |
| ORA-14213 ORA-14213, 00000, “VALUES LESS THAN or AT clause cannot be used for List subpartitioned tables” Cause: VALUES LESS THAN or AT clause was used for List subpartitioned tables Action: Use VALUES (<value list>) clause for List subpartitioned tables |
| ORA-14214 ORA-14214, 00000, “VALUES (<value list>) cannot be used for Range subpartitioned tables” Cause: VALUES (<value list>) clause was used for Range subpartitioned tables Action: Use VALUES LESS THAN or AT clause with Range subpartitioned tables |
| ORA-14215 ORA-14215, 00000, “subpartition bound list contains too many elements” Cause: Subpartition bound list contained more elements than there are subpartitioning columns Action: Ensure that the number of elements in subpartition bound list is equal to the number of subpartitioning columns of the table or index |
| ORA-14216 ORA-14216, 00000, “subpartition bound list contains too few elements” Cause: Subpartition bound list contained fewer elements than there are subpartitioning columns Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index |
| ORA-14217 ORA-14217, 00000, “VALUES (<value list>) clause expected” Cause: VALUES (<value list>) clause was not specified for the list subpartition being added Action: Specify a VALUES (<value list>) clause |
| ORA-14240 ORA-14240, 00000, “use of syntax for SYSTEM and Range Composite/System (R+S) partitioning methods” Document: NO Cause: Action: // Level 1+ Allow use of aforementioned syntax |
| ORA-14241 ORA-14241, 00000, “invalid table partitioning method” Document: NO Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, SYSTEM, LIST, HASH, or Composite Range (R+S or R+H).” Action: Specify one of valid partitioning methods |
| ORA-14242 ORA-14242, 00000, “table is not partitioned by System, or Hash method” Document: NO Cause: The table in the ADD PARTITIONS operation is partitioned by method other than System, or Hash Action: Ensure that the table is partitioned by System, or Hash method |
| ORA-14243 ORA-14243, 00000, “table is not partitioned by Range, System, List, or Hash method” Document: NO Cause: The table in the MOVE PARTITION operation is partitioned by method other than Range, System, List, or Hash method Action: Ensure that the table is partitioned by Range, System, List, or Hash method |
| ORA-14244 ORA-14244, 00000, “illegal operation for a Composite Range/System partitioned table” Document: NO Cause: any operation done to a Composite Range/System partitioned table is controlled through event 14240 Action: Ensure that the event is turned on |
| ORA-14251 ORA-14251, 00000, “Specified subpartition does not exist” Cause: Subpartition not found for the object. Action: Retry with correct subpartition name. |
| ORA-14252 ORA-14252, 00000, “invalid ALTER TABLE MODIFY PARTITION option for a Hash partition” Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a Hash partition. Action: Specify only legal options. |
| ORA-14253 ORA-14253, 00000, “table is not partitioned by Composite Range method” Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by Composite Range method Action: Ensure that the table is partitioned by Composite Range method |
| ORA-14254 ORA-14254, 00000, “cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table” Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a Range or Composite Range partitioned table which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION. |
| ORA-14255 ORA-14255, 00000, “table is not partitioned by Range, List, Composite Range or Composite List method” Cause: The table was not partitioned by Range, List, Composite Range or Composite List method. Action: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by Range, List, Composite Range or Composite List methods. Ensure that the table is partitioned appropriately. |
| ORA-14256 ORA-14256, 00000, “invalid resulting partition description(s)” Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or <subpartition-description> clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a Composite Range partitioned table which is illegal Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range method |
| ORA-14257 ORA-14257, 00000, “cannot move partition other than a Range, List, System, or Hash partition” Cause: User attempt to move a partition that is not a Range,List,System, or Hash partition which is illegal Action: Specify MOVE PARTITION for a Range,List,System, or Hash partition only |
| ORA-14258 ORA-14258, 00000, “invalid partition description” Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or <subpartition-description> clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a Composite Range/Hash partitioned table which is illegal Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range/Hash method |
| ORA-14259 ORA-14259, 00000, “table is not partitioned by Hash method” Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method Action: Specify valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method |
| ORA-14260 ORA-14260, 00000, “incorrect physical attribute specified for this partition” Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a Hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified. Action: Remove invalid option(s) |
| ORA-14261 ORA-14261, 00000, “partition bound may not be specified when adding this Hash partition” Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a Hash partitioned table which is illegal Action: Remove VALUES LESS THAN clause from the description of partition being added |
| ORA-14262 ORA-14262, 00000, “new subpartition name must differ from the old subpartition name” Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying <new-subpartition-name> which is identical to the name of the subpartition being renamed Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index |
| ORA-14263 ORA-14263, 00000, “new subpartition name must differ from that of any other subpartition of the object” Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying <new-subpartition-name> which is identical to the name of some existing subpartition of the object Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index |
| ORA-14264 ORA-14264, 00000, “table is not partitioned by Composite Range method” Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method Action: Ensure that the table is partitioned by Composite method |
| ORA-14265 ORA-14265, 00000, “data type or length of a table subpartitioning column may not be changed” Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of table subpartitioning column(s) |
| ORA-14266 ORA-14266, 00000, “data type or length of an index subpartitioning column may not be changed” Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of index subpartitioning column(s) |
| ORA-14267 ORA-14267, 00000, “cannot specify PARALLEL clause when adding a (Composite) Range partition” Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a Range or Composite Range partition which is illegal Action: Remove the PARALLEL clause. |
| ORA-14268 ORA-14268, 00000, “subpartition ‘%s’ of the partition resides in offlined tablespace” Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. |
| ORA-14269 ORA-14269, 00000, “cannot exchange partition other than a Range,List,System, or Hash partition” Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a Range,List,System, or Hash partition which is illegal Action: Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition only |
| ORA-14270 ORA-14270, 00000, “table is not partitioned by Range, System, Hash or List method” Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Range,List,System, or Hash method which is illegal. Action: Ensure that the table is partitioned by Range,List,System, or Hash method |
| ORA-14271 ORA-14271, 00000, “table is not partitioned by Composite Range method” Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Composite Range method which is illegal. Action: Ensure that the table is partitioned by Composite Range method |
| ORA-14272 ORA-14272, 00000, “only a partition with higher bound can be reused” Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal. Action: Use the higher-bound partition to be the resulting partition or specify a new partition name |
| ORA-14273 ORA-14273, 00000, “lower-bound partition must be specified first” Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal Action: Specify lower-bound partition then higher-bound partition |
| ORA-14274 ORA-14274, 00000, “partitions being merged are not adjacent” Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal Action: Specify two partitions that are adjacent |
| ORA-14275 ORA-14275, 00000, “cannot reuse lower-bound partition as resulting partition” Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal Action: Specify new resulting partition name or reuse the higher-bound partition only |
| ORA-14276 ORA-14276, 00000, “EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table” Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered. |
| ORA-14277 ORA-14277, 00000, “tables in EXCHANGE SUBPARTITION must have the same number of columns” Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns Action: Ensure that the two tables have the same number of columns with the same type and size. |
| ORA-14278 ORA-14278, 00000, “column type or size mismatch in EXCHANGE SUBPARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size Action: Ensure that the two tables have the same number of columns with the same type and size. |
| ORA-14279 ORA-14279, 00000, “index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION” Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. |
| ORA-14280 ORA-14280, 00000, “all rows in table do not qualify for specified subpartition” Cause: There is at least one row in the non partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION Action: Ensure that all the rows in the segment qualify for the subpartition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that subpartition to find out the invalid rows and delete them. |
| ORA-14281 ORA-14281, 00000, “CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them. Action: Ensure that the two tables do not have CHECK constraint defined on any column |
| ORA-14282 ORA-14282, 00000, “FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints. Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. |
| ORA-14283 ORA-14283, 00000, “UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION” Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis // key columns) constraint is defined on the other table or // a matching constraint is defined on the other table, but it // differs from that defined on the first table vis-a-vis being // enabled and/or validated. Action: Ensure that for every UNIQUE constraint defined on one of the // tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement // there is a matching (vis-a-vis key columns and being enabled and/or // validated) UNIQUE constraint defined on the other table. // If UNIQUE constrains are enabled, UNIQUE constraints on the // partitioned table should be enforced using local indexes. |
| ORA-14284 ORA-14284, 00000, “one or more of table’s subpartitions reside in a read-only tablespace” Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more subpartitions of which reside in read-only tablespaces, which is illegal Action: Avoid performing aformentioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces |
| ORA-14285 ORA-14285, 00000, “cannot COALESCE the only partition of this hash partitioned table or index” Cause: A COALESCE PARTITION command was issued when there is only one partition in the table or index, which is illegal Action: Ensure that there is at least one partition. Drop the table or index to remove all partitions. |
| ORA-14286 ORA-14286, 00000, “cannot COALESCE the only subpartition of this table partition” Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal Action: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions. |
| ORA-14287 ORA-14287, 00000, “cannot REBUILD a partition of a Composite Range partitioned index” Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal Action: REBUILD the index partition, a subpartition at a time |
| ORA-14288 ORA-14288, 00000, “index is not partitioned by Composite Range method” Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by Composite Range method |
| ORA-14289 ORA-14289, 00000, “cannot make local index partition of Composite Range partitioned table unusable” Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal |
| ORA-14290 ORA-14290, 00000, “PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION” Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints. Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation. |
| ORA-14291 ORA-14291, 00000, “cannot EXCHANGE a composite partition with a non-partitioned table” Cause: A composite partition can only be exchanged with a partitioned table. Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite. |
| ORA-14292 ORA-14292, 00000, “Partitioning type of table must match subpartitioning type of composite partition” Cause: When exchanging a partitioned table with a composite partition the partitioning type of the table must match the subpartitioning type of the composite partition. Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition. |
| ORA-14293 ORA-14293, 00000, “Number of partitioning columns does not match number of subpartitioning columns” Cause: When exchanging a partitioned table with a composite partition the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition. Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the the composite partition. |
| ORA-14294 ORA-14294, 00000, “Number of partitions does not match number of subpartitions” Cause: When exchanging a partitioned table with a composite partition the number of partitions of the table must match the number of subpartitions of the composite partition. Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition. |
| ORA-14295 ORA-14295, 00000, “column type or size mismatch between partitioning columns and subpartitioning columns” Cause: When exchanging a partitioned table with a composite partition the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition. Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition. |
| ORA-14296 ORA-14296, 00000, “Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION” Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match. *Action Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match. |
| ORA-14297 ORA-14297, 00000, “Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION” Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. *Action Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. |
| ORA-14298 ORA-14298, 00000, “LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION” Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. *Action Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. |
| ORA-14299 ORA-14299, 00000, “total number of partitions/subpartitions exceeds the maximum limit” Cause: The total number of combined fragments specified in partitions /subpartitions exceeds 1048575. *Action Reissue the statement with fewer number of fragments |
| ORA-14301 ORA-14301, 00000, “table-level attributes must be specified before partition-level attributes” Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or // while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions. Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement. |
| ORA-14302 ORA-14302, 00000, “only one list of added-LOB-storage-clauses can be specified in a statement” Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list. Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement. |
| ORA-14303 ORA-14303, 00000, “partitions or subpartitions are not in the right order” Cause: Descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently from the DDL order of partitions or subpartitions. Action: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement. Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal |
| ORA-14304 ORA-14304, 00000, “List partitioning method expects a single partitioning column” Cause: number of columns in a partitioning column list exceeded the legal limit of 1 for List partitioned objects Action: modify partitioning column list so that it consists of at most 1 column |
| ORA-14305 ORA-14305, 00000, “List value ‘%s’ specified twice in partition ‘%s’” Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value |
| ORA-14306 ORA-14306, 00000, “List value ‘%s’ specified twice in partitions ‘%s’, ‘%s’” Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value |
| ORA-14307 ORA-14307, 00000, “partition contains too many list values” Cause: Partition list contains more than 524288 list values Action: Reduce the number of values to not exceed 524288 values |
| ORA-14308 ORA-14308, 00000, “partition bound element must be one of: string, datetime or interval literal, number, or NULL” Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL) Action: Ensure that all elements of partition bound list are of valid type |
| ORA-14309 ORA-14309, 00000, “Total count of list values exceeds maximum allowed” Cause: Partitioned object contains more than 524288 list values Action: Reduce number of values to less than 524288. |
| ORA-14310 ORA-14310, 00000, “VALUES LESS THAN or AT clause cannot be used with List partitioned tables” Cause: VALUES LESS THAN or AT clause can be used only with Range partitioned tables Action: Use VALUES (<value list>) clause with List partitioned tables |
| ORA-14311 ORA-14311, 00000, “Expecting VALUES LESS THAN or AT clause” Cause: VALUES (<value list>) clause can be used only with List partitioned tables Action: Use VALUES LESS THAN clause with Range partitioned tables |
| ORA-14312 ORA-14312, 00000, “Value %s already exists in partition %s” Cause: One of the list values in the ADD PARTITION or ADD VALUES // statement already exists in another partition Action: Remove the duplicate value from the statement and try again |
| ORA-14313 ORA-14313, 00000, “Value %s does not exist in partition %s” Cause: One of the list values in the SPLIT PARTITION or DROP VALUES // statement does not exist in the partition Action: Remove the value from the statement and try again |
| ORA-14314 ORA-14314, 00000, “resulting List partition(s) must contain atleast 1 value” Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value Action: Ensure that each of the resulting partitions contains atleast 1 value |
| ORA-14315 ORA-14315, 00000, “cannot merge a partition with itself” Cause: The same partition name was specified twice for the merge operation Action: Re-submit operation with 2 distinct partition names |
| ORA-14316 ORA-14316, 00000, “table is not partitioned by List method” Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects Action: Re-issue the command against a List partitioned object. |
| ORA-14317 ORA-14317, 00000, “cannot drop the last value of partition” Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition Action: Cannot execute the command, unless two or more values exist for partition |
| ORA-14318 ORA-14318, 00000, “DEFAULT partition must be last partition specified” Cause: A partition description follows the one describing the default partition Action: Ensure that the DEFAULT partition is the last partition description |
| ORA-14319 ORA-14319, 00000, “DEFAULT cannot be specified with other values” Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition Action: Ensure that if DEFAULT is specified, it is the only value specified |
| ORA-14320 ORA-14320, 00000, “DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT” Cause: DEFAULT keyword has been specified when doing a ADD VALUES or DROP VALUES or SPLIT partition or subpartition. Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operation. |
| ORA-14321 ORA-14321, 00000, “cannot add/drop values to DEFAULT partition” Cause: A ADD/DROP VALUES operation is being done on the default partition Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition |
| ORA-14322 ORA-14322, 00000, “DEFAULT partition already exists” Cause: A partition already exists with DEFAULT value Action: |
| ORA-14323 ORA-14323, 00000, “cannot add partition when DEFAULT partition exists” Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists Action: Issue a SPLIT of the DEFAULT partition instead |
| ORA-14324 ORA-14324, 00000, “values being added already exist in DEFAULT partition” Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added |
| ORA-14325 ORA-14325, 00000, “only LOCAL indexes may be specified in this clause” Cause: A global index has been specified in the UPDATE INDEXES (..) clause Action: Only specify local indexes when using this clause |
| ORA-14326 ORA-14326, 00000, “Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause” Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified in the UPDATE INDEXES (..) clause Action: Do not specify any of these indexes when using this clause |
| ORA-14327 ORA-14327, 00000, “Some index [sub]partitions could not be rebuilt” Cause: The first phase (partition DDL and index [sub]partition placement) completed successfully. During the second phase, some of the index [sub]partitions could not be rebuilt. Action: Search the alert log for the string DBMS_INDEX_UTL. Check the error associated with each of the [sub]partitions that could not be rebuilt and take the appropriate corrective action. |
| ORA-14328 ORA-14328, 00000, “Allow UPDATE INDEXES clause for PIOTs. To be used for testing” Document: NO Cause: Action: // Level 1+ Allow UPDATE INDEXES clause for IOTs. |
| ORA-14329 ORA-14329, 00000, “domain index [sub]partitions cannot be renamed in this clause” Cause: The user tried to rename a domain index [sub]partition in the UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not allowed. Action: Leave the name blank or use the same name. |
| ORA-14330 ORA-14330, 00000, “Cannot drop a partition of a global hash-partitioned index” Cause: An attempt was made to drop a partition of a hash-partitioned global index. Action: Try COALESCE PARTITION instead. |
| ORA-14400 ORA-14400, 00000, “inserted partition key does not map to any partition” Cause: An attempt was made to insert a record into, a Range or Composite Range object, with a concatenated partition key that is beyond the concatenated partition bound list of the last partition -OR- An attempt was made to insert a record into a List object with a partition key that did not match the literal values specified for any of the partitions. Action: Do not insert the key. Or, add a partition capable of accepting the key, Or add values matching the key to a partition specification |
| ORA-14401 ORA-14401, 00000, “inserted partition key is outside specified partition” Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement Action: do not insert the key or insert it in another partition |
| ORA-14402 ORA-14402, 00000, “updating partition key column would cause a partition change” Cause: An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition Action: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key. |
| ORA-14403 ORA-14403, 00000, “cursor invalidation detected after getting DML partition lock” Cause: cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. This error is never returned to user, because is caught in opiexe() and the DML statement is retried. Action: nothing to be done, error should never be returned to user |
| ORA-14404 ORA-14404, 00000, “partitioned table contains partitions in a different tablespace” Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace Action: find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace |
| ORA-14405 ORA-14405, 00000, “partitioned index contains partitions in a different tablespace” Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. Action: find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. |
| ORA-14406 ORA-14406, 00000, “updated partition key is beyond highest legal partition key” Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition. Action: Do not update the key. Or, add a partition capable of accepting the key. |
| ORA-14407 ORA-14407, 00000, “partitioned table contains subpartitions in a different tablespace” Cause: An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace Action: find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace |
| ORA-14408 ORA-14408, 00000, “partitioned index contains subpartitions in a different tablespace” Cause: An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. Action: find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. |
| ORA-14409 ORA-14409, 00000, “inserted partition key is outside specified subpartition” Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement Action: do not insert the key or insert it in another subpartition |
| ORA-14410 ORA-14410, 00000, “RPI LOCK TABLE issued to table referenced through synonym” Document: NO Cause: RPI LOCK TABLE statement was issued to acquire DML locks before KGL locks for a table referenced through a synonym. This error is never returned to user. Action: nothing to be done, error should never be returned to user |
| ORA-14411 ORA-14411, 00000, “The DDL cannot be run concurrently with other DDLs” Cause: Another conflicting DDL was already running. Action: Retry after the conflicting DDL has finished. |
| ORA-14450 ORA-14450, 00000, “attempt to access a transactional temp table already in use” Cause: An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session. Action: do not attempt to access the temporary table until the concurrent transaction has committed or aborted. |
| ORA-14451 ORA-14451, 00000, “unsupported feature with temporary table” Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause. Action: do not do that. |
| ORA-14452 ORA-14452, 00000, “attempt to create, alter or drop an index on temporary table already in use” Cause: An attempt was made to create, alter or drop an index on temporary table which is already in use. Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions. |
| ORA-14453 ORA-14453, 00000, “attempt to use a LOB of a temporary table, whose data has alreadybeen purged” Cause: An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has commited or aborted, table was truncated or session which created this LOB has ended. Action: This LOB locator is invalid and cannot be used. |
| ORA-14454 ORA-14454, 00000, “attempt to reference temporary table in a referential integrity constraint” Cause: An attempt was made to reference temporary table in a referencial integrity constraint. This is not supported. Action: Use triggers. |
| ORA-14455 ORA-14455, 00000, “attempt to create referential integrity constraint on temporary table” Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported. Action: Use triggers. |
| ORA-14456 ORA-14456, 00000, “cannot rebuild index on a temporary table” Cause: An attempt was made to rebuild an index on a temp table. Action: The index data is anyway lost at end of session/transaction. |
| ORA-14457 ORA-14457, 00000, “disallowed Nested Table column in a Temporary table” Cause: An attempt made to create a Nested Table column in a temporary table. This is not supported. Action: Do not specify these datatypes for temporary tables. |
| ORA-14458 ORA-14458, 00000, “attempt was made to create a temporary table with INDEX organization” Cause: An attempt was made to create an Index Organized Temporary table. This is not supported. Action: Create the table with HEAP organization and the primary key. |
| ORA-14459 ORA-14459, 00000, “missing GLOBAL keyword” Cause: keyword GLOBAL is missing while creating temporary table. Action: supply keyword. |
| ORA-14460 ORA-14460, 00000, “only one COMPRESS or NOCOMPRESS clause may be specified” Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified. Action: specify each desired COMPRESS or NOCOMPRESS clause option only once. |
| ORA-14461 ORA-14461, 00000, “cannot REUSE STORAGE on a temporary table TRUNCATE” Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table. This is unsupported as it is meaningless. Action: Specify DROP STORAGE instead (which is the default). |
| ORA-14462 ORA-14462, 00000, “cannot TRUNCATE temporary table in an autonomous transaction which is already in use by the parent transaction” Cause: An attempt was made to TRUNCATE a temporary table in an autonomous transaction which is already in use by the parent transaction. Action: Make sure the temporary table is not being used by the parent transaction before trying to TRUNCATE in an autonomous transaction. |
| ORA-14463 ORA-14463, 00000, “OPERATIONS keyword not specified” Cause: OPERATIONS keyword was not specified in the Compression Clause. Action: specify OPERATIONS in the Compression Clause. |
| ORA-14464 ORA-14464, 00000, “Compression Type not specified” Cause: Compression Type was not specified in the Compression Clause. Action: specify Compression Type in the Compression Clause. |
| ORA-14500 ORA-14500, 00000, “LOCAL option not valid without partition name” Cause: Incorrect syntax specified Action: Retry the command |
| ORA-14501 ORA-14501, 00000, “object is not partitioned” Cause: Table or index is not partitioned. Invalid syntax. Action: Retry the command with correct syntax. |
| ORA-14503 ORA-14503, 00000, “only one partition name can be specified” Cause: More than one partition name has been specified for analyze Action: Specify one partition name. |
| ORA-14504 ORA-14504, 00000, “syntax not supported for analyze” Cause: A partition/subpartition number or bind variable has been used Action: Specify a valid partition/subpartition name. |
| ORA-14505 ORA-14505, 00000, “LOCAL option valid only for partitioned indexes” Cause: Incorrect syntax specified Action: Retry the command |
| ORA-14506 ORA-14506, 00000, “LOCAL option required for partitioned indexes” Cause: Incorrect syntax specified Action: Retry the command |
| ORA-14507 ORA-14507, 00000, “partition corrupt. all rows do not fall within partition bounds” Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation Action: Delete rows in partition which do not qualify |
| ORA-14508 ORA-14508, 00000, “specified VALIDATE INTO 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-14509 ORA-14509, 00000, “specified VALIDATE INTO table form incorrect” Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. See utlvalid.sql for more information. |
| ORA-14510 ORA-14510, 00000, “can specify VALIDATE INTO clause only for partitioned tables” Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster or index. Action: Use syntax correctly |
| ORA-14511 ORA-14511, 00000, “cannot perform operation on a partitioned object” Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes. Action: Retry the command with correct syntax. |
| ORA-14512 ORA-14512, 00000, “cannot perform operation on a clustered object” Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes. Action: Retry the command with correct syntax. |
| ORA-14513 ORA-14513, 00000, “partitioning column may not be of object datatype” Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal. Action: Ensure that no partitioning column is an object datatype. |
| ORA-14514 ORA-14514, 00000, “LOCAL option not valid without subpartition name” Cause: Incorrect syntax specified Action: Retry the command |
| ORA-14515 ORA-14515, 00000, “only one aubpartition name can be specified” Cause: More than one subpartition name has been specified for analyze Action: Specify one subpartition name. |
| ORA-14516 ORA-14516, 00000, “subpartition corrupt. all rows do not fall within subpartition bounds” Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation Action: Delete rows in subpartition which do not qualify |
| ORA-14517 ORA-14517, 00000, “subpartition of index ‘%s.%s’ is in unusable state” Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation Action: REBUILD the unusable index subpartition |
| ORA-14518 ORA-14518, 00000, “partition contains rows corresponding to values being dropped” Cause: table partition contains rows for the values being dropped. Action: DELETE all rows for the values being dropped and reissue statement |
| ORA-14519 ORA-14519, 00000, “Conflicting tablespace blocksizes for %s %s: Tablespace %s block size %s [%s] conflicts with previously specified/implied tablespace %s block size %s [%s]” Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size. Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size. |
| ORA-14520 ORA-14520, 00000, “Tablespace %s block size [%s] does not match existing object block size [%s]” Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object’s default tablespace (or one of the object’s partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object’s partitions/subpartitions. Action: Specify a tablespace of the same block size as the partitioned object. |
| ORA-14521 ORA-14521, 00000, “Default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]” Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object. Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. |
| ORA-14522 ORA-14522, 00000, “Partition-level default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]” Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object. Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created. |
| ORA-14523 ORA-14523, 00000, “Cannot co-locate [sub]partition of %s %s with table [sub]partition because %s block size [%s] does not match table block size [%s]” Cause: A DDL statement was issued that would require a partition/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/local index are different. Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table. |
| ORA-14524 ORA-14524, 00000, “Always allow partitioning. To be used only by trusted clients” Document: NO Cause: Action: // Level 1+ Allow partitioning irrespective of edition. |
| ORA-14525 ORA-14525, 00000, “Fast Split event” Document: NO Cause: Action: // Level Action 0×0001 Dont try fast split 0×0002 Tracing for why fast split failed |
| ORA-14526 ORA-14526, 00000, “This event is no longer used.” Document: NO Cause: Action: However don’t reuse the event because there might be installations have it set. |
| ORA-14527 ORA-14527, 00000, “Allow ROWID datatype for partitioning key columns” Document: NO Cause: Action: Level 1+ Allow partitioning on columns having ROWID datatype. Note: remove this event once we fully support partitioning on columns with ROWID datatype in 10g+. |
| ORA-14528 ORA-14528, 00000, “simulated crash during drop table optimization” Document: NO Cause: Oracle internal testing only Action: Never set this event (to be used only for internal testing) |
| ORA-14529 ORA-14529, 00000, “copy hakan factor during ctas at facilitate exchange partition” Document: NO Cause: Oracle internal testing only Action: Never set this event unless running into bug 3747472 |
| ORA-14530 ORA-14530, 00000, “row mismatches found in table %s.%s and index %s.%s” Document:YES Cause: rows in table and index inconsistent Action: run complete analyze to determine corrupt rows |
| ORA-14531 ORA-14531, 00000, “Event to enable Hash composite partitioning for 11.0.0.0″ Document: NO Cause: Oracle internal testing only Action: Never set this event (to be used only for internal testing) |
| ORA-14532 ORA-14532, 00000, “Event for bug 5618049″ Document: NO Cause: Needs to be set to turn on fix for 5618049 Action: |
| ORA-14533 ORA-14533, 00000, “Event for ALTER TABLE enhancements for code point semantics” Document: NO Cause: Action: Needs to be set to turn on fix for bug 5952255 |
| ORA-14534 ORA-14534, 00000, “Event for bug 5996430 fix to be turned on” Document: NO Cause: Action: Needs to be set to turn on fix for bug 5996430 |
| ORA-14536 ORA-14536, 00000, “Event to turn on row movement during CREATE TABLE” Document: NO Cause: Action: |
| ORA-14551 ORA-14551, 00000, “cannot perform a DML operation inside a query ” Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave. Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave. |
| ORA-14552 ORA-14552, 00000, “cannot perform a DDL, commit or rollback inside a query or DML ” Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement. Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation. |
| ORA-14553 ORA-14553, 00000, “cannot perform a lob write operation inside a query ” Cause: A lob write operation cannot be performed inside a query or a PDML slave. Action: Ensure that the offending lob write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave. |
| ORA-14554 ORA-14554, 00000, “cannot perform requested operation during database startup ” Cause: Requested operation requires the Cost Based Optimizer(CBO) which is not available during database startup. Features like partitioning, IOTs, grouping sets, and flashback cursor require the CBO. Action: Retry the query after the database is open. |
| ORA-14601 ORA-14601, 00000, “Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template” Cause: Cannot specify these clauses while specifying a template Action: Correct the subpartition template clause. |
| ORA-14602 ORA-14602, 00000, “SUBPARTITION TEMPLATE is legal only for a composite partitioned table” Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned tables Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables. |
| ORA-14603 ORA-14603, 00000, ” [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables” Cause: This syntax is valid only if subpartitioning dimension is hash Action: |
| ORA-14604 ORA-14604, 00000, “During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified” Cause: Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else Action: Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause |
| ORA-14605 ORA-14605, 00000, “Name missing for subpartition / lob segment in template” Cause: A subpartition / lob segment was not specified a name in the template descriptions Action: All subpartitions / lob segments must have names specified in the template |
| ORA-14606 ORA-14606, 00000, “Tablespace was specified for previous subpartitions in template but is not specified for %s” Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions Action: Either specify tablespaces for all or for none of the subpartitions |
| ORA-14607 ORA-14607, 00000, “Tablespace was not specified for previous subpartitions in template but is specified for %s” Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions Action: Either specify tablespaces for all or for none of the subpartitions |
| ORA-14608 ORA-14608, 00000, “Tablespace was specified for the previous lob segments of column %s in template but is not specified for %s” Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column Action: Either specify tablespaces for all or for none of the lob segments |
| ORA-14609 ORA-14609, 00000, “Tablespace was not specified for the previous lob segments of column %s in template but is specified for %s” Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column Action: Either specify tablespaces for all or for none of the lob segments |
| ORA-14610 ORA-14610, 00000, “Lob attributes not specified for lob column %s for subpartition %s” Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all |
| ORA-14611 ORA-14611, 00000, “Duplicate subpartition name %s in template” Cause: A subpartition name cannot be duplicated within the template Action: Rename one of the subpartitions. |
| ORA-14612 ORA-14612, 00000, “Duplicate lob segment name %s for lob column %s in template” Cause: Two lob segments of the same column were given the same name in the template Action: Rename one of the lob segments |
| ORA-14613 ORA-14613, 00000, “Attempt to generate name from parent name %s and template name %s failed as the combine named would have been longer than allowed” Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier Action: Shorten either partition or template name. |
| ORA-14614 ORA-14614, 00000, “List value ‘%s’ specified twice in subpartition ‘%s’” Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value |
| ORA-14615 ORA-14615, 00000, “List value ‘%s’ specified twice in subpartitions ‘%s’, ‘%s’” Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value |
| ORA-14616 ORA-14616, 00000, “table is not subpartitioned by List method” Cause: A subpartition maintenance operation, such as ALTER TABLE MODIFY SUBPARTITION ADD|DROP VALUES, was performed on a non-List subpartitioned object. Action: Reissue the command against a List subpartitioned object. |
| ORA-14617 ORA-14617, 00000, “cannot add/drop values to DEFAULT subpartition” Cause: A ADD/DROP VALUES operation is being done on the default subpartition Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition |
| ORA-14618 ORA-14618, 00000, “cannot drop the last value of subpartition” Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition Action: Cannot execute the command, unless two or more values exist for subpartition |
| ORA-14619 ORA-14619, 00000, “resulting List subpartition(s) must contain at least 1 value” Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value Action: Ensure that each of the resulting subpartitions contains atleast 1 value |
| ORA-14620 ORA-14620, 00000, “DEFAULT subpartition already exists” Cause: A subpartition already exists with DEFAULT value Action: Remove the DEFAULT value from the list specified |
| ORA-14621 ORA-14621, 00000, “cannot add subpartition when DEFAULT subpartition exists” Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists Action: Issue a SPLIT of the DEFAULT subpartition instead |
| ORA-14622 ORA-14622, 00000, “Value %s already exists in subpartition %s” Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES // statement already exists in another subpartition Action: Remove the duplicate value from the statement and try again |
| ORA-14623 ORA-14623, 00000, “Value %s does not exist in subpartition %s” Cause: One of the list values in the SPLIT PARTITION or DROP VALUES // statement does not exist in the subpartition Action: Remove the value from the statement and try again |
| ORA-14624 ORA-14624, 00000, “DEFAULT subpartition must be last subpartition specified” Cause: A subpartition description follows the one describing the default subpartition Action: Ensure that the DEFAULT subpartition is the last subpartition description |
| ORA-14625 ORA-14625, 00000, “subpartition contains rows corresponding to values being dropped” Cause: table subpartition contains rows for the values being dropped. Action: DELETE all rows for the values being dropped and reissue statement |
| ORA-14626 ORA-14626, 00000, “values being added already exist in DEFAULT subpartition” Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added |
| ORA-14627 ORA-14627, 00000, “Invalid operation was specified on a GLOBAL partitioned index” Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned |
| ORA-14628 ORA-14628, 00000, “specification of bounds is inconsistent with LIST method” Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions |
| ORA-14629 ORA-14629, 00000, “cannot drop the only subpartition of a partition” Cause: A drop subpartition command is being executed when there is only one subpartition in the partition |
| ORA-14630 ORA-14630, 00000, “subpartition resides in offlined tablespace” Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. |
| ORA-14631 ORA-14631, 00000, “the partition bounds do not match the subpartition bounds of the partition” Cause: When exchanging a partitioned table with a composite partition the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition. Action: Ensure that the bounds describing partitions in the partitioned table is the same as the bounds of the subpartitions in the the composite partition. |
| ORA-14632 ORA-14632, 00000, “cannot specify PARALLEL clause when adding a List subpartition” Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL clause for a List subpartition of a Range/List partitioned object which is illegal Action: Remove the PARALLEL clause. |
| ORA-14633 ORA-14633, 00000, “Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table” Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table. Action:Remove clause and reissue operation |
| ORA-14634 ORA-14634, 00000, “Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table” Cause: During a split or a merge of a partition of a range list partitioned table you cannot specify any subpartitioning information for the resulting partition (s) Action: Remove all subpartitioning information from the DDL. |
| ORA-14635 ORA-14635, 00000, “only one resulting subpartition can be specified for MERGE SUBPARTITIONS” Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE Action: Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd |
| ORA-14636 ORA-14636, 00000, “only 2 resulting subpartition can be specified for SPLIT SUBPARTITION” Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation |
| ORA-14637 ORA-14637, 00000, “cannot merge a subpartition with itself” Cause: The same subpartition name was specified twice for the merge operation Action: Re-submit operation with 2 distinct subpartition names within the same composite partition |
| ORA-14638 ORA-14638, 00000, “cannot MERGE subpartitions in different Range Composite partitions” Cause: Attempted to MERGE subpartitions in different Range Composite partitions Action: Reissue the command after ensuring that the 2 subpartitions being merged lie in the same composite partition |
| ORA-14639 ORA-14639, 00000, “SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition” Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method Action: Reissue the command after ensuring that the SUBPARTITIONS clause is not specified, to specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause |
| ORA-14640 ORA-14640, 00000, “add/coalesce index partition operation is valid only for hash partitioned global indexes” Cause: User attempted to add or coalesce an index partition of a global index not partitioned by hash method. Action: Issue the statement on a global index partitioned by hash method. or if the index is partitioned by range method consider using split/drop instead of add/coalesce. |
| ORA-14641 ORA-14641, 00000, “STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition” Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed” Action: Re-issue the stament after removing the STORE-IN clause |
| ORA-14642 ORA-14642, 00000, “Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION” Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors. Action: Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable. |
| ORA-14643 ORA-14643, 00000, “Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION” Cause: Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal. Action: If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables. |
| ORA-14644 ORA-14644, 00000, “table is not subpartitioned by Hash method” Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects Action: Re-issue the command against a Hash subpartitioned object. |
| ORA-14645 ORA-14645, 00000, “STORE IN clause cannot be specified for Range List objects” Cause: A STORE IN clause was specified for Range List partitioned object Action: Re-issue the command after removng the STORE IN clause |
| ORA-14646 ORA-14646, 00000, “Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes” Cause: The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction. Action: A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete. |
| ORA-14650 ORA-14650, 00000, “operation not supported for reference-partitioned tables” Cause: Attempted to perform an operation on a reference-partitioned table that was not supported. Action: Do not perform the unsupported operation. |
| ORA-14651 ORA-14651, 00000, “reference partitioning constraint is not supported” Cause: The specified partitioning constraint was not supported for reference-partitioned tables. The partitioning constraint must be enabled, validated, and not deferrable. The partitioning constraint must not have ON DELETE SET NULL semantics. Action: Correct the statement to specify a supported partitioning constraint. |
| ORA-14652 ORA-14652, 00000, “reference partitioning foreign key is not supported” Cause: The specified partitioning foreign key was not supported for reference-partitioned tables. All columns of the partitioning foreign key must be constrained NOT NULL with enabled, validated, and not deferrable constraints. Furthermore, a virtual column cannot be part of the partitioning foreign key. Action: Correct the statement to specify a supported partitioning foreign key. |
| ORA-14653 ORA-14653, 00000, “parent table of a reference-partitioned table must be partitioned” Cause: Attempted to create a reference-partitioned table with a non-partitioned parent table. Action: Correct the statement and reenter. |
| ORA-14654 ORA-14654, 00000, “number of partitions of reference-partitioned table must equal that of the parent table” Cause: Attempted to create a reference-partitioned table with a number of partitions which was different from that of the parent table. Action: Correct the CREATE TABLE statement to specify a correct number of partitions. |
| ORA-14655 ORA-14655, 00000, “reference partitioning constraint not found” Cause: Partitioning constraint specified in CREATE TABLE … PARTITION BY REFERENCE was not one of the referential constraints on the table being created. Action: Ensure that the specified partitioning constraint is one of the referential constraints on the table being created. |
| ORA-14656 ORA-14656, 00000, “cannot drop the parent of a reference-partitioned table” Cause: Attempted to drop the parent of a reference-partitioned table. Action: Drop all reference-partitioned child tables before dropping the parent table. |
| ORA-14657 ORA-14657, 00000, “cannot cascade row migration to reference-partitioned child table” Cause: Update of a parent key may require migration of rows in reference-partitioned child tables, however this is not supported because the parent key was not suitably indexed. Action: Replace the existing index on the parent key with a unique index that does not contain any columns in addition to the parent key. |
| ORA-14658 ORA-14658, 00000, “specified dependent table is not affected by this operation” Cause: A table has been specified in the DEPENDENT TABLES clause that is not a reference-partitioned table affected by the operation. Action: Correct the statement and reenter. |
| ORA-14659 ORA-14659, 00000, “Partitioning method of the parent table is not supported” Cause: An attempt was made to create a reference-partitioned table with an interval partitioned parent table. Action: Do not create a reference-partitioned table with an interval partitioned parent table. |
| ORA-14660 ORA-14660, 00000, “parent table of a reference-partitioned table cannot be index-organized” Cause: Attempted to create a reference-partitioned table with a index-organized parent table. Action: Correct the statement and reenter. |
| ORA-14661 ORA-14661, 00000, “row movement must be enabled” Cause: Attempted to disable row movement for a reference-partitioned table, although row movement was enabled for its parent table. Action: Disable row movement for parent table before disabling row movement for the reference-partitioned table. |
| ORA-14662 ORA-14662, 00000, “row movement cannot be enabled” Cause: Attempted to enable row movement for a partitioned table, although row movement was disabled for a reference-partitioned child table. Action: Enable row movement for reference-partitioned child tables before enabling row movement for the parent table. |
| ORA-14663 ORA-14663, 00000, “reference partitioning parent key is not supported” Cause: Parent key of the reference-partitioned table’s partitioning constraint contained virtual columns. Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter. |
| ORA-14700 ORA-14700, 00000, “Object(s) owned by SYS cannot be locked by non-SYS user” Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML privileges on object, or non-SYS user should connect as SYS |
| ORA-14701 ORA-14701, 00000, “partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method” Cause: User attempted not to use partition-extended syntax for a table partitioned by the System method Action: Must use of partition-extended syntax in contexts mentioned above. |
| ORA-14702 ORA-14702, 00000, “The partition number is invalid or out-of-range” Cause: Attempted to use nonnumerical value or the number was out of range of the partitions. Action: Use a valid partition number. |
| ORA-14703 ORA-14703, 00000, “The AFTER clause can be used to ADD PARTITION only to a System Partitioned table.” Cause: The table is not partitioned by the System method Action: Skip the AFTER clause. |
| ORA-14704 ORA-14704, 00000, “Create table as select disallowed for SYSTEM patitioned tables” Cause: User attempted to create a SYSTEM partitioned table by doing a create table as select. Action: Do a create table followed by an insert as select into each partition. |
| ORA-14750 ORA-14750, 00000, “Range partitioned table with INTERVAL clause has more than one column” Cause: You attempted to create an interval partitioned table with more than one partitioning column. Action: Use a single partitioning column. |
| ORA-14751 ORA-14751, 00000, “Invalid data type for partitioning column of an interval partitioned table” Cause: You attempted to use interval partitioning on a table partitioned on a column of data type other than number or date/time. Action: Use only number or date/time columns as partitioning columns for interval partitioned tables. |
| ORA-14752 ORA-14752, 00000, “Interval expression is not a constant of the correct type” Cause: You attempted to use either a nonconstant interval or an interval whose data type does not correspond to the partitioning column Action: Use only constant expressions for the interval. If the data type of partitioning column is numeric, the interval must be a numeric constant. If the data type is of type date/time, the interval must be a constant of interval type |
| ORA-14753 ORA-14753, 00000, “Interval cannot be zero” Cause: The interval mapped to zero. Action: You must use a nonzero interval. |
| ORA-14754 ORA-14754, 00000, “Interval string is too long” Cause: The interval string was too long Action: Specify interval using a shorter string |
| ORA-14755 ORA-14755, 00000, “Invalid partition specification for FOR VALUES clause.” Cause: The [SUB]PARTITION FOR VALUES (…) clause can only take constants. In addition it takes as many arguments as there are partitioning columns and the values must be coercible to the partitioning columns. Action: Specify a valid FOR VALUES clause. |
| ORA-14756 ORA-14756, 00000, “Table is not partitioned by Interval method.” Cause: The table was not partitioned by Interval method. Action: ALTER TABLE SET STORE IN is only valid for Interval partitioned tables. Ensure that the table by Interval. |
| ORA-14757 ORA-14757, 00000, “Table is already a range partitioned table” Cause: SET INTERVAL () is used to convert an interval partitioned table to a range partitioned table. It is not legal on a range partitioned table Action: Use SET INTERVAL () only on an interval partitioned table. |
| ORA-14758 ORA-14758, 00000, “Last partition in the range section cannot be dropped” Cause: An attempt was made to drop the last range partition of an interval partitioned table. Action: Do not attempt to drop this partition. |
| ORA-14759 ORA-14759, 00000, “SET INTERVAL is not legal on this table.” Cause: ALTER TABLE SET INTERVAL is only legal on a range partitioned table with a single partitioning column. Additionally this table cannot have a maxvalue partition. Action: Use SET INTERVAL only on a valid table |
| ORA-14760 ORA-14760, 00000, “ADD PARTITION is not permitted on Interval partitioned objects” Cause: ALTER TABLE ADD PARTITION was attempted on an Interval partitioned object. Action: Do not perform the operation on an Interval partitioned object. Insert a row to create the new partition. |
| ORA-14761 ORA-14761, 00000, “MAXVALUE partition cannot be specified for Interval partitioned objects” Cause: An attempt was made to create a partition with a MAXVALUE highbound on an Interval partitioned object. Action: Do not create a partition with a MAXVALUE highbound. |
| ORA-14762 ORA-14762, 00000, “Domain index creation on interval partitioned tables is not permitted” Cause: An attempt was made to create a domain index on an interval partitioned table. Action: Do not create a domain index on an interval partitioned table. |
| ORA-14763 ORA-14763, 00000, “Unable to resolve FOR VALUES clause to a partition number” Cause: Could not determine the partition corresponding to the FOR VALUES clause. Action: Remove bind variables and dependencies on session parameters from the values specified in the FOR VALUES clause. |
| ORA-14764 ORA-14764, 00000, “FOR VALUES clause cannot be specified for only one partition” Cause: An attempt was made to specify the FOR VALUES clause for only one of the two partitions being merged. Action: Specify a FOR VALUES clause for each of the two partitions being merged or do not specify the FOR VALUES clause for either. |
| ORA-14765 ORA-14765, 00000, “Cannot create a partition while doing a create index” Cause: An attempt was made to create a partition concurrently with index creation. Action: Retry the statement after the index build is finished. |
| ORA-14766 ORA-14766, 00000, “Unable to obtain a stable metadata snapshot” Cause: This operation was not able to obtain a stable snapshot of the interval partitioning metadata. Action: Retry the statement. |
| ORA-14767 ORA-14767, 00000, “Cannot specify this interval with existing high bounds” Cause: The interval specified conflicts with the existing high bound for the last partition. The combination might lead to invalid dates for high bounds in the future. Action: If this is a CREATE TABLE, try specifying a different high bound value for the last partition, or a different interval. If this is an ALTER TABLE SET INTERVAL, please choose either a different interval, or, modify the table to change the high bound for the last partition. |
| ORA-14768 ORA-14768, 00000, “Error Loading Versioned object” Document: NO Cause: Internal Error. Should never be returned to user Action: If seen by user report to Oracle support. |
| ORA-14799 ORA-14799, 00000, “Temporary interval error %s, %s” Document: NO Cause: Ignore Action: Ignore |
| ORA-14801 ORA-14801, 00000, “Hash composite partitioning is not supported” Cause: An attempt was made to partition a table using a Hash composite method. Action: Do not partition the table by a Hash composite method. |
| ORA-14802 ORA-14802, 00000, “Specified operation is not permitted on Hash composite partitioned objects” Cause: An unsupported operation was attempted on a Hash composite partitioned object. Action: Do not perform the operation on a Hash composite partitioned object. |
| ORA-14803 ORA-14803, 00000, “partition bound may not be specified for hash subpartitioned tables” Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition description. Action: Remove the VALUES LESS THAN or VALUES clause from the subpartition description. |
| ORA-15000 ORA-15000, 00000, “command disallowed by current instance type” Cause: The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance. Action: Connect to the correct instance type and re-issue the command. // |
| ORA-15001 ORA-15001, 00000, “diskgroup \”%s\” does not exist or is not mounted” Cause: An operation failed because the diskgroup specified does not exist or is not mounted by the current ASM instance. Action: Verify that the diskgroup name used is valid, that the diskgroup exists, and that the diskgroup is mounted by the current ASM instance. // |
| ORA-15002 ORA-15002, 00000, “parameter LOCK_NAME_SPACE exceeds limit of %s characters” Cause: The LOCK_NAME_SPACE initialization parameter contained a value that is too long. Action: Correct the LOCK_NAME_SPACE initialization parameter. // |
| ORA-15003 ORA-15003, 00000, “diskgroup \”%s\” already mounted in another lock name space” Cause: The diskgroup could not be mounted by the ASM instance because it was operating in a lockspace different than another existing ASM instance which had already mounted the diskgroup. Action: Check the LOCK_NAME_SPACE initialization parameter value, or dismount the diskgroup from the other ASM instances. // |
| ORA-15004 ORA-15004, 00000, “alias \”%s\” does not exist” Cause: The specified alias did not exist within the diskgroup. Action: Check the alias name and diskgroup name. // |
| ORA-15005 ORA-15005, 00000, “name \”%s\” is already used by an existing alias” Cause: An existing alias in the diskgroup used the same name. Action: Select another alias name, or drop the existing alias. // |
| ORA-15006 ORA-15006, 00000, “template \”%s\” does not exist” Cause: The specified template did not exist within the diskgroup. Action: Check the template name and diskgroup name. // |
| ORA-15007 ORA-15007, 00000, “name is already used by an existing template” Cause: A template with the same name already exists. Action: Select another template name, or drop the existing template. // |
| ORA-15008 ORA-15008, 00000, “cannot drop system template” Cause: The specified template was created by the system and must always exist for proper operation. Action: Select another template name. // |
| ORA-15009 ORA-15009, 00000, “ASM disk \”%s\” does not exist” Cause: The specified ASM disk was not found. Action: Check the ASM disk name. // |
| ORA-15010 ORA-15010, 00000, “name ‘%s’ is already used by an existing ASM disk” Cause: The specified name was already used in this diskgroup. Action: Specify a different ASM disk name. // |
| ORA-15011 ORA-15011, 00000, “failure group \”%s\” does not exist in diskgroup \”%s\”" Cause: The specified name did not match the failure group of any disks in the diskgroup. This usually indicates that the failure group name was specified incorrectly. Action: Check the failure group name. // |
| ORA-15012 ORA-15012, 00000, “ASM file ‘%s’ does not exist” Cause: The ASM file was not found. Action: Check the ASM file name. // |
| ORA-15013 ORA-15013, 00000, “diskgroup \”%s\” is already mounted” Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup which is already mounted by the current ASM instance. Action: Check the name of the diskgroup. // |
| ORA-15014 ORA-15014, 00000, “path ‘%s’ is not in the discovery set” Cause: The operating system path specified was outside the set of disks that are discovered by the instance. Action: Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter. // |
| ORA-15015 ORA-15015, 00000, “Specified path ‘%s’ conflicts with path ‘%s’” Cause: The ASM instance previously discovered specified disk with an ASM library using a different path. Action: Use the discovery string of the ASM library to add the disk. // |
| ORA-15016 ORA-15016, 00000, “inconsistent respecification of path ‘%s’” Cause: The specified path was provided more than once with different properties. Action: Do not provide a path more than once. Alternatively, provide consistent properties. // |
| ORA-15017 ORA-15017, 00000, “diskgroup \”%s\” cannot be mounted” Cause: The specified diskgroup could not be mounted. Action: Check for additional errors reported. // |
| ORA-15018 ORA-15018, 00000, “diskgroup cannot be created” Cause: The specified diskgroup could not be created. Action: Check for additional errors reported. // |
| ORA-15019 ORA-15019, 00000, “discovered duplicate path ‘%s’ for ‘%s’” Cause: The discovery encountered multiple paths to the same disk. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. // |
| ORA-15020 ORA-15020, 00000, “discovered duplicate ASM disk \”%s\”" Cause: The discovery encountered two disks claiming to be the same named ASM disk. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. // |
| ORA-15021 ORA-15021, 00000, “parameter \”%s\” is not valid in %s instance” Cause: The specified parameter was not supported when starting an instance of this type. Action: Delete the specified parameter from the INIT.ORA file. |
| ORA-15023 ORA-15023, 00000, “reached maximum allowable number of disks %s” Cause: An attempt was made to add another disk to a diskgroup which already contains the maximum number of disks allowed. Action: Consider dropping existing disks from the diskgroup before adding additional ones, or create a new diskgroup. // |
| ORA-15024 ORA-15024, 00000, “discovered duplicately numbered ASM disk %s” Cause: The discovery encountered two disks claiming to have the same ASM disk number. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. // |
| ORA-15025 ORA-15025, 00000, “could not open disk ‘%s’” Cause: The specified disk could not be opened. Action: Check the additional error messages, if any. |
| ORA-15026 ORA-15026, 00000, “disk ‘%s’ is not an ASM disk” Cause: The disk did not contain a valid ASM disk header. Action: Check to see if the data on the disk has been changed by some system administrator action. // |
| ORA-15027 ORA-15027, 00000, “active use of diskgroup \”%s\” precludes its dismount” Cause: An ALTER DISKGROUP … DISMOUNT command specified a diskgroup which had database client instances with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed by the database client instances. Action: Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP … DISMOUNT command. The V$ASM_CLIENT fixed view in an ASM instance provides a list of its active database client instances. // |
| ORA-15028 ORA-15028, 00000, “ASM file ‘%s’ not dropped; currently being accessed” Cause: An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped. Action: Shut down all database instances that might be accessing this file and then retry the drop command. // |
| ORA-15029 ORA-15029, 00000, “disk ‘%s’ is already mounted by this instance” Cause: An attempt was made to add to a diskgroup a disk that was already mounted by the current instance as part of some (possibly other) diskgroup. Action: Specify a different disk in the command. Note that not even the FORCE option can be used to correct the situation until the diskgroup containing the disk becomes dismounted by this instance. // |
| ORA-15030 ORA-15030, 00000, “diskgroup name \”%s\” is in use by another diskgroup” Cause: A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup. Action: Select a different name for the diskgroup. // |
| ORA-15031 ORA-15031, 00000, “disk specification ‘%s’ matches no disks” Cause: The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered. Action: Check the device specification string matches a disk on the system. // |
| ORA-15032 ORA-15032, 00000, “not all alterations performed” Cause: At least one ALTER DISKGROUP action failed. Action: Check the other messages issued along with this summary error. // |
| ORA-15033 ORA-15033, 00000, “disk ‘%s’ belongs to diskgroup \”%s\”" Cause: An attempt was made to ADD to a diskgroup a disk that was already part of another diskgroup, or an attempt was made to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup. Action: For ADD, check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. For the other commands, check the name of the specified disk. // |
| ORA-15034 ORA-15034, 00000, “disk ‘%s’ does not require the FORCE option” Cause: An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted. Action: Avoid gratuitous use of the FORCE option. // |
| ORA-15035 ORA-15035, 00000, “no disks belong to diskgroup \”%s\”" Cause: An attempt was made to mount a diskgroup for which no member disks were discovered. Action: Specify a valid diskgroup name that contains disks. // |
| ORA-15036 ORA-15036, 00000, “disk ‘%s’ is truncated” Cause: The size of the disk, as reported by the operating system, was smaller than the size of the disk as recorded in the disk header block on the disk. Action: Check if the system configuration has changed. // |
| ORA-15037 ORA-15037, 00000, “disk ‘%s’ is smaller than mimimum of %s MBs” Cause: The size of the disk, as reported by the operating system, was too small to allow the disk to become part of the diskgroup. Action: Check if the system configuration is correct. // |
| ORA-15038 ORA-15038, 00000, “disk ‘%s’ size mismatch with diskgroup [%s] [%s] [%s]” Cause: An attempt was made to mount into a diskgroup a disk whose recorded allocation unit size, metadata block size, or physical sector size was inconsistent with the other diskgroup members. Action: Check if the system configuration has changed. // |
| ORA-15039 ORA-15039, 00000, “diskgroup not dropped” Cause: An attempt to drop a diskgroup failed. Action: See the associated messages for details about why the drop was not successful. // |
| ORA-15040 ORA-15040, 00000, “diskgroup is incomplete” Cause: Some of the disks comprising a diskgroup were not present. Action: Check the hardware to ensure that all disks are functional. Also check that the setting of the ASM_DISKSTRING initialization parameter has not changed. Alternatively, for normal or high redundancy diskgroups, use MOUNT FORCE to offline missing disks as part of mounting the diskgroup. // |
| ORA-15041 ORA-15041, 00000, “diskgroup space exhausted” Cause: The diskgroup ran out of space. Action: Add more disks to the diskgroup, or delete some existing files. // |
| ORA-15042 ORA-15042, 00000, “ASM disk \”%s\” is missing” Cause: The specified disk, which is a necessary part of a diskgroup, could not be found on the system. Action: Check the hardware configuration. // |
| ORA-15043 ORA-15043, 00000, “ASM disk \”%s\” is not a diskgroup member” Cause: The specified disk has been removed from the diskgroup, but a disk matching its name was found. Action: Check the hardware configuration. // |
| ORA-15044 ORA-15044, 00000, “ASM disk ‘%s’ is incorrectly named” Cause: Either the specified disk had its contents changed such that it no longer contained an ASM disk name in its header that matches the diskgroup information or its FAILGROUP information may have become inconsistent. Action: Drop the disk from the diskgroup. // |
| ORA-15045 ORA-15045, 00000, “ASM file name ‘%s’ is not in reference form” Cause: The ASM file name was not in a form that can be used to reference an existing file because a file/incarnation number or an alias name was not present or a template name was included. Action: Correct the specified ASM file name. // |
| ORA-15046 ORA-15046, 00000, “ASM file name ‘%s’ is not in single-file creation form” Cause: The ASM file name was not in a form that can be used to create an single file because a file/incarnation number was present. Action: Correct the specified ASM file name. // |
| ORA-15047 ORA-15047, 00000, “ASM file name ‘%s’ is not in multiple-file creation form” Cause: The ASM file name was not in a form that can be used to create multiple files because either a fully-qualified file name or an alias name was present. Action: Correct the specified ASM file name. // |
| ORA-15048 ORA-15048, 00000, “ASM internal files cannot be deleted” Cause: An attempt was made to delete a metadata file used by ASM to manage the diskgroup. Action: Check the specified ASM file name. // |
| ORA-15049 ORA-15049, 00000, “diskgroup \”%s\” contains %s error(s)” Cause: Errors were discovered by the ALTER DISKGROUP CHECK command. Action: See the alert log for details of the errors. // |
| ORA-15050 ORA-15050, 00000, “disk \”%s\” contains %s error(s)” Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command. Action: See the alert log for details of the errors. // |
| ORA-15051 ORA-15051, 00000, “file ‘%s’ contains %s error(s)” Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command. Action: See the alert log for details of the errors. // |
| ORA-15052 ORA-15052, 00000, “ASM file name ‘%s’ is not in diskgroup \”%s\”" Cause: The ASM file name did not contain a diskgroup name that specified the correct diskgroup as implied by the other arguments to the command. Action: Correct the specified ASM file name or diskgroup name. // |
| ORA-15053 ORA-15053, 00000, “diskgroup \”%s\” contains existing files” Cause: An attempt was made to drop a diskgroup that still contains existing files. Action: Specify the INCLUDING CONTENTS option to drop the diskgroup and all of its existing files. // |
| ORA-15054 ORA-15054, 00000, “disk \”%s\” does not exist in diskgroup \”%s\”" Cause: An attempt was made to DROP (or CHECK) a disk that is not part of the specified diskgroup. Action: Check the name of the specified disk and the specified diskgroup. // |
| ORA-15055 ORA-15055, 00000, “unable to connect to ASM instance” Cause: The RDBMS instance was unable to connect to the required ASM instance when accessing a disk group. Action: Check the additional error messages. May need to configure correct ASM sid or make sure the RDBMS instance has OS privileges for ASM SYSDBA. // |
| ORA-15056 ORA-15056, 00000, “additional error message” Cause: An operating system error occured. Action: Correct the operating system error and retry the operation. // |
| ORA-15057 ORA-15057, 00000, “specified size of %s MB is larger than actual size of %s MB” Cause: A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system. Action: Specify a valid size. // |
| ORA-15058 ORA-15058, 00000, “disk ‘%s’ belongs to an incompatible diskgroup” Cause: An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release. Action: Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. // |
| ORA-15059 ORA-15059, 00000, “invalid device type for ASM disk” Cause: The device type of the discovered disk was not valid for use as an ASM disk. Action: Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information. // |
| ORA-15060 ORA-15060, 00000, “template \”%s\” does not exist” Cause: A command specified a template name, either directly or as part of an ASM file name, which did not exist. Action: Check the template specifier in the command. // |
| ORA-15061 ORA-15061, 00000, “ASM operation not supported [%s]” Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance. Action: This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services. // |
| ORA-15062 ORA-15062, 00000, “ASM disk is globally closed” Cause: The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information. Action: Bring the disk online for I/Os to get through. // |
| ORA-15063 ORA-15063, 00000, “ASM discovered an insufficient number of disks for diskgroup \”%s\”" Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation. Action: Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance. // |
| ORA-15064 ORA-15064, 00000, “communication failure with ASM instance” Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down. Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally. // |
| ORA-15065 ORA-15065, 00000, “hash collision for diskgroup names ‘%s’ and ‘%s’” Cause: There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names. Action: Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided. // |
| ORA-15066 ORA-15066, 00000, “offlining disk \”%s\” may result in a data loss” Cause: Following I/O failures, the disks holding all copies of a data // block were attempted to be taken offline. Action: Check the accompanying error messages for more information on the reason for the disk I/O failures. // |
| ORA-15067 ORA-15067, 00000, “command or option incompatible with diskgroup redundancy” Cause: An attempt was made to use a feature which is not permitted by the diskgroup’s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes. Action: Omit the option from the command. // |
| ORA-15068 ORA-15068, 00000, “maximum number of diskgroups %s already mounted” Cause: An attempt was made to mount more diskgroups than the instance is capable of mounting at one time. Action: Dismount a mounted diskgroup and retry the command. // |
| ORA-15069 ORA-15069, 00000, “ASM file ‘%s’ not accessible; timed out waiting for lock” Cause: An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed. Action: No action required, or try again later, after the create or resize has completed. // |
| ORA-15070 ORA-15070, 00000, “maximum number of files %s exceeded in diskgroup \”%s\”" Cause: The diskgroup ran out of space. Action: Delete some existing ASM files or create files in a new diskgroup. // |
| ORA-15071 ORA-15071, 00000, “ASM disk \”%s\” is already being dropped” Cause: An attempt was made to drop a disk from a diskgroup that was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option that was already being forcibly dropped from the diskgroup. Action: Check the ASM disk name and FORCE option as specified in the command. |
| ORA-15072 ORA-15072, 00000, “command requires at least %s failure groups, discovered only %s” Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered. Action: Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM. // |
| ORA-15073 ORA-15073, 00000, “diskgroup %s is mounted by another ASM instance” Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance. Action: dismount the diskgroup from all nodes except the one performing the drop diskgroup command. // |
| ORA-15074 ORA-15074, 00000, “diskgroup %s requires rebalance completion” Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup. Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation. // |
| ORA-15075 ORA-15075, 00000, “disk(s) are not visible cluster-wide” Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration. Action: Determine which disks are causing the problem from the GV$ASM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk. // |
| ORA-15076 ORA-15076, 00000, “Emulating I/O errors on the OSM disk” Cause: The disk to which the I/O request was issued is in an error // emulation mode. Action: Bring the disk online for I/Os to get through. // |
| ORA-15077 ORA-15077, 00000, “could not locate ASM instance serving a required diskgroup” Cause: The instance failed to perform the specified operation because it could not locate a required ASM instance. Action: Start an ASM instance and mount the required diskgroup. // |
| ORA-15078 ORA-15078, 00000, “ASM diskgroup was forcibly dismounted” Cause: The diskgroup to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed. Action: Mount the diskgroup to allow access again. // |
| ORA-15079 ORA-15079, 00000, “ASM file is closed” Cause: The file to which the I/O request was issued was closed. This could have been a consequence of the diskgroup being dismounted. Action: Make sure the diskgroup is mounted and the file is open. // |
| ORA-15080 ORA-15080, 00000, “synchronous I/O operation to a disk failed” Cause: A synchronous I/O operation invoked on a disk has failed. Action: Make sure that all the disks are operational. // |
| ORA-15081 ORA-15081, 00000, “failed to submit an I/O operation to a disk” Cause: A submission of an I/O operation to a disk has failed. Action: Make sure that all the disks are operational. // |
| ORA-15082 ORA-15082, 00000, “ASM failed to communicate with database instance” Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down). Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally. // |
| ORA-15083 ORA-15083, 00000, “failed to communicate with ASMB background process” Cause: A database instance failed to communicate with its ASMB background process when attempting to access an ASM file. Action: Check the alert log for more information on the reason for the failure. // |
| ORA-15084 ORA-15084, 00000, “ASM disk \”%s\” is offline and cannot be dropped.” Cause: An attempt was made to drop a disk that is offline. Action: Check the ASM disk name as specified in the command; or, if needed, use the DROP DISK FORCE option. // |
| ORA-15090 ORA-15090, 00000, “handle %s is not a valid descriptor” Cause: The file handle was not valid in this session. Action: Submit a handle obtained from a successful call to DBMS_DISKGROUP.OPEN(). // |
| ORA-15091 ORA-15091, 00000, “operation incompatible with open handle in this session” Cause: The current session contained an open handle from the DBMS_DISKGROUP PL/SQL package which precluded performing the command. Action: Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session. // |
| ORA-15092 ORA-15092, 00000, “I/O request size %s is not a multiple of logical block size %s” Cause: The length of the request was not a multiple of logical block size. Action: Correct the error and retry the operation. // |
| ORA-15093 ORA-15093, 00000, “buffer only contains %s bytes, I/O requested is %s bytes” Cause: The buffer supplied for write was too small to satisfy the request. Action: Correct the error and retry the operation. // |
| ORA-15094 ORA-15094, 00000, “attempted to write to file opened in read only mode” Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have write privileges. Action: Obtain a file handle in read-write mode and retry the write operation. // |
| ORA-15095 ORA-15095, 00000, “reached maximum ASM file size (%s GB)\n” Cause: An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM. Action: Use smaller files. |
| ORA-15096 ORA-15096, 0000, “lost disk write detected” Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active. Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups. // |
| ORA-15097 ORA-15097, 00000, “cannot SHUTDOWN ASM instance with connected RDBMS instance” Cause: A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances. Action: Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance. // |
| ORA-15098 ORA-15098, 00000, “file type not recognized by ASM instance” Cause: An attempt was made by DB instance to create a file for a file type that is not recognized by current version of ASM instance. Action: Upgrade ASM to higher version that recognizes this file type. // |
| ORA-15099 ORA-15099, 00000, “disk ‘%s’ is larger than maximum size of %s MBs” Cause: The specified size of the disk was too big to allow the disk to become part of the diskgroup. Action: Specify a smaller disk size than the maximum allowed size. // |
| ORA-15100 ORA-15100, 00000, “invalid or missing diskgroup name” Cause: The command did not specify a valid diskgroup name. Action: Specify a valid diskgroup name. // |
| ORA-15101 ORA-15101, 00000, “no action specified” Cause: The ALTER DISKGROUP command did not specify any alterations. Action: Specify at least one operation clause. // |
| ORA-15102 ORA-15102, 00000, “invalid POWER expression” Cause: The syntax of the POWER expression was invalid. Action: Specify a valid POWER expression. // |
| ORA-15103 ORA-15103, 00000, “conflicting or duplicate REPAIR options” Cause: The command specified conflicting or duplicate REPAIR keywords. Action: Specify only one REPAIR action. // |
| ORA-15104 ORA-15104, 00000, “conflicting CONTENTS options” Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options. Action: Specify only one option. // |
| ORA-15105 ORA-15105, 00000, “missing or invalid FAILGROUP name” Cause: The command did not specify a valid failure group name. Action: Specify a valid failure group name. // |
| ORA-15106 ORA-15106, 00000, “missing or invalid operating system disk locator string” Cause: The command did not specify a valid operating system path for the device as a string. Action: Specify a valid operating system path for the device. // |
| ORA-15107 ORA-15107, 00000, “missing or invalid ASM disk name” Cause: The command did not specify a valid ASM disk name identifier. Action: Specify a valid ASM disk name identifier. // |
| ORA-15108 ORA-15108, 00000, “missing or invalid template name” Cause: The command did not specify a valid template name identifier. Action: Specify a valid template name identifier. // |
| ORA-15109 ORA-15109, 00000, “conflicting protection attributes specified” Cause: The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords. Action: Specify only one keyword. // |
| ORA-15110 ORA-15110, 00000, “no diskgroups mounted” Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups. Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error. // |
| ORA-15111 ORA-15111, 00000, “conflicting or duplicate STRIPE options” Cause: The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once. Action: Specify only one keyword. // |
| ORA-15112 ORA-15112, 00000, “no diskgroups currently mounted” Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks. Action: Mount the diskgroups on which you wish to operate or ignore the error. // |
| ORA-15113 ORA-15113, 00000, “alias name ‘%s’ refers to a directory” Cause: The name specified referred to a directory in the alias directory and not a valid alias entry. Action: Check the alias name and retry. // |
| ORA-15114 ORA-15114, 00000, “missing or invalid ASM file name” Cause: The command did not specify a valid ASM file name identifier. Action: Specify a valid ASM file name identifier. // |
| ORA-15115 ORA-15115, 00000, “missing or invalid ASM disk size specifier” Cause: The command did not specify a valid ASM disk size. Action: Specify a valid ASM disk size. // |
| ORA-15116 ORA-15116, 00000, “invalid combination of ALTER DISKGROUP options” Cause: The ALTER DISKGROUP options may not be combined in this manner. Action: Issue separate ALTER DISKGROUP commands to accomplish the desired action. // |
| ORA-15117 ORA-15117, 00000, “command only operates on one diskgroup” Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command specified a list of diskgroups or the keyword ALL in a context where only a single diskgroup was permitted. Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP commands to accomplish the desired action. // |
| ORA-15120 ORA-15120, 00000, “ASM file name ‘%s’ does not begin with the ASM prefix character” Cause: A file name was specified to ASM which did not begin with the ASM prefix character (currently ‘+’). ASM uses the prefix to determine that a file specification is in fact an ASM file. Action: Correct the file name specification. // |
| ORA-15121 ORA-15121, 00000, “ASM file name ‘%s’ contains an invalid diskgroup name” Cause: A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters ‘$’ and ‘_’. Action: Correct the file name specification. // |
| ORA-15122 ORA-15122, 00000, “ASM file name ‘%s’ contains an invalid file number” Cause: A numeric file name was specified which did not contain a valid ASM file number. The ASM file number follows immediately after the diskgroup name. It must be preceeded by a ‘.’ character, and contain only numeric characters. Action: Correct the file name specification. |
| ORA-15123 ORA-15123, 00000, “ASM file name ‘%s’ contains an invalid incarnation number” Cause: A numeric file name was specified which did not contain a valid ASM incarnation number. The ASM incarnation number follows immediately after the ASM file number. It must be preceeded by a ‘.’ character, and contain only numeric characters. Action: Correct the file name specification. |
| ORA-15124 ORA-15124, 00000, “ASM file name ‘%s’ contains an invalid alias name” Cause: A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters ‘$’, ‘_’, ‘-’, or ‘#”. A space can separate two parts of an alias name. Action: Correct the file name specification. |
| ORA-15125 ORA-15125, 00000, “ASM file name ‘%s’ contains an invalid template name” Cause: A file name was specified to ASM which did not contain a valid template name. The template name, if present, follows immediately after the ASM incarnation number or the ASM alias name, if such is used in place of the ASM file number. It must be enclosed in parenthesis, start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters ‘$’ and ‘_’. Action: Correct the file name specification. |
| ORA-15126 ORA-15126, 00000, “component within ASM file name ‘%s’ exceeds maximum length” Cause: The maximum identifier length of 30 characters was exceeded for the diskgroup name, template name, or alias name field within the ASM file name. Action: Correct the file name specification. // |
| ORA-15127 ORA-15127, 00000, “ASM file name ‘%s’ cannot use templates” Cause: A fully qualified ASM file name was specified. Such a specification does not permit the inclusion of a template name in the ASM file name. Action: Correct the file name specification. // |
| ORA-15128 ORA-15128, 00000, “ASM file name ‘%s’ exceeds maximum length %s” Cause: The maximum ASM file name length of 256 characters was exceeded for the combination of diskgroup name, file number, template name, alias name plus punctuation within the ASM file name. Action: Correct the file name specification. // |
| ORA-15129 ORA-15129, 00000, “entry ‘%s’ does not refer to a valid directory” Cause: The entry indicated did not refer to a directory. Attempt was made to access the contents of this directory. Action: Correct the error and try again. // |
| ORA-15130 ORA-15130, 00000, “diskgroup \”%s\” is being dismounted” Cause: The diskgroup is being dismounted by request or because an I/O error was encountered that could not be handled by taking the disks offline. A disk cannot be offlined whenever doing so could result in all copies of a redundant extent being unavailable. Action: Repair the hardware problem and re-mount the diskgroup. Refer to the alert log to determine which disks have failed. // |
| ORA-15131 ORA-15131, 00000, “block %s of file %s in diskgroup %s could not be read” Cause: A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a copy of the block are either offline or received errors. Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed. // |
| ORA-15132 ORA-15132, 00000, “block %s of file %s in diskgroup %s could not be written” Cause: A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which contain a copy of the block are either offline or received errors. Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed. // |
| ORA-15133 ORA-15133, 00000, “instance recovery required for diskgroup %s” Cause: An instance in the cluster crashed making instance recovery necessary. Action: None. This error should not normally be seen by an ASM client. ASM will trap this error and retry the operation after doing instance recovery automatically. // |
| ORA-15150 ORA-15150, 00000, “instance lock mode ‘%s’ conflicts with other ASM instance(s)” Cause: Some other ASM instance used the lock name space in a conflicting mode. Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict. // |
| ORA-15151 ORA-15151, 00000, “missing or invalid version number for rolling migration” Cause: The command did not sepcify a valid version number. Action: Correct the version number in the command. It should be of the form v#.#.#.#.# or other forms with fewer numbers delimited by a period. The version number must be different from the current software version of the instance. // |
| ORA-15152 ORA-15152, 00000, “cluster in rolling upgrade” Cause: The cluster was already in the middle of rolling upgrade. Action: Rolling upgrade needs to be stopped before attempting to start again. // |
| ORA-15153 ORA-15153, 00000, “cluster not in rolling upgrade” Cause: The cluster was not in rolling upgrade. Action: Start the rolling upgrade using the ALTER SYSTEM START ROLLING command. // |
| ORA-15154 ORA-15154, 00000, “cluster rolling upgrade incomplete” Cause: The cluster was still performing rolling upgrade. Action: Ensure that all the instances in the cluster are upgraded before retrying the command. // |
| ORA-15155 ORA-15155, 00000, “version incompatible with the cluster” Cause: The current software version of the instance was incompatible with the other members of the cluster. Action: Make sure that all the members of the cluster are at the same version. If you are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING command. Ensure that the version being upgraded to is compatible with the existing version of the cluster. // |
| ORA-15156 ORA-15156, 00000, “cluster in rolling upgrade from version [%s] to [%s]” Cause: The current software version of the instance was incompatible with the rolling upgrade operation of the cluster. Action: The version number of new member instance must be one of the two versions involved in the rolling upgrade. // |
| ORA-15157 ORA-15157, 00000, “rolling migration is not allowed” Cause: The cluster was not capable of handling ASM rolling migration. Action: The Oracle Cluster Services is using vendor clusterware. Oracle cannot perform rolling upgrade or downgrade using vendor cluster ware. Restart ASM instances using Oracle cluster ware and retry the operation. // |
| ORA-15158 ORA-15158, 00000, “rolling upgrade prevented by %s” Cause: One or more instances were blocking the rolling upgrade. Action: Terminate or wait until the reported operation is complete before attempting the rolling upgrade to the cluster. // |
| ORA-15159 ORA-15159, 00000, “Internal testing event” Document: NO Cause: Set this event only under the supervision of Oracle development. Action: Traces execution of rolling upgrade. Level indicates verbosity of tracing. // // |
| ORA-15160 ORA-15160, 00000, “rolling migration internal fatal error in module %s,%s” Cause: Rolling migration experienced a fatal error. Action: Please contact Oracle support services. // |
| ORA-15161 ORA-15161, 00000, “invalid SYS_CLUSTER_PROPERTIES parameter” Cause: The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid Action: Pass in the correct parameter, refer to user documentation for a list of allowed parameter values. // |
| ORA-15162 ORA-15162, 00000, “cluster in rolling downgrade” Cause: The cluster was already in the middle of rolling downgrade. Action: Rolling downgrade needs to be stopped before attempting to start again. // |
| ORA-15163 ORA-15163, 00000, “cluster not in rolling downgrade” Cause: The cluster was not in rolling downgrade. Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING command. // |
| ORA-15164 ORA-15164, 00000, “cluster rolling downgrade incomplete” Cause: The cluster was still performing rolling downgrade. Action: Ensure that all the instances in the cluster are downgraded before retrying the command. // |
| ORA-15166 ORA-15166, 00000, “cluster in rolling downgrade from version [%s] to [%s]” Cause: The current software version of the instance was incompatible with the rolling downgrade operation of the cluster. Action: The version number of new member instance must be one of the two versions involved in the rolling downgrade. // |
| ORA-15168 ORA-15168, 00000, “rolling downgrade prevented by %s” Cause: One or more instances were blocking the rolling downgrade. Action: Terminate or wait until the reported operation is complete before attempting the rolling downgrade to the cluster. // |
| ORA-15169 ORA-15169, 00000, “destination ‘%s’ is a subdirectory of ‘%s’” Cause: Attempt to rename directory failed because the new directory name was a subdirectory of the original directory. Action: Correct the path of the destination and try again. // |
| ORA-15170 ORA-15170, 00000, “cannot add entry ‘%s’ in directory ‘%s’” Cause: Other errors prevented directory/alias creation. Action: Correct the errors and try again. // |
| ORA-15171 ORA-15171, 00000, “invalid syntax in the alias path after ‘%s’” Cause: An invalid alias/directory name syntax was specified. Action: Correct the alias path and try again. // |
| ORA-15173 ORA-15173, 00000, “entry ‘%s’ does not exist in directory ‘%s’” Cause: The specified alias did not exist in the given directory. Action: Correct the alias path and try again. // |
| ORA-15175 ORA-15175, 00000, “cannot create alias for diskgroup metadata file ‘%s’” Cause: An attempt was made to create an alias for a diskgroup metadata file. Action: Correct the alias path and try again. // |
| ORA-15176 ORA-15176, 00000, “file ‘%s’ already has an alias associated with it” Cause: An attempt was made to create an alias for a file that already had an existing alias. Action: Correct the file name and try again or drop existing alias. // |
| ORA-15177 ORA-15177, 00000, “cannot operate on system aliases” Cause: An attempt was made to modify a system alias. Action: Correct the alias name and try again. // |
| ORA-15178 ORA-15178, 00000, “directory ‘%s’ is not empty; cannot drop this directory” Cause: An attempt was made to drop a directory that contained valid entries. Action: Correct the directory path or specify the FORCE option to drop a directory that is not empty. // |
| ORA-15179 ORA-15179, 00000, “missing or invalid alias name” Cause: The command did not specify a valid alias identifier. Action: Specify a valid alias identifier. // |
| ORA-15180 ORA-15180, 00000, “could not open dynamic library %s, error [%s]” Cause: The library was not accessible Action: Correct the permissions of the library and try again. // |
| ORA-15181 ORA-15181, 00000, “symbol [%s] not found in library %s, error [%s]” Cause: An error was encountered while loading the specified ASMLIB symbol. Action: Correct the error reported and try again. // |
| ORA-15182 ORA-15182, 00000, “ASMLIB [%s] version mismatch, ORACLE version [%s]” Cause: The ASMLIB version reported is not supported by the ORACLE binary. Action: Install the correct library and try again. // |
| ORA-15183 ORA-15183, 00000, “ASMLIB initialization error [%s]” Cause: Unable to initialize the ASMLIB in ORACLE. Action: Contact ASMLIB library vendor support with the error details. // |
| ORA-15184 ORA-15184, 00000, “ASMLIB error could not be determined [%s] [%s]” Cause: An error was encountered which cannot be diagnosed further. Action: Contact ASMLIB libary vendor for support. |
| ORA-15185 ORA-15185, 00000, “could not close dynamic library %s, error [%s]” Cause: Could not close the dynamic library. Action: Contact ASMLIB libary vendor for support. // |
| ORA-15186 ORA-15186, 00000, “ASMLIB error function = [%s], error = [%s], mesg = [%s]” Cause: An error occured during a call to function listed in the error. Action: The detailed message associated with the error is listed along with the error. Correct the error and try again or contact ASMLIB library vendor for support. // |
| ORA-15190 ORA-15190, 00000, “Internal ASM testing event number 15190″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM disks encounter rebalance IO errors. // |
| ORA-15191 ORA-15191, 00000, “Internal ASM testing event number 15191″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are emulated. // |
| ORA-15192 ORA-15192, 00000, “invalid ASM disk header [%s] [%s] [%s] [%s] [%s]” Cause: ASM encountered an invalid disk header. Action: Contact Oracle Support Services. // |
| ORA-15193 ORA-15193, 00000, “Internal ASM tracing event number 15193″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: None. // |
| ORA-15194 ORA-15194, 00000, “Internal ASM-DB interaction testing event number 15194″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM-DB operation is interuppted. // |
| ORA-15195 ORA-15195, 00000, “Internal ASM testing event number 15195″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are simulated. // |
| ORA-15196 ORA-15196, 00000, “invalid ASM block header [%s:%s] [%s] [%s] [%s] [%s != %s]” Cause: ASM encountered an invalid metadata block. Action: Contact Oracle Support Services. // |
| ORA-15197 ORA-15197, 00000, “suppressing %s additional ASM messages” Cause: The ASM command generated so many erorrs that this summary message was reported in place of many individual messages. Action: If the command contained multiple actions, try separating each action into its own command and executing each command by itself. Otherwise, try not to generate so many errors. // |
| ORA-15198 ORA-15198, 00000, “operation %s is not yet available” Cause: An unimplemented operation was attempted. Action: Consider upgrading to later releases as they become available. // |
| ORA-15199 ORA-15199, 00000, “Internal ASM tracing event number 15199″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: Traces execution of ASM. Level indicates verbosity of tracing. // |
| ORA-15200 ORA-15200, 00000, “initialization parameter %s (%s) is not a power of two” Cause: The value specified for this initialization parameter was not a power of two. Action: Correct the initialization parameter value and restart the instance. // |
| ORA-15201 ORA-15201, 00000, “disk %s contains a valid RDBMS file” Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP … ADD DISK command appeared to contain a file from an existing database. By default, ASM will not allow a diskgroup to be created using this disk, as a safeguard against damaging an existing database. Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database is reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL command. // |
| ORA-15202 ORA-15202, 00000, “cannot create additional ASM internal change segment” Cause: The mount of a diskgroup by an additional instance in a RAC cluster required more space for internal use by ASM than was available in the diskgroup. Action: Delete unused files from the diskgroup or add additional disks to the diskgroup and retry the operation. |
| ORA-15203 ORA-15203, 00000, “diskgroup %s contains disks from an incompatible version of ASM” Cause: Diskgroup was created by an ASM instance with a higher compatibility setting. Action: Use an ASM instance with the appropriate software version to mount the diskgroup. |
| ORA-15204 ORA-15204, 00000, “database version %s is incompatible with diskgroup %s” Cause: The database compatibility of the diskgroup was advanced to a later version. Action: Upgrade the database instance to appropriate version of ORACLE. // |
| ORA-15205 ORA-15205, 00000, “requested mirror side unavailable” Cause: The requested mirror side of a block is either unallocated or allocated on a disk that has been dropped from the diskgroup. Action: Resubmit the request or try another mirror side. // |
| ORA-15206 ORA-15206, 00000, “duplicate diskgroup %s specified” Cause: A command specified the same diskgroup twice. Action: Specify each diskgroup only once. // |
| ORA-15207 ORA-15207, 00000, “Internal ASM testing event number 15207″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are simulated. // |
| ORA-15208 ORA-15208, 00000, “Internal ASM testing event number 15208″ Document: NO Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are simulated. // |
| ORA-15210 ORA-15210, 00000, “conflicting or duplicate PERMISSION options” Cause: The PERMISSION clause contained the USER, GROUP, or OTHER keyword more than once. Action: Specify each keyword, at most, once. // |
| ORA-15211 ORA-15211, 00000, “conflicting or duplicate OWNERSHIP options” Cause: The OWNERSHIP clause contained either the OWNER or the GROUP keyword more than once. Action: Specify each keyword, at most, once. // |
| ORA-15212 ORA-15212, 00000, “missing or invalid OWNER or GROUP name” Cause: The command did not specify a valid name for either the OWNER or the GROUP keyword. Action: Specify a valid name for either the OWNER or the GROUP keyword. // |
| ORA-15213 ORA-15213, 00000, “command operates on only one attribute” Cause: More than one disk group attribute was specified in the ALTER DISKGROUP statement. Action: Specify only one disk group attribute per ALTER DISKGROUP statement. // |
| ORA-15214 ORA-15214, 00000, “missing or invalid attribute specification” Cause: The command did not specify a valid attribute name or a valid attribute value. Action: Specify a valid attribute name and value pair. // |
| ORA-15215 ORA-15215, 00000, “missing or invalid user name” Cause: The command did not specify a valid user name. Action: Specify a valid user name. // |
| ORA-15216 ORA-15216, 00000, “missing or invalid user group name” Cause: The command did not specify a valid user group name. Action: Specify a valid user group name. // |
| ORA-15217 ORA-15217, 00000, “missing or invalid timeout value after DROP AFTER” Cause: The command did not specify a valid timeout value after the DROP AFTER clause. Action: Specify a valid timeout value after the DROP AFTER clause. // |
| ORA-15218 ORA-15218, 00000, “timeout value exceeded range” Cause: The OFFLINE timeout value exceeded the range of 0-136 years, inclusive. 136 years are 49674 days, 1192176 hours, and 71530560 minutes. Action: Specify a timeout value within the range of 0-136 years, inclusive. // |
| ORA-15219 ORA-15219, 00000, “conflicting or duplicate ZONE options” Cause: The command contained one or more of the following: – both the HOT and the COLD keywords – both the MIRRORHOT and the MIRRORCOLD keywords – the HOT keyword more than once – the COLD keyword more than once – the MIRRORHOT keyword more than once – the MIRRORCOLD keyword more than once Action: Specify either the HOT or the COLD keyword and either the MIRRORHOT or the MIRRORCOLD keyword, at most, once. // |
| ORA-15220 ORA-15220, 00000, “invalid file attribute specification” Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE was specified in a MODIFY FILE clause. These file attributes are immutable once a file is created. Action: Specify a ZONE keyword; for example, HOT, COLD, MIRRORHOT, or MIRRORCOLD. // |
| ORA-15221 ORA-15221, 00000, “ASM operation requires compatible.asm of %s or higher” Cause: The ASM operation specified requires a higher disk group attribute value for compatible.asm. Action: Set the disk group attribute compatible.asm to or above the requested version. // |
| ORA-15230 ORA-15230, 00000, “diskgroup ‘%s’ does not require the FORCE option” Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE option. Action: MOUNT and DROP diskgroup with the FORCE option are only permitted if the diskgroup cannot be mounted normally. // |
| ORA-15231 ORA-15231, 00000, “advancing diskgroup compatibility would exclude connected clients” Cause: Disk group compatibility could not be advanced because connected clients were at a lower compatibility than the target value. Action: Make sure all connected clients are at target compatibility level or higher. // |
| ORA-15232 ORA-15232, 00000, “cannot advance diskgroup compatibility due to offline disks” Cause: Disk group compatibilty could not be advanced because some disks are offline. Action: Retry the command after offline disks are dropped. // |
| ORA-15233 ORA-15233, 00000, “cannot advance diskgroup compatibility due to [%s]” Cause: Disk group compatibilty could not be advanced because of errors. Action: Check the alert log for more information on the reason for the failure. // |
| ORA-15234 ORA-15234, 00000, “target RDBMS compatibility (%s) exceeds ASM compatibility (%s)” Cause: An attempt was made to advance RDBMS compatibility beyond the disk group’s ASM compatibility. Action: Advance ASM compatibility before advancing RDBMS compatibility. // |
| ORA-15235 ORA-15235, 00000, “diskgroup %s mount mode conflicts with existing mount” Cause: The mode specified in the diskgroup mount command conflicted with the mode in which it was mounted on some other instance. Action: Specify a compatible mode in the diskgroup mount command. // |
| ORA-15236 ORA-15236, 00000, “diskgroup %s mounted in restricted mode” Cause: The specified diskgroup was mounted in restricted mode prohibiting client access. Action: Dismount the diskgroup and remount it in appropriate mode. // |
| ORA-15237 ORA-15237, 00000, “attribute %s cannot be set in CREATE DISKGROUP” Cause: The specified attribute may not be set with the CREATE DISKGROUP command. Action: Check the attribute name or use ALTER DISKGROUP SET ATTRIBUTE. // |
| ORA-15238 ORA-15238, 00000, “%s is not a valid value for attribute %s” Cause: The specified value was not valid for the attribute. Action: Check the attribute name and value. // |
| ORA-15239 ORA-15239, 00000, “allocation unit size higher than %s requires RDBMS compatibility %s” Cause: The allocation unit size requested exceeded the limit imposed by the RDBMS compatibility setting. Action: Use a smaller allocation unit size or specify a higher RDBMS compatibility setting. // |
| ORA-15240 ORA-15240, 00000, “attribute name %s is invalid” Cause: The attribute name was not valid or was not recognized. Action: Check the attribute name. // |
| ORA-15241 ORA-15241, 00000, “attribute %s is read only” Cause: The attribute value is read-only and cannot be changed. Action: None. The attribute value cannot be changed. // |
| ORA-15242 ORA-15242, 00000, “could not set attribute %s” Cause: An error occurred while setting the attribute. Action: Look at the underlying error(s) on the error stack. // |
| ORA-15243 ORA-15243, 00000, “%s is not a valid version number” Cause: The given version number was invalid, or not valid in this context. Action: Verify that the version number is valid and is appropriate for this command. Check for additional errors reported. // |
| ORA-15244 ORA-15244, 00000, “new compatibility setting less than current [%s]” Cause: The compatibility setting was invalid. The compatibility setting can only be advanced. Action: Check the version number. // |
| ORA-15245 ORA-15245, 00000, “ASM disk %s is already being brought online” Cause: An attempt was made to bring online a disk that is already being brought online. Action: Change the ONLINE statement to exclude the disk. // |
| ORA-15246 ORA-15246, 00000, “cannot bring ASM disk %s both online and then offline in the same statement” Cause: An attempt was made to bring the specified disk both online and offline in the same statement. Action: Revise the statement to either bring the disk online or take the disk offline. // |
| ORA-15247 ORA-15247, 00000, “cannot specify both WAIT and NOWAIT options in the same statement” Cause: An attempt was made to specify both WAIT and NOWAIT options in the same statement. Action: Revise the statement and include at most one option. // |
| ORA-15248 ORA-15248, 00000, “ASM attributes feature not enabled” Cause: The ASM attributes feature was not enabled. Action: Advance disk group ASM compatibility to version 11.1.0 or newer. // |
| ORA-15249 ORA-15249, 00000, “could not locate ASM attribute %s” Cause: The specified attribute could not be accessed. Action: Check the attribute name and examine underlying error(s) on the error stack. // |
| ORA-15250 ORA-15250, 0000, “insufficient diskgroup space for rebalance completion” Cause: The command attempted to reduce the available diskgroup space below the current space used. Action: Consult V$ASM_DISK to determine the space requirements for the diskgroup contents, and repeat the command after making the required storage available. // |
| ORA-15251 ORA-15251, 00000, “only restricted mount is allowed in the ASM instance” Cause: The ASM instance was started in restricted mode, and an attempt was made to mount a diskgroup in non-restricted mode. Action: Start the ASM instance in non-restricted mode and mount the diskgroup again, or mount the diskgroup in restricted mode. // |
| ORA-15281 ORA-15281, 00000, “not all specified disks were brought ONLINE” Cause: Some of the disks specified either experienced I/O errors while being brought ONLINE, or were simultaneously brought OFFLINE or dropped in another session, or were full. Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were not brought ONLINE. Inspect any additional error messages and the alert log to determine the exact cause. If some of the disks failed, either fix the cause of the failures or drop the disks. If some of the disks are full, either free space in the disk group or add new disks to the diskgroup. // |
| ORA-15282 ORA-15282, 00000, “ASM disk \”%s\” is not visible cluster-wide” Cause: An ALTER DISKGROUP ONLINE command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration. Action: Check operating system permissions for the device and the storage sub-system configuration on each node in the RAC cluster that cannot identify the disk. // |
| ORA-15283 ORA-15283, 00000, “ASM operation requires compatible.rdbms of %s or higher” Cause: The ASM operation specified requires a higher disk group attribute value for compatible.rdbms. Action: Set the disk group attribute compatible.rdbms to or above the requested version. // |
| ORA-15284 ORA-15284, 00000, “ASM terminated ALTER DISKGROUP ONLINE” Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be brought ONLINE. Action: Inspect additional error messages and the alert log to determine why the specified disks cannot be brought ONLINE. // |
| ORA-15285 ORA-15285, 00000, “disk ‘%s’ violates disk group attribute %s” Cause: Including the specifed disk would violate a restriction imposed by the specified disk group attribute. Action: Retry the operation while omitting the offending disk or change the attribute. // |
| ORA-15286 ORA-15286, 00000, “could not set disk group attribute %s due to offline disks” Cause: The specified disk group attribute could not be set because the disk group includes offline disks. Action: Retry the operation after the offline disks in this disk group are dropped or brought online. // |
| ORA-15287 ORA-15287, 00000, “could not set disk group attribute %s due to incompatible disks” Cause: The specified disk group attribute could not be set because the disk group includes disks that conflict with the new value. Action: Retry the operation after dropping the conflicting disks in this disk group. // |
| ORA-15288 ORA-15288, 00000, “disk(s) require disk group attribute %s clause” Cause: Some of the disks specified by the command also require the specified disk group attribute to be stated. Action: Retry the command including an ATTRIBUTE clause for the required disk group attribute. Alternatively, omit the disks that require setting the disk group attribue. See the alert log for additional information on the disks that require setting the disk group attribute. |
| ORA-15289 ORA-15289, 00000, “ASM disk %s cannot be resized beyond %s M” Cause: A resize disk command specified a size beyond the maximum allowed for this disk. Action: Check alert logs from all ASM instances to identify the reason for the size limitation. If there are any 10g database instances using this disk group, shut down those instances and retry the resize operation. |
| ORA-15290 ORA-15290, 00000, “operation not permitted on offline disk %s” Cause: An attempt was made to specify an operation that is only permitted on disks that are online. The specified disk was not online. Action: Online the disk or wait for online to complete before retrying the operation. |
| ORA-15291 ORA-15291, 00000, “ASM could not add disk \”%s\” to disk group \”%s\”" Cause: An attempt was made to add a disk to a disk group while the distribution of disks in failure groups was too uneven. Action: Add or drop disks to or from failure groups to balance their distribution in all failure groups and retry the operation. |
| ORA-15292 ORA-15292, 00000, “Disk name %s is being used by another disk” Cause: The specified disk name could not be reused because an 11.1.0.6.0 or earlier database instance had it cached in memory. Action: Do one of the following – Specify a different name for the disk. – Wait for the rebalance to complete successfully. – Identify the database instance with the problem and shut it down before retrying the command. // |
| ORA-15293 ORA-15293, 00000, “operation disallowed by ASM_POWER_LIMIT” Cause: This operation required data movement in order to complete successfully. However, ASM_POWER_LIMIT was set to zero, thereby preventing this operation. Action: Repeat the operation after setting ASM_POWER_LIMIT to a non-zero value. // |
| ORA-15294 ORA-15294, 00000, “SYSASM privilege not allowed on database instance” Cause: The SYSASM privilege was not allowed on this database instance; it is allowed only on an ASM instance. Action: Use either the SYSDBA or the SYSOPER privilege. // |
| ORA-15295 ORA-15295, 00000, “FINE striping not allowed for the Staleness Registry” Cause: An SQL command attempted to set the striping attribute of the ASM_STALE template to FINE striping. Action: Do not modify the striping attribute of the ASM_STALE template. // |
| ORA-15450 ORA-15450, 00000, “invalid volume name specifier” Cause: The volume name specified was invalid Action: Specify a valid volume name. // |
| ORA-15451 ORA-15451, 00000, “missing or invalid volume size specifier” Cause: The volume size specified was invalid. Action: Specify a valid volume size. // |
| ORA-15452 ORA-15452, 00000, “missing or invalid stripe width specifier” Cause: The volume stripe width specified was invalid. Action: Specify a valid volume stripe width. // |
| ORA-15453 ORA-15453, 00000, “invalid STRIPE_COLUMNS specifier” Cause: An ADD VOLUME command did not specify a valid number of stripe columns. Action: Specify a valid number of stripe columns. // |
| ORA-15454 ORA-15454, 00000, “ALTER DISKGROUP ALL cannot use single volume names” Cause: An ALTER DISKGROUP ALL command specified a single volume or a list of volumes Action: Use the ALL keyword when specifying volumes on multiple diskgroups. // |
| ORA-15455 ORA-15455, 00000, “FORCE option cannot be used when specifying ALL volumes” Cause: The FORCE option was used to disable ALL volumes. Action: Use FORCE option to disable one volume at a time. // |
| ORA-15456 ORA-15456, 00000, “missing or invalid volume usage specifier” Cause: The command did not specify a valid volume usage string. Action: Specify a valid volume usage string with alphanumeric characters. // |
| ORA-15457 ORA-15457, 00000, “first letter of the volume name is not alphabetic” Cause: A volume name was specified with a nonalphabetic first character. Action: Set the first character of the volume name to be alphabetic. // |
| ORA-15458 ORA-15458, 00000, “invalid character in volume name” Cause: A volume name was specified with an invalid character. Action: Use a volume name with only alphanumeric characters. // |
| ORA-15459 ORA-15459, 00000, “STRIPE_WIDTH of %s is not a power of two” Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not a power of two. Action: Select a STRIPE_WIDTH that is a power of two; for example, 4K, 8K, etc. // |
| ORA-15460 ORA-15460, 00000, “volume name ‘%s’ is already in use” Cause: An ADD VOLUME command specified a volume name that was already used by another volume. Action: Select a different name for the volume. // |
| ORA-15461 ORA-15461, 00000, “STRIPE_WIDTH of %s bytes is less than the minimum of %s bytes” Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too small. Action: Select a larger STRIPE_WIDTH. // |
| ORA-15462 ORA-15462, 00000, “STRIPE_WIDTH of %s bytes is greater than the maximum of %s bytes” Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too large. Action: Select a smaller STRIPE_WIDTH. // |
| ORA-15463 ORA-15463, 00000, “volume size of %sK is less then the minimum of %sM” Cause: The volume size specified was too small. Action: Select a larger volume size. // |
| ORA-15464 ORA-15464, 00000, “STRIPE_COLUMNS of %s is greater than the maximum of %s” Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that was too large. Action: Select a smaller STRIPE_COLUMNS value. // |
| ORA-15465 ORA-15465, 00000, “STRIPE_COLUMNS of %s is less than the minimum of %s” Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too small. Action: Select a larger STRIPE_COLUMNS value. // |
| ORA-15466 ORA-15466, 00000, “volume name ‘%s’ does not exist” Cause: The command specified a volume name that does not exist. Action: Ensure a valid volume name is used. // |
| ORA-15467 ORA-15467, 00000, “volume operation is already in progress” Cause: Another command is currently operating on the specified volume. Action: Wait a short time before retrying the command. // |
| ORA-15468 ORA-15468, 00000, “operation not permitted; volume ‘%s’ currently being accessed” Cause: An attempt was made to communicate with the volume driver. The volume was being accessed by another application and, therefore, could not be changed. Action: Shut down all applications that might be accessing this volume and then retry the command. // |
| ORA-15469 ORA-15469, 00000, “VBG process terminated with error” Cause: A volume background process terminated with error. Action: Wait for process to restart. // |
| ORA-15470 ORA-15470, 00000, “VDBG process terminated with error” Cause: The volume driver background process terminated with error. Action: Warm start instance. // |
| ORA-15471 ORA-15471, 00000, “volume redundancy incompatible with diskgroup redundancy” Cause: An ADD VOLUME command specified a volume redundancy that was incompatible with the diskgroups redundancy. Action: Specify a valid volume redundancy. A volume cannot have external redundancy with a high redundancy diskgroup. Also, a volume cannot have high redundancy with an external redundancy diskgroup. // |
| ORA-15472 ORA-15472, 00000, “volume library cannot be loaded. Platform may not support volume creation.” Cause: The volume library could not be loaded. Either the platform does not support volume operations, or there is a problem with the library. Action: Ensure that the platform supports volumes. If the platform does support volumes, check the alert log for library loading failure information. // |
| ORA-15473 ORA-15473, 00000, “access to a volume’s storage through an unsupported interface” Cause: An attempt was made to access or modify a volume’s storage through an unsupported interface. Action: Use supported interfaces for access to volume devices. // |
| ORA-15474 ORA-15474, 00000, “volume name is greater than %s characters” Cause: An ADD VOLUME command specified a volume name that was too long. Action: Select a smaller volume name. // |
| ORA-15475 ORA-15475, 00000, “usage string is greater than %s characters” Cause: The usage string specified was too long. Action: Select a smaller usage string. // |
| ORA-15476 ORA-15476, 00000, “resize of OFS volume must use OFS resize command” Cause: An attempt was made to resize an OFS volume through SQL. Action: Use the supported OFS commands to resize the volume. // |
| ORA-15477 ORA-15477, 00000, “cannot communicate with the volume driver” Cause: An attempt was made to communicate with the volume driver. Action: Check that the ASM volume driver is loaded. If so, check the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. // |
| ORA-15478 ORA-15478, 00000, “OFSC process terminated with error” Cause: The ofs background process terminated with error Action: Wait for process restart |
| ORA-15479 ORA-15479, 00000, “diskgroup version incompatible with ASM volumes” Cause: The diskgroup’s version was incompatible with creating volumes. Action: Upgrade the diskgroup version in order to use volume functionality. // |
| ORA-15480 ORA-15480, 00000, “error reported in the ASM volume driver” Cause: An error was reported in the ASM volume driver. Action: Check the operating system log files to identify the reason for the failure and take necessary action to prevent such failures in the future. // |
| ORA-15481 ORA-15481, 00000, “missing or invalid volume mountpath specifier” Cause: A invalid volume mountpath string was specified. Action: Specify a valid volume mountpath string with alphanumeric characters. // |
| ORA-15482 ORA-15482, 00000, “failed to create/remove path to volume device file” Cause: Improper driver installation. Action: Check the alert log for device file creation failure information. Reload the driver using the supported installation method. // |
| ORA-15500 ORA-15500, 00000, “Reserved for Workload Capture and Replay tracing” Document: NO Cause: Action: // |
| ORA-15501 ORA-15501, 00000, “cannot start workload capture on instance %s” Cause: Given instance encountered unexpected errors while trying to start the workload capture. Action: Check the alert log and other diagnostics in the given instance to diagnose the problem. // |
| ORA-15502 ORA-15502, 00000, “cannot stop workload capture on instance %s” Cause: Given instance encountered unexpected errors while trying to stop the workload capture. Action: Check the alert log and other diagnostics in the given instance to diagnose the problem. // |
| ORA-15503 ORA-15503, 00000, “cannot startup instance when procedures in \”DBMS_WORKLOAD_CAPTURE\” or \”DBMS_WORKLOAD_REPLAY\” are in the middle of their execution” Cause: The new instance could not be started because the database was executing a procedure in either the DBMS_WORKLOAD_CAPTURE or DBMS_WORKLOAD_REPLAY package. Action: Start the new instance after such procedures in the given packages have finished execution. // |
| ORA-15504 ORA-15504, 00000, “cannot start workload capture because instance %s not present in RESTRICTED SESSION mode” Cause: The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE was FALSE, therefore all the active instances were expected to be in the RESTRICTED SESSION mode. Action: Start all instances using STARTUP RESTRICT or execute ALTER SYSTEM ENABLE RESTRICTED SESSION on all active instances before issuing DBMS_WORKLOAD_CAPTURE.START_CAPTURE. // |
| ORA-15505 ORA-15505, 00000, “cannot start workload capture because instance %s encountered errors while accessing directory \”%s\”" Cause: Given instance could not access the specified CAPTURE directory or the specified CAPTURE directory already had a workload capture in it. Action: Provide a directory object that is valid, empty and accessible from all the instances in the database cluster. // |
| ORA-15506 ORA-15506, 00000, “cannot prepare instance %s for replay” Cause: Given instance encountered unexpected errors while trying to prepare for a workload replay. Action: Check the alert log and other diagnostics in the given instance to diagnose the problem. // |
| ORA-15507 ORA-15507, 00000, “cannot start workload replay on instance %s” Cause: Given instance encountered unexpected errors while trying to start a workload replay. Action: Check the alert log and other diagnostics in the given instance to diagnose the problem. // |
| ORA-15508 ORA-15508, 00000, “cannot cancel workload replay on instance %s” Cause: Given instance encountered unexpected errors while trying to cancel a workload replay. Action: Check the alert log and other diagnostics in the given instance to diagnose the problem. // |
| ORA-15509 ORA-15509, 00000, “workload replay has been cancelled” Cause: Workload replay was cancelled. Action: Restart the workload replay. // |
| ORA-15510 ORA-15510, 00000, “cannot perform operation when \”STATISTICS_LEVEL\” is \”BASIC\”" Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC. Action: Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL or ALL. // |
| ORA-15511 ORA-15511, 00000, “cannot process workload capture because no user sessions were recorded” Cause: No user sessions were recorded in the given workload capture. Processing this capture failed because no user workload was captured. Action: Capture a workload in which at least one user session connects and performs some operations. // |
| ORA-15512 ORA-15512, 00000, “directory \”%s\” does not contain a valid processed workload capture” Cause: One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE were missing. Action: Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE and then retry the command. // |
| ORA-15513 ORA-15513, 00000, “cannot access the input directory” Cause: Given input directory is either invalid or inaccessible. Action: Verify that the input directory is valid and accessible and then retry the command. // |
| ORA-15514 ORA-15514, 00000, “cannot find a match for the remote procedure call during replay” Cause: The corresponding PL/SQL program was either dropped or modified. Action: Verify that the corresponding PL/SQL program is defined the same way during replay as it was defined during workload capture. // |
| ORA-15515 ORA-15515, 00000, “error while replaying remote procedure call: \”%s.%s.%s\”" Cause: Error encountered during the replay of a remote procedure call. Action: Correct the cause of the preceding error and restart workload replay. // |
| ORA-15516 ORA-15516, 00000, “parallel preprocessing worker hit error ORA-%s” Cause: One of the parallel preprocessing workers died unexpectedly while processing the workload. Action: Find the root cause or simply preprocess the workload using only one process. // |
| ORA-15517 ORA-15517, 00000, “cannot start parallel preprocessing worker” Cause: One of the parallel preprocessing workers could not be started. Action: Find the root cause or simply preprocess the workload using only one process. // |
| ORA-15518 ORA-15518, 00000, “parallel preprocessing encountered an unexpected error” Cause: An unexpected error occured during parallel preprocessing. Action: Find the root cause or simply preprocess the workload using only one process. // |
| ORA-15551 ORA-15551, 00000, “workload replay client cannot connect to database server” Cause: The server connection identifier was invalid. Action: Restart the client with correct server connection identifier. // |
| ORA-15552 ORA-15552, 00000, “workload replay client cannot login to database server” Cause: 1) the replay client used an invalid username or password; 2) the replay user does not have the privilege to switch user; 3) the recorded username does not exist in the replay database. Action: 1) restart replay client with correct username and password 2) grant user switching prvilege to the replay user 3) verify whether the replay database was restored properly // |
| ORA-15553 ORA-15553, 00000, “workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package” Cause: Workload Replay Client’s replay user did not have EXECUTE permission on the DBMS_WORKLOAD_REPLAY package. Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package to replay user and restart the Workload Replay Client. // |
| ORA-15554 ORA-15554, 00000, “cannot start workload replay client because the database server is not in PREPARE mode” Cause: The Workload Replay Client could not connect to the database server because the database server was not in the PREPARE mode. Action: Put the database in PREPARE mode by using DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the Workload Replay Client. // |
| ORA-15555 ORA-15555, 00000, “workload replay client encountered unexpected error: \”%s\”" Cause: Workload Replay Client encountered an unexpected error. Action: Check the Workload Replay Client’s log files and the database server alert log to diagnose the problem. // |
| ORA-15556 ORA-15556, 00000, “invalid input specified to the workload replay client” Cause: Invalid input was specified. Action: Use the Workload Replay Client’s HELP=Y option to know more about valid input options. // |
| ORA-15557 ORA-15557, 00000, “workload replay client cannot access the replay directory or the database version do not match the preprocessing one” Cause: The Workload Replay Client could not access the directory that contained the workload to be replayed, or the workload was preprocessed by a different version of the database. Action: Restart the workload replay after specifying the correct replay directory, or preprocess it with the correct database. // |
| ORA-15558 ORA-15558, 00000, “replay thread encountered unexpected error” Cause: A single replay thread got disconnected from the server due to an unexpected error. Action: Check the Workload Replay Client’s log files and the database server alert log to diagnose the problem. // |
| ORA-15559 ORA-15559, 00000, “workload replay client cannot open workload capture file” Cause: The Workload Replay Client could not access one or more workload capture files from the replay directory. Action: Restart the workload replay after copying all the workload capture files to the replay directory. // |
| ORA-15560 ORA-15560, 00000, “workload replay client cannot access the work directory” Cause: The Workload Replay Client could not access the work directory to write log files for debug information. Action: Restart the Workload Replay Client after specifying the correct work directory. |
| ORA-15561 ORA-15561, 00000, “workload replay client cannot connect to the remapped connection with conn_id : %s” Cause: The specified connection is invalid or the specified host is inaccessible. Action: Test the specified connection using other methods and redefine the connection remapping, if necessary. Consult the view DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings. // |
| ORA-15562 ORA-15562, 00000, “workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view” Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or was not accessible. Action: Re-create the workload capture and replay views. For additional information, see the documentation. // |
| ORA-15563 ORA-15563, 00000, “workload replay client cannot spawn new threads” Cause: The Workload Replay Client does not have enough resource (CPU or memory) to spawn new threads. Action: Restart the workload replay after allocating more resource (CPU and memory) to the Workload Replay Client or use more hosts as replay clients to drive the workload. // |
| ORA-15564 ORA-15564, 00000, “contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server” Cause: The processed workload capture files given to the workload replay client directory did not match the contents of the replay directory given as input to DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY. Action: Provide the same processed workload capture files to both the database server and all the workload replay clients and restart the replay. If the same workload capture files were processed more than once, provide a copy of the latest processed workload capture files to all the workload replay clients and the database server. // |
| ORA-15566 ORA-15566, 00000, “workload replay client cannot replay user call in the current version” Cause: The workload replay client encountered a user call in the captured workload that was not supported for replay in the current version. Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call that encountered this error. Refer to the documentation for more details on the types of workload that are not supported in the current version. // |
| ORA-15590 ORA-15590, 00000, “encountered an incomplete workload capture file” Cause: The captured workload contained one or more incomplete recording files. This can happen when the original workload capture’s FINISH_CAPTURE command timed out while waiting for all the active sessions to close their workload capture files. Action: Incomplete capture files will not interfere with the processing and replaying of the captured workload. This is simply a warning message to point out that some database calls might not have been recorded due to FINISH_CAPTURE command timing out. // |
| ORA-15599 ORA-15599, 00000, “Last message reserved for WCR (KEC)” Document: NO Cause: Action: // |
| ORA-15600 ORA-15600, 00000, “Reserved for Automated Maintenance Tasks” Document: NO Cause: Action: // |
| ORA-15601 ORA-15601, 00000, “Invalid value specified for parameter \”%s\”" Cause: An invalid value was specified for the given parameter. Action: Correct the value being specified for the parameter. |
| ORA-15602 ORA-15602, 00000, “Parameter \”%s\” cannot be NULL.” Cause: An attempt was made to call a procedure without a required parameter. Action: Specify a valid value for this parameter. |
| ORA-15603 ORA-15603, 00000, “Action cannot be performed when database is in read-only mode.” Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database was open in read-only mode. Action: Retry when database is open in read/write mode. |
| ORA-15604 ORA-15604, 00000, “Initialization parameters prevent client from being enabled.” Cause: An attempt was made to enable a client that was disabled for automatic execution by an initialization parameter. Action: Check the related client parameters and try again. |
| ORA-15605 ORA-15605, 00000, “\”%s\” is not a Maintenance Window” Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of the MAINTENANCE_WINDOW_GROUP. Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call. |
| ORA-15649 ORA-15649, 00000, “Last message reserved for Automated Maintenance Tasks (KET).” Document: NO Cause: Action: // |
| ORA-15650 ORA-15650, 00000, “invalid DIRECT_ACCESS command” Document: NO Cause: Action: |
| ORA-15651 ORA-15651, 00000, “invalid option \”%s\” for \”%s\” in DIRECT_ACCESS command” Document: NO Cause: Action: |
| ORA-15652 ORA-15652, 00000, “Fixed table \”%s\” does not exist.” Document: NO Cause: Action: |
| ORA-15653 ORA-15653, 00000, “Fixed table \”%s\” is not supported by DIRECT_ACCESS.” Document: NO Cause: Action: |
| ORA-15654 ORA-15654, 00000, “No more than %s columns can be specified in a DIRECT_ACCESS SELECT query.” Document: NO Cause: Action: |
| ORA-15655 ORA-15655, 00000, “Fixed table \”%s\” cannot be accessed safely in prelim connection.” Document: NO Cause: Action: Run ORADEBUG DIRECT_ACCESS SET MODE=UNSAFE and query again. |
| ORA-15656 ORA-15656, 00000, “DIRECT_ACCESS statement is too long.” Document: NO Cause: Action: |
| ORA-15699 ORA-15699, 00000, “last message reserved for DIRECT_ACCESS” Document: NO Cause: Action: // |
| ORA-16000 ORA-16000, 00000, “database open for read-only access” Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements // generate this error. Action: In order to modify the database, it must first be shut down and re-opened for read-write access. |
| ORA-16001 ORA-16001, 00000, “database already open for read-only access by another instance” Cause: The database has been opened for read-only access by another // instance, and cannot be opened for read-write access by this // instance. Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access. |
| ORA-16002 ORA-16002, 00000, “database already open for read-write access by another instance” Cause: The database has been opened for read-write access by another // instance, and cannot be opened for read-only access by this // instance. Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access. |
| ORA-16003 ORA-16003, 00000, “standby database is restricted to read-only access” Cause: To ensure its integrity, a standby database can only be opened for read-only access. Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY. |
| ORA-16004 ORA-16004, 00000, “backup database requires recovery” Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance. Action: Perform the necessary recovery and re-open for read-only access. |
| ORA-16005 ORA-16005, 00000, “database requires recovery” Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance. Action: Perform the necessary recovery and re-open for read-only access. |
| ORA-16006 ORA-16006, 00000, “audit_trail destination incompatible with database open mode” Cause: The audit_trail initialization parameter was set to “DB” (or TRUE), which is incompatible with a database opened for read-only access. Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to “OS” or “NONE” (FALSE). |
| ORA-16007 ORA-16007, 00000, “invalid backup control file checkpoint” Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access. Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. |
| ORA-16008 ORA-16008, 00000, “indeterminate control file checkpoint” Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access. Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. |
| ORA-16009 ORA-16009, 00000, “remote archive log destination must be a STANDBY database” Cause: The database associated with the archive log destination service // name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. |
| ORA-16010 ORA-16010, 00000, “disable stale RFS process extermination” Document: NO Cause: Disables the termination of RFS processes waiting for tcp_keepalive_interval to expire. Action: No action is required. |
| ORA-16011 ORA-16011, 00000, “Archivelog Remote File Server process in Error state” Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data. Action: Correct the problem at the standby database site. |
| ORA-16012 ORA-16012, 00000, “Archive log standby database identifier mismatch” Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. |
| ORA-16013 ORA-16013, 00000, “log %s sequence# %s does not need archiving” Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived. Action: No action is required. |
| ORA-16014 ORA-16014, 00000, “log %s sequence# %s not archived, no available destinations” Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors. Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred. |
| ORA-16015 ORA-16015, 00000, “log %s sequence# %s not archived, media recovery disabled” Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed. Action: Disable the standby destination or enable media recovery and retry. |
| ORA-16016 ORA-16016, 00000, “archived log for thread %s sequence# %s unavailable” Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file. Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command. |
| ORA-16017 ORA-16017, 00000, “cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination” Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly. Action: Set the primary archive destination to a valid non-NULL value. |
| ORA-16018 ORA-16018, 00000, “cannot use %s with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST” Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1…10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST. Action: Eliminate any incompatible parameter definitions. |
| ORA-16019 ORA-16019, 00000, “cannot use %s with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST” Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1…10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter. Action: Eliminate any incompatible parameter definitions. |
| ORA-16020 ORA-16020, 00000, “less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST” Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value. Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| ORA-16021 ORA-16021, 00000, “session %s destination cannot be the same as session %s destination” Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter. Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters. |
| ORA-16022 ORA-16022, 00000, “LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL” Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL. Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value. |
| ORA-16023 ORA-16023, 00000, “system %s destination cannot be the same as session %s destination” Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1…10) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate. Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter. |
| ORA-16024 ORA-16024, 00000, “parameter %s cannot be parsed” Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…10) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. |
| ORA-16025 ORA-16025, 00000, “parameter %s contains repeated or conflicting attributes” Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…10) parameter contained either repeated attributes or attributes that conflicted with each other. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. |
| ORA-16026 ORA-16026, 00000, “parameter %s contains an invalid attribute value” Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…10) parameter contained an attribute with an invalid value. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. |
| ORA-16027 ORA-16027, 00000, “parameter %s is missing a destination option” Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. |
| ORA-16028 ORA-16028, 00000, “new %s causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires” Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1…10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value. Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| ORA-16029 ORA-16029, 00000, “cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations” Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations. Action: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1…10). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| ORA-16030 ORA-16030, 00000, “session specific change requires a LOG_ARCHIVE_DEST_n destination” Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command. Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1…10) parameters. |
| ORA-16031 ORA-16031, 00000, “parameter %s destination string exceeds %s character limit” Cause: The value for the specified parameter contained a destination string that is too long. Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message. |
| ORA-16032 ORA-16032, 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-16033 ORA-16033, 00000, “parameter %s destination cannot be the same as parameter %s destination” Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter. Action: Specify a different value for one of the archive log parameters. |
| ORA-16034 ORA-16034, 00000, “FROM parameter is incompatible with MANAGED recovery” Cause: Use of the FROM ‘location’ parameter is not allowed when MANAGED recovery has been specified. Action: Correct the syntax and retry the command. |
| ORA-16035 ORA-16035, 00000, “missing required keyword %s” Cause: The indicated keyword is required but was not specified. Action: Correct the syntax and retry the command. |
| ORA-16036 ORA-16036, 00000, “invalid MANAGED recovery CANCEL option” Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement. Action: Specify either nothing or IMMEDIATE following CANCEL. |
| ORA-16037 ORA-16037, 00000, “user requested cancel of managed recovery operation” Cause: The managed standby database recovery operation has been canceled per user request. Action: No action is required. // |
| ORA-16038 ORA-16038, 00000, “log %s sequence# %s cannot be archived” Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error. Action: No action is required. |
| ORA-16039 ORA-16039, 00000, “RFS request version mismatch” Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site. Action: Verify that compatible versions of Oracle are running on the primary and all standby sites. |
| ORA-16040 ORA-16040, 00000, “standby destination archive log file is locked” Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process. Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database. |
| ORA-16041 ORA-16041, 00000, “Remote File Server fatal error” Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible. Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action. |
| ORA-16042 ORA-16042, 00000, “user requested cancel immediate of managed recovery operation” Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state. Action: No action is required. |
| ORA-16043 ORA-16043, 00000, “managed recovery session canceled” Cause: The standby database managed recovery operation has been canceled per user request or operation timeout. Action: More specific messages will accompany this message. |
| ORA-16044 ORA-16044, 00000, “destination %s attribute cannot be specified at session level” Cause: An archive log destination attribute was attempted to be modified at the session level. Action: Use the ALTER SYSTEM command to modify the destination attribute. |
| ORA-16045 ORA-16045, 00000, “circular archive log destination dependency chain” Cause: An archive log destination contains a dependency to another // archive log destination that also contains a dependency. Action: The parent archive log destination cannot be dependent on another // archive log destination. Use the ALTER SYSTEM command to remove // one of the dependency attributes. |
| ORA-16046 ORA-16046, 00000, “Archive log destination failed due to failed dependent destination” Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails. Action: No action required. |
| ORA-16047 ORA-16047, 00000, “DGID mismatch between destination setting and standby” Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination. Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination. |
| ORA-16048 ORA-16048, 00000, “enable simulated error on archive log write” Document: NO Cause: Causes an I/O error to be signalled during the writing of // an archival operation. Action: No action is required. |
| ORA-16049 ORA-16049, 00000, “simulated error on archive log write” Document: NO Cause: I/O error returned for a simulated archival failure during // an archival operation. Action: No action is required. |
| ORA-16050 ORA-16050, 00000, “destination exceeded specified quota size” Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations. Action: No action is required. |
| ORA-16051 ORA-16051, 00000, “parameter %s contains an invalid delay time” Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes). Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. |
| ORA-16052 ORA-16052, 00000, “DB_UNIQUE_NAME attribute is required” Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled. Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. |
| ORA-16053 ORA-16053, 00000, “DB_UNIQUE_NAME %s is not in the Data Guard Configuration” Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration. Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance. |
| ORA-16054 ORA-16054, 0000, “Event for automatic RFS gap sequence detection” Document: NO Cause: This is a Oracle internal event code. The condition is posted when the ARC process is about to request the remote RFS to detect gap sequence. The event is used to allow run time disabling of the automatic gap sequence detection. Such run time disable function allows the ORATST to test the other get gap sequence code path: kcrrggs()…etc Action: N/A, this is a Oracle internal event code |
| ORA-16055 ORA-16055, 0000, “FAL request rejected” Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons. Action: Check the alert log on the primary database. Take the appropriate action to solve the problem. |
| ORA-16056 ORA-16056, 00000, “backup control file archival requires proper syntax” Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified. Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required. |
| ORA-16057 ORA-16057, 00000, “DGID from server not in Data Guard configuration” Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby. Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby. |
| ORA-16058 ORA-16058, 00000, “standby database instance is not mounted” Cause: The RFS process on the standby database received an internal error. Action: Check the standby alert log and RFS trace files for more information. |
| ORA-16059 ORA-16059, 00000, “Log file is empty or invalid next available block” Cause: Archiving not allowed of an empty or invalid log file. Action: No action is required. |
| ORA-16060 ORA-16060, 00000, “Log file is current” Cause: The current log file cannot be archived using its file name. Action: No action is required. |
| ORA-16061 ORA-16061, 00000, “Log file status has changed” Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation. Action: No action is required. |
| ORA-16062 ORA-16062, 00000, “DGID from standby not in Data Guard configuration” Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server. Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server. |
| ORA-16063 ORA-16063, 00000, “remote archival is enabled by another instance” Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance. Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance. |
| ORA-16064 ORA-16064, 00000, “remote archival is disabled by another instance” Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance. Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance. |
| ORA-16065 ORA-16065, 00000, “remote archival disabled at standby destination” Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database. Action: If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur. |
| ORA-16066 ORA-16066, 00000, “remote archival disabled” Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled. Action: If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur. |
| ORA-16067 ORA-16067, 00000, “activation identifier mismatch in archive log %s” Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database. Action: Locate the appropriate archive log for the database. |
| ORA-16068 ORA-16068, 00000, “redo log file activation identifier mismatch” Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database. Action: |
| ORA-16069 ORA-16069, 00000, “Archive Log standby database activation identifier mismatch” Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. |
| ORA-16070 ORA-16070, 00000, “parameter %s contains an invalid REGISTER attribute value” Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S). Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. |
| ORA-16071 ORA-16071, 00000, “dependency archived log file not found %s” Cause: The specified archived log file was not found at the indicated standby destination. Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file. |
| ORA-16072 ORA-16072, 00000, “a minimum of one standby database destination is required” Cause: No standby database archive log destinations were specified. Action: Specify a standby archive log destination in the initialization parameter file. |
| ORA-16073 ORA-16073, 00000, “archiving must be enabled” Cause: Online log file archiving is disabled. Action: Enable log file archiving. |
| ORA-16074 ORA-16074, 00000, “ARCH processes must be active” Cause: There are no active ARCH processes. Action: It is required that at least one ARCH process be active. |
| ORA-16075 ORA-16075, 00000, “standby database destination mismatch” Cause: A standby database destination was specified that is not accessed by another instance. Action: All database instances must access the same standby databases. |
| ORA-16076 ORA-16076, 00000, “unknown standby database destination” Cause: A standby database destination was specified that is not accessed by another instance. Action: All database instances must access the same standby databases. |
| ORA-16077 ORA-16077, 00000, “simulate network transmission error” Document: NO Cause: Used for internal testing – DO NOT USE. Action: If set, value will be returned as error. |
| ORA-16078 ORA-16078, 00000, “media recovery disabled” Cause: The database is not in ARCHIVELOG mode. Action: Place the database in ARCHIVELOG mode. |
| ORA-16079 ORA-16079, 00000, “standby archival not enabled” Cause: The standby database does not have archival enabled. Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active. |
| ORA-16080 ORA-16080, 00000, “invalid LogMiner session %s for APPLY” Cause: Logical standby apply engine was started with an invalid LogMiner session identifier. Action: Fix the problem with the LogMiner session or create a new session. |
| ORA-16081 ORA-16081, 00000, “insufficient number of processes for APPLY” Cause: Logical standby apply engine was started with fewer processes available than needed. Action: Increase the values of the initialization parameters PROCESSES and or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. |
| ORA-16082 ORA-16082, 00000, “logical standby is not initialized correctly” Cause: Logical standby apply engine was started but it found inconsistencies in its metadata. Action: Look in the trace file for more information. |
| ORA-16083 ORA-16083, 00000, “LogMiner session has not been created” Cause: Logical standby apply engine was started without creating a LogMiner session. Action: Create a LogMiner session and restart the apply engine. |
| ORA-16084 ORA-16084, 00000, “an apply engine is already running” Cause: A logical standby apply engine was running when another was created. Action: Shut down the previous apply engine before starting a new one. |
| ORA-16085 ORA-16085, 00000, “apply engine related event” Document: NO Cause: Action: |
| ORA-16086 ORA-16086, 0000, “standby database does not contain available standby log files” Cause: The primary database is in “no data loss” mode, but the standby database does not contain any “standby log files”. Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted. |
| ORA-16087 ORA-16087, 0000, “graceful switchover requires standby or current control file” Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file. Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation. |
| ORA-16088 ORA-16088, 0000, “archive log has not been completely archived” Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a “current” log file. Action: Specify a completed archive log. |
| ORA-16089 ORA-16089, 0000, “archive log has already been registered” Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted. Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information. |
| ORA-16090 ORA-16090, 0000, “archive log to be replaced not created by managed standby process” Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation. Action: No user action required. |
| ORA-16091 ORA-16091, 00000, “dependent archive log destination already archived” Cause: An archive log destination contains a dependency to another // archive log destination that has previously been archived. Action: The parent archive log destination cannot be dependent on another // archive log destination. Use the ALTER SYSTEM command to remove // one of the dependency attributes. |
| ORA-16092 ORA-16092, 00000, “dependent archive log destination is not active” Cause: An archive log destination contains a dependency to another // archive log destination that is not active” Action: The child archive log destination cannot be dependent on another // invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes. |
| ORA-16093 ORA-16093, 00000, “dependent archive log destination is not LGWR-enabled” Cause: An archive log destination contains a dependency to another // archive log destination that is not enabled for the LGWR process” Action: The child archive log destination cannot be dependent on another // archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process. |
| ORA-16094 ORA-16094, 00000, “database shutdown during archival operation” Cause: The database was shut down while an online log file archival was active. Action: None required. The ARCH process is terminated. |
| ORA-16095 ORA-16095, 00000, “Dependent destination removal for inactivation” Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user. Action: None required. |
| ORA-16096 ORA-16096, 00000, “ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY” Cause: None Action: Specify this command to prepare the primary database for switchover |
| ORA-16097 ORA-16097, 00000, “ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY” Cause: None Action: Specify this command to prepare the standby database for switchover |
| ORA-16098 ORA-16098, 00000, “inaccessible standby database forced shutdown to protect primary” Cause: No standby database archive log destinations remain accessible and the primary database is in “protected” no-data-loss mode. Action: Specify an alternate standby archive log destination in the initialization parameter file. |
| ORA-16099 ORA-16099, 00000, “internal error ORA-00600 occurred at standby database” Cause: The RFS process on the standby database received an internal error. Action: Check the standby alert log and RFS trace files for more information. // |
| ORA-16100 ORA-16100, 00000, “not a valid Logical Standby database” Cause: This database has not been completely configured as a Logical Standby database. Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax. |
| ORA-16101 ORA-16101, 00000, “a valid start SCN could not be found” Cause: An SCN from which to start could not be found. Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement. |
| ORA-16102 ORA-16102, 00000, “remote information is not available on the specified primary” Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream. Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information. |
| ORA-16103 ORA-16103, 00000, “Logical Standby apply must be stopped to allow this operation” Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation. Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation. |
| ORA-16104 ORA-16104, 00000, “Invalid Logical Standby parameter” Cause: The specified parameter is not valid. Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package documentation for the correct statement syntax. |
| ORA-16105 ORA-16105, 00000, “Logical Standby is already running in background” Cause: A Logical Standby apply operation is already running. Action: none |
| ORA-16106 ORA-16106, 0000, “Event for enabling netslave testing” Document: NO Cause: This is a Oracle internal event code. It is used to test LGWR or single ARCH sending log files using another netslave process. Action: N/A, this is a Oracle internal event code |
| ORA-16107 ORA-16107, 00000, “all log data from primary has been processed” Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command. Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; |
| ORA-16108 ORA-16108, 00000, “database is no longer a standby database” Cause: The current database has already been made a primary database. Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; |
| ORA-16109 ORA-16109, 00000, “failed to apply log data from previous primary” Cause: Log data from previous primary could not be completely applied. Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, re-issue command. |
| ORA-16110 ORA-16110, 00000, “user procedure processing of logical standby apply DDL” Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed. Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views. |
| ORA-16111 ORA-16111, 00000, “log mining and apply setting up” Cause: This logical standby process is setting up to begin processing changes. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16112 ORA-16112, 00000, “log mining and apply stopping” Cause: This logical standby process is cleaning up and stopping Logical Standby apply. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16113 ORA-16113, 00000, “applying change to table or sequence %s” Cause: The process is applying changes to a specific schema object. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16114 ORA-16114, 00000, “applying DDL transaction with commit SCN %s” Cause: The process is applying a DDL change that’s committed at the given SCN. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16115 ORA-16115, 00000, “%s\% of LogMiner dictionary loading is done” Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16116 ORA-16116, 00000, “no work available” Cause: The process is idle waiting for additional changes to be made available. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16117 ORA-16117, 00000, “processing” Cause: The process is performing its primary function and is not waiting on any significant event. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16118 ORA-16118, 00000, “enable RFS wait event threshold identification” Document: NO Cause: Specifies the maximum time, in hundreths of seconds, that an RFS // operation can take. Any RFS operation that exceeds this threshold logs a message with the operation duration to the RFS trace file. The value “100″ is “1″ second. Action: No action is required. |
| ORA-16119 ORA-16119, 00000, “building transaction at SCN %s” Cause: The transaction being committed at the given SCN is being prepared for apply. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16120 ORA-16120, 00000, “dependencies being computed for transaction at SCN %s” Cause: The transaction committed at the given SCN is being analyzed for dependencies. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16121 ORA-16121, 00000, “applying transaction with commit SCN %s” Cause: The transaction committed at the given SCN is being applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16122 ORA-16122, 00000, “applying large dml transaction at SCN %s” Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16123 ORA-16123, 00000, “transaction %s %s %s is waiting for commit approval” Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16124 ORA-16124, 00000, “transaction %s %s %s is waiting on another transaction” Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16125 ORA-16125, 00000, “large transaction %s %s %s is waiting for more data” Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16126 ORA-16126, 00000, “loading table or sequence %s” Cause: Information on the given table or sequence is being loaded into an in memory cache for future use. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16127 ORA-16127, 00000, “stalled waiting for additional transactions to be applied” Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes. |
| ORA-16128 ORA-16128, 00000, “User initiated stop apply successfully completed” Cause: Logical standby was shutdown in an orderly fashion. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16129 ORA-16129, 00000, “unsupported dml encountered” Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support. Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply. |
| ORA-16130 ORA-16130, 00000, “supplemental log information is missing from log stream” Cause: Supplemental logging is not enabled at the primary database. Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS; |
| ORA-16131 ORA-16131, 00000, “An error occurred during a Terminal Recovery of the standby.” Cause: An error occurred during a Terminal Recovery of the standby. Action: Check the standby alert log additional information. |
| ORA-16132 ORA-16132, 00000, “An error occurred during activation of the standby.” Cause: An error occurred during activation of the standby database following a Terminal Recovery. Action: Check the standby alert log additional information. |
| ORA-16133 ORA-16133, 00000, “Datafile %s has incorrect terminal recovery stamp.” Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption. Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery. |
| ORA-16134 ORA-16134, 00000, “invalid MANAGED recovery FINISH option” Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement. Action: Specify either nothing or NOWAIT following FINISH. |
| ORA-16135 ORA-16135, 00000, “Invalid LOG_ARCHIVE_CONFIG modification while in protected mode” Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode. Action: Make the modification before the database is opened by any instance. |
| ORA-16136 ORA-16136, 00000, “Managed Standby Recovery not active” Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active. Action: No action is necessary. |
| ORA-16138 ORA-16138, 00000, “end of log stream not received from primary” Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible. Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command. |
| ORA-16139 ORA-16139, 00000, “media recovery required” Cause: An error has occurred while performing a switchover. Action: If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed. See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database. // If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Verify that redo apply is active and wait until the SWITCHOVER_STATUS column of the V$DATABASE dynamic performance view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying the switchover. |
| ORA-16140 ORA-16140, 00000, “standby online logs have not been recovered” Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs. Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE. |
| ORA-16141 ORA-16141, 00000, “enable simulated archive log error” Document: NO Cause: Causes an error to be signalled during the archival operation. Action: No action is required. |
| ORA-16142 ORA-16142, 00000, “simulated archive log error” Document: NO Cause: Error returned for a simulated archival failure during // an archival operation. Action: No action is required. |
| ORA-16143 ORA-16143, 00000, “RFS connections not allowed during or after terminal recovery” Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery. Action: The primary must not attempt to archive to the standby after a terminal recovery. |
| ORA-16144 ORA-16144, 00000, “simulate RFS error while terminal recovery in progress” Document: NO Cause: Used for internal testing – DO NOT USE. Action: If set, value will be returned as error. |
| ORA-16145 ORA-16145, 00000, “archival for thread# %s sequence# %s in progress” Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived. Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command. |
| ORA-16146 ORA-16146, 00000, “standby destination control file enqueue unavailable” Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself. Action: Check for and eliminate the standby destination archive log parameter in question. |
| ORA-16147 ORA-16147, 00000, “standby database referenced by multiple archive log destinations” Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed. Action: Remove one of the duplicate archive log destinations. |
| ORA-16148 ORA-16148, 00000, “user requested expiration of managed recovery operation” Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement. Action: No action is required. |
| ORA-16149 ORA-16149, 00000, “enable simulated ARCH RAC archival testing” Document: NO Cause: Allows ARCH archival even when RAC not enabled Action: No action is required. |
| ORA-16150 ORA-16150, 00000, “FINISH recovery performed on another, older standby database” Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected. Action: No action is required. |
| ORA-16151 ORA-16151, 00000, “Managed Standby Recovery not available” Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation. Action: Wait for the managed standby recovery session to end. Then retry the operation. |
| ORA-16152 ORA-16152, 00000, “standby database is in ‘no-data-loss’ protected mode” Cause: The attempted database operation is not allowed while the standby database is in ‘no-data-loss’ protected mode. Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement. |
| ORA-16153 ORA-16153, 00000, “enable ARCH Physical RFS client debugging” Document: NO Cause: Enables the ARCH physical RFS client callback. Action: No action is required. |
| ORA-16154 ORA-16154, 00000, “suspect attribute: %s” Cause: Use of the indicated attribute is illegal in the given context. Action: Make the appropriate changes and reissue the statement. |
| ORA-16155 ORA-16155, 00000, “enable arch procs to not exceed log_archive_max_processes” Document: NO Cause: disallow arch processes to exceed log_archive_max_processes in releases prior to 9i. Note that in 9i and subsequent releases this event is not required. We reserve this event for 9i and subsequent releases to allow us to backport the new log_arch_max_processes behavior for earlier releases. Action: No action is required. |
| ORA-16156 ORA-16156, 00000, “LGWR archive log dependency not allowed if database is standby protected” Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files. Action: Remove the LGWR archive log dependency and use normal LGWR archival instead. |
| ORA-16157 ORA-16157, 00000, “media recovery not allowed following successful FINISH recovery” Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed. Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY. |
| ORA-16158 ORA-16158, 00000, “simulated failure during terminal recovery” Document: NO Cause: Causes an error to be signalled during terminal recovery. Action: No action is required. |
| ORA-16159 ORA-16159, 00000, “Cannot change protected standby destination attributes” Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database. Action: No action is required. |
| ORA-16160 ORA-16160, 00000, “Cannot change protected standby database configuration” Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode. Action: The standby database must be added to the configuration before the primary database is opened. |
| ORA-16161 ORA-16161, 00000, “Cannot mix standby and online redo log file members for group %s” Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group. Action: Verify the log file group type using the TYPE column of the V$LOG fixed view. |
| ORA-16162 ORA-16162, 00000, “Cannot add new standby databases to protected configuration” Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode. Action: The standby database must be added to the configuration before the primary database is opened. |
| ORA-16163 ORA-16163, 00000, “LGWR network server host attach error” Cause: The LGWR network server could not attach to remote host Action: The alert log contains more problem-specific information |
| ORA-16164 ORA-16164, 00000, “LGWR network server host detach error” Cause: The LGWR network server could not detach from remote host Action: The alert log contains more problem-specific information |
| ORA-16165 ORA-16165, 00000, “LGWR failed to hear from network server” Cause: The LGWR lost its connection to the network server Action: The alert log contains more problem-specific information |
| ORA-16166 ORA-16166, 00000, “LGWR network server failed to send remote message” Cause: The LGWR network server could not communicate with the remote host Action: The alert log contains more problem-specific information |
| ORA-16167 ORA-16167, 00000, “LGWR network server could not switch to non-blocking mode” Cause: The LGWR network server could not switch to non-blocking mode Action: The alert log contains more problem-specific information |
| ORA-16168 ORA-16168, 00000, “LGWR network server could not switch to blocking mode” Cause: The LGWR network server could not switch to blocking mode Action: The alert log contains more problem-specific information |
| ORA-16169 ORA-16169, 00000, “LGWR network server invalid parameters” Cause: The LGWR network server could not switch to blocking mode Action: The alert log contains more problem-specific information |
| ORA-16170 ORA-16170, 00000, “Terminal recovery may have left the database in an inconsistent state” Cause: When terminal recovery is invoked in a standby database // without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open. Action: Continue standby recovery with additional log shipping from primary. |
| ORA-16171 ORA-16171, 00000, “RECOVER…FINISH not allowed due to gap for thr %s, seq %s-%s” Cause: See alert log for more details Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER…FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files. |
| ORA-16172 ORA-16172, 00000, “archive logs detected beyond Terminal End-Of-Redo” Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR. Action: |
| ORA-16173 ORA-16173, 00000, “incompatible archival network connections active” Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented. Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation. |
| ORA-16174 ORA-16174, 00000, “user requested thread/sequence termination of managed recovery” Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement. Action: No action is required. |
| ORA-16175 ORA-16175, 00000, “cannot shut down database when media recovery is active” Cause: An attempt was made to shut down a standby database while media recovery was active. Action: Cancel media recovery to proceed with the shutdown. |
| ORA-16176 ORA-16176, 00000, “background dictionary build cannot be running” Cause: The background process dedicated to dictionary build is active. Action: wait and try it later. |
| ORA-16177 ORA-16177, 00000, “media recovery is not required” Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required. Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby. |
| ORA-16178 ORA-16178, 00000, “Cannot specify remote destinations in archivelog manual mode” Cause: The database is operating in ARCHIVELOG MANUAL mode. Remote archivelog destinations are not allowed in this mode. Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic archivelog mode, or defer the archivelog destinations that specify the SERVICE= attribute. |
| ORA-16179 ORA-16179, 00000, “incremental changes to \”%s\” not allowed with SPFILE” Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE. Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command. |
| ORA-16180 ORA-16180, 00000, “number of processes specified is too large” Cause: The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048. Action: Retry with a lower value. |
| ORA-16181 ORA-16181, 00000, “SGA specified for Logical Standby is too large” Cause: MAX_SGA is larger than the larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET. Action: Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower. |
| ORA-16182 ORA-16182, 00000, “Internal error on internal channel during remote archival” Cause: An internal error was encountered on the internal channel between LGWR and Network Server. Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival. |
| ORA-16183 ORA-16183, 00000, “Internal event for testing purposes” Document: NO Cause: This is an internal event used for testing purposes Action: No action is necessary. |
| ORA-16184 ORA-16184, 00000, “DB_UNIQUE_NAME %s hashes to the same value as DB_UNIQUE_NAME %s” Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME. Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value. |
| ORA-16185 ORA-16185, 00000, “REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive” Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive. Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter. |
| ORA-16186 ORA-16186, 00000, “Modifying LOG_ARCHIVE_CONFIG requires SID=’*’ qualifier” Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required. Action: Re-enter the command using the SID=’*’ qualifier. |
| ORA-16187 ORA-16187, 00000, “LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes” Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes. Action: Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter. |
| ORA-16188 ORA-16188, 00000, “LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance” Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances. Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings. |
| ORA-16189 ORA-16189, 00000, “Internal event for testing RTA purposes” Document: NO Cause: This is an internal event used for testing purposes Action: No action is necessary. |
| ORA-16190 ORA-16190, 00000, “Internal event for RFS Auth testing purposes” Document: NO Cause: This is an internal event used for testing purposes Action: No action is necessary. |
| ORA-16191 ORA-16191, 0000, “Primary log shipping client not logged on standby” Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials. Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE. |
| ORA-16192 ORA-16192, 0000, “Primary and standby network integrity mismatch” Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary. Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby. |
| ORA-16193 ORA-16193, 0000, “Primary and standby network encryption mismatch” Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary. Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby. |
| ORA-16194 ORA-16194, 00000, “Modifying DB_UNIQUE_NAME requires SID=’*’ qualifier” Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required. Action: Re-enter the command using the SID=’*’ qualifier. |
| ORA-16195 ORA-16195, 00000, “DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined” Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined. Action: Explicitly define a valid DB_UNIQUE_NAME. |
| ORA-16196 ORA-16196, 00000, “database has been previously opened and closed” Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime. Action: Shut down the instance. |
| ORA-16197 ORA-16197, 00000, “Invalid DB_UNIQUE_NAME parameter specification” Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and “_”, “$” and “#”. Action: Check the documentation and re-enter the parameter. |
| ORA-16198 ORA-16198, 00000, “Timeout incurred on internal channel during remote archival” Cause: A timeout was incurred during remote archival. Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival. |
| ORA-16199 ORA-16199, 00000, “Terminal recovery failed to recover to a consistent point” Cause: See alert log for more details Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support. |
| ORA-16200 ORA-16200, 00000, “Skip procedure requested to skip statement” Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16201 ORA-16201, 00000, “Skip procedure requested to apply statement” Cause: Logical standby called a skip procedure that requested for a particular statement to be applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16202 ORA-16202, 00000, “Skip procedure requested to replace statement” Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16203 ORA-16203, 00000, “Unable to interpret skip procedure return values” Cause: The skip procedure returned conflicting or invalid values. Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also ensure SKIP_ACTION is specified correctly. |
| ORA-16204 ORA-16204, 00000, “DDL successfully applied” Cause: A DDL statement has successfully commited on the logical standby database. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16205 ORA-16205, 00000, “DDL skipped due to skip setting” Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16206 ORA-16206, 00000, “database already configured as Logical Standby database” Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation. Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request. |
| ORA-16207 ORA-16207, 00000, “Logical standby dictionary build not permitted.” Cause: A dictionary build is currently in progress. Only one build can be active at a time. Action: Wait for the active build to complete before invoking a new build. |
| ORA-16208 ORA-16208, 00000, “Logical standby dictionary build failed to start.” Cause: Failure to start the logical standby dictionary build process (LSP1) Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| ORA-16209 ORA-16209, 00000, “Logical standby dictionary build failed to complete.” Cause: The logical standby dictionary build process terminated abnormally. Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| ORA-16210 ORA-16210, 00000, “Logical standby coordinator process terminated with error” Cause: The logical standby coordinator process terminated abnormally. Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| ORA-16211 ORA-16211, 00000, “unsupported record found in the archived redo log” Cause: Log apply services encountered a record in the archived redo log that could not be interpreted. Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it’s unimportant. 2. ALTER DATABASE START LOGICAL STANDBY APPLY; 3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record. 4. Provide the log file to Oracle Support Services. |
| ORA-16212 ORA-16212, 00000, “number of processes specified for SQL Apply is too great” Cause: Logical standby apply engine was started with more processes requested than are available. Action: Adjust the values of the initialization parameters PROCESSES or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. If you did not specify MAX_SERVERS, but instead specified PREPARE_SERVERS and APPLY_SERVERS through the dbms_logstdby.apply_set procedure, you will need to decrease either one or both of them. |
| ORA-16213 ORA-16213, 00000, “ddl encountered, stopping apply engine” Cause: stop_on_ddl callout specified and DDL was encountered. Action: Either disable stop_on_ddl callout or remove DDL. |
| ORA-16214 ORA-16214, 00000, “apply stalled for apply delay” Cause: A delay has been specified on the primary database for this destination. Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET(‘APPLY_DELAY’); to override. |
| ORA-16215 ORA-16215, 00000, “history metadata inconsistency” Cause: internal error. Action: This is an internal error. Contact Oracle support. |
| ORA-16216 ORA-16216, 00000, “Log stream sequence error” Cause: The log stream being processed did not follow the last processed stream. Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream. |
| ORA-16217 ORA-16217, 00000, “prepare to switchover has not completed” Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete. Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby. |
| ORA-16218 ORA-16218, 00000, “This database is already preparing to switch over.” Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt. Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request. |
| ORA-16219 ORA-16219, 00000, “This database is not preparing to switch over.” Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command. Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command. |
| ORA-16220 ORA-16220, 00000, “no failed transaction found” Cause: No failed transaction was found. Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option. |
| ORA-16221 ORA-16221, 00000, “history table synchronization error” Cause: internal error. Action: This is an internal error. Contact Oracle support. |
| ORA-16222 ORA-16222, 00000, “automatic Logical Standby retry of last action” Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply. Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16223 ORA-16223, 00000, “DDL skipped, unsupported in current version” Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped. Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16224 ORA-16224, 00000, “Database Guard is enabled” Cause: Operation could not be performed because database guard is enabled Action: Verify operation is correct and disable database guard |
| ORA-16225 ORA-16225, 00000, “Missing LogMiner session name for Streams” Cause: An attempt was made to register the log file for Streams without a specified LogMiner session name. Action: Specify a valid LogMiner session name to which the log file will be registered. |
| ORA-16226 ORA-16226, 00000, “DDL skipped due to lack of support” Cause: Logical Standby does not support this type of DDL in this version, so the DDL is skipped. Action: The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details. |
| ORA-16227 ORA-16227, 00000, “DDL skipped due to missing object” Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database. Action: No action is necessary, this infomational statement is provided to record the event for diagnostic purposes. |
| ORA-16228 ORA-16228, 00000, “Insufficient recovery for logical standby” Cause: Insufficient amount of recovery was run for logical standby instantiation. Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE. |
| ORA-16229 ORA-16229, 00000, “PDML child %s %s %s for parent %s %s %s cannot be skipped.” Cause: A request was made to skip a parallel DML child transaction id. This is not supported. Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate. |
| ORA-16230 ORA-16230, 00000, “committing transaction %s %s %s” Cause: Logical Standby apply was committing changes for the given transaction. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16232 ORA-16232, 00000, “adding Logical Standby skip entry for table %s.%s” Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported. Action: To have Logical Standby maintain the table, import that table directly from the primary. |
| ORA-16233 ORA-16233, 00000, “The table %s.%s is unsupported now” Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions. Action: None. |
| ORA-16234 ORA-16234, 00000, “restarting to reset Logical Standby apply” Cause: Logical Standby encountered a work load that required a restart to properly reschedule. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16235 ORA-16235, 00000, “DDL skipped because import has occurred” Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16236 ORA-16236, 00000, “Logical Standby metadata operation in progress” Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished. Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation. |
| ORA-16237 ORA-16237, 00000, “SGA specified for Logical Standby is too small” Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby. Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes. |
| ORA-16238 ORA-16238, 00000, “attempt to use version 9 log” Cause: Version 9 log files are not supported. Action: Use log files of a supported version. |
| ORA-16239 ORA-16239, 00000, “IMMEDIATE option not available without standby redo logs” Cause: The IMMEDIATE option cannot be used without standby redo logs. Action: Do not specify the IMMEDIATE option unless standby redo logs are being used. |
| ORA-16240 ORA-16240, 00000, “Waiting for logfile (thread# %s, sequence# %s)” Cause: Reader process is idle waiting for additional logfile to be available. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16241 ORA-16241, 00000, “Waiting for gap logfile (thread# %s, sequence# %s)” Cause: Reader process is idle waiting for the logfile to fill the log sequence gap. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16242 ORA-16242, 00000, “Processing logfile (thread# %s, sequence# %s)” Cause: Reader process is processing the logfile. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16243 ORA-16243, 00000, “paging out %s bytes of memory to disk” Cause: Builder process is paging out momery to free up space in lcr cache. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16246 ORA-16246, 00000, “User initiated abort apply successfully completed” Cause: SQL Apply was stopped using the abort option. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16247 ORA-16247, 00000, “DDL skipped on internal schema” Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = ‘INTERNAL SCHEMA’. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16248 ORA-16248, 00000, “RFS connections not permitted during Terminal Apply” Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply. Action: Permit any outstanding Logical Standby operations to complete. |
| ORA-16249 ORA-16249, 00000, “Terminal apply failed to complete during failover” Cause: The logical standby coordinator process terminated abnormally.” Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover. |
| ORA-16250 ORA-16250, 00000, “Failed to acquire starting scn of new log stream” Cause: The starting SCN for the new log stream could not be determined. Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command. |
| ORA-16251 ORA-16251, 00000, “LSP1 Background Build not permitted” Cause: The LSP1 background process is not permitted to start because it had previously been attempted. Action: This is an internal error. Contact Oracle support. |
| ORA-16252 ORA-16252, 00000, “Rebuild operation not permitted” Cause: The REBUILD operation is not permitted. Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete. |
| ORA-16253 ORA-16253, 00000, “Logical Standby cannot start due to incomplete terminal apply” Cause: A previous ACTIVATE of the logical standby failed to complete. Action: Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command. |
| ORA-16254 ORA-16254, 00000, “change db_name to %s in the client-side parameter file (pfile)” Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile). Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again. |
| ORA-16255 ORA-16255, 00000, “Log Auto Delete conflicts with another LogMiner session” Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database. Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first. |
| ORA-16256 ORA-16256, 00000, “Failure to complete standby redo logfile archival after failover” Cause: The standby redo logfiles processed during the failover of a logical standby were not archived. Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival. |
| ORA-16257 ORA-16257, 00000, “Switchover initiated stop apply successfully completed” Cause: SQL Apply was stopped because of a switchover. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16258 ORA-16258, 00000, “marking index unusable due to a constraint violation” Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted. Action: No action necessary. See alert log for index schema and name. |
| ORA-16259 ORA-16259, 00000, “Switchover to logical standby requires a log archive destination” Cause: A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required. Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation. |
| ORA-16260 ORA-16260, 00000, “Waiting to replace partial or corrupt logfile (thread# %s, sequence# %s)” Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered. Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file. |
| ORA-16261 ORA-16261, 00000, “Identification key mismatch for table \”%s\”.\”%s\”.” Cause: Internal error in SQL Apply. Action: Contact Oracle Support Services. |
| ORA-16262 ORA-16262, 00000, “Invalid value specified for Logical Standby parameter” Cause: The value specified in APPLY_SET is invalid for the parameter. Action: Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY PL/SQL package for details. |
| ORA-16263 ORA-16263, 00000, “Dynamic parameters can only be set on SQL apply instance” Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running. Action: Connect to the instance where SQL apply coordinator is running and re-issue the statement. |
| ORA-16264 ORA-16264, 00000, “invalid value for PREPARE_SERVERS parameter” Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased. Action: set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly. |
| ORA-16265 ORA-16265, 00000, “Unsupported PL/SQL procedure encountered” Cause: Apply encountered an unsupported procedure from an Oracle supplied PL/SQL package that is otherwise supported Action: Either add a skip rule for this procedure or manually apply the procedure and restart apply skipping the failed transaction Please refer to documentation on the PL/SQL package for details. |
| ORA-16266 ORA-16266, 00000, “Cannot instantiate a Logical Standby from another Logical Standby” Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported. Action: Instantiate a Logical Standby database only from a Primary Database. |
| ORA-16267 ORA-16267, 00000, “Cannot instantiate a Logical Standby during a switchover” Cause: An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover. Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again. |
| ORA-16268 ORA-16268, 00000, “user procedure processing of logical standby apply PL/SQL” Cause: A user-provided stored procedure was called to inspect a PL/SQL statement prior to the statement being processed. Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views. |
| ORA-16269 ORA-16269, 00000, “PL/SQL procedure skipped due to failure on primary database” Cause: Because the PL/SQL procedure failed when executed on the primary database, it could not be executed on the standby database. Action: This informational statement is provided to record the event for diagnostic purposes. The failed PL/SQL procedure needs to be investigated to ensure it did not commit interesting data before it failed. |
| ORA-16270 ORA-16270, 00000, “PL/SQL procedure skipped due to unmaintained standby objects” Cause: Because the PL/SQL procedure manipulated objects not being maintained by the standby database, it was skipped. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16271 ORA-16271, 00000, “PL/SQL successfully applied” Cause: A PL/SQL procedure was successfully applied on the logical standby database. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16272 ORA-16272, 00000, “PL/SQL procedure skipped due to skip setting” Cause: A setting in the logical standby skip table indicated that this PL/SQL procedure should always be skipped. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. |
| ORA-16273 ORA-16273, 00000, “invalid value for APPLY_SERVERS parameter” Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased. Action: set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly. |
| ORA-16274 ORA-16274, 00000, “failure to perform DDL on all RAC instances” Cause: One or more instances encountered an error while performing an operation. Action: Ensure every instance in the RAC meets the requirements for the operation, and retry the operation. |
| ORA-16275 ORA-16275, 00000, “prior failed CTAS detected and pre-existing table dropped” Cause: During the processing of a CTAS operation, an existing empty table with the same name and attributes as the CTAS source table was found, and the table was dropped. Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes. |
| ORA-16276 ORA-16276, 00000, “specified database link does not correspond to primary database” Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database. Action: Specify a database link that corresponds to the primary database for this logical standby database. The link should have privileges to read and lock the table being instantiated, as well as the SELECT_CATALOG_ROLE. |
| ORA-16277 ORA-16277, 00000, “specified table is not supported by logical standby database” Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate an unsupported table on the logical standby database. Tables with unsupported data types cannot be replicated to a logical standby database. Action: Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view. |
| ORA-16278 ORA-16278, 00000, “specified table has a multi-object skip rule defined” Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters. Action: Remove or rewrite any skip rules defined for the specified table so that they no longer contain wildcard characters, or no longer affect the specified table. |
| ORA-16279 ORA-16279, 00000, “Supplied dblink must have CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles” Cause: A dblink was specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE that lacked one or more of the CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles. Action: Grant the CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles to the specified dblink, and retry the operation. |
| ORA-16280 ORA-16280, 00000, “cannot change master key on a logical standby database” Cause: An attempt was made to change the master key for transparent data encryption on a logical standby database. Action: Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database. |
| ORA-16281 ORA-16281, 00000, “missing identification key for table \”%s\”.\”%s\”.” Cause: No identification key was created for specified table. Action: Create a primakey key or unique index for specified table. |
| ORA-16282 ORA-16282, 00000, “operation not permitted during rolling upgrade” Cause: An operation was attempted that is not supported during a rolling upgrade. Action: Retry the operation upon completion of the upgrade. |
| ORA-16300 ORA-16300, 00000, “LSBY architected tracing event” Cause: Action: |
| ORA-16301 ORA-16301, 00000, “LSBY debug event” Cause: Action: Document: NO |
| ORA-16400 ORA-16400, 00000, “quota attributes are not allowed with DB_RECOVERY_FILE_DEST” Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined. Action: No action is required. |
| ORA-16401 ORA-16401, 00000, “archivelog rejected by RFS” Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database. Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes. |
| ORA-16402 ORA-16402, 00000, “ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support” Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters. Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error. |
| ORA-16403 ORA-16403, 00000, “shutdown in progress – remote connection is not permitted” Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE. Action: Wait for the remote instance to be restarted, or contact your DBA. |
| ORA-16404 ORA-16404, 0000, “Internal event for simulating software version mismatches” Document: NO Cause: This is an Oracle internal event code. It is used to test software version mismatches between the primary and a standby database. Setting this event causes the software version number to be incremented by the value of the event level. Action: N/A, this is a Oracle internal event code |
| ORA-16405 ORA-16405, 0000, “Internal event for simulating software version mismatches” Document: NO Cause: This is an Oracle internal event code. It is used to test software version mismatches between the primary and a standby database. Setting this event causes the software version number to be decremented by the value of the event level. Action: N/A, this is a Oracle internal event code |
| ORA-16406 ORA-16406, 0000, “Primary and standby database software version mismatch” Cause: The primary database and standby database Oracle software is not compatible. Action: Install the correct Oracle software and try again. |
| ORA-16407 ORA-16407, 00000, “Standby database is in the future of the archive log” Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs. Action: No action is required. |
| ORA-16408 ORA-16408, 00000, “Incompatible archival Redo Branch lineage” Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs. Action: No action is required. |
| ORA-16409 ORA-16409, 00000, “Archive log switchover reference number mismatch” Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. Action: No action is required. |
| ORA-16410 ORA-16410, 00000, “enable simulated LGWR netslave infinite wait” Document: NO Cause: Causes the LGWR to wait indefinitely to simulate network connection indefinite stall. Action: N/A, this is a Oracle internal event code |
| ORA-16411 ORA-16411, 00000, “ONDEMAND archival requires active managed recovery operation” Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection. Action: Start the managed recovery operation on the standby database. |
| ORA-16412 ORA-16412, 00000, “ONDEMAND archival requires active SQL apply operation” Cause: The use of the ONDEMAND attribute for a logical standby database destination requires that the SQL apply operation be active prior to establishing the network connection. Action: Start the SQL apply operation on the standby database. |
| ORA-16413 ORA-16413, 00000, “Unsupported database type for ONDEMAND archivelog destinations” Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute. Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database. |
| ORA-16414 ORA-16414, 0000, “Event to prevent MRP from clearing online redo logfiles” Document: NO Cause: This is a Oracle internal event code. This event is used to prevent the MRP process from automatically creating and/or clearing the online redo logfiles (ORLs) on a standby database. Action: N/A, this is a Oracle internal event code |
| ORA-16415 ORA-16415, 0000, “Event to enable lock dumping” Document: NO Cause: This is a Oracle internal event code. This event is used to enable dumping of lock structures when desired. Action: N/A, this is a Oracle internal event code |
| ORA-16416 ORA-16416, 00000, “Switchover target is not synchronized with the primary” Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted. Action: Allow the switchover target to become synchronized and then re-attempt the switchover. |
| ORA-16417 ORA-16417, 00000, “Activation occurred after recovery from standby redo log files; a full database backup is required” Cause: Activation occurred after recovery from standby redo log files. Action: Take a full database backup. |
| ORA-16418 ORA-16418, 0000, “Event to simulate idle RFS process in Physical Standby” Document: NO Cause: This is a Oracle internal event code. This event is used to simulate idle RFS process in Physical Standby Action: N/A, this is a Oracle internal event code |
| ORA-16419 ORA-16419, 00000, “Snapshot standby must be converted from physical standby” Cause: The database is not physical standby. Action: Convert to physical standby and retry the operation. |
| ORA-16420 ORA-16420, 00000, “fast-start failover target cannot be converted to snapshot standby” Cause: The database chosen for conversion to a snapshot standby was the fast-start failover target standby database. Action: Choose another physical standby database and retry the operation. |
| ORA-16421 ORA-16421, 00000, “Event to disable streaming network I/O for Data Guard” Document: NO Cause: This is a Oracle internal event code. This event is used to disable streaming I/O for vaious Data Guard processes. Action: N/A, this is a Oracle internal event code |
| ORA-16422 ORA-16422, 0000, “Event to disable archive process functions” Document: NO Cause: This is a Oracle internal event code. This event is used to disable archive process functions Action: N/A, this is a Oracle internal event code |
| ORA-16423 ORA-16423, 0000, “Event to test ASM mirrors in Physical Standby” Document: NO Cause: This is a Oracle internal event code. This event is used to test ASM mirrors in Physical Standby. Action: N/A, this is a Oracle internal event code |
| ORA-16424 ORA-16424, 0000, “Terminal recovery cannot start due to GAP on Physical Standby” Cause: Terminal Recovery failed because of gap behind the start point of standby recovery. Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE |
| ORA-16425 ORA-16425, 0000, “Terminal recovery branch %s older than target branch %s” Cause: Terminal Recovery failed because of new branch on Physical Standby. Action: Issue real time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another terminal recovery. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE |
| ORA-16426 ORA-16426, 0000, “log requested by recovery is not the correct log” Cause: Media recovery has selected an incorrect log Action: Verify that the proper log has been properly registered and restart media recovery. |
| ORA-16427 ORA-16427, 0000, “Potential archive log gap too large to service” Cause: Standby destination is too far behind the primary database for automatic archive log gap detection/resolution to take place. Action: Standby database should be recreated with a recent backup copy of the primary database. |
| ORA-16428 ORA-16428, 0000, “Event to set timeout value for ORA-19528 error” Document: NO Cause: This is an Oracle internal event code. This event is used to set the timeout value for the ORA-19528 error. Action: N/A, this is an Oracle internal event code |
| ORA-16429 ORA-16429, 0000, “Event to disable Redo Transport Compression (RTC) back-off logic” Document: NO Cause: This is a Oracle internal event code. This event is used to disable Redo Transport Compression (RTC) back-off logic. Action: N/A, this is a Oracle internal event code |
| ORA-16430 ORA-16430, 00000, “Event to kick off krs*.c error path tests” Document: NO Cause: Oracle internal testing only Action: N/A, this is an Oracle intenal event for test purposes (valid values are 1-26, 1 for krsa.c up through 26 for krsz.c) |
| ORA-16431 ORA-16431, 00000, “Cannot expand control file” Cause: More threads were added on the primary database after this standby control file was created. Action: Shut down the standby database, either replace the control file with a new standby control file from primary database or change the COMPATIBLE parameter to 10.2.0 or above, and restart the standby database. |
| ORA-16432 ORA-16432, 00000, “inconsistent set of terminal logs detected” Cause: Media Recovery stopped because it detected an inconsistency between the first log in the new incarnation and the state of the previous incarnation. If this database is a bystander standby database, this is most likely because there was a failover operation, and this database applied terminal logs generated from that failover operation for some redo threads but applied corresponding logs from the old primary database of that failover operation for some other redo threads. Action: Flashback or restore this database to before the standby_became_primary_scn of that failover operation and restart media recovery. The standby_became_primary_scn of the failover operation can be obtained from V$DATABASE on the new primary. |
| ORA-16433 ORA-16433, 00000, “The database has not been opened in read-write mode” Cause: When a physical standby database is converted to a read-write database or there was a failed open resetlogs attempt, the database should be opened in read-write mode to have correct file access information in the controlfile. Action: Open the database in read-write mode and reissue the command. |
| ORA-16438 ORA-16438, 00000, “Switchover to primary cannot be executed at this time” Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details. Action: Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY. |
| ORA-16501 ORA-16501, 00000, “the Data Guard broker operation failed” Cause: The Data Guard broker operation failed. Action: See accompanying messages for details. |
| ORA-16502 ORA-16502, 00000, “the Data Guard broker operation succeeded with warnings” Cause: The Data Guard broker operation succeeded with warnings. Action: See accompanying messages for details. |
| ORA-16503 ORA-16503, 00000, “site ID allocation failure” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16504 ORA-16504, 00000, “the Data Guard configuration already exists” Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration. Action: To create a new configuration, the existing configuration must be deleted. |
| ORA-16505 ORA-16505, 00000, “site ID is invalid” Cause: The request contained an invalid site ID. Action: Make the request again with a valid site ID. |
| ORA-16506 ORA-16506, 00000, “out of memory” Cause: Process exceeded private or shared memory limits. Action: Check for memory leaks, increase system parameters and restart. |
| ORA-16507 ORA-16507, 00000, “unrecognized request identifier” Cause: The specified request identifier was not recognized by the Data Guard broker. Action: Reissue the request using a valid request identifier. |
| ORA-16508 ORA-16508, 00000, “channel handle not initialized” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16509 ORA-16509, 00000, “request timed out” Cause: The Data Guard broker timed out out the request. Action: Check the Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request. |
| ORA-16510 ORA-16510, 00000, “messaging error using ksrwait” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16511 ORA-16511, 00000, “messaging error using ksrget” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16512 ORA-16512, 00000, “parameter exceeded maximum size limit” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16513 ORA-16513, 00000, “maximum requests exceeded” Cause: The maximum number of requests that the broker can service |
| ORA-16514 ORA-16514, 00000, “request was not found” Cause: An attempt was made to read a response but a matching request was not found. Action: Verify request identifier is valid and that it references a previously issued request. |
| ORA-16515 ORA-16515, 00000, “no receive channel” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16516 ORA-16516, 00000, “current state is invalid for the attempted operation” Cause: The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either: // – The databases changing roles are shut down. – The primary database is not shipping redo data. – The standby database that will become the primary database is not applying redo data. // If this error was returned for database state change operations, the database state specified was invalid. Action: If this error is returned when attempting a switchover operation, make sure that: // – The databases changing roles are started. – The primary database is shipping redo data. – The standby database is applying redo data. // If this error is returned when attempting a database state change operation, make sure a valid database state is specified. |
| ORA-16517 ORA-16517, 00000, “object handle is invalid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16518 ORA-16518, 00000, “unable to allocate virtual instance ID” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16519 ORA-16519, 00000, “resource handle is invalid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16520 ORA-16520, 00000, “unable to allocate resource ID” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16521 ORA-16521, 00000, “unable to create generic template ID” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16522 ORA-16522, 00000, “generic template not found” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16523 ORA-16523, 00000, “operation requires the client to connect to instance \”%s\”" Cause: The switchover or failover operation required the client to connect to the apply instance of the target database. Action: Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command. |
| ORA-16524 ORA-16524, 00000, “unsupported operation” Cause: A command or option was not supported in this release. Action: Contact Oracle Support Services. |
| ORA-16525 ORA-16525, 00000, “the Data Guard broker is not yet available” Cause: The Data Guard broker process was either not yet started, was initializing, or failed to start. Action: If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation. |
| ORA-16526 ORA-16526, 00000, “unable to allocate task element” Cause: The Data Guard broker was unable to allocate memory for a request. Action: Increase the size of the SGA. |
| ORA-16527 ORA-16527, 00000, “unable to allocate broker SGA memory” Cause: The Data Guard broker was unable to allocate memory within the SGA. Action: Increase the size of the SGA memory. |
| ORA-16528 ORA-16528, 00000, “unable to allocate PGA memory” Cause: There was insufficient space in PGA to allocate memory. Action: Increase process virtual memory. |
| ORA-16529 ORA-16529, 00000, “bad sender ID” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16530 ORA-16530, 00000, “invalid buffer or length” Cause: A NULL buffer or a length of zero was specified. Action: Correct the command parameters and retry the command. |
| ORA-16531 ORA-16531, 00000, “unable to post message” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16532 ORA-16532, 00000, “Data Guard broker configuration does not exist” Cause: A broker operation was requested that required a broker configuration to already be created. Action: Create a Data Guard broker configuration prior to performing other broker operations. |
| ORA-16533 ORA-16533, 00000, “inconsistent Data Guard broker state” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16534 ORA-16534, 00000, “no more requests accepted” Cause: The Data Guard broker returned this status because either: – A failover operation was submitted or was in progress. – A switchover operation was submitted or was in progress. – An instance restart was pending for one or more databases. Action: Wait until the operation is complete and reissue the request. |
| ORA-16535 ORA-16535, 00000, “CRS is preventing execution of a broker operation” Cause: The broker was unable to have CRS stop management of all of the instances of this database. Action: Suspend CRS management of this database using the SRVCTL STOP DATABASE -D <NAME> -O NONE command. Then reissue the broker request. |
| ORA-16536 ORA-16536, 00000, “unknown object type” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16537 ORA-16537, 00000, “child count exceeded” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16538 ORA-16538, 00000, “no match on requested item” Document: NO Cause: The Data Guard broker did not recognize the specified property or state name. Action: Verify command parameters and reissue the request. |
| ORA-16539 ORA-16539, 00000, “task element not found” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16540 ORA-16540, 00000, “invalid argument” Document: NO Cause: One of the arguments for the specified request was invalid for the request type. Action: Verify arguments and then reissue the request. |
| ORA-16541 ORA-16541, 00000, “database is not enabled” Cause: The database specified in the request was not enabled. Action: Select an enabled database and reissue the request. |
| ORA-16542 ORA-16542, 00000, “unrecognized operation” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16543 ORA-16543, 00000, “invalid request made to broker” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16544 ORA-16544, 00000, “modifying DG_BROKER_START requires SID=’*’ qualifier” Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID=’*’ qualifier was required in the command. Action: Reenter the command using the SID=’*’ qualifier. |
| ORA-16545 ORA-16545, 00000, “unable to get response” Cause: The Data Guard broker was unable to return the result of a previous request. Action: Contact Oracle Support Services. |
| ORA-16546 ORA-16546, 00000, “missing or invalid value” Cause: The value of the request to return was not specified or was invalid. Action: Specify the value of the response starting from one. |
| ORA-16547 ORA-16547, 00000, “cannot disable or delete the primary database” Cause: An attempt was made to disable broker management of the primary database or delete the primary database from the broker configuration while the configuration was enabled. Action: If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to delete the primary database from the broker configuration while the configuration is enabled, you must instead delete the entire broker configuration. |
| ORA-16548 ORA-16548, 00000, “database not enabled” Cause: An attempt was made to modify or query a disabled database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created because of a failover or switchover operation. Action: If broker management of the database is disabled, enable it and reissue the request. |
| ORA-16549 ORA-16549, 00000, “invalid string” Cause: An invalid or NULL string value was specified. Action: Correct command parameters and retry. |
| ORA-16550 ORA-16550, 00000, “truncated result” Cause: A string property value was truncated due to insufficient buffer size. Action: Specify a larger receive buffer. |
| ORA-16551 ORA-16551, 00000, “short string copied” Cause: A string property value that did not fill the receive buffer was placed in the receive buffer. Action: This is an informational message only. |
| ORA-16552 ORA-16552, 00000, “an error occurred when generating the CLIENT OPERATION table” Cause: An error occurred while Data Guard broker was generating the CLIENT OPERATION table. Action: See the next error message for more detailed information. Execute the action described in the next error or contact Oracle Support Services. |
| ORA-16553 ORA-16553, 00000, “the Data Guard broker process (DMON) failed to shutdown” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16554 ORA-16554, 00000, “translation not valid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16555 ORA-16555, 00000, “database is not active” Cause: An operation was attempted on a database that was not active. not active. Action: Verify that the database is active and retry the operation. |
| ORA-16556 ORA-16556, 00000, “observer version mismatch” Cause: This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server. Action: Use a version of the observer that is compatible with the Oracle database server to be observed. |
| ORA-16557 ORA-16557, 00000, “database is already in use” Cause: An attempt was made to create a duplicate database in the broker configuration. Action: Check the database to be added to ensure there are no duplicates. |
| ORA-16558 ORA-16558, 00000, “database specified for switchover is not a standby database” Cause: An attempt was made to switchover to a database that was not a standby database. Action: Locate an enabled standby database and select that database as the target of the switchover. |
| ORA-16559 ORA-16559, 00000, “out of memory at %s” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16560 ORA-16560, 00000, “unable to convert document, syntax error at \”%s\” ” Document: NO Cause: There was an error in the specified sting. Action: Correct the errors and submit the request again. |
| ORA-16561 ORA-16561, 00000, “cannot remove an active instance” Cause: The instance to be removed was running. Action: Shut down the instance and reissue the REMOVE command. |
| ORA-16562 ORA-16562, 00000, “INTENDED_STATE not used here, syntax error at \”%s\”" Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16563 ORA-16563, 00000, “unable to add value, syntax error at \”%s\”" Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16564 ORA-16564, 00000, “lookup failed, syntax error at %s” Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16565 ORA-16565, 00000, “duplicate property, syntax error at \”%s\”" Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16566 ORA-16566, 00000, “unsupported document type” Document: NO Cause: The XML document type was not supported. Action: Correct the errors and submit the request again. |
| ORA-16567 ORA-16567, 00000, “Data Guard broker internal parser error at \”%s\”" Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16568 ORA-16568, 00000, “cannot set property %s” Cause: The specified property could not be modified because it was either a monitorable property or a property that did not exist. Action: Retry the command with a valid configurable property. |
| ORA-16569 ORA-16569, 00000, “Data Guard configuration is not enabled” Cause: The requested operation required that broker management of the Data Guard configuration must be enabled. Action: Enable the Data Guard configuration and reissue the request. |
| ORA-16570 ORA-16570, 00000, “database needs restart” Cause: The Data Guard broker operation required this database instance to be shut down and restarted. Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it. |
| ORA-16571 ORA-16571, 00000, “Data Guard configuration file creation failure” Cause: The Data Guard broker was unable to create the configuration file on permanent storage. Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation. |
| ORA-16572 ORA-16572, 00000, “Data Guard configuration file not found” Cause: The Data Guard broker configuration file was either unavailable or did not exist. Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. |
| ORA-16573 ORA-16573, 00000, “attempt to change or access configuration file for an enabled broker configuration” Cause: The operation was rejected because the Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example: – An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running. – Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information. Action: Disable the broker configuration and shut down the Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration. |
| ORA-16574 ORA-16574, 00000, “switchover disallowed when required databases are shut down” Cause: Switchover failed because either the primary database or the designated standby database were shut down. Action: Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database. |
| ORA-16575 ORA-16575, 00000, “request terminated at broker discretion” Cause: This error was returned when the broker terminated a command because it was processing a failover command. Action: Wait for failover to complete and then retry the command. |
| ORA-16576 ORA-16576, 00000, “failed to update Data Guard configuration file” Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage. Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. |
| ORA-16577 ORA-16577, 00000, “corruption detected in Data Guard configuration file” Cause: The Data Guard broker detected errors while loading the configuration file. Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services. |
| ORA-16578 ORA-16578, 00000, “failed to read Data Guard configuration file” Cause: A failure was encountered while the broker was reading the configuration file on permanent storage. Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. |
| ORA-16579 ORA-16579, 00000, “bad network state detected” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16580 ORA-16580, 00000, “bad network link” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16581 ORA-16581, 00000, “Data Guard broker could not reach remote database” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16582 ORA-16582, 00000, “cannot change instance-specific property” Cause: An attempt was made to change an instance-specific property for a database that had more than one instance. Action: Retry the command and identify a specific instance whose property value is to be changed. |
| ORA-16583 ORA-16583, 00000, “bad Data Guard broker connection process state” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16584 ORA-16584, 00000, “illegal operation on a standby database” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16585 ORA-16585, 00000, “illegal operation on a primary database” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16586 ORA-16586, 00000, “cannot change database property with EDIT INSTANCE command” Cause: An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command. Action: Use an EDIT DATABASE command to change database properties. |
| ORA-16587 ORA-16587, 00000, “ambiguous object specified to Data Guard broker” Cause: An object was specified that the broker could not uniquely distinguish from other objects in the configuration. Action: Try to further distinguish the object specified for the operation and reissue the command. |
| ORA-16588 ORA-16588, 00000, “no more internal buffers” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16589 ORA-16589, 00000, “Data Guard broker detected network transfer error” Cause: The Data Guard broker detected an error while transferring data from one database to another. This may happen when: – the broker detects an inconsistency in the block count of configuration file when the file is transmitted between databases. – the broker encountered an error when writing the configuration file. Action: Contact Oracle Support Services. |
| ORA-16590 ORA-16590, 00000, “Data Guard configuration does not contain a primary database” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16591 ORA-16591, 00000, “unknown field \”%s\” in document” Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16592 ORA-16592, 00000, “missing field \”%s\” in document” Document: NO Cause: There was an error in the specified string. Action: Correct the errors and submit the request again. |
| ORA-16593 ORA-16593, 00000, “XML conversion failed” Document: NO Cause: There was an error in the XML document. Action: Correct the errors and submit the request again. |
| ORA-16594 ORA-16594, 00000, “DMON background process is not running” Cause: The Data Guard broker background process, DMON, was not running. Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is not running. |
| ORA-16595 ORA-16595, 00000, “process %s failed to terminate” Cause: The specified process did not terminate at the request of the Data Guard broker. Action: Contact Oracle Support Services. |
| ORA-16596 ORA-16596, 00000, “database not part of the Data Guard broker configuration” Cause: The specified database is not in the Data Guard broker configuration. Action: Retry the command with a database that is in the broker configuration. |
| ORA-16597 ORA-16597, 00000, “Data Guard broker detects two or more primary databases” Cause: The Data Guard broker detected two or more primary databases in the broker configuration and could not continue. Action: Contact Oracle Support Services. |
| ORA-16598 ORA-16598, 00000, “Data Guard broker detected a mismatch in configuration” Cause: The Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more databases in the broker configuration. This can occur when the primary database has stale broker configuration files. Action: Contact Oracle Support Services. |
| ORA-16599 ORA-16599, 00000, “Data Guard broker detected a stale configuration” Cause: The Data Guard broker detected a stale configuration during initialization for this database. Action: The broker will automatically resolve this situation once the primary database completes its initialization. |
| ORA-16600 ORA-16600, 00000, “not connected to target standby database for failover” Cause: The failover command failed because the client was not connected to the target standby database. Action: Explicitly connect to the standby database to be failed over to and retry the failover command. |
| ORA-16601 ORA-16601, 00000, “site contains required resources that are disabled” Document: NO Cause: Resources required to complete this command were disabled. Action: Enable all required resources and reissue the request. |
| ORA-16602 ORA-16602, 00000, “database must be disabled to perform this operation” Cause: An attempt was made to edit a database property while the database was enabled. Action: Disable the database and retry the command. |
| ORA-16603 ORA-16603, 00000, “Data Guard broker detected a mismatch in configuration ID” Cause: There was a mismatch in configuration unique ID. This could occur if the original configuration was re-created while this database was disconnected from the network or the same database was added to two different Data Guard broker configurations. Action: Make sure the database belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to false. Then remove the Data Guard broker configuration files. Finally restart the broker by setting the DG_BROKER_START initialization parameter to true. |
| ORA-16604 ORA-16604, 00000, “unable to describe template using package \”%s\”" Document: NO Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package. Action: Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package. |
| ORA-16605 ORA-16605, 0000, “event to control fast-start failover diagnostic tracing” Document: NO Cause: This is an Oracle internal event code. This event is used to control fast-start failover diagnostic tracing. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16606 ORA-16606, 00000, “unable to find property \”%s\”" Cause: The specified property did not exist. Action: Specify a valid property name and reissue the request. |
| ORA-16607 ORA-16607, 00000, “one or more databases have failed” Cause: A failure was detected for one or more databases in the Data Guard broker configuration. Action: Locate the database(s) with a failure status and correct it. |
| ORA-16608 ORA-16608, 00000, “one or more databases have warnings” Cause: A warning was detected for one or more databases in the Data Guard broker configuration. Action: Locate the database(s) with a warning status and correct it. |
| ORA-16609 ORA-16609, 00000, “database is being disabled” Cause: A command was attempted on a database that was being disabled. For example, attempting to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated. Action: Wait for the Data Guard broker to disable the database and then retry the command. |
| ORA-16610 ORA-16610, 00000, “command \”%s\” in progress” Cause: The specified broker command was already running and the command issued could not be completed. Action: Wait for the specified command to finish and then retry the command. |
| ORA-16611 ORA-16611, 00000, “command aborted at user request” Cause: The command was aborted at the user’s request. Action: No action required. |
| ORA-16612 ORA-16612, 00000, “string value too long for attribute \”%s\”" Cause: The string value for the named attribute was too long. Action: Specify a shorter string value. |
| ORA-16613 ORA-16613, 00000, “initialization in progress for database” Cause: A request was made to modify the Data Guard broker configuration before the Data Guard broker had completed initialization. Action: Wait until the Data Guard broker has completed initialization before attempting to modify the broker configuration. |
| ORA-16614 ORA-16614, 00000, “Data Guard broker configuration is disabled” Cause: An attempt to enable a database failed because the Data Guard broker configuration was disabled. Action: Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any databases that are still disabled. If the database you tried to enable is still disabled, issue the DGMGRL CLI SHOW DATABASE command to check the status of the database. If the database status indicates that the database needs to be reinstated then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the database does not require reinstatement then issue the DGMGRL CLI ENABLE DATABASE command to enable the database. |
| ORA-16615 ORA-16615, 0000, “event for Data Guard NetSlave testing” Document: NO Cause: This is an Oracle internal event code. This event is used for verifying NetSlave functionality in Data Guard. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16616 ORA-16616, 0000, “event for Data Guard monitor testing” Document: NO Cause: This is an Oracle internal event code. This event is used for verifying Monitor functionality in Data Guard. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16617 ORA-16617, 0000, “unknown object identifier specified in request” Cause: Object identifier specified in the request was invalid or unknown. Action: Verify that a valid object identifier is specified and reissue reissue the request. |
| ORA-16618 ORA-16618, 0000, “response document of size \”%s\” bytes is too large” Document: NO Cause: The document response could not be returned because the size of the document was too large. Action: View the broker log for the given database directly. |
| ORA-16619 ORA-16619, 0000, “health check timed out” Cause: The standby database could not be reached during a routine health check. Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame. Check the network connections between the primary and standby databases. |
| ORA-16620 ORA-16620, 0000, “one or more databases could not be reached for a delete operation” Cause: One or more standby databases could not be reached for either a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command. Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database Data Guard broker log to determine which standby databases could not be reached. For each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, DG_BROKER_START, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to true. |
| ORA-16621 ORA-16621, 0000, “database name for ADD DATABASE must be unique” Cause: An attempt was made to add a database to the broker configuration that already included a database with the specified name. The database names must be unique. Action: Verify that a unique name is specified for the new database to be added. Also, the database name must match the DB_UNIQUE_NAME initialization parameter of the database. |
| ORA-16622 ORA-16622, 0000, “two or more broker database objects resolve to the same database” Cause: Multiple database objects referred to the same database. Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases referring to the same database. If two or more database profiles in the broker configuration have the same value for the DGConnectIdentifier database property, either: – Remove and re-add the erroneously defined database(s) to resolve the ambiguity. – Ensure that the DGConnectIdentifier database property for each database allows the broker to properly connect to that database. |
| ORA-16623 ORA-16623, 0000, “database detected role change” Cause: A successful switchover or failover operation had been completed and was detected during database startup or broker health check. If this database was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Data Guard broker. Action: Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation. |
| ORA-16624 ORA-16624, 0000, “broker protocol version mismatch detected” Cause: A network protocol version number mismatch was detected. This could happen if the databases in the broker configuration were not running the same version of Oracle. The broker would disable standby databases that were not running the same version of Oracle as the primary database if this situation was detected. Action: Examine the version of Oracle installed on all databases in the broker configuration to ensure they are identical. Once all of the datbases in the broker configuration are running the same version of Oracle, reenable the standby databases that were disabled. |
| ORA-16625 ORA-16625, 0000, “cannot reach the database” Cause: The command could not be executed because the database required to complete the command was not reachable from the database where the command was issued. If the command modifies the configuration, the command must be processed by the copy of the broker running on an instance of the primary database. Action: Check the network connections between all of the databases in the configuration. Alternatively, connect to a different database in the Data Guard broker configuration and retry the command. If an attempt was made to determine the status of a particular database in the configuration, connect to that database and get the current value of the StatusReport property for that database. |
| ORA-16626 ORA-16626, 0000, “failed to enable specified database” Cause: This status was returned when attempting to enable a standby database that: – Could not locate itself in the broker configuration file. – Failed to distinguish itself from two or more databases in the configuration file. – Determined it missed a role change within the configuration. Action: To correct the problem, try one of these actions: – Confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE. – Confirm that there are not two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not reach the same database. – If a failover had been performed and the old primary database has been re-created (or a standby database has been re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database. |
| ORA-16627 ORA-16627, 0000, “operation disallowed since no standby databases would remain to support protection mode” Cause: This status was returned because of one of the following: – The broker rejected an attempt to change the overall configuration protection mode since it could not find any enabled standby databases that supported the proposed protection mode. – The broker rejected an attempt to enable the configuration if it determined that there were no enabled standby databases that supported the overall protection mode. – The broker rejected an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that could support the overall configuration protection mode. – The broker rejected an attempt to switchover if doing so would violate the overall configuration protection mode. – Performing automatic health check if the broker determined that no standby datbases supported the overall protection mode. Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode. – For enable failures, confirm that at least one standby database has a LogXptMode configurable property setting that supports the current overall protection mode. – For delete and disable failures, confirm that at least one other standby database has a LogXptMode configurable property setting that supports the overall protection mode. – For switchover failures that occur when the configuration is operating in maximum protection or maximum availability mode, confirm that at least one other standby database has its LogXptMode configurable property set to the value “SYNC”. If the configuration contains a primary database and a single standby database and is operating in either maximum protection or maximum availability mode, ensure that the LogXptMode configurable property of the primary database is set to the value “SYNC”. Since the old primary database will become the standby database after switchover completes, its LogXptMode configurable property setting must support the configuration protection mode. – For health check error, confirm that at least one standby database has a LogXptMode configurable property setting that supports the current overall protection mode. |
| ORA-16628 ORA-16628, 00000, “broker protection mode inconsistent with the database setting” Cause: The Data Guard broker protection mode saved in the broker configuration file was inconsistent with the actual database setting. Action: Reset the protection mode through the Data Guard broker. |
| ORA-16629 ORA-16629, 00000, “database reports a different protection level from the protection mode” Cause: The actual or current database protection level was different from the configured protection mode. This typically is caused by redo transport problems. Action: Check the database alert logs and Data Guard broker logs for more details. Also, check the redo transport status. Ensure that one standby database supports the configured protection mode and that the network to that standby database is working properly. |
| ORA-16630 ORA-16630, 00000, “database property has been deprecated” Cause: The property that was specified in the command was deprecated. Action: Check the broker documentation to identify a replacement property or SQL command for the deprecated property. |
| ORA-16631 ORA-16631, 00000, “operation requires shutdown of database or instance \”%s\”" Cause: The Data Guard broker operation required a shutdown of the database or instance. Action: If database or instance has not been shutdown by the DGMGRL CLI or Enterprise Manager, shutdown the database or instance manually. |
| ORA-16632 ORA-16632, 00000, “instance being added to database profile” Cause: The Data Guard broker determined that an instance successfully found its database profile within the broker configuration file, but lacked an instance-specific profile. The broker automatically created an instance-specific profile and associated the instance with its database profile. Action: No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance into broker activity. |
| ORA-16633 ORA-16633, 00000, “the only instance of the database cannot be removed” Cause: The instance to be removed was the only instance of the corresponding database that was known to the broker. Action: Remove the corresponding database object from the broker configuration instead of the individual instance object of the database. |
| ORA-16634 ORA-16634, 0000, “Event for Data Guard NetSlave tracing” Document: NO Cause: This is an Oracle internal event code. This event is used to control trace output of the Data Guard NetSlave process. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16635 ORA-16635, 0000, “network connection failed during transmission” Cause: The Data Guard broker detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (for example, the broker configuration file) to the remote database. Action: In most cases, no user action is required. The Data Guard broker always tries to resend the data. This error will be reported if the problem persists. This error indicates there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and correct the actual problem. |
| ORA-16636 ORA-16636, 0000, “fast-start failover target standby in error state, cannot stop observer” Cause: A STOP OBSERVER operation could not be completed when fast-start failover was enabled because the target standby database could not participate in the STOP OBSERVER operation. Action: Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps to identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. If the problem can be corrected by the information in the broker log file, retry the operation. Alternatively, fast-start failover may be forcibly disabled by connecting to the primary database and issuing the DISABLE FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has been forcibly disabled, the observer can be stopped regardless of the current state of the target standby database. |
| ORA-16637 ORA-16637, 0000, “an instance failed to access the Data Guard broker configuration” Cause: The broker could not access the broker configuration files on one or more database instances. This can happen when the DG_BROKER_CONFIG_FILE[1|2] initialization parameter values are not to the same set of file locations for a RAC database. Action: Shut off the broker by setting the DG_BROKER_START initialization parameter to false. Then set the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters to file locations that are shared by all instances of a RAC database. Finally, restart the broker by setting the DG_BROKER_START initialization parameter to true. |
| ORA-16638 ORA-16638, 00000, “could not get the instance status” Cause: The broker could not determine whether the specified instance was running. Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services. |
| ORA-16639 ORA-16639, 0000, “specified instance inactive or currently unavailable” Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable. Action: Ensure that the instance specified in the operation is running and then retry the operation. |
| ORA-16640 ORA-16640, 00000, “CRS warns that multiple instances may still be running” Cause: The broker failed to have CRS stop instance monitoring and shut down all but one instance. CRS instance monitoring did stop, but CRS may not have been able to shut down all but one instance. The broker operation was canceled. Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D <NAME> -O NONE. Reissue the broker request. |
| ORA-16641 ORA-16641, 0000, “failure to acquire broker configuration metadata lock” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16642 ORA-16642, 0000, “DB_UNIQUE_NAME mismatch” Cause: The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the database that the broker contacted using the connect identifier that was associated with that database. Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that database. |
| ORA-16643 ORA-16643, 0000, “unable to determine location of broker configuration files” Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Action: Retry the operation and, if the error persists, contact Oracle Support Services. |
| ORA-16644 ORA-16644, 0000, “apply instance not available” Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available. Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command. |
| ORA-16645 ORA-16645, 0000, “unexpected new instance interrupted current operation” Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically. Action: Reissue the operation after the new instance has joined the Data Guard configuration. |
| ORA-16646 ORA-16646, 0000, “fast-start failover is disabled” Cause: The operation was not allowed because fast-start failover was disabled. Action: Enable fast-start failover and retry the operation. |
| ORA-16647 ORA-16647, 0000, “could not start more than one observer” Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which fast-start failover may have been enabled. Action: Stop the running observer. Retry the operation. |
| ORA-16648 ORA-16648, 0000, “a new observer registered with identifier %s” Cause: The observer was registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a fast-start failover. Action: None |
| ORA-16649 ORA-16649, 0000, “possible failover to another database prevents this database being opened” Cause: An attempt to open the database was made either when a failover occurred or while fast-start failover was enabled and the fast-start failover status could not be evaluated. Action: Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between this database and either the observer or the target standby database. Then, try opening the database again. |
| ORA-16650 ORA-16650, 0000, “command incompatible when fast-start failover is enabled” Cause: An attempt was made to issue a command that is not permitted when fast-start failover is enabled. The command was not issued using the Data Guard broker. Action: The command must be issued using the Data Guard broker. |
| ORA-16651 ORA-16651, 0000, “requirements not met for enabling fast-start failover” Cause: The attempt to enable fast-start failover could not be completed because one or more requirements were not met: – The Data Guard configuration must be in either MaxAvailability or MaxPerformance protection mode. – The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to SYNC if the configuration protection mode is set to MaxAvailability mode. – The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode is set to MaxPerformance mode. – The primary database and the fast-start failover target standby database must both have flashback enabled. – No valid target standby database was specified in the primary database FastStartFailoverTarget property prior to the attempt to enable fast-start failover, and more than one standby database exists in the Data Guard configuration. Action: Retry the command after correcting the issue: – Set the Data Guard configuration to either MaxAvailability or MaxPerformance protection mode. – Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to SYNC if the configuration protection mode is set to MaxAvailability. – Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to ASYNC if the configuration protection mode is set to MaxPerformance. – Ensure that both the primary database and the fast-start failover target standby database have flashback enabled. – Set the primary database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired target standby database and the desired target standby database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary database. |
| ORA-16652 ORA-16652, 0000, “fast-start failover target standby database is disabled” Cause: The command to enable or disable fast-start failover could not be completed because Data Guard broker management of the fast-start failover target standby database is currently disabled. Action: Enable broker management of the target standby database and reissue the command. If an attempt was made to disable fast-start failover when this error was reported, disable fast-start failover forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE command. Consult the documentation for more information. |
| ORA-16653 ORA-16653, 0000, “failed to reinstate database” Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled. Action: Additional information about this failure is recorded in the primary database or the specified database Data Guard broker log files. This information is helpful in determining how to proceed. |
| ORA-16654 ORA-16654, 0000, “fast-start failover is enabled” Cause: The attempted command was not allowed while fast-start failover was enabled: – The FastStartFailoverTarget property may not be modified. – The LogXptMode property for either the primary database or the fast-start failover target standby database may not be modified. – The configuration’s protection mode may not be modified. – Neither the broker configuration nor the fast-start failover target standby database may be disabled using the DGMGRL CLI DISABLE command. – Neither the broker configuration nor the fast-start failover target standby database may be removed using the DGMGRL CLI REMOVE command. – The FAILOVER IMMEDIATE command is not allowed. – The DG_BROKER_START initialization parameter may not be set to FALSE. Action: Disable fast-start failover, using the FORCE option if required. Then retry the attempted command. |
| ORA-16655 ORA-16655, 0000, “specified target standby database invalid” Cause: The attempted command was not allowed because fast-start failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database. Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, fast-start failover may be disabled. Then retry the command using the originally specified target standby database. |
| ORA-16656 ORA-16656, 0000, “Data Guard broker detected role change” Cause: The Data Guard broker detected a role during database startup or health check. Action: Additional information about this failure is recorded in the Data Guard broker log files, one for the primary database and one for each standby database in the Data Guard configuration. This information is helpful in determining how best to proceed from this failure. |
| ORA-16657 ORA-16657, 0000, “reinstatement of database in progress” Cause: Reinstatement of this database was in progress. Action: None |
| ORA-16658 ORA-16658, 0000, “unobserved fast-start failover configuration” Cause: The fast-start failover configuration was currently unobserved so failover was disallowed. Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable fast-start failover to perform a failover in the absence of the observer process. |
| ORA-16659 ORA-16659, 0000, “failover operation in progress” Cause: A primary database that restarted contacted a standby database that is being failed over to. Action: Shut down the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to fast-start failover, restarting the primary database after failover is complete allows it to be automatically reinstated as a standby database to the new primary database. |
| ORA-16660 ORA-16660, 0000, “fast-start failover operation attempted in absence of a broker configuration” Cause: An attempt was made to enable or disable fast-start failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands. Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database from the primary database. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) Use the FORCE option to override fast-start failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that fast-start failover is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other and if the state of fast-start failover has been altered at the primary database in the meantime. |
| ORA-16661 ORA-16661, 00000, “the standby database needs to be reinstated” Cause: A switchover or failover operation has caused this database to require reinstatement. Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database. |
| ORA-16662 ORA-16662, 0000, “network timeout when contacting a database” Cause: In response to the issued command, the Data Guard broker attempted to contact a database in the Data Guard configuration. That attempt failed because there was no response from that database after the period of time specified by the NetTimeout property for that database. Action: Check the Data Guard broker log for the details of the failure. Fix the problem and try the command again. |
| ORA-16663 ORA-16663, 0000, “event to control broker actions in the development environment” Document: NO Cause: This is an Oracle internal event code. This event is used to control the broker actions in the development environment. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16664 ORA-16664, 0000, “unable to receive the result from a database” Cause: During execution of a command, a database in the Data Guard broker configuration failed to return a result. Action: Check Data Guard broker logs for the details of the failure. Fix any possible network problems and try the command again. |
| ORA-16665 ORA-16665, 0000, “timeout waiting for the result from a database” Cause: The Data Guard broker was forced to time out a network connection |
| ORA-16666 ORA-16666, 00000, “unable to initiate fast-start failover on a standby database” Cause: The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made to a standby database. An application may only request that fast-start failover be initiated by calling DBMS_DG.INITIATE_FS_FAILOVER on a primary database. Action: Call DBMS_DG.INITIATE_FS_FAILOVER on the primary database. |
| ORA-16667 ORA-16667, 00000, “request Data Guard broker client to reissue command” Cause: The Data Guard broker operation required the same command be issued again from the client. Action: If DGMGRL or Enterprise Manager has not already done so, reissue the same command to the Data Guard broker manually. |
| ORA-16668 ORA-16668, 0000, “operation invalid on fast-start failover target database” Cause: The attempted command was not allowed on the fast-start failover target standby database when fast-start failover is currently enabled. Action: Retry the attempted command on a database other than the fast-start failover target standby database. Alternatively, disable fast-start failover and reissue the same command to the fast-start failover target standby database. |
| ORA-16700 ORA-16700, 00000, “the standby database has diverged from the primary database” Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option. Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to. |
| ORA-16701 ORA-16701, 00000, “Data Guard broker command failed” Cause: Command to modify or query the database failed. Action: Check the Data Guard broker log for the reason for the failure, and reissue the command. |
| ORA-16702 ORA-16702, 00000, “Data Guard broker command warning” Cause: A command to modify or query the database resulted in a warning. Action: Check the Data Guard broker log for the warning and, if necessary, reissue the command. |
| ORA-16703 ORA-16703, 00000, “cannot set property while the database is enabled” Cause: An attempt was made to change a database property while the database was enabled. Action: Disable the database first, update the property and then, reenable the database. |
| ORA-16704 ORA-16704, 00000, “cannot modify a read-only property” Cause: An attempt was made to change a read-only property. Action: The property is controlled internally by the Data Guard broker and cannot be modified. |
| ORA-16705 ORA-16705, 00000, “internal error in Data guard broker” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16706 ORA-16706, 00000, “no resource guard is available” Cause: Resource guard was not available to service the request. Action: Contact Oracle Support Services. |
| ORA-16707 ORA-16707, 00000, “the value of the property %s is invalid, valid values are %s” Cause: An invalid property value was entered while broker management of the database was disabled. Action: Reset the property to a valid value. |
| ORA-16708 ORA-16708, 00000, “the state supplied to broker is invalid” Cause: The state name specified was invalid for the database. Action: Check the state name and reissue the request. |
| ORA-16709 ORA-16709, 00000, “standby archived log location settings conflict with database recovery area” Cause: The StandbyArchiveLocation or AlternateLocation property was set to USE_DB_RECOVERY_FILE_DEST, but the initialization parameter DB_RECOVERY_FILE_DEST did not specify a valid destination. Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for StandbyArchiveLocation or AlternateLocation, or set up a valid database recovery area by setting DB_RECOVERY_FILE_DEST to a valid destination. |
| ORA-16711 ORA-16711, 00000, “the resource guard index is out of bounds” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16712 ORA-16712, 00000, “the resource handle is invalid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16713 ORA-16713, 00000, “the Data Guard broker command timed out” Cause: The Data Guard broker timed out the command. Action: Verify that the command is valid for the database and then retry the command. |
| ORA-16714 ORA-16714, 0000, “the value of property %s is inconsistent with the database setting” Cause: The value of the specified configuration property was inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property. Action: Query the InconsistentProperties property on the database to determine the which properties are set inconsistently. Reset the properties to make them with the database settings. |
| ORA-16715 ORA-16715, 0000, “redo transport-related property %s of standby database \”%s\” is inconsistent” Cause: The value of the specified redo transport-related configuration property of the given standby database was inconsistent with the primary database redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property. Action: Query the InconsistentLogXptProps property on the primary database to determine which redo transport properties are set inconsistently Reset the properties on the standby database to make them consistent with the primary database redo transport settings. |
| ORA-16716 ORA-16716, 00000, “clearing parameter LOG_ARCHIVE_DEST failed” Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed. Action: Contact Oracle Support Services. |
| ORA-16717 ORA-16717, 00000, “clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed” Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed. Action: Contact Oracle Support Services. |
| ORA-16718 ORA-16718, 00000, “failed to locate database” Cause: The Data Guard broker was unable to locate the database in the broker configuration. Action: Add the database to the broker configuration and then reissue the command. |
| ORA-16719 ORA-16719, 00000, “unable to query V$ARCHIVE_DEST fixed view” Cause: The broker failed to query the V$ARCHIVE_DEST fixed view.” Action: Test and clear the problem using SQL*Plus. |
| ORA-16720 ORA-16720, 00000, “no LOG_ARCHIVE_DEST_n initialization parameters available” Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use. Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database redo transport. |
| ORA-16721 ORA-16721, 00000, “unable to set LOG_ARCHIVE_DEST_n initialization parameters” Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters. Action: Check the Data Guard broker log and Oracle alert logs for more details. |
| ORA-16722 ORA-16722, 00000, “unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters” Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters. Action: Check the Data Guard broker log and Oracle alert logs for more details. |
| ORA-16723 ORA-16723, 00000, “setting AlternateLocation property conflicts with the redo transport setting” Cause: The standby database was not using standby redo logs, and the redo transport service to the standby database is set to a nonzero value for the ReopenSecs property and a value of zero for the MaxFailure property. In this case, the redo transport service will attempt to send redo data to the standby database indefinitely and never switch to the alternate destination. Action: Any one of the following actions will solve the problem: – add standby redo logs to the standby database. – set ReopenSecs property to zero. – set MaxFailure property to a nonzero value. After performing one of the above actions, reset the standby database AlternateLocation property. |
| ORA-16725 ORA-16725, 00000, “the phase supplied to resource guard is invalid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16726 ORA-16726, 00000, “the external condition supplied to resource guard is invalid” Document: NO Cause: This was an internal error. Action: Contact Oracle Support Services. |
| ORA-16727 ORA-16727, 00000, “cannot close database” Cause: The Data Guard broker could not close the database. Action: Terminate any active sessions connected to the database and then reissue the request. |
| ORA-16728 ORA-16728, 00000, “consistency check for property %s found %s error” Cause: The consistency check for the specified property failed due to the error shown. Action: Check the error message and clear the error. |
| ORA-16729 ORA-16729, 00000, “validation of value for property %s found %s error” Cause: The property value validation failed due to the error shown. Action: Check the error message and clear the error. |
| ORA-16730 ORA-16730, 00000, “error executing DBMS_LOGSTDBY.SKIP_TXN procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16731 ORA-16731, 00000, “error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16732 ORA-16732, 00000, “error executing DBMS_LOGSTDBY.SKIP procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16733 ORA-16733, 00000, “error executing DBMS_LOGSTDBY.UNSKIP procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16734 ORA-16734, 00000, “error executing DBMS_LOGSTDBY.SKIP_ERROR procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16735 ORA-16735, 00000, “error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure” Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. |
| ORA-16736 ORA-16736, 00000, “unable to find the destination entry of standby database \”%s\” in V$ARCHIVE_DEST” Cause: Either the standby destination was manually changed or deleted outside of Data Guard broker, or no entry was available for the Data Guard broker to use. Action: Clean up the destination setting, remove the unused settings, and reset the redo transport service. |
| ORA-16737 ORA-16737, 00000, “the redo transport service for standby database \”%s\” has an error” Cause: A communication problem with the standby database caused the redo transport to fail. Action: Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16738 ORA-16738, 00000, “redo transport service for database \”%s\” is not running” Cause: The redo transport service for the specified standby database was not running. Action: Check the Data Guard broker log and/or the alert log for more details. If necessary, start the redo transport service for the standby database. |
| ORA-16739 ORA-16739, 00000, “redo transport service for standby database \”%s\” is running” Cause: The redo transport service for the standby database was running. Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database. |
| ORA-16740 ORA-16740, 00000, “redo transport service for standby database \”%s\” incorrectly set to ALTERNATE” Cause: The redo transport service to the standby database was set to ALTERNATE when no other destination was set to alternate to this destination. Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters. |
| ORA-16741 ORA-16741, 00000, “the destination parameter of standby database \”%s\” has incorrect syntax” Cause: The destination defined in the server parameter file of the primary database had incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled. Action: Fix the syntax error in the primary database server parameter file or remove the entry from the server parameter file. Also, check the values of the redo transport-related properties for the specified standby database. |
| ORA-16742 ORA-16742, 00000, “the standby database \”%s\” has exhausted its quota” Cause: The standby database exhausted its quota for storing archived redo logs. Action: Remove some archived redo logs from the standby database or increase its quota. |
| ORA-16743 ORA-16743, 00000, “cannot determine status of redo transport service for standby database \”%s\”" Cause: The status of redo transport to the specified standby database could not be determined. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16744 ORA-16744, 00000, “the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full” Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list. Action: Remove some unused entries in the DG_CONFIG list, then reenable the database. |
| ORA-16745 ORA-16745, 00000, “unable to add DB_UNIQUE_NAME \”%s\” into the DG_CONFIG list because it is full” Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list. Action: Remove some unused entries in the DG_CONFIG list, then reenable the database. |
| ORA-16746 ORA-16746, 00000, “Data Guard broker cannot mount the database” Cause: The Data Guard broker failed to mount the database.” Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16747 ORA-16747, 00000, “logical standby database guard could not be turned on” Cause: The Data Guard broker could not turn on the logical standby database guard. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16748 ORA-16748, 00000, “Data Guard broker cannot open the primary database” Cause: The Data Guard broker failed to open the primary database” the database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16749 ORA-16749, 00000, “switchover to logical standby database failed” Cause: The Data Guard broker failed to switch a logical standby database over to a primary database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16750 ORA-16750, 00000, “failed to activate logical standby database” Cause: The Data Guard broker failed to activate a logical standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16751 ORA-16751, 00000, “failed to switchover to physical standby database” Cause: The Data Guard broker failed to switch a physical standby database over to a primary database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16752 ORA-16752, 00000, “Dump System State” Document: NO Cause: The Data Guard broker detected an internal problem and request a system state dump. Action: N/A, this is an Oracle internal event code. |
| ORA-16753 ORA-16753, 00000, “Data Guard broker cannot open standby database” Cause: The Data Guard broker failed to open the standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16754 ORA-16754, 00000, “failed to activate physical standby database” Cause: The Data Guard broker failed to activate the physical standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16755 ORA-16755, 00000, “failed to set initialization parameter” Cause: The Data Guard broker failed to set an initialization parameter using either the ALTER SYSTEM SET or ALTER SYSTEM RESET command. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16756 ORA-16756, 00000, “Dump Hang Analysis” Document: NO Cause: The Data Guard broker detected an internal problem and request a hang analysis dump. Action: N/A, this is an Oracle internal event code. |
| ORA-16757 ORA-16757, 00000, “unable to get this property’s value” Cause: The Data Guard broker failed to get the value for the specified property, possibly because the specified property’s value is not available for the current database role. Action: If the specified property’s value is not available for the database’s current role, please specify this property for a database for which it is available. Otherwise, check the Data Guard broker log for more details. |
| ORA-16758 ORA-16758, 00000, “the specified apply instance is not running” Cause: The Data Guard broker could not start apply services on the specified instance because that instance was not running. Action: Start the instance and then retry the command. |
| ORA-16759 ORA-16759, 00000, “cannot start SQL Apply with initial SCN” Cause: The Data Guard broker failed to start SQL Apply with an initial SCN. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16760 ORA-16760, 00000, “cannot start SQL Apply” Cause: The Data Guard broker failed to start SQL Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16761 ORA-16761, 00000, “cannot stop SQL Apply” Cause: The Data Guard broker failed to stop SQL Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16762 ORA-16762, 00000, “invalid database state” Cause: Database was not in the intended state. Action: Determine the reason why the database is not running in the intended state and reissue the command. |
| ORA-16763 ORA-16763, 00000, “redo transport service for a standby database is running” Cause: The redo transport service for a standby database was running. Action: Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database. |
| ORA-16764 ORA-16764, 00000, “redo transport service to a standby database is not running” Cause: The redo transport service to a standby database was not running. Action: Query the StatusReport property of the primary database for more details. If necessary, start the redo transport service. |
| ORA-16765 ORA-16765, 00000, “Redo Apply is running” Cause: Redo Apply was running when it should have been stopped. Action: If necessary, stop Redo Apply. |
| ORA-16766 ORA-16766, 00000, “Redo Apply is stopped” Cause: Redo Apply was stopped when it should have been running. Action: If necessary, start Redo Apply. |
| ORA-16767 ORA-16767, 00000, “SQL Apply is running” Cause: SQL Apply was running when it should have been stopped.” Action: If necessary, stop SQL Apply. |
| ORA-16768 ORA-16768, 00000, “SQL Apply is stopped” Cause: SQL Apply was stopped when it should have been running.” Action: If necessary, start SQL Apply. |
| ORA-16769 ORA-16769, 00000, “the physical standby database is open read-only” Cause: All instances in the physical standby database were put into a read-only state instead of APPLY-OFF. Action: Issue the EDIT DATABASE SET STATE command to set the database to the APPLY-OFF state. |
| ORA-16770 ORA-16770, 00000, “Redo Apply not started since physical standby database is opening” Cause: Redo Apply services could not be started on the physical standby database because it was being opened. The Data Guard broker will start Redo Apply services once the physical standby database has been opened. Action: No action required. |
| ORA-16771 ORA-16771, 00000, “failover to a physical standby database failed” Cause: The Data Guard broker encountered errors when converting a physical standby database to a primary database. Action: Check the Data Guard broker log and the Oracle alert log for more details about the error. |
| ORA-16772 ORA-16772, 00000, “switchover to a standby database failed” Cause: The Data Guard broker encountered errors when switching over to the specified standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16773 ORA-16773, 00000, “cannot start Redo Apply” Cause: The Data Guard broker failed to start Redo Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. If the database is already open, the broker will not be able to start Redo Apply if the COMPATIBLE initialization parameter is set to a value less than 11.0. |
| ORA-16774 ORA-16774, 00000, “cannot stop Redo Apply” Cause: The Data Guard broker failed to stop Redo Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16775 ORA-16775, 00000, “target standby database in broker operation has potential data loss” Cause: The target standby database specified for the broker operation did not have all the redo data from the primary database. Action: Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Reissue the broker command once all redo data is available on the target standby database. |
| ORA-16776 ORA-16776, 00000, “health check of the redo transport service failed” Cause: The Data Guard broker could not complete the health check for the redo transport service. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16777 ORA-16777, 00000, “unable to find the destination entry of a standby database in V$ARCHIVE_DEST” Cause: Either a destination was manually deleted or no entry was available for Data Guard. Action: Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset. |
| ORA-16778 ORA-16778, 00000, “redo transport error for one or more databases” Cause: The redo transport service was unable to send redo data to one or more standby databases. Action: Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors. |
| ORA-16779 ORA-16779, 00000, “the destination parameter of a database is set incorrectly” Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on. Action: Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct. |
| ORA-16780 ORA-16780, 00000, “a database has exhausted its archived redo log storage quota” Cause: A database has exhausted its quota for storing archived redo logs. Action: Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota. |
| ORA-16781 ORA-16781, 00000, “cannot determine status of redo transport service for standby database” Cause: The status of redo transport to the specified standby database could not be determined. Action: Check the Data Guard broker log and Oracle alert log for more details. |
| ORA-16782 ORA-16782, 00000, “instance not open for read and write access” Cause: The database was mounted on an instance but not opened for read and write access. Action: Check the StatusReport property for more details and, if possible, open the instance manually. |
| ORA-16783 ORA-16783, 00000, “instance %s not open for read and write access” Cause: The database was mounted on an instance but not opened for read and write access. Action: Check the StatusReport property for more details and, if possible open the instance manually. |
| ORA-16784 ORA-16784, 00000, “database name specified by Dependency property is incorrect” Cause: The database name, that should be the value of the DB_UNIQUE_NAME initialization parameter, specified in the Dependency property was incorrect. Action: Reset the Dependency property to the correct name of the database. |
| ORA-16785 ORA-16785, 00000, “the database is in NOARCHIVELOG mode” Cause: The database was in NOARCHIVELOG mode when it was either a primary database or when it was a standby database that was being switched over to be a primary database. Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG command. |
| ORA-16786 ORA-16786, 00000, “unable to access Data Guard broker metadata” Cause: The Data Guard broker configuration files did not exist or for some other reason the Data Guard broker configuration metadata could not be accessed. Action: Check the Data Guard broker log for more details. |
| ORA-16787 ORA-16787, 0000, “event for Data Guard resource guard process testing” Document: NO Cause: This is an Oracle internal event code. This event is used for verifying resource guard process functionality. DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-16788 ORA-16788, 0000, “unable to set one or more database configuration property values” Cause: This situation occurred when the broker attempted to set database configurable property values into the database by issuing ALTER SYSTEM or ALTER DATABASE commands. Typical causes of this error are: – The values of redo transport-related properties contain syntax syntax errors. – The value of the LogArchiveTrace property was out of range. Action: Check the Data Guard broker log to see which property has the problem and set the property to the correct value. |
| ORA-16789 ORA-16789, 0000, “standby redo logs not configured” Cause: Standby redo logs were not configured for the database. Action: Standby redo logs are required when the redo transport mode is set to SYNC or ASYNC. Check the Data Guard documentation to see how to create standby redo logs. |
| ORA-16790 ORA-16790, 0000, “the value of the configurable property is invalid” Cause: An invalid property value was entered. Action: Reset the property to a correct value. |
| ORA-16791 ORA-16791, 0000, “unable to check the existence of the standby redo logs” Cause: The database may not be mounted, or the query of the V$STANDBY_LOG fixed view failed. Action: Ensure the database is mounted and query the V$STANDBY_LOG fixed view to see if the problem has been corrected, and retry the operation. |
| ORA-16792 ORA-16792, 0000, “configurable property value is inconsistent with database setting” Cause: The values of one or more configurable properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker. Action: Query the InconsistentProperties property on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters. |
| ORA-16793 ORA-16793, 0000, “logical standby database guard is off” Cause: The logical standby database guard was turned off. Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error or warning is cleared. |
| ORA-16794 ORA-16794, 0000, “database guard is on for primary database” Cause: The database guard was turned on for the primary database. Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard and verify that Data Guard health check error or warning is cleared. |
| ORA-16795 ORA-16795, 0000, “the standby database needs to be re-created” Cause: A switchover or failover operation caused this database to require re-creation. The database was marked for re-creation because it was not a viable standby database for the new primary database. Until this error status is resolved for this database, information Action: Re-create (or flash back) the standby database. Connect to the Alternatively, many client commands that cannot be completed at |
| ORA-16796 ORA-16796, 0000, “one or more properties could not be imported from the database” Cause: The broker was unable to import property values for the database being added to the broker configuration. This error indicates: – The Oracle Net service name specified in DGMGRL CREATE CONFIGURATION or ADD DATABASE command was not one that provides access to the database being added. – There were no instances running for the database being added. Action: Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the Oracle Net service name provides access to the running instance. Also check the broker log file for additional information. Then, reissue the CREATE CONFIGURATION or ADD DATABASE command. |
| ORA-16797 ORA-16797, 0000, “database is not using a server parameter file” Cause: The database was not using a server parameter file or the broker was unable to access the server parameter file. Action: Issue the CREATE SPFILE=’..’ FROM PFILE=’…’” command to create a server parameter file and then restart the database to use it. |
| ORA-16798 ORA-16798, 0000, “unable to complete terminal recovery on the standby database” Cause: Terminal recovery on the standby database failed during the failover operation. Action: Check the Data Guard broker log and the Oracle alert logs to see more details on the reason for the failure. |
| ORA-16799 ORA-16799, 0000, “Redo Apply is not running” Cause: Either the Data Guard broker metadata indicates that Redo Apply was turned off, or the recovery process, MRP0, was not running. As a result, Redo Apply-related properties could not be set. Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property. |
| ORA-16800 ORA-16800, 00000, “redo transport service for a standby database incorrectly set to ALTERNATE” Cause: The redo transport service for a standby database was set to ALTERNATE when no other destination is set to alternate to this destination. Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters. |
| ORA-16801 ORA-16801, 0000, “redo transport-related property is inconsistent with database setting” Cause: The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker. Action: Query the InconsistentLogXptProps property on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters. |
| ORA-16802 ORA-16802, 0000, “downgrading redo transport mode from SYNC disallowed” Cause: An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This was not disallowed even though there may have been other standby databases with redo transport modes set to SYNC to support the protection mode. Action: Do one of the following if the redo transport mode of the standby must be downgraded: – Shut down all instances of the primary database and restart one instance with the initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode of the standby database of interest. Then, shutdown the instance, set the the CLUSTER_DATABASE initialization parameter to TRUE, and restart all primary database instances. – Downgrade the protection mode to Maximum Performance mode and then, downgrade the redo transport mode of the standby database of interest. Finally, upgrade the protection mode. This will require a restart of all primary database instances if upgrading to Maximum Protection mode. Note that the above only works when there is at least one standby database in the configuration that has its redo transport mode set to SYNC. |
| ORA-16803 ORA-16803, 0000, “unable to query a database table or fixed view” Cause: Failed to query a database table or fixed view. The database may not be opened or mounted. Action: Check the Data Guard broker log for more details. |
| ORA-16804 ORA-16804, 0000, “one or more configuration properties in metadata have invalid values” Cause: Data Guard broker health check detected that one or more configuration properties in the broker configuration had invalid values. The property values were changed while broker management of the database was disabled. Action: Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker. |
| ORA-16805 ORA-16805, 0000, “change of LogXptMode property violates overall protection mode” Cause: The broker disallowed the attempt to change the LogXptMode configurable property for the standby database because, if allowed, the overall protection mode for the configuration would have been violated. Action: If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, the LogXptMode configuration property for the standby database can be changed. |
| ORA-16806 ORA-16806, 0000, “supplemental logging is not turned on” Cause: Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to be the primary database. Action: Check the Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging. |
| ORA-16807 ORA-16807, 0000, “unable to change database protection mode” Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed. Action: Check the Data Guard broker log and the Oracle log for more information. |
| ORA-16808 ORA-16808, 0000, “primary database is not open” Cause: A prior attempt to open the primary database was disallowed because the fast-start failover status could not be evaluated. The fast-start failover status has since been evaluated and the database can now be opened. Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN command. |
| ORA-16809 ORA-16809, 0000, “multiple warnings detected for the database” Cause: The broker detected multiple warnings for the database. Action: Check the StatusReport monitorable property of the specifed database to get a detailed status report. |
| ORA-16810 ORA-16810, 0000, “multiple errors or warnings detected for the database” Cause: The broker detected multiple errors or warnings for the database. Action: Check the StatusReport monitorable property of the specified database to get a detailed status report. |
| ORA-16811 ORA-16811, 0000, “apply instance not recorded by the Data Guard broker” Cause: The broker did not register an apply instance for a standby database. Action: Reenable the standby database to clear the error. |
| ORA-16812 ORA-16812, 0000, “log apply service not running on apply instance recorded by the broker” Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon. Action: Reenable the standby database to clear the error. |
| ORA-16813 ORA-16813, 0000, “log apply service not running on apply instance %s recorded by the broker” Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon. Action: Reenable the standby database to clear the error. |
| ORA-16814 ORA-16814, 0000, “incorrect redo transport setting for AlternateLocation for standby database” Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following: – The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting. – The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting. – The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute. – The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE. – The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error. Action: Reenable the primary database to clear the error. |
| ORA-16815 ORA-16815, 0000, “incorrect redo transport setting for AlternateLocation for standby database \”%s\”" Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following: – The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting. – The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting. – The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute. – The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE. – The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error. Action: Reenable the primary database to clear the error. |
| ORA-16816 ORA-16816, 0000, “incorrect database role” Cause: The Data Guard broker detected that the specified database had a database role that was different from the database role recorded in the Data Guard configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database. Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database. |
| ORA-16817 ORA-16817, 0000, “unsynchronized fast-start failover configuration” Cause: The fast-start failover target standby database was not synchronized with the primary database. As a result, a fast-start failover could not happen automatically in case of a primary database failure. Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then fail over automatically to the standby database in the event of loss of the primary database. |
| ORA-16818 ORA-16818, 0000, “fast-start failover suspended” Cause: The primary database was intentionally shutdown. As a result, a fast-start failover could not happen automatically. Action: Start the primary database. This effectively restores the ability to automatically perform a fast-start failover in the event of a failure of the primary database. |
| ORA-16819 ORA-16819, 0000, “fast-start failover observer not started” Cause: The observer for fast-start failover was not started. As a result, fast-start failover could not happen in the case of a primary database failure. Action: Start the fast-start failover observer by using, for example, the DGMGRL START OBSERVER command. |
| ORA-16820 ORA-16820, 0000, “fast-start failover observer is no longer observing this database” Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were: – The host where the observer was running was not available. – The network connection between the observer and this database was not available. – The observer process was terminated unexpectedly. Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL STOP OBSERVER command. Then, restart the observer on another host. Finally, use the DGMGRL START OBSERVER command to start the observer on the other host. |
| ORA-16821 ORA-16821, 0000, “logical standby database dictionary not yet loaded” Cause: The logical standby database had not loaded the dictionary. This status was detected by the broker health check mechanism. Alternatively, this status may be returned when attempting to switch or fail over to a logical standby database that had not yet loaded its dictionary. Action: Start SQL Apply on the logical standby database, if it is not already running, and wait for it to reach the APPLYING state. |
| ORA-16822 ORA-16822, 0000, “new primary database not yet ready for standby database reinstatement” Cause: The new primary database, as a result of a logical standby database failover operation, had not fully completed the failover operation. An attempt to reinstate a disabled standby database could not be completed until failover completed on the new primary database. Action: Wait until the failover operation has completed on the new primary database. Then retry the reinstate operation. |
| ORA-16823 ORA-16823, 0000, “redo transport mode is incompatible for current operation” Cause: The redo transport mode of this database was incompatible for this broker operation. Action: Reset the LogXptMode database property for this database and retry the broker operation. |
| ORA-16824 ORA-16824, 0000, “multiple warnings, including fast-start failover-related warnings, detected for the database” Cause: The broker detected multiple warnings for the database. At least one of these warnings may have prevented fast-start failover from occurring. Action: Check the StatusReport monitorable property of the database specified. |
| ORA-16825 ORA-16825, 0000, “multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database” Cause: The broker detected multiple errors or warnings for the database. At least one of these errors or warnings may have prevented a fast-start failover from occurring. Action: Check the StatusReport monitorable property of the database specified. |
| ORA-16826 ORA-16826, 0000, “apply service state is inconsistent with the DelayMins property” Cause: This warning was caused by one of the following reasons: – The apply service was started without specifying the real-time apply option or without the NODELAY option when the DelayMins property was set to zero. – The apply service was started with the real-time apply option or with the NODELAY option when the DelayMins property was set to a value greater than zero. Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property. |
| ORA-16827 ORA-16827, 0000, “Flashback Database is disabled” Cause: The broker detected that the Flashback Database feature was disabled. With Flashback Database disabled, the broker would not be able to: – reinstate a database that required reinstatement. – convert a physical standby database to a snapshot standby database. – convert a snapshot standby database to a physical standby database. Flashback Database may been disabled manually with the ALTER DATABASE FLASHBACK DATABASE OFF command or automatically by the database in the event of an error. Action: Check the database alert log to determine whether Flashback Database was disabled due to errors and then correct the problem. If Flashback Database had been manually disabled, reenable Flashback Database with the ALTER DATABASE FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the database still cannot be reinstated or converted, you must re-create the database from a copy of the primary database. |
| ORA-16828 ORA-16828, 00000, “invalid value specified for REDO_TRANSPORT_USER initialization parameter” Cause: An invalid value was specified for the REDO_TRANSPORT_USER initialization parameter. The length of the user name exceeded 30 characters. Action: Check the documentation and specify a new value for the REDO_TRANSPORT_USER initialization parameter. |
| ORA-16829 ORA-16829, 0000, “fast-start failover configuration is lagging” Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure. Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property. |
| ORA-16830 ORA-16830, 0000, “primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down” Cause: The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation. Action: Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database. |
| ORA-16831 ORA-16831, 00000, “operation disallowed on this standby database type” Cause: The Data Guard broker operation was disallowed on the standby database type. Action: Check the documentation for the correct standby database type and reissue the Data Guard broker command to another standby database that is of the correct standby database type. |
| ORA-16950 ORA-16950, 00000, “Remote mapped cursors are not supported by this feature.” Cause: This cursor is a remote mapped cursor which could not be processed locally. Action: Try to process this statement directly on the remote site. |
| ORA-16951 ORA-16951, 00000, “Too many bind variables supplied for this SQL statement.” Cause: Binding this SQL statement failed because too many bind variables were supplied. Action: Pass the correct number of bind variables. |
| ORA-16952 ORA-16952, 00000, “Failed to bind this SQL statement.” Cause: Binding this SQL statement failed. Action: Check if bind variables for that statement are properly specified. |
| ORA-16953 ORA-16953, 00000, “Type of SQL statement not supported.” Cause: This type of SQL statement could not be processed. Action: |
| ORA-16954 ORA-16954, 00000, “SQL parse error.” Cause: The specified SQL statement failed to be parsed. Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name. |
| ORA-16955 ORA-16955, 00000, “Unknown error during SQL analyze.” Cause: The specified SQL statement failed to be analyzed. Action: This is an internal error, please contact Oracle support. |
| ORA-16956 ORA-16956, 00000, “Only SELECT or DML statements are supported for test execute.” Cause: The specified SQL statement cannot be tested for execute. Action: |
| ORA-16957 ORA-16957, 00000, “SQL Analyze time limit interrupt” Cause: This is an internal error code used indicate that SQL analyze has reached its time limit. Action: |
| ORA-16958 ORA-16958, 00000, “DML statements running parallel are not supported for test execute.” Cause: The specified DML statement cannot be tested for execute because part of it is running parallel. Action: |
| ORA-16959 ORA-16959, 00000, “Statement type has been disabled for SQL Analyze” Cause: The system attempted to analyze a type of statement that was disabled by the current feature. Action: Try a different feature capable of analyzing this statement type. |
| ORA-16960 ORA-16960, 00000, “SQL Analyze could not reproduce the desired plan.” Cause: SQL Analyze failed to reproduce a particular plan using an outline. Action: Check the outline data. |
| ORA-16961 ORA-16961, 00000, “SQL statement with SQL patch is ignored” Cause: SQL statements with SQL patches are not supported by SQL tuning advisor. Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL statement for a potential better SQL patch. |
| ORA-17500 ORA-17500, 00000, “ODM err:%s” Cause: An error returned by ODM library Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance |
| ORA-17501 ORA-17501, 00000, “logical block size %s is invalid” Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum Action: check INIT.ORA file parameters |
| ORA-17502 ORA-17502, 00000, “ksfdcre:%s Failed to create file %s” Cause: file creation failed due to either insufficient OS permission or the file already exists Action: check additional error messages |
| ORA-17503 ORA-17503, 00000, “ksfdopn:%s Failed to open file %s” Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length. Action: check additional error messages |
| ORA-17504 ORA-17504, 00000, “ksfddel:Failed to delete file %s” Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file. Action: check additional error messages |
| ORA-17505 ORA-17505, 00000, “ksfdrsz:%s Failed to resize file to size %s blocks” Cause: There is insufficient space left on the device or the process has insufficient permission to resize file. Action: check additional error messages |
| ORA-17506 ORA-17506, 00000, “I/O Error Simulation” Cause: The i/o request is marked with error because the i/o error simulation event is turned on. Action: |
| ORA-17507 ORA-17507, 00000, “I/O request size %s is not a multiple of logical block size” Cause: i/o’s are done in multiple of logical block size Action: Check additional error messages |
| ORA-17508 ORA-17508, 00000, “I/O request buffer ptr is not alligned” Cause: i/o request buffer should be alligned, check additional information for buffer ptr value Action: Call Oracle Support Services |
| ORA-17509 ORA-17509, 00000, “Attempt to do i/o beyond block1 offset” Cause: When a file is identified with logical block size of 0, only i/o’s to block1 is allowed. Action: check additional error messages and call Oracle Support Services |
| ORA-17510 ORA-17510, 00000, “Attempt to do i/o beyond file size” Cause: The i/o request points to a block beyond End Of File Action: check additional error messages and call Oracle Support Services |
| ORA-17511 ORA-17511, 00000, “Event used internally for farm testing using RMAN seed database” Document: NO Cause: This event fixes db_name and file names in control file so that files restored from RMAN seed database works in another view. Action: |
| ORA-17512 ORA-17512, 00000, “Block Verification Failed” Cause: Block Verification after a read operation on a database file failed since the block is media corrupt. Action: check additional error messages in the trace file and call Oracle Support Services |
| ORA-17610 ORA-17610, 00000, “file ‘%s’ does not exist and no size specified” Cause: An attempt to create a file found neither an existing file nor a size for creating the file. Action: Specify a size for the file. |
| ORA-17611 ORA-17611, 00000, “ksfd: file ‘%s’ cannot be accessed, global open closed” Cause: An attempt to write to a file which has gone offline/unidentified Action: Check for other errno in the stack |
| ORA-17612 ORA-17612, 00000, “Failed to discover Oracle Disk Manager library, return value %s” Cause: Discovery of the odm library by calling odm_discover() failed Action: Contact your storage vendor who has provided the ODM library or call Oracle Support |
| ORA-17613 ORA-17613, 00000, “Failed to initialize Oracle Disk Manager library: %s” Cause: ODM initialization for the thread failed due to insufficient previlige or memory. Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library |
| ORA-17614 ORA-17614, 00000, “Event to cause disk subsystem to require pre-allocation” Document: NO Cause: Action: |
| ORA-17615 ORA-17615, 00000, “Event to disable pre-allocation algorithm during backup” Document: NO Cause: Action: |
| ORA-17616 ORA-17616, 00000, “Event to disable pupulating V$RMAN_STATUS” Document: NO Cause: This event disables the dbsm_backup_restore functions createRmanStatusRow, updateRmanStatusRow, and commitRmanStatusRow (the functions will be no op). In order to limit size of rows in V$RMAN_STATUS and to delete the entire V$RMAN_STATUS use the named event KRBMRSR_LIMIT. If the level of that event is 1, then size of the V$RMAN_STATUS view will be zero so the above functions will signal ORA-19901. If the level is bigger than 1, then it sets the maximum number of rows in the V$RMAN_STATUS fixed view. Action: |
| ORA-17617 ORA-17617, 00000, “Event to disable populating V$RMAN_OUTPUT” Document: NO Cause: This event disables the dbsm_backup_restore function createRmanOutputRow (the function will be no op). In order to limit size of rows in V$RMAN_OUTPUT and to delete the entire V$RMAN_OUTPUT, use the named event KRBMROR_LIMIT. If the level of that event is 1, then size of the V$RMAN_OUTPUT view will be zero, so the function createRmanOutputRow will signal ORA-19901. If the level is bigger than 1, then level*256 is maximum number of the rows in the V$RMAN_OUTPUT fixed view. Action: |
| ORA-17618 ORA-17618, 00000, “Unable to update block 0 to version 10 format” Cause: An attempt was made to update block 0 to version 10 format. Action: Check additional error messages and call Oracle Support Services |
| ORA-17619 ORA-17619, 00000, “max number of processes using I/O slaves in a instance reached” Cause: An attempt was made to start large number of processes requiring I/O slaves. Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance. |
| ORA-17620 ORA-17620, 00000, “failed to register the network adapter with Oracle Disk Manager library: %s” Cause: The ODM library returned an error while trying to register the network adapter. Action: Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges. |
| ORA-17621 ORA-17621, 00000, “failed to register the memory with Oracle Disk Manager library” Cause: The ODM library returned an error while trying to register the memory. Action: Contact the Oracle Disk Manager Library provider. |
| ORA-17622 ORA-17622, 00000, “failed to deregister the memory with Oracle Disk Manager library” Cause: The ODM library returned an error while trying to deregister the memory. Action: Contact the Oracle Disk Manager Library provider |
| ORA-17623 ORA-17623, 00000, “Event to enable compression debugs in backup and restore” Document: NO Cause: Action: |
| ORA-17624 ORA-17624, 00000, “Failed to delete directory %s” Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory. Action: check additional error messages. |
| ORA-17625 ORA-17625, 00000, “Event to test delete directory” Document: NO Cause: For internal use only. Action: |
| ORA-17626 ORA-17626, 00000, “ksfdcre: %s file exists” Cause: trying to create a database file, but file by that name already exists Action: verify that name is correct, specify REUSE if necessary |
| ORA-17627 ORA-17627, 00000, “%s” Cause: An error returned by OCI while sending/receiving message from remote instance Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance |
| ORA-17628 ORA-17628, 00000, “Oracle error %s returned by remote Oracle server” Cause: Oracle server on the remote instance has returned an error. Action: Look at remote instance alert log/trace file for more information and take appropriate action or contact Oracle Support Services for further assistance |
| ORA-17629 ORA-17629, 00000, “Cannot connect to the remote database server” Cause: Connecting to the remote server specified by database connect string for netowrk file transfer failed. Action: Check additional error messages |
| ORA-17630 ORA-17630, 00000, “Mismatch in the remote file protocol version client %s server %s” Cause: Cannot communicate with the remote database server as there is a mismatch in the Oracle file protocol version. Action: Check additional error messages |
| ORA-17631 ORA-17631, 00000, “dbname ‘%s’ specified by remote server does not match the instance name ‘%s’” Cause: The dbname specified by the remote server is not intended for this instance. Action: Check the dbname specified in the command of the remote instance and look for further error messages. |
| ORA-17632 ORA-17632, 0000, “file ‘%s’ is a formatted ASM disk” Cause: An attempt to create a datafile on a device that was formatted for ASM disk failed. Action: Check that the device specified is not an ASM disk. If you would like to use the disk for datafiles, please clear the disk before you retry the operation. |
| ORA-18000 ORA-18000, 00000, “invalid outline name” Cause: The parser detected a missing or invalid outline name Action: |
| ORA-18001 ORA-18001, 00000, “no options specified for ALTER OUTLINE” Cause: The parser detected that no clause was specified on the command // Our performance tests, which are not typical as they exercise all // branches of the code, have shown approximately a 30% performance // increase line for ALTER OUTLINE. Action: Re-issue the command, specifying a valid ALTER OUTLINE clause. |
| ORA-18002 ORA-18002, 00000, “the specified outline does not exist” Cause: Either the outline did not exist to begin with, or a timing window // allowed for another thread to drop or alter the outline midstream. Action: |
| ORA-18003 ORA-18003, 00000, “an outline already exists with this signature” Cause: The signature generation algorithm generates signatures that are // are 16 bytes in length so it is highly unlikely that any 2 // signatures will be identical. This message is raised in such a // rare case. Action: Either re-issue the statement that led to the outline being created // with some whitespace added or force the outline to be created in a // different category. |
| ORA-18004 ORA-18004, 00000, “outline already exists” Cause: An outline already exists, either with the specified name, or for // the specified SQL text. Action: |
| ORA-18005 ORA-18005, 00000, “CREATE ANY OUTLINE privilege is required for this operation” Cause: Action: |
| ORA-18006 ORA-18006, 00000, “DROP ANY OUTLINE privilege is required for this operation” Cause: Action: |
| ORA-18007 ORA-18007, 00000, “ALTER ANY OUTLINE privilege is required for this operation” Cause: Action: |
| ORA-18008 ORA-18008, 00000, “cannot find OUTLN schema” Cause: The database creation script that creates this schema must not // have been executed. Action: Review the log files to see what happened when the database // was created. |
| ORA-18009 ORA-18009, 00000, “one or more outline system tables do not exist” Cause: Either the database creation script that creates these tables // was not executed or a user accidently deleted the table Action: Review the log files to see what happened when the database // was created. |
| ORA-18010 ORA-18010, 00000, “command missing mandatory CATEGORY keyword” Cause: User failed to specify the CATEGORY keyword Action: Re-issue the command with the CATEGORY keyword included |
| ORA-18011 ORA-18011, 00000, “the outline specified in the FROM clause does not exist” Cause: Action: |
| ORA-18012 ORA-18012, 00000, “select_catalog_role role is required for this operation” Cause: Action: |
| ORA-18013 ORA-18013, 00000, “timed out while waiting for resource %s” Cause: Action: |
| ORA-18014 ORA-18014, 00000, “deadlock detected while waiting for resource %s” Cause: Action: |
| ORA-18015 ORA-18015, 00000, “invalid source outline signature” Cause: User imported an 8i outline into a 9i database without updating signatures Action: execute dbms_outln.update_signatures |
| ORA-19000 ORA-19000, 00000, “missing RELATIONAL keyword” Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification. Action: Supply the RELATIONAL keyword in the storage clause |
| ORA-19001 ORA-19001, 00000, “Invalid storage option specified” Cause: An invalid storage option was specified for the XMLType. Action: Supply a valid storage option. |
| ORA-19002 ORA-19002, 00000, “Missing XMLSchema URL” Cause: A XML schema URL must be specified in the storage option. Action: Specify a URL for the XMLSchema. |
| ORA-19003 ORA-19003, 00000, “Missing XML root element name” Cause: A root element in the XMLSchema must be specified if the XML schema is given. Action: Specify a root element in the XML schema. |
| ORA-19004 ORA-19004, 00000, “Duplicate XMLType OBJECT RELATIONAL storage option” Cause: A duplicate storage option for the XMLType column was specified Action: Specify a single storage option for an XMLType column |
| ORA-19005 ORA-19005, 00000, “Duplicate XMLType LOB storage option” Cause: A duplicate storage option for the XMLType column was specified Action: Specify a single storage option for an XMLType column |
| ORA-19006 ORA-19006, 00000, “XMLType TYPE storage option not appropriate for storage type” Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column |
| ORA-19007 ORA-19007, 00000, “Schema %s does not match expected %s.” Cause: The given XML document conformed to a different schema than expected. Action: Insert/Update only the XML documents that conform to that particular schema. |
| ORA-19008 ORA-19008, 00000, “Invalid version of the XMLType ” Cause: An invalid version of the XMLType was found. Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database. |
| ORA-19009 ORA-19009, 00000, “Missing XMLSchema keyword” Cause: The XMLSchema keyword is missing Action: Specify the XMLSchema URL and element name. |
| ORA-19010 ORA-19010, 00000, “Cannot insert XML fragments” Cause: XML fragments got from extractNode cannot be inserted into the database. Action: Convert the fragment into a proper XML document before insertion. |
| ORA-19011 ORA-19011, 00000, “Character string buffer too small” Cause: The string result asked for is too big to return back Action: Get the result as a lob instead |
| ORA-19012 ORA-19012, 00000, “Cannot convert XML fragment to the required datatype” Cause: A conversion to a datatype was requested which cannot be performed Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype. |
| ORA-19013 ORA-19013, 00000, “Cannot create VARRAY columns containing XMLType” Cause: An attempt was made to create a VARRAY column which contains a XMLType Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead |
| ORA-19015 ORA-19015, 00000, “Invalid XML tag identifier (%s)” Cause: An invalid XML identifer was detected during XML generation Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification |
| ORA-19016 ORA-19016, 00000, “attributes cannot occur after element specifications” Cause: Attributes specified using the “@” identifier can only occur before any other element definition when creating XML Action: Change the order of the types so that the attributes occur in the begining |
| ORA-19017 ORA-19017, 00000, “Attributes can only be simple scalars” Cause: Attribute values can only be simple scalar values Action: Use only simple datatypes for attribute values |
| ORA-19018 ORA-19018, 00000, “Invalid character in XML tag ‘%s’” Cause: A tag name was found to have an invalid XML character during XML generation. Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters. |
| ORA-19019 ORA-19019, 00000, “Invalid context passed to DBMS_XMLGEN.GETXML” Cause: The value of context passed to GETXML was invalid. Action: Rewrite the query so that the value of context passed to GETXML is valid. |
| ORA-19020 ORA-19020, 00000, “invalid dereference of XMLType columns ” Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table Action: You can only dereference the attributes of a base table XMLType column |
| ORA-19021 ORA-19021, 00000, “General event for XML operations” Document: NO Cause: Disables functional evaluation of XML XPath operators on level 1 Action: N/A, this is a Oracle internal event code |
| ORA-19022 ORA-19022, 00000, “XML XPath functions are disabled” Document: NO Cause: Event 19021 is enabled, which prevents functional evaluation of Xpath operations Action: If the XML functional evaluation is disabled. Disable event 19021 to not see this error message |
| ORA-19023 ORA-19023, 00000, “The first argument to UPDATEXML operator has to be an XMLTYPE” Cause: The first argument passed to the update value operator was not an XMLTYPE. Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE. |
| ORA-19024 ORA-19024, 00000, “Cursor expression must be named” Cause: The value of context passed to GETXML was invalid. Action: Rewrite the query so that the value of context passed to GETXML is valid. |
| ORA-19025 ORA-19025, 00000, “EXTRACTVALUE returns value of only one node” Cause: Given XPath points to more than one node. Action: Rewrite the query so that exactly one node is returned. |
| ORA-19026 ORA-19026, 00000, “EXTRACTVALUE can only retrieve value of leaf node” Cause: Given XPath does not point to a leaf node. Action: Rewrite the query so that a leaf node is returned. |
| ORA-19027 ORA-19027, 00000, “Event for supressing query rewrite with XML operators” Document: NO Cause: This event turns off query rewrite for XML operators Action: N/A, this is a Oracle internal event code |
| ORA-19028 ORA-19028, 00000, “Invalid ADT parameter passed to toObject() function” Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type. Action: Pass an object of the correct type to toObject(). |
| ORA-19029 ORA-19029, 00000, “Cannot convert the given XMLType to the required type ” Cause: The passed in XMLType could not be convert to the required type Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types. |
| ORA-19030 ORA-19030, 00000, “Method invalid for non-schema based XML Documents.” Cause: The method can be invoked on only schema based xmltype objects. Action: Don’t invoke the method for non schema based xmltype objects. |
| ORA-19031 ORA-19031, 00000, “XML element or attribute %s does not match any in type %s.%s” Cause: The passed in XML tag does not match any in the object type Action: Pass a valid canonical XML that can map to the given object type |
| ORA-19032 ORA-19032, 00000, “Expected XML tag %s got %s” Cause: When converting XML to object, a wrong tag name was present Action: Pass a valid canonical XML that can map to the given object type |
| ORA-19033 ORA-19033, 00000, “schema specified in the XML document does not match the schema parameter” Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the ‘schema’ parameter. Action: Change the schema parameter to match the schema specified in the XML document. |
| ORA-19034 ORA-19034, 00000, “Type not supported during schema generation” Cause: The object type contained a type that is not supported for schema generation. Action: Use a different type or do not generate a schema. |
| ORA-19035 ORA-19035, 00000, “Invalid select item of the query in newContextFromHierarchy()” Cause: The query does not have a number select item followed by an XMLType select item only. Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType. |
| ORA-19036 ORA-19036, 00000, “Invalid query result set in newContextFromHierarchy()” Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query. Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query. |
| ORA-19037 ORA-19037, 00000, “XMLType result can not be a fragment” Cause: The select item of the query in newContextFromHierarchy() is an XML fragment. Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment |
| ORA-19038 ORA-19038, 00000, “Invalid opertions on query context” Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy(). Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy(). |
| ORA-19039 ORA-19039, 00000, “Keyword %s reserved for future use” Cause: The keyword is reserved for future use as a builtin function. Action: Change the name mentioned above to a different one. |
| ORA-19040 ORA-19040, 00000, “Element %s does not match expected %s.” Cause: The given XML document had a different root element than expected. Action: Insert/Update only the XML documents that conform to that particular schema and element. |
| ORA-19041 ORA-19041, 00000, “Comment data cannot contain two consecutive ‘-’s” Cause: The given comment string expression has two consecutive ‘-’s. Action: Modify comment string to eliminate one or both of the consevutive ‘-’s. |
| ORA-19042 ORA-19042, 00000, “Enclosing tag %s cannot be xml in any case combination” Cause: The given enclosing tag matched ‘xml’ in some case combination Action: Modify the enclosing tag so that it is not xml in any case combination. |
| ORA-19043 ORA-19043, 00000, “Multiply nested XMLROOT function disallowed” Cause: An XMLROOT function has an operand that is also an XMLROOT function. Action: Modify the query so that there are no multiply nested XMLROOT functions. |
| ORA-19044 ORA-19044, 00000, “character length specified for XMLSerialize is too small.” *Cause : An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small. *Action : Modify the query so that the character length specified is larger. |
| ORA-19045 ORA-19045, 00000, “character set id specified for XMLSerialize not valid ” *Cause : An XMLSerialize function was called with an invalid value for the caracter set id. *Action : Modify the query so that the character set id is valid. |
| ORA-19100 ORA-19100, 00000, “PASSING or RETURNING keyword expected” Cause: The keyword PASSING or RETURNING was missing. Action: Specify the PASSING or RETURNING keyword. |
| ORA-19101 ORA-19101, 00000, “CONTENT keyword expected” Cause: The keyword CONTENT was missing. Action: Specify the CONTENT keyword. |
| ORA-19102 ORA-19102, 00000, “XQuery string literal expected” Cause: The string literal containing the XQuery expression was missing. Action: Specify the XQuery expression as a string literal. |
| ORA-19103 ORA-19103, 00000, “VALUE keyword keyword” Cause: The keyword VALUE was missing. Action: Specify the VALUE keyword. |
| ORA-19104 ORA-19104, 00000, “invalid XQueryX: missing attribute %s ” Cause: The XQueryX expression was not assigned the expected attribute. Action: Specify a valid XQueryX. |
| ORA-19105 ORA-19105, 00000, “invalid XQueryX: expected text node – got %s ” Cause: The XQueryX expression did not contain a text node as expected. Action: Specify a valid XQueryX. |
| ORA-19106 ORA-19106, 00000, “invalid XQueryX: expected %s – got %s ” Cause: The XQueryX expression did not contain the node as expected. Action: Specify a valid XQueryX. |
| ORA-19107 ORA-19107, 00000, “invalid XQueryX – unsupported construct – %s” Cause: The given XQuery expression contains an unsupported construct. Action: Specify a valid XQueryX. |
| ORA-19108 ORA-19108, 00000, “WHITESPACE keyword expected” Cause: The keyword WHITESPACE was missing. Action: Specify the WHITESPACE keyword. |
| ORA-19109 ORA-19109, 00000, “RETURNING keyword expected” Cause: The keyword RETURNING was missing. Action: Specify the RETURNING keyword. |
| ORA-19110 ORA-19110, 00000, “unsupported XQuery expression” Cause: The program specified an XQuery expression that is not supported. Action: Rewrite the XQuery with a expression that is supported. |
| ORA-19111 ORA-19111, 00000, “error during evaluation of the XQuery expression” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19112 ORA-19112, 00000, “error raised during evaluation: %s” Cause: The error function was called during evaluation of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19113 ORA-19113, 00000, “trace function called during evaluation: %s” Cause: The trace function was called during evaluation of the XQuery expression. Action: Check the log file for the trace message. |
| ORA-19114 ORA-19114, 00000, “XPST0003 – error during parsing the XQuery expression: %s” Cause: An error occurred during the parsing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19115 ORA-19115, 00000, “too many context items specified” Cause: More than one context item was specified as input to the XMLQuery function. Action: Specify a single context item for the XMLQuery function. |
| ORA-19116 ORA-19116, 00000, “too many xmlspace declarations” Cause: The query prolog contained multiple xmlspace declarations. Action: Remove the duplicate xmlspace declarations. |
| ORA-19117 ORA-19117, 00000, “XQST0070 – invalid redefinition of predefined namespace prefix ‘%s’” Cause: The given predefined namespace was being redefined in a namespace declaration. Action: Remove the namespace declaration that redefines the predefined namespace prefix. |
| ORA-19118 ORA-19118, 00000, “XQST0066 – duplicate default namespace definition – %s” Cause: More than one default namespace declaration used the given namespace URI. Action: Remove the duplicate default namespace definition. |
| ORA-19119 ORA-19119, 00000, “Event for turning on XMLQuery and XMLTable function” Document: NO Cause: This event turns on the XMLQuery and XMLTable functions Action: N/A, this is a Oracle internal event code |
| ORA-19120 ORA-19120, 00000, “Event for changing behavior of XMLQuery and XMLTable functions” Document: NO Cause: This event changes the behavior of the XMLQuery and XMLTable functions Action: N/A, this is a Oracle internal event code |
| ORA-19121 ORA-19121, 00000, “duplicate attribute definition – %s” Cause: More than one attribute with the same name. Action: Remove the duplicate attribute definition. |
| ORA-19122 ORA-19122, 00000, “unsupported XQuery declaration” Cause: The program specified an XQuery declaration that is not supported. Action: Rewrite the XQuery with a declaration that is supported. |
| ORA-19123 ORA-19123, 00000, “FORG0003: fn:zero-or-one() called with a sequence containing more than one item” Cause: sequence with more than one item was passed into fn:zero-or-one() function Action: correct input argument to fn:zero-or-one() function |
| ORA-19124 ORA-19124, 00000, “FORG0004: fn:one-or-more() called with a sequence containing no items” Cause: sequence containing no items was passed into fn:one-or-more() function Action: correct input argument to fn:one-or-more() function |
| ORA-19125 ORA-19125, 00000, “FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item” Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function Action: correct input argument to fn:exactly-one() function |
| ORA-19126 ORA-19126, 00000, “XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces” Cause: No expression was enclosed in curly braces for the extension expression or the pragma content was not recognized. Action: Correct inputs to extension expression. |
| ORA-19127 ORA-19127, 00000, “XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19128 ORA-19128, 00000, “XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19129 ORA-19129, 00000, “XQST0069: A static error is raised if a Prolog contains more than one empty order declaration” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19130 ORA-19130, 00000, “XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19131 ORA-19131, 00000, “XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19132 ORA-19132, 00000, “XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19133 ORA-19133, 00000, “XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 … Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19134 ORA-19134, 00000, “XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19135 ORA-19135, 00000, “XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19136 ORA-19136, 00000, “XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19137 ORA-19137, 00000, “XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19138 ORA-19138, 00000, “The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator \”?\”; otherwise a static error is raised” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19139 ORA-19139, 00000, “XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19140 ORA-19140, 00000, “XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19141 ORA-19141, 00000, “XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19142 ORA-19142, 00000, “FONC0001 = FONC0001: undefined context item” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19143 ORA-19143, 00000, “XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19145 ORA-19145, 00000, “XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19146 ORA-19146, 00000, “XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19147 ORA-19147, 00000, “XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19148 ORA-19148, 00000, “XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19149 ORA-19149, 00000, “XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19150 ORA-19150, 00000, “XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19151 ORA-19151, 00000, “XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 … Mi … M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19152 ORA-19152, 00000, “FOCH0001 = FOCH0001: codepoint not valid” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19153 ORA-19153, 00000, “FOCH0002: unsupported collation” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19154 ORA-19154, 00000, “FOCH0003: unsupported normalization form” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19155 ORA-19155, 00000, “FOCH0004: collation does not support collation units” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19156 ORA-19156, 00000, “FODC0001: no context document” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19157 ORA-19157, 00000, “FODC0002: error retrieving resource” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19158 ORA-19158, 00000, “FODC0004: invalid argument to fn:collection()” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19159 ORA-19159, 00000, “FODC0005: invalid argument to fn:doc” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19160 ORA-19160, 00000, “XPST0003 – syntax error: invalid variable name %s” Cause: The given XQuery variable does not begin with the ‘$’ sign Action: Fix the variable name to start with the “$” sign. |
| ORA-19161 ORA-19161, 00000, “XPTY0004 – XQuery type mismatch: invalid argument type ‘%s’ for function ‘%s’” Cause: The type of the argument that was passed to the given function was not valid. Action: Fix the argument to be of a type supported by the given function. |
| ORA-19162 ORA-19162, 00000, “XPTY0004 – XQuery type mismatch: invalid argument types ‘%s’, ‘%s’ for function ‘%s’” Cause: The type of the arguments that were passed to the given function was not valid. Action: Fix the arguments to be of a type appropriate for the given function. |
| ORA-19163 ORA-19163, 00000, “XPTY0004 – XQuery type mismatch: argument type mismatch: expected – ‘%s’ got – ‘%s’ for function ‘%s’” Cause: The type of the arguments that were passed to the given function was not valid. Action: Fix the arguments to be of a type appropriate for the given function. |
| ORA-19164 ORA-19164, 00000, “XQST0085 – It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1].” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19165 ORA-19165, 00000, “FONS0003: no prefix defined for namespace” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19166 ORA-19166, 00000, “FONS0003: FONS0004: no namespace found for prefix” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19167 ORA-19167, 00000, “FONS0005: base uri not defined in the static context” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19168 ORA-19168, 00000, “FORG0002: invalid argument to fn:resolve-uri()” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19169 ORA-19169, 00000, “FORG0006: invalid argument type in ‘%s’” Cause: There was a zero-length URI in namespace declaration. Action: Fix the namespace declaration. |
| ORA-19170 ORA-19170, 00000, “Event for turning on XML Query Cost-based Rewrite” Document: NO Cause: This event turns on the XML Query Cost-based Rewrite. Action: This is an Oracle internal event code. No action is required. |
| ORA-19171 ORA-19171, 00000, “FORG0007: invalid argument to aggregate function” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19172 ORA-19172, 00000, “FORG0008: both arguments to fn:dateTime have a specified timezone” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19173 ORA-19173, 00000, “FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19174 ORA-19174, 00000, “FORX0001: invalid regular expression flags” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19175 ORA-19175, 00000, “FORX0002: invalid regular expression” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19176 ORA-19176, 00000, “FORX0003: regular expression matches zero-length string” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19177 ORA-19177, 00000, “FORX0004: invalid replacement string” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19178 ORA-19178, 00000, “FOTY0001: type error” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19179 ORA-19179, 00000, “FOTY0011: Type error. Context item is not a node” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19180 ORA-19180, 00000, “FOTY0012: argument node does not have a typed value” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19181 ORA-19181, 00000, “FOTY0014: type exception” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19182 ORA-19182, 00000, “FORT0001: invalid number of parameters” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19183 ORA-19183, 00000, “FOTY0002: type definition not found” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19184 ORA-19184, 00000, “FOTY0021: invalid node type” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19185 ORA-19185, 00000, “FOAR0002: numeric operation overflow/unflow” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19186 ORA-19186, 00000, “FOCA0001: input value too large for decimal” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19187 ORA-19187, 00000, “FOCA0002: invalid lexical value” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19188 ORA-19188, 00000, “FOCA0003: input value too large for integer” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19189 ORA-19189, 00000, “FOCA0005: NaN supplied as float/double value” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19190 ORA-19190, 00000, “FOER0000: Unidentified error” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19191 ORA-19191, 00000, “FOAR0001: division by zero” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19192 ORA-19192, 00000, “XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19193 ORA-19193, 00000, “XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19194 ORA-19194, 00000, “XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string \”?>\”" Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19200 ORA-19200, 00000, “Invalid column specification” Cause: All input arguments must be valid columns Action: Specify a valid list of columns |
| ORA-19201 ORA-19201, 00000, “Datatype not supported” Cause: The particular datatype is not supported in the XMLGEN operator Action: Specify only supported datatypes as arguments to the XMLGEN operator |
| ORA-19202 ORA-19202, 00000, “Error occurred in XML processing%s” Cause: An error occurred when processing the XML function Action: Check the given error message and fix the appropriate problem |
| ORA-19203 ORA-19203, 00000, “Error occurred in DBMS_XMLGEN processing%s” Cause: An error occurred when processing the DBMS_XMLGEN functions Action: Check the given error message and fix the appropriate problem |
| ORA-19204 ORA-19204, 00000, “Non-scalar value ‘%s’ is marked as XML attribute” Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by ‘@’. In this case, a non-scalar value was prefixed with ‘@’ Action: Remove the ‘@’ sign, or make the value a scalar. |
| ORA-19205 ORA-19205, 00000, “Attribute ‘%s’ qualifies a non-scalar value in the select list” Cause: The attribute immediately follows a value of object or collection type in the select list or type definition. Action: Remove the ‘@’ sign, or make the previous value a scalar. |
| ORA-19206 ORA-19206, 00000, “Invalid value for query or REF CURSOR parameter” Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR. Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR. |
| ORA-19207 ORA-19207, 00000, “scalar parameter %s of XMLELEMENT cannot have an alias.” Cause: The scalar parameter to XMLELEMENT has been qualified with an alias. Action: Remove the AS clause of the scalar element. |
| ORA-19208 ORA-19208, 00000, “parameter %s of function %s must be aliased” Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression. Action: Specify an alias for the expression using the AS clause. |
| ORA-19209 ORA-19209, 00000, “invalid or unsupported formatting argument” Cause: An invalid or unsupported formatting argument was supplied Action: Change the formatting argument to legal supported values |
| ORA-19210 ORA-19210, 00000, “column ‘%s’, specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table ‘%s’” Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table. Action: Change the column specified to be a column in the table |
| ORA-19211 ORA-19211, 00000, “column ‘%s’, specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type” Cause: The column specified using setKeyColumn() was a non-scalar type column. Action: Change the column specified to be a scalar column in the table |
| ORA-19212 ORA-19212, 00000, “no key columns specified before call to DBMS_XMLSTORE.updateXML()” Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML. Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns |
| ORA-19221 ORA-19221, 00000, “XPST0001 – XQuery static context component %s not initialized” Cause: An unitialized static context component was encountered during the static analysis of the expression. Action: initialize the given static context. |
| ORA-19222 ORA-19222, 00000, “XPDY0002 – XQuery dynamic context component %s not initialized” Cause: An unitialized dynamic context component was encountered during the evaluation of the expression. Action: Initialize the particular dynamic context component. |
| ORA-19223 ORA-19223, 00000, “XPST0003 – syntax error in XQuery expression” Cause: The given XQuery expression contains syntax errors. Action: Fix the syntax error in the XQuery expression. |
| ORA-19224 ORA-19224, 00000, “XPTY0004 – XQuery static type mismatch: expected – %s got – %s ” Cause: The expression could not be used because it’s static type is not appropriate for the context in which it was used. Action: Fix the expression to be of the required type or add appropriate cast functions around the expression. |
| ORA-19225 ORA-19225, 00000, “XPST0005 – XQuery static type error: expected non empty type got empty sequence” Cause: The static type assigned to an expression other than the () expression must not be the empty type. Action: Fix the expression so it does not return empty sequences. |
| ORA-19226 ORA-19226, 00000, “XPTY0006 – XQuery dynamic type mismatch: expected %s got %s” Cause: The expression could not be used because it’s dynamic type did not match the required type as specified by XQuery sequencetype matching rules. Action: Fix the expression to return the expected type or use appropriate cast functions. |
| ORA-19227 ORA-19227, 00000, “XPTY0007 – fn:data function is applied to a node (type (%s)) whose type annotation denotes a complex type with non-mixed complex content.” Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content. Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content. |
| ORA-19228 ORA-19228, 00000, “XPST0008 – undeclared identifier: prefix ‘%s’ local-name ‘%s’” Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context. Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace. |
| ORA-19229 ORA-19229, 00000, “XQST0009 – schema import not supported” Cause: A schema import was encountered in the query. Action: remove the schema import. |
| ORA-19230 ORA-19230, 00000, “XPST0010 – unsupported axis %s ” Cause: An unsupported axis was encountered in the given expression. Action: Remove the unsupported axis from the expression. |
| ORA-19231 ORA-19231, 00000, “XPST0011 – ” Cause: Action: |
| ORA-19232 ORA-19232, 00000, “XQST0012 – imported schemas violate validity rules” Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification. Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique — that is, the pool of definitions must not contain two or more schema components with the same name and target namespace. |
| ORA-19233 ORA-19233, 00000, “XQST0013 – invalid pragma” Cause: A pragma was specified whose contents are invalid. Action: Specify the pragma with the correct contents. |
| ORA-19234 ORA-19234, 00000, “XQST0014 – invalid or unsupported must-understand extension” Cause: The must-understand extension specified was either invalid or unsupported. Action: remove the unsupported must-understand extension or fix the error. |
| ORA-19235 ORA-19235, 00000, “XQST0015 – unsupported must-understand extension” Cause: The XQuery flagger was enabled and the query contained a must-understand extension. Action: remove the unsupported must-understand extension. |
| ORA-19236 ORA-19236, 00000, “XQST0016 – module declaration or import not supported” Cause: The given query had a module declaration or module import. Action: Remove the import module or module declaration. |
| ORA-19237 ORA-19237, 00000, “XPST0017 – unable to resolve call to function – %s:%s” Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. |
| ORA-19238 ORA-19238, 00000, “XPTY0018 – It is a type error if the result of the last step in a path expression contains both nodes and atomic values” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19239 ORA-19239, 00000, “XPTY0019 – It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value” Cause: The step expression returned a sequence containing an atomic value. Action: Fix the path expression to return only nodes. |
| ORA-19240 ORA-19240, 00000, “XPTY0020 – context item must be node in an axis expression” Cause: The context item that was used in the axis epression is not a node. Action: Change the context item to be a node. |
| ORA-19241 ORA-19241, 00000, “XPDY0021 – cast to type %s failed” Cause: The value inside a cast expression could not be cast to the required type. Action: Fix the input to the cast expression to be of a castable type. |
| ORA-19242 ORA-19242, 00000, “XQST0022 – namespace declaration attribute must be a literal” Cause: The namespace declaration attribute was not a literal string. Action: Fix the namespace declaration to be a literal string. |
| ORA-19243 ORA-19243, 00000, “XQTY0023 – invalid document node content in element constructor” Cause: The content sequence in an element constructor contained a document node. Action: Change the content of the element constructor so that it does not contain a document node. |
| ORA-19244 ORA-19244, 00000, “XQTY0024 – invalid attribute node in element constructor” Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node. Action: Change the content sequence of the element constructor so that it does not contain the attribute node. |
| ORA-19245 ORA-19245, 00000, “XQDY0025 – duplicate attribute name %s” Cause: The content sequence of the element constructor contained more than one attribute that had the same name. Action: Remove the duplicate attributes. |
| ORA-19246 ORA-19246, 00000, “validation failed – element %s not found in in-scope element declarations” Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations. Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration. |
| ORA-19247 ORA-19247, 00000, “XQDY0027 – validation error” Cause: An error was encountered during the validation of the expression. Action: Fix the validation error. |
| ORA-19248 ORA-19248, 00000, “XQTY0028 – invalid node in document constructor” Cause: The content sequence in a document constructor contained either a document or an attribute node. Action: Fix the content so it does not contain any of the above node types. |
| ORA-19249 ORA-19249, 00000, “XQDY0029 – value does not match facet of the target type” Cause: The input value to a cast expression did not satisfy the facets of the target type. Action: Fix the value to conform to the facets of the target type. |
| ORA-19250 ORA-19250, 00000, “XQTY0030 – too many values to validate expression” Cause: The argument of a validate expression returned more than one element or document node. Action: Fix the argument of the validate expression to return a single element or document node. |
| ORA-19251 ORA-19251, 00000, “XQST0031 – unsupported query version” Cause: The query version specified in the prolog was not supported. Action: Supply the version of the query that is supported. |
| ORA-19252 ORA-19252, 00000, “XQST0032 – too many declarations for base URI” Cause: The query prolog contained multiple declarations for the base URI. Action: Remove the duplicate definitions for the base URI. |
| ORA-19253 ORA-19253, 00000, “XQST0033 – too many declarations for namespace prefix %s” Cause: The query prolog contained multiple declarations for the same namespace prefix. Action: Remove the duplicate definitions for the namespace prefix. |
| ORA-19254 ORA-19254, 00000, “XQST0034 – too many declarations for function %s” Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName. Action: Remove the duplicate function definitions. |
| ORA-19255 ORA-19255, 00000, “XQST0035 – too many declarations of %s in imported schemas” Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope. Action: Fix the schema imports to remove the name conflict. |
| ORA-19256 ORA-19256, 00000, “XQST0036 – missing type definitions in imported module” Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module. Action: Fix the module definintion to include the in-scope type definition. |
| ORA-19257 ORA-19257, 00000, “XQST0037 – function or variable %s in module already defined” Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module. Action: Remove the conflicting declarations. |
| ORA-19258 ORA-19258, 00000, “XQST0038 – unsupported or duplicate default collation specified” Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported. Action: Remove the duplicate definition or specify a supported collation. |
| ORA-19259 ORA-19259, 00000, “XQST0039 – duplicate parameter name %s in function declaration” Cause: The function declaration contained more than one parameter with the same name. Action: Fix the function declaration to remove the duplicate parameters. |
| ORA-19260 ORA-19260, 00000, “XQST0040 – invalid namespace node in element constructor” Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node. Action: Remove the namespace node in the element constructor. |
| ORA-19261 ORA-19261, 00000, “XQDY0041 – non empty URI in QName” Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty. Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part. |
| ORA-19262 ORA-19262, 00000, “XQST0042 – namespace constructor not inside an element constructor” Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor. Action: Fix the namespace constructor to be inside an element constructor. |
| ORA-19263 ORA-19263, 00000, “XQST0043 – duplicate namespace prefix %s” Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix. Action: Remove the duplicate namespace definitions. |
| ORA-19264 ORA-19264, 00000, “XQDY0044 – invalid namespace in attribute constructors” Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns). Action: Change the namespace for the computed attribute constructor. |
| ORA-19265 ORA-19265, 00000, “XQST0045 – invalid or unknown prefix %s in function declaration” Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local. Action: Fix the function declaration to have the correct prefix. |
| ORA-19266 ORA-19266, 00000, “XQST0046 – invalid URI” Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema. Action: Fix the URI. |
| ORA-19267 ORA-19267, 00000, “module %s not found” Cause: The module with the given target URI could not be found. Action: Fix the prolog to import only available modules. |
| ORA-19268 ORA-19268, 00000, “XQST0048 – namespace %s does not match target namespace %s” Cause: The module contained a function or variable whose namespace did not match the target namespace of the module. Action: Fix the namespace of the function or variable to match the target namespace of the module. |
| ORA-19269 ORA-19269, 00000, “XQST0049 – variable %s defined multiple times” Cause: The module defined or imported the same variable multiple times. Action: Fix the import or the module definition to remove duplicate definitions. |
| ORA-19270 ORA-19270, 00000, “XPDY0050 – treat failed – expected %s got %s” Cause: The type of the operand to the treat expression did not match the required type. Action: Fix the input operand to be of the correct type. |
| ORA-19271 ORA-19271, 00000, “XPST0051 – invalid atomic type definition” Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type. Action: Use the correct atomic type name. |
| ORA-19272 ORA-19272, 00000, “XQDY0052 – invalid atomic value in attribute or element constructor” Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string. Action: Fix the content to contain atomic values that can be cast to a string. |
| ORA-19273 ORA-19273, 00000, “XQST0053 – empty string in namespace declaration” Cause: An empty string was used in a namespace declaration. Action: Fix the namespace declaration to have a non-empty string. |
| ORA-19274 ORA-19274, 00000, “XQST0054 – variable initialization failed due to circularity” Cause: A circular definition was encountered when the variable was initialized. Action: Remove the circularity in the initialization. |
| ORA-19275 ORA-19275, 00000, “XQST0055 – schema path %s not found in list of in-scope schema definitions” Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions. Action: Include the appropriate schema that can be used to resolve the ElementTest. |
| ORA-19276 ORA-19276, 00000, “XPST0005 – XPath step specifies an invalid element/attribute name: (%s)” Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure. Action: Correct the element or attribute name as the name may be mis-spelled. |
| ORA-19277 ORA-19277, 00000, “XPST0005 – XPath step specifies an item type matching no node: (%s)” Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure. Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure. |
| ORA-19278 ORA-19278, 00000, “Invalid value: (%s) for type: (%s)” Cause: The value was invalid for the type. Action: Correct the value or change the type. |
| ORA-19279 ORA-19279, 00000, “XPTY0004 – XQuery dynamic type mismatch: expected singleton sequence – got multi-item sequence” Cause: The XQuery sequence passed in had more than one item. Action: Correct the XQuery expression to return a single item sequence. |
| ORA-19280 ORA-19280, 00000, “XQuery dynamic type mismatch: expected atomic value – got node” Cause: A node was passed in to the expression where an atomic value was expected. Action: Correct the XQuery expression to return an atomic value. |
| ORA-19281 ORA-19281, 00000, “XQST0055 – It is a static error if a Prolog contains more than one copy-namespaces declaration” Cause: The query prolog contained multiple copy-namespaces declarations. Action: Remove the duplicate copy-namespaces declarations. |
| ORA-19282 ORA-19282, 00000, “XQST0068 – It is a static error if a Prolog contains more than one xmlspace declaration” Cause: The query prolog contained multiple xmlspace declarations. Action: Remove the duplicate xmlspace declarations. |
| ORA-19283 ORA-19283, 00000, “XQST0031 – It is a static error if the version number specified in a version declaration is not supported by the implementation.” Cause: The query contained a version declaration not supported by this implementation. Action: Change the version declaration to 1.0 which is the version supported by this implementation. |
| ORA-19284 ORA-19284, 00000, “Encoding specification in version declaration not supported” Cause: The query contained an encoding specification. Action: Remove the encoding specification. |
| ORA-19285 ORA-19285, 00000, “FODC0002 – error retrieving resource” Cause: The URI provided could not be resolved to a valid resource. Action: Provide a valid URI for a resource. |
| ORA-19286 ORA-19286, 00000, “XPST0017 – unable to resolve call to function – %s” Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. |
| ORA-19287 ORA-19287, 00000, “XPST0017 – invalid number of arguments to function – %s:%s” Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. |
| ORA-19288 ORA-19288, 00000, “XPST0017 – invalid number of arguments to function – %s” Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. |
| ORA-19289 ORA-19289, 00000, “XQST0034 – function %s:%s declared or defined multiple times” Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments. Action: Fix the function declaraction or definition to remove duplicates. |
| ORA-19290 ORA-19290, 00000, “XQST0069 – more than one empty order declaration declared in the prolog” Cause: A prolog had more than one empty order declaration. Action: Fix the prolog to have just one empty order declaration. |
| ORA-19291 ORA-19291, 00000, “XPST0081 – specified QName cannot be expanded into a namespace URI” Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces. Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces. |
| ORA-19292 ORA-19292, 00000, “XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19293 ORA-19293, 00000, “XQST0058: It is a static error if multiple schema imports specify the same target namespace” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19294 ORA-19294, 00000, “XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19295 ORA-19295, 00000, “XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19296 ORA-19296, 00000, “XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19297 ORA-19297, 00000, “XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to \”XML\” (in any combination of upper and lower case” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19298 ORA-19298, 00000, “XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19299 ORA-19299, 00000, “XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration” Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. |
| ORA-19300 ORA-19300, 00000, “Error occurred in uri processing%s” Cause: An error occurred when processing the URL Action: Check the given error message and fix the appropriate problem |
| ORA-19320 ORA-19320, 00000, “Host name not specified in HTTP URL” Cause: A host name was not specified in the HTTP url Action: Specify a host name in the HTTP url when creating the URL string |
| ORA-19321 ORA-19321, 00000, “Could not open HTTP connection to host (%s): port (%s)” Cause: A HTTP connection could not be opened to the host Action: Specify a valid host name and port to connect to |
| ORA-19322 ORA-19322, 00000, “An error occurred while reading from host (%s): port (%s)” Cause: An error occurred while reading from the HTTP host Action: Specify a valid host name and port to read from |
| ORA-19323 ORA-19323, 00000, “Invalid url string” Cause: The URL must be a valid URL string Action: Specify a valid url string |
| ORA-19330 ORA-19330, 00000, “Type ‘%s’.'%s’ not installed. Please install the type before using the CREATE_DBURI operator” Cause: The type required for the CREATE_DBURI operator has not been installed correctly. Action: Read the installation notes to install the type correctly. |
| ORA-19331 ORA-19331, 00000, “Last argument to CREATE_DBURI operator must be a column” Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created. Action: Specify a valid column name in the query. |
| ORA-19332 ORA-19332, 00000, “Invalid column in the CREATE_DBURI operator” Cause: The argument to the CREATE_DBURI operator can only be a column. Action: Specify a valid column name for the operator |
| ORA-19333 ORA-19333, 00000, “Invalid flags for the CREATE_DBURI operator” Cause: The flags argument given to the DBURI operator is invalid Action: Specify a valid flag value (TEXT) for the DBURI operator |
| ORA-19334 ORA-19334, 00000, “Invalid column specification for CREATE_DBURI operator” Cause: All columns must be valid and pointing to the same table or view Action: Specify valid list of columns that are from the same table or view. |
| ORA-19335 ORA-19335, 00000, “Invalid format type object” Cause: An invalid format type object was specified for the XML function Action: Specify a valid format type object |
| ORA-19336 ORA-19336, 00000, “Missing XML root element” Cause: The XML being generated does not have an enclosing root element. Action: The XML generated must have a root element |
| ORA-19361 ORA-19361, 00000, “ONLINE option not allowed with this type of index” Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option. |
| ORA-19371 ORA-19371, 00000, “invalid update option” Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE. Action: Adjust the update option and retry the operation. |
| ORA-19372 ORA-19372, 00000, “invalid update condition” Cause: The user attempted to call load_sqlset with an invalid update condition. Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation. |
| ORA-19373 ORA-19373, 00000, “invalid staging table or tablespace” Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace Action: Check the arguments and try again. |
| ORA-19374 ORA-19374, 00000, “invalid staging table” Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table Action: Provide a correct staging table or grant the appropriate privileges |
| ORA-19375 ORA-19375, 00000, “no CREATE TABLE privilege on schema \”%s\”" Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema. Action: Grant the privilege to the user and retry // |
| ORA-19376 ORA-19376, 00000, “no privileges on tablespace provided or tablespace is offline” Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline Action: Allocate space on the tablespace, bring it online, and retry |
| ORA-19377 ORA-19377, 00000, “no \”SQL Tuning Set\” with name like \”%s\” exists for owner like \”%s\”" Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively Action: Provide a different filter after checking the state of the system |
| ORA-19378 ORA-19378, 00000, “invalid mode” Cause: The user specified an invalid mode argument to the capture function. Action: Provide a mode argument that was defined in the dbmssqlt file |
| ORA-19379 ORA-19379, 00000, “invalid time_limit or repeat_interval” Cause: The user specified a NULL value for either the time_limit or the repeat_interval, or a repeat_interval that is greater than the time_limit Action: Provide a non-null value and make sure time_limit >= repeat_interval |
| ORA-19380 ORA-19380, 00000, “invalid plan filter” Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function. Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED. |
| ORA-19381 ORA-19381, 00000, “cannot create staging table in SYS schema” Cause: The user attempted to create a staging table in the sys schema Action: Create the table in another schema. |
| ORA-19382 ORA-19382, 00000, “timeout encountered during sqltune test-execute” Document: NO Cause: This is an internal error code used internally to signal a timeout during a SQL Tune test-execute operation |
| ORA-19383 ORA-19383, 00000, “all plans encountered errors during sqltune test-execute” Document: NO Cause: This is an internal error code used to signify that a sqltune test-execute operation in RESILIENT mode ended with all plans encountering errors. Action: Examine the errors stored in the plans one by one. |
| ORA-19384 ORA-19384, 00000, “cannot pack into staging table from previous version” Cause: An attempt was made to perform a pack operation on a staging table from a previous version. Action: Create a staging table in the current version and retry the operation. |
| ORA-19385 ORA-19385, 00000, “staging table is empty” Cause: An attempt was made to perform an operation on an empty staging table. Action: Check the staging table to make sure that it has rows. |
| ORA-19386 ORA-19386, 00000, “target object already exists for tuning task \”%s\”" Cause: An attempt was made to set a target object for a tuning task when one had already been set. Action: Create a new task if another target object is needed. |
| ORA-19387 ORA-19387, 00000, “\”SQL Tuning Set\” \”%s\” belongs to another tuning task” Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one task within the scope of another task. Action: Check the SQL Tuning Set and retry the operation. |
| ORA-19388 ORA-19388, 00000, “operation not supported for \”SQL Tuning Set\” type” Cause: The attempted operation was unsupported for the type of the given SQL Tuning Set. Action: Check the SQL Tuning Set and retry the operation. |
| ORA-19391 ORA-19391, 00000, “autonfs – kgodm tracing ” Document: NO Cause: This is an Oracle internal event code. This event is bitmask used to control trace output of AutoNFS kgodm . DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-19392 ORA-19392, 00000, “autonfs – kgnfs tracing ” Document: NO Cause: This is an Oracle internal event code. This event is bitmask used to control trace output of AutoNFS kgnfs . DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-19393 ORA-19393, 00000, “autonfs – skgnfs tracing ” Document: NO Cause: This is an Oracle internal event code. This event is bitmask used to control trace output of AutoNFS skgnfs . DO NOT USE. Action: N/A, this is an Oracle internal event code. |
| ORA-19400 ORA-19400, 00000, “System type conflict with object SYS.%s” Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly. Action: Remove the conflicting object and rerun migration. |
| ORA-19500 ORA-19500, 00000, “device block size %s is invalid” Cause: the device block size returned by sequential I/O OSD is invalid Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle. |
| ORA-19501 ORA-19501, 00000, “read error on file \”%s\”, block number %s (block size=%s)” Cause: read error on input file Action: check the file |
| ORA-19502 ORA-19502, 00000, “write error on file \”%s\”, block number %s (block size=%s)” Cause: write error on output file Action: check the file |
| ORA-19503 ORA-19503, 00000, “cannot obtain information on device, name=\”%s\”, type=\”%s\”, parms=\”%s\”" Cause: call to get device information returned an error Action: check device name, type and parameters |
| ORA-19504 ORA-19504, 00000, “failed to create file \”%s\”" Cause: call to create file returned an error Action: check additional messages, check access permissions |
| ORA-19505 ORA-19505, 00000, “failed to identify file \”%s\”" Cause: call to identify the file returned an error Action: check additional messages, and check if the file exists |
| ORA-19506 ORA-19506, 00000, “failed to create sequential file, name=\”%s\”, parms=\”%s\”" Cause: call to create the sequential file returned an error Action: check additional messages, check access permissions |
| ORA-19507 ORA-19507, 00000, “failed to retrieve sequential file, handle=\”%s\”, parms=\”%s\”" Cause: call to retrieve the sequential file returned an error Action: check additional messages, and check if the file exists |
| ORA-19508 ORA-19508, 00000, “failed to delete file \”%s\”" Cause: call to delete the file returned an error Action: check additional messages |
| ORA-19509 ORA-19509, 00000, “failed to delete sequential file, handle=\”%s\”, parms=\”%s\”" Cause: call to delete the sequential file returned an error Action: check additional messages |
| ORA-19510 ORA-19510, 00000, “failed to set size of %s blocks for file \”%s\” (block size=%s)” Cause: call to resize the file returned an error Action: check additional messages |
| ORA-19511 ORA-19511, 00000, “Error received from media manager layer, error text:\n %s” Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager. Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software. |
| ORA-19512 ORA-19512, 00000, “file search failed” Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed. Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed. |
| ORA-19513 ORA-19513, 00000, “failed to identify sequential file” Cause: Unable to identify the sequential file. Action: Check additional messages, and check if the file exists on media. |
| ORA-19525 ORA-19525, 00000, “tempfile for the clone database must be renamed” Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile. *Action Rename the tempfiles manually or automatically by using the DB_FILE_NAME_CONVERT initialization parameter. |
| ORA-19526 ORA-19526, 00000, “only one location allowed for parameter %s” Cause: A list of default locations was provided in an Oracle-managed files parameter. *Action Edit the parameter to include a single location. |
| ORA-19527 ORA-19527, 00000, “physical standby redo log must be renamed” Cause: The CLEAR LOGFILE command was used at a physical standby database. This command cannot be used at a physical standby database unless the LOG_FILE_NAME_CONVERT initialization parameter is set. This is required to avoid overwriting the primary database’s log files. *Action Set the LOG_FILE_NAME_CONVERT initialization parameter. |
| ORA-19528 ORA-19528, 00000, “redo logs being cleared may need access to files” Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to. Action: Wait for the redo logs to be cleared. |
| ORA-19529 ORA-19529, 00000, “Pattern %s in initialization parameter %s has an Oracle Managed Files file name.” Cause: An attempt was made to convert a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid operation. Action: Retry the operation with a pattern template instead of a full Oracle Managed Files file name. |
| ORA-19550 ORA-19550, 00000, “cannot use backup/restore functions while using dispatcher” Cause: Attempted to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process. Action: Connect directly to the instance then re-execute the backup or restore function. |
| ORA-19551 ORA-19551, 00000, “device is busy, device type: %s, device name: %s” Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy. Action: Either attempt to allocate another device or wait until the required device is no longer busy. |
| ORA-19552 ORA-19552, 00000, “device type %s is invalid” Cause: The device type indicated is invalid. Action: Supply a correct device type and retry the allocation. |
| ORA-19553 ORA-19553, 00000, “device name %s is invalid” Cause: The device name indicated is invalid. Action: Supply a correct device name and retry the allocation. |
| ORA-19554 ORA-19554, 00000, “error allocating device, device type: %s, device name: %s” Cause: The specified device could not be allocated. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| ORA-19555 ORA-19555, 00000, “invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value” Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range. Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2. |
| ORA-19556 ORA-19556, 00000, “required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred” Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination. Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter. |
| ORA-19557 ORA-19557, 00000, “device error, device type: %s, device name: %s” Cause: An error occurred in the platform-specific device code Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| ORA-19558 ORA-19558, 00000, “error de-allocating device” Cause: The specified device could not be de-allocated. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| ORA-19559 ORA-19559, 00000, “error sending device command: %s” Cause: An error occurred while sending the indicated command to the session device. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| ORA-19560 ORA-19560, 00000, “%s is not a valid device limit” Cause: An invalid type of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT. Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL. |
| ORA-19561 ORA-19561, 00000, “%s requires a DISK channel” Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found. Action: Deallocate the current device and allocate a DISK channel, then then retry the command. |
| ORA-19562 ORA-19562, 00000, “file %s is empty” Cause: The indicated file, which is an archived log, control file, or datafile was found to be empty during a copy, backup, or scan] operation. Action: Ensure that the correct files are being specified for the copy or backup operation. |
| ORA-19563 ORA-19563, 00000, “%s header validation failed for file %s” Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database. Action: Ensure that the correct files are being specified for the copy or backup operation. |
| ORA-19564 ORA-19564, 00000, “error occurred writing %s bytes at block number %s” Cause: An error occurred while writing to a file. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation. |
| ORA-19565 ORA-19565, 00000, “BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices” Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled. Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices. |
| ORA-19566 ORA-19566, 00000, “exceeded limit of %s corrupt blocks for file %s” Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup. Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt. |
| ORA-19567 ORA-19567, 00000, “cannot shrink file %s because it is being backed up or copied” Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied. Action: Retry the resize after the backup or copy is complete. |
| ORA-19568 ORA-19568, 00000, “a device is already allocated to this session” Cause: A device cannot be allocated to a session if another device is already allocated. Action: Deallocate the current device |
| ORA-19569 ORA-19569, 00000, “no device is allocated to this session” Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated. Action: Allocate a device then retry the operation. |
| ORA-19570 ORA-19570, 00000, “file number %s is outside valid range of 1 through %s” Cause: A file number used in a copy, backup, or restore operation is not valid for the current database. Action: Specify a valid file number. |
| ORA-19571 ORA-19571, 00000, “%s RECID %s STAMP %s not found in control file” Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file. Action: Specify a correct RECID/STAMP and retry the copy or backup. |
| ORA-19572 ORA-19572, 00000, “cannot process file %s, file is being being resized” Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized. Action: Wait for the resize to complete then retry the copy or backup. |
| ORA-19573 ORA-19573, 00000, “cannot obtain %s enqueue for datafile %s” Cause: The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is ‘shared’, then the file is the input file for a backup or copy. If the type is ‘exclusive’, then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file – in this case, the file must be offline or the database must be closed. If the type is ‘read-only’, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode. Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly. |
| ORA-19574 ORA-19574, 00000, “output file name must be specified” Cause: This type of copy or restore requires an output file name. Action: Specify an output file name and retry the copy. |
| ORA-19575 ORA-19575, 00000, “expected %s blocks in file %s, found %s” Cause: During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header. Action: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted. |
| ORA-19576 ORA-19576, 00000, “datafile %s not defined in control file” Cause: The specified file number was not found in the control file. Action: Specify a correct file number and retry the operation. |
| ORA-19577 ORA-19577, 00000, “file %s is MISSING” Cause: A COPYDATAFILECOPY, RESTOREDATAFILETO or PROXYRESTOREDATAFILE function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration. Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file. |
| ORA-19578 ORA-19578, 00000, “end of volume while duplexing to sequential files, backup piece incomplete” Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently. Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing. |
| ORA-19579 ORA-19579, 00000, “archived log record for %s not found” Cause: No archived log record corresponding to input file could be found in the control file. Action: Specify a valid archived log file name and retry the operation. |
| ORA-19580 ORA-19580, 00000, “%s conversation not active” Cause: A backup or restore operation was attempted before a conversation was started. Action: Start a conversation then retry the operation. |
| ORA-19581 ORA-19581, 00000, “no files have been named” Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore. Action: Specify some files then retry the operation. |
| ORA-19582 ORA-19582, 00000, “archived log file header validation for %s failed” Cause: Archived log file header is corrupt and could not be validated. Action: Provide a valid archived log file and retry the operation. |
| ORA-19583 ORA-19583, 00000, “conversation terminated due to error” Cause: An error occurred which forced the termination of the current backup or restore conversation. Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation. |
| ORA-19584 ORA-19584, 00000, “file %s already in use” Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database. Action: Specify a different name and retry the operation. |
| ORA-19585 ORA-19585, 00000, “premature end of volume on piece %s” Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set. Action: Retry the piece with a larger piece of output media. |
| ORA-19586 ORA-19586, 00000, “%s k-byte limit is too small to hold piece directory” Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data. Action: Use the SETLIMIT procedure to increase the k-byte limit and retry the operation. |
| ORA-19587 ORA-19587, 00000, “error occurred reading %s bytes at block number %s” Cause: An error occurred while reading from a file. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation. |
| ORA-19588 ORA-19588, 00000, “%s RECID %s STAMP %s is no longer valid” Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was ‘consumed’ by a SWITCHTOCOPY operation. Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID. |
| ORA-19589 ORA-19589, 00000, “%s is not a snapshot or backup control file” Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file. Action: Specify the name of a snapshot or backup control file. |
| ORA-19590 ORA-19590, 00000, “conversation already active” Cause: You tried to begin a backup or restore conversation, but another conversation is already active in this session. Action: Either continue the current conversation, or call BACKUPCANCEL or RESTORECANCEL to end the current conversation before starting a new one. |
| ORA-19591 ORA-19591, 00000, “backup aborted because job time exceeded duration time” Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup. Action: Adjust the duration time and re-run the command. Or run the backup command without duration option. |
| ORA-19592 ORA-19592, 00000, “wrong %s conversation type” Cause: You attempted to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19593 ORA-19593, 00000, “datafile number %s already included as %s” Cause: This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19594 ORA-19594, 00000, “control file already included as %s” Cause: The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19595 ORA-19595, 00000, “archived log %s already included in backup conversation” Cause: The indicated archived log has already been specified for inclusion in this backup conversation. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19596 ORA-19596, 00000, “SPFILE already included” Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19597 ORA-19597, 00000, “file %s block size %s does not match set block size of %s” Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size. Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified. |
| ORA-19598 ORA-19598, 00000, “can not backup SPFILE because the instance was not started with SPFILE” Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance. Action: Create an SPFILE and re-start the instance using the SPFILE. |
| ORA-19599 ORA-19599, 00000, “block number %s is corrupt in %s %s” Cause: A corrupt block was found in a control file, archived log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archived logs, or backup pieces. Action: None. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried. |
| ORA-19600 ORA-19600, 00000, “input file is %s %s (%s)” Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown. For a datafile, the file number refers to the datafile’s absolute file number as shown in the DBA_DATA_FILES view. For a datafile copy, the file number refers to the copy’s control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log’s control file record number as shown in the RECID column of the V$ARCHIVED_LOG view. Action: See other error message. |
| ORA-19601 ORA-19601, 00000, “output file is %s %s (%s)” Cause: This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its control file record number may not have been determined when the message is printed. In that case, the record number shown is zero. Action: See other error message. |
| ORA-19602 ORA-19602, 00000, “cannot backup or copy active file in NOARCHIVELOG mode” Cause: You tried to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs. Action: Take the tablespace offline clean or close the database and retry the copy or backup. |
| ORA-19603 ORA-19603, 00000, “cannot backup or copy active file with KEEP .. UNRECOVERABLE option” Cause: The user tried to copy or backup a file that was not closed cleanly, with KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of KEEP .. UNRECOVERABLE option. Action: Take the tablespace offline cleanly, or close the database and retry the copy or backup. |
| ORA-19604 ORA-19604, 00000, “conversation file naming phase is over” Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed. Action: You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation. |
| ORA-19605 ORA-19605, 00000, “input file name must be specified” Cause: The input file name was not specified for a control file copy operation. Action: Specify an input file name and retry the operation. |
| ORA-19606 ORA-19606, 00000, “Cannot copy or restore to snapshot control file” Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file. Action: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified. |
| ORA-19607 ORA-19607, 00000, “%s is an active control file” Cause: A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file. Action: Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified. |
| ORA-19608 ORA-19608, 00000, “%s is not a backup piece” Cause: The specified file is not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece. Action: Specify a different file name and retry the operation. |
| ORA-19609 ORA-19609, 00000, “%s is from different backup set: stamp %s count %s” Cause: The specified file is not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown. Action: Specify the correct backup piece and retry the operation. |
| ORA-19610 ORA-19610, 00000, “directory block %s is corrupt” Cause: The indicated directory block failed checksum validation. This backup piece is unusable. Action: Supply another copy of the same backup piece, or terminate the restore conversation. |
| ORA-19611 ORA-19611, 00000, “backup piece out of order. Expected %s but found %s” Cause: This backup piece is out of sequence. Action: Supply the correct backup piece. |
| ORA-19612 ORA-19612, 00000, “datafile %s not restored due to %s” Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece. Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled. |
| ORA-19613 ORA-19613, 00000, “datafile %s not found in backup set” Cause: The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the control file. Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files. |
| ORA-19614 ORA-19614, 00000, “archived log thread %s sequence %s not found in backup set” Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set. Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files. |
| ORA-19615 ORA-19615, 00000, “some files not found in backup set” Cause: Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file that was not found. Action: See the instructions for message 19613. |
| ORA-19616 ORA-19616, 00000, “output file name must be specified if database not mounted” Cause: A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file. Action: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls. |
| ORA-19617 ORA-19617, 00000, “file %s contains different RESETLOGS data” Cause: The indicated file contains RESETLOGS data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same RESETLOGS data. Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set. |
| ORA-19618 ORA-19618, 00000, “cannot name files after RESTOREVALIDATE has been called” Cause: A call was made to specify a file to restore from a backup set, but a previous call to RESTOREVALIDATE has already been made. Action: You must cancel and restart the conversation if you wish to specify files to restore. |
| ORA-19619 ORA-19619, 00000, “cannot call RESTOREVALIDATE after files have been named” Cause: RESTOREVALIDATE was called after some files had already been specified for restoration. Action: You must cancel and restart the conversation if you wish to call RESTOREVALIDATE. |
| ORA-19620 ORA-19620, 00000, “%s is not of %s type” Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database. Action: The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation. |
| ORA-19621 ORA-19621, 00000, “archived log range has already been specified” Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation. Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired. |
| ORA-19622 ORA-19622, 00000, “archived log thread %s sequence %s not restored due to %s” Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece. Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled. |
| ORA-19623 ORA-19623, 00000, “file %s is open” Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent datafile is open. Action: Take the owning tablespace offline or close the database, then retry the operation. |
| ORA-19624 ORA-19624, 00000, “operation failed, retry possible” Cause: A backup, restore or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried. Action: This message is used by recovery manager to decide whether or not to retry the operation. |
| ORA-19625 ORA-19625, 00000, “error identifying file %s” Cause: A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An OS-specific error accompanies this error to help pinpoint the problem. Action: Specify an different file and retry the operation. |
| ORA-19626 ORA-19626, 00000, “backup set type is %s – can not be processed by this conversation” Cause: The data in the backup set is not compatible with the current conversation. Action: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set. |
| ORA-19627 ORA-19627, 00000, “cannot read backup pieces during control file application” Cause: This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation. Action: The conversation is still active and more control files may be applied. |
| ORA-19628 ORA-19628, 00000, “invalid SCN range” |
| ORA-19629 ORA-19629, 00000, “no files in specified archived log SCN range” Cause: This backup set contains no files in the specified range. Action: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set. |
| ORA-19630 ORA-19630, 00000, “end of volume encountered while copying backup piece” Cause: While copying a backup piece from the OS native file system to an output device, the output device encountered end-of-volume. Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece. |
| ORA-19631 ORA-19631, 00000, “archived log record contains no file name” Cause: This archived log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost. Action: Specify the RECID of an archived log record that contains a file name. Fixed view v$archived_log can be used to examine the archived logs. |
| ORA-19632 ORA-19632, 00000, “file name not found in control file” Cause: The name passed to GETFNO was not found in the control file. Action: Supply a valid file name. |
| ORA-19633 ORA-19633, 00000, “control file record %s is out of sync with recovery catalog” Cause: The control file record describing the file to be deleted in a call to DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or DELETEARCHIVEDLOG does not match the validation data supplied by recovery manager. Action: contact Oracle support |
| ORA-19634 ORA-19634, 00000, “file name required for this function” Cause: The FNAME or HANDLE parameter was not specified for DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE. Action: Specify the FNAME or HANDLE parameter when calling these functions. |
| ORA-19635 ORA-19635, 00000, “input and output file names are identical: %s” Cause: Identical input and output file names were specified for a datafile copy operation. Action: Specify an output file name which is different from the input file name. |
| ORA-19636 ORA-19636, 00000, “archived log thread %s sequence %s already included” Cause: The indicated archived log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archived log. Action: No action required – the conversation is still active, and more files can be specified. |
| ORA-19637 ORA-19637, 00000, “BACKUPPIECECREATE requires file name when using DISK device” Cause: The session device is currently allocated to disk, and so a file name is required. Action: Supply a file name and retry the operation. |
| ORA-19638 ORA-19638, 00000, “file %s is not current enough to apply this incremental backup” Cause: The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost. Action: Supply a backup set that can be applied and retry the operation. |
| ORA-19639 ORA-19639, 00000, “file %s is more current than this incremental backup” Cause: The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it. Action: Supply a backup set that can be applied and retry the operation. |
| ORA-19640 ORA-19640, 00000, “datafile checkpoint is SCN %s time %s” Cause: This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied. Action: See other error message. |
| ORA-19641 ORA-19641, 00000, “backup datafile checkpoint is SCN %s time %s” Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied. Action: See other error message. |
| ORA-19642 ORA-19642, 00000, “start SCN of incremental backup is %s” Cause: This message identifies the starting SCN of an incremental backup that could not be applied. Action: See other error message. |
| ORA-19643 ORA-19643, 00000, “datafile %s: incremental-start SCN is too recent” Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed. Action: Specify a smaller incremental-start SCN. |
| ORA-19644 ORA-19644, 00000, “datafile %s: incremental-start SCN is prior to RESETLOGS SCN %s” Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the RESETLOGS SCN. Action: Specify a larger incremental-start SCN. |
| ORA-19645 ORA-19645, 00000, “datafile %s: incremental-start SCN is prior to creation SCN %s” Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile’s creation SCN. Action: Specify a larger incremental-start SCN. |
| ORA-19646 ORA-19646, 00000, “cannot change size of datafile %s from %s to %s” Cause: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed. Action: Examine the other messages which should be present to indicate the cause of the failure. |
| ORA-19647 ORA-19647, 00000, “non-zero LEVEL cannot be specified when INCREMENTAL is FALSE” Cause: BACKUPSETDATAFILE was called with a non-zero backup_level and a FALSE incremental indication. Action: Either set incremental to TRUE or change backup_level to zero. |
| ORA-19648 ORA-19648, 00000, “datafile %s: incremental-start SCN equals checkpoint SCN” Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile’s checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to. Action: Specify a smaller incremental-start SCN. // NOTE that this message will usually only be encountered by the user while taking an incremental backup with Recovery Manager. Recovery Manager should intercept all usual cases of this error and simply ignore the incremental backup for this file. So, if you do encounter this error, please report it to Oracle Support. |
| ORA-19649 ORA-19649, 00000, “offline-range record RECID %s STAMP %s not found in file %s” Cause: APPLYOFFLINERANGE was called with a RECID/STAMP which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is. Action: Specify the RECID/STAMP of a record that exists in the control file copy. |
| ORA-19650 ORA-19650, 00000, “Offline-range record RECID %s STAMP %s in file %s has SCN %s” Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file. Action: See other error message. |
| ORA-19651 ORA-19651, 00000, “cannot apply offline-range record to datafile %s: SCN mismatch” Cause: APPLYOFFLINERANGE cannot apply an offline-range record to a target datafile unless the datafile’s checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record. Action: Specify an offline-range record whose offline-clean SCN matches the target datafile’s checkpoint. |
| ORA-19652 ORA-19652, 00000, “cannot apply offline-range record to datafile %s: file is fuzzy” Cause: The target datafile for an APPLYOFFLINERANGE call is fuzzy. Action: Specify a target datafile that is closed cleanly. |
| ORA-19653 ORA-19653, 00000, “cannot switch to older file incarnation” Cause: SWITCHTOCOPY was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up. Action: Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile. |
| ORA-19654 ORA-19654, 00000, “must use backup control file to switch file incarnations” Cause: This SWITCHTOCOPY operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file. Action: Restore and mount a backup control file. |
| ORA-19655 ORA-19655, 00000, “cannot switch to incarnation with different RESETLOGS data” Cause: This SWITCHTOCOPY operation is attempting to switch to a datafile which comes from a different RESETLOGS version of the database. Action: Either restore a backup control file that was taken from the same database version as the target datafile copy, or switch to a different datafile copy. |
| ORA-19656 ORA-19656, 00000, “cannot backup, copy, or delete online log %s” Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs. Action: The indicated log file cannot be processed – select another file. |
| ORA-19657 ORA-19657, 00000, “cannot inspect current datafile %s” Cause: The file being inspected is already part of the currently mounted database. Action: None – the file is already part of the database. |
| ORA-19658 ORA-19658, 00000, “cannot inspect %s – file is from different RESETLOGS” Cause: The RESETLOGS data in the log file being inspected does not match that in the currently mounted control file. Action: The indicated file cannot be processed – inspect another file. |
| ORA-19659 ORA-19659, 00000, “incremental restore would advance file %s past RESETLOGS” Cause: This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database. Action: This incremental cannot be applied to this datafile. If you wish to recover the file to the RESETLOGS SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file. |
| ORA-19660 ORA-19660, 00000, “some files in the backup set could not be verified” Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set. Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set. |
| ORA-19661 ORA-19661, 00000, “datafile %s could not be verified” Cause: Some data blocks for the indicated datafile were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set. |
| ORA-19662 ORA-19662, 00000, “archived log thread %s sequence %s could not be verified” Cause: Some data blocks for the indicated archived log were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set. |
| ORA-19663 ORA-19663, 00000, “cannot apply current offline range to datafile %s” Cause: An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range. Action: The datafile remains unchanged. |
| ORA-19664 ORA-19664, 00000, “file type: %s, file name: %s” Cause: This message is issued to identify the file which is the subject of an error. Action: None – this is an informational message. There should be other Oracle messages explaining the cause of the error. |
| ORA-19665 ORA-19665, 00000, “size %s in file header does not match actual file size of %s” Cause: The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks. Action: This file is not usable – it has most likely been truncated. |
| ORA-19666 ORA-19666, 00000, “cannot do incremental restore of the control file” Cause: The control file was included in an incremental restore conversation Action: If you wish to restore the control file, you must do a full restore of the control file |
| ORA-19667 ORA-19667, 00000, “cannot do incremental restore of datafile %s” Cause: The backup of the datafile is a full backup Action: If you wish to restore the datafile, you must do a full restore of the datafile |
| ORA-19668 ORA-19668, 00000, “cannot do full restore of datafile %s” Cause: The backup of the datafile is an incremental backup Action: If you wish to restore the datafile, you must do an incremental restore of the datafile |
| ORA-19669 ORA-19669, 00000, “proxy copy functions cannot be run on DISK channel” Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK. Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a 3rd-party media management software product that supports the this backup/restore feature. |
| ORA-19670 ORA-19670, 00000, “file %s already being restored” Cause: A proxy restore function has already named this file as a restore destination. Action: Use a different file name. If this message occurs during a recovery manager job, then this is an internal error in recovery manager, and you should contact Oracle support. |
| ORA-19671 ORA-19671, 00000, “media management software returned invalid proxy handle” Cause: During a proxy backup or restore, the media management software returned an invalid file handle. Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor. |
| ORA-19672 ORA-19672, 00000, “media management software returned invalid file status” Cause: During a proxy backup or restore, the media management software returned an invalid file status. Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor. |
| ORA-19673 ORA-19673, 00000, “error during proxy copy of file %s” Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully. Action: There should be other errors on the error stack which explain why the file could not be successfully copied. |
| ORA-19674 ORA-19674, 00000, “file %s is already being backed up with proxy copy” Cause: Recovery manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another recovery manager job. Action: Wait until the other recovery manager backup of this file is complete, then retry the backup. |
| ORA-19675 ORA-19675, 00000, “file %s was modified during proxy copy” Cause: A proxy backup of the specified file failed because the file was brought on-line or otherwise modified while the proxy backup was in progress. This file was off-line or read-only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress. Action: Take another backup of this file. |
| ORA-19676 ORA-19676, 00000, “one or more files failed during proxy backup or restore” Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully. Action: Examine the messages regarding the specific files to determine the cause of the problems. |
| ORA-19677 ORA-19677, 00000, “RMAN configuration name exceeds maximum length of %s” Cause: The configuration name string exceeds maximum length. Action: Supply a correct configuration name and retry the function. |
| ORA-19678 ORA-19678, 00000, “RMAN configuration value exceeds maximum length of %s” Cause: The configuration value string exceeds maximum length. Action: Supply a correct configuration value and retry the operation. |
| ORA-19679 ORA-19679, 00000, “RMAN configuration number %s is outside valid range of 1 through %s” Cause: An invalid RMAN Configuration number was specified. Action: Specify a correct datafile number and retry the operation. |
| ORA-19680 ORA-19680, 00000, “some blocks not recovered. See trace file for details” Cause: Some blocks are not recovered during block media recovery. Action: See trace files for details of the problem. |
| ORA-19681 ORA-19681, 00000, “block media recovery on control file not possible” Cause: file number 0 specified in block media recovery Action: check file number |
| ORA-19682 ORA-19682, 00000, “file %s not in block media recovery context” Cause: Internal error Action: |
| ORA-19683 ORA-19683, 00000, “real and backup block size of file %s are unequal” Cause: block size changed between backup & real file Action: use right backup |
| ORA-19684 ORA-19684, 00000, “block media recovery failed because database is suspended” Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement Action: Execute ALTER SYSTEM RESUME then retry block media recovery |
| ORA-19685 ORA-19685, 00000, “SPFILE could not be verified” Cause: Some data blocks for the SPFILE were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set. |
| ORA-19686 ORA-19686, 00000, “SPFILE not restored due to %s” Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece. Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set. |
| ORA-19687 ORA-19687, 00000, “SPFILE not found in backup set” Cause: The SPFILE could not be restored, because it is not in this backup set. Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file. |
| ORA-19688 ORA-19688, 00000, “control file AUTOBACKUP format(%s) for %s does not have %F” Cause: control file AUTOBACKUP format must contain %F for the device. Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE |
| ORA-19689 ORA-19689, 00000, “cannot have more than one %F in control file AUTOBACKUP format(%s) for %s” Cause: control file AUTOBACKUP format contains more than one %F for the device. Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE |
| ORA-19690 ORA-19690, 00000, “backup piece release %s incompatible with Oracle release %s” Cause: The backup piece was created by incompatible software. Action: Either restart with a compatible software release or create another backup using the current release. |
| ORA-19691 ORA-19691, 00000, “%s is from different database: id=%s, name=%s” Cause: The database name or database id in backup piece header does not match the one in control file. Action: Supply the correct backup piece belonging to this database. |
| ORA-19692 ORA-19692, 00000, “missing creation stamp on piece %s” Cause: The backup piece doesn’t have information about creation stamp. Action: Supply another backup piece which is created by oracle 9i or later version. |
| ORA-19693 ORA-19693, 00000, “backup piece %s already included” Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece. Action: Remove the specified duplicate backup piece in restore steps and restart the conversation. |
| ORA-19694 ORA-19694, 00000, “some changed blocks were not found in the change tracking file” Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file. Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup. |
| ORA-19695 ORA-19695, 00000, “fixed table X$KRBMSFT has not been populated” Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES. Action: Internal error – contact Oracle Customer Support. |
| ORA-19696 ORA-19696, 00000, “control file not found in backup set” Cause: The control file could not be restored because it is not in this backup set. Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file. |
| ORA-19697 ORA-19697, 00000, “standby control file not found in backup set” Cause: The standby control file could not be restored because it is not in this backup set. Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file. |
| ORA-19698 ORA-19698, 00000, “%s is from different database: id=%s, db_name=%s” Cause: Catalog failed because the database id in file header does not match the one in control file. Action: Supply the correct file belonging to this database. |
| ORA-19699 ORA-19699, 00000, “cannot make copies with compression enabled” Cause: Datafile copies with compression are not supported. Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called outside RMAN, then the incompatible values are being passed for the parameters DOCOMPRESS and IMAGCP. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support. |
| ORA-19700 ORA-19700, 00000, “device type exceeds maximum length of %s” Cause: The device type indicated is invalid. Action: Supply a correct device type and retry the allocation. |
| ORA-19701 ORA-19701, 00000, “device name exceeds maximum length of %s” Cause: The device name indicated is invalid. Action: Supply a correct device name and retry the allocation. |
| ORA-19702 ORA-19702, 00000, “device parameter exceeds maximum length of %s” |
| ORA-19703 ORA-19703, 00000, “device command string exceeds maximum length of %s” Cause: The device command string exceeds maximum length. Action: Correct the command and retry the operation. |
| ORA-19704 ORA-19704, 00000, “file name exceeds maximum length of %s” Cause: The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system. Action: Retry the operation with a shorter file name. |
| ORA-19705 ORA-19705, 00000, “tag value exceeds maximum length of %s characters” Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header. Action: Supply a shorter tag and retry the operation. |
| ORA-19706 ORA-19706, 00000, “invalid SCN” Cause: The input SCN is either not a positive integer or too large. Action: Check the input SCN and make sure it is a valid SCN. |
| ORA-19707 ORA-19707, 00000, “invalid record block number – %s ” Cause: The input number is either negative or too large. Action: Check the input record block number and make sure it is a valid number clauses in the create database statement. |
| ORA-19708 ORA-19708, 00000, “log destination exceeds maximum length of %s characters” Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum. Action: Supply a shorter destination and retry the operation. |
| ORA-19709 ORA-19709, 00000, “numeric parameter must be non-negative integer” Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion. Action: Supply a valid numeric parameter. |
| ORA-19710 ORA-19710, 00000, “unsupported character set %s” Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment. Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable. |
| ORA-19711 ORA-19711, 00000, “cannot use RENORMALIZEALLFILENAMES while database is open” Cause: An attempt was made to re-normalize all the file names in the control file while the database is open. Action: Close the database before using the RENORMALIZEALLFILENAMES procedure. |
| ORA-19712 ORA-19712, 00000, “table name exceeds maximum length of %s” Cause: The table name string exceeds maximum length. Action: Retry the operation with a shorter table name. |
| ORA-19713 ORA-19713, 00000, “invalid copy number: %s ” Cause: The copy number is not in a valid range or you have reached maximum limit. Action: Report the error and other information to support. |
| ORA-19714 ORA-19714, 00000, “length for generated name longer than %s” Cause: The specified format exceeds the maximum length for the piece name. Action: Change the format to create shorter piece names. |
| ORA-19715 ORA-19715, 00000, “invalid format %s for generated name” Cause: A restricted format or undefined format was used incorrectly. Action: Change the format specified in the additional information by removing the restricted format. |
| ORA-19716 ORA-19716, 00000, “error processing format %s to generate name for backup” Cause: There were errors while processing the format to generate name for backup. Action: Change the format. |
| ORA-19717 ORA-19717, 00000, “for non-OMF search the pattern must be specified” Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE. Action: Either specify the pattern or set the parameter OMF to TRUE. |
| ORA-19718 ORA-19718, 00000, “length for command id longer than %s” Cause: The specified command id exceeds the maximum length for command id. Action: Supply a shorter command id and retry the operation. |
| ORA-19719 ORA-19719, 00000, “length for operation name longer than %s” Cause: The specified operation name exceeds the maximum length for operation name. Action: Supply a shorter operation name and retry the operation. |
| ORA-19720 ORA-19720, 00000, “Error occurred when converting an OCI number into an SCN” Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file. Action: See other errors on the error stack to look for the source of the problem. |
| ORA-19721 ORA-19721, 00000, “Cannot find datafile with absolute file number %s in tablespace %s” Cause: Can not find one of the datafile that should be in the Pluggable Set. Action: Make sure all datafiles are specified via import command line option or parameter files. |
| ORA-19722 ORA-19722, 00000, “datafile %s is an incorrect version” Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version. Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only. |
| ORA-19723 ORA-19723, 00000, “Cannot recreate plugged in read-only datafile %s” Cause: The datafile is plugged in read only. It can not recreated. Action: Use ALTER DATABASE RENAME FILE command instead. |
| ORA-19724 ORA-19724, 00000, “snapshot too old: snapshot time is before file %s plug-in time” Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database. Action: retry the query. |
| ORA-19725 ORA-19725, 00000, “can not acquire plug-in enqueue” Cause: There maybe another “ALTER DATABASE RESET COMPATIBILITY” command issued concurrently, preventing this process from acquiring the plug-in enqueue. Action: retry the operation. |
| ORA-19726 ORA-19726, 00000, “cannot plug data [%s] at level %s into database running at compatibility level %s” Cause: Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data. Action: Raise the “compatible” init.ora parameter and retry the operation. |
| ORA-19727 ORA-19727, 00000, “cannot plug data [%s] at level %s into database running Oracle %s” Cause: Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data. Action: Upgrade Oracle and retry the operation. |
| ORA-19728 ORA-19728, 00000, “data object number conflict between table %s and partition %s in table %s” Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One can not exchange the table with the partition in this case. Action: Use “alter table move partition” command to move the offending partition, so that the partition will get a new data object number. Retry the operation then. |
| ORA-19729 ORA-19729, 00000, “File %s is not the initial version of the plugged in datafile” Cause: The file is not the initial version of the plugged in datafile. Action: Use the correct initial version of the plugged in datafile. |
| ORA-19730 ORA-19730, 00000, “can not convert offline plugged-in datafile %s” Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online. Action: Online the datafile and retry the operation. |
| ORA-19731 ORA-19731, 00000, “cannot apply change to unverified plugged-in datafile %s” Cause: Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery. Action: Use the correct control file and continue recovery. |
| ORA-19732 ORA-19732, 00000, “incorrect number of datafiles for tablespace %s” Cause: The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file. Action: Use the correct export file and retry the operation. |
| ORA-19733 ORA-19733, 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-19734 ORA-19734, 00000, “wrong creation SCN – control file expects converted plugged-in datafile” Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile. Action: Either restore the converted datafile or continue recovering the datafile. |
| ORA-19735 ORA-19735, 00000, “wrong creation SCN – control file expects initial plugged-in datafile” Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the converted datafile. Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file. |
| ORA-19736 ORA-19736, 00000, “can not plug a tablespace into a database using a different national character set” Cause: Oracle does not support plugging a tablespace into a database using a different national character set. Action: Use import/export or unload/load to move data instead. |
| ORA-19737 ORA-19737, 00000, “simulate read-only database connection to execute sql query” Document: NO Cause: Set on RMAN foreground connections when archiver was hung. Action: Turn off plsql/sql statistics collection, obtaining the temp segment for sorting and grabbing the sequence number from disk. |
| ORA-19738 ORA-19738, 00000, “cannot find language information for character set: ‘%s’” Cause: The compatibility check failed because a character set name that was provided is not valid. Action: Correct the character set name and retry. |
| ORA-19740 ORA-19740, 00000, “text is longer than %s” Cause: The specified text exceeds the maximum length for text. Action: Supply a shorter text and retry the operation. |
| ORA-19750 ORA-19750, 00000, “change tracking file: ‘%s’” Cause: This message reports the name of a file involved in other messages. Action: See associated error messages for a description of the problem. |
| ORA-19751 ORA-19751, 00000, “could not create the change tracking file” Cause: It was not possible to create the change tracking file. Action: Check that there is sufficient disk space and no conflicts in file names and try to enable block change tracking again. |
| ORA-19752 ORA-19752, 00000, “block change tracking is already enabled” Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database. Action: None, this is an informative message only. |
| ORA-19753 ORA-19753, 00000, “error writing to change tracking file” Cause: An I/O error occurred while writing to the change tracking file. Action: There will be other messages on the error stack that show details of the problem. |
| ORA-19754 ORA-19754, 00000, “error reading from change tracking file” Cause: An I/O error occurred while reading from the change tracking file. Action: There will be other messages on the error stack that show details of the problem. |
| ORA-19755 ORA-19755, 00000, “could not open change tracking file” Cause: The change tracking file could not be opened. Action: There will be other messages on the error stack that show details of the problem. |
| ORA-19756 ORA-19756, 00000, “corrupt block number %s found in change tracking file” Cause: The specified block number is corrupt in the change tracking file. Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block. |
| ORA-19757 ORA-19757, 00000, “could not resize change tracking file to %s blocks” Cause: An error occurred while trying to change the size of the change tracking file. Action: There will be other messages on the error stack that show details of the problem. |
| ORA-19758 ORA-19758, 00000, “failed to enable/disable block change tracking: out of SGA memory” Cause: out of SGA memory Action: Increase SGA and restart the instance. |
| ORA-19759 ORA-19759, 00000, “block change tracking is not enabled” Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled. Action: None, this is an informative message only. |
| ORA-19760 ORA-19760, 00000, “error starting change tracking” Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error. Action: Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking. |
| ORA-19761 ORA-19761, 00000, “block size %s is not valid for change tracking file” Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt. Action: If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file. |
| ORA-19762 ORA-19762, 00000, “invalid file type %s” Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt. Action: Disable then re-enable change tracking. |
| ORA-19763 ORA-19763, 00000, “compatibility version %s is higher than maximum allowed: %s” Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade. Action: Disable then re-enable change tracking. |
| ORA-19764 ORA-19764, 00000, “database id %s does not match database id %s in control file” Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed. Action: Disable then re-enable change tracking. |
| ORA-19765 ORA-19765, 00000, “mount id %s does not match mount id %s in control file” Cause: The change tracking file does not match the one that was present when this instance was opened. In RAC, this error is most likely caused by having a change tracking file that cannot be consistently updated by all instances. Action: In RAC, ensure that the name specified for the change tracking file truly represents the same disk location for all nodes in the cluster. Disable then re-enable change tracking. |
| ORA-19766 ORA-19766, 00000, “missing CHANGE keyword” Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING |
| ORA-19767 ORA-19767, 00000, “missing TRACKING keyword” Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING |
| ORA-19768 ORA-19768, 00000, “USING clause only valid with ENABLE CHANGE TRACKING” Cause: The USING clause was specified with DISABLE CHANGE TRACKING Action: Correct the statement. |
| ORA-19769 ORA-19769, 00000, “missing FILE keyword” Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING |
| ORA-19770 ORA-19770, 00000, “invalid change tracking file name” Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given. Action: Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file. |
| ORA-19771 ORA-19771, 00000, “cannot rename change tracking file while database is open” Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file. Action: Close the database and reissue the command. |
| ORA-19772 ORA-19772, 00000, “change tracking file name exceeds limit of %s characters” Cause: The name specified for the change tracking file is too long. Action: Specify a shorter change tracking file name. |
| ORA-19773 ORA-19773, 00000, “must specify change tracking file name” Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set. Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter. |
| ORA-19776 ORA-19776, 00000, “PROXY restore to ASM disk group \”%s\” is not supported.” Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported. Action: Use a different file name and reissue RMAN command. |
| ORA-19777 ORA-19777, 00000, “ASM file %s cannot be proxy backed up.” Cause: An attempt was made to proxy backup a ASM file. This is not supported. Action: Use a different file name and reissue RMAN command. |
| ORA-19778 ORA-19778, 00000, “event to be in hot backup mode for given seconds” Document: NO Cause: N/A Action: Set to test shutdown during proxy backup |
| ORA-19779 ORA-19779, 00000, “could not obtain resilvering status for change tracking file” Cause: An error occurred while obtaining the mirror resilvering status of the change tracking file. Action: Refer to other error messages shown for additional details of the problem. |
| ORA-19800 ORA-19800, 00000, “Unable to initialize Oracle Managed Destination” Cause: The name given for an Oracle managed files destination cannot be initialized. Action: Check previous error messages for the reason Oracle was unable to initialize destination. Take corrective action, if possible, and retry the command or use a different name for destination. |
| ORA-19801 ORA-19801, 00000, “initialization parameter DB_RECOVERY_FILE_DEST is not set” Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command. |
| ORA-19802 ORA-19802, 00000, “cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE” Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use. Action: Correct the dependency parameter definitions and retry the command. |
| ORA-19803 ORA-19803, 00000, “Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 – %s)” Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid. Action: Specify a valid number within the range. |
| ORA-19804 ORA-19804, 00000, “cannot reclaim %s bytes disk space from %s limit” Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit. Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN. |
| ORA-19805 ORA-19805, 00000, “RECID %s of %s was deleted to reclaim disk space” Cause: The file described by the record in control file was deleted in order to reclaim disk space from flash recovery area for other operations. Action: Wait and try again. |
| ORA-19806 ORA-19806, 00000, “cannot make duplex backups in recovery area” Cause: Duplex backup to recovery area is not supported. Action: Remove duplex option and try again. |
| ORA-19808 ORA-19808, 00000, “recovery destination parameter mismatch” Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters. Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances. |
| ORA-19809 ORA-19809, 00000, “limit exceeded for recovery files” Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded. // Action:The error is accompanied by 19804. See message 19804 for further details. |
| ORA-19810 ORA-19810, 00000, “Cannot create temporary control file %s in DB_RECOVERY_FILE_DEST” Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST. Action: Retry the operation with a new file name. |
| ORA-19811 ORA-19811, 00000, “cannot have files in DB_RECOVERY_FILE_DEST with keep attributes” Cause: An attempt was made to 1) Create a backup piece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area. Action: Reissue RMAN command without KEEP options. |
| ORA-19812 ORA-19812, 00000, “cannot use %s without DB_RECOVERY_FILE_DEST” Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use. Action: Eliminate any incompatible parameter definitions. |
| ORA-19813 ORA-19813, 00000, “cannot have unavailable file %s in DB_RECOVERY_FILE_DEST” Cause: An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE. Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash. |
| ORA-19815 ORA-19815, 00000, “WARNING: %s of %s bytes is %s%% used, and has %s remaining bytes available.” Cause: DB_RECOVERY_FILE_DEST is running out of disk space. Action: One of the following: 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3. Consider changing RMAN retention policy. 4. Consider changing RMAN archived log deletion policy. 5. Delete files from recovery area using RMAN. |
| ORA-19816 ORA-19816, 00000, “WARNING: Files may exist in %s that are not known to database.” Cause: One of the following events caused this: 1. A database crash happened during file creation. 2. A backup control file was restored. 3. The control file was re-created. 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled. Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility. Do not use messages 19817; it is used for simulating lock failure Do not use messages 19818; it is used for space reclamation before backup Do not use messages 19819; it is used to disable clearing file name |
| ORA-19830 ORA-19830, 00000, “error from target database: \n%s” Cause: This error should be followed by other errors indicating the cause of the problem. Action: No action required. |
| ORA-19831 ORA-19831, 00000, “incompatible %s.%s.%s.%s DBMS_BACKUP_RESTORE package: %s.%s.%s.%s required” Cause: This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database. Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. |
| ORA-19851 ORA-19851, 00000, “OS error while managing auxiliary database %s” Cause: An OS error was received while managing the automatic auxiliary instance. Action: Check the accompanying errors. |
| ORA-19852 ORA-19852, 00000, “error creating services for auxiliary instance %s (error %s)” Cause: An error was received while managing the services of the auxiliary instance. Action: Check the accompanying errors. |
| ORA-19853 ORA-19853, 00000, “error preparing auxiliary instance %s (error %s)” Cause: An error was received while managing the automatic auxiliary instance. Action: Check the accompanying errors. |
| ORA-19854 ORA-19854, 00000, “error obtaining connect string from target” Cause: Could not obtain the connect string from the target database Action: Check the accompanying errors. |
| ORA-19860 ORA-19860, 00000, “piece validation cannot be performed more than once” Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation. Action: Do not attempt to validate the pieces more than once. |
| ORA-19861 ORA-19861, 00000, “additional backup pieces cannot be validated in this conversation” Cause: The user tried to add new pieces to the list of files being validated after the validation had already been // performed. In a validation conversation, the list can // only be validated once. Action: Add all the backup pieces to the list before validating, // or start a new validation conversation for the remaining pieces. |
| ORA-19862 ORA-19862, 00000, “backup pieces must be validated before accessing results” Cause: The user tried to get validation results for backup pieces before the pieces were actually validated. Action: Validate the pieces before trying to access the results. |
| ORA-19863 ORA-19863, 00000, “device block size %s is larger than max allowed: %s” Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup. Action: Change the device BLKSIZE to be smaller than the maximum allowed. |
| ORA-19864 ORA-19864, 00000, “%s” Cause: Action: |
| ORA-19865 ORA-19865, 00000, “Backup piece %s has no data” Cause: No data was returned for the specified backup piece. Action: This normally indicates a problem with the media management software which is linked with Oracle to provide backup and restore services. Contact the media management software vendor. |
| ORA-19866 ORA-19866, 00000, “error writing file header for datafile %s” Cause: During a block recovery, the header of the datafile could not be updated. Action: Contact Oracle Support Services. |
| ORA-19870 ORA-19870, 00000, “error while restoring backup piece %s” Cause: This error should be followed by other errors indicating the cause of the problem. Action: See other errors actions. |
| ORA-19873 ORA-19873, 00000, “cannot apply this backup section to file %s” *Cause RMAN cannot restore a multi-section backup to the indicated file, because this section is not a backup of this file, or the file was not prepared correctly for this restore. Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support. |
| ORA-19874 ORA-19874, 00000, “cannot finish multi-section restore to file %s” Cause: During a multi-section restore, the file being restored is not a file in which a multi-section restore is in progress. Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support. |
| ORA-19875 ORA-19875, 00000, “multi-section restore not complete for file %s” Cause: While completing a multi-section restore, it was found that all required sections for this file were not correctly applied. Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support. |
| ORA-19880 ORA-19880, 00000, “Corrupted space header for datafile %s, block %s” Cause: When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information. Action: The corrupt space header must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups. |
| ORA-19881 ORA-19881, 00000, “Corrupted space bitmap for datafile %s, block %s” Cause: When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information. Action: The corrupt space bitmap must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups. |
| ORA-19882 ORA-19882, 00000, “datafile %s checkpoint %s is ahead of space bitmap datafile %s checkpoint %s” Cause: When checkpointing the datafile containing the space bitmaps for the datafile being backed up in order to use Unused Block Optimization, the checkpoint of the datafile containing the space bitmaps did not advance. Action: Examine the trace and alert files for possible causes. Fix underlying problem to use Unused Block Optimization for datafile’s backup. |
| ORA-19883 ORA-19883, 00000, “Unused Block Optimization stopped for datafile %s” Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used. Action: See accompanying errors for appropiate action. |
| ORA-19900 ORA-19900, 00000, “RESETLOGS must be specified after recovery to new incarnation” Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command. Action: Open the database with the RESETLOGS option. |
| ORA-19901 ORA-19901, 00000, “database needs more recovery to create new incarnation” Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied. Action: Continue recovery. |
| ORA-19902 ORA-19902, 00000, “incarnation key %s not found” Cause: The specified incarnation was not found in the control file. Action: Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command. |
| ORA-19903 ORA-19903, 00000, “test recovery not allowed when recovering to new incarnation” Cause: Either a new incarnation was set using RMAN’s RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed. Action: Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery. |
| ORA-19904 ORA-19904, 00000, “test recovery not allowed for datafile %s” Cause: The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery. Action: Perform actual recovery. |
| ORA-19905 ORA-19905, 00000, “log_archive_format must contain %%s, %%t and %%r” Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique. Action: Add the missing format elements to log_archive_format. |
| ORA-19906 ORA-19906, 00000, “recovery target incarnation changed during recovery” Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files. Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when RESETLOGS is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN’s RESET DATABASE TO INCARNATION <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command. |
| ORA-19907 ORA-19907, 00000, “recovery time or SCN does not belong to recovered incarnation” Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested. Action: Either change the specified recovery time/SCN, or change the recovery destination using RMAN’s RESET DATABASE command. |
| ORA-19908 ORA-19908, 00000, “datafile %s has invalid checkpoint” Cause: The specified datafile has an invalid checkpoint. Action: Restore the datafile from a backup. |
| ORA-19909 ORA-19909, 00000, “datafile %s belongs to an orphan incarnation” Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information. Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup. |
| ORA-19910 ORA-19910, 00000, “can not change recovery target incarnation in control file” Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed. Action: Close the database then re-issue the command. |
| ORA-19911 ORA-19911, 00000, “datafile %s contains future changes at the incarnation boundary” Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation. Action: Use older backup of the file and then re-issue the command. |
| ORA-19912 ORA-19912, 00000, “cannot recover to target incarnation %s” Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation. Action: Restore the latest control file from the target incarnation and retry. |
| ORA-19913 ORA-19913, 00000, “unable to decrypt backup” Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open. Action: If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open. |
| ORA-19914 ORA-19914, 00000, “unable to encrypt backup” Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open. Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup. |
| ORA-19915 ORA-19915, 00000, “unable to encrypt pre-10.2 files” Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted. Action: Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted. |
| ORA-19916 ORA-19916, 00000, “%s” Cause: An error occurred when processing user request. Action: Do not use message 19917; it is used internally for testing purpose. Do not use message 19918; it is an internal event used by encryption. |
| ORA-19919 ORA-19919, 00000, “encrypted backups to tertiary storage require Oracle Secure Backup” Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel. Action: Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption. |
| ORA-19921 ORA-19921, 00000, “maximum number of %s rows exceeded” Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded. Action: Close some of existing and unused RMAN connections and sessions. |
| ORA-19922 ORA-19922, 00000, “there is no parent row with id %s and level %s” Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist. Action: This is an internal error. Contact Oracle Support. |
| ORA-19923 ORA-19923, 00000, “the session for row with id %s is not active” Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died. Action: This is an internal error. Contact Oracle Support. |
| ORA-19924 ORA-19924, 00000, “there are no row with id %s” Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don’t exist. Action: This is an internal error. Contact Oracle Support. |
| ORA-19925 ORA-19925, 00000, “Internal error while cleaning memory used by V$RMAN_STATUS view” Cause: Action: This is an internal error. Contact Oracle Support. |
| ORA-19926 ORA-19926, 1, “Database cannot be converted at this time” Cause: Another CONVERT DATABASE operation is already in progress. Action: Retry CONVERT DATABASE command later. |
| ORA-19927 ORA-19927, 1, “CONVERT DATABASE operation cannot proceed” Cause: An error occurred earlier during CONVERT DATABASE operation. Action: Retry CONVERT DATABASE command. |
| ORA-19930 ORA-19930, 00000, “file %s has invalid checkpoint SCN %s” Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed. Action: Ensure that the correct files are being specified for the catalog or backup operation. |
| ORA-19931 ORA-19931, 00000, “file %s has invalid creation SCN %s” Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed. Action: Ensure that the correct files are being specified for the catalog or backup operation. |
| ORA-19932 ORA-19932, 00000, “control file is not clone or standby” Cause: The operation failed because the control file was not mounted as standby or clone. Action: Mount the database as standby or clone and retry. |
| ORA-19941 ORA-19941, 00000, “invalid blocksize in cross platform datafile %s” Cause: Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read/write with compatibility 10.0 or greater at source database or datafile copy is corrupted. Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion. |
| ORA-19942 ORA-19942, 00000, “datafile copy %s not created with compatibility 10.0 or greater” Cause: The specified datafile copy to be converted at the target was not produced after making the tablespace in read/write mode with compatibility 10.0 or greater at the source database. Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion. |
| ORA-19943 ORA-19943, 00000, “The current database incarnation changed during backup” Cause: The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change: – The database was opened using ALTER DATABASE OPEN RESETLOGS statement. – RMAN command RESET DATABASE TO INCARNATION was issued. – If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation. Action: Re-try the backup. |
| ORA-19951 ORA-19951, 00000, “cannot modify control file until DBNEWID is completed” Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress. Action: Wait until NID completes before attempting the operation. |
| ORA-19952 ORA-19952, 00000, “database should be mounted exclusively” Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively. Action: Shut down the database and start it in exclusive mode. |
| ORA-19953 ORA-19953, 00000, “database should not be open” Cause: The database was open. To change the DBID, the database must be mounted exclusively. Action: Shut down the database and mount it in exclusive mode. |
| ORA-19954 ORA-19954, 00000, “control file is not current” Cause: The operation failed because a non-current, non-standby control file was mounted. Action: Make the control file current and retry. |
| ORA-19955 ORA-19955, 00000, “only one open thread is allowed to change the DBID” Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down. Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again. |
| ORA-19956 ORA-19956, 00000, “database should have no offline immediate datafiles” Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode. Action: Drop the datafiles or recover them and bring them online. |
| ORA-19957 ORA-19957, 00000, “database should have no datafiles in unknown state” Cause: The operation failed because the database had one or more datafiles that were in an unknown state. Action: Drop the datafiles or recover them and bring them online. |
| ORA-19958 ORA-19958, 00000, “potential deadlock involving DIAG process” Cause: DIAG requested a control file operation that may lead to a deadlock Action: Try last operation later when the control file is released |
| ORA-19960 ORA-19960, 00000, “Internal use only” Cause: NID usage Action: None |
| ORA-19999 ORA-19999, 00000, “skip_row procedure was called” Cause: The skip_row procedure was called which raises this error Action: Skip_row should only be called within a trigger or a procedure called by a trigger. |
| ORA-20000 ORA-20000, 00000, “%s” Cause: The stored procedure ‘raise_application_error’ was called which causes this error to be generated. Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information. |
| ORA-21000 ORA-21000, 00000, “error number argument to raise_application_error of %s%s is out of range” Cause: Action: Use an error number in the range of -20000 to -20999, inclusive. |
| ORA-21001 ORA-21001, 00000, “error number argument to raise_system_error of %s%s is out of range” Cause: Action: Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive. |
| ORA-21300 ORA-21300, 00000, “objects option not installed” Cause: The objects option is not installed at this site. object types and other object features are, therefore, unavailable. Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the objects option needs to be purchased. |
| ORA-21301 ORA-21301, 00000, “not initialized in object mode” Cause: This function requires the OCI process to be initialized in object mode. Action: Specify OCI_OBJECT mode when calling OCIInitialize(). |
| ORA-21500 ORA-21500, 00000, “internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]” Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition. Action: Report as a bug – the first argument is the internal error number. |
| ORA-21501 ORA-21501, 00000, “program could not allocate memory” Cause: The operating system has run out of memory. Action: Take action to make more memory available to the program. |
| ORA-21503 ORA-21503, 00000, “program terminated by fatal error” Cause: A program is in an unrecoverable error state. Action: Report as a bug. |
| ORA-21520 ORA-21520, 00000, “database server driver not installed” Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in. Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table. |
| ORA-21521 ORA-21521, 00000, “exceeded maximum number of connections in OCI (object mode only)” Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode. Action: Close some of existing and unused connections before opening more connections. |
| ORA-21522 ORA-21522, 00000, “attempted to use an invalid connection in OCI (object mode only)” Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated. Action: Ensure that the connection exists and is still valid. |
| ORA-21523 ORA-21523, 00000, “functionality not supported by the server (object mode only)” Cause: User attempted to use a functionality that the server does not support. Action: Upgrade the server |
| ORA-21524 ORA-21524, 00000, “object type mismatch” Cause: The object type of the object is different from what is specified. Action: Check the type of the object and correct it. |
| ORA-21525 ORA-21525, 00000, “attribute number or (collection element at index) %s violated its constraints” Cause: Attribute value or collection element value violated its constraint. Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element’s schema information. |
| ORA-21526 ORA-21526, 00000, “initialization failed” Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value. Action: Check that all NLS environment variables are well-formed. |
| ORA-21527 ORA-21527, 00000, “internal OMS driver error” Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions. Action: Report this as a bug to Oracle Support Services. |
| ORA-21560 ORA-21560, 00000, “argument %s is null, invalid, or out of range” Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB – 1), or when an invalid open mode is used to open a file, etc. Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value. |
| ORA-21561 ORA-21561, 00000, “OID generation failed” Cause: The handles passed in may not be valid Action: Check the validity of the env, svc handles |
| ORA-21600 ORA-21600, 00000, “path expression too long” Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression. Action: User should pass in the correct path expression to locate the attribute. |
| ORA-21601 ORA-21601, 00000, “attribute is not an object” Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type. Action: User should avoid performing such operation to an attribute of built-in type. |
| ORA-21602 ORA-21602, 00000, “operation does not support the specified typecode” Cause: The user attempts to perform an operation that does not support the specified typecode. Action: User should use the range of valid typecodes that are supported by this operation. |
| ORA-21603 ORA-21603, 00000, “property id [%s] is invalid” Cause: The specified property id is invalid. Action: User should specify a valid property id. Valid property ids are enumerated by OCIObjectPropId. |
| ORA-21604 ORA-21604, 00000, “property [%s] is not a property of transient or value instances” Cause: Trying to get a property which applies only to persistent objects. Action: User should check the lifetime and only get this property for persistent objects. |
| ORA-21605 ORA-21605, 00000, “property [%s] is not a property of value instances” Cause: Trying to get a property which applies only to persistent and transient objects. Action: User should check the lifetime and only get this property for persistent and transient objects. |
| ORA-21606 ORA-21606, 00000, “can not free this object” Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified. Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE |
| ORA-21607 ORA-21607, 00000, “memory cartridge service handle not initialized” Cause: Attempt to use the handle without initializing it. Action: Initialize the memory cartridge service handle. |
| ORA-21608 ORA-21608, 00000, “duration is invalid for this function” Cause: Attempt to use a duration not valid for this function. Action: Use a valid duration – a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory. |
| ORA-21609 ORA-21609, 00000, “memory being resized without being allocated first” Cause: Attempt to resize memory without allocating it first. Action: Allocate the memory first before resizing it. |
| ORA-21610 ORA-21610, 00000, “size [%s] is invalid” Cause: Attempt to resize memory with invalid size. Action: Pass in a valid size (must be a positive integer). |
| ORA-21611 ORA-21611, 00000, “key length [%s] is invalid” Cause: Attempt to use an invalid key length. Action: Key length is invalid and valid range is 0 to 64 |
| ORA-21612 ORA-21612, 00000, “key is already being used” Cause: Attempt to use a key that is already used. Action: Use a new key that is not yet being used. |
| ORA-21613 ORA-21613, 00000, “key does not exist” Cause: Attempt to use a non-existent key Action: Use a key that already exists. |
| ORA-21614 ORA-21614, 00000, “constraint violation for attribute number [%s]” Cause: Constraints on the attribute were violated Action: Correct the value (of the attribute) so that it satisfies constraints |
| ORA-21615 ORA-21615, 00000, “copy of an OTS (named or simple) instance failed” Cause: see following message Action: Check that no attribute value violates constraints. |
| ORA-21700 ORA-21700, 00000, “object does not exist or is marked for delete” Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete. Action: User needs to re-initialize the reference to reference an existent object or the user needs to unmark the object. |
| ORA-21701 ORA-21701, 00000, “attempt to flush objects to different servers” Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program. Action: User should avoid performing such operation. |
| ORA-21702 ORA-21702, 00000, “object is not instantiated or has been de-instantiated in cache” Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object. Action: User should check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired. |
| ORA-21703 ORA-21703, 00000, “cannot flush an object that is not modified” Cause: See the error message. Action: The object should not be flushed. |
| ORA-21704 ORA-21704, 00000, “cannot terminate cache or connection without flushing first” Cause: See the error message. Action: The transaction should be aborted or committed before terminating the cache or connection. |
| ORA-21705 ORA-21705, 00000, “service context is invalid” Cause: The service context that is supplied by the user is not valid. Action: User needs to establish the service context. |
| ORA-21706 ORA-21706, 00000, “duration does not exist or is invalid” Cause: The duration number that is supplied by the user is not valid. Action: User needs to establish the duration or use a correct predefined duration. |
| ORA-21707 ORA-21707, 00000, “pin duration is longer than allocation duration” Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters. Action: User should use a shorter pin duration or use the null duration. |
| ORA-21708 ORA-21708, 00000, “inappropriate operation on a transient object” Cause: User attempted to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking. Action: User should avoid performing such operation on a transient object. |
| ORA-21709 ORA-21709, 00000, “cannot refresh an object that has been modified” Cause: User attempted to refresh an object that has been marked for delete, update or insert (new). Action: User should unmark the object before refreshing it. |
| ORA-21710 ORA-21710, 00000, “argument is expecting a valid memory address of an object” Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object. Action: User should pass in a valid memory address of an object to the function. |
| ORA-21779 ORA-21779, 00000, “duration not active” Cause: User is trying to use a duration that has been terminated. Action: User should avoid performing such operation. |
| ORA-21780 ORA-21780, 00000, “Maximum number of object durations exceeded.” Cause: This typically happens if there is infinite recursion in the PL/SQL function that is being executed. Action: User should alter the recursion condition in order to prevent infinite recursion. |
| ORA-22053 ORA-22053, 00000, “overflow error” Cause: This operation’s result is above the range of Oracle number. Action: Decrease the input value(s) so that the result is in the range of Oracle number. |
| ORA-22054 ORA-22054, 00000, “underflow error” Cause: This operation’s result is below the range of Oracle number. Action: Increase the input value(s) so that the result is in the range of Oracle number. |
| ORA-22055 ORA-22055, 00000, “unknown sign flag value [%s]” Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED. Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag. |
| ORA-22056 ORA-22056, 00000, “value [%s] is divided by zero” Cause: Given value is divied by zero. Action: Modify divisor value to be non-zero. |
| ORA-22057 ORA-22057, 00000, “bad integer length [%s]” Cause: The length of the integer (ie number of bytes) to be converted to or from an Oracle number is invalid. Action: Use integer length 1, 2, 4 or 8 bytes only. |
| ORA-22059 ORA-22059, 00000, “buffer size [%s] is too small – [%s] is needed” Cause: The buffer to hold the resulting text string is too small. Action: Provide a buffer of the required size. |
| ORA-22060 ORA-22060, 00000, “argument [%s] is an invalid or uninitialized number” Cause: An invalid or uninitialized number is passed in. Action: Use a valid number. To initialize number call OCINumberSetZero(). |
| ORA-22061 ORA-22061, 00000, “invalid format text [%s]” Cause: The numeric format string for converting characters to or from an Oracle number is invalid. Action: Use valid format string as documented in OCI Programmer’s Guide. |
| ORA-22062 ORA-22062, 00000, “invalid input string [%s]” Cause: The text string for converting to numbers is invalid. Action: Use a valid input string as documented in OCI Programmer’s Guide. |
| ORA-22063 ORA-22063, 00000, “reading negative value [%s] as unsigned” Cause: Attempt to convert a negative number to an unsigned integer. Action: Use the sign flag ORLTSB to convert a signed number. |
| ORA-22064 ORA-22064, 00000, “invalid NLS parameter string [%s]” Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid. Action: Use valid format string as documented in OCI Programmer’s Guide. |
| ORA-22065 ORA-22065, 00000, “number to text translation for the given format causes overflow” Cause: Rounding done due to the given string format causes overflow. Action: Change the string format such that overflow does not occur. |
| ORA-22130 ORA-22130, 00000, “buffer size [%s] is less than the required size [%s]” Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small. Action: Provide a buffer of the required size. |
| ORA-22131 ORA-22131, 00000, “hexadecimal string length is zero” Cause: The given hexadecimal string length must be greater than zero. Action: Specify a length greater than zero. |
| ORA-22132 ORA-22132, 00000, “hexadecimal string does not correspond to a valid REF” Cause: The given hexadecimal string is invalid. Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex(). |
| ORA-22140 ORA-22140, 00000, “given size [%s] must be in the range of 0 to [%s]” Cause: The given resize size is invalid. Action: Ensure that the given size is in the required range. |
| ORA-22141 ORA-22141, 00000, “given size [%s] must be even in UTF-16 environment” Cause: The given resize size is odd. In a UTF-16 environment, all characters are 2 bytes in length. Action: Ensure that the given size is even. |
| ORA-22150 ORA-22150, 00000, “variable-length array has not been initialized” Cause: An un-initialized variable-length array is being operated upon. Action: Initialize the variable-length array prior to calling this function. |
| ORA-22151 ORA-22151, 00000, “cannot resize non-zero variable-length array to zero elements” Cause: Trying to resize a non-zero variable-length array to 0 elements. Action: Specify a non-zero size. |
| ORA-22152 ORA-22152, 00000, “destination variable-length array is not initialized” Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized. Action: Initialize the destination variable-length array prior to calling this function. |
| ORA-22153 ORA-22153, 00000, “source variable-length array is not initialized” Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized. Action: Initialize the destination variable-length array prior to calling this function. |
| ORA-22160 ORA-22160, 00000, “element at index [%s] does not exist” Cause: Collection element at the given index does not exist. Action: Specify the index of an element which exists. |
| ORA-22161 ORA-22161, 00000, “type code [%s] is not valid” Cause: Given type code is not valid. Action: Use one of the typecodes enumerated in OCITypeCode. |
| ORA-22162 ORA-22162, 00000, “element at index [%s] has been previously deleted” Cause: Trying to delete a non-existent collection element. Action: Check for the existence of the element prior to calling this function. |
| ORA-22163 ORA-22163, 00000, “left hand and right hand side collections are not of same type” Cause: Left hand and right side collections are not of same type. Action: Ensure that the same collection type is passed for both left hand and right hand side of this function. |
| ORA-22164 ORA-22164, 00000, “delete element operation is not allowed for variable-length array” Cause: Trying to delete an element of a variable-length array. Action: Ensure that the collection is not a variable-length array prior to calling this function. |
| ORA-22165 ORA-22165, 00000, “given index [%s] must be in the range of [%s] to [%s]” Cause: Given index is not in the required range. Action: Ensure that the given index is in the required range. |
| ORA-22166 ORA-22166, 00000, “collection is empty” Cause: Given collection is empty. Action: Test if collection is empty prior to invoking this function. |
| ORA-22167 ORA-22167, 00000, “given trim size [%s] must be less than or equal to [%s]” Cause: Given trim size is greater than the current collection size. Action: Ensure that the given size is less than or equal to the collection size prior to calling this function. |
| ORA-22275 ORA-22275, 00000, “invalid LOB locator specified” Cause: There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body — LOBs in trigger bodies are read only; (5) the locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator; (6) the locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator; Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2),(3), (5) and (6)pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value. |
| ORA-22276 ORA-22276, 00000, “invalid locator for LOB buffering” Cause: There are several causes: (1) the locator was never enabled for buffering (2) it is not an updated locator but is being used for a write/flush operation Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation |
| ORA-22277 ORA-22277, 00000, “cannot use two different locators to modify the same LOB” Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators. Action: When using LOB buffering, modify the LOB through one LOB locator only. |
| ORA-22278 ORA-22278, 00000, “must update the LOB only through the LOB buffers” Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed. Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command. |
| ORA-22279 ORA-22279, 00000, “cannot perform operation with LOB buffering enabled” Cause: The operation attempted is not allowed when LOB buffering is enabled. Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command. |
| ORA-22280 ORA-22280, 00000, “no more buffers available for operation” Cause: There are two causes: (1) All buffers in the buffer pool have been used up by previous operations (2) Attempt to flush a LOB without any previous buffered update operations. Action: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers. |
| ORA-22281 ORA-22281, 00000, “cannot perform operation with an updated locator” Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem. Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command. |
| ORA-22282 ORA-22282, 00000, “non-contiguous append to a buffering enabled LOB not allowed” Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB. Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation. |
| ORA-22283 ORA-22283, 00000, “filename contains characters that refer to parent directory” Cause: Filename contains a path “../” which references a parent directory Action: Ensure that the filename does not contain characters which reference a parent directory. |
| ORA-22285 ORA-22285, 00000, “non-existent directory or file for %s operation” Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist. Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct. |
| ORA-22286 ORA-22286, 00000, “insufficient privileges on file or directory to perform %s operation” Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation. Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file. |
| ORA-22287 ORA-22287, 00000, “invalid or modified directory occurred during %s operation” Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the DBA since the last access. Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occured, then close the file and retry the operation with a valid directory alias as modified by your DBA. Oracle recommends that directories should be modified only during quiescent periods. |
| ORA-22288 ORA-22288, 00000, “file or LOB operation %s failed\n%s” Cause: The operation attempted on the file or LOB failed. Action: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the DBA. |
| ORA-22289 ORA-22289, 00000, “cannot perform %s operation on an unopened file or LOB” Cause: The file or LOB is not open for the required operation to be performed. Action: Precede the current operation with a successful open operation on the file or LOB. |
| ORA-22290 ORA-22290, 00000, “operation would exceed the maximum number of opened files or LOBs” Cause: The number of open files or LOBs has reached the maximum limit. Action: Close some of the opened files or LOBs and retry the operation. |
| ORA-22291 ORA-22291, 00000, “Open LOBs exist at transaction commit time” Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time. Action: Close the LOBs before committing the transaction. |
| ORA-22292 ORA-22292, 00000, “Cannot open a LOB in read-write mode without a transaction” Cause: An attempt was made to open a LOB in read-write mode before a transaction was started. |
| ORA-22293 ORA-22293, 00000, “LOB already opened in the same transaction” Cause: An attempt was made to open a LOB that already is open in this transaction. Action: Close the LOB before attempting to re-open it. |
| ORA-22294 ORA-22294, 00000, “cannot update a LOB opened in read-only mode” Cause: An attempt was made to write to or update a LOB opened in read-only mode. Action: Close the LOB and re-open it in read-write mode before attempting to write to or update the LOB. |
| ORA-22295 ORA-22295, 00000, “cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement” Cause: An attempt was made to bind data more than 4000 bytes of data to both LOB and LONG columns in the same insert or update statement. You can bind more than 4000 bytes of data to either a LONG column or one or more LOB columns but not both. Action: Bind more than 4000 bytes of data to either the LONG column or one or more LOB columns but not both. |
| ORA-22296 ORA-22296, 00000, “invalid ALTER TABLE option for conversion of LONG datatype to LOB” Cause: An attempt was made to specify ALTER TABLE options which are disallowed during conversion of LONG datatype to LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to LOB are the default clause and LOB storage clause for the column being converted to LOB. Action: Remove the disallowed options. |
| ORA-22297 ORA-22297, 00000, “warning: Open LOBs exist at transaction commit time” Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time. Action: This is just a warning. The transaction was commited successfully, but any domain or functional indexes on the open LOBs were not updated. You may want to rebuild those indexes. |
| ORA-22298 ORA-22298, 00000, “length of directory alias name or file name too long” Cause: The length of directory alias name or file name given for a BFILE is too long. Action: Use a shorter alias or file name. |
| ORA-22299 ORA-22299, 00000, “Synonym compile without validating base object” Document: No Cause: Action: No validation of the base object. |
| ORA-22300 ORA-22300, 00000, “acquiring DML lock in WAIT mode on table that is locked by KGL or KQR” Document: NO Cause: An attempt was made to acquire a DML lock in WAIT mode on a table that is locked by KGL or KQR. Action: This is just a warning. The transaction was commited successfully, but any domain or functional indexes on the open LOBs were not updated. You may want to rebuild those indexes. |
| ORA-22303 ORA-22303, 00000, “type \”%s\”.\”%s\” not found” Cause: The user is trying to obtain information for a type that cannot be found. Action: Check that the schema is correct and that the type has been created correctly. |
| ORA-22304 ORA-22304, 00000, “input type is not an object type” Cause: The user is trying to obtain the supertype information for a non-object type. Action: Pass in only an object type. |
| ORA-22305 ORA-22305, 00000, “attribute/method/parameter \”%s\” not found” Cause: Type element with the given name is not found in the type. Action: Check to make sure that the type element exists. |
| ORA-22306 ORA-22306, 00000, “type \”%s\”.\”%s\” already exists” Cause: The user is trying to create a type that already exists. Action: Check to make sure that the type has not been created prior to this. |
| ORA-22307 ORA-22307, 00000, “operation must be on a user-defined type” Cause: attempt to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type. Action: Check to make sure that only user-defined types are being operated on. |
| ORA-22308 ORA-22308, 00000, “operation not allowed on evolved type” Cause: An attempt was made to replace a type whose attribute definition been been altered. Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE REPLACE. |
| ORA-22309 ORA-22309, 00000, “attribute with name \”%s\” already exists” Cause: The user is attempting to create an object type where more than one attributes have the same name. Action: Check to make sure that all attribute names are unique. |
| ORA-22310 ORA-22310, 00000, “ALTER TYPE error. Refer to table \”%s\”.\”%s\” for errors” Cause: An invalid alter type statement was submitted. Action: Correct the errors listed in specified table and resubmit statement. |
| ORA-22311 ORA-22311, 00000, “type for attribute \”%s\” does not exist” Cause: The type of the attribute does not exist. Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute’s type in the DDL transaction. |
| ORA-22312 ORA-22312, 00000, “must specify either CASCADE or INVALIDATE option” Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option. Action: Resubmit the statement with either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade the type change to dependent types and tables; otherwise, specify INVALIDATE to invalidate all dependents. |
| ORA-22313 ORA-22313, 00000, “cannot use two versions of the same type \”%s\”" Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type. Action: Check that the libraries being linked with this application and use the same versions of the type. |
| ORA-22314 ORA-22314, 00000, “method information mismatch in ALTER TYPE” Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported. Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods. |
| ORA-22315 ORA-22315, 00000, “type \”%s\” does not contain a map or order function” Cause: The input type does not contain a map or order function so one cannot be returned. Action: Add a map or order function to the type or catch this error. |
| ORA-22316 ORA-22316, 00000, “input type is not a collection type” Cause: The user is trying to obtain information for collection types on a non-named collection type. Action: Use a named collection type for the function. |
| ORA-22317 ORA-22317, 00000, “typecode %d is not legal as a number type” Cause: The user is trying to use a number typecode that is not valid. Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL. |
| ORA-22318 ORA-22318, 00000, “input type is not an array type” Cause: The user is trying to obtain the number of elements for a non-array type. Action: Pass in only a named collection type which is an array. |
| ORA-22319 ORA-22319, 00000, “type attribute information altered in ALTER TYPE” Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added. Action: Check that all type alterations are legal. |
| ORA-22320 ORA-22320, 00000, “missing user version string” Cause: The VERSION option is specified without a user version string. Action: Resubmit the statement with the version string following the VERSION keyword. |
| ORA-22321 ORA-22321, 00000, “method does not return any result” Cause: OCITypeResult() was called on a method that does not return any results. Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly. |
| ORA-22322 ORA-22322, 00000, “error table \”%s\”.\”%s\” has incorrect structure” Cause: The specified error table does not have the expected table structure. Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table, then resubmit the statement using the new error table. |
| ORA-22323 ORA-22323, 00000, “error table \”%s\”.\”%s\” does not exist” Cause: The error table does not exist. Action: Resubmit the statement with a correct error table name. |
| ORA-22324 ORA-22324, 00000, “altered type has compilation errors” Cause: The use of the ALTER TYPE statement caused a compilation error. Action: Correct the error reported and resubmit the statement. |
| ORA-22325 ORA-22325, 00000, “event for create type with user version string” Cause: Action: |
| ORA-22326 ORA-22326, 00000, “cannot change a type to FINAL if it has subtypes” Cause: An attempt was made to change a type with subtypes to FINAL. Action: Drop all subtypes of the target type before changing it to FINAL. |
| ORA-22327 ORA-22327, 00000, “cannot change a type to NOT INSTANTIABLE if it has dependent tables” Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE. Action: Drop all dependent tables of the target type and resubmit the statement. |
| ORA-22328 ORA-22328, 00000, “object \”%s\”.\”%s\” has errors.\n%s” Cause: Altering the target type causes errors in its dependent object. Action: Correct the problem in the dependent object and resubmit the statement. |
| ORA-22329 ORA-22329, 00000, “cannot alter a non-object type” Cause: An attempt was made to execute ALTER TYPE on a non-object type. Action: Drop the non-object type first, then re-create it as an object type. |
| ORA-22330 ORA-22330, 00000, “cannot alter a type that is not valid” Cause: An attempt was made to perform ALTER TYPE on an invalid type. Action: Use the CREATE OR REPLACE TYPE command to modify the type. |
| ORA-22331 ORA-22331, 00000, “cannot alter an incomplete type” Cause: An attempt was made to perform ALTER TYPE on an incomplete type. Action: Use CREATE TYPE to completely define the original type before executing the ALTER TYPE. |
| ORA-22332 ORA-22332, 00000, “a dependent object in schema \”%s\” has errors.\n%s” Cause: Altering the target type causes errors in its dependent object. Action: Correct the problem in the dependent object and resubmit the statement. |
| ORA-22333 ORA-22333, 00000, “cannot reset type \”%s\”.\”%s\” due to invalid dependent types and tables” Cause: An attempt was made to reset the type version with invalid dependent types and tables. Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA to upgrade all the dependent tables then resubmit the statement. |
| ORA-22334 ORA-22334, 00000, “cannot reset type \”%s\”.\”%s\”. Dependent tables must be upgraded to latest version” Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version. Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement. |
| ORA-22335 ORA-22335, 00000, “The client cannot work with an altered type” Cause: A pre 8.2 client has requested a type that has been altered on the server. Action: Only 8.2 or higher clients could access altered types |
| ORA-22336 ORA-22336, 00000, “table contained 8.0 image format, must specify INCLUDING DATA” Cause: One of the following: 1) An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified. 2) An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified. Action: Resubmit the statement with INCLUDING DATA option. |
| ORA-22337 ORA-22337, 00000, “the type of accessed object has been evolved” Cause: The type of the accessed object has been altered and the client’s object is based on an earlier type definition. Action: The user needs to exit application and modify application to accommodate the type change. From SQL/PLUS, reconnect and resubmit statement. |
| ORA-22338 ORA-22338, 00000, “must specify CASCADE INCLUDING DATA when altering the final property” Cause: An attempt was made to alter the final property of a type with dependent table(s) without specifying the CASCADE INCLUDING DATA . option. Action: Resubmit the statement with the CASCADE INCLUDING DATA option. |
| ORA-22339 ORA-22339, 00000, “cannot alter to not final since its attribute column is substitutable” Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable. Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then resubmit the ALTER TYPE statement. |
| ORA-22340 ORA-22340, 00000, “cannot %s type \”%s\”.\”%s\”. Dependent tables must be upgraded to latest version” Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version. Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement. |
| ORA-22341 ORA-22341, 00000, “cannot assign supertype instance to subtype” Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance. Action: Make sure the runtime type of the source of the assignment or copy is the same type as the destination or is a subtype of the destination type |
| ORA-22342 ORA-22342, 00000, “dependent VARRAY column exceeds the maximum inline column size” Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created. Action: Specify the VARRAY column to be stored as LOB at the table level when the table is created. |
| ORA-22343 ORA-22343, 00000, “Compilation error for type invalidated by ALTER TYPE” Cause: Compilation failed for a type which was invalidated by ALTER TYPE. We throw this error and rollback the compilation effort so that the user may be able to fix whatever is causing the compilation error and try again. It is important that we do not chnage status here and modify the dependency information as this will affect the creation of versions. Action: Check what is causing teh compilation error and correct it and try again. |
| ORA-22344 ORA-22344, 00000, “can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change” Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change. Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change. |
| ORA-22345 ORA-22345, 00000, “recompile type %s.%s before attempting this operation” Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid Action: Recompile the specified type and retry the operation |
| ORA-22346 ORA-22346, 00000, “Type has cyclical dependency. Should use CASCADE option” Cause: An attempt was made to alter a type which has a cyclical dependency, with invalidate option. Action: Give CASCADE option instead of INVALIDATE |
| ORA-22347 ORA-22347, 00000, “No changes to type specified for ALTER TYPE” Cause: The ALTER TYPE does not contain any changes to the type. Action: If any change is required for the type, modify the ALTER TYPE to specify the change. Else no need for the ALTER. |
| ORA-22369 ORA-22369, 00000, “invalid parameter encountered in method %s” Cause: An invalid parameter is being passed to this method of SYS.AnyType ,SYS.AnyData or SYS.AnyDataSet Action: Check the parameters being passed to this method and make sure that the parameters are allowed. |
| ORA-22370 ORA-22370, 00000, “incorrect usage of method %s” Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately. Action: Check the documentation for correct usage. |
| ORA-22371 ORA-22371, 00000, “Table contains data of type %s.%s, version %s, which does not exist” Cause: Some of the older versions of the type may have got deleted because one or more of the types it were referencing was dropped. Action: These data could not be read as the whole ADT. Read the data at individual scalar attribute level. |
| ORA-22372 ORA-22372, 00000, “Event for type dictionary upgrade” Cause: This is an internally used event for type dictionary upgrades from 8.0 to 8.1. Action: None. |
| ORA-22373 ORA-22373, 00000, “Older version hashcode encountered” Cause: An older version HC is encountered when creating a new version hahscode. Currently this is handled internally. Action: None. |
| ORA-22600 ORA-22600, 00000, “encountered 8.0.2 (Beta) VARRAY data that cannot be processed” Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data. Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data. There is no provided script or tool to help automate this conversion. |
| ORA-22601 ORA-22601, 00000, “pickler TDS context [%s] is not initialized” Cause: Attempt to use the pickler TDS context without initializing it. Action: Use OCIPicklerTdsCtxInit to initialize the context. |
| ORA-22602 ORA-22602, 00000, “pickler TDS handle [%s] is not well-formed” Cause: Attempt to use the pickler TDS handle without initializing/ constructing it. Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed. |
| ORA-22603 ORA-22603, 00000, “cannot add an attribute to the already generated TDS handle” Cause: Attempt to add an attribute to the already constructed TDS. Action: Use a TDS handle that is initialized but not yet constructed. |
| ORA-22604 ORA-22604, 00000, “TDS handle already generated” Cause: Attempt to geneate TDS that is already genearated. Action: Use a TDS handle that is initialized but not yet generated. |
| ORA-22605 ORA-22605, 00000, “FDO handle [%s] is not initialized” Cause: Attempt to use an uninitialized FDO handle. Action: Use OCIPicklerFdoInit to initialize FDO handle”. |
| ORA-22606 ORA-22606, 00000, “pickler image handle [%s] is not well-formed” Cause: Attempt to use the image handle without initializing/ constructing it. Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed. |
| ORA-22607 ORA-22607, 00000, “image handle already generated” Cause: Attempt to geneate image that is already genearated. Action: Use a image handle that is initialized but not yet generated. |
| ORA-22608 ORA-22608, 00000, “cannot add an attribute to the already generated image handle” Cause: Attempt to add an attribute to the already constructed image. Action: Use a image handle that is initialized but not yet constructed. |
| ORA-22609 ORA-22609, 00000, “error %s during initialization of FDO” Cause: Error during FDO initialization. Action: Take an action based on the specified error. |
| ORA-22610 ORA-22610, 00000, “error while adding a scalar to the image handle” Cause: Error while adding a scalar attribute to the image handle Action: Make sure image handle is initialized before adding scalar |
| ORA-22611 ORA-22611, 00000, “TDS version is not recognized” Cause: Incorrect TDS handle is passed Action: Make sure image handle is initialized with the correct TDS |
| ORA-22612 ORA-22612, 00000, “TDS does not describe a collection TDS” Cause: collection construct/access routines are being on an image but // the TDS does not describe that a collection TDS Action: Make sure a collection TDS is used before invoking collection // routines on the image handle |
| ORA-22613 ORA-22613, 00000, “buflen does not match the size of the scalar” Cause: buflen is incorrect Action: Make sure buflen is correct and matches the size of the scalar |
| ORA-22614 ORA-22614, 00000, “error while construction the collection in the image” Cause: Error during the construction of collection Action: Make sure image handle is initialized and // OCIPicklerImageCollBegin is called to begin collection |
| ORA-22615 ORA-22615, 00000, “attribute is not a collection” Cause: collection routine is invoked upon a non-collection attribute Action: Make sure attribute is a collection |
| ORA-22616 ORA-22616, 00000, “image is not of Oracle 8.1 format” Cause: The function being invoked is applicable only for 8.1 images Action: Make sure image is of 8.1 format |
| ORA-22617 ORA-22617, 00000, “error while accessing the image handle collection” Cause: Error while accessing collection in the image handle Action: Make sure image is initialized correctly and the collection // is constructed properly. |
| ORA-22618 ORA-22618, 00000, “attribute is a BAD NULL in the image handle” Cause: attribute in question is probably the attribute of a null // embedded image Action: Make sure attribute number is valid or it is NULL or // NOT NULL. |
| ORA-22619 ORA-22619, 00000, “all collection elements have already been accessed” Cause: Accessing a collection element after all the collection // elements are already accessed Action: This function should not be invoked any more. |
| ORA-22620 ORA-22620, 00000, “buffer size too small to hold the value” Cause: Buffer size is not enough to hold the value. Most likely // while doing the character set conversion, a bigger buffer // is needed. Action: Pass in a bigger buffer. If the client character set format // differs from that of server, doing the conversion may result // in 4X expansion. |
| ORA-22621 ORA-22621, 00000, “error transfering an object from the agent” Cause: Any error returned from pickler routines on the agent side. Action: Contact Oracle Support. |
| ORA-22625 ORA-22625, 00000, “OCIAnyData is not well-formed” Cause: Attempt to use the OCIAnyData without initializing constructing it. Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert to do the construction. MAke sure it is properly constructed before accessing attributes. |
| ORA-22626 ORA-22626, 00000, “Type Mismatch while constructing or accessing OCIAnyData” Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute. Action: Make sure the type supplied matches the type of object to to be constucted or accessed. |
| ORA-22627 ORA-22627, 00000, “tc [%s] must be that of object/varray/nested table” Cause: Type code is not that of object/varray/nested table Action: Make sure the type code is OCI_TYPECODE_OBJECT or OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE |
| ORA-22628 ORA-22628, 00000, “OCIAnyData already constructed” Cause: Attempt to add attributes to OCIAnyData that is already constructed. Action: Use the OCIAnyData that is initialized but not yet constructed. |
| ORA-22629 ORA-22629, 00000, “OCIAnyData is null” Cause: Attempting an operation that is not valid on null OCIAnyData Action: Make sure OCIAnyData is not null. |
| ORA-22630 ORA-22630, 00000, “attribute [%s] is null or it is not well-formed” Cause: Passing an attribute that is null or not well-formed Action: Make sure the attribute is not null or is well-formed. |
| ORA-22631 ORA-22631, 00000, “attribute [%s] is is not well-formed or does not match the type” Cause: Passing an attribute that is not well-formed or does not match the input type. Action: Make sure the attribute is well-formed and matches the type specified. |
| ORA-22632 ORA-22632, 00000, “AnyDataSet parameter is not valid for the current operation” Cause: The AnyDataSet parameter is null or it is somehow invalid for the current operation. Action: Check the documentation for the current operation. |
| ORA-22633 ORA-22633, 00000, “Error freeing AnyDataSet” Cause: AnyDataSet that is passed in may not be valid. Action: Check all the AnyDataSet parameters. |
| ORA-22634 ORA-22634, 00000, “Error adding new instance to AnyDataSet” Cause: Current instance in the AnyDataSet has not been fully constructed. Action: Make sure that the current instance is fully constructed before adding new instance. |
| ORA-22700 ORA-22700, 00000, “object access trace event number” Cause: N/A Action: If the trace event number is set to a level greater than 0 then all the dangling REFs are dumped. *Note: THIS IS NOT A USER ERROR NUMBER/ |