

CREATE TABLE errors
(
    code                             VARCHAR2 (9)                    NOT NULL
  , description                      VARCHAR2 (200)                  
  , cause                            VARCHAR2 (4000)                 
  , action                           VARCHAR2 (4000)                 
)
;

CREATE UNIQUE INDEX pk_errorcode ON errors
(
    code
)
;

ALTER TABLE errors ADD CONSTRAINT pk_errorcode PRIMARY KEY
(
    code
)
NOT DEFERRABLE
INITIALLY IMMEDIATE
ENABLE NOVALIDATE;

INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00000',' normal, successful completion',' An operation has completed normally, having met no exceptions.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00001',' unique constraint (string.string) violated',' An UPDATE or INSERT statement attempted to insert a duplicate key.',' Either remove the unique restriction or do not insert the key.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00017',' session requested to set trace event',' The current session was requested to set a trace event by another session.',' This is used internally; no action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00018',' maximum number of sessions exceeded',' All session state objects are in use.',' Increase the value of the SESSIONS initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00019',' maximum number of session licenses exceeded',' All licenses are in use.',' Increase the value of the LICENSE MAX SESSIONS initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00020',' maximum number of processes (string) exceeded',' All process state objects are in use.',' Increase the value of the PROCESSES initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00021',' session attached to some other process; cannot switch session',' The user session is currently used by others.',' Do not switch to a session attached to some other process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00022',' invalid session ID; access denied',' Either the session specified does not exist or the caller does not have the privilege to access it.',' Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00023',' session references process private memory; cannot detach session',' An attempt was made to detach the current session when it contains references to process private memory.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00024',' logins from more than one process not allowed in single-process mode',' An attempt was made to log in more than once from different processes for Oracle started in single-process mode.',' Log off from the other process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00025',' failed to allocate string',' An application failed because Oracle ran out of memory.',' Restart Oracle with a larger SGA heap.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00026',' missing or invalid session ID',' The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified.',' Retry the command with a valid session ID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00027',' cannot kill current session',' An attempt was made to use ALTER SYSTEM KILL SESSION to kill the current session.',' If it is necessary to kill the current session, do so from another session.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00028',' your session has been killed',' A privileged user killed the session and it is no longer logged in to the database.',' Contact the database administrator. The administrator may be attempting to perform an operation that requires users to be logged out. When the database administrator announces that the database is available, log in and resume work.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00029',' session is not a user session',' The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started.',' Retry the command with a valid session ID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00030',' User session ID does not exist.',' The user session ID no longer exists, probably because the session was logged out.',' Use a valid session ID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00031',' session marked for kill',' The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately because the session is involved in a non-interruptible operation (for example, rolling back a transaction or being blocked by a network operation). The session has been marked to be killed as soon as possible after the current operation is done.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00032',' invalid session migration password',' The session migration password specified in a session creation call was invalid (probably too long).',' Retry with a valid password (less than 30 characters).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00033',' current session has empty migration password',' An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.',' Create the session with a non-empty migration password.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00034',' cannot string in current PL/SQL session',' 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 a ALTER SESSION DISABLE COMMIT IN PROCEDURE statement.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00035',' LICENSE_MAX_USERS cannot be less than current number of users',' Specified values for LICENSE_MAX_USERS is less than the current number of users.',' Check the license limit and drop extra users or purchase more licenses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00036',' maximum number of recursive SQL levels (string) exceeded',' An attempt was made to go more than the specified number of recursive SQL levels.',' Remove the recursive SQL, possibly a recursive trigger.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00037',' cannot switch to a session belonging to a different server group',' An attempt was made to switch to a session in a different server group. This is not allowed.',' Make sure the server switches to a session that belongs to its server group.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00038',' Cannot create session: server group belongs to another user',' An attempt was made to create a non-migratable session in a server group that is owned by a different user.',' 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 log 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00050',' operating system error occurred while obtaining an enqueue',' 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.',' Look up the operating system error in your system documentation and perform the needed action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00051',' timeout occurred while waiting for a resource',' This message is usually caused by an instance that has terminated abnormally.',' Restart any non-recovered instances.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00052',' maximum number of enqueue resources (string) exceeded',' Ran out of enqueue resources.',' Increase the value of the ENQUEUE_RESOURCES initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00053',' maximum number of enqueues exceeded',' Ran out of enqueue state objects.',' Increase the value of the ENQUEUES initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00054',' resource busy and acquire with NOWAIT specified',' The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.',' Try the command after a few minutes or enter the command without the NOWAIT keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00055',' maximum number of DML locks exceeded',' Ran out of DML lock state objects.',' Increase the value of the DML_LOCKS initialization parameter and restart Oracle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00056',' DDL lock on object ''string.string'' is already held in an incompatible mode',' The attempted lock is incompatible with the DDL lock already held on the object. This happens if you attempt to drop a table that has parse locks.',' Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00057',' maximum number of temporary table locks exceeded',' The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.',' Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and restart Oracle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00058',' DB_BLOCK_SIZE must be string to mount this database (not string)',' The value of the DB_BLOCK_SIZE initialization parameter used to start this database does not match the value used when that database was created. Potential reasons for this mismatch are:',' For one of the above causes, either:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00059',' maximum number of DB_FILES exceeded',' The value of the DB_FILES initialization parameter was exceeded.',' Increase the value of the DB_FILES parameter and restart Oracle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00060',' deadlock detected while waiting for resource',' Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.',' Either:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00061',' another instance has a different DML_LOCKS setting',' The shared instance being started is using DML locks, and the running instances are not, or vice-versa.',' Either:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00062',' DML full-table lock cannot be acquired; DML_LOCKS is 0',' The instance was started with the value of DML_LOCKS set to zero, and the statement being executed needs a full-table lock (S, X, or SSX).',' Restart the instance with DML_LOCKS not equal to zero, and re-execute the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00063',' maximum number of LOG_FILES exceeded',' The value of the LOG_FILES initialization parameter was exceeded.',' Increase the value of the LOG_FILES initialization parameter and restart Oracle. The value of the parameter needs to be as large as the highest number of log files that currently exist rather than just the count of logs that exist.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00064',' object is too large to allocate on this O/S (string,string)',' An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.',' Reduce the value of the initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00065',' initialization of FIXED_DATE failed',' The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.',' Make sure the initialization parameter is in the correct date format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00066',' LOG_FILES is string but needs to be string to be compatible',' The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.',' Change the value of the LOG_FILES initialization parameter to be compatible.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00067',' invalid value string for parameter string; must be at least string',' The value for the initialization parameter is invalid.',' Choose a value as indicated by the message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00068',' invalid value string for parameter string, must be between string and string',' The value for the initialization parameter is invalid.',' Choose a value as indicated by the message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00069',' cannot acquire lock -- table locks disabled for string',' 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.',' Use the ALTER TABLE... ENABLE TABLE LOCK command, and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00070',' command string is not valid',' An invalid debugger command was specified.',' Type HELP to see the list of available commands.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00071',' process number must be between 1 and string',' An invalid process number was specified.',' Specify a valid process number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00072',' process "string" is not active',' An invalid process was specified.',' Specify a valid process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00073',' command string takes between string and string argument(s)',' An incorrect number of arguments was specified.',' Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00074',' no process has been specified',' No debug process has been specified.',' Specify a valid process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00075',' process "string" not found in this instance',' The specified process was not logged on to the current instance.',' Specify a valid process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00076',' dump string not found',' An attempt was made to invoke a dump that does not exist.',' Type DUMPLIST to see the list of available dumps.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00077',' dump string is not valid',' An attempt was made to invoke an invalid dump.',' Try another dump.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00078',' cannot dump variables by name',' An attempt was made to dump a variable by name on a system that does not support this feature.',' Try the PEEK command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00079',' variable string not found',' An attempt was made to dump a variable that does not exist.',' Use a valid variable name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00080',' invalid global area specified by level string',' An attempt was made to dump an invalid global area.',' Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use extra&nbsp;+&nbsp;level to dump global area level as well as extra bytes for every pointer; extra must be a multiple of 4.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00081',' address range [string, string) is not readable',' An attempt was made to read/write an invalid memory address range.',' Try another address or length.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00082',' memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring',' An invalid length was specified for the POKE command.',' Use a valid length (either 1, 2, 4, or possibly 8).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00083',' warning: possibly corrupt SGA mapped',' Even though there may be SGA corruptions, the SGA was mapped.',' Use the DUMPSGA command to dump the SGA.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00084',' global area must be PGA, SGA, or UGA',' An attempt was made to dump an invalid global area.',' Specify either PGA, SGA, or UGA.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00085',' current call does not exist',' An invalid attempt was made to dump the current call heap.',' Wait until the process starts a call.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00086',' user call does not exist',' An invalid attempt was made to dump the user call heap.',' Wait until the process starts a call.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00087',' command cannot be executed on remote instance',' Cluster database command issued for non cluster database ORADEBUG command.',' Issue the command without the cluster database syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00088',' command cannot be executed by shared server',' A debug command was issued on a shared server.',' Reissue the command using a dedicated server.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00089',' invalid instance number in ORADEBUG command',' An invalid instance number was specified in a cluster database ORADEBUG command.',' Reissue the command with valid instance numbers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00090',' failed to allocate memory for cluster database ORADEBUG command',' Could not allocate memory needed to execute cluster database oradebug.',' Reissue the command on each instance with single-instance ORADEBUG.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00091',' LARGE_POOL_SIZE must be at least string',' The value of LARGE_POOL_SIZE is below the minimum size.',' Increase the value of LARGE_POOL_SIZE past the minimum size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00092',' LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC',' The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.',' Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00093',' string must be between string and string',' The parameter value is not in a valid range.',' Modify the parameter value to be within the specified range.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00094',' string requires an integer value',' The parameter value is not an integer.',' Modify the parameter value to be an integer.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00096',' invalid value string for parameter string, must be from among string',' The value for the initialization parameter is invalid.',' Choose a value as indicated by the message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00097',' use of Oracle SQL feature not in SQL92 string Level',' An attempt was made to use an Oracle SQL feature that is not compliant with the SQL92 standard.',' Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00099',' timed out while waiting for resource, potential PDML deadlock',' The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system.',' Increase the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00100',' no data found',' An application made a reference to unknown or inaccessible data.',' Handle this condition within the application or make appropriate modifications to the application code.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00101',' invalid specification for system parameter DISPATCHERS',' The syntax for the DISPATCHERS initialization parameter is incorrect.',' Enter the DISPATCHERS initialization parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00102',' network protocol string cannot be used by dispatchers',' The network specified in DISPATCHERS does not have the functionality required by the dispatchers.',' Refer to your Oracle operating system-specific documentation for network protocols supported by the dispatchers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00103',' invalid network protocol; reserved for use by dispatchers',' The network specified in the Net8 connect string is reserved for use by the dispatchers.',' Specify other network protocols in the connection string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00104',' deadlock detected; all public servers blocked waiting for resources',' 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.',' Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automatically start new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00105',' dispatching mechanism not configured for network protocol string',' An attempt was made to alter the dispatcher''s configuration for a network protocol that was not specified in the initialization parameter file.',' Do one of the following:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00106',' cannot startup/shutdown database when connected to a dispatcher',' An attempt was made to start or shut down an instance while connected to a shared server via a dispatcher.',' Reconnect 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00107',' failed to connect to ORACLE listener process',' Most likely due to the fact that the network listener process has not been started.',' Check for the following:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00108',' failed to set up dispatcher to accept connection asynchronously',' The network protocol used by the dispatcher does not support asynchronous operations.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00111',' not all servers started because number of servers is limited to string',' An attempt was made to start more servers than the maximum number specified by the system parameter MAX_SHARED_SERVERS.',' Increase the value of the MAX_SHARED_SERVERS initialization parameter as needed or re-issue the ALTER SYSTEM SET SHARED_SERVERS statement with an appropriate number of servers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00112',' only created up to string (maximum specified) dispatchers',' An attempt was made to start more dispatchers than the maximum number specified by the system parameter MAX_DISPATCHERS.',' Increase the value of the MAX_DISPATCHERS initialization parameter as needed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00113',' protocol name string is too long',' A protocol name specified in the DISPATCHERS initialization parameter is too long.',' Use a valid protocol name for the DISPATCHERS value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00114',' missing value for system parameter SERVICE_NAMES',' No value was specified for the SERVICE_NAMES initialization parameter, nor for the DB_NAME parameter.',' Add an SERVICE_NAMES or DB_NAME definition to the initialization parameter file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00115',' connection refused; dispatcher connection table is full',' A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.',' Connect to a different dispatcher or use a dedicated server.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00116',' SERVICE_NAMES name is too long',' The service name specified in the SERVICE_NAMES initialization parameter is too long.',' Use a shorter name for the SERVICE_NAMES value (less than or equal to 255 characters).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00117',' value out of range for system parameter SHARED_SERVERS',' The specified value of the SHARED_SERVERS initialization parameter is incorrect.',' SHARED_SERVERS must be greater than or equal to 0 and less than or equal to the value of MAX_SHARED_SERVERS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00118',' value out of range for system parameter DISPATCHERS',' The value of the DISPATCHERS parameter is incorrect.',' The sum of all DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value of MAX_DISPATCHERS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00119',' invalid specification for system parameter string',' The syntax for the specified parameter is incorrect.',' Refer to the Oracle9i Database Reference for the correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00120',' dispatching mechanism not enabled or installed',' Either the dispatching mechanism was not enabled or the Oracle executable image was not installed with the dispatching mechanism.',' Refer to the Oracle9i Database Administrator''s Guide and your operating system-specific documentation for procedures for starting and configuring the dispatcher process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00121',' SHARED_SERVERS specified without DISPATCHERS',' A definition for SHARED_SERVERS was specified in the initialization parameter file, but no definition for DISPATCHERS was specified. Without a value for DISPATCHERS, shared servers will never be used.',' Add a definition for DISPATCHERS in the initialization parameter file (or remove the definition for SHARED_SERVERS, if shared servers are not being used).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00122',' cannot initialize network configuration',' Oracle could not initialize Net8.',' See accompanying messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00123',' idle public server terminating',' Too many idle servers were waiting on the common queue.',' This error is used internally, no action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00124',' DISPATCHERS specified without MAX_SHARED_SERVERS',' A definition for DISPATCHERS was specified in the initialization parameter file, but MAX_SHARED_SERVERS was specified as zero.',' Specify MAX_SHARED_SERVERS to be greater than zero.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00125',' connection refused; invalid presentation',' The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.',' Correct the PRESENTATION specified in the TNS address.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00126',' connection refused; invalid duplicity',' The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.',' Correct the DUPLICITY specified in the TNS address.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00127',' dispatcher string does not exist',' There is currently no dispatcher running with the specified name.',' Retry with a name of the form "D###" denoting an existing dispatcher process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00128',' this command requires a dispatcher name',' Wrong syntax for ALTER SYSTEM SHUTDOWN.',' Use correct syntax:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00129',' listener address validation failed ''string''',' An error was encountered while validating the listener address.',' Resolve the error or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00130',' invalid listener address ''string''',' The listener address specification is not valid.',' Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00131',' network protocol does not support registration ''string''',' The specified protocol does not support async notification.',' Refer to the manual for information on supported network protocols.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00132',' syntax error or unresolved network name ''string''',' Listener address has syntax error or cannot be resolved.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00150',' duplicate transaction ID',' An attempt was made to start a new transaction with an ID already in use by an existing transaction.',' Check your application.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00151',' invalid transaction ID',' The specified transaction ID does not correspond to an existing valid transaction.',' Check your application.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00152',' current session does not match requested session',' The current session is not the same as the session that was passed into a UPIXADO() call.',' Check your application.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00153',' internal error in XA library',' The XA library could not access thread-specific pointers.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00154',' protocol error in transaction monitor',' The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.',' Contact the transaction monitor customer support.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00155',' cannot perform work outside of global transaction',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00160',' global transaction length string is greater than maximum (string)',' An external global transaction ID with a too large length field was passed in.',' Report the problem to your external transaction coordinator vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00161',' transaction branch length string is illegal (maximum allowed string)',' An external transaction branch ID with a length either too large or 0 was passed in.',' Report the problem to your external transaction coordinator vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00162',' external dbid length string is greater than maximum (string)',' An external database name with too large a length field was passed in.',' Report the problem to your external transaction coordinator vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00163',' internal database name length string is greater than maximum (string)',' An internal database name with a too large length field was passed in.',' Report the problem to your external transaction coordinator vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00164',' distributed autonomous transaction disallowed within migratable distributed transaction',' A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.',' Roll back or commit the current distributed transaction first.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00165',' migratable distributed autonomous transaction with remote operation is not allowed',' A request was made by the application to start a migratable distributed autonomous transaction with remote operation.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00200',' controlfile could not be created',' It was not possible to create the control file.',' Check that there is sufficient disk space and no conflicts in file names and try to create the control file again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00201',' controlfile version string incompatible with ORACLE version string',' The control file was created by incompatible software.',' Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00202',' controlfile: ''string''',' This message reports the name file involved in other messages.',' See associated error messages for a description of the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00203',' using the wrong controlfiles',' 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.',' Check that the correct control files were specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00204',' error in reading (block string, # blocks string) of controlfile',' A disk I/O failure was detected on reading the control file.',' Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle''s inability to read the disk or control file. See the Oracle9i Database Administrator''s Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00205',' error in identifying controlfile, check alert log for more info',' The system could not find a control file of the specified name and size.',' One of the following:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00206',' error in writing (block string, # blocks string) of controlfile',' A disk I/O failure was detected on writing to the control file.',' Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle''s inability to write to the disk or control file. See the Oracle9i Database Administrator''s Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00207',' controlfiles are not for the same database',' 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.',' Check that the control file is for the correct database and is not an old version. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00208',' number of controlfile names exceeds limit of string',' An attempt was made to use more control files than Oracle supports.',' Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00209',' control file blocksize mismatch, check alert log for more info',' The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.',' Reduce the block size to the amount specified in the message and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00210',' cannot open the specified controlfile',' Cannot open the control file.',' Check to make sure the control file exists and is not locked by some other program.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00211',' controlfile does not match previous controlfiles',' A control file was specified that belongs to another database.',' Find and install the correct control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00212',' block size string below minimum required size of string bytes',' The block size specified was too small. Space for the system overhead is required.',' Specify a larger block size and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00213',' cannot reuse controlfile; old file size string, string required',' To reuse a control file, it must be the same size as the one previously used.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00214',' controlfile ''string'' version string inconsistent with file ''string'' version string',' An inconsistent set of control files, datafiles, and redo log files was used.',' Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00215',' must be at least one controlfile',' No control file is specified or the control file specified does not exist.',' Specify at least one valid control file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00216',' controlfile could not be resized for migration from 8.0.2',' Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed.',' Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00217',' controlfile could not be resized for migration from 9.0.1',' Controlfiles created by release 9.0.1 were missing some records. These records are automatically added by resizing the controlfile when attempting to run a later release. The resize failed.',' Look in the alert log for the reason the resize failed. If it can be fixed by giving the controlfile more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumpped to the trace file to create a new controlfile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00218',' block size string of controlfile does not match DB_BLOCK_SIZE (string)',' 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.',' Restore a good copy of the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00219',' required controlfile size string exceeds maximum allowable size string',' An invocation of CREATE DATABASE, CREATE CONTROLFILE, cfileCalcSizeList, or cfileCalcSizeArray was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.',' In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00220',' controlfile not mounted by first instance, check alert log for more info',' 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.',' Find and install the correct control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00221',' error on write to controlfile',' An error occurred when writing to one or more of the control files.',' See accompanying messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00222',' operation would reuse name of a currently mounted controlfile',' The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.',' Retry the operation with a different file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00223',' convert file is invalid or incorrect version',' 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 the ALTER DATABASE CONVERT command is issued.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00224',' controlfile resize attempted with illegal record type (string)',' An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.',' Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1 to 16).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00225',' expected size string of controlfile differs from actual size string',' 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.',' Restore a good copy of the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00226',' operation disallowed while alternate controlfile open',' The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.',' Retry the operation after calling cfileUseCurrent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00227',' corrupt block detected in controlfile: (block string, # blocks string)',' A block header corruption or checksum error was detected on reading the control file.',' Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00228',' length of alternate controlfile name exceeds maximum of string',' The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system.',' Retry the operation with a shorter file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00229',' operation disallowed: already hold snapshot controlfile enqueue',' The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.',' Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00230',' operation disallowed: snapshot controlfile enqueue unavailable',' The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.',' Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00231',' snapshot controlfile has not been named',' During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot, it was detected that no file name for the snapshot control file had previously been specified.',' Specify a name for the snapshot control file by calling cfileSetSnapshotName.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00232',' snapshot controlfile is nonexistent, corrupt, or unreadable',' The snapshot control file was found to be non-existent, corrupt, or unreadable during an invocation of cfileUseSnapshot.',' Call cfileMakeAndUseSnapshot again (or for the first time).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00233',' copy controlfile is corrupt or unreadable',' The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.',' Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00234',' error in identifying or opening snapshot or copy controlfile',' A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.',' Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00235',' controlfile fixed table inconsistent due to concurrent update',' Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.',' Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00236',' snapshot operation disallowed: mounted controlfile is a backup',' Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.',' Mount a current control file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00237',' snapshot operation disallowed: controlfile newly created',' An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.',' Mount a current control file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00238',' operation would reuse a filename that is part of the database',' The file name 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.',' Retry the operation with a different file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00250',' archiver not started',' An attempt was made to stop automatic archiving, but the archiver process was not running.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00251',' LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string',' 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.',' Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00252',' log string of thread string is empty, cannot archive',' 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 the instance died during a log switch and the log was empty.',' Empty logs do not need to be archived. Do not attempt to archive the redo log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00253',' character limit string exceeded by archive destination string string',' The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.',' Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00254',' error in archive control string ''string''',' The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.',' Check the archive string used to make sure it refers to a valid online device.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00255',' error archiving log string of thread string, sequence # string',' An error occurred during archiving.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00256',' cannot translate archive destination string string',' The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.',' Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00257',' archiver error. Connect internal only, until freed.',' 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.',' Check the 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00258',' manual archiving in NOARCHIVELOG mode must identify log',' 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 file name.',' Specify the log by file name, by group number or by thread and sequence number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00259',' log string of open thread string is the current log, cannot archive',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00260',' cannot find online log sequence string for thread string',' The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations:',' Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00261',' log string of thread string is being archived or modified',' 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.',' Wait for the current operation to complete and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00262',' current log string of closed thread string cannot switch',' 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.',' Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00263',' there are no logs that need archiving for thread string',' An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00264',' no recovery required',' An attempt was made to perform media recovery on files that do not need any type of recovery.',' Do not attempt to perform media recovery on the selected files. Check to see that the file names were entered properly. If not, retry the command with the proper file names.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00265',' instance recovery required, cannot set ARCHIVELOG mode',' The database either crashed or was shut down with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.',' Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00266',' name of archived log file needed',' During media recovery, the name of an archived redo log file was requested, but no name was entered.',' Mount the correct redo log file and enter its name when it is requested.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00267',' name of archived log file not needed',' During media recovery, the name of an archived redo log file was entered, but no name was requested.',' Continue media recovery, but do not enter a new log name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00268',' specified log file does not exist ''string''',' The given redo log file does not exist.',' Check the spelling and capitalization of the file name and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00269',' specified log file is part of thread string not string',' The given redo log file is not part of the given thread.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00270',' error creating archive log string',' An error was encountered when either creating or opening the destination file for archiving.',' Check that the archive destination is valid and that there is sufficient space on the destination device.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00271',' there are no logs that need archiving',' An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00272',' error writing archive log string',' An I/O error occurred while archiving a redo log file.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00273',' media recovery of direct load data that was not logged',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00274',' illegal recovery option string',' An illegal option was specified for a recovery command.',' Correct the syntax and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00275',' media recovery has already been started',' An attempt was made to start a second media recovery operation in the same session.',' Complete or cancel the first media recovery session or start another session to perform media recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00276',' CHANGE keyword specified but no change number given',' The CHANGE keyword was specified on the command line, but no change number was given.',' Retry the command using a valid change number after the CHANGE keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00277',' illegal option to the UNTIL recovery flag string',' Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.',' Correct the syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00278',' log file ''string'' no longer needed for this recovery',' The specified redo log file is no longer needed for the current recovery.',' No action is 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00279',' change string generated at string needed for thread string',' The requested log is required to proceed with recovery.',' Supply the requested log with ALTER DATABASE RECOVER LOGFILE filename or cancel recovery with ALTER DATABASE RECOVER CANCEL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00280',' change string for thread string is in sequence #string',' This message helps to locate the redo log file with the specified change number requested by other messages.',' Use the information provided in this message to specify the required archived redo log files for other errors.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00281',' media recovery may not be performed using dispatcher',' An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.',' Connect to the instance via a dedicated server process to perform media recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00282',' UPI string call not supported, use ALTER DATABASE RECOVER',' The given UPI call is no longer supported.',' Use the ALTER DATABASE RECOVER command for all recovery actions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00283',' recovery session canceled due to errors',' An error during recovery was determined to be fatal enough to end the current recovery session.',' More specific messages will accompany this message. Refer to the other messages for the appropriate action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00284',' recovery session still in progress',' An error during recovery was determined to be minor enough to allow the current recovery session to continue.',' More specific messages will accompany this message. Refer to the other messages for the appropriate action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00285',' TIME not given as a string constant',' UNTIL TIME was not followed by a string constant for the time.',' Enter the time enclosed in single quotation marks.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00286',' no members available, or no member contains valid data',' None of the members of a redo log file group are available, or the available members do not contain complete data.',' If a member is temporarily offline, attempt to make it available. Make sure that the correct file names are being used, especially if the redo log file is being accessed from a remote location.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00287',' specified change number string not found in thread string',' The given change number does not appear in any of the online redo logs for the given thread.',' Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00288',' to continue recovery type ALTER DATABASE RECOVER CONTINUE',' During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.',' Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00289',' suggestion : string',' This message reports the next redo log file name 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.',' Consider using this file name for the next log needed for recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00290',' operating system archival error occurred. See error below',' While attempting to archive to a redo log file, the server encountered an unexpected operating system error.',' Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00291',' numeric value required for PARALLEL option',' A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.',' Re-enter the command with a numeric argument specifying the degree of parallelism desired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00292',' parallel recovery feature not installed',' A parallel recovery was requested when the parallel recovery option is not installed.',' Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00293',' controlfile out of sync with redo log',' The redo log file and control file are out of sync because a non-current control file was specified when the instance was started.',' Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00294',' invalid archivelog format specifier ''string''',' An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted for string are s, S, t, and T.',' Correct the initialization file and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00295',' datafile/tempfile number string is invalid, must be between 1 and string',' An invalid file number was specified.',' Specify a valid datafile or tempfile number and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00296',' maximum number of files (string) exceeded for RECOVER DATAFILE LIST',' 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.',' Restart the instance with a higher value for DB_FILES.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00297',' must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START',' 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.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00298',' Missing or invalid attribute value',' A nonzero integer value is required when the following keyword attributes are specified:',' Correct the syntax and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00299',' must use file-level media recovery on data file string',' The control file does not contain an entry for this file, so block media recovery cannot be done.',' Restore the data file and perform file-level media recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00300',' illegal redo log block size string specified - exceeds limit of string',' The specified block size of the redo log is greater than the maximum block size for the operating system.',' Create the redo log on a device with a smaller block size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00301',' error in adding log file ''string'' - file cannot be created',' The creation of the redo log file failed',' Check whether:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00302',' limit of string logs exceeded',' The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16).',' Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00303',' cannot process Parallel Redo',' A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.',' Use a later release that supports Parallel Redo.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00304',' requested INSTANCE_NUMBER is busy',' An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.',' Either:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00305',' log string of thread string inconsistent; belongs to another database',' 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.',' Specify the correct redo log file, and then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00306',' limit of string instances in this database',' Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.',' You cannot start more than the lower of:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00307',' requested INSTANCE_NUMBER out of range, maximum is string',' The initialization parameter INSTANCE_NUMBER specified a number that was out of range.',' Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1 and the maximum value is the lower of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00308',' cannot open archived log ''string''',' The system cannot access a required archived redo log file.',' Check that the offline 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00309',' log belongs to wrong database',' The system cannot access the archived redo log because it belongs to another database.',' Specify the correct redo log file and then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00310',' archived log contains sequence string; sequence string required',' The archived log is out of sequence, probably because it is corrupted or the wrong redo log file name was specified during recovery.',' Specify the correct redo log file and then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00311',' cannot read header from archived log',' An I/O error occurred when attempting to read the log file header from the specified archived redo log file.',' Other messages will accompany this message. See the associated messages for the appropriate action to take.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00312',' online log string thread string: ''string''',' This message reports the file name for details of another message.',' Other messages will accompany this message. See the associated messages for the appropriate action to take.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00313',' open failed for members of log group string of thread string',' The online log cannot be opened. The file may not be in the expected location.',' Specify the correct redo log file or make the log available, if necessary. Also, see the accompanying messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00314',' log string of thread string, expected sequence# string doesn''t match string',' The online log is corrupted or is an old version.',' Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00315',' log string of thread string, wrong thread # string in header',' The online log is corrupted or is an old version.',' Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00316',' log string of thread string, type string in header is not log file',' The online log is corrupted or is an old version.',' Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00317',' file type string in header is not log file',' This is not an archived log file.',' Find the correct file and try again. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00318',' log string of thread string, expected file size string doesn''t match string',' The file size indicated in the control file did not match the file size contained in the log file.',' Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00319',' log string of thread string has incorrect log reset status',' An online redo log has log reset data that is different from the log reset data in the control file. The log is probably an incorrectly restored backup.',' Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00320',' cannot read file header from log string of thread string',' The file is not available.',' Restore the log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00321',' log string of thread string, cannot update log file header',' Cannot write to the log file.',' Restore access to the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00322',' log string of thread string is not current copy',' An online log appears to be an incorrectly restored backup.',' Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00323',' Current log of thread string not useable and all others need archiving',' An attempt to open the 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.',' Archive the logs for the thread and then retry the open.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00324',' log file ''string'' translated name ''string'' too long, string characters exceeds string limit',' The translated name for a log file is too long.',' Choose an untranslated name that yields a shorter translated name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00325',' archived log for thread string, wrong thread # string in header',' The archived log is corrupted or for another thread. Cannot use the log for applying the redo.',' Find the correct archived log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00326',' log begins at change string, need earlier change string',' The archived log supplied for recovery was generated after the log that is needed. Cannot yet use the log for applying redo.',' Find the correct archived log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00327',' log string of thread string, physical size string less than needed string',' A log file has shrunk in size. This is likely to have been caused by a computer operator''s mistake or an operating system error.',' Restore the log file from backup. If a backup is not available, drop this log and re-create it. If the database was shut down cleanly, no further action should be required; otherwise, incomplete recovery may be required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00328',' archived log ends at change string, need later change string',' The archived log supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo.',' Find the correct archived log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00329',' archived log begins at change string, need change string',' The archived log is not the correct log. An earlier log is needed.',' Restore the correct log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00330',' archived log ends at change string, need change string',' The archived log is not the correct log. A later log is needed.',' Restore the correct log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00331',' log version string incompatible with ORACLE version string',' The log was written by an incompatible version of Oracle.',' Recover the database with the compatible software, shut it down cleanly, and then restart Oracle with the current software.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00332',' archived log is too small - may be incompletely archived',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00333',' redo log read error block string count string',' An I/O error occurred while reading the log described in the accompanying error.',' Restore accessibility to file, or get another copy of the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00334',' archived log: ''string''',' This message reports the file name involved with other errors.',' See associated error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00335',' online log string: No log with this number, log does not exist',' This message reports the file name involved with other errors.',' See associated error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00336',' log file size string blocks is less than minimum string blocks',' The log file size as specified in the CREATE DATABASE statement is too small.',' Increase the log file size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00337',' log file ''string'' does not exist and no size specified',' An attempt to add a log found neither an existing file nor a size for creating the file.',' Specify a size for the log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00338',' log string of thread string is more recent than controlfile',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00339',' archived log does not contain any redo',' 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.',' Restore the correct log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00340',' IO error processing online log string of thread string',' An I/O error occurred on the named online log.',' Restore accessibility to the file or restore the file from backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00341',' log string of thread string, wrong log # string in header',' The internal information in an online log file does not match the control file.',' Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator''s Guide for recovery procedures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00342',' archived log was created before last RESETLOGS',' Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.',' Supply the correct log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00343',' too many errors, log member closed',' The maximum number of errors on this log member has been exceeded.',' Correct the underlying problem by referring to the other error messages found with this one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00344',' unable to re-create online log ''string''',' An I/O failure occurred when attempting to re-create an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.',' Correct the file/device as indicated by accompanying errors.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00345',' redo log write error block string count string',' An I/O error occurred while writing the log.',' Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00346',' log member marked as STALE',' A log file member no longer is complete.',' Correct the underlying problem by referring to the other error messages found with this one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00347',' log string of thread string, expected block size string doesn''t match string',' During online recovery, the block size specified in the control file did not match the block size contained in the redo log file.',' Restore the correct redo file from a backup or reset the online redo log files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00348',' single-process redo failure. Must abort instance',' 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.',' SHUTDOWN ABORT and restart the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00349',' failure obtaining block size for ''string''',' The operating system was unable to determine the block size for the given file name.',' Consult the accompanying error message, and correct the device or specify another file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00350',' log string of thread string needs to be archived',' The command cannot be done because the log has not been archived, and media recovery has been enabled.',' 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 unusable, and forcing the drop of some offline files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00351',' recover-to time invalid',' The time specified in a recover-until statement must be after January 1st 1988.',' Specify a time after January 1st 1988.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00352',' all logs for thread string need to be archived - cannot enable',' An attempt was made 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.',' Archive a log for the thread or disable media recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00353',' log corruption near block string change string time string',' Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.',' Perform recovery with a good version of the redo log or do incomplete recovery up to the indicated change or time.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00354',' corrupt redo log block header',' The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message.',' Perform recovery with a good version of the redo log or perform cancel-based recovery up to, but not including, the corrupted redo log file. 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00355',' change numbers out of order',' 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.',' Perform recovery with a good version of the log or perform time-based recovery up to the indicated time.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00356',' inconsistent lengths in change description',' 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.',' Perform recovery with a good version of the log or do time-based recovery up to the indicated time.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00357',' too many members specified for log file, the maximum is string',' 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.',' Use fewer log file members.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00358',' Too many file members specified, the maximum is string',' A CREATE or ALTER statement specified too many members in a parenthesised file list.',' Specify a number of file members that is within the port-defined limit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00359',' logfile group string does not exist',' An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist.',' Check the configuration of the log files and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00360',' not a logfile member: string',' A file name was given to DROP LOGFILE MEMBER command that is not a part of the database, or which is a datafile.',' Supply a valid log file member name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00361',' cannot remove last log member string for group string',' An attempt has been made to remove the last member of a log file group.',' If desired, delete the entire log, by using DROP LOGFILE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00362',' member is required to form a valid logfile in group string',' A request to drop a log file member was denied because it would remove data required to form a complete log file.',' If desired, delete the entire log (after archiving if required), by using DROP LOGFILE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00363',' log is not the archived version',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00364',' cannot write header to new log member',' An I/O error occurred when attempting to write the header to a log member that is being added to an existing group.',' See accompanying errors. Fix the problem or use another file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00365',' the specified log is not the correct next log',' 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.',' Find the log that was generated by this copy of the database and give that file name to recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00366',' log string of thread string, checksum error in the file header',' 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.',' Find and install correct version of the log or reset the logs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00367',' checksum error in log file header',' 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.',' Find the correct file and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00368',' checksum error in redo log block',' The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents.',' Perform 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. Restore the correct file or reset logs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00369',' Current log of thread string not useable and other log being cleared',' An attempt to open the 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00371',' not enough shared pool memory',' The SHARED_POOL_SIZE initialization parameter is too small.',' Increase the parameter value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00372',' file string cannot be modified at this time',' An attempt was made 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.',' Check the status of the file and its tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00373',' online log version string incompatible with ORACLE version string',' The online log was written by an incompatible version of Oracle. This can occur when the log file was created by either a new or older version of Oracle.',' Recover the database with the compatible software, shut it down cleanly, and then restart with current software.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00374',' parameter db_block_size = string invalid; must be a multiple of string in the range [string..string]',' An invalid value was specified for the DB_BLOCK_SIZE parameter.',' Adjust the value of the parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00375',' unable to get default db_block_size',' The system was unable to determine the default value for DB_BLOCK_SIZE.',' See the accompanying system-specific error. As a workaround, specify the block size in the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00376',' file string cannot be read at this time',' An attempt was made to read from a file that is not readable. Most likely the file is offline.',' Check the state of the file. Bring it online.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00377',' Frequent backups of file string causing write operation to stall',' 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.',' Increase the interval between begin hot-backup commands for this file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00378',' buffer pools cannot be created as specified',' The number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration.',' Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00379',' no free buffers available in buffer pool string for block size stringK',' All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.',' Increase the number of buffers in the specified pool for the specified block size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00380',' cannot specify db_numberk_cache_size since numberK is the standard block size',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00381',' cannot use both new and old parameters for buffer cache size specification',' User specified one or more of {DB_CACHE_SIZE, DB_RECYCLE_CACHE_SIZE, DB_KEEP_CACHE_SIZE, DB_nK_CACHE_SIZE (where n is one of {2, 4, 8, 16, 32}) AND one or more of {DB_BLOCK_BUFFERS, BUFFER_POOL_KEEP, BUFFER_POOL_RECYCLE}. This is illegal.',' Use EITHER the old (pre-Oracle 9.0.0) 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00382',' string not a valid block size, valid range [string..string]',' 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.',' Remove corresponding parameter from the initialization parameter file and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00383',' DEFAULT cache for blocksize string cannot be reduced to zero',' User attempted to reduce DB_CACHE_SIZE to zero, or attempted to reduce DB_nK_CACHE_SIZE to zero while there were still online tablespaces with block size nK. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set DB_CACHE_SIZE to zero.',' Offline any tablespaces with the corresponding block size and then perform the operation again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00384',' Insufficient memory to grow cache',' The system could not allocate sufficient memory to grow the cache to the specified size.',' Attempt a smaller increase in the value of the parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00390',' log string of thread string is being cleared, cannot become current log',' 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 usable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.',' If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command, or drop the log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00391',' All threads must switch to new log format at the same time',' An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00392',' log string of thread string is being cleared, operation not allowed',' 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.',' If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command or drop the log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00393',' log string of thread string is needed for recovery of offline datafiles',' 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.',' Archive the log and then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00394',' online log reused while attempting to archive it',' An attempt was made to reuse an online log file that is being archived.',' The online log file has been overwritten; it cannot be archived.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00395',' online logs for the clone database must be renamed',' A clone database open forces log file renaming to avoid overwriting the primary log files.',' Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00396',' error string required fallback to single-pass recovery',' The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.',' Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the new algorithm. This usually requires making more main storage available to the recovery process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00397',' lost write detected for file string, block string',' The specified block is missing changes that should have been written to disk, indicating a lost write by the file I/O subsystem or volume manager.',' Run diagnostic checks on the I/O subsystem and resolve any errors');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00398',' abort thread recovery due to reconfiguration',' Global enqueue service reconfiguration occurred during instance/crash recovery.',' This is used internally, no action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00399',' corrupt change description in redo log',' A change vector in the redo log failed validation checks.',' Do recovery with a good version of the log or do time based recovery up to the indicated time.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00400',' invalid release value string for parameter string',' The release level given for the specified initialization parameter is invalid.',' Correct the parameter value in the parameter file and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00401',' the value for parameter string is not supported by this release',' The value specified cannot be supported by this release of the software.',' Choose an appropriate value, or remove the parameter value to use the default value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00402',' database changes by release string cannot be used by release string',' Changes have been made to the database that require a newer software release or that violate the compatibility parameters.',' Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00403',' string (string) is not the same as other instances (string)',' Another instance has set the COMPATIBLE or COMPATIBLE NO RECOVERY parameters differently than this instance.',' Change the parameters of the current instance to match other instances already running.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00404',' Convert file not found: ''string''',' The file used for converting the database from V7 to V8 could not be found.',' Verify that the migration process has been started on this database and that the convert file name is accessible.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00405',' compatibility type "string"',' Reporting a type associated with another error.',' See the accompanying error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00406',' COMPATIBLE parameter needs to be string or greater',' The value of 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.',' Shut down and restart with a higher compatibility setting.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00407',' rolling upgrade from release string.string to string.string is not allowed',' Another instance executing software at a different point release already has the database mounted.',' Shut down all instances then restart with the new software.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00408',' parameter string is set to TRUE',' Reporting the parameter that resulted in the compatibility error.',' Shut down and restart with a higher compatibility setting.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00409',' COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT',' This is due to upgrading from an older release of Oracle with tablespaces created using automatic segment-space management. To open the database, the COMPATIBLE parameter needs to be set to the specified value or higher.',' Shut down and start up with the specified compatibility setting.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00436',' ORACLE is not licensed. Contact Oracle Corp. for assistance',' This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.',' Check that Oracle is installed correctly. Then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00437',' ORACLE feature is not licensed. Contact Oracle Corp. for assistance',' This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.',' Check that Oracle is installed correctly. Then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00438',' string Option not installed',' The specified option is not installed.',' Either avoid calling the option, or purchase and install the option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00439',' feature not enabled: string',' The specified feature is not enabled.',' Do not attempt to use this feature.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00443',' background process "string" did not start',' The specified process did not start.',' Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00444',' background process "string" failed while starting',' Usually due to a bad (or non-existent) background process image.',' Get a good background process image.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00445',' background process "string" did not start after string seconds',' The specified process did not start after the specified time.',' Ensure that the background did not die and leave a trace file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00446',' background process started when not expected',' The background process specified started after Oracle was already running.',' Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process, report the message to Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00447',' fatal error in background process',' One of the background processes died unexpectedly.',' Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00448',' normal completion of background process',' One of the background processes completed normally as requested by the user.',' If you are solving a problem, check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00449',' background process ''string'' unexpectedly terminated with error string',' A foreground process needing service from a background process has discovered the process died.',' Refer to the message code given in the message and the trace file for the foreground and the background processes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00470',' LGWR process terminated with error',' The Log Writer process terminated abnormally.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00471',' DBWR process terminated with error',' The Database Writer process terminated abnormally.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00472',' PMON process terminated with error',' The Process Monitor process terminated abnormally.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00473',' ARCH process terminated with error',' The Archiver process terminated abnormally.',' Check the accompanying messages, if any, 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00474',' SMON process terminated with error',' The System Monitor process terminated abnormally.',' Check the accompanying messages, if any, 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00475',' TRWR process terminated with error',' The system tracing process terminated abnormally.',' Restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00476',' RECO process terminated with error',' The distributed transaction (two-phase commit) recovery process terminated abnormally.',' Restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00477',' SNP* process terminated with error',' A materialized view refresh process terminated abnormally.',' PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00478',' SMON process terminated due to error string',' SMON was unable to service the requests due to an error in cleanup of resources.',' Warm start the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00480',' LCK* process terminated with error',' One Lock process terminated abnormally.',' Check the accompanying messages, if any, 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00481',' LMON process terminated with error',' The global enqueue service monitor process terminated abnormally.',' Restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00482',' LMD* process terminated with error',' A global enqueue service daemon process terminated abnormally.',' Restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00483',' During shutdown a process abnormally terminated',' One of the background processes did not exit normally at or near the time of shutdown.',' Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00484',' LMS* process terminated with error',' A global cache service process terminated abnormally.',' Warm start the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00485',' DIAG process terminated with error string',' A global diagnostic process died.',' Wait for the process to restart.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00568',' Maximum number of interrupt handlers exceeded',' The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed.',' Reduce the number of registered interrupt handlers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00600',' internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]',' This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:',' Report this error to Oracle Support Services after gathering the following information:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00601',' cleanup lock conflict',' The Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00602',' internal programming exception',' Internal programming exception occurred.',' Report this error as a program bug to Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00603',' ORACLE server session terminated by fatal error',' An Oracle Server session is in an unrecoverable state.',' Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00604',' error occurred at recursive SQL level string',' An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).',' If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00606',' Internal error code',' A call to deferred UPI functions was made in non-deferred mode.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00607',' Internal error occurred while making a change to a data block',' An internal error or memory exception occurred while Oracle was applying redo to a data block.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00701',' object necessary for warmstarting database cannot be altered',' An attempt was made to alter or drop a database object (table, cluster, or index) defined in the control file''s bootstrap segment and needed to warm start the database.',' Correct the spelling of the object name or remove it from the ALTER or DROP statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00702',' bootstrap verison ''string'' inconsistent with version ''string''',' The version of the bootstrap data is incompatible with the current version of the software.',' Restore a version of the software that is compatible with the datafiles.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00703',' maximum number of row cache instance locks exceeded',' There are not enough row cache enqueues.',' Increase the value of the ROW CACHE ENQUEUE parameter and restart the system.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00704',' bootstrap process failure',' Failure in processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem.',' Correct the problems mentioned in the other messages. If the problem persists, contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00705',' inconsistent state during start up; shut down the instance, then restart it',' A previous attempt to start an instance was terminated.',' Shut down the instance completely and then restart it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00706',' error changing format of file ''string''',' An attempt to change the block0 format of the specified file failed because the file is read-only or offline.',' Make the file read-write or bring the file online and set the BLK0_FMTCHG event.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-00816',' error message translation failed',' There is an internal error where a routine was unable to translate a message code.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12315',' database link type is invalid for the ALTER DATABASE statement',' 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.',' 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 statement. See your documentation for Oracle security-related products for more information about creating database links using the ROM: link type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12316',' syntax error in database link''s connect string',' The connect string in the CREATE DATABASE LINK statement has a syntactical error.',' Drop the database link and re-create it using valid syntax. See the Oracle9i SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12317',' logon to database (link name string) denied',' 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).',' 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 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12318',' database (link name string) is already mounted',' You are attempting to mount a secondary database that has already been mounted by your instance.',' The database is already mounted, so you need not take additional action to mount it. To establish access, use the ALTER DATABASE linkname OPEN statement to open the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12319',' database (link name string) is already open',' You are attempting to open a secondary database that is already open.',' The database is open and you need not take additional action to establish access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12321',' database (link name string) is not open and AUTO_MOUNTING=FALSE',' The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12322',' unable to mount database (link name string)',' This message should be accompanied by additional error messages that indicate the cause of the problem.',' Follow the steps outlined in the accompanying error messages to resolve the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12323',' unable to open database (link name string)',' This message should be accompanied by additional error messages that indicate the cause of the problem.',' Follow the steps outlined in the accompanying error messages to resolve the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12324',' cannot use the ROM: link type on a private database link',' You can only specify the ROM: link type on a public, not a private, database link.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12326',' database string is closing immediately; no operations are permitted',' The database you attempted to access is closing, so your operation has been terminated.',' Wait until the database has been reopened, or contact the database administrator.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12329',' database string is closed; no operations are permitted',' The database you attempted to access is closed, so your operation has been terminated.',' Wait until the database is reopened, or contact the database administrator.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12333',' database (link name string) is not mounted',' An attempt was made to open a database that has not been mounted.',' Mount the database with the ALTER DATABASE linkname MOUNT statement, then re-attempt to open the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12334',' database (link name string) is still open',' An attempt was made to dismount a database that is still open.',' Close the database with the ALTER DATABASE linkname CLOSE statement, then re-attempt to dismount the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12335',' database (link name string) is not open',' An attempt was made to close a database that is not open.',' The database is closed; you can proceed with dismounting it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12336',' cannot login to database (link name string)',' An attempt was made to login while another user is mounting or dismounting the same database.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12341',' maximum number of open mounts exceeded',' The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12342',' open mounts exceeds limit set on the OPEN_MOUNTS parameter',' The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.',' Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12345',' user string lacks CREATE SESSION privilege in database link (linkname string)',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12350',' database link being dropped is still mounted',' An attempt was made to drop a ROM: database link that was still mounted and/or opened.',' Close and dismount the database and then re-issue the drop statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12351',' cannot create view using a remote object which has a remote object reference',' An attempt was made to create a view which references a remote object which, in turn, references an object on another database. Since the view that would have been created references a remote object, that object cannot reference an object on another database.',' Choose a different object to reference in your view or change the remote object so that it does not reference another database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12352',' object string.string@string is invalid',' 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.',' Manually recompile the invalid object in the secondary database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12353',' secondary stored object cannot reference remote object',' An attempt was made 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.',' Choose a different object to reference or change the remote view or procedure so that it does not reference another database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12354',' secondary object being dropped',' An attempt was made to access an object (for example, a table or view) on a secondary database that was in the process of being dropped.',' 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 Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12400',' invalid argument to facility error handling',' An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility.',' Specify a valid facility error handling parameter value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12401',' invalid label string: string',' The policy could not convert the label string to a valid internal label.',' Correct the syntax of the label string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12402',' invalid format string: string',' The format string is not supported by the policy.',' Correct the syntax of the format string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12403',' invalid internal label',' An internal label could not be converted to a valid label for the policy.',' Analyze any additional messages on the error stack and consult the policy documentation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12404',' invalid privilege string: string',' The policy could not interpret the privilege string.',' Specify a privilege string that is supported by the policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12405',' invalid label list',' The policy determined that the label list was invalid for its intended use.',' Check the policy constraints on the specific list of labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12406',' unauthorized SQL statement for policy string',' The policy did not authorize the database session to perform the requested SQL statement.',' Grant the user or program unit the necessary policy privilege or additional authorizations.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12407',' unauthorized operation for policy string',' The policy did not authorize the database session to perform the requested operation.',' Grant the user or program unit the necessary policy privilege or additional authorizations.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12408',' unsupported operation: string',' The specified policy does not support the requested operation.',' Consult the policy documentation to determine the supported access mediation operations.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12409',' policy startup failure for string policy',' The policy encountered an error during startup processing; access to the data protected by the policy is prohibited.',' Check the alert log for additional information, correct the policy error, and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12410',' internal policy error for policy: string Error: string',' The policy enforcement encountered an internal error.',' Consult the policy documentation for details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12411',' invalid label value',' The specified label value does not exist.',' Check the data dictionary views for the policy to identify valid labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12412',' policy package string is not installed',' The policy package does not exist in the database.',' Check that the policy package name is correct or install the required policy package.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12413',' labels do not belong to the same policy',' The labels being compared belong to different policies.',' Only compare labels that belong to the same policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12414',' internal LBAC error: string Error: string',' An internal label policy framework error occurred.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12415',' A column of another datatype exists on the specified table',' The datatype of the column present in the table is different from the datatype set for the policy column.',' Drop the column on the table or change the datatype for the policy column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12416',' policy string not found',' The specified policy does not exist in the database.',' Enter the correct policy name or create the policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12417',' database object "string" not found',' The specified object was not in the database.',' Enter the correct name for the database object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12418',' user string not found',' The specified user does not exist in the database.',' Correct the user name or create the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12419',' null binary label value',' A null value was provided for a binary label operation.',' Provide a valid binary label for the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12420',' required procedures and functions not in policy package "string"',' The policy package did not contain all of the procedures and functions necessary to enforce the policy.',' Consult the label framework documentation for a list of required procedures and functions for a policy package.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12421',' different size binary labels',' The label sizes for the binary label operation were not equal.',' Provide binary labels with the same lengths for the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12422',' max policies exceeded',' You tried to create a new policy, but the maximum number of policies for the instance had already been created.',' Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12423',' invalid position specified',' The position specified for a binary label operation was invalid.',' Provide a position that is within the label size limits.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12424',' length exceeds binary label size',' The length specified for a binary label operation exceeded the size of the binary label.',' Provide a bit or byte length that is within the label size limits.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12425',' cannot apply policies or set authorizations for system schemas',' 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.',' Apply policies and set authorizations only for non-system users.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12426',' invalid audit option',' The option specified was not a valid audit option for the specified policy.',' Enter a correct audit option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12427',' invalid input value for string parameter',' An input parameter was specified incorrectly.',' Correct the parameter value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12429',' label list range exceeded',' The specified index value was not between 1 and 6.',' Correct the index value for the label list operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12430',' invalid privilege number',' The specified privilege number was not between 1 and 32.',' Correct the privilege number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12431',' invalid audit action',' The specified audit action was not a valid audit action.',' Correct the audit action number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12432',' LBAC error: string',' LBAC enforcement resulted in an error.',' Correct the problem identified in the error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12433',' create trigger failed, policy not applied',' The policy could not be applied due to errors during the creation of a DML trigger.',' Correct the SQL syntax of the label function specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12434',' invalid audit type: string',' The audit type must be BY ACCESS or BY SESSION.',' Correct the audit type value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12435',' invalid audit success: string',' The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.',' Correct the audit success value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12436',' no policy options specified',' A NULL option string was specified, but no default schema or policy option string was found.',' Enter a valid option string, or alter the schema or policy to have a valid default option string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12437',' invalid policy option: string',' A value that was not a valid policy option was entered.',' Correct the policy option value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12438',' repeated policy option: string',' A policy option was entered more than once in the option string.',' Remove the duplicate policy option value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12439',' invalid combination of policy options',' A set of contradictory policy options was entered.',' Provide a set of compatible policy options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12440',' insufficient authorization for the SYSDBA package',' The use of the SYSDBA package requires the LBAC_DBA role.',' Grant the LBAC_DBA role to the database user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12441',' policy string already exists',' You tried to create a policy with the same name as an existing one.',' Use a different name or drop the existing policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12442',' policy column "string" already used by an existing policy',' You tried to create a policy with the same policy column name as an existing policy.',' Use a different name for the policy column or drop the existing policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12443',' policy not applied to some tables in schema',' You applied a policy to a schema, and some of the tables in the schema already had the policy applied.',' No action necessary; the policy was applied to the remaining tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12444',' policy already applied to table',' You tried to apply a policy to a table that was already protected by the policy.',' To change the policy options, predicate, or label function, remove the policy from the table and re-apply it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12445',' cannot change HIDDEN property of column',' You tried to specify a different HIDE option for a table with an existing policy column.',' Drop the column from the table and re-apply the policy with the new HIDE option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12446',' Insufficient authorization for administration of policy string',' You tried to perform an administrative function for a policy, but you have not been granted the policy_DBA role.',' Grant the user the policy_DBA role for the specified policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12447',' policy role already exists for policy string',' The role named policy_DBA already exists.',' Correct the policy name or delete the existing policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12448',' policy string not applied to schema string',' You tried to alter a schema policy that was not applied.',' Correct the policy name or schema name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12449',' Labels specified for user must be of type USER',' You tried to set labels for a user, but the labels in the list were not all designated as USER labels.',' Alter the labels to be USER labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12450',' LOB datatype disabled in LBAC initialization file',' You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled.',' Change the LBAC initialization file to allow the creation of LOB columns and attributes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12451',' label not designated as USER or DATA',' A label is either a DATA label, a USER label, or both DATA and USER.',' Enter TRUE for at least DATA or USER.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12452',' label tag string already exists',' The label tag value you entered is already in use for another label.',' Enter a different value for the label tag.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12453',' label string already exists',' The label value you entered already exists.',' No action necessary; alter the label to change its tag or type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12454',' label string does not exist for policy string',' The label tag or value you entered did not identify a label for the policy.',' Enter a label value or tag that is in use by the policy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12461',' undefined level string for policy string',' The specified level is not defined for the policy.',' Correct the level identifier value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12462',' undefined compartment string for policy string',' The specified compartment is not defined for the policy.',' Correct the compartment identifier value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12463',' undefined group string for policy string',' The specified group is not defined for the policy.',' Correct the group identifier value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12464',' invalid characters in label component string',' Label components can contain only alphanumeric characters, blanks, and underscores.',' Correct syntax of the label component.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12465',' not authorized for read or write on specified groups or compartments',' You included groups or compartments that are not in the user''s list of groups and compartments authorized for read or write access.',' Include read access when authorizing groups or compartments for write access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12466',' default level is greater than the user''s maximum',' The default level cannot be greater than the user''s maximum.',' Enter an authorized level.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12467',' minimum label can contain a level only',' You included compartments or groups in the minimum label.',' Enter only an authorized minimum level as the label.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12468',' max write level does not equal max read level',' The level in the max write label must equal the level in the max read label.',' Enter max read and max write labels with the same level component.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12469',' no user levels found for user string and policy string',' No levels have been specified for the user.',' Enter the maximum and minimum labels for the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12470',' NULL or invalid user label: string',' The label entered is NULL or not within the user''s authorizations.',' Enter the authorized labels for the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12471',' Specified compartment or group is not authorized for user',' 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.',' Enter an authorized compartment or group.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12476',' least upper bound resulted in an invalid OS label',' You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.',' Consult your OS label management documentation for information on invalid label generation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12477',' greatest lower bound resulted in an invalid OS label',' You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system.',' Consult your OS label management documentation for information on invalid label generation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12479',' file label string must equal DBHIGH string',' A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled.',' Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12480',' specified clearance labels not within the effective clearance',' You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance.',' Specify clearance labels that are within your own clearance range.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12481',' effective label not within program unit clearance range',' The effective label when the program unit was invoked was not within the range authorized for the program unit.',' Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12482',' internal MLS error: string Error: string',' An internal MLS policy error occurred.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12483',' label not in OS system accreditation range',' The specified label is above the OS maximum label or below the OS minimum label.',' Use a label that is within the accreditation range for the host OS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12484',' invalid OS label',' The specified label does not exist in the OS host''s label definition file.',' Use the OS label management tools to define the label.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12485',' new effective label not within effective clearance',' 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.',' Enter a value between the min and the max labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12486',' effective max labels and min labels cannot be changed',' You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed.',' Enter NULL values for the effective minimum and maximum labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12487',' clearance labels not between DBHIGH and DBLOW',' You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW.',' Enter clearance label values between DBHIGH and DBLOW.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12488',' maximum label does not dominate minimum label',' You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels.',' Enter label values that preserves the dominance relationship between the minimum and maximum.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12489',' default label not within clearance range',' 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.',' Enter a default label value within the clearance range.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12490',' DBHIGH cannot be lowered',' You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH.',' Enter a value for DBHIGH that dominates the old value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12491',' DBHIGH value does not dominate DBLOW',' You attempted to enter a value for DBHIGH that did not dominate DBLOW.',' Enter a value for DBHIGH that dominates DBLOW.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12492',' DBLOW cannot be changed',' 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.',' To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12493',' invalid MLS binary label',' 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.',' Check the DBA_MLS_LABELS view for the valid MLS labels.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12494',' cannot insert or delete a level, category, or release category',' You attempted to insert or delete a level, category, or release category definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12495',' cannot disable an enabled level, category, or release category',' You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may exist in some database label, so it cannot be disabled.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12496',' cannot change existing level, category, or release numbers',' You attempted to change the number assigned to level, category or releasability category.',' Change the character string representations, not the numbers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12497',' maximum combined categories exceeds string',' The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded.',' Enter numbers that do not add up to more than the maximum.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12700',' invalid NLS parameter value (string)',' An invalid NLS initialization parameter was specified.',' Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12701',' CREATE DATABASE character set is not known',' The character set specified in the CREATE DATABASE command does not exist on the system.',' Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12702',' invalid NLS parameter string used in SQL function',' An invalid parameter or value was entered in the NLS parameter string in a SQL function.',' Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12703',' this character set conversion is not supported',' An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.',' Use character sets available on the system in the CONVERT function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12704',' character set mismatch',' One of the following:',' Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12705',' invalid or unknown NLS parameter value specified',' There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.',' Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12706',' this CREATE DATABASE character set is not allowed',' An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.',' Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12707',' error while getting create database NLS parameter string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12708',' error while loading create database NLS parameter string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12709',' error while loading create database character set',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12710',' CREATE CONTROLFILE character set is not known',' The character set specified when creating the control file is unknown.',' Specify a known character set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12711',' this CREATE CONTROLFILE character set is not allowed',' It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.',' Create the correct control file for machine and character set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12712',' new character set must be a superset of old character set',' 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.',' Specify a superset character set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12713',' Character data loss in NCHAR/CHAR conversion',' 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.',' Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to false.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12714',' invalid national character set specified',' Only UTF8 and AL16UTF16 are allowed to be used as the national character set.',' Ensure that the specified national character set is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12715',' invalid character set specified',' The character set specified is not allowed for this operation or is invalid.',' Ensure that the specified character set is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12716',' Cannot ALTER DATABASE CHARACTER SET when CLOB data exists',' CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.',' Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as export/import.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12717',' Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists',' NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.',' Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12718',' operation requires connection as SYS',' This command can only be run when connecting as user SYS.',' Connect as user SYS to run this command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12719',' operation requires database is in RESTRICTED mode',' This command can only be run when the database is in RESTRICTED mode.',' Ensure that the system is in RESTRICTED mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12720',' operation requires database is in EXCLUSIVE mode',' This command can only be run when the database is in EXCLUSIVE mode.',' Ensure that the system is in EXCLUSIVE mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12721',' operation cannot execute when other sessions are active',' This command can only be run when there are no other sessions active.',' Ensure there are no other connections to the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12800',' system appears too busy for parallel query execution',' Load on the system is too high to perform parallel queries.',' Re-execute serially or wait until the system load is reduced.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12801',' error signaled in parallel query server string',' A parallel query server reached an exception condition.',' Check the following error message for the cause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12802',' parallel query server lost contact with coordinator',' A parallel query server lost contact with the foreground (coordinator) process/thread.',' Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12803',' parallel query server lost contact with another server',' A parallel query server lost contact with another server.',' Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12804',' parallel query server appears to have died',' Cannot find process information for a parallel query server thread.',' Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12805',' parallel query server died unexpectedly',' A parallel query server died unexpectedly, PMON cleaning up the process.',' Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12806',' could not get background process to hold enqueue',' This is an internal error.',' This error should not normally occur. If it persists, THEN contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12807',' process queue could not receive parallel query message',' This is an internal error.',' This error should not normally occur. If it persists, THEN contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12808',' cannot set string_INSTANCES greater than number of instances string',' An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.',' See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12809',' cannot set string_INSTANCES when mounted in exclusive mode',' An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.',' SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12810',' PARALLEL_MAX_SERVERS must be less than or equal to string',' An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.',' Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12811',' PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string',' An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.',' Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12812',' only one PARALLEL or NOPARALLEL clause may be specified',' 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.',' Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12813',' value for PARALLEL or DEGREE must be greater than 0',' PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12814',' only one CACHE or NOCACHE clause may be specified',' 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.',' Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12815',' value for INSTANCES must be greater than 0',' PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.',' specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12816',' parallel create index fastpath operation',' The parallel create index fastpath operation event has been set.',' Set this event only under the supervision Oracle development.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12817',' parallel query option must be enabled',' A parallel query option feature has been invoked but this option has not been enabled.',' Enable the parallel query option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12818',' invalid option in PARALLEL clause',' An unrecognized option was used within a PARALLEL clause.',' specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12819',' missing options in PARALLEL clause',' PARALLEL clause cannot be empty.',' specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12820',' invalid value for DEGREE',' Invalid value for DEGREE was specified within a PARALLEL clause.',' Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12821',' invalid value for INSTANCES',' An invalid value for INSTANCES was specified within a PARALLEL clause.',' Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12822',' duplicate option in PARALLEL clause',' DEGREE or INSTANCES was specified more than once within a PARALLEL clause.',' Specify each desired PARALLEL clause option only once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12823',' default degree of parallelism may not be specified here',' The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.',' Respecify with an explicit degree of parallelism.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12824',' INSTANCES DEFAULT may not be specified here',' INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.',' Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12825',' explicit degree of parallelism must be specified here',' The DEGREE option was omitted from an ALTER DATABASE RECOVER command.',' Respecify with an explicit degree of parallelism.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12826',' hung parallel query server was killed',' The parallel query server was hung and subsequently killed.',' Re-execute the query and report suspicious events in the trace file to Oracle Support Services if the error persists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12827',' insufficient parallel query slaves available',' PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.',' Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12828',' Can''t start parallel transaction at a remote site',' PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.',' Do not use PDML at remote sites.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12829',' Deadlock - itls occupied by siblings at block string of file string',' A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction.',' Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Support Services if the error persists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12830',' Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE',' After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.',' Execute COMMIT or ROLLBACK before issuing another SQL command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12831',' Must COMMIT or ROLLBACK after executing INSERT with APPEND hint',' After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.',' Execute COMMIT or ROLLBACK before issuing another SQL command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12832',' Could not allocate slaves on all specified instances',' After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query.',' To allow results to be returned by successfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12833',' Coordinator''s instance not a member of parallel_instance_group',' The coordinator''s instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run.',' Either add the coordinator''s instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12834',' Instance group name, ''string'', too long, must be less than string characters',' The instance group name is too long.',' Either shorten the name or get rid of the instance group.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12835',' No instances are active in the GLOBAL_VIEW_ADMIN_GROUP',' There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views.',' Change the value of GLOBAL_VIEW_ADMIN_GROUP.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12838',' cannot read/modify an object after modifying it in parallel',' 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.',' Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12839',' cannot modify an object in parallel after modifying it',' 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.',' Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12840',' cannot access a remote table after parallel/insert direct load txn',' Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.',' Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12841',' Cannot alter the session parallel DML state within a transaction',' Transaction in progress.',' Commit or roll back the transaction and then re-execute.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12842',' schema modified during parallel execution',' Schema modified during the parse phase of parallel processing.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12843',' pdml lock not held properly on the table',' The coodinator crashed or released the lock on the partition which the slave is trying to aquire.',' Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12900',' must specify a default temporary tablespace for a locally managed database',' A locally managed database must have a temporary tablespace other than SYSTEM tablespace.',' Specify the default temporary tablespace when creating a locally managed database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12901',' Default temporary tablespace must be of TEMPORARY type',' In a locally managed database, default temporary tablespace must be TEMPORARY type.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12902',' default temporary tablespace must be SYSTEM or of TEMPORARY type',' In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12903',' default temporary tablespace must be an ONLINE tablespace',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12904',' default temporary tablespace cannot be altered to PERMANENT type',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12905',' default temporary tablespace cannot be brought OFFLINE',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12906',' cannot drop default temporary tablespace',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12907',' tablespace string is already the default temporary tablespace',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12908',' cannot specify SYSTEM as default temporary tablespace when creating database',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12909',' TEMPORARY keyword expected',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12910',' cannot specify temporary tablespace as default tablespace',' An attempt was made to assign a temporary tablespace to be a user''s default tablespace.',' Assign a permanent tablespace to be the default tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12911',' permanent tablespace cannot be temporary tablespace',' An attempt was made to assign a permanent tablespace to be a user''s temporary tablespace.',' Assign a temporary tablespace to be user''s temporary tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12912',' Dictionary managed tablespace specified as temporary tablespace',' An attempt was made to assign a dictionary managed tablespace to be a user''s temporary tablespace.',' Assign a locally managed temporary tablespace to be the user''s temporary tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12913',' Cannot create dictionary managed tablespace',' An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.',' Create a locally managed tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12914',' Cannot migrate tablespace to dictionary managed type',' An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed SYSTEM tablespace.',' Such an operation cannot be issued.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12915',' Cannot alter dictionary managed tablespace to read write',' An attempt was made to alter a dictionary managed tablespace to read write in a database whose SYSTEM tablespace is locally managed. This tablespace can only be dropped.',' Such an operation cannot be issued.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12920',' database is already in force logging mode',' The ALTER DATABASE FORCE LOGGING statement failed because the database is already in force logging mode.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12921',' database is not in force logging mode',' The ALTER DATABASE NO FORCE LOGGING statement failed because the database is not in force logging mode.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12922',' concurrent ALTER DATABASE [NO] FORCE LOGGING command is running',' There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING statement running in the system.',' Contact the database administrator who is responsible for the concurrent statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12923',' tablespace string is in force logging mode',' An attempt to alter the specified temporary tablespace failed because the tablespace is in force logging mode.',' Put the tablespace out of force logging mode by issuing an ALTER TABLESPACE NO FORCE LOGGING statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12924',' tablespace string is already in force logging mode',' An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12925',' tablespace string is not in force logging mode',' An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12926',' FORCE LOGGING option already specified',' In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.',' Remove all but one of the FORCE LOGGING options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12980',' checkpoint option not allowed with SET UNUSED',' An attempt was made to specify checkpoint option with SET UNUSED.',' Remove the checkpoint option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12981',' cannot drop column from an object type table',' An attempt was made to drop a column from an object type table.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12982',' cannot drop column from a nested table',' An attempt was made to drop a column from a nested table.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12983',' cannot drop all columns in a table',' An attempt was made to drop all columns in a table.',' Make sure at least one column remains in the table after the drop column operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12984',' cannot drop partitioning column',' An attempt was made to drop a column used as the partitioning key.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12985',' tablespace ''string'' is read only, cannot drop column',' An attempt was made to drop column from a partition/subpartition on a read-only tablespace.',' Set the tablespace to read write and resubmit statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12986',' columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE',' An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted).',' Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12987',' cannot combine drop column with other operations',' An attempt was made to combine drop column with other ALTER TABLE operations.',' Ensure that drop column is the sole operation specified in ALTER TABLE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12988',' cannot drop column from table owned by SYS',' An attempt was made to drop a column from a system table.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12989',' invalid value for checkpoint interval',' An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).',' Correct checkpoint interval and resubmit statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12990',' duplicate option specified',' Duplicate option specified in statement.',' Remove the duplicate option and resubmit statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12991',' column is referenced in a multi-column constraint',' An attempt was made to drop a column referenced by some constraints.',' Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12992',' cannot drop parent key column',' An attempt was made to drop a parent key column.',' Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12993',' tablespace ''string'' is offline, cannot drop column',' An attempt was made to drop a column from a partition/subpartition on an offline tablespace.',' Bring the tablespace online and resubmit statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12994',' drop column option only allowed once in statement',' An attempt was made to repeat the drop column option in a single statement.',' Separate drop column options into different statements and resubmit statements.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12995',' no columns in partially dropped state',' An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.',' Cannot submit this statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12996',' cannot drop system-generated virtual column',' An attempt was made to drop a virtual column generated by the system.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-12997',' cannot drop primary key column from an index-organized table',' An attempt was made to drop a primary key column from an index- organized table.',' This action is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13000',' dimension number is out of range',' The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.',' Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13001',' dimensions mismatch error',' The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.',' Make sure that the number of dimensions in the HHCODEs match.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13002',' specified level is out of range',' The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.',' Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13003',' the specified range for a dimension is invalid',' The specified range for a dimension is invalid.',' Make sure that the lower bound (lb) is less than the upper bound (ub).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13004',' the specified buffer size is invalid',' The buffer size for a function is not valid.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13005',' recursive HHCODE function error',' An error occurred in a recursively called HHCODE function.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13006',' the specified cell number is invalid',' The cell identifier is either less than 0 or greater than (2^ndim - 1).',' Make sure that the cell identifier is between 0 and (2^ndim - 1).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13007',' an invalid HEX character was detected',' A character that is not in the range [0-9] or [A-Fa-f] was detected.',' Verify that all characters in a string are in the range [0-9] or [A-Fa-f].');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13008',' the specified date format has an invalid component',' Part of the specified date format is invalid.',' Verify that the date format is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13009',' the specified date string is invalid',' The specified date string has a bad component or does not match the specified format string.',' Make sure that the components of the date string are valid and that the date and format strings match.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13010',' an invalid number of arguments has been specified',' An invalid number of arguments was specified for an SDO function.',' Verify the syntax of the function call.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13011',' value is out of range',' A specified dimension value is outside the range defined for that dimension.',' Make sure that all values to be encoded are within the defined dimension range.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13012',' an invalid window type was specified',' An invalid window type was specified.',' Valid window types are RANGE, PROXIMITY, POLYGON.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13013',' the specified topology was not INTERIOR or BOUNDARY',' A topology was specified that was not INTERIOR or BOUNDARY.',' Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE''s topology.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13014',' a topology identifier outside the range of 1 to 8 was specified',' A topology identifier outside the range of 1 to 8 was specified.',' Specify a topology in the range of 1 to 8.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13015',' the window definition is not valid',' The number of values used to define the window does not correspond to the window type.',' Verify that the number of values used to define the window is correct for the window type and number of dimensions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13016',' bad partition definition',' The partition common code was not correctly decoded.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13017',' unrecognized line partition shape',' The shape of a 2-D line partition could not be determined.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13018',' bad distance type',' The specified distance type is invalid.',' The only supported distance functions are EUCLID and MANHATTAN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13019',' coordinates out of bounds',' Vertex coordinates lie outside the valid range for the specified dimension.',' Re-define vertex coordinates within specified boundaries.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13020',' coordinate is NULL',' A vertex coordinate has a NULL value.',' Re-define vertex coordinate to have a non-NULL value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13021',' element not continuous',' The coordinates defining a geometric element are not connected.',' Re-define coordinates for the geometric element.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13022',' polygon crosses itself',' The coordinates defining a polygonal geometric element represent crossing segments.',' Re-define the coordinates for the polygon.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13023',' interior element interacts with exterior element',' An interior element of a geometric object interacts with the exterior element of that object.',' Re-define coordinates for the geometric elements.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13024',' polygon has less than three segments',' The coordinates defining a polygonal geometric element represent less than three segments.',' Re-define the coordinates for the polygon.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13025',' polygon does not close',' The coordinates defining a polygonal geometric element represent an open polygon.',' Re-define the coordinates of the polygon.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13026',' unknown element type for element string.string.string',' The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.',' Re-define 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 User''s Guide and Reference for an explanation of SDO_ETYPE and its possible values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13027',' unable to read dimension definition from string',' There was a problem reading the dimension definition from the layer_SDODIM table.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13028',' Invalid Gtype in the SDO_GEOMETRY object',' There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.',' Verify that the geometries have valid gtypes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13029',' Invalid SRID in the SDO_GEOMETRY object',' There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.',' Verify that the geometries have valid SRIDs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13030',' Invalid dimension for the SDO_GEOMETRY object',' There is a mismatch between the dimension in the SDO_GTYPE and the dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.',' Verify that the geometries have valid dimensionality.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13031',' Invalid Gtype in the SDO_GEOMETRY object for point object',' 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.',' Verify that the geometries have valid gtypes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13032',' Invalid NULL SDO_GEOMETRY object',' There are invalid SDO_POINT_TYPE, SDO_ELEM_INFO_ARRAY, or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13033',' Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object',' 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.',' Verify that the geometries have valid data.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13034',' Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object',' 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, Y, or both.',' Verify that the geometries have valid data.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13035',' Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object',' 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.',' Verify that the geometries have valid data.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13036',' Operation [string] not supported for Point Data',' The specified geometry function is not supported for Point data.',' Make sure that the specified geometry function is not called on point data.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13037',' SRIDs do not match for the two geometries',' A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.',' Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13039',' failed to update spatial index for element string.string.string',' Another error will accompany this message that will indicate the problem.',' Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13040',' failed to subdivide tile',' This is an internal error.',' Note any accompanying errors and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13041',' failed to compare tile with element string.string.string',' The spatial relationship between a generated tile and the specified element could not be determined.',' This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13041 and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13042',' invalid SDO_LEVEL and SDO_NUMTILES combination',' 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.',' Verify that the SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User''s Guide and Reference. Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13043',' failed to read meta data from the layer_SDOLAYER table',' An error was encountered reading the layer meta data from the layer_SDOLAYER table.',' 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, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13044',' the specified tile size exceeds the maximum resolution',' The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.',' See the Oracle Spatial User''s Guide and Reference 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 lesser tile size value than the current one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13045',' invalid compatibility flag',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13046',' invalid number of arguments',' An invalid number of arguments was specified for an SDO_GEOM function.',' Refer to the Oracle Spatial User''s Guide and Reference for a description of the syntax and semantics of the relevant SDO_GEOM function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13047',' unable to determine ordinate count from table layer_SDOLAYER',' An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.',' Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13048',' recursive SQL fetch error',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13049',' unable to determine tolerance value from table layer_SDODIM',' An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.',' Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13050',' unable to construct spatial object',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13051',' failed to initialize spatial object',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13052',' unsupported geometric type for geometry string.string',' The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.',' Check the Oracle Spatial User''s Guide and Reference for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13053',' maximum number of geometric elements in argument list exceeded',' The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.',' Check the Oracle Spatial User''s Guide and Reference 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 as an argument in a call to the SDO_GEOM function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13054',' recursive SQL parse error',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13055',' Oracle object string does not exist in specified table',' The requested object is not present in the specified table.',' Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13108',' spatial table string not found',' The specified spatial table does not exist.',' Check the Spatial Data option data dictionary to make sure that the table is registered.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13109',' spatial table string exists',' The specified spatial table is registered in the Spatial Data option data dictionary.',' Remove the existing table from the Spatial Data option data dictionary or use a different name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13110',' spatial table string is not partitioned',' The specified spatial table is not partitioned.',' Check the Spatial Data option data dictionary and make sure that a high water mark is set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13111',' spatial table string has no partition key defined',' The specified spatial table does not have a partition key defined.',' Check the Spatial Data option data dictionary and make sure that the table is partitioned.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13112',' invalid count mode string',' The specified count mode is not valid.',' Alter the count mode. Valid count modes are ESTIMATE or EXACT.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13113',' Oracle table string does not exist',' The specified Oracle table does not exist.',' Check the Oracle7 data dictionary and make sure that the table exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13114',' tablespace string not found',' The specified tablespace does not exist.',' Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13115',' tablespace string is already allocated',' The specified tablespace is already allocated to the spatial table.',' Allocate another tablespace name to the table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13116',' tablespace string is not allocated to table string',' The specified tablespace is not allocated to the specified spatial table.',' Allocate the tablespace to the spatial table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13117',' partition string not found',' The specified partition does not exist.',' Verify the name of the partition by checking the Spatial Data option data dictionary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13119',' source and target tablespaces are identical',' Identical source and target tablespaces were specified when trying to move partition.',' Specify different source and target tablespaces if you wish to move a partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13121',' failed to create child partition',' The creation of a child partition failed.',' Check for other errors that accompany this error and correct them first.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13122',' child partition string not found',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13123',' column string is already defined',' The specified column is already defined for the spatial table.',' Use a different column name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13124',' unable to determine column id for column string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13125',' partition key is already set',' A partition key is already set for the spatial table.',' Only one partition key can be specified per spatial table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13126',' unable to determine class for spatial table string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13127',' failed to generate target partition',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13128',' current tiling level exceeds user specified tiling level',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13129',' HHCODE column string not found',' The specified spatial column does not exist.',' Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13135',' failed to alter spatial table',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13136',' null common code generated',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13137',' failed to generate tablespace sequence number',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13138',' could not determine name of object string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13139',' could not obtain column definition for string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13140',' invalid target type',' The specified target type is not valid.',' Substitute a valid target type. Valid target types are TABLE or VIEW.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13141',' invalid RANGE window definition',' The RANGE window specified is not correctly defined.',' A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13142',' invalid PROXIMITY window definition',' The PROXIMITY window specified is not correctly defined.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13143',' invalid POLYGON window definition',' The POLYGON window specified is not correctly defined.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13144',' target table string not found',' This is an internal error.',' Document messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13145',' failed to generate range list',' This is an internal error.',' Document messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13146',' could not find table substitution variable string',' The partition name substitution variable string was not found in the SQL filter.',' The substitution variable string must be in the SQL filter to indicate where that partition name should be placed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13147',' failed to generate MBR',' This is an internal error.',' Document messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13148',' failed to generate SQL filter',' This is an internal error.',' Document messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13149',' failed to generate next sequence number for spatial table string',' This is an internal error.',' Document messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13150',' failed to insert exception record',' Operation failed to insert a record into the exception table.',' Fix any other errors reported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13151',' failed to remove exception record',' Operation failed to insert a record into the exception table.',' Fix any other errors reported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13152',' invalid HHCODE type',' The specified HHCODE type is not valid.',' Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13153',' invalid high water mark specified',' The highwater mark must be greater than or equal to zero.',' Make sure that the highwater mark is an integer greater than or equal to zero.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13154',' invalid precision specified',' The precision specified is out of range.',' The precision must be an integer greater than or equal to zero.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13155',' invalid number of dimensions specified',' The number of dimensions specified is out of range.',' The number of dimensions must be between 1 and 32.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13156',' table to be registered string.string is not empty',' The specified table has rows in it.',' Make sure that the table to be registered is empty.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13157',' Oracle error ORAstring encountered while string',' The specified Oracle error was encountered.',' Correct the Oracle error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13158',' Oracle object string does not exist',' The specified object does not exist.',' Verify that the specified object exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13159',' Oracle table string already exists',' The specified table already exists.',' Drop the specified table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13181',' unable to determine length of column string_SDOINDEX.SDO_CODE',' The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.',' Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13182',' failed to read element string.string.string',' The specified element could not be read from the layer_SDOGEOM table.',' Verify that the specified element exists in the table. Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13183',' unsupported geometric type for geometry string.string',' The geometry type in the layer_SDOGEOM table is unsupported.',' Modify the geometry type to be one of the supported types.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13184',' failed to initialize tessellation package',' Initialization of the tessellation package failed.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13185',' failed to generate initial HHCODE',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13186',' fixed tile size tessellation failed',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13187',' subdivision failed',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13188',' cell decode failed',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13189',' recursive SQL parse failed',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13190',' recursive SQL fetch failed',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13191',' failed to read SDO_ORDCNT value',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13192',' failed to read number of element rows',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13193',' failed to allocate space for geometry',' There was insufficient memory to read the geometry from the database.',' Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13194',' failed to decode supercell',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13195',' failed to generate maximum tile value',' This is an internal error.',' Record the error messages that are returned and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13196',' failed to compute supercell for element string.string.string',' The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.',' Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13197',' element string.string.string is out of range',' 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.',' Verify that the geometry is valid and within the defined domain.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13198',' Spatial Cartridge error: string',' Internal error in some Spatial Cartridge stored procedure.',' Record the sequence of procedure calls or events that preceeded this error and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13199',' string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13200',' internal error [string] in spatial indexing.',' This is an internal error.',' Contact Oracle Support Services with the exact error text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13201',' invalid parameters supplied in CREATE INDEX statement',' An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.',' Check the Spatial Cartridge User Guide for the number, syntax, and semantics of expected parameters for spatial index creation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13202',' failed to create or insert into the SDO_INDEX_METADATA table',' An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.',' Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13203',' failed to read USER_SDO_GEOM_METADATA table',' An error was encountered while trying to read USER_SDO_GEOM_METADATA table.',' Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13204',' failed to create spatial index table',' An error was encountered while trying to create the index table.',' Check that user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13205',' internal error while parsing spatial parameters',' An internal error was encountered while parsing the spatial parameters.',' Check to make sure that the parameters passed in the parameter string are all valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13206',' internal error [string] while creating the spatial index',' An internal error was encountered while creating the spatial index.',' Contact Oracle Support Services with the exact error text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13207',' incorrect use of the [string] operator',' An error was encountered while evaluating the specified operator.',' Check the parameters and the return type of the specified operator.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13208',' internal error while evaluating [string] operator',' An internal error was encountered.',' Contact Oracle Support Services with the exact error text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13209',' internal error while reading SDO_INDEX_METADATA table',' An internal error was encountered while trying to read SDO_INDEX_METADATA table.',' Contact Oracle Support Services. Note this and accompanying error numbers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13210',' error inserting data into the index table',' An error was encountered while trying to insert data into the index table. Likely causes are:',' Check the accompanying error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13211',' failed to tessellate the window object',' An internal error was encountered while trying to tessellate the window object.',' Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY procedure.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13212',' failed to compare tile with the window object',' The spatial relationship between a generated tile and the specified window object could not be determined.',' This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any accompanying errors and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13213',' failed to generate spatial index for window object',' Another error, indicating the real cause of the problem, should accompany this error.',' Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13214',' failed to compute supercell for window object',' The system was unable to compute the minimum bounding tile or supercell for the geometry.',' Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13215',' window object is out of range',' 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.',' Verify that the geometry is valid and within the defined domain.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13216',' failed to update spatial index',' Another error will accompany this message that will indicate the problem.',' Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13217',' invalid parameters supplied in ALTER INDEX statement',' An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.',' Check the Oracle Spatial User''s Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13218',' max number of supported index tables reached for [string] index',' An add_index parameter is passed to ALTER INDEX when the number of existing index tables is already at maximum.',' Delete one of the index tables before adding another index table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13219',' failed to create spatial index table [string]',' An error was encountered while trying to create the index table.',' There is a table in the index''s schema with the specified name. The create index will try to create an index table with this name. Either rename this table or change the name of the index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13220',' failed to compare tile with the geometry',' The spatial relationship between a generated tile and the specified geometry could not be determined.',' This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13220 and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13221',' unknown geometry type in the geometry object',' The SDO_GTYPE attribute in the geometry object contains an invalid value.',' Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial User''s Guide and Reference for an explanation of SDO_GTYPE and its possible values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13222',' failed to compute supercell for geometry in string',' The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.',' Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13223',' duplicate entry for string in SDO_GEOM_METADATA table',' There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table',' Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13224',' specified index name is too long for a spatial index',' An index name was specified which is longer than the supported length of the spatial index name.',' Check the supported size of the index name and reduce the size of the index name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13225',' specified index table name is too long for a spatial index',' An index table name was specified which is longer than the supported length of the spatial index table name.',' Check the supported size of the index table name and reduce the size of the index name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13226',' interface not supported without a spatial index',' The geometry table does not have a spatial index.',' Verify that the geometry table referenced in the spatial operator has a spatial index on it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13227',' SDO_LEVEL values for the two index tables do not match',' The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.',' Verify that two compatible indexes are used for the spatial join operator. Indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13228',' Spatial index create failed due to invalid type',' An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.',' Make sure that the index is created on a column of type SDO_GEOMETRY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13230',' failed to create temporary table [string] during R-tree creation',' The specified temporary table either already exists or there is not enough tablespace.',' Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13231',' failed to create index table [string] during R-tree creation',' The specified index table either already exists or there is not enough tablespace. Otherwise, contact Oracle Support Services.',' Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13232',' failed to allocate memory during R-tree creation',' This feature assumes a minimum of 64 KB memory for bulk creation.',' Create the index for a small subset of the data. Then, use transactional inserts for the rest.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13233',' failed to create sequence number [string] for R-tree',' The specified sequence number exists.',' Delete the sequence object or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13234',' failed to access R-tree-index table [string]',' The index table is either deleted or corrupted.',' Rebuild the index or contact Oracle Support Services with accompanying error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13236',' internal error in R-tree processing: [string]',' An internal error occurred in R-tree processing.',' Contact Oracle Support Services with message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13237',' internal error during R-tree concurrent updates: [string]',' An inconsistency was encountered during concurrent updates possibly due to the use of serializable isolation level.',' Change the isolation level to "read committed" using alter session or contact Oracle Support Services with the message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13239',' sdo_dimensionality not specified during n-d R-tree creation',' An error occurred in reading the dimensionality parameter.',' Check the documentation for a valid range and specify the dimensionality as a parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13240',' specified dimensionality greater than that of the query mbr',' An error occurred because of too few values in query mbr.',' Omit the dimensionality or use the dimensionality of the query.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13241',' specified dimensionality does not match that of the data',' An error occurred because the dimensionality specified in the CREATE INDEX does not match that of the data.',' Change it to the data dimensionality.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13242',' failed to read tolerance values for n-d R-tree',' An error occurred in reading the information for the specified table and column in USER_SDO_GEOM_METADATA table.',' Insert appropriate row specifying the tolerance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13243',' specified operator is not supported for n-d R-tree: [string]',' Currently, an n-d R-tree only supports sdo_filter operator.',' Check the documentation for querytype parameters for sdo_filter or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13249',' string',' An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.',' Contact Oracle Support Services with the exact error text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13250',' insufficient privileges to modify metadata table entries',' The user requesting the operation does not have the appropriate privileges on the referenced tables.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13251',' duplicate entry string in metadata table',' The specified entry already exists in the metadata table.',' Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13260',' layer table string does not exist',' Data migration source table layer_SDOGEOM does not exist.',' Ensure that the specified layername is correct and that the corresponding spatial layer tables exist in the current schema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13261',' geometry table string does not exist',' The specified geometry table does not exist in the current schema.',' Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13262',' geometry column string does not exist in table string',' The specified table does not have a column of type SDO_GEOMETRY.',' Alter or recreate the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13263',' column string in table string is not of type SDO_GEOMETRY',' The column intended for storing the geometry is not of type SDO_GEOMETRY.',' Alter the column definition to be of type SDO_GEOMETRY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13264',' geometry identifier column string does not exist in table string',' The specified table does not contain a GID column.',' Confirm that the GID columnname was correctly specified and that it exists in the specified table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13265',' geometry identifier column string in table string is not of type NUMBER.',' GID column is not of type NUMBER.',' Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13266',' error inserting data into table string',' An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small.',' There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13267',' error reading data from layer table string',' There was an error reading the geometry data from the layer_SDOGEOM table.',' Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, then run VALIDATE_GEOMETRY on the specified layer.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13268',' error obtaining dimension from USER_SDO_GEOM_METADATA',' There is no entry in USER_SDO_GEOM_METADATA for the specified geometry table.',' Insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13269',' internal error [string] encountered when processing geometry table',' An internal error occurred.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13270',' OCI error string',' An OCI error occurred while processing the layer or geometry tables.',' Take the appropriate steps to correct the OCI specific error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13271',' error allocating memory for geometry object',' Insufficient memory.',' Make more memory available to the current session/process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13272',' geometric object string in table string is invalid',' The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY.',' Consult the Oracle Spatial User''s Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13273',' dimension metadata table string does not exist',' The layer_SDODIM table does not exist.',' Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13274',' Operator invoked with non compatible SRIDs',' A Spatial operator was invoked with a window geometry with an SRID and the layer without an SRID or window has no SRID and the layer has an SRID.',' Make sure that the layer and window both have an SRID or they both do not have an SRID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13275',' Spatial index creation failure on unsupported type',' A spatial index create was invoked on a column that is not of type SDO_GEOMETRY.',' Spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13276',' internal error [string] in coordinate transformation',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13278',' failure to convert SRID to native format',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13281',' failure in execution of sql statement to retrieve WKT',' OCI internal error or SRID does not match a table entry.',' Check that a valid SRID is being used.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13282',' failure on initialization of coordinate transformation',' Parsing error on source or destination coordinate system WKT or incompatible coordinate systems.',' Check validity of WKT for table entries and the legitimacy of the requested transformation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13283',' failure to get new geometry object for conversion in place',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13284',' failure to copy geometry object for conversion in place',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13285',' Geometry coordinate transformation error',' A coordinate pair was out of valid range for a conversion/projection.',' Check that data to be transformed is consistent with the desired conversion/projection.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13287',' can''t transform unknown gtype',' A geometry with a gtype of &lt;= 0 was specified for transformation. Only a gtype &gt;= 1 is allowed.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13288',' Point coordinate transformation error',' An internal error while transforming points.',' Check the accompanying error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13290',' The specified unit is not supported',' Spatial function called with an unknown UNIT.',' Check the supported units by Spatial and call the spatial function with the correct UNIT parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13291',' Conversion error between the specified unit and standard unit',' Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.',' Check unit specification and respecify it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13292',' Incorrect ARC_TOLERANCE specification',' 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.',' Check ARC_TOLERANCE specification and make sure it is correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13293',' Cannot specify unit for geometry without a georeferenced SRID',' A Spatial function with unit parameter is called on a geometry without a georeferenced SRID.',' Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13294',' Cannot transform geometry containing circular arcs',' It is impossible to transform a 3-point representation of a circular arc without distortion.',' Make sure a geometry does not contain circular arcs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13295',' Geometry objects are in different coordinate systems',' A Spatial function is called with two geometries with two different SRIDs.',' Transform geometry objects to be in the same coordinate system and call the spatial function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13296',' Incorrect Coordinate System Specification',' Wrong numbers in WKT for Earth radius or flattening for the current SRID.',' Check WKT in CS_SRS table for Earth radius and inverse flattening.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13300',' Single point transform error',' Low level coordinate transformation error trap.',' Check the accompanying error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13303',' failure to retrieve a geometry object from a table',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13304',' failure to insert a transformed geometry object in a table',' OCI internal error.',' Contact Oracle Support Services with the exact error message text.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13330',' invalid MASK',' The MASK you passed to RELATE function is not valid.',' Verify that the mask is not NULL. See the Oracle Spatial User''s Guide and Reference for a list of supported masks.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13331',' invalid LRS segment',' The given LRS segment was not a valid linestring.',' 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 Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or latitude/longitude plus measure).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13332',' invalid LRS point',' Given LRS point was not a point-geometry with measure information.',' Check the given point geometry.A valid LRS point is a point geometry in Oracle Spatial with additional measure dimension.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13333',' invalid LRS measure',' The given measure for linear referencing was out of range.',' Re-define the given measure.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13334',' LRS segments not connected',' The given geometric segments were not connected.',' Check the start/end points of the given geometric segments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13335',' LRS measure information not defined',' The measure information of a given geometric segments was not assigned (IS NULL).',' Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13336',' Failure in converting standard diminfo/geometry to LRS dim/geom',' No room for measure dimension in the given diminfo or the given standard geometry is not a point a linestring.',' Check if the diminfo dimensions are less than 3 or given geometry type is point or linestring.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13337',' failure in concatenating LRS polygons',' LRS concatenation involving LRS polygons is not supported.',' Check geometry and element type to make sure the concatenate operation is not called with a polygon type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13338',' failure in reversing LRS polygon/collection geometry',' Reversing an LRS polygon/collection geometry produces an invalid geometry as this operation is not well defined for polygon geometry.',' Check the geometry type to make sure this operation is called on non polygon type geometry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13339',' LRS Polygon clipping across multiple rings',' Clipping (dynseg) a polygon across multiple rings.',' Polygon clipping only allowed for a single ring.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13340',' a point geometry has more than one coordinate',' A geometry, specified as being a point, has more than one coordinate in its definition.',' A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, then remove the extraneous coordinates from its definition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13341',' a line geometry has less than two coordinates',' A geometry, specified as being a line, has less than two coordinates in its definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13342',' an arc geometry has less than three coordinates',' A geometry, specified as being an arc, has less than three coordinates in its definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13343',' a polygon geometry has less than four coordinates',' A geometry, specified as being a polygon, has less than four coordinates in its definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13344',' an arcpolygon geometry has less than five coordinates',' A geometry, specified as being an arcpolygon, has less than six coordinates in its definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13345',' a compound polygon geometry has less than five coordinates',' A geometry, specified as being a compound polygon, has less than five coordinates in its definition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13346',' the coordinates defining an arc are collinear',' Invalid definition of an arc. An arc is defined using three non-collinear coordinates.',' Alter the definition or the arc or set the SDO_ETYPE or SDO_GTYPE to the line type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13347',' the coordinates defining an arc are not distinct',' Two or more of the three points defining an arc are the same.',' Alter the definition of the arc, ensuring that three distinct coordinate values are used.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13348',' polygon boundary is not closed',' The boundary of a polygon does not close.',' Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13349',' polygon boundary crosses itself',' The boundary of a polygon intersects itself.',' Correct the geometric definition of the object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13350',' two or more rings of a complex polygon touch',' The inner or outer rings of a complex polygon touch.',' All rings of a complex polygon must be disjoint. Correct the geometric description of the object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13351',' two or more rings of a complex polygon overlap',' The inner or outer rings of a complex polygon overlap.',' All rings of a complex polygon must be disjoint. Correct the geometric description of the object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13352',' the coordinates do not describe a circle',' The set of coordinates used to describe a circle are incorrect.',' Confirm that the set of coordinates actually represent points on the circumference of a circle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13353',' ELEM_INFO_ARRAY not grouped in threes',' The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements than expected.',' Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13354',' incorrect offset in ELEM_INFO_ARRAY',' The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY references an invalid array subscript in SDO_ORDINATE_ARRAY.',' Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13355',' SDO_ORDINATE_ARRAY not grouped by number of dimensions specified',' The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.',' Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13356',' adjacent points in a geometry are redundant',' There are repeated points in the sequence of coordinates.',' Remove the redundant point.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13357',' extent type does not contain 2 points',' Extent type should be represented by 2 points: lower left and upper right.',' Confirm that there are only 2 points for extent type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13358',' circle type does not contain 3 points',' Circle type should be represented by 3 distinct points on the circumference.',' Confirm that there are only 3 points for circle type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13359',' extent does not have an area',' The 2 points representing the extent are identical.',' Confirm that the 2 points describing the extent type are distinct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13360',' invalid subtype in a compound type',' This subtype is not allowed within the ETYPE specified.',' Refer to Oracle Spatial User''s Guide and Reference for type definitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13361',' not enough sub-elements within a compound ETYPE',' The compound type declare more sub-elements than actually defined.',' Confirm that the number of sub-elements is consistent with the compound type declaration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13362',' disjoint sub-element in a compound polygon',' Compound polygon must describe an enclosed area.',' Confirm that all sub-elements are connected.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13363',' no valid ETYPE in the geometry',' None of the ETYPEs within the geometry is supported.',' Confirm that there is at least one valid ETYPE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13364',' Layer Dimensionality does not match geometry dimensions',' Spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.',' Make sure that all geometries in a layer have the same dimensions and they match the dimensions in the SDO_DIM_ARRAY object for the layer in USER_SDO_GEOM_METADATA.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13365',' Layer SRID does not match geometry SRID',' Spatial layer has a geometry with a different SRID than the SRID specified for the layer.',' Make sure that all geometries in a layer have the same SRID and the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13366',' Invalid combination of interior exterior rings',' In the Spatial geometry, interior and exterior rings are not used consistently.',' Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13367',' Wrong orientation for interior/exterior rings',' In a spatial geometry, the exterior and/or interior rings are not oriented correctly.',' The exterior rings should be oriented counter clock-wise and interior rings should be oriented clock wise.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13368',' Simple Polygon type has more than one exterior ring',' In a polygon type geometry, there is more than one exterior ring.',' Set the type to be multi-polygon if more than one exterior is present in the geometry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13369',' Invalid value for etype in the 4 digit format',' A 4 digit etype for non polygon type element is used or the orientation is not a valid orientation for interior/exterior rings of the polygon.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13370',' failure in applying 3D LRS functions',' Only Non-geodetic 3D linestring geometry (made of line segments) are supported for 3D LRS package.',' Check the geometry and element types and SRID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13371',' invalid position of measure dimension',' LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in dim_info_array.',' Check geometry gtype and its dim_info_array.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13372',' failure in modifying metadata for a table with spatial index',' Modifying the metadata after the index is created will cause inconsistency between geometry gtype and diminfo.',' Modify(or Prepare) metadata before creating index on sdo_geometry column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13373',' Element of type Extent is not supported for Geodetic data',' Element type extent for a polygon geometry is not supported for geodetic data.',' Convert the extent type polygon to a regular 5 point polygon and set etype accordingly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13374',' SDO_MBR not supported for geodetic data',' The SDO_MBR functionality is not supported for geodetic data.',' Find an alternative function that can be used in this context.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13375',' The layer is of type [string] while geometry inserted has type [string]',' The layer has a type that is different or inconsistent with the type of the current geometry.',' Change the geometry type to agree with the layer type or change the layer type to agree with the geometry type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13376',' Invalid type name specified for layer_gtype parameter',' An invalid type name is specified for the layer gtype constraint.',' Consult the Oracle Spatial User''s Guide and Reference to get a list of valid layer gtypes that can be used in defining a layer gtype constraint.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13377',' Invalid combination of elements with orientation',' An element of the geometry has orientation specified while some other element has no orientation specified (4 digit etype).',' Make sure all the polygon elements have orientation specified using the 4 digit etype notation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13378',' Invalid index for element to be extracted',' An invalid (or out of bounds) index was specified for extracting an element from a geometry.',' Make sure the parameters to the extract function are in the valid range for the given geometry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13379',' Invalid index for sub-element to be extracted',' An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.',' Make sure the parameters to the extract function are in the valid range for the given geometry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13400',' Oracle GeoImage internal error, arguments: [string], [string], [string], [string], [string]',' This is an internal Oracle GeoImage error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13401',' unsupported geoimage format',' The GeoImage format is not supported.',' Confirm that the GeoImage format is valid and supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13402',' NULL destination',' The object specified as the destination is NULL.',' Confirm that the object specified as the destination is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13403',' NULL source geometry',' The source GeoImage has a NULL geometry.',' Verify that the geometry of the source GeoImage is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13404',' not a local source',' An attempt has been made to modify a GeoImage which is not stored in the database.',' Import the GeoImage in order to modify it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13405',' NULL source',' The object specified as the source is NULL.',' Confirm that the object specified as the source is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13406',' unsupported image processing command [string]',' The image processing command specified is not supported for a GeoImage.',' Consult the Oracle interMedia User''s Guide and Reference to verify which image processing commands are supported within an Oracle GeoImage method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13407',' unrecognized space type qualifier [string]',' The GeoImage space type qualifier is invalid.',' Use a valid space type qualifier (RASTER or MODEL).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13408',' NULL table name',' The table name parameter is NULL.',' Verify that the parameter used for the table name is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13409',' Oracle table "string" does not exist.',' The table specified does not exist.',' Verify that the table name used is valid and the table exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13410',' NULL column name',' The column name parameter is NULL.',' Verify that the parameter used for the column name is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13411',' Oracle column "string" does not exist.',' The column specified does not exist.',' Verify that the column name used is valid and the column exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13412',' invalid ROWID',' The ROWID value used is not valid.',' Verify that the ROWID value used is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13413',' could not select the GeoImage for initialization',' The GeoImage in the table could not be selected.',' Verify that the GeoIMage is present in the table and the supplied parameters are valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13414',' could not update the table containing the GeoImage',' The table containing the GeoImage could not be updated.',' Verify that the table exists and is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13415',' invalid domain',' The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain.',' Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13416',' invalid geometry, arguments [string]',' The SDO_GEOMETRY value used is not valid.',' Verify that the SDO_GEOMETRY is valid. Consult the Oracle Spatial User''s Guide and Reference for a list of valid geometries.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13417',' undefined raster to model space transformation',' The raster to model space transformation associated with a GeoImage is undefined.',' Verify that the GeoImage format is valid and that the particular operation is supported for that format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13418',' undefined model to raster space transformation',' The model to raster space transformation associated with a GeoImage is undefined.',' Verify that the GeoImage format is valid and that the particular operation is supported for that format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13419',' invalid latitude value',' A latitude value outside the valid range [-90,90] has been used.',' Verify that the GeoImage geometry definition is within the domain.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13420',' invalid model to raster space transformation',' The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated.',' Verify that the transformation is supported and that the GeoImage format is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13421',' invalid raster to model space transformation',' The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated.',' Verify that the transformation is supported and that the GeoImage format is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13422',' uninitialized source',' The LOB used for the source is not initialized.',' Verify that the source is properly initialized.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13423',' empty source',' The LOB used for the source is empty.',' Verify that the source is properly initialized and data has been imported into it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13424',' uninitialized destination',' The LOB used for the destination is not initialized.',' Verify that the destination is properly initialized.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13425',' empty destination',' The LOB used for the destination is empty.',' Verify that the destination is properly initialized and data has been imported into it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13426',' unsupported raster origin',' The raster origin specified is not supported.',' Verify that the origin specified is supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13427',' unknown raster origin',' The value specified for the raster origin is invalid.',' Verify that the value used to specify the raster origin is valid and supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13428',' source does not exist',' The source does not exist or cannot be accessed.',' Verify that the source specification is correct and accessible.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13429',' operation "string" not supported on GeoImage type "string"',' The specified operation is not supported on the particular geoimage type.',' Verify that the operation is supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13430',' model coordinate system not supported',' The model specified for the definition of the coordinate system is not supported.',' Verify that the model value is correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13433',' NULL crop geometry',' The geometry used to crop a GeoImage is NULL.',' Verify that the geometry used for the crop operation is not NULL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13442',' invalid scaling parameters [string] [string]',' The parameters used in the scale operation are invalid.',' Verify that the scaling parameters are greater than zero.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13443',' unrecognized scale mode [string]',' The scale mode used in the scale operation is invalid.',' Consult the Oracle interMedia User''s Guide and Reference for a list of valid scale mode qualifiers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13451',' unsupported conversion format [string]',' The format specified for conversion is invalid or unsupported.',' Verify that the conversion format specified is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13461',' invalid tag/key [string]',' The tag or key is invalid.',' Verify that the format version is supported or the format is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13462',' invalid tie point',' One of the tie points is invalid.',' Verify that the tie points used are valid (for example all raster tie points are &gt;= 0).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13463',' unsupported GeoTIFF geometry definition',' The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported.',' Verify that the GeoTIFF format version is supported and the format is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13464',' unsupported conversion',' The format specified for conversion is not supported. In GeoTIFF, only a limited number of tags/keys combinations are supported for conversion.',' Verify that the GeoTIFF format version is supported and conversion to the desired format is available.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-13465',' invalid destination window',' The window specified as destination in the command is not valid.',' Verify that the window definition is correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14000',' only one LOCAL clause may be specified',' CREATE INDEX statement contained more than one LOCAL clause.',' Specify LOCAL option at most once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14001',' LOCAL clause contradicts previosly specified GLOBAL clause',' CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.',' Specify LOCAL or GLOBAL clause, but not both.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14002',' only one GLOBAL clause may be specified',' CREATE INDEX statement contained more than one GLOBAL clause.',' Specify GLOBAL option at most once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14003',' GLOBAL clause contradicts previosly specified LOCAL clause',' CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.',' Specify GLOBAL or LOCAL clause, but not both.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14004',' missing PARTITION keyword',' Keyword PARTITION missing.',' Supply missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14005',' missing RANGE keyword',' Keyword RANGE missing.',' Supply missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14006',' invalid partition name',' A partition name of the form identifier is expected but not present.',' Enter an appropriate partition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14007',' missing LESS keyword',' Keyword LESS missing.',' Supply missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14008',' missing THAN keyword',' Keyword THAN missing.',' Supply missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14009',' partition bound may not be specified for a LOCAL index partition',' 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.',' Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14010',' this physical attribute may not be specified for an index partition',' 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.',' Remove invalid option(s) from the list of physical attributes of an index partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14011',' names assigned to resulting partitions must be distinct',' Names of partitions resulting from splitting of an existing table or index partition are not distinct.',' Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14012',' resulting partition name conflicts with that of an existing partition',' 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.',' Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14013',' duplicate partition name',' Name of a partition of a table or index being created is not unique.',' Rename partition(s) to ensure that their names are unique among partitions of the table or index being created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14014',' maximum number of partitioning columns is 16',' Number of columns in a partitioning column list exceeded the legal limit of 16.',' Modify partitioning column list so that it consists of at most 16&nbsp;columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14015',' too many partition descriptions',' CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 65535.',' Reduce the number of partitions to not exceed 65535.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14016',' underlying table of a LOCAL partitioned index must be partitioned',' An attempt was made 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.',' Correct the statement and re-enter it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14017',' partition bound list contains too many elements',' Partition bound list contained more elements than there are partitioning columns.',' Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14018',' partition bound list contains too few elements',' Partition bound list contained fewer elements than there are partitioning columns.',' Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14019',' partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE',' Partition bound list contained an element of invalid type (that is, not a number, non-empty string, datetime or interval literal, or MAXVALUE).',' Ensure that all elements of partition bound list are of valid type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14020',' this physical attribute may not be specified for a table partition',' 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.',' Remove invalid option(s) from the list of physical attributes of a table partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14021',' MAXVALUE must be specified for all columns',' In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns.',' Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14022',' creation of LOCAL partitioned cluster indices is not supported',' An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal.',' Remove LOCAL along with partition_descriptions, if any, from the CREATE INDEX statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14023',' creation of GLOBAL partitioned cluster indices is not supported',' An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal.',' Remove PARTITION BY RANGE clause along with partition_descriptions from the CREATE INDEX statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14024',' number of partitions of LOCAL index must equal that of the underlying table',' An attempt was made to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.',' Correct the CREATE INDEX statement to specify a correct number of partitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14025',' PARTITION may not be specified for a materialized view or a materialized view log',' PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log.',' Ensure that a definition of a MATERIALIZED VIEW does not include invalid options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14026',' PARTITION and CLUSTER clauses are mutually exclusive',' Definition of a table contained both PARTITION and CLUSTER clauses which is illegal.',' Remove one of the conflicting clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14027',' only one PARTITION clause may be specified',' CREATE TABLE statement contained more than one PARTITION clause.',' Specify PARTITION option at most once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14028',' missing AT or VALUES keyword',' Keyword AT or VALUES is missing.',' Supply missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14029',' GLOBAL partitioned index must be prefixed',' The partitioning columns of a global partitioned index did not contain a prefix of the index''s key columns.',' Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14030',' non-existent partitioning column in CREATE TABLE statement',' Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created.',' Ensure that all columns in the partitioning column list are columns of the table being created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14031',' partitioning column may not be of type LONG or LONG RAW',' Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal.',' Ensure that no partitioning column is of type LONG or LONG RAW.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14032',' partition bound of partition number string is too high',' 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.',' Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14036',' partition bound value too large for column',' Length of partition bound value is longer than that of the corresponding partitioning column.',' Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14037',' partition bound of partition "string" is too high',' 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.',' Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14038',' GLOBAL partitioned index must be prefixed',' An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal.',' If a non-prefixed index is desired, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14039',' partitioning columns must form a subset of key columns of a UNIQUE index',' An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal.',' If you want 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''s partitioning columns form a subset of its key columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14041',' partition bound may not be specified for resulting partitions',' 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.',' Remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14042',' partition bound may not be specified for a partition being moved, modified or rebuilt',' 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.',' Remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14043',' only one partition may be added',' ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added.',' Ensure that the statement contains exactly one partition definition and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14044',' only one partition may be moved',' ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved.',' Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14045',' only one partition may be modified',' ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified.',' Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14046',' a partition may be split into exactly two new partitions',' 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.',' Ensure that the statement describes exactly two partition into which an existing partition is to be split.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14047',' ALTER TABLE|INDEX RENAME may not be combined with other operations',' ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal.',' Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14048',' a partition maintenance operation may not be combined with other operations',' The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.',' Ensure that a partition maintenance operation is the sole operation specified in an 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) can be combined.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14049',' invalid ALTER TABLE MODIFY PARTITION option',' 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.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14050',' invalid ALTER INDEX MODIFY PARTITION option',' An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14051',' invalid ALTER MATERIALIZED VIEW option',' An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14052',' partition-extended table name syntax is disallowed in this context',' An attempt was made to use partition-extended table name syntax in illegal context (that is, not in FROM-clause or INSERT, DELETE, or UPDATE statement).',' Avoid use of partition-extended table name in contexts other those mentioned above.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14053',' illegal attempt to modify string in string statement',' Certain attributes of objects (for example, tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes.',' Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14054',' invalid ALTER TABLE TRUNCATE PARTITION option',' Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE.',' Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14055',' keyword REBUILD in ALTER INDEX REBUILD must immediately follow index_name',' ALTER INDEX statement contained REBUILD keyword following some index attributes (for example, INITRANS).',' Ensure that keyword REBUILD immediately follows the name of the index being altered.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14056',' partition number string: sum of PCTUSED and PCTFREE may not exceed 100',' 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.',' Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14057',' partition "string": sum of PCTUSED and PCTFREE may not exceed 100',' 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.',' Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14058',' partition number string: INITRANS value must be less than MAXTRANS value',' 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.',' Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14059',' partition "string": INITRANS value must be less than MAXTRANS value',' 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.',' Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14060',' data type or length of a table partitioning column may not be changed',' 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.',' Avoid modifying data type and/or length of table partitioning column(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14061',' data type or length of an index partitioning column may not be changed',' 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.',' Avoid modifying data type and/or length of index partitioning column(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14062',' one or more of table''s partitions reside in a read-only tablespace',' 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.',' Avoid performing aforementioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14063',' Unusable index exists on unique/primary constraint key',' An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable.',' Drop the existing index or rebuild it using ALTER INDEX REBUILD.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14064',' Index with Unusable partition exists on unique/primary constraint key',' An attempt was made 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.',' Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14065',' ALLOCATE STORAGE may not be specified for a partitioned table',' User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14066',' illegal option for a non-partitioned index-organized table',' An attempt was made to issue a CREATE or ALTER TABLE command on a non-partitioned index-organized table, 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.',' Remove the illegal options from the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14067',' duplicate TABLESPACE_NUMBER specification',' TABLESPACE_NUMBER clause was specified more than once for a table, an index, or an index partition.',' Correct the code generating text of CREATE INDEX statement sent to the slaves.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14068',' TABLESPACE and TABLESPACE_NUMBER may not be both specified',' Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, an index, or an index partition.',' Correct the code generating text of CREATE INDEX statement sent to the slaves.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14069',' invalid TABLESPACE_NUMBER value',' The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF.',' Correct the code generating text of CREATE INDEX statement sent to the slaves.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14070',' option may be specified only for partitioned indices or with REBUILD',' User issued ALTER INDEX statement 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.',' Remove illegal option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14071',' invalid option for an index used to enforce a constraint',' 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.',' Choose one of the valid index options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14072',' fixed table may not be truncated',' An attempt was made to truncate a fixed table which is illegal.',' Ensure that the table being truncated is not a fixed table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14073',' bootstrap table or cluster may not be truncated',' An attempt was made to truncate a bootstrap table or cluster which is illegal.',' Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14074',' partition bound must collate higher than that of the last partition',' Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table''s last partition, which is illegal.',' Ensure that the partition bound of the partition to be added collates higher than that of the table''s last partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14075',' partition maintenance operations may only be performed on partitioned indices',' Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless.',' Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14076',' DROP/SPLIT PARTITION may not be applied to a LOCAL index partition',' An attempt was made to drop or split a partition of a LOCAL index which is illegal.',' Ensure that the index named in such statement is a GLOBAL partitioned index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14078',' you may not drop the highest partition of a GLOBAL index',' An attempt was made to drop highest partition of a GLOBAL index, which is illegal.',' Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14079',' illegal option for a partition marked Index Unusable',' ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal.',' Ensure that only valid options are specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14080',' partition cannot be split along the specified high bound',' An attempt was made 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.',' 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 of a partition immediately preceding the one to be split.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14081',' new partition name must differ from the old partition name',' User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of the partition being renamed.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14082',' new partition name must differ from that of any other partition of the object',' User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of some existing partition of the object.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14083',' cannot drop the only partition of a partitioned table',' A drop partition command is being executed when there is only one partition in the table.',' Ensure that there is at least one partition. Drop table to remove all partitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14084',' you may specify TABLESPACE DEFAULT only for a LOCAL index',' An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal.',' Re-enter the statement without TABLESPACE DEFAULT clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14085',' partitioned table cannot have column with LONG datatype',' An attempt was made to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14086',' a partitioned index may not be rebuilt as a whole',' An attempt was made to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal.',' Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and re-create the entire index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14094',' invalid ALTER TABLE EXCHANGE PARTITION option',' Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEXES][{WITH|WITHOUT} VALIDATION].',' Ensure that no options besides INCLUDING INDEXES or EXCLUDING INDEXES are specified with ALTER TABLE EXCHANGE PARTITION.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14095',' ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table',' The table in the EXCHANGE operation is either clustered or partitioned.',' Ensure that the table with which the partition is being exchanged for is not partitioned or clustered.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14096',' tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns',' The two tables specified in the EXCHANGE have different number of columns.',' Ensure that the two tables have the same number of columns with the same type and size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14097',' column type or size mismatch in ALTER TABLE EXCHANGE PARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size.',' Ensure that the two tables have the same number of columns with the same type and size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14098',' index mismatch for tables in ALTER TABLE EXCHANGE PARTITION',' The two tables specified in the EXCHANGE have indexes which are not equivalent.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14099',' all rows in table do not qualify for specified partition',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14100',' partition extended table name cannot refer to a remote object',' An attempt was made to use partition-extended table name syntax in conjunction with remote object name which is illegal.',' Correct the statement and re-enter it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14101',' partition extended table name cannot refer to a synonym',' An attempt was made to use partition-extended table name syntax in conjunction with synonym name which is illegal.',' Correct the statement and re-enter it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14102',' only one LOGGING or NOLOGGING clause may be specified',' LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.',' Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14103',' LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE',' A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14104',' RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices',' CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14105',' RECOVERABLE/UNRECOVERABLE may not be specified in this context',' RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14106',' LOGGING/NOLOGGING may not be specified for a clustered table',' An attempt was made to specify LOGGING or NOLOGGING clause in CREATE TABLE or ALTER TABLE statement involving a clustered table.',' Remove offending clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14107',' partition specification is required for a partitioned object',' parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects.',' Supply the missing parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14108',' illegal partition-extended table name syntax',' Partition to be accessed may only be specified using its name. An attempt was made to use a partition number or a bind variable.',' Modify the statement to refer to a partition using its name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14109',' partition-extended object names may only be used with tables',' An attempt was made to use a partition-extended object name with an object which is not a table.',' Avoid using partition-extended name syntax with objects which are not tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14110',' partitioning column may not be of type ROWID',' Partitioning column specified by the user was of type ROWID, which is illegal.',' Ensure that no partitioning column is of type ROWID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14111',' creation of GLOBAL partitioned indices on clustered tables is not supported',' An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.',' Remove PARTITION BY RANGE() clause along with (partition_list) to create a GLOBAL non-partitioned index on a clustered table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14112',' RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition',' Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal.',' Remove offending clause. Use LOGGING or NOLOGGING instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14113',' partitioned table cannot have column with LOB datatype',' An attempt was made to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14114',' partitioned table cannot have column with object, REF, nested table, array datatype',' An attempt was made 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14115',' partition bound of partition number string is too long',' 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).',' Change representation of a partition high bound to bring its length within legal limit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14116',' partition bound of partition "string" is too long',' 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).',' Change representation of a partition high bound to bring its length within legal limit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14117',' partition resides in offlined tablespace',' 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.',' Bring the tablespace online before attempting the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14118',' CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them.',' Ensure that the two tables do not have CHECK constraint defined on any column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14119',' specified partition bound is too long',' 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).',' Change representation of a partition high bound to bring its length within legal limit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14120',' incompletely specified partition bound for a DATE column',' An attempt was made to use a date expression whose format does not fully (that is, 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).',' Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (that is, day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (that is, including the century) specification of the year, use TO_DATE() (for example, TO_DATE(''01-01-1999'', ''MM-DD-YYYY'') to fully express the desired date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14121',' MODIFY DEFAULT ATTRIBUTES may not be combined with other operations',' ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14122',' only one REVERSE or NOREVERSE clause may be specified',' Both REVERSE and NOREVERSE were specified in CREATE INDEX statement.',' Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14123',' duplicate NOREVERSE clause',' NOREVERSE was specified more than once in ALTER INDEX statement.',' Remove all but one of the NOREVERSE clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14124',' duplicate REVERSE clause',' REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements.',' Remove all but one of the REVERSE clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14125',' REVERSE/NOREVERSE may not be specified in this context',' REVERSE/NOREVERSE clause is not allowed in this context.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14126',' only a parallel_clause may follow description(s) of resulting partitions',' 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.',' Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14128',' FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14129',' INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints',' Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command.',' Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14130',' UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14131',' enabled UNIQUE constraint exists on one of the tables',' 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.',' Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14132',' table cannot be used in EXCHANGE',' 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:',' Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14133',' ALTER TABLE MOVE cannot be combined with other operations',' An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY.',' Make sure that MOVE is the only operation specified in ALTER TABLE statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14134',' indexes cannot use both DESC and REVERSE',' An attempt was made to make a reverse index with some index columns marked DESC.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14135',' a LOB column cannot serve as a partitioning column',' An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column.',' Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14136',' ALTER TABLE EXCHANGE restricted by fine-grained security',' User doing exchange does not have full table access due to VPD policies.',' Grant exempt priviliges to this user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14150',' missing SUBPARTITION keyword',' Keyword SUBPARTITION missing.',' Supply the missing parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14151',' invalid table partitioning method',' Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or composite range/hash (R+H).',' Specify one of valid partitioning methods.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14152',' invalid number of partitions specified in PARTITIONS clause',' number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-65535).',' Specify a number between 1 and 65535 in the number-of-partitions clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14153',' only one of STORE IN or partition_description clause may be specified',' Both STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command.',' Remove one of offending clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14154',' only one of STORE IN or subpartition_description clause may be specified',' 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.',' Remove one of offending clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14155',' missing PARTITION or SUBPARTITION keyword',' Expected either the PARTITION or SUBPARTITION keyword but neither was supplied.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14156',' invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause',' Number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-65535).',' Specify a number between 1 and 65535 in the number-of-subpartitions clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14157',' invalid subpartition name',' A subpartition name of the form identifier is expected but not present.',' Enter an appropriate subpartition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14158',' too many subpartition descriptions',' CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 65535.',' Reduce the number of subpartitions to not exceed 65535.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14159',' duplicate subpartition name',' Name of a subpartition of a table or index being created is not unique.',' Rename the subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14160',' this physical attribute may not be specified for a table subpartition',' An unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option.',' Remove the invalid option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14161',' subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100',' 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.',' Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14162',' subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100',' 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.',' Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14163',' subpartition number string: INITRANS value must be less than MAXTRANS value',' The 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14164',' subpartition "string": INITRANS value must be less than MAXTRANS value',' The 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14165',' MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations',' An ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14166',' missing INTO keyword',' Keyword INTO missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14167',' only one subpartition may be moved',' ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved.',' Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14168',' only one subpartition may be modified',' ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified.',' Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14169',' invalid ALTER TABLE MODIFY SUBPARTITION option',' An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14170',' cannot specify partition_description clause in CREATE TABLE|INDEX',' 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.',' Remove one of offending clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14171',' cannot specify subpartition_description clause in CREATE|ALTER TABLE',' User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified subpartition_description clause which is illegal.',' Remove one of offending clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14172',' invalid ALTER TABLE EXCHANGE SUBPARTITION option',' Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION].',' Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14173',' illegal subpartition-extended table name syntax',' Subpartition to be accessed may only be specified using its name. An attempt was made to use a subpartition number or a bind variable.',' Modify statement to refer to a subpartition using its name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14174',' only a parallel_clause may follow COALESCE PARTITION|SUBPARTITION',' ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional parallel_clause. No partition/subpartition attributes may be specified.',' Ensure that no partition/subpartition attribute was specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14175',' a subpartition maintenance operation may not be combined with other operations',' An ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (for example, MOVE SUBPARTITION) with some other operation (for example, MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14176',' this attribute may not be specified for a hash partition',' An invalid option was encountered while parsing physical attributes of a partition of a table partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions.',' Remove the invalid option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14177',' STORE-IN (Tablespace list) can only be specified for a LOCAL index on a table which is hash or composite partitioned',' STORE-IN (Tablespace list) clause was used while creating a local index on a table which is range or list partitioned.',' Do not use the STORE_IN (Tablespace list) clause while creating a local index on range or list partitioned table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14183',' TABLESPACE DEFAULT can be specified only for Composite LOCAL index',' An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash-partitioned LOCAL index object, which is illegal.',' Replace TABLESPACE DEFAULT with TABLESPACE ts_name or remove it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14185',' incorrect physical attribute specified for this index partition',' An unexpected option was encountered while parsing physical attributes of a local index partition; valid options for range 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.',' Remove the invalid option(s) from the list of physical attributes of an index partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14186',' number of sub-partitions of LOCAL index must equal that of the underlying table',' An attempt was made to create a LOCAL partitioned index with a number of subpartitions which is different from that of the underlying table.',' Correct the CREATE INDEX statement to specify a correct number of subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14187',' partitioning method for LOCAL index is inconsistent with that of the underlying table',' An attempt was made to create a LOCAL partitioned index that is not equipartitioned with the underlying table. The partitioning types are mismatched.',' Correct the CREATE INDEX statement to ensure that the index partitioning method is consistent with that of the base table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14188',' sub-partitioning columns must form a subset of key columns of a UNIQUE index',' An attempt was made to create a UNIQUE partitioned index whose subpartitioning columns do not form a subset of its key columns which is illegal.',' If you want 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''s subpartitioning columns form a subset of its key columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14189',' this physical attribute may not be specified for an index subpartition',' An unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option.',' Remove the invalid option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14190',' only one ENABLE/DISABLE ROW MOVEMENT clause can be specified',' One of the following:',' Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and then reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14191',' ALLOCATE STORAGE may not be specified for Composite Range partitioned object',' User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14192',' cannot modify physical index attributes of a Hash index partition',' An attempt was made to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a hash-partitioned index.',' Remove the physical attributes one is trying to modify.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14193',' invalid ALTER INDEX MODIFY SUBPARTITION option',' An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14194',' only one subpartition may be rebuilt',' ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt.',' Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14195',' ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object',' User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14251',' Specified subpartition does not exist',' Subpartition not found for the object.',' Retry with correct subpartition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14252',' invalid ALTER TABLE MODIFY PARTITION option for a Hash partition',' Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a hash partition.',' Specify only legal options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14253',' table is not partitioned by Composite Range method',' 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.',' Ensure that the table is partitioned by composite range method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14254',' cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table',' User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a range or composite range partitioned table which is illegal.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14255',' table is not partitioned by Range or Composite Range or List method',' ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by range, list, or composite range method.',' Ensure that the table is partitioned by range, list, or composite range method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14256',' invalid resulting partition description(s)',' 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.',' Remove the invalid clause(s), or ensure that the table is partitioned by composite range method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14257',' cannot move partition other than a Range or Hash partition',' An attempt was made to move a partition that is not a range or hash partition which is illegal.',' Specify MOVE PARTITION for a range or hash partition only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14258',' invalid partition description',' 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.',' Remove the invalid clause(s), or ensure that the table is partitioned by composite range/hash method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14259',' table is not partitioned by Hash method',' ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method.',' Specify a valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14260',' incorrect physical attribute specified for this partition',' 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.',' Remove the invalid option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14261',' partition bound may not be specified when adding this Hash partition',' User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a hash-partitioned table which is illegal.',' Remove the VALUES LESS THAN clause from the description of partition being added.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14262',' new subpartition name must differ from the old subpartition name',' User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of the subpartition being renamed.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14263',' new subpartition name must differ from that of any other subpartition of the object',' User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of some existing subpartition of the object.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14264',' table is not partitioned by Composite Range method',' The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method.',' Ensure that the table is partitioned by Composite method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14265',' data type or length of a table subpartitioning column may not be changed',' 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.',' Avoid modifying data type and/or length of table subpartitioning column(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14266',' data type or length of an index subpartitioning column may not be changed',' 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.',' Avoid modifying data type and/or length of index subpartitioning column(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14267',' cannot specify PARALLEL clause when adding a (Composite) Range partition',' User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a range or composite range partition which is illegal.',' Remove the PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14268',' subpartition ''string'' of the partition resides in offlined tablespace',' 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.',' Bring tablespace online before attempting the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14269',' cannot exchange partition other than a Range or Hash partition',' User attempt to exchange a partition with a non-partitioned table but the specified partition is not a range or hash partition which is illegal.',' Specify EXCHANGE PARTITION for a range or hash partition only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14270',' table is not partitioned by Range or Hash or List method',' The table in ALTER TABLE MODIFY PARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by range or hash method which is illegal.',' Ensure that the table is partitioned by range or hash method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14271',' table is not partitioned by Composite Range method',' 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.',' Ensure that the table is partitioned by composite range method.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14272',' only a partition with higher bound can be reused',' User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.',' Use the higher-bound partition to be the resulting partition or specify a new partition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14273',' lower-bound partition must be specified first',' User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal.',' Specify lower-bound partition then higher-bound partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14274',' partitions being merged are not adjacent',' User attempt to merge two partitions that are not adjacent to each other which is illegal.',' Specify two partitions that are adjacent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14275',' cannot reuse lower-bound partition as resulting partition',' User attempt to reuse lower-bound partition of the partitions being merged which is illegal.',' Specify new resulting partition name or reuse the higher-bound partition only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14276',' EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table',' The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned.',' Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14277',' tables in EXCHANGE SUBPARTITION must have the same number of columns',' The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns.',' Ensure that the two tables have the same number of columns with the same type and size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14278',' column type or size mismatch in EXCHANGE SUBPARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size.',' Ensure that the two tables have the same number of columns with the same type and size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14279',' index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION',' The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14280',' all rows in table do not qualify for specified subpartition',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14281',' CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them.',' Ensure that the two tables do not have CHECK constraint defined on any column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14282',' FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14283',' UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14284',' one or more of table''s subpartitions reside in a read-only tablespace',' 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.',' Avoid performing aforementioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14285',' cannot COALESCE the only partition of this partitioned table',' A COALESCE PARTITION command was issued when there is only one partition in the table which is illegal.',' Ensure that there is at least one partition. Drop table to remove all partitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14286',' cannot COALESCE the only subpartition of this table partition',' A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal.',' Ensure that there is at least one subpartition. Drop partition to remove all subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14287',' cannot REBUILD a partition of a Composite Range partitioned index',' An attempt was made to rebuild a partition of a composite range-partitioned index which is illegal.',' REBUILD the index partition, a subpartition at a time.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14288',' index is not partitioned by Composite Range method',' 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.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14289',' cannot make local index partition of Composite Range partitioned table unusable',' An attempt was made to rebuild a partition of a composite range partitioned index which is illegal.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14290',' PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION',' The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14291',' cannot EXCHANGE a composite partition with a non-partitioned table',' A composite partition can only be exchanged with a partitioned table.',' Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14292',' Partitioning type of table must match subpartitioning type of composite partition',' When exchanging a partitioned table with a composite partition, the partitioning type of the table must match the subpartitioning type of the composite partition.',' Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14293',' Number of partitioning columns does not match number of subpartitioning columns',' 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.',' Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14294',' Number of partitions does not match number of subpartitions',' 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.',' Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14295',' column type or size mismatch between partitioning columns and subpartitioning columns',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14296',' Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14297',' Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION',' The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14298',' LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14301',' table-level attributes must be specified before partition-level attributes',' 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.',' Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14302',' only one list of added-LOB-storage-clauses can be specified in a statement',' 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.',' Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14303',' partitions or subpartitions are not in the right order',' Descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently from the DDL order of partitions or subpartitions.',' Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14304',' List partitioning method expects a single partitioning column',' Number of columns in a partitioning column list exceeded the legal limit of 1 for list partitioned objects.',' Modify partitioning column list so that it consists of at most 1 column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14305',' List value ''string'' specified twice in partition ''string''',' A list value cannot be specified more that once.',' Remove one of the specifications of the value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14306',' List value ''string'' specified twice in partitions ''string'', ''string''',' A list value cannot be specified more that once.',' Remove one of the specifications of the value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14307',' partition contains too many list values',' Partition list contains more than 65535 list values.',' Reduce the number of values to not exceed 65535 values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14308',' partition bound element must be one of: string, datetime or interval literal, number, or NULL',' Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL).',' Ensure that all elements of partition bound list are of valid type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14309',' Total count of list values exceeds maximum allowed',' Partitioned object contains more than 65535 list values.',' Reduce number of values to less than 65535.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14310',' VALUES LESS THAN or AT clause cannot be used with List partitioned tables',' VALUES LESS THAN or AT clause can be used only with range partitioned tables.',' Use VALUES (&lt;value list&gt;) clause with list partitioned tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14311',' Expecting VALUES LESS THAN or AT clause',' VALUES (&lt;value list&gt;) clause can be used only with list partitioned tables.',' Use VALUES LESS THAN clause with range partitioned tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14312',' Value string already exists in partition string',' One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition.',' Remove the duplicate value from the statement and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14313',' Value string does not exist in partition string',' One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition.',' Remove the value from the statement and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14314',' resulting List partition(s) must contain atleast 1 value',' After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value.',' Ensure that each of the resulting partitions contains at least 1 value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14315',' cannot merge a partition with itself',' The same partition name was specified twice for the merge operation.',' Re-submit operation with 2 distinct partition names.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14316',' table is not partitioned by List method',' ALTER TABLE ADD|DROP VALUES can only be performed on list partitioned objects.',' reissue the command against a list partitoned object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14317',' cannot drop the last value of partition',' ALTER TABLE DROP VALUES tried to drop the last value of the partition.',' Cannot execute the command, unless two or more values exist for partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14318',' DEFAULT partition must be last partition specified',' A partition description follows the one describing the default partition.',' Ensure that the DEFAULT partition is the last partition description.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14319',' DEFAULT cannot be specified with other values',' DEFAULT keyword has been specified along with other values when specifying the values for a list partition.',' Ensure that if DEFAULT is specified, it is the only value specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14320',' DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT',' DEFAULT keyword has been specified when performing an ADD VALUES, DROP VALUES, SPLIT partition, or subpartition.',' Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operations.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14321',' cannot add/drop values to DEFAULT partition',' An ADD/DROP VALUES operation is being performed on the default partition.',' Ensure that ADD/DROP VALUES is not performed on the DEFAULT partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14322',' DEFAULT partition already exists',' A partition already exists with DEFAULT value.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14323',' cannot add partition when DEFAULT partition exists',' An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists.',' Issue a SPLIT of the DEFAULT partition instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14324',' values being added already exist in DEFAULT partition',' An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition.',' Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14400',' inserted partition key does not map to any partition',' 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.',' Do not insert the key. Or, add a partition capable of accepting the key. Or, add values matching the key to a partition specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14401',' inserted partition key is outside specified partition',' 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.',' Do not insert the key or insert it in another partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14402',' updating partition key column would cause a partition change',' An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14403',' cursor invalidation detected after getting DML partition lock',' Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14404',' partitioned table contains partitions in a different tablespace',' An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14405',' partitioned index contains partitions in a different tablespace',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14406',' updated partition key is beyond highest legal partition key',' 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.',' Do not update the key. Or, add a partition capable of accepting the key.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14407',' partitioned table contains subpartitions in a different tablespace',' An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14408',' partitioned index contains subpartitions in a different tablespace',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14409',' inserted partition key is outside specified subpartition',' 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.',' Do not insert the key or insert it in another subpartition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14450',' attempt to access a transactional temp table already in use',' An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session.',' Do not attempt to access the temporary table until the concurrent transaction has committed or aborted.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14451',' unsupported feature with temporary table',' An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14452',' attempt to create, alter or drop an index on temporary table already in use',' An attempt was made to create, alter or drop an index on temporary table which is already in use.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14453',' attempt to use a LOB of a temporary table, whose data has already been purged',' 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 committed or aborted, table was truncated or session which created this LOB has ended.',' This LOB locator is invalid and cannot be used.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14454',' attempt to reference temporary table in a referential integrity constraint',' An attempt was made to reference temporary table in a referential integrity constraint. This is not supported.',' Use triggers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14455',' attempt to create referential integrity constraint on temporary table',' An attempt was made to create a referential integrity constraint on a temporary table. This is not supported.',' Use triggers.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14456',' cannot rebuild index on a temporary table',' An attempt was made to rebuild an index on a temporary table.',' The index data is anyway lost at end of session/transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14457',' disallowed VARRAY and Nested Table column in a Temporary table',' An attempt made to create a VARRAY or Nested Table column in a temporary table. This is not supported.',' Do not specify these datatypes for temporary tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14458',' attempt was made to create a temporary table with INDEX organization',' An attempt was made to create an Index Organized Temporary table. This is not supported.',' Create the table with HEAP organization and the primary key.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14459',' missing GLOBAL keyword',' Keyword GLOBAL is missing while creating temporary table.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14460',' only one COMPRESS or NOCOMPRESS clause may be specified',' COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified.',' Specify each desired COMPRESS or NOCOMPRESS clause option only once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14500',' LOCAL option not valid without partition name',' Incorrect syntax specified.',' Retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14501',' object is not partitioned',' Table or index is not partitioned. Invalid syntax.',' Retry the command with correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14503',' only one partition name can be specified',' More than one partition name has been specified for analyze.',' Specify one partition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14504',' syntax not supported for analyze',' A partition/subpartition number or bind variable has been used.',' Specify a valid partition/subpartition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14505',' LOCAL option valid only for partitioned indexes',' Incorrect syntax specified.',' Retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14506',' LOCAL option required for partitioned indexes',' Incorrect syntax specified.',' Retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14507',' partition corrupt. all rows do not fall within partition bounds',' The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation.',' Delete rows in partition which do not qualify.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14508',' specified VALIDATE INTO table not found',' The specified table either does not exist or user does not have the proper privileges.',' Specify the correct table to use.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14509',' specified VALIDATE INTO table form incorrect',' The specified table does not have the proper field definitions.',' Specify the correct table to use. See UTLVALID.SQL for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14510',' can specify VALIDATE INTO clause only for partitioned tables',' The VALIDATE INTO has been specified for a non-partitioned table or cluster or index.',' Use the syntax correctly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14511',' cannot perform operation on a partitioned object',' An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.',' Retry the command with correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14512',' cannot perform operation on a clustered object',' An attempt was made to perform an operation that is not allowed on clustered tables or indexes.',' Retry the command with correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14513',' partitioning column may not be of object datatype',' Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal.',' Ensure that no partitioning column is an object datatype.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14514',' LOCAL option not valid without subpartition name',' Incorrect syntax specified.',' Retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14515',' only one aubpartition name can be specified',' More than one subpartition name has been specified for analyze.',' Specify one subpartition name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14516',' subpartition corrupt. all rows do not fall within subpartition bounds',' The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation.',' Delete rows in subpartition which do not qualify.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14517',' subpartition of index ''string.string'' is in unusable state',' An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation.',' REBUILD the unusable index subpartition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14518',' partition contains rows corresponding to values being dropped',' A table partition contains rows for the values being dropped.',' DELETE all rows for the values being dropped and reissue statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14519',' Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14520',' Tablespace string block size [string] does not match existing object block size [string]',' 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.',' Specify a tablespace of the same block size as the partitioned object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14521',' Default tablespace string block size [string] for string string does not match existing string block size [string]',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14522',' Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14523',' Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]',' 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.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14551',' cannot perform a DML operation inside a query',' DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14552',' cannot perform a DDL, commit or rollback inside a query or DML',' 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.',' Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14553',' cannot perform a lob write operation inside a query',' A LOB write operation cannot be performed inside a query or a PDML slave.',' 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14601',' Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template',' Cannot specify these clauses while specifying a template.',' Correct the subpartition template clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14602',' SUBPARTITION TEMPLATE is legal only for a composite partitioned table',' SUBPARTITION TEMPLATEs can only be specified for composite partitioned tables.',' Do not use SUBPARTITION TEMPLATEs on non-partitioned or non-composite partitioned tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14603',' [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables',' This syntax is valid only if subpartitioning dimension is hash.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14604',' During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified',' Once a subpartition template has been specified during CREATE TABLE, it is illegal to specify SUBPARTITIONS or STORE IN anywhere else.',' Remove either SUBPARTITIONS or STORE IN, or remove the SUBPARTITION TEMPLATE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14605',' Name missing for subpartition / lob segment in template',' A subpartition / lob segment was not specified a name in the template descriptions.',' All subpartitions / lob segments must have names specified in the template.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14606',' Tablespace was specified for previous subpartitions in template but is not specified for string',' Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.',' Either specify tablespaces for all or for none of the subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14607',' Tablespace was not specified for previous subpartitions in template but is specified for string',' Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.',' Either specify tablespaces for all or for none of the subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14608',' Tablespace was specified for the previous lob segments of column string in template but is not specified for string',' Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.',' Either specify tablespaces for all or for none of the lob segments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14609',' Tablespace was not specified for the previous lob segments of column string in template but is specified for string',' Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.',' Either specify tablespaces for all or for none of the lob segments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14610',' Lob attributes not specified for lob column string for subpartition string',' Lob attributes of a column must be specified for all subpartitions or must not be specified at all.',' Ensure lob attributes of a column are specified for all subpartitions or not specified at all.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14611',' Duplicate subpartition name string in template',' A subpartition name cannot be duplicated within the template.',' Rename one of the subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14612',' Duplicate lob segment name string for lob column string in template',' Two lob segments of the same column were given the same name in the template.',' Rename one of the lob segments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14613',' Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed',' Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier.',' Shorten either the partition name or the template name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14614',' List value ''string'' specified twice in subpartition ''string''',' A list value cannot be specified more than once.',' Remove one of the specifications of the value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14615',' List value ''string'' specified twice in subpartitions ''string'', ''string''',' A list value cannot be specified more than once.',' Remove one of the specifications of the value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14616',' table is not subpartitioned by List method',' A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD | DROP VALUES or ALTER TABLE DROP | SPLIT | MERGE SUBPARTITION can only be performed on List subpartitioned objects.',' Re-issue the command against a List subpartitioned object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14617',' cannot add/drop values to DEFAULT subpartition',' An ADD/DROP VALUES operation is being performed on the default subpartition.',' Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14618',' cannot drop the last value of subpartition',' ALTER TABLE DROP VALUES tried to drop the last value of the subpartition.',' Cannot execute the command, unless two or more values exist for subpartition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14619',' resulting List subpartition(s) must contain at least 1 value',' After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value.',' Ensure that each of the resulting subpartitions contains at least 1 value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14620',' DEFAULT subpartition already exists',' A subpartition already exists with DEFAULT value.',' Remove the DEFAULT value from the specified list.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14621',' cannot add subpartition when DEFAULT subpartition exists',' An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists.',' Issue a SPLIT of the DEFAULT subpartition instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14622',' Value string already exists in subpartition string',' One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition.',' Remove the duplicate value from the statement and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14623',' Value string does not exist in subpartition string',' One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition.',' Remove the value from the statement and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14624',' DEFAULT subpartition must be last subpartition specified',' A subpartition description follows the one describing the default subpartition.',' Ensure that the DEFAULT subpartition is the last subpartition description.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14625',' subpartition contains rows corresponding to values being dropped',' Table subpartition contains rows for the values being dropped.',' DELETE all rows for the values being dropped and re-issue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14626',' values being added already exist in DEFAULT subpartition',' An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition.',' Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14627',' Invalid operation was specified on a GLOBAL partitioned index',' An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index.',' Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14628',' specification of bounds is inconsistent with LIST method',' An operation such as ALTER TABLE SPLIT | ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method.',' Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14629',' cannot drop the only subpartition of a partition',' A drop subpartition command is being executed when there is only one subpartition in the partition.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14630',' subpartition resides in offlined tablespace',' 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 indexes defined on it or is referenced by a constraint.',' Bring the tablespace online before attempting the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14631',' the partition bounds do not match the subpartition bounds of the partition',' 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.',' Ensure that the bounds describing partitions in the partitioned table are the same as the bounds of the subpartitions in the composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14632',' cannot specify PARALLEL clause when adding a List subpartition',' An ALTER TABLE ADD SUBPARTITION statement was issued with a PARALLEL clause for a List subpartition of a Range/List partitioned object. This is not allowed.',' Remove the PARALLEL clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14633',' Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table',' The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.',' Remove clause and re-issue the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14634',' Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table',' During a split or a merge of a partition of a range list partitioned table, you cannot specify any subpartitioning information for the resulting partitions.',' Remove all subpartitioning information from the DDL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14635',' only one resulting subpartition can be specified for MERGE SUBPARTITIONS',' ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE.',' Ensure that the statement describes exactly one subpartition as the target that needs to be MERGEd.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14636',' only 2 resulting subpartition can be specified for SPLIT SUBPARTITION',' ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT.',' Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14637',' cannot merge a subpartition with itself',' The same subpartition name was specified twice for the merge operation.',' Re-submit operation with 2 distinct subpartition names within the same composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14638',' cannot MERGE subpartitions in different Range Composite partitions',' An attempt was made to MERGE subpartitions in different Range Composite partitions.',' Re-issue the command after ensuring that the 2 subpartitions being merged lie within the same composite partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14639',' SUBPARTITIONS clause can be specified only for Hash, Composite Range Hash table/partition',' Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method.',' Re-issue 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.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14640',' DROP/SPLIT SUBPARTITION may not be applied to a LOCAL index subpartition',' User attempted to drop or split a subpartition of a LOCAL index which is illegal.',' Issue the statement on a table subpartition instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14641',' STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition',' Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed.',' Re-issue the statement after removing the STORE-IN clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14642',' Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION',' 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.',' Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14643',' Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION',' 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.',' 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, then perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14644',' table is not subpartitioned by Hash method',' A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects.',' Re-issue the command against a Hash subpartitioned object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-14645',' STORE IN clause cannot be specified for Range List objects',' A STORE IN clause was specified for Range List partitioned object.',' Re-issue the command after removing the STORE IN clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16000',' database open for read-only access',' The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.',' In order to modify the database, it must first be shut down and reopened for read-write access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16001',' database already open for read-only access by another instance',' The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.',' This instance must be opened for read-write access, or all other instances must first be shut down and reopened for read-only access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16002',' database already open for read-write access by another instance',' The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.',' This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read-write access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16003',' standby database is restricted to read-only access',' To ensure its integrity, a standby database can only be opened for read-only access.',' reissue the ALTER DATABASE OPEN specifying READ ONLY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16004',' backup database requires recovery',' The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.',' Perform the necessary recovery and re-open for read-only access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16005',' database requires recovery',' The database requires recovery, and therefore cannot be opened for read-only access by this instance.',' Perform the necessary recovery and re-open for read-only access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16006',' audit_trail destination incompatible with database open mode',' The AUDIT_TRAIL initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.',' When the database is opened for read-only access, the AUDIT_TRAIL initialization parameter can only be set to "OS" or "NONE" (FALSE).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16007',' invalid backup control file checkpoint',' 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.',' First open the database for read-write access which will result in a valid control file checkpoint. Then re-open the database for read-only access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16008',' indeterminate control file checkpoint',' 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.',' First open the database for read-write access which will result in a valid control file checkpoint. Then re-open the database for read-only access.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16009',' remote archive log destination must be a STANDBY database',' 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.',' Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16010',' remote archive log destination database is opened for update',' The database associated with the archive log destination service name is opened for update access. Remote archival of redo log files to standby databases opened for update access is not allowed.',' Shut down the standby destination instance and re-open for read-only access or simply leave the standby instance mounted and unopened.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16011',' Archivelog Remote File Server process in Error state',' 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.',' Correct the problem at the standby database site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16012',' Archive log standby database identifier mismatch',' 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.',' Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.');
