Oracle7 Server Messages Go to Product Documentation Library
Library		 Go to books for this product
Product		 Go to Contents for this book
Contents		 Go to Index
Index


Go to previous file in sequence Go to next file in sequence

Server Messages ORA-00000 to ORA-25699

00000-00100: Oracle Server

ORA-00000 normal, successful completion

Cause:An operation has completed normally, having met no exceptions.
Action:No action required.
ORA-00001 unique constraint table.column violated

Cause:An update or insert statement attempted to insert a duplicate key.
Action:Either remove the unique restriction or do not insert the key.

ORA-00017 session requested to set trace event

Cause:The current session was requested to set a trace event by another session.
Action:This is used internally; no action required.
ORA-00018 maximum number of sessions exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of sessions is specified by the initialization parameter SESSIONS. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the SESSIONS parameter in the initialization parameter file, and restart Oracle.
ORA-00019 maximum number of session licenses exceeded

Cause:All licenses are in use.
Action:Call customer support before increasing the number of session licenses.
ORA-00020 maximum number of processes num exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of processes is specified by the initialization parameter PROCESSES. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the PROCESSES parameter in the initialization parameter file, and restart Oracle.
ORA-00021 session attached to some other process; cannot switch session

Cause:The user session is currently being used by someone else.
Action:Do not execute calls in a user session concurrently.
ORA-00022 invalid session id; access denied

Cause:Either the session specified does not exist, or the caller does not have the privilege to access it.
Action:Specify a valid session ID. This requires ownership of the session id or the CHANGE_USER privilege.
ORA-00023 session references process' private memory; cannot detach session

Cause:An attempt was made to detach the current session, which contains references to the process' private memory.
Action:A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links or cursors. Detaching a session with operating system privileges is always disallowed.
ORA-00024 logins from more than one process not allowed in single-process mode

Cause:An attempt was made to log in more than once from different processes after Oracle had been started in single-process mode.
Action:When Oracle is running in single-process mode, out of the previous process before trying to log in from another one.
ORA-00025 failed to allocate num

Cause:An allocation failed because Oracle ran out of memory.
Action:Restart Oracle with a larger SGA heap.
ORA-00026 missing or invalid session id

Cause:The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified.
Action:Retry the command with a valid session ID.
ORA-00027 cannot kill current session

Cause:An attempt was made to kill the current session with the ALTER SYSTEM KILL SESSION command.
Action:If it is necessary to kill the current session, do so from another session.
ORA-00028 your session has been killed

Cause:A privileged user killed the session and it is no longer logged in to the database.
Action: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.
ORA-00029 session is not a user session

Cause:The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started.
Action:Retry the command with a valid session ID.
ORA-00030 user session ID does not exist

Cause:The user session ID no longer exists, probably because the session was logged out.
Action:Use a valid session ID.
ORA-00031 session marked for kill

Cause:The session specified in the 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.
Action:No action required. The session will be killed when the operation is completed. Further executions of the ALTER SYSTEM KILL SESSION command may cause the session to be killed sooner.
ORA-00033 current session has empty migration password

Cause:An attempt was made to detach or clone the current session, and it has an empty migration password. This is not allowed.
Action:Create the session with a non-empty migration password.
ORA-00034 cannot COMMIT or ROLLBACK in current PL/SQL session

Cause:An attempt was made to ROLLBACK from a PL/SQL object (procedure, function, package) in a session where COMMIT and ROLLBACK are disabled by an ALTER SESSION DISABLE COMMIT IN PROCEDURE statement.
Action:Enable COMMITs from PL/SQL in this session or do not attempt a COMMIT or ROLLBACK when disabled.
ORA-00035 LICENSE_MAX_USERS cannot be less than current number of users

Cause:Specified value for LICENSE_MAX_USERS is less than current number of users.
Action:Check the license limit and drop extra users or purchase more licenses.
ORA-00050 O/S error occurred while obtaining an enqueue. See O/S error

Cause:Could not obtain the operating system resources necessary for an Oracle enqueue. This most often occurs when the user resource quota on the operating system is too low.
Action:Look up the operating system error in the operating system-specific Oracle documentation and perform the needed action.
ORA-00051 time-out occurred while waiting for resource

Cause:This message is usually caused by an instance that has terminated abnormally.
Action:Restart any non-recovered instances.
ORA-00052 maximum number of enqueue resources num exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of enqueue resources is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.
ORA-00053 maximum number of enqueues exceeded

Cause:An operation requested a resource that was unavailable and the enqueue list for the resource had reached its maximum length. If a request is made for a resource that is unavailable, the request is enqueued to wait for the resource. The number of requests that may be queued for a given resource is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests may be added to the enqueue list.
Action:Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.
ORA-00054 resource busy and acquire with NOWAIT specified

Cause:The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.
Action:Try the command after a few minutes or enter the command without the NOWAIT keyword.
ORA-00055 maximum number of DML locks exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of DML locks is specified by the DML_LOCKS parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the DML_LOCKS parameter in the initialization parameter file, and restart Oracle.
ORA-00056 DDL lock on object "str.name" already held in an incompatible mode

Cause:The attempted lock is incompatible with the DDL lock already held on the object. This usually occurs when attempting to drop a table that has parse locks.
Action:Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation.
ORA-00057 maximum number of temporary table locks exceeded

Cause:The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action:Increase the TEMPORARY_TABLE_LOCKS parameter and restart Oracle.
ORA-00058 DB_BLOCK_SIZE must be num to mount this database not num

Cause:The DB_BLOCK_SIZE parameter value in the initialization parameter file used to start a database does not match the value used when that database was created.

Action:For one of the above causes, either
ORA-00059 maximum number of DB_FILES exceeded

Cause:An unavailable resource was requested. The maximum number of datafiles is specified by the DB_FILES parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action:Try again when the resource is freed. If this message occurs often, Oracle must be shut down and restarted after increasing the DB_FILES parameter in the initialization parameter file. If the DB_FILES parameter cannot be changed because it is already set to the MAXDATAFILES parameter value, set at database creation, you must create a new control file.
ORA-00060 deadlock detected while waiting for resource

Cause: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.
Action:Either

ORA-00061 another instance has a different DML_LOCKS setting

Cause:The shared instance being started is using DML locks and the running instances are not, or vice versa.
Action:Either

ORA-00062 DML full-table lock cannot be acquired; DML_LOCKS is 0

Cause:The instance was started with the initialization parameter DML_LOCKS set to zero, but the statement being executed needs a full-table lock (S, X, or SRX).
Action:Set DML_LOCKS to a non-zero value, restart the instance, and re-enter the statement.
ORA-00063 LOG_FILES initialization parameter exceeded

Cause:The value of the LOG_FILES initialization parameter was exceeded.
Action:Increase the value of LOG_FILES and warm start Oracle. The value needs to be as large as the highest number log that currently exists rather than just the count of the logs that exist. If this parameter cannot be increased because it would exceed the MAXLOGFILES set at database creation, you must create a new control file first.
ORA-00064 object is too large to allocate on this O/S num, num

Cause:The initialization parameter DB_BLOCK_SIZE is set to a value that calls for more contiguous space than can be allocated on the operating system being used.
Action:Reduce the value of DB_BLOCK_SIZE so that the requested contiguous space is within the capacity of the operating system.
ORA-00065 initialization of FIXED_DATE failed

Cause:An attempt was made to enter a fixed date string that was not in the proper format.
Action:Enter the date string using the format YYYY-MM-DD:HH24:MI:SS.
ORA-00066 LOG_FILES is num but needs to be num to be compatible

Cause:The maximum number of redo log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action:Check that the LOG_FILES initialization parameter is the same for all instances.
ORA-00067 invalid value num for parameter num, must be at least num

Cause:The value for the initialization parameter is invalid.
Action:Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.
ORA-00068 invalid value num for parameter num, must be between num and num

Cause:The value for the initialization parameter is invalid.
Action:Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.
ORA-00069 cannot acquire lock -- table locks disabled for name

Cause:A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are LOCK TABLE, ALTER TABLE ... ADD (...), and so on.
Action:Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command.
ORA-00070 command name is not valid

Cause:An invalid debugger command was specified.
Action:Type HELP to see the list of available commands.
ORA-00071 process number must be between 1 and num

Cause:An invalid process number was specified.
Action:Specify a valid process number.
ORA-00072 process \

Cause:An invalid process was specified.
Action:Specify a valid process.
ORA-00073 command name takes between num1 and num2 argument(s)

Cause:An incorrect number of arguments was specified.
Action:Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.
ORA-00074 no process has been specified

Cause:No debug process has been specified.
Action:Specify a valid process.
ORA-00075 process \

Cause:The specified process was not logged on to the current instance.
Action:Specify a valid process.
ORA-00076 dump name not found

Cause:An attempt was made to invoke a dump which doesn't exist.
Action:Type DUMPLIST to see the list of available dumps.
ORA-00077 dump name is not valid

Cause:An attempt was made to invoke an invalid dump.
Action:Try another dump.
ORA-00078 cannot dump variables by name

Cause:An attempt was made to dump a variable by name on a system which does not support this feature.
Action:Try the PEEK command.
ORA-00079 variable var not found

Cause:An attempt was made to dump a variable which doesn't exist.
Action:Use a valid variable name.
ORA-00080 invalid global area specified by level num

Cause:An attempt was made to dump an invalid global area.
Action:Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra + level> to dump global area as well as <extra> bytes for every pointer; <extra> must be a multiple of 4.
ORA-00081 address range [num1, num2) is not readable

Cause:An attempt was made to read/write an invalid memory address range.
Action:Try another address or length.
ORA-00082 memory size of num is not in valid set of [1], [2], [4]num1num2num3num4num5

Cause:An invalid length was specified for the POKE command.
Action:Use a valid length (either 1, 2, 4, or possibly 8).
ORA-00083 warning: possibly corrupt SGA mapped

Cause:Even though there may be SGA corruptions, the SGA was mapped.
Action:Use the "dumpsga" command to dump the SGA.
ORA-00084 global area must be PGA, SGA, or UGA

Cause:An attempt was made to dump an invalid global area.
Action:Specify either PGA, SGA, or UGA.
ORA-00085 current call does not exist

Cause:An invalid attempt was made to dump the current call heap.
Action:Wait until the process starts a call.
ORA-00086 user call does not exist

Cause:An invalid attempt was made to dump the user call heap.
Action:Wait until the process starts a call.
ORA-00097 use of Oracle SQL feature not in SQL92 compliance level

Cause:You tried to use an Oracle SQL feature that is not compliant with the SQL92 standard.
Action:Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance.
ORA-00100 no data found

Cause:An application made reference to unknown or inaccessible data.
Action:Handle this condition within the application or make appropriate modifications to the application code.
NoteIf the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.

00101-00149: Multi-threaded Server

ORA-00100 no data found

Cause:An application made reference to unknown or inaccessible data.
Action:Handle this condition within the application or make appropriate modifications to the application code.
NoteIf the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403. will be generated instead of ORA-00100.
ORA-00101 invalid specification for initialization parameter MTS_DISPATCHERS

Cause:The syntax for the MTS_DISPATCHERS parameter is incorrect.
Action:Enter the MTS_DISPATCHERS parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance.
ORA-00102 network protocol str cannot be used by the dispatchers

Cause:The network specified in MTS_DISPATCHERS initialization parameter does not have the functionality required by the dispatchers.
Action:Refer to your Oracle7 operating system-specific documentation for network protocols supported by the dispatchers.
ORA-00103 invalid network protocol; reserved for use by dispatchers

Cause:The network specified in SQL*Net CONNECT string is reserved for use by the dispatchers.
Action:Specify other network protocols in the CONNECT string.
ORA-00104 deadlock detected; all public servers blocked waiting for resource

Cause:This message occurs when a client locks a resource and the maximum number of shared servers are taken by other clients who are requesting a locked resource. The original client is unable to get a shared server and cannot release the lock on the resource.
Action:The system automatically starts up new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_SERVERS. If this problem occurs frequently, ensure more shared servers will be available at the next restart of the instance by increasing the value of the initialization parameter MTS_SERVERS or MTS_MAX_SERVERS.
ORA-00105 dispatching mechanism not configured to support network protocol

Cause:The ALTER SYSTEM SET MTS_DISPATCHERS command was used to alter a set of dispatchers for a network protocol that is not specified in the initialization parameter file.
Action:Do either of the following:

ORA-00106 cannot startup/shutdown database when connected to a dispatcher

Cause:An attempt was made to start up or shut down an instance while connected to a shared server process via a dispatcher.
Action:Reconnect to the database using a dedicated server.
ORA-00107 failed to connect to network listener process

Cause:Usually caused by the fact that the network listener process has not been started.
Action:Check for the following:

ORA-00108 failed to set up dispatcher to accept connection asynchronously

Cause:The network protocol used by the dispatcher does not support asynchronous operations.
Action:Contact customer support.
ORA-00111 Warning: maximum number of servers is only num; adding num servers

Cause:An attempt was made to start more shared server processes than the number allowed by the initialization parameter MTS_MAX_SERVERS. The actual number of shared servers started is specified in the message.
Action:If more shared server processes are required, increase the initialization parameter MTS_MAX_SERVERS and restart the instance.
ORA-00112 only created up to num maximum specified dispatchers

Cause:An attempt was made to start up more dispatchers than the maximum number specified by the initialization parameter MTS_MAX_DISPATCHERS.
Action:If more dispatchers are required, increase MTS_MAX_DISPATCHERS, restart the instance, and add dispatchers using the ALTER SYSTEM MTS_DISPATCHERS command.
ORA-00113 protocol name string is too long

Cause:A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long.
Action:Use a valid protocol name for the MTS_DISPATCHERS initialization parameter.
ORA-00114 missing value for initialization parameter MTS_SERVICE

Cause:There is no value for the MTS_SERVICE initialization parameter, nor for the DB_NAME parameter.
Action:Add an MTS_SERVICE or DB_NAME definition to the initialization parameter file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE is explicitly specified.
ORA-00115 connection refused; dispatcher connection table is full

Cause:A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
Action:Connect to a different dispatcher or use a dedicated server.
ORA-00116 MTS_SERVICE name is too long

Cause:The service name specified in the MTS_SERVICE initialization parameter is too long.
Action:Use a shorter name for the MTS_SERVICE value (maximum is 255 characters).
ORA-00117 value out of range for the MTS_SERVERS system parameter

Cause:The value of the MTS_SERVERS parameter is incorrect.
Action:The MTS_SERVERS parameter must be from 0 to MTS_MAX_SERVERS.
ORA-00118 value out of range for MTS_DISPATCHERS system parameter

Cause:The value of the MTS_DISPATCHERS parameter is incorrect.
Action:The sum of all MTS_DISPATCHERS values must be from 0 to MTS_MAX_DISPATCHERS.
ORA-00119 invalid specification for system parameter MTS_LISTENER_ADDRESS

Cause:The syntax for the MTS_LISTENER_ADDRESS is incorrect.
Action:Refer to the Oracle7 Server Administrator's Guide for the correct syntax.
ORA-00120 dispatching mechanism not enabled or installed

Cause:Either the dispatching mechanism is not enabled or the Oracle executable image is not installed with the dispatching mechanism.
Action:Refer to the Oracle7 Server Administrator's Guide and your Oracle7 operating system-specific documentation for procedures for starting and configuring the dispatcher processes.
ORA-00121 MTS_SERVERS specified without MTS_DISPATCHERS

Cause:A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition for MTS_DISPATCHERS was specified. If no value is specified for MTS_DISPATCHERS, shared servers will not be used.
Action:Add a definition for MTS_DISPATCHERS in the INIT.ORA file. If you do not intend to use shared servers, remove the MTS_SERVERS definition.
ORA-00122 cannot initialize network configuration

Cause:Oracle could not initialize SQL*Net Version 2.
Action:See accompanying messages.
ORA-00123 idle public server terminating

Cause:Too many idle servers were waiting on the common queue.
Action:This is used internally, no action required.
ORA-00124 MTS_DISPATCHERS specified without MTS_MAX_SERVERS

Cause:A definition for MTS_DISPATCHERS was specified in the INIT.ORA file, but MTS_MAX_SERVERS was specified as zero.
Action:Specify MTS_MAX_SERVERS to be greater than zero.

00150-00159: Oracle*XA

ORA-00150 duplicate transaction ID

Cause:Attempted to start a new transaction with an ID already in use by an existing transaction.
Action:Check that your application uses a valid transaction ID.
ORA-00151 invalid transaction ID

Cause:The specified transaction ID does not correspond to an existing valid transaction.
Action:Check that your application uses a valid transaction ID.
ORA-00152 current session does not match requested session

Cause:The current session is not the same as the session that was passed into a UPIXADO() call.
Action:Check that your application is coded correctly.

00200-00249: Control Files

ORA-00200 cannot create control file name

Cause:The control file cannot be created, usually because of insufficient disk storage or filename conflicts.
Action:Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
ORA-00201 control file version num incompatible with Oracle version num

Cause:The control file was created by a different version of Oracle.
Action:Either

ORA-00202 control file: name

Cause:This message reports the name of the file involved in other messages.
Action:See the associated messages for a description of the problem.
ORA-00203 using the wrong control files

Cause:The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but are not the same files. The most likely cause is that one instance is using a backup of the control file. If you want to use a backed up control file, you can recover using the USING BACKUP CONTROLFILE option.
Action:Check that all instances are using the correct version of the control file.
ORA-00204 error in reading control file name block num, # blocks num

Cause:A disk read-failure occurred while attempting to read the specified control file. The block location of the failure is given.
Action:Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating system reasons for Oracle's inability to read the disk or control file. Refer to the Oracle7 Server Administrator's Guide for information about recovering from the loss of a control file. See also your operating system-specific Oracle documentation.
ORA-00205 error in identifying control file name

Cause:The system could not find a control file of the specified name and size.
Action:Either

ORA-00206 error in writing control file name block num, # blocks num

Cause:A disk write-failure occurred while attempting to write to the specified control file. The block location of the failure is given.
Action:Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating system reasons for Oracle's inability to write to the disk or control file. See the Oracle7 Server Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.
ORA-00207 control files are not for the same database

Cause:The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. The most likely cause is either that one of the mounts used the wrong control file or there are two databases with the same name.
Action:Check that the control file is for the correct database and 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 filename 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 filename in the initialization parameter file.
ORA-00208 number of control file names exceeds limit of num

Cause:An attempt was made to use more control files than Oracle supports. The limit is given in the message.
Action:Shut down Oracle, reduce the number of control filenames specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.
ORA-00209 block size num exceeds limit of num bytes

Cause:A block size larger than that allowed by the operating system was specified.
Action:Reduce the block size to the amount specified in the message and try again.
ORA-00210 cannot open control file name

Cause:The system was unable to open a control file.
Action:Check that the control file exists, that the storage device is online, and that the file is not locked by some other program and try again. Also, check to see that the operating system limit on the number of open files per process has not been exceeded.

ORA-00211 control file name does not match previous control files

Cause:The specified control file is from another database.
Action:Locate and specify the correct control file for this database, then retry the operation. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control filename 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, create another copy of the control file, and include the new filename in the initialization parameter file.
ORA-00212 block size num below minimum required size of num bytes

Cause:The specified block size is too small. Additional space is needed for system overhead.
Action:Specify a larger block size and retry the operation.
ORA-00213 cannot reuse control file name; old file size num, num required

Cause:To reuse a control file, it must be the same size as the previous one used.
Action:In the CREATE DATABASE statement, do not specify REUSE.
ORA-00214 control file name version num inconsistent with file name version num

Cause:An inconsistent set of control files, datafiles, and redo log files was used.
Action: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.
ORA-00215 must be at least one control file

Cause:No control file was specified, or the control file specified does not exist.
Action:Specify at least one valid control file and retry the operation.
ORA-00216 unable to determine physical block size for control file name

Cause:An error occurred while determining the physical block size of the specified control file.
Action:Check the accompanying message stack for more detailed information.
ORA-00217 control file name physical block size num inconsistent with num

Cause:The physical block size of the operating system is inconsistent with the block size of the control file.
Action:The system will not operate with invalid control files. Either restore a valid control file or recreate the database. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control filename 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 with a new filename in the initialization parameter file.
ORA-00218 control file name was created with block size num now is num

Cause:The physical block size, stored in the control file header, was different in physical block size returned by the O/S. This usually indicates that the control file was corrupted.
Action:Restore a good copy of the control file.

ORA-00219 required control file size num larger than maximum num

Cause:The CREATE DATABASE statement specified a combination of initialization parameters that results in the control file exceeding the internal maximum size.
Action:You must recreate the database. In the CREATE DATABASE statement, use a value less than the maximum permissible value for clauses such as MAXDATAFILES and MAXLOGFILES as described in the Oracle7 Server Administrator's Guide.
ORA-00220 control file name not mounted by first instance

Cause:The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.
Action:Find and use the correct control file.
ORA-00221 error on write to control file

Cause:An error occurred when writing to one or more of the control files.
Action:See accompanying messages.
ORA-00222 control file may not be queried using dispatcher

Cause:Attempted to use client process connected to dispatcher. This is not allowed for queries to control file fixed tables due to the memory requirements.
Action:Connect directly to the instance, then execute the query.
ORA-00223 conversion datafile is invalid or incorrect version

Cause:A Version 6 to Oracle7 conversion datafile contains invalid data or was created with an old version of the migration utility.
Action:Regenerate the conversion file with the correct version of the migration utility or use the correct file for converting the database.
ORA-00224 the specified file is not a control file

Cause:The file specified in the initialization parameter file is not a control file.
Action:Edit the initialization parameter file and specify the correct control filename.
ORA-00225 expected size num of controlfile name differs from actual size num

Cause:The expected size of the control file as stored in its header was different than the actual operating system file size of the control file. This usually indicates that the control file was corrupted.
Action:Restore a good copy of the control file.

00250-00299: Archiving and Recovery

ORA-00250 archiver not started

Cause:An attempt was made to stop automatic archiving, but the archiver process was not running.
Action:No action required.
ORA-00252 log name of thread num is empty, cannot archive

Cause:The specified redo log was not used since it was introduced to the database. It is also possible that the instance died during a log switch, and the log was left empty.
Action:Empty logs do not need to be archived. Do not attempt to archive the redo log file.
ORA-00253 limit of num exceeded by length num of archive string name

Cause:The specified archive string is too long. The limit is given in the message.
Action:Use a shorter string, making sure not to exceed the given limit and try again.
ORA-00254 error in archive control string archive_log_location

Cause:The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.
Action:Specify a valid location name.
ORA-00255 error archiving log name of thread num, sequence # num

Cause:An error occurred during archiving.
Action:Check the accompanying message stack for more detailed information.

ORA-00256 error occurred in translating archive text string str

Cause:An error occurred while translating the archive control string.
Action:Check the accompanying message stack for more detailed information.
ORA-00257 archiver is stuck. CONNECT INTERNAL only, until freed

Cause:The ARCH process received an error while trying to archive a redo log file. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is that the destination device is out of space to store the redo log file.
Action: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.
ORA-00258 manual archiving in NOARCHIVELOG mode must identify log

Cause:An attempt was made to archive a redo log file manually without specifying the sequence number, group number, or filename while the database was in NOARCHIVELOG mode.
Action:The name, group number, or thread and sequence number of redo log files must be specified to archive redo log files manually while the database is in NOARCHIVELOG mode.
ORA-00259 log name of open thread num is the current log, cannot archive

Cause:An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for generation of redo entries.
Action:Force a log switch in the instance where the thread is open. If no instances are open, open the database so instance recovery can recover the thread.
ORA-00260 cannot find online log sequence num for thread num

Cause:The log sequence number specified in the ARCHIVE statement does not match any of the online logs for the specified thread. This can result from any of the following situations:

Action:Check the ARCHIVE statement; then specify a valid log sequence number.
ORA-00261 log name of thread num is being archived or modified, cannot archive

Cause:Either the log is being archived by another process or an administrative command is executing and modifying the log. Clearing, adding a member, dropping a member, renaming a member, and dropping the log are operations that modify a log.
Action:Wait for the current operation to complete and try again.
ORA-00262 current log name of closed thread num cannot switch

Cause:The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived or cleared and cannot be reused.
Action:Archive another log in the same thread first or complete the clearing. See attached errors for the reason the switch cannot be completed.
ORA-00263 there are no logs that need archiving for thread num

Cause:An attempt was made to archive the unarchived logs in this thread manually, but no logs need archiving.
Action:No action required.
ORA-00264 no recovery required

Cause:An attempt was made to perform media recovery on files that do not need any type of recovery.
Action:Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.
ORA-00265 instance recovery required, cannot set ARCHIVELOG mode

Cause: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 datafiles.
Action:Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE options.
ORA-00266 name of archived log file needed

Cause:During media recovery, the name of an archived redo log file was requested, but no name was entered.
Action:Mount the correct redo log file and enter its name when it is requested.
ORA-00267 name of archived log file not needed

Cause:During media recovery, the name of an archived redo log file was entered, but no name was requested.
Action:Continue media recovery, but do not enter a new log name.
ORA-00268 specified log file does not exist name

Cause:The given redo log file does not exist.
Action:Check the spelling and capitalization of the filename and retry the command.
ORA-00269 specified log file is part of thread num not num

Cause:The given redo log file is not part of the given thread.
Action:Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.
ORA-00270 error creating archive log

Cause:An error was encountered when either creating or opening the destination file for archiving.
Action:Check that the archive destination is valid and that there is sufficient space on the destination device.
ORA-00271 there are no logs that need archiving

Cause:An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.
Action:No action required.
ORA-00272 error writing archive log

Cause:An I/O error occurred while archiving a redo log file.
Action:Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.
ORA-00273 media recovery of direct load data that was not logged

Cause:A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.
Action:The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.
ORA-00274 illegal recovery option str

Cause:An illegal option was specified for a recovery command.
Action:Correct the syntax and retry the command.
ORA-00275 media recovery has already been started

Cause:An attempt was made to start a second media recovery operation in the same session.
Action:Complete or cancel the first media recovery session or start another session to perform media recovery.
ORA-00276 CHANGE keyword specified but no change given

Cause:The CHANGE keyword was specified on the command line, but no change number was given.
Action:Retry the command using a valid change number after the CHANGE keyword.
ORA-00277 illegal option to the UNTIL recovery flag str

Cause:Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.
Action:Correct the syntax.
ORA-00278 log file name no longer needed for this recovery

Cause:The specified redo log file is no longer needed for the current recovery.
Action:No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.
ORA-00279 change num generated at name needed for thread num

Cause:The requested log is required to proceed with recovery.
Action:Please specify the requested log in the command or cancel recovery.
ORA-00280 change num for thread num is in sequence #num

Cause:This message helps to locate the redo log file with the specified change number requested by other messages.
Action:Use the information provided in this message to specify the required archived redo log files for other errors.
ORA-00281 media recovery may not be performed using dispatcher

Cause:An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.
Action:Connect to the instance via a dedicated server process to perform media recovery.
ORA-00282 UPI name call not supported, use ALTER DATABASE RECOVER

Cause:The given UPI call is no longer supported.
Action:Use the ALTER DATABASE RECOVER command for all recovery actions.
ORA-00283 recovery session canceled due to errors

Cause:An error during recovery was determined to be fatal enough to end the current recovery session.
Action:More specific messages will accompany this message. Refer to the other messages for the appropriate action.
ORA-00284 recovery session still in progress

Cause:An error during recovery was determined to be minor enough to allow the current recovery session to continue.
Action:More specific messages will accompany this message. Refer to other messages for the appropriate action.
ORA-00285 TIME not given as a string constant

Cause:UNTIL TIME was not followed by a string constant for the time.
Action:Enter the time enclosed in single quotation marks.
ORA-00286 no members available, or no member contains valid data

Cause:None of the members of a redo log file group are available, or the available members do not contain complete data.
Action:If a member is temporarily off line, attempt to make it available. Check that the correct filenames are being used, especially if the redo log file is being accessed from a remote location.
ORA-00287 specified change number num not found in thread num

Cause:The given change number does not appear in any of the online redo logs for the given thread.
Action:Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.
ORA-00288 to continue recovery type ALTER DATABASE RECOVER CONTINUE

Cause:During media recovery, redo information from a new log is not required but the continuation command is necessary to do a checkpoint and report errors.
Action:Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
ORA-00289 suggestion: filename

Cause:This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.
Action:Consider using this filename for the next log needed for recovery.

ORA-00290 operating system archiving error occurred. See error below

Cause:While attempting to archive to a redo log file, the server encountered an unexpected operating system error.
Action:Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.
ORA-00291 numeric value required for PARALLEL option

Cause:A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
Action:Re-enter the command with a numeric argument specifying the degree of parallelism desired.
ORA-00292 parallel recovery feature not installed

Cause:A parallel recovery was requested when the parallel recovery option is not installed.
Action:Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.
ORA-00293 control file out of sync with redo log

Cause:The redo log and control file are out of sync because a non-current control file was specified when the instance was started.
Action:Retry the Recover command using the current control file or retry the Recover command using the USING BACKUP CONTROL FILE clause.

00300-00369: Redo Log Files

ORA-00300 illegal redo log block size num specified - exceeds limit of num

Cause:The specified block size of the redo log file is greater than the maximum block size for the operating system.
Action:Create the redo log on a device with a smaller block size.
ORA-00301 error in adding log file name - file cannot be created

Cause:The creation of the redo log file failed.
Action:Check that there is enough storage space on the device, that the name of the file is valid, and that the device is online; then try again.

ORA-00302 limit of num logs exceeded

Cause:The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16).
Action:Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES.
ORA-00304 requested INSTANCE_NUMBER is busy

Cause:An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.
Action:Specify another value for INSTANCE_NUMBER in the initialization parameter file or wait for recovery to finish for that instance number. Then restart the instance.
ORA-00305 log name of thread num inconsistent; belongs to another database

Cause:The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.
Action:Specify the correct redo log file, then retry the operation.
ORA-00306 limit of num log writer instances in this database

Cause:Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only when attempting to start another instance in Parallel Server mode.
Action:It is not possible to start more than the given number of instances. The maximum is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.
ORA-00307 requested INSTANCE_NUMBER out of range, maximum is num

Cause:The initialization parameter INSTANCE_NUMBER specified a number that was out of range.
Action:Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.
ORA-00308 cannot open archived log name

Cause:The system cannot access a required archived redo log file.
Action:Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.
ORA-00309 log belongs to wrong database

Cause:The system cannot access the archived redo log because it belongs to another database.
Action:Specify the correct redo log file, then retry the operation.
ORA-00310 archived log contains sequence num; sequence num required

Cause:The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified during recovery.
Action:Specify the correct redo log file; then retry the operation.
ORA-00311 cannot read header from archived log

Cause:An error occurred when attempting to read the file header from the archived redo log file.
Action:Other messages will accompany this message. See the associated messages for the appropriate action to take.
ORA-00312 online log name thread num: str

Cause:This message reports the filename for details of another message.
Action:Other messages will accompany this message. See the associated messages for the appropriate action to take.
ORA-00313 open failed for members of log group name of thread name

Cause:The online log cannot be opened. The file may not be in the expected location.
Action:Specify the correct redo log file or make log available, if necessary. Also, see the following messages, if any.
ORA-00314 log name of thread num, expected sequence # num does not match num

Cause:The online log is out of sequence, probably because it is corrupted or an old version.
Action:For more information on recovery procedures, see the Oracle7 Server Administrator's Guide.
ORA-00315 log name of thread num, wrong thread # num in header

Cause:The online redo log file is corrupted or is an old version.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00316 log name of thread num, type str in header is not redo log file

Cause:The online redo log file is corrupted or is an old version.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00317 file type str in header is not log file

Cause:This is not an archived redo log file.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00318 log name of thread num, expected file size num does not match num

Cause:The file size indicated in the control file did not match the file size contained in the redo log file.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00319 log name of thread num has incorrect log reset status

Cause:An online redo log file has log reset data that is different from the log reset data listed in the control file. The redo log file is probably an incorrectly restored backup.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00320 cannot read file header from log name of thread num

Cause:The system is unable to read the redo log file header because the file is not available or the file is corrupted.
Action:Specify the correct redo log file, then retry the operation.
ORA-00321 log name of thread num, cannot update log file header

Cause:The system cannot write to the redo log file.
Action:Restore access to the redo log file; then retry the operation.
ORA-00322 log name of thread num is not current copy

Cause:An online redo log file appears to be an incorrectly restored backup, according to a check of the redo log file header.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00323 current log of thread num not usable and all others need archiving

Cause:An attempt to open a thread failed because it is necessary to switch to another online log, but all the other online redo logs need to be archived before they can be used.
Action:Archive the online redo logs for the thread, then retry the operation.
ORA-00324 log file name translated name name too long, num characters exceeds num limit

Cause:The translated name for a redo log file is too long.
Action:Respecify a redo log filename that produces a shorter filename on translation.
ORA-00325 archived log for thread num, wrong thread # num in header

Cause:The archived redo log file is corrupted, or it belongs to another thread. This redo log file cannot be used.
Action:Find and use the correct archived redo log file, then retry the operation.
ORA-00326 log begins at change num, need earlier change num

Cause:The archived redo log file supplied for recovery was generated after the redo log file that is needed. Cannot use the log for applying redo information at this time.
Action:Find and install the correct archived redo log file, then retry the operation.
ORA-00327 log name of thread num, physical size num less than needed num

Cause:A redo log file has shrunk in size. This is usually caused by a computer operator's mistake or an operating system error.
Action:Restore the redo log file from backup. If the database was shut down cleanly, no further action should be required. Otherwise, manual recovery may be necessary.
ORA-00328 archived log ends at change num, need later change num

Cause:The archived redo log file supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo information at this time.
Action:Find and install the correct archived redo log file, then retry the operation.
ORA-00329 archived log begins at change num, need change num

Cause:The archived redo log file supplied for recovery is not the correct log. An earlier redo log file is needed.
Action:Find and install the correct archived redo log file, then retry the operation.
ORA-00330 archived log ends at change num, need change num

Cause:The archived redo log file supplied for recovery is not the correct log. A later redo log file is needed.
Action:Find and install the correct archived redo log file, then retry the operation.
ORA-00331 log version num incompatible with Oracle version num

Cause:The log was created under an older, incompatible version of Oracle, or an attempt was made to use the wrong log.
Action:Specify the correct redo log file or recover the database with the old software. Then shut down and restart Oracle with the new software.
ORA-00332 archived log is too small - may be incompletely archived

Cause:The log occupies less space than is allocated to it. This may result from a shutdown abort while the archiver was writing it.
Action:Get a complete version of the file, either the online version or one that was successfully archived, and use that for recovery.
ORA-00333 redo log read error block num count num

Cause:An error occurred while reading the redo log file. Other messages will accompany this message and will give the name of the file.
Action:Restore access to the file or get another copy of the file.
ORA-00334 archived log: name

Cause:This message reports the filename involved with other errors.
Action:See the associated messages for a description of the problem.
ORA-00335 online log name: No log with this number, log does not exist

Cause:This message reports the filename involved with other messages.
Action:Correct the underlying problems mentioned in the other messages.
ORA-00336 log file size num blocks is less than minimum num blocks

Cause:The redo log file size specified in the CREATE DATABASE statement is too small.
Action:Increase the redo log file size and re-enter the statement.
ORA-00337 log file name does not exist and no size specified

Cause:The system could not add a redo log file because it could not find an existing file or a size for creating the file.
Action:Specify a size for the redo log file, then retry the operation.
ORA-00338 log name of thread num is more recent than control file

Cause:The control file change sequence number in the redo 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 to happen by reopening the database may cause the error to stop happening without correcting the problem. Every attempt to open the database advances the control file change sequence number.
Action:Use the correct control file or perform recovery using a backup of the control file.
ORA-00339 archived log does not contain any redo

Cause:The archived log being applied is not the correct log. The log being applied is possibly a copy of a log or was an online log being prepared to be used as the current log.
Action:Restore the correct redo log file.
ORA-00340 I/O error processing online log name of thread num

Cause:An I/O error occurred on the named online redo log file, probably because the file was not accessible or because it was corrupted.
Action:Restore access to the file or restore the file from a backup.
ORA-00341 log name of thread num, wrong log # num in header

Cause:The internal information in an online redo log file does not match the control file information.
Action:Refer to the Oracle7 Server Administrator's Guide for recovery procedures.
ORA-00342 archived log was created before last RESETLOGS

Cause:Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.
Action:Find and install the correct archived redo log file, then retry the operation.
ORA-00343 too many errors, log member closed

Cause:The maximum number of errors on this log member has been exceeded. Other messages will accompany this message.
Action:Correct the underlying problems mentioned in the other messages.
ORA-00344 unable to recreate online log name

Cause:An I/O failure occurred when attempting to recreate an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR log file command.
Action:Check the accompanying messages. Check that the file is accessible.
ORA-00345 redo log write error block num count num

Cause:An I/O error has occurred while writing the log, probably because the file was not accessible, or a device failed.
Action:Make the file accessible or restore the device, then restart the system. If the log is lost, apply media or incomplete recovery.
ORA-00346 log member marked as STALE

Cause:A redo log file member is no longer complete. Other messages will accompany this message.
Action:Correct the underlying problem mentioned in the other messages.
ORA-00347 log name of thread num expected block size num does not match num

Cause:During online recovery, the block size specified in the control file did not match the block size indicated in the redo log file.
Action:Restore the correct redo log file from a backup or reset the online redo log files.
ORA-00348 single-process redo failure. Must abort instance

Cause:A failure occurred during a single-process redo log operation. This error does not occur during normal multi-process operations.
Action:Shut down and restart the database.
ORA-00349 failure obtaining block size for name

Cause:The operating system was unable to determine the block size for the named file.
Action:Check the accompanying messages, then restore the device or specify another file.
ORA-00350 log name of thread num needs to be archived

Cause:Media recovery is enabled and the specified log was not archived.
Action:Archive the redo log file or disable media recovery. If the command supports the UNARCHIVED option, then it can be used. However, this may result in making backups unusable and forcing some offline files to be dropped.
ORA-00351 recover-to time invalid

Cause:The time specified in a RECOVER DATABASE... UNTIL is before January 1, 1988.
Action:Specify a time after January 1, 1988.
ORA-00352 all logs for thread num need to be archived - cannot enable

Cause:An attempt was made to enable a thread when all of the online redo log files in the thread needed to be archived, and media recovery has been enabled. There is no online redo log file that can be made the new current log for the thread.
Action:Archive a redo log file for the thread.
ORA-00353 log corruption near block num change str time str

Cause:Some type of redo log file corruption has been discovered. This message describes the location of the corruption. Other messages will accompany this message and describe the type of corruption.
Action:Perform recovery with a good version of the redo log file or perform incomplete recovery up to the indicated change or time.

ORA-00354 corrupt redo log block header

Cause:The block header on the block in the redo log file is not valid. The block number and time-stamp are given in an accompanying message.
Action:Perform recovery with a good version of the redo log file or perform cancel-based recovery up to, but not including, the corrupted redo log file.
ORA-00355 change numbers out of order

Cause:A change number found in the redo log file is lower than a previously encountered change number. The redo log file is corrupted in some way. The corruption may be at the earlier change number or at this one. The block number and time-stamp are given in an accompanying message.
Action:Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.
ORA-00356 inconsistent lengths in change description

Cause:A change record in the redo log file contains lengths that do not add up to a consistent value. The redo log file is corrupted in some way.
Action:Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.
ORA-00357 too many members specified for log file, the maximum is num

Cause:An attempt was made to add a redo log group or add a redo log group member that would result in a set of online redo logs with too many members. The maximum number of members is set when the database is created.
Action:Use fewer redo log group members or use the CREATE CONTROLFILE command and set the parameter MAXLOGMEMBERS to a larger value.
ORA-00358 too many file members specified, the maximum is num

Cause:A CREATE or ALTER statement specified too many members in the file list.
Action:Specify a number of files that is within the given limit or use the CREATE CONTROLFILE command and set the parameter MAXLOGMEMBERS to a larger value.
ORA-00359 log file group num does not exist

Cause:An attempt to add or drop a redo log group member specified a redo log file group number that does not exist.
Action:Check the configuration of the redo log files and retry the command with a valid group number.
ORA-00360 not a log file member: name

Cause:An invalid filename was given to drop a redo log group member. Either the file is not a part of the database, or it is a datafile.
Action:Specify a valid member name and retry the command.
ORA-00361 cannot remove last log member name group num

Cause:An attempt was made to remove the last member of a redo log group.
Action:If desired, delete the entire log by using the DROP log file command.
ORA-00362 member is required to form a valid log file in group name

Cause:A request to drop a redo log group member was denied because it would remove data required to form a complete online redo log group.
Action:If desired, delete the entire log after archiving, if required, using the DROP log file command.
ORA-00363 log is not the archived version

Cause:The log given for 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 the end of the thread. This message can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.
Action:Find the archived version of the log and specify its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.
ORA-00364 cannot write header to new log member

Cause:An I/O error occurred when attempting to write the header to a redo log group member that is being added to an existing group.
Action:See accompanying messages. Fix the problem or use another file.
ORA-00365 the specified log is not the correct next log

Cause:The specified log failed to pass checks to ensure it corresponds to the log that was generated against a cold backup image of the database.
Action:Find the log that was generated by this copy of the database and give that filename to recover.
ORA-00369 current log of thread num not useable and other log being cleared

Cause:Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.
Action:If the ALTER DATABASE CLEAR log file command is still active then wait for it to complete. Otherwise, re-enter the CLEAR command. If there are other online logs for the thread that are not being cleared, then archive the logs.

00370-00389: KCB Errors

ORA-00371 no free buffer handles available

Cause:The value of the initialization parameter DB_HANDLES is too small.
Action:Shut down the instance, increase the value of DB_HANDLES in the initialization parameter file, and then restart the instance. Under normal circumstances, let DB_HANDLES take its default value by omitting the parameter from the initialization parameter file.
ORA-00372 file name cannot be modified at this time

Cause:An attempt was made to access a file being taken off line, or the database may be closing.
Action:Access the file after it is taken off line. Attempts will either succeed because the datafile is back online or fail with a message describing which file is off line. Repeat until successful.
ORA-00373 online log version num incompatible with Oracle version num

Cause:The online log was written by an incompatible version of Oracle. This can occur when the redo log file was created by either a newer or older version of Oracle.
Action:Recover the database using a compatible version, shut it down cleanly; then restart with the current software.
ORA-00374 parameter DB_BLOCK_SIZE = num invalid, valid range num..num

Cause:An invalid value has been used for the DB_BLOCK_SIZE initialization parameter.
Action:Adjust the parameter and restart the instance.
ORA-00375 unable to get default DB_BLOCK_SIZE

Cause:The system was unable to determine the default DB_BLOCK_SIZE.
Action:See the corresponding operating system-specific message. As a work-around, specify the block size with the parameter DB_BLOCK_SIZE in the initialization parameter file. See also your operating system-specific Oracle documentation.
ORA-00376 file name cannot be read at this time

Cause:An attempt was made to read from a file that is not readable. The most likely cause is that the file is off line.
Action:Check the state of the file. Bring the file online, if necessary.

00390-00399: Redo Log Files

ORA-00390 log name of thread num is being cleared, cannot become current log

Cause:An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.
Action:If the clear command is still executing, then wait for its completion. If it terminated, then re-enter the clear command or drop the log.
ORA-00391 all threads must switch to new log format at the same time

Cause:An attempt to switch the current log of a single thread is not allowed because the 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.
Action:Open the database to cause the coordinated log switch. If that is not possible, then return to the same software version and compatibility setting last used to open the database.
ORA-00392 log name of thread num is being cleared, operation not allowed

Cause:An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.
Action:If the clear command is still executing, then wait for its completion. If it terminated, then re-enter the clear command or drop the log.
ORA-00393 log name of thread num is needed for recovery of offline datafiles

Cause:Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped.
Action:Archive the log, then repeat the clear command. If archiving is not possible and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.

00400-00420: Oracle Compatibility

ORA-00400 invalid release value num for parameter name

Cause:The release level given for the specified initialization parameter is invalid.
Action:Correct the parameter value in the initialization parameter file and retry.
ORA-00401 the value for parameter name is not supported by this release

Cause:The value specified cannot be supported by this release of the software.
Action:Choose an appropriate value or remove the initialization parameter value to use the default value.
ORA-00402 database changes by release num cannot be used by release num

Cause:Changes have been made to the database that require a newer software release or that violate the open compatibility initialization parameters.
Action:Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file.
ORA-00403 str str is not the same as other instances str

Cause:The recovery compatible, or recovery not compatible, initialization parameters were changed for another running instance.
Action:Change the initialization parameters of the current instance to match other instances already running.
ORA-00404 conversion data file not found: name

Cause:The file used for converting the database from Oracle Version 6 to Oracle7 could not be found.
Action:Check that the conversion process has been started on this database and that the datafile name is accessible.
ORA-00405 compatibility type name

Cause:Reporting a type associated with another message.
Action:See accompanying message.
ORA-00406 COMPATIBLE parameter needs to be num or greater

Cause:The specification for the initialization parameter COMPATIBLE is too low to allow the requested operation.
Action:Shut down and specify a higher COMPATIBLE value, then restart.
ORA-00407 rolling upgrade from release num.num to num.num is not allowed

Cause:Another instance has the database mounted and that instance is for a different release of Oracle than you are using.
Action:Shut down and start up all instances with the new release of Oracle.

00436-00437: Licensing

ORA-00436 Oracle is not licensed. Contact Oracle Corporation for assistance

Cause: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.
Action:Check that Oracle is installed correctly. Then contact customer support.
ORA-00437 Oracle feature is not licensed. Contact Oracle Corporation for assistance

Cause: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.
Action:Check that Oracle is installed correctly. Then contact customer support.

00440-00460: Detached Process Startup

ORA-00443 background process name did not start

Cause:The specified process did not start.
Action:Check that the executable image is in the correct place with the correct protections and that there is enough memory.
ORA-00444 background process name failed while starting

Cause:This message is usually caused by a faulty or non-existent background process image.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages or obtain a proper background process image, then retry the operation.
ORA-00445 background process name did not start after num seconds

Cause:The specified process did not start.
Action:Check and, if necessary, correct problems indicated by one or more of the following:

ORA-00446 background process started when not expected

Cause:A background process started after Oracle was already running.
Action: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 customer support.
ORA-00447 fatal error in background process

Cause:One of the background processes completed unexpectedly.
Action:Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST.
ORA-00448 normal completion of background process

Cause:One of the background processes completed normally as requested by the user.
Action: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.
ORA-00449 background process name unexpectedly terminated with error num

Cause:A foreground process needing service from a background process has discovered the background process died.
Action:Refer to the message code given in the message and the trace file for the foreground and the background processes.

00470-00485: Detached Process Death

ORA-00470 LGWR process terminated with error

Cause:The log writer process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process errors, check the trace file for the mentioned process until the root error is found.
ORA-00471 DBWR process terminated with error

Cause:The Database Writer process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-00472 PMON process terminated with error

Cause:The Process Monitor process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-00473 ARCH process terminated with error

Cause:The Archiver process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-00474 SMON process terminated with error

Cause:The System Monitor process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-00475 TRWR process terminated with error.

Cause:The system tracing process died.
Action:Restart the instance.
ORA-00476 RECO process terminated with error

Cause:The distributed transaction, two-phase commit, recovery process died.
Action:Restart the instance.
ORA-00477 SNP* process terminated with an error

Cause:A snapshot refresh process died.
Action:Restart the instance.
ORA-00480 LCK* process terminated with error

Cause:One Lock process terminated abnormally.
Action:Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-00483 during shutdown a process abnormally terminated

Cause:One of the background processes did not exit normally when the instance shut down.
Action:Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then 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.

00486-00569: Interrupt Handlers

ORA-00568 maximum number of interrupt handlers exceeded

Cause:The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed.
Action:Reduce the number of registered interrupt handlers.

00570-00599: SQL*Connect Opening and Reading Files

00600-00639: Oracle Exceptions

ORA-00600 internal error code, arguments: [num], [?], [?], [?], [?], [?]

Cause:This is a catchall internal error message for Oracle program exceptions. It indicates that a process has met a low-level, unexpected condition.

Action:Report this error to customer support after gathering the following information:
ORA-00601 cleanup lock conflict

Cause:The Process Monitor process encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00602 internal programming exception

Cause:An internal programming exception has occurred.
Action:Report this error as a program bug to customer support.
ORA-00603 Oracle Server session terminated by fatal error

Cause:An Oracle Server session is in an unrecoverable state.
Action:Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.
ORA-00604 error occurred at recursive SQL level num

Cause:An error occurred while processing a recursive SQL statement. A recursive SQL statement is one that applies to internal dictionary tables.
Action:If the situation described in the next message on the stack can be corrected, do so; otherwise, contact customer support.
ORA-00606 internal error code

Cause:A call to deferred UPI functions was made in non-deferred mode.
Action:Contact customer support.

00640-00699: SQL*Connect

00700-00709: Dictionary Cache

ORA-00701 object necessary for warm starting database cannot be altered

Cause:An attempt was made to alter or drop a table, cluster, or index defined in the control file's bootstrap segment and needed to warm start the database.
Action:Correct the spelling of the object name or remove it from the ALTER or DROP statement.
ORA-00702 bootstrap version version inconsistent with version version

Cause:The version of the bootstrap data in a file is incompatible with the current version of the software.
Action:Restore a version of the software that is compatible with the datafiles.
ORA-00703 maximum number of dictionary cache instance locks exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of dictionary cache instance locks is specified by the ROW_CACHE_INSTANCE_LOCKS parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this error occurs often, contact customer support.
ORA-00704 bootstrap process failure

Cause:An error occurred when processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem.
Action:Correct the problems mentioned in the other messages. If the problem persists, contact customer support.

00816-00816: Message Translation

ORA-00816 error message translation failed

Cause:There is an internal error where a routine was unable to translate a message code.
Action:Contact customer support.

00900-00999: SQL Parsing

ORA-00900 invalid SQL statement

Cause:The statement is not recognized as a valid SQL statement.

Action:Correct the syntax or install the Procedural Option.
ORA-00901 invalid CREATE command

Cause:The CREATE command was not followed by a valid CREATE option.
Action:Correct the syntax.
ORA-00902 invalid datatype

Cause:The datatype entered in the CREATE or ALTER TABLE statement is not valid.
Action:Correct the syntax.
ORA-00903 invalid table name

Cause:A table or cluster name is invalid or does not exist. This message is also issued if an invalid cluster name or no cluster name is specified in an ALTER CLUSTER or DROP CLUSTER statement.
Action:Check spelling. A valid table name or cluster name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word.
ORA-00904 invalid column name

Cause:The column name entered is either missing or invalid.
Action:Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist of only alphanumeric characters and the special characters $, _, and #. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word.
ORA-00905 missing keyword

Cause:A required keyword is missing.
Action:Correct the syntax.
ORA-00906 missing left parenthesis

Cause:A required left parenthesis has been omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses also are required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements.
Action:Correct the syntax, inserting a left parenthesis where required, and retry the statement.
ORA-00907 missing right parenthesis

Cause:A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.
Action:Correct the syntax and retry the statement.
ORA-00908 missing NULL keyword

Cause:Either of the following:

SELECT * FROM EMP WHERE DEPTNO IS NOT;

Action:Correct the syntax.
ORA-00909 invalid number of arguments

Cause:An Oracle function was referenced with an incorrect number of arguments. All Oracle functions, except for SYSDATE, require at least one argument.
Action:Correct the syntax of the function by entering the required number of arguments.
ORA-00910 specified length too long for its datatype

Cause:No size was specified for a character field or the size was invalid. A maximum length must be specified for each character column. The maximum value for this length varies for each character datatype, such as CHAR or VARCHAR2.
Action:Enter a maximum length for the field.
ORA-00911 invalid character

Cause:Special characters are valid only in certain places. If special characters other than $, _, and # are used in a name and the name is not enclosed in double quotation marks ("), this message will be issued. One exception to this rule is for database names; in this case, double quotes are stripped out and ignored.
Action:Remove the invalid character from the statement or enclose the object name in double quotation marks.
ORA-00913 too many values

Cause:The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT.
Action:Check the number of items in each set and change the SQL statement to make them equal.
ORA-00914 missing ADD keyword

Cause:The keyword ADD does not precede one of the following:

Action:Specify the keyword ADD in the ALTER statement.
ORA-00915 network access of dictionary table not currently allowed

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00917 missing comma

Cause:A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), ...).
Action:Correct the syntax.
ORA-00918 column ambiguously defined

Cause:A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.
Action:Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above.
ORA-00919 invalid function

Cause:An entry was formatted like a function call, but it is not recognizable as an Oracle function.
Action:Correct the syntax.
ORA-00920 invalid relational operator

Cause:A search condition was entered with an invalid or missing relational operator.
Action:Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT] LIKE in the condition.
ORA-00921 unexpected end of SQL command

Cause:The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted.
Action:Correct the syntax.
ORA-00922 missing or invalid option

Cause:An invalid option was specified in defining a column or storage clause. The valid option in specifying a column is NOT NULL to specify that the column cannot contain any NULL values. Only constraints may follow the datatype. Specifying a maximum length on a DATE or LONG datatype also causes this error.
Action:Correct the syntax. Remove the erroneous option or length specification from the column or storage specification.
ORA-00923 FROM keyword not found where expected

Cause:In a SELECT or REVOKE statement, the keyword FROM was either missing, misplaced, or misspelled. The keyword FROM must follow the last selected item in a SELECT statement or the privileges in a REVOKE statement.
Action:Correct the syntax. Insert the keyword FROM where appropriate. The SELECT list itself also may be in error. If quotation marks were used in an alias, check that double quotation marks enclose the alias. Also, check to see if a reserved word was used as an alias.
ORA-00924 missing BY keyword

Cause:The keyword BY was omitted in a GROUP BY, ORDER BY, or CONNECT BY clause. In a GRANT statement, the keyword IDENTIFIED must also be followed by the keyword BY.
Action:Correct the syntax. Insert the keyword BY where required and then retry the statement.
ORA-00925 missing INTO keyword

Cause:An INSERT statement has been entered without the keyword INTO.
Action:Correct the syntax. Insert the keyword INTO where required and then retry the statement.
ORA-00926 missing VALUES keyword

Cause:An INSERT statement has been entered without the keyword VALUES or SELECT. Either a VALUES clause or a SELECT subquery must follow the INSERT INTO clause.
Action:Correct the syntax. Enter either a VALUES clause or a subquery after the INSERT INTO clause.
ORA-00927 missing equal sign

Cause:An equal sign has been omitted in one of the following places:

Action:Correct the syntax. Insert the equal sign where required and retry the statement.
ORA-00928 missing SELECT keyword

Cause:A SELECT subquery must be included in a CREATE VIEW statement.
Action:Correct the syntax. Insert the required SELECT clause after the CREATE VIEW clause and then retry the statement.
ORA-00929 missing period

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00930 missing asterisk

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00931 missing identifier

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00932 inconsistent datatypes

Cause:Either

Action:If the cause is
ORA-00933 SQL command not properly ended

Cause:The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY may not be used to create an ordered view or to insert in a certain order. Also, an improper SQL ending occurs if IN clause is used with only one argument (IN(X), for example). An IN clause must have two or more arguments.
Action:Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces.
ORA-00934 group function is not allowed here

Cause:One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause.
Action:Remove the group function from the WHERE or GROUP BY clause.

ORA-00935 group function is nested too deeply

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00936 missing expression

Cause:A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE.
Action:Check the statement syntax and specify the missing component.
ORA-00937 not a single-group group function

Cause:A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause.
Action:Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed.
ORA-00938 not enough arguments for function

Cause:The function was referenced with too few arguments.
Action:Check the function syntax and specify the required number of arguments.
ORA-00939 too many arguments for function

Cause:The function was referenced with too many arguments.
Action:Check the function syntax and specify only the required number of arguments.
ORA-00940 invalid ALTER command

Cause:An invalid ALTER option was specified.
Action:Correct the syntax.
ORA-00941 missing cluster name

Cause:The cluster name was either missing or invalid.
Action:Specify a valid cluster name. A valid cluster name must start with a letter, be less than or equal to 30 characters, and contain only alphanumeric characters or the special characters $, _, and #. It may not be a reserved word. The name must be specified immediately following the keywords CREATE CLUSTER.
ORA-00942 table or view does not exist

Cause:The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it.

Action:Check each of the following:
ORA-00943 cluster does not exist

Cause:The current user owns no cluster by the specified name.

Action:Specify a valid cluster name following the keyword CLUSTER, then retry the statement.
ORA-00944 insufficient number of clustered columns

Cause:An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created.
Action:Specify all cluster columns in the CREATE TABLE statement, then retry it.
ORA-00945 specified clustered column does not exist

Cause:A column specified in the cluster clause of a CREATE TABLE statement is not a column in this table.

Action:Re-execute the statement, using the names of columns defined for the table.
ORA-00946 missing TO keyword

Cause:A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered.
Action:Check the syntax for the GRANT command, insert the keyword TO where required, and retry the statement.
ORA-00947 not enough values

Cause:This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in: 

WHERE (A,B) IN (SELECT C FROM ...) 

INSERT INTO EMP(EMPNO,ENAME) VALUES('JONES')

Action:Check the number of items in each set and change the SQL statement to make them equal.
ORA-00948 ALTER CLUSTER statement no longer supported

Cause:The ALTER CLUSTER statement has been withdrawn.
Action:To add data to a cluster from an existing table, use the following series of SQL statements: 

CREATE TABLE newtable SELECT * FROM oldtable CLUSTER clustername;
DROP oldtable;
RENAME TABLE newtable oldtable;

ORA-00949 illegal reference to remote database

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-00950 invalid DROP option

Cause:A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW.
Action:Check the command syntax, specify a valid DROP option, and then retry the statement.
ORA-00951 cluster not empty

Cause:A DROP CLUSTER statement specified a cluster that is not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause is specified. Tables may also be removed from a cluster by using the DROP TABLE command.
Action:Either specify the INCLUDING TABLES clause in the DROP CLUSTER statement or remove all tables from the cluster with the DROP TABLE command before issuing the DROP CLUSTER command.
ORA-00952 missing GROUP keyword

Cause:Groups are not currently implemented.
Action:No user action required.
ORA-00953 invalid index name

Cause:In a CREATE INDEX, DROP INDEX, or VALIDATE INDEX statement, the index name was missing or invalid.
Action:Specify a valid index name after the keyword INDEX. To drop or validate an existing index, check the name by querying the data dictionary. To create a new index, check the syntax before retrying.
ORA-00954 missing IDENTIFIED keyword

Cause:A GRANT CONNECT statement was issued without the keyword IDENTIFIED.
Action:Check the syntax and insert the keyword IDENTIFIED after the last username. The format is

GRANT CONNECT TO user-list IDENTIFIED BY password-list;

ORA-00955 name is already used by an existing object

Cause:An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already exists. A user's database objects must have distinct names.
Action:Enter a unique name for the database object or modify or drop the existing object so it can be reused.
ORA-00956 missing or invalid auditing option

Cause:An AUDIT or NOAUDIT command was not followed by a valid option or the keyword ALL. For example, when AUDITing tables an option such as ALTER, AUDIT, COMMENT, DELETE, GRANT, INDEX, INSERT, LOCK, RENAME, SELECT, or UPDATE must be specified.
Action:Correct the syntax.
ORA-00957 duplicate column name

Cause:A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster.
Action:In a CREATE statement, change one of the column names to a new, unique column name. In an INSERT statement, remove one of the duplicate names.
ORA-00958 missing CHECK keyword

Cause:The keyword CHECK should follow the keyword WITH in the WITH OPTION clause of the CREATE VIEW statement.
Action:Check the statement syntax and insert the keyword CHECK where required. Then retry the statement.
ORA-00959 tablespace "name" does not exist

Cause:A statement specified the name of a tablespace that does not exist.

Action:Enter the name of an existing tablespace. For a list of tablespace names, query the data dictionary. If a tablespace is dropped and re-created with the same name, use ALTER USER to reset the default or temporary tablespace name, because the new tablespace is not the same as the dropped tablespace, even though they have the same name.
ORA-00960 ambiguous column naming in select list

Cause:A column name in the order-by list matches more than one select list column.
Action:Remove the duplicate column naming in the select list.
ORA-00962 too many group-by or order-by expressions

Cause:The group-by or order-by column list contains more than 255 expressions.
Action:Use no more than 255 expressions in the group-by or order-by list.
ORA-00964 table name not in FROM list

Cause:A table specified in a query's SELECT list is not named in the FROM clause list.
Action:Check spelling of the table names, check that each table name in the SELECT list matches a table name in the FROM list, and then retry the statement.
ORA-00965 column aliases not allowed for "*"

Cause:An alias was used with the return-all-columns function (*) in the SELECT list. For example: 

SELECT * COL_ALIAS FROM EMP;

Action:Either specify individual columns or do not specify an alias with a "*".
ORA-00966 missing TABLE keyword

Cause:A LOCK statement was specified and the keyword TABLE was missing, misspelled, or misplaced. A LOCK statement must begin with LOCK TABLE tablename.
Action:Correct the syntax.
ORA-00967 missing WHERE keyword

Cause:The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.
Action:Correct the syntax.
ORA-00968 missing INDEX keyword

Cause:The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.
Action:Correct the syntax.
ORA-00969 missing ON keyword

Cause:The keyword ON in a GRANT, REVOKE, or CREATE INDEX statement was missing, misspelled, or misplaced.
Action:Check syntax and spelling, and use the keyword ON where required.
ORA-00970 missing WITH keyword

Cause:The keyword START was specified without the keyword WITH. Both keywords are necessary if a START WITH clause is desired in a tree-structured query.
Action:Change the keyword START to the keywords START WITH. Then retry the statement.
ORA-00971 missing SET keyword

Cause:The keyword SET in an UPDATE statement is missing, misspelled, or misplaced.
Action:Check syntax and spelling, and use the keyword SET after the name of the table to be updated.
ORA-00972 identifier is too long

Cause:The name of a schema object exceeds 30 characters. Schema objects are tables, clusters, views, indexes, synonyms, tablespaces, and usernames.
Action:Shorten the name to 30 characters or less.
ORA-00974 invalid PCTFREE value percentage

Cause:The percentage of free space specified in a CREATE INDEX statement is not between 0 and 100. A PCTFREE value of 0 means the entire block is available. The value 100 is not useful because it means that no data may be inserted. The default is 10.
Action:Specify a PCTFREE value between 0 and 100. Then retry the statement.
ORA-00975 date + date not allowed

Cause:An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates.
Action:Use the Oracle function TO_NUMBER to convert one of the date fields to a numeric field before adding it to the other date field.
ORA-00976 LEVEL, PRIOR, or ROWNUM not allowed here

Cause:The use of the PRIOR clause, the pseudo-column LEVEL, or ROWNUM is incorrect in this context.
Action:Check the syntax for the SQL statement. Then remove or relocate the keyword PRIOR, LEVEL, or ROWNUM.
ORA-00977 duplicate auditing option

Cause:An AUDIT or NOAUDIT statement specified the same option more than once.
Action:Either specify ALL without other auditing options or remove the duplicate auditing specifications.
ORA-00978 nested group function without GROUP BY

Cause:A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause.
Action:Either add a GROUP BY clause or remove the extra level of nesting.
ORA-00979 not a GROUP BY expression

Cause:The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, must be listed in the GROUP BY clause.
Action:Include in the GROUP BY clause all SELECT expressions that are not group function arguments.
ORA-00980 synonym translation is no longer valid

Cause:The synonym used is based on a table, view, or synonym that no longer exists.
Action:Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.
ORA-00981 cannot mix table and system auditing options

Cause:Both table-wide and system-wide options were specified within a single AUDIT statement.
Action:Check the AUDIT command syntax. Then retry one or more AUDIT statements.
ORA-00982 missing plus sign

Cause:A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign is expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses.
Action:Correct the SQL syntax and retry the statement.
ORA-00984 column not allowed here

Cause:A column name was used in an expression where it is not permitted, such as in the VALUES clause of an INSERT statement.
Action:Check the syntax of the statement and use column names only where appropriate.
ORA-00985 invalid program name

Cause:Probably a syntax error.
Action:Correct syntax.
ORA-00986 missing or invalid group names(s)

Cause:Probably a syntax error.
Action:Correct syntax.
ORA-00987 missing or invalid username(s)

Cause:No username was specified in a GRANT statement or one of the specified usernames is invalid. Valid usernames must be specified following the keyword TO in a GRANT statement to define a user. A username must begin with a letter, consist only of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word.
Action:Specify a valid username, or list of usernames, following the keyword TO in the GRANT statement.
ORA-00988 missing or invalid password(s)

Cause:More usernames than passwords were specified in a GRANT statement. A valid password must be specified for each username listed in the GRANT statement.
Action:Enter a valid password for each username.
ORA-00989 too many passwords for usernames given

Cause:More passwords than usernames were specified in a GRANT statement. Only one password may be entered for each username listed in the GRANT statement.
Action:Enter an equal number of usernames and passwords.
ORA-00990 missing or invalid privilege

Cause:No privileges were specified in a GRANT privilege statement, or one of the specified privileges is invalid.
Action:Enter one or more valid privileges such as SELECT, INSERT, DELETE, UPDATE, ALTER, INDEX, REFERENCES, or ALL. More than one privilege may be granted by entering the privileges in a list separated by commas (,) or by specifying the keyword ALL to grant all privileges.
ORA-00991 only MAC privileges may be granted to procedures

Cause:Object privileges or non-MAC system privileges were granted to the procedure.
Action:Only grant MAC privileges using the PROCEDURE clause.

ORA-00992 invalid format for REVOKE command

Cause:An invalid form of the REVOKE command was entered. There are two forms of the REVOKE command. The first form is used to revoke a user's database access privileges. The second form is used to revoke a user's object privileges.
Action:Check the command syntax and retry the statement.
ORA-00993 missing GRANT keyword

Cause:The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. To grant privileges to a user and the permission to grant those privileges to another user, you must specify the keywords WITH GRANT OPTION at the end of the GRANT statement.
Action:Change the keyword WITH to the keywords WITH GRANT OPTION, then retry the statement.
ORA-00994 missing OPTION keyword

Cause:The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION.
Action:Change the keywords WITH GRANT to the keywords WITH GRANT OPTION. Then retry the statement.
ORA-00995 missing or invalid synonym identifier

Cause:In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid.
Action:Check syntax and spelling. A valid synonym name must be specified immediately following the keyword SYNONYM in both statements. Valid synonym names must begin with a letter, consist of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. They may not be reserved words.

ORA-00996 the concatenate operator is ||, not |

Cause:A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator is a double bar (||).
Action:Enter a double bar (||) for concatenation or remove the single bar (|) if concatenation was not intended.
ORA-00997 illegal use of LONG datatype

Cause:A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause.
Action:Remove the LONG value from the function or clause.
ORA-00998 must name this expression with a column alias

Cause:An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement.
Action:Enter a column name for each column in the view in parentheses after the view name.
ORA-00999 invalid view name

Cause:In a CREATE VIEW statement, the view name was missing or invalid.
Action:Enter a valid view name following CREATE VIEW. Valid view names must begin with a letter, consist of only alphanumeric characters and the special characters $, _, and #, be less than or equal to 30 characters, and may not be reserved words. If the view name contains other characters, it must be enclosed in double quotation marks.

01000-01099: User Program Interface

ORA-01000 maximum open cursors exceeded

Cause:A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action:Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
ORA-01001 invalid cursor

Cause:Either a host language program call specified an invalid cursor or the values of the AREASIZE and MAXOPENCURSORS options in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
Action:Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the AREASIZE and MAXOPENCURSORS options before precompiling.
ORA-01002 fetch out of sequence

Cause:In a host language program, a FETCH call was issued out of sequence. A successful parse-and-execute call must be issued before a fetch. This can occur if an attempt was made to FETCH from an active set after all records have been fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor after a commit. A PL/SQL cursor loop implicitly does fetches and may also cause this error.
Action:Parse and execute a SQL statement before attempting to fetch the data.
ORA-01003 no statement parsed

Cause:A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.
Action:Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor.
ORA-01004 default username feature not supported; logon denied

Cause:An attempt was made to use automatic logon on a system not supporting this feature.
Action:Provide the complete username and password to log on to Oracle.
ORA-01005 null password given; logon denied

Cause:An invalid password was given when logging on.
Action:Provide a valid password.
ORA-01006 bind variable does not exist

Cause:A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB.
Action:Modify the BIND call to reference one of the substitute variables specified in the associated SQL statement.
ORA-01007 variable not in select list

Cause:A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter is less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error.
Action:In OCI, specify a position number between 1 and the number of variables in the SELECT clause. In SQL*Forms or SQL*Report, specify an equal number of variables in the SELECT and INTO clauses.
ORA-01008 not all variables bound

Cause:A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement is executed.
Action:In OCI, use an OBIND or OBINDN call to substitute the required values.
ORA-01009 missing mandatory parameter

Cause:A host language program call did not pass all required parameters. The syntax and parameter description for each call is shown in the Programmer's Guide to the Oracle Precompilers.
Action:Check the syntax for the call and enter all required parameters.
ORA-01010 invalid OCI operation

Cause:One of the following:

Action:For the above causes:
ORA-01011 cannot use V7 compatibility mode when talking to V6 server

Cause:An attempt was made to use Oracle7 compatibility mode when accessing Oracle Version 6.
Action:Use V6 SQL language type. You may need to use the SET COMPATIBILITY V6 command.
ORA-01012 not logged on

Cause:A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.
Action:Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.
ORA-01013 user requested cancel of current operation

Cause:The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.
Action:Continue with the next operation.
ORA-01014 Oracle shutdown in progress

Cause:A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons are disabled while Oracle is being shut down.
Action:Wait until Oracle is brought back up before attempting to log on.
ORA-01015 logon called recursively

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-01016 this function can be called only after a fetch

Cause:The cursor is in an invalid state.
Action:Ensure the appropriate OCI/UPI function is called after the fetch and before the offending function.
ORA-01017 invalid username/password; logon denied

Cause:An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.

Action:Enter a valid username and password combination in the correct format.
ORA-01018 column does not have a LONG datatype

Cause:An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG.
Action:Re-execute the fetch without the LONG fetch option or create the table with a LONG column.
ORA-01019 unable to allocate memory in the user side

Cause:The user side memory allocator returned an error.
Action:Increase the size of the process heap or switch to the old set of calls.
ORA-01020 unknown context state

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-01022 database operation not supported in this configuration

Cause:The attempted database operation does not conform to the user programming interface (UPI) for the two communicating Oracle servers.

Action:You may need to upgrade one or more of your Oracle servers or relink your user-side application with new libraries.
ORA-01023 cursor context not found (invalid cursor number)

Cause:The cursor number is not a valid open cursor.
Action:Make sure that the cursor is open.
ORA-01024 invalid datatype in OCI call

Cause:An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes are specified as numbers between 1 and 7. Datatypes are described in the Programmer's Guide to the Oracle Precompilers.
Action:Check the datatype description and enter the correct number for the datatype.
ORA-01025 UPI parameter out of range

Cause:An integer parameter to a UPI function is out of range. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-01026 multiple buffers of size > 2000 in the bind list

Cause:There is more than one long buffer in the bind list.
Action:Change the buffer size to be less than 255 for the bind variable bound to a normal column.
ORA-01027 bind variables not allowed for data definition operations

Cause:An attempt was made to use a bind variable in a SQL data definition statement; for example, a CREATE TABLE AS SELECT statement in which the SELECT's WHERE clause refers to a variable.
Action:Remove the bind variable. Then retry the SQL statement.
ORA-01030 SELECT ... INTO variable does not exist

Cause:The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
Action:If it is not possible to correct the statement, call customer support.
ORA-01031 insufficient privileges

Cause:An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to UPDATE a table with only SELECT privileges, if attempting to CONNECT INTERNAL, or if attempting to install a database without the necessary operating-system privileges.

Action:Ask the database administrator to perform the operation or grant the required privileges.
ORA-01032 no such userid

Cause:This is an internal error message related to Export/Import.
Action:Contact customer support.
ORA-01033 Oracle startup or shutdown in progress

Cause:An attempt was made to log on while Oracle is being started up or shut down.
Action:Wait a few minutes. Then retry the operation.
ORA-01034 Oracle not available

Cause:Oracle was not started up. Possible causes include the following:

Action:Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. Retry after Oracle has been initialized.
ORA-01035 Oracle only available to users with RESTRICTED SESSION privilege

Cause:Logins were disallowed because an instance started in restricted mode. Only users with the RESTRICTED SESSION system privilege can log on.
Action:Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
ORA-01036 illegal variable name/num

Cause:Unable to find bind context on user side.
Action:Make sure that the variable being bound is in the SQL statement.
ORA-01037 maximum cursor memory exceeded

Cause:An attempt was made to process a complex SQL statement that consumed all available memory of the cursor.
Action:Simplify the complex SQL statement.
ORA-01038 cannot write datafile version num with Oracle Version num

Cause:An attempt was made to write datafile headers in an old format. The new format cannot be used until after the database has been verified as being compatible with this software version.
Action:Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, use the previous software release to do the operation.
ORA-01039 insufficient privileges on underlying objects of the view

Cause:An attempt was made to use another user's view without the necessary privileges on the underlying objects of the view.
Action:Obtain the necessary privileges or do not perform the offending operation.
ORA-01040 invalid character in password; logon denied

Cause:There are multi-byte characters in the password or some characters in the password are not in the US7ASCII range.
Action:Retry password with valid characters.
ORA-01041 internal error. HOSTDEF extension does not exist

Cause:The pointer to the HOSTDEF extension in HOSTDEF is null.
Action:Report as a bug to customer support.
ORA-01042 detaching a session with open cursors not allowed

Cause:An attempt was made to detach a session that has open cursors.
Action:Close all the cursors before detaching the session.
ORA-01043 user side memory corruption [num], [num], [num], [num]

Cause:The application code corrupted some of the user memory.
Action:Make certain that the application code is not overwriting memory. Contact customer support.
ORA-01044 size num of buffer bound to variable name exceeds maximum num

Cause:An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. The total array size for arrays is calculated as (element_size) * (number of elements)
Action:Reduce the buffer size.
ORA-01045 user name lacks CREATE SESSION privilege; logon denied

Cause:An attempt was made to connect to a userid that does not have create session privilege.
Action:If required, GRANT the user the CREATE SESSION privilege.
ORA-01046 cannot acquire space to extend context area

Cause:Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message.
Action:Close some cursors and try again or check operating system quotas to allow use of more virtual memory. See also your operating system-specific Oracle documentation.
ORA-01047 the above error occurred in schema=name, package=name, procedure=name

Cause:This message is displayed after a previous message to provide more specific information.
Action:See the cause and action for the previous message.
ORA-01048 couldn't find the specified procedure in the given context

Cause:The user of the procedure specified a deferred RPC that does not exist.
Action:Ensure that the procedure was specified correctly and that the replication process can locate the procedure.
ORA-01049 bind by name is not supported in streamed RPC

Cause:This error occurs when a newer server version requests from an older server version an operation that is not supported.
Action:You may need to upgrade one or more of your Oracle servers or relink your user application with new libraries.
ORA-01050 cannot acquire space to open context area

Cause:Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message.
Action:Close some cursors and try again or check operating system quotas to allow use of more virtual memory. See also your operating system-specific Oracle documentation.
ORA-01051 deferred RPC buffer format invalid

Cause:The deferred RPC data in SYS.DEF$_CALL is corrupted.
Action:Contact customer support.
ORA-01053 user storage address cannot be read

Cause:A bind variable or other user area could not be read by Oracle.
Action:Check that binds are done correctly on valid user buffers, then retry the operation.
ORA-01054 user storage address cannot be written

Cause:A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle.
Action:Check that INTO variables and indicators are correctly specified. Then retry the operation.
ORA-01057 invalid or ambiguous block.field reference in user exit

Cause:The reference to a block.field identifier in a user exit is incorrect or ambiguous, probably because it is misspelled or incomplete.
Action:Check syntax and identifier spelling. Then correct the reference.
ORA-01058 internal New Upi interface error

Cause:An attempt was made to delete a non-existent HSTDEF extension.
Action:Contact customer support.
ORA-01059 parse expected before a bind or execute

Cause:The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.
Action:Ensure the statement is parsed before a bind or execute.
ORA-01060 array binds or executes not allowed

Cause:The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.
Action:Bind a single cursor or execute the PL/SQL block one.
ORA-01070 using an old version of Oracle for the server

Cause:An attempt was made to run an older, obsolete Oracle7 Server.
Action:Upgrade the server.
ORA-01071 cannot perform operation without starting up Oracle

Cause:An attempt was made to perform an operation before Oracle was started.
Action:Start up Oracle. Then retry the operation.
ORA-01072 cannot stop Oracle; Oracle not running

Cause:An attempt was made to stop Oracle, but Oracle was not running.
Action:No action required.
ORA-01073 fatal connection error: unrecognized call type

Cause:An illegal internal operation was attempted. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-01074 cannot shut down Oracle; inside a logon session - log off first

Cause:An attempt was made to shut down Oracle inside a logon session.
Action:Log off before shutting down Oracle.
ORA-01075 currently logged on

Cause:An attempt was made to log on while already logged on.
Action:No action required.
ORA-01076 multiple logons per process not yet supported

Cause:Oracle does not support multiple logons per process.
Action:No action required.
ORA-01077 background process initialization failure

Cause:A failure occurred during initialization of the background processes.
Action:Refer to the diagnostic information in the accompanying message stack or in the trace file and take appropriate action.
ORA-01078 failure in processing initialization parameters

Cause:A failure occurred during processing of the initialization parameters during system startup.
Action:Refer to the diagnostic information in the accompanying message stack and take appropriate action.
ORA-01079 Oracle database was not properly created, operation aborted

Cause:There was an error when the database or control file was created.
Action:Check the message signaled when the database was first created or when the control file was re-created. Take appropriate actions to re-create the database or a new control file.
ORA-01080 error in shutting down Oracle

Cause:A failure occurred during system shutdown.
Action:Refer to the diagnostic information in the accompanying message stack and take appropriate action.
ORA-01081 cannot start already-running Oracle - shut it down first

Cause:An attempt was made to start Oracle while it was already running.
Action:Shut down Oracle first, if you want to restart it.
ORA-01083 value of parameter name is inconsistent with that of other servers

Cause:The value of the given initialization parameter is required to be the same for all servers in the parallel configuration.
Action:Change the value in the initialization parameter file to match that of the other control files.
ORA-01084 invalid argument in OCI call

Cause:The failing OCI call contains an argument with an invalid value.
Action:Use valid argument values. For more information, see the Programmer's Guide to the Oracle Call Interface and the appropriate programming language supplement.
ORA-01085 preceding errors in deferred RPC to name.name.name

Cause:Errors were encountered when the named procedure was executed as a deferred, remote procedure call.
Action:Correct the cause of the preceding errors.
ORA-01086 savepoint name never established

Cause:An attempt was made to roll back to a savepoint that was never established.
Action:No action required.
ORA-01087 cannot start up Oracle - currently logged on

Cause:An attempt was made to start up Oracle by a user who is currently logged on.
Action:Log off. Then issue the STARTUP command.
ORA-01088 cannot shut down Oracle while active processes exist

Cause:Users are still logged on to the instance.
Action:Either wait for all users to log off or issue the SHUTDOWN IMMEDIATE command to force the users off the system. Alternatively, issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.
ORA-01089 immediate shutdown in progress - no operations are permitted

Cause:The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, terminating any active operations.
Action:Wait for the instance to be restarted or contact the database administrator.
ORA-01090 shutdown in progress - connection is not permitted

Cause:The SHUTDOWN command was used to shut down a running Oracle instance, disallowing any connects to Oracle.
Action:Wait for the instance to restart or contact the database administrator.
ORA-01091 failure during startup force

Cause:Unable to destroy the old SGA.
Action:Manually remove the old SGA. See your operating system-specific Oracle documentation for instructions. Then retry the STARTUP command.
ORA-01092 Oracle instance terminated. Disconnection forced

Cause:The instance connected to was terminated abnormally, probably due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance.
Action:Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again.
ORA-01093 ALTER DATABASE CLOSE only permitted with no sessions connected

Cause:There is at lease one more session, other than the current one, logged in to the instance. ALTER DATABASE CLOSE is not permitted when other sessions are active.
Action:Find the other sessions and disconnect them. Then retry the ALTER DATABASE CLOSE command. Also, issue the SHUTDOWN IMMEDIATE command to force users off the system, or issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.
ORA-01094 ALTER DATABASE CLOSE in progress. Connections not permitted

Cause:An attempt was made to connect while the database is being closed with the ALTER DATABASE CLOSE command.
Action:Attempt to connect again when the database is open. Contact the database administrator to find out when the database will be open.
ORA-01095 DML statement processed zero rows

Cause:A DML cursor from the OTEX() call processed 0 rows when executed.
Action:Caller can either do a rollback or ignore the message and execute the rest of the cursors in the cursor array.
ORA-01096 program version num incompatible with instance num

Cause:The program was linked with a different version of the server than the instance to which it is attempting to connect.
Action:Relink the program against the same version of Oracle as the instance or restart (startup force) the database using the program's version of the SERVER.
ORA-01097 cannot shutdown while in a transaction - commit or rollback

Cause:An attempt was made to shut down the database while a transaction was in progress.
Action:Either commit or rollback the current transaction and then attempt to shut down the database.
ORA-01098 program interface error during LONG insert

Cause:The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid.
Action:Retry the insert or update.
ORA-01099 cannot mount database in SHARED mode if started in single process mode

Cause:An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.
Action:Either mount the database in EXCLUSIVE mode or set the initialization parameter SINGLE_PROCESS to FALSE before starting the instance in parallel (shared) mode.

01100-01250: Oracle Files

ORA-01100 database already mounted

Cause:An attempt was made to mount a database with the name of a currently mounted database.
Action:No action required.
ORA-01101 database being created currently mounted by some other instance

Cause:An attempt was made to create a database with the name of a currently mounted database.
Action:Either change the database name or shut down the other instance.
ORA-01102 cannot mount database in exclusive mode

Cause:An instance tried to mount the database in exclusive mode, but some other instance has already mounted the database in exclusive or parallel mode.
Action:Either mount the database in parallel mode or shut down all other instances before mounting the database in exclusive mode.
ORA-01103 database name name in control file is not name

Cause:The database name used does not match that in the control file.
Action:Ensure the correct control file and database name are used.
ORA-01104 number of control files num does not equal num

Cause:The number of control files used by this instance disagrees with the number of control files in an existing instance that is accessing the same database.
Action:Make sure all control files are listed in the initialization parameter CONTROL_FILES, then retry the operation.
ORA-01105 mount is incompatible with mounts by other instances

Cause:An attempt was made to mount the database, but another instance has already mounted a database by the same name, and the mounts are not compatible. Additional messages will accompany this message to report why the mounts are incompatible.
Action:See the accompanying messages for the appropriate action to take.
ORA-01106 database must be closed before dismounting

Cause:An attempt was made to dismount a database before it was closed.
Action:Close the database, then retry the operation.
ORA-01107 database must be mounted for media recovery

Cause:An attempt to perform media recovery was made, but the database is not mounted.
Action:Mount the database, then retry the operation.
ORA-01108 media recovery active on file name

Cause:Media recovery is actively being applied to the given file. The file cannot be used for normal database access or crash recovery.
Action:Wait for media recovery to complete or cancel the media recovery session.
ORA-01109 database not open

Cause:An attempt was made to perform an operation on an unopened database.
Action:Open the database, then retry the operation.
ORA-01110 datafile name: str

Cause:This message reports the filename involved with other messages.
Action:See the associated messages for a description of the problem.
ORA-01111 name for datafile name is unknown - rename to correct file

Cause:The datafile was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.
Action:Rename the missing file to the name of the real file.
ORA-01112 media recovery not started

Cause:An attempt was made to continue media recovery, but media recovery had not been started.
Action:No action required.
ORA-01113 file name needs media recovery

Cause:An attempt was made to open a datafile that is in need of media recovery.
Action:First apply media recovery to the datafile identified in the message, then retry the operation.
ORA-01114 IO error writing block to file name block # num

Cause:The device on which the file resides is probably off line.
Action:Restore access to the device, then retry the operation.
ORA-01115 IO error reading block from file name block # num

Cause:The device on which the file resides is probably off line.
Action:Restore access to the device, then retry the operation.
ORA-01116 error in opening datafile name

Cause:Usually the file is not accessible.
Action:Make sure the datafile is in the expected location and can be accessed properly, then retry the operation.
ORA-01117 adding file name with illegal block size num, limit is num

Cause:An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed.
Action:Retry the operation with a smaller block size.
ORA-01118 cannot add any more datafiles: limit of num exceeded

Cause:An attempt to add a datafile failed because the limit for such files had already been reached.
Action:If more database space is required, export the database and re-create it with a higher limit for datafiles and perhaps increased file size.
ORA-01119 error in creating datafile name

Cause:Insufficient space on device.
Action:Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the statement, then specify a file size smaller than the available space on the device.
ORA-01120 cannot remove online datafile name; database is open or mounted parallel

Cause:An attempt to remove an online datafile failed because the file was not closed or was opened in parallel mode. This message can occur when trying to drop a tablespace. A tablespace cannot be dropped while users are accessing its data, index, rollback, or temporary segments or while the database is mounted in parallel mode.
Action:Shut down Oracle and mount the database in exclusive mode to drop a tablespace. To prevent users from opening the tablespace, take it off line or put the instance in restricted access mode.
ORA-01121 cannot rename datafile name - file is in use or recovery

Cause:An attempt to rename an online datafile failed because the file was not closed or was being recovered. Either the file is online and the datafile is open to some instance, or another process is currently performing media recovery on the file.
Action:Close the file or shut down Oracle and mount the database in exclusive mode. End all recovery sessions. To prevent users from opening the file, take its tablespace off line or put the instance into restricted mode.
ORA-01122 datafile name - failed verification check

Cause:The information in the datafile is inconsistent with information from the control file. This could be for any of the following reasons:

Action:Make certain that the datafiles and control files are the correct files for this database, then retry the operation.
ORA-01123 cannot start online backup; media recovery not enabled

Cause:An attempt to start backup of an online tablespace failed because archiving was not enabled.
Action:Enable archiving and retry the operation.
ORA-01124 cannot recover online file name - file is in use or recovery

Cause:An attempt to do media recover found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is currently doing media recovery on the file.
Action:Do not do media recovery.
ORA-01125 cannot disable media recovery - file name has online backup set

Cause:An attempt to disable media recovery encountered an online recovery still in progress.
Action:Wait for the recovery to finish before retrying the operation.
ORA-01126 database must be mounted exclusive and not open for this operation

Cause:An operation failed because the database was not mounted in exclusive mode.
Action:Shut down Oracle and mount the database in exclusive mode.
ORA-01127 database name name exceeds size limit of num characters

Cause:The specified database name is too long.
Action:Shorten the database name to eight characters or fewer, then retry the operation.
ORA-01128 cannot start online backup - file name is offline

Cause:A file to be backed up in the online backup is offline.
Action:Either of the following:

ORA-01129 user's default tablespace does not exist

Cause:A user's default or temporary tablespace was dropped.
Action:Re-create the tablespace that was dropped or change the user's default or temporary tablespace.
ORA-01130 datafile version num incompatible with Oracle Version num

Cause:The named datafile was created under an incompatible version of Oracle, or the file is invalid or nonexistent.
Action:Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists.
ORA-01131 DB_FILES files initialization parameter value num exceeds limit of num

Cause:The specified value of the initialization parameter DB_FILES is too large.
Action:Reduce the value of the DB_FILES parameter and retry the operation.
ORA-01132 length of datafile name name exceeds limit of num characters

Cause:The specified datafile name is too long.
Action:Shorten the filename and retry the operation.
ORA-01133 length of log file name name exceeds limit of num characters

Cause:The specified redo log filename is too long.
Action:Shorten the filename and retry the operation.
ORA-01134 database mounted exclusive by another instance

Cause:An attempt to access a database failed because it is mounted in exclusive mode by another instance.
Action:Either shut down the other instance or wait for the other instance to either close the database or mount it in parallel mode, before retrying the operation.
ORA-01135 file name accessed for DML query is offline

Cause:A query failed because it referenced a datafile that belongs to an offline tablespace. An offline tablespace must be brought online to access its data.
Action:Wait until the tablespace is brought online before executing the query.
ORA-01136 specified size of file num num blocks is less than original size of num blocks

Cause:An attempt was made to specify a size in the AS clause of the ALTER DATABASE CREATE datafile command that is smaller than the size needed.
Action:Issue the statement again using the correct size for the file.
ORA-01137 datafile name is still in the middle of going offline

Cause:It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.
Action:Wait for the other instance to release the lock on the file.
ORA-01138 database must either be open in this instance or not at all

Cause:The requested operation cannot be done when the database is mounted but not open by this instance, and another instance has the database open.
Action:Execute the operation in the open instance, open the database in the current instance, or close the database in the other instances.
ORA-01139 RESET LOGS option only valid after an incomplete database recovery

Cause:The RESET LOGS option was specified in an ALTER DATABASE OPEN statement, but there has been no incomplete recovery session.
Action:Re-execute the statement without specifying RESET LOGS.
ORA-01140 cannot end online backup - all files are offline

Cause:All the files were offline when attempting to end an online backup.
Action:None. Online backup does not need to be ended for this tablespace.
ORA-01141 error renaming datafile name - new file name not found

Cause:An attempt to change a datafile's name in the control file failed because no file was found with the new name.
Action:Make sure that the datafile has been properly renamed by the operating system, then retry the operation.
ORA-01142 cannot end online backup - none of the files are in backup

Cause:None of the files were found to be in the online backup when attempting to end the online backup.
Action:None. Online backup does not need to be ended for this tablespace.
ORA-01143 cannot disable media recovery - file name needs media recovery

Cause:An attempt to disable media recovery found a file that needs media recovery. Therefore, media recovery cannot be disabled.
Action:Recover the offending file or drop the tablespace to which it belongs, then retry the operation.
ORA-01144 file size num blocks exceeds maximum of num blocks

Cause:The specified file size is larger than the maximum allowable size.
Action:Specify a smaller size.
ORA-01145 offline immediate disallowed unless media recovery enabled

Cause:ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVEREDO LOG mode.
Action:Take the tablespace offline as usual or do a shutdown abort before attempting the required operation. It is worthwhile reconsidering the backup strategy for the database. The attempted operations can be done if ARCHIVEREDO LOG mode is enabled.
ORA-01146 cannot start online backup - file name is already in backup

Cause:An attempt was made to start an online backup, but an online backup was already started for one of the datafiles.
Action:End the first backup before beginning another.
ORA-01147 SYSTEM tablespace file name is offline

Cause:A file belonging to the SYSTEM tablespace has been marked offline by the database administrator. The database cannot be started until all SYSTEM tablespace files are online and can be opened.
Action:Bring the file online.
ORA-01148 database must be mounted EXCLUSIVE for this operation

Cause:An attempt was made to mount the database PARALLEL without the existence of a lock manager.
Action:Mount the database in EXCLUSIVE mode and retry the operation.
ORA-01149 cannot shutdown - file name has online backup set

Cause:A normal shutdown was attempted while the online backup was in progress.
Action:End the online backup and then shut down.
ORA-01150 cannot prevent writes - file name has online backup set

Cause:Tablespace cannot be taken offline or made read-only when online backup is running. Ending the backup entails writing the file header, which this operation, were it permitted, would prevent.
Action:End the online backup and then take the tablespace offline or make it read-only.
ORA-01151 use media recovery to recover block, restore backup if needed

Cause:Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. This message is usually accompanied by ORA-01172.
Action:There is additional information for ORA-01172. Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, restore the file from a backup and recover it again.
ORA-01152 file name was not restored from a sufficiently old backup

Cause:An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action:Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery.
ORA-01153 an incompatible media recovery is active

Cause:An attempt was made to start an incompatible media recovery or to open resetlogs during media recovery. Media recovery sessions are incompatible if they attempt to recover the same datafile. Incomplete media recovery or OPEN RESETLOGS is incompatible with any media recovery.
Action:Complete or cancel the other media recovery session.
ORA-01154 database busy. Open, Close, mount, and dismount not allowed now

Cause:Some operation is in progress that expects the state of the instance to remain open or mounted.
Action:Wait for the operation to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
ORA-01155 the database is being opened, closed, mounted, or dismounted

Cause:The attempted operation will not succeed while the instance is in one of the states mentioned in the message.
Action:Wait for the open, close, mount, or dismount to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
ORA-01156 recovery in progress may need access to files

Cause:Either media or instance recovery is in progress. The recovery may need access to the files that the attempted operation tried to use.
Action:Wait for the recovery to complete and try again.
ORA-01157 cannot identify datafile name - file not found

Cause:The background process was not able to find one of the datafiles. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online datafiles. Accompanying messages from the operating system will describe why the file was not found.
Action:Make the file available to the database. Then either open the database or do ALTER SYSTEM CHECK datafiles. See also your operating system-specific Oracle documentation.
ORA-01158 database name already mounted

Cause:Another instance has mounted a database of this name already.
Action:Find and shut down the instance that has this database mounted before issuing the CREATE CONTROLFILE statement.
ORA-01159 file name is not from same database as previous files - wrong database id

Cause:Not all of the files specified in the CREATE CONTROLFILE statement are from the same database.
Action:Check the list of files specified in the CREATE CONTROLFILE statement and remove files that are not part of the same database.
ORA-01160 file name is not a str - it is of type str

Cause:The file in the datafile or log file section of the CREATE CONTROLFILE statement is not of the type listed in the command line.
Action:Check the file and determine its type. Enter the command again using the correct type for the file.
ORA-01161 database name name in file header does not match given name of name

Cause:The database name given at the command line does not match the database name found in the file header. The database name specified at the command line is incorrect.
Action:Enter the command again with the correct name for the database.
ORA-01162 block size num in file header does not match DB_BLOCK_SIZE num

Cause:CREATE CONTROLFILE discovered that the block size for this file is incompatible with the initialization parameter DB_BLOCK_SIZE used to allocate cache buffers. If this is not the first file, then there is a mixture of block sizes, or the file is corrupt.
Action:If this is the first file in the command, then correct DB_BLOCK_SIZE to match the file and restart the instance; if it is not the first file, find the correct version of the file.
ORA-01163 SIZE clause indicates num blocks, but should match header num

Cause:The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.
Action:Specify the correct filename and size, in bytes.
ORA-01164 MAXLOGFILES may not exceed num

Cause:The value for MAXLOGFILES specified on the command line is greater than num.
Action:Retry the command with a value of MAXLOGFILES that is num or less.
ORA-01165 MAXDATAFILES may not exceed num

Cause:The value for MAXDATAFILES specified on the command line is greater than num.
Action:Retry the command with a value of MAXDATAFILES that is num or less.
ORA-01166 file number num is larger than num num

Cause:In the CREATE CONTROLFILE statement, the file mentioned has a file number that is larger than that specified in MAXDATAFILES or MAXLOGFILES, or the file number is larger than the maximums specified in the initialization parameter, DB_FILES.
Action:Increase the values of MAXLOGFILES, MAXDATAFILES, or of the parameter DB_FILES.
ORA-01167 two files are the same file/group number or the same file

Cause:There is an overlap of file numbers in the files specified on the command line, or the same file is specified twice. If they are not the exact same file, then one is likely to be a backup of the other. If they are two members of the same redo log, they must be specified together in a group file spec.
Action:Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files, then omit the earlier backup. If they are members of the same redo log, ensure they are in the same group file specification.
ORA-01168 physical block size num does not match size num of other members

Cause:The file is located on a device with a different physical block size than the other members in the group.
Action:Use a physical device with matching block size.
ORA-01169 datafile number 1 not found. Must be present

Cause:datafile number 1 was not specified in a CREATE CONTROLFILE statement.
Action:Locate datafile number 1 and retry the CREATE CONTROLFILE statement, making certain to include datafile on the command line.
ORA-01170 file not found name

Cause:A file specified in the CREATE CONTROLFILE statement was not found. All datafiles and all redo log files, if NORESETLOGS was used, must be accessible by the process that issues the CREATE CONTROLFILE statement.
Action:Check the statement for a typing mistake in the filename and check for the existence of all files. Then issue the statement again after correcting the filenames.
ORA-01171 datafile str is going offline due to error advancing checkpoint

Cause:The checkpoint in the file header could not be advanced. See accompanying messages for the reason. The datafile will be taken offline the same as for a write error of a data block.
Action:See accompanying messages for details. Restore access to the file, do media recovery, and bring it back online.
ORA-01172 recovery of thread num stuck at block num of file name

Cause:Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
Action:Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it again.
ORA-01173 data dictionary indicates missing datafile from system tablespace

Cause:Either

Action:Either
ORA-01174 DB_FILES is num but needs to be num to be compatible

Cause:The maximum number of datafiles supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action:Change the value of the DB_FILES initialization parameter to be compatible.
ORA-01175 data dictionary has more than the num files allowed by the instance

Cause:The data dictionary has more files than the instance can support.
Action:Increase the value of the initialization parameter DB_FILES, then shut down and restart the instance.
ORA-01176 data dictionary has more than the num files allowed by the control file

Cause:After a CREATE CONTROLFILE statement, the data dictionary has more datafiles than supported by the control file.
Action:Re-create the control file with a larger value for MAXDATAFILES.
ORA-01177 datafile does not match dictionary - probably old incarnation

Cause:When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
Action:Do a CREATE CONTROLFILE with the correct file or none at all.
ORA-01178 file name created before last CREATE CONTROLFILE, cannot be recreated

Cause:An attempt was made to use the ALTER DATABASE CREATE datafile to re-create a datafile that existed at the last CREATE CONTROLFILE command. The information needed to re-create the file was lost with the control file that existed when the file was added to the database.
Action:Find a backup of the file and recover it. Perform incomplete recovery to the time before the file was originally created.
ORA-01179 file name does not exist

Cause:During datafile recovery, a file was listed that was not part of the database.
Action:Recheck the filename. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the filename is translated in the operating environment of SQL*DBA.
ORA-01180 cannot create datafile 1

Cause:datafile 1 cannot be created with the ALTERDATABASECREATEDATA FILE command.
Action:Either recover the file from a backup or re-create the database.
ORA-01181 file name created before last RESETLOGS, cannot be recreated

Cause:An attempt was made to use the ALTER DATABASE CREATE datafile command to re-create a datafile that existed before the last time the database was opened using the RESETLOGS option.
Action:Find a backup of the file and recover the backup file. Perform incomplete recovery to a time before the file was originally created.
ORA-01182 cannot create datafile name - file is in use or recovery

Cause:An attempt was made to use the ALTER DATABASE CREATE datafile command to re-create a datafile that is currently online in an open instance or is currently being recovered.
Action:Close the database to all instances or end all recovery sessions. Then take the file offline and retry the operation.
ORA-01183 cannot mount database in SHARED mode

Cause:The database is mounted in exclusive mode by another instance. It is not possible to mount a database in SHARED mode if it is mounted in exclusive mode by another instance.
Action:Shut down the other instance and try again.
ORA-01184 log file group num already exists

Cause:An ALTER DATABASE ADD log file command specified a log number for the new redo log which is already in use.
Action:Specify a different redo log file number or let the database choose an unused value.
ORA-01185 log file group number num is invalid

Cause:An ALTER DATABASE ADD log file command specified a redo log number for the new redo log that is too large.
Action:Specify a valid redo log file number.
ORA-01186 verification tests failed on file name

Cause:The datafile did not pass the checks to ensure it is part of the database. See the accompanying messages for the reason the verification failed.
Action:Make the correct file available to database. Then either open the database or execute ALTER DATABASE CHECK.
ORA-01187 cannot read from file name because it failed verification tests

Cause:The datafile did not pass the checks to ensure it is part of the database. Reading the file is not allowed until it is verified.
Action:Make the correct file available to database. Then either open the database or execute ALTER DATABASE CHECK.
ORA-01188 block size num in header does not match physical block size

Cause:A redo log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the redo log.
Action:Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE.
ORA-01189 file is from a different RESETLOGS than previous files

Cause:In a CREATE CONTROLFILE command, either this file or all previous files were backups from before the last RESETLOGS. This also may occur if this is a file that is offline and has been offline since before the last RESETLOGS.
Action:If the file was taken offline normally before the last RESETLOGS and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise, find the version of the mentioned file consistent with the rest of the datafiles and retry the command.
ORA-01190 control file or datafile name is from before the last RESETLOGS

Cause:An attempt was made to perform media recovery when the redo log reset information in a datafile does not match the control file. Either the datafile or the control file must be a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS.
Action:Restore the file from a more recent backup.
ORA-01191 file name is already offline - cannot do a normal offline

Cause:An attempt was made to take a tablespace offline as usual, but the file named in the message was already offline.
Action:Bring the datafile online first or use the IMMEDIATE option when taking the tablespace offline.
ORA-01192 must have at least one enabled thread

Cause:At least two redo log files from at least one thread must be specified in the CREATE CONTROLFILE command line.
Action:Find the missing redo log files and retry the command with the newly found redo log files included in the command line.
ORA-01193 file name is not the same file seen at start of recovery

Cause:An attempt was made to perform media recovery on a file, but a different copy of the file now exists since the last media recovery. Perhaps an invalid backup of the file was restored.
Action:Find the correct version of the file, then retry media recovery.
ORA-01194 file name needs more recovery to be consistent

Cause:An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The named file was not closed cleanly when it was last opened by the database. The most likely cause of this message is forgetting to restore the file from a backup before doing incomplete recovery.
Action:The file must be recovered to a time when it was not being updated. Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat recovery.

ORA-01195 online backup of file name needs more recovery to be consistent

Cause:An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The reported file is an online backup that must be recovered to the time the backup ended.
Action:Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat the recovery.

ORA-01196 file name is inconsistent due to a failed media recovery session

Cause:The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.
Action:Either apply more logs until the file is consistent or restore the backup again and repeat recovery.

ORA-01197 thread num only contains one log

Cause:During a CREATE CONTROLFILE statement, all threads represented in the redo logs must be represented by at least two redo logs: a last redo log and a second redo log. The named thread does not contain two redo logs.
Action:Either find more redo logs from the named thread or remove all references to redo logs from that thread, then retry the command.
ORA-01198 must specify size for log file name if RESETLOGS

Cause:File sizes must be given for all redo log files if doing a CREATE CONTROLFILE with the RESETLOGS option.
Action:Retry the command with the appropriate redo log file size.
ORA-01200 actual file size of num is smaller than correct size of num blocks

Cause:The size of the file, as returned by the operating system, is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated.
Action:Restore a good copy of the datafile from a backup and perform recovery as needed.
ORA-01201 file size num in header does not match size num in control file

Cause:The file sizes in the control file and in the file header do not match. One of the files probably is corrupted.
Action:Replace the corrupted file with a good copy and perform recovery as needed.
ORA-01202 wrong incarnation of this file - wrong creation time

Cause:The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.
Action:Restore a current copy of the datafile and perform recovery as needed.
ORA-01203 wrong incarnation of this file - wrong creation SCN

Cause:The creation change number in the file header is not the same as the creation change number in the control file. This is probably a copy of a file that was dropped.
Action:Restore a current copy of the datafile and perform recovery as needed.
ORA-01204 wrong file - file number is num rather than num

Cause:The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.
Action:Restore a copy of the correct datafile and perform recovery as needed.
ORA-01205 not a datafile - type number in header is num

Cause:The file type in the header is not correct for a datafile. This is probably a redo log file or control file.
Action:Restore a copy of the correct datafile and perform recovery as needed.
ORA-01206 file is not part of this database - wrong database id

Cause:The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a datafile at all. If the database was rebuilt, this may be a file from before the rebuild.
Action:Restore a copy of the correct datafile and perform recovery as needed.
ORA-01207 file is more recent than control file - old control file

Cause:The control file change sequence number in the datafile is greater than the number in the control file. This implies that the wrong control file is being used.
Note: If this message occurs repeatedly, by opening the database many times, the message may stop occurring without the problem being corrected. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Action:Use the current control file or perform cancel-based recovery to make the control file current. Be sure to follow all restrictions on performing a cancel-based recovery.
ORA-01208 datafile is an old version - not accessing current version

Cause:The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance or if another instance just caused this file to be placed online, then the database is probably looking at a different version of the file. Otherwise, a backup of the file was probably restored while the file was still in use.
Action:Make correct file available to database. Then either open the database or do ALTER DATABASE CHECK.
ORA-01209 datafile is from before the last RESETLOGS

Cause:The reset redo log data in the file header does not match the control file. If the database is closed or the file is offline, this is an old backup that was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is already open by another instance or if another instance just put this file online, then we are probably looking at a different version of the file. Otherwise a backup of the file was probably restored while the file was in use.
Action:Make the correct file available to the database. Then either open the database or issue an ALTER DATABASE CHECK statement.
ORA-01210 datafile header is media corrupt

Cause:The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistency of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.
Action:Make the correct file available to the database. Refer to any trace file generated after this message for more information. If the trace file indicates that the checksum is wrong, restore the file from a backup and perform media recovery.
ORA-01211 Version 6 datafile is not from conversion to Oracle7

Cause:The file is not a copy of the file last used under Version 6. When converting a database from Version 6 to Oracle7, the conversion utility must be run the last time the database is opened under Version 6. Only the datafiles that were current when the conversion was done may be accessed by Oracle7. Either this datafile is a backup taken from before the conversion or the database was opened by Version 6 after the conversion.
Action:Have the operating system make the correct datafile available to the database or repeat the Version 6 to Oracle7 conversion.
ORA-01212 MAXLOGMEMBERS may not exceed num

Cause:The value specified for MAXLOGMEMBERS is too large.
Action:Retry the command with a smaller value for MAXLOGMEMBERS.
ORA-01213 MAXINSTANCES may not exceed num

Cause:The value specified for MAXINSTANCES is too large.
Action:Retry the command with a smaller value for MAXINSTANCES.
ORA-01214 MAXLOGHISTORY may not exceed num

Cause:The value specified for MAXLOGHISTORY is too large.
Action:Retry the command with a smaller value for MAXLOGHISTORY.
ORA-01215 enabled thread num is missing after CREATE CONTROLFILE

Cause:A CREATE CONTROLFILE command did not list all of the enabled threads for the database.
Action:Issue the CREATE CONTROLFILE command again and include all of the enabled threads.
ORA-01216 thread num is expected to be disabled after CREATE CONTROLFILE

Cause:A thread specified in the CREATE CONTROLFILE command was enabled, but the datafiles indicate that the thread should be disabled. This is probably because the redo log files supplied to the CREATE CONTROLFILE command are from a time before the thread was disabled.
Action:This thread is not required for the operation of the database. Retry the command without specifying the thread. If desired, the thread can be re-created after the database has been opened.
ORA-01217 log file member belongs to a different redo log file group

Cause:A member of a redo log file group specified in the CREATE CONTROLFILE command is not part of the same group as the previous members.
Action:Group together the correct members of the redo log file group for the CREATE CONTROLFILE command.
ORA-01218 log file member is not from the same point-in-time

Cause:A member of a redo log file group specified in the CREATE CONTROLFILE command is from a different point in time from the previous members. One of the members specified may be an older, possibly a backup copy, version of the redo log.
Action:Find the correct version of the redo log or leave it out of the CREATE CONTROLFILE command.
ORA-01219 database not open: queries allowed on fixed tables/views only

Cause:A query was issued against an object not recognized as a fixed table or fixed view before the database was opened.
Action:Revise the query to include only fixed objects or open the database.
ORA-01220 file based sort illegal before database is open

Cause:A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
Action:Rephrase the query to avoid a large sort and increase the SORT_AREA_SIZE parameter in the initialization parameter file to enable the sort to be done in memory.
ORA-01221 datafile name is not the same file to a background process

Cause:When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The time-stamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
Action:Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the filename successfully access the same file when opened by a background process.
ORA-01222 MAXINSTANCES of num requires MAXLOGFILES be at least num, not num

Cause:An attempt was made to create a database or control file that does not have room for at least two redo logs per thread of redo. A thread of redo must have two online redo logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
Action:Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
ORA-01223 RESETLOGS must be specified to set a new database name

Cause:The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
Action:Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.
ORA-01224 group number in header name does not match GROUP name

Cause:Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
Action:Omit the GROUP option or give the correct one.
ORA-01225 thread number num is greater than MAXINSTANCES num

Cause:The redo log is for a thread greater than the MAXINSTANCES arguments.
Action:Increase the value for MAXINSTANCES and retry the command.
ORA-01226 file header of redo log member is inconsistent with other member

Cause:The redo log file member in the accompanying message is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted redo log.
Action:Correct the redo log member or omit this member from the command.

ORA-01227 log name is inconsistent with other log

Cause:The redo log file in the accompanying message is inconsistent with the contents of other redo logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the redo log listed because all that can be detected is that there is an inconsistency. All redo log files listed in the command must be the current versions of the online redo logs.
Action:Find the correct online redo logs or use the RESETLOGS option.

ORA-01228 SET DATABASE option required to install seed database

Cause:The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database ID. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
Action:Retry the command with the SET DATABASE and RESETLOGS options.
ORA-01229 datafile name is inconsistent with logs

Cause:The datafile in the accompanying message is inconsistent with the contents of the redo logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online redo logs was missing from the command. It is also possible that one or more of the redo logs is an old copy rather than the current version. All online redo log files must be listed in the command and must be the current versions of the online redo logs.
Action:Retry the command with the correct online redo logs or use the RESETLOGS option.

ORA-01230 cannot make read only - file name is offline

Cause:An attempt to make a tablespace read-only encountered an offline file.
Action:Bring the file online and retry the operation.
ORA-01231 cannot make read write - file name is offline

Cause:An attempt to make a tablespace read-write encountered an offline file.
Action:Bring the file online and retry the operation.
ORA-01232 cannot start online backup - file name is read only

Cause:An attempt to start an online backup encountered a read-only file.
Action:Read-only files do not need to be set into online backup mode. Start the backup without using the BEGIN BACKUP command.
ORA-01233 file name is read only - cannot recover using backup control file

Cause:An attempt to do media recovery using a backup control file encountered a read-only file. Typically, read-only files do not need to be recovered. However, if the recovery is using a backup control file, all online files must be recovered.
Action:Take the read-only file offline and bring the tablespace online only after opening the database. Ensure that the backup control file was in use when the currently read-only file was read-write. If such a control file is unavailable, you may be able to re-create it using the CREATE CONTROLFILE command.
ORA-01239 database must be in ARCHIVELOG mode to use external cache

Cause:An online file used an external cache, but the database was in NOARCHIVELOG mode. Since an external cache may require media recovery this cannot be allowed.
Action:Change the database to be in ARCHIVELOG mode or do not use an external cache.

ORA-01240 too many datafiles to add in one command

Cause:The command specified adding more datafiles than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.
Action:If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands.

ORA-01241 an external cache has died

Cause:The external cache may have been restarted.
Action:Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You can also restart all instances to make sure they access all datafiles through consistent external caches.

ORA-01242 data file suffered media failure: database in NOARCHIVELOG

Cause:The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
Action:Restore accessibility to the file mentioned in the error stack and restart the instance.

ORA-01243 system tablespace file suffered media failure

Cause:A system tablespace file was detected as inaccessible due to media failure.
Action:Restore accessibility to the file mentioned in the error stack and restart the instance.

ORA-01244 unnamed datafile(s) added to controlfile by media recovery

Cause:Media recovery with a backup controlfile or a controlfile that was rebuilt encountered the creation of a datafile that was not in the controlfile. An entry has been added to the controlfile for the new datafiles, but with the file name UNNAMEDnum, where num is the file number. Attached errors describe the file names that were originally used to create the files.
Action:Rename the files to valid file names and resume recovery. If necessary, the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered, then take it offline with the DROP option.

ORA-01245 offline file name will be lost if RESETLOGS is done

Cause:An attempt was done to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the DROP option.
Action:Either bring the file online and recover it, or take it offline with the DROP option.

01400-01489: SQL Execution

ORA-01400 primary key or mandatory (NOT NULL) column is missing or NULL during insert

Cause:When inserting or updating rows, a value for a column defined as NOT NULL was not specified.
Action:Specify a value for each NOT NULL column or modify the table definition to allow NULL values in columns now defined as NOT NULL.
ORA-01401 inserted value too large for column

Cause:The value entered is larger than the maximum width defined for the column.
Action:Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.
ORA-01402 view WITH CHECK OPTION where-clause violation

Cause:An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view's WHERE clause.
Action:Examine the view's WHERE clause in the dictionary table VIEWS. If the current view does not have the CHECK OPTION, then its FROM clause must reference a second view that is defined using the CHECK OPTION. The second view's WHERE clause must also be satisfied by any INSERT or UPDATE statements. To insert the row, it may be necessary to insert it directly into the underlying table, rather than through the view.
ORA-01403 no data found

Cause:In a host language program, all records have been fetched. The return code from the fetch was +4, indicating that all records have been returned from the SQL query.
Action:Terminate processing for the SELECT statement.
ORA-01404 ALTER COLUMN will make a concatenated index too large

Cause:Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum index length (255). The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields are calculated as a length of 7, character fields are calculated at their defined width, and numeric fields are length 22.
Action:The only way to alter the column is to drop the affected index. The index cannot be recreated if to do so would exceed the maximum index width.
ORA-01405 fetched column value is NULL

Cause:The INTO clause of a FETCH operation contained a NULL value, and no indicator was used. The column buffer in the program remained unchanged, and the cursor return code was +2. This is an error unless you are running Oracle7 with DBMS=6, emulating version 6, in which case it is only a warning.
Action:You may do any of the following:

ORA-01406 fetched column value was truncated

Cause:In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3.
Action:Increase the column buffer area to hold the largest column value or perform other appropriate processing.
ORA-01407 cannot update mandatory NOT NULL column to NULL

Cause:An attempt was made to update data in a NOT NULL column to a NULL value.
Action:Specify a value for the column or modify the table definition to accept NULL values in that column.
ORA-01408 such column list already indexed

Cause:A CREATE INDEX statement specified a column that is already indexed. A single column may be indexed only once. Additional indexes may be created on the column if it is used as a portion of a concatenated index, that is, if the index consists of multiple columns.
Action:Do not attempt to re-index the column, as it is unnecessary. To create a concatenated key, specify one or more additional columns in the CREATE INDEX statement.
ORA-01409 NOSORT option may not be used; rows are not in ascending order

Cause:Creation of index with NOSORT option when rows were not ascending. The NOSORT option may only be used for indexes on groups of rows that already are in ascending order.

Action:Create the index without the NOSORT option or ensure that the table is stored in one extent.
ORA-01410 invalid ROWID

Cause:A ROWID was entered incorrectly. ROWIDs must be entered as formatted hexadecimal strings using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'.
Action:Check the format, then enter the ROWID using the correct format. ROWID format: block id, row in block, file id.
ORA-01411 cannot store the length of column in the indicator

Cause:Oracle tried to fetch a column more than 64K long and could not store the length of the column in the given indicator size of 2 bytes.
Action:Use the new bind type with callbacks to fetch the long column.
ORA-01412 zero length not allowed for this datatype

Cause:The length for datatype 97 is 0.
Action:Specify the correct length for the datatype.
ORA-01413 illegal value in packed decimal number buffer

Cause:The user buffer bound by the user as a packed decimal number contained an illegal value.
Action:Use a legal value.
ORA-01414 invalid array length when trying to bind array

Cause:An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.
Action:Specify a valid length.
ORA-01416 two tables cannot be outer-joined to each other

Cause:Two tables in a join operation specified an outer join with respect to each other. If an outer join is specified on one of the tables in a join condition, it may not be specified on the other table.
Action:Remove the outer join specification (+) from one of the tables, then retry the operation.
ORA-01417 a table may be outer joined to at most one other table

Cause:A table in a join operation specified an outer join to more than one other table. A table may specify an outer join to only one other table.
Action:Specify only one outer join (+) to this table, then retry the operation.
ORA-01418 specified index does not exist

Cause:An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that does not exist. Only existing indexes can be altered, dropped, or validated. Existing indexes may be listed by querying the data dictionary.
Action:Specify the name of an existing index in the ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement.
ORA-01422 exact fetch returns more than requested number of rows

Cause:More rows were returned from an exact fetch than specified.
Action:Rewrite the query to return fewer rows or specify more rows in the exact fetch.
ORA-01423 error encountered while checking for extra rows in exact fetch

Cause:An error was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages.
Action:See the accompanying messages and take appropriate action.
ORA-01424 missing or illegal character following the escape character

Cause:The character following the escape character in LIKE pattern is missing or not one of the wildcard characters '%' or '_'.
Action:Remove the escape character or specify the missing character.
ORA-01425 escape character must be character string of length 1

Cause:Given escape character for LIKE is not a character string of length 1.
Action:Change it to a character string of length 1.
ORA-01426 numeric overflow

Cause:Evaluation of a value expression has caused an overflow or possibly an underflow.
Action:Rewrite the expression as a series of expressions with fewer operands than the 'overloaded' expression.
ORA-01427 single-row subquery returns more than one row

Cause:The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row.
Action:Use ANY, ALL, IN, or NOT IN to specify which values to compare or reword the query so only one row is retrieved.
ORA-01428 argument num is out of range

Cause:An illegal value for a mathematical function argument was specified. For example

SELECT SQRT(-1) "Square Root" FROM DUAL;

Action:See Oracle7 Server SQL Reference manual for valid input and ranges of the mathematical functions.
ORA-01429 a date in binary format has an out of range value

Cause:The date, in binary format, for an external type DATE was out of range for one or more of the seven possible bytes.
Action:Select values for each of the seven bytes that conform to the required date specification or use the TO_DATE function with character data.
ORA-01430 column being added already exists in table

Cause:An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table.
Action:Specify a unique name for the new column, then re-execute the statement.
ORA-01431 internal inconsistency in GRANT command

Cause:An internal error occurred while attempting to execute a GRANT statement.
Action:Contact customer support.
ORA-01432 public synonym to be dropped does not exist

Cause:The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It may be a private synonym.
Action:Correct the synonym name or use DROP SYNONYM if the synonym is not public.
ORA-01433 synonym to be created is already defined

Cause:A CREATE SYNONYM statement specified a synonym name that is the same as an existing synonym, table, view, or cluster. Synonyms may not have the same name as any other synonym, table, view, or cluster available to the user creating the synonym.
Action:Specify a unique name for the synonym, then re-execute the statement.
ORA-01434 private synonym to be dropped does not exist

Cause:A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary.
Action:Specify the name of an existing synonym in the DROP SYNONYM statement.
ORA-01435 user does not exist

Cause:This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that does not exist. Only a GRANT CONNECT statement may specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, usernames must already exist.
Action:Specify only existing usernames in the SELECT, GRANT, or REVOKE statement or ask the database administrator to define the new username.
ORA-01436 CONNECT BY loop in user data

Cause:The condition specified in a CONNECT BY clause caused a loop in the query, where the next record to be selected is a descendent of itself. When this happens, there can be no end to the query.
Action:Check the CONNECT BY clause and remove the circular reference.
ORA-01437 cannot have join with CONNECT BY

Cause:A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause is used in a SELECT statement for a tree-structured query, only one table may be referenced in the query.
Action:Remove either the CONNECT BY clause or the join operation from the SQL statement.
ORA-01438 value larger than specified precision allows for this column

Cause:When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.
Action:Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.
ORA-01439 column to be modified must be empty to change datatype

Cause:An ALTER TABLE MODIFY statement attempted to change the datatype of a column containing data. A column whose datatype is to be altered must contain only NULL values.
Action:To alter the datatype, first set all values in the column to NULL.
ORA-01440 column to be modified must be empty to decrease precision or scale

Cause:An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. In order to decrease either of these values, the column must contain only NULL values. An attempt to increase the scale without also increasing the precision will also cause this message.
Action:Set all values in the column to NULL before decreasing the numeric precision or scale. If attempting to increase the scale, increase the precision in accordance with the scale or set all values in the column to NULL first.
ORA-01441 column to be modified must be empty to decrease column length

Cause:An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values.
Action:Set all values in column to NULL before decreasing the maximum size.
ORA-01442 column to be modified to NOT NULL is already NOT NULL

Cause:An ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NOT NULL to NOT NULL.
Action:No action required.
ORA-01443 internal inconsistency; illegal datatype in resultant view column

Cause:An internal error occurred in referencing a view.
Action:Contact customer support.
ORA-01444 internal inconsistency; internal datatype maps to invalid external type

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-01445 cannot select ROWID from a join view without a key-preserved table

Cause:A SELECT statement attempted to select ROWIDs from a view derived from a join operation. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.
Action:Remove ROWID from the view selection clause, then re-execute the statement.
ORA-01446 cannot select ROWID from view with DISTINCT, GROUP BY, etc.

Cause:A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.
Action:Remove ROWID from the view selection clause, then re-execute the statement.
ORA-01447 ALTER TABLE does not operate on clustered columns

Cause:An ALTER TABLE MODIFY statement specified a column used to cluster the table. Clustered columns may not be altered.
Action:To alter the column, first recreate the table in non-clustered form. The column's size can be increased at the same time.
ORA-01448 index must be dropped before changing to desired type

Cause:An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the datatype LONG may not be indexed, so the index must be dropped before the modification.
Action:Drop all indexes referencing the column before changing its datatype to LONG.
ORA-01449 column contains NULL values; cannot alter to NOT NULL

Cause:An ALTER TABLE MODIFY statement attempted to change the definition of a column containing NULL values to NOT NULL. The column may not currently contain any NULL values if it is to be altered to NOT NULL.
Action:Set all NULL values in the column to values other than NULL before ALTERING the column to NOT NULL.
ORA-01450 maximum key length exceeded

Cause:The combined length of all the columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum index length varies by operating system. The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have their defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1.
Action:Select columns to be indexed so the total index length does not exceed the maximum index length for the operating system. See also your operating system-specific Oracle documentation.
ORA-01451 column to be modified to NULL cannot be modified to NULL

Cause:The column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint, or an ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NULL to NULL.
Action:If a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint.
ORA-01452 cannot CREATE UNIQUE INDEX; duplicate keys found

Cause:A CREATE UNIQUE INDEX statement specified one or more columns that currently contain duplicate values. All values in the indexed columns must be unique by row to create a UNIQUE INDEX.
Action:If the entries need not be unique, remove the keyword UNIQUE from the CREATE INDEX statement, then re-execute the statement. If the entries must be unique, as in a primary key, then remove duplicate values before creating the UNIQUE index.
ORA-01453 SET TRANSACTION must be first statement of transaction

Cause:A transaction was not processed properly because the SET TRANSACTION statement was not the first statement.
Action:Commit or roll back the current transaction before using the statement SET TRANSACTION.
ORA-01454 cannot convert column into numeric datatype

Cause:A non-numeric value could not be converted into a number value.
Action:Check the value to make sure it contains only numbers, a sign, a decimal point, and the character "E" or "e", then retry the operation.
ORA-01455 converting column overflows integer datatype

Cause:The converted form of the specified expression was too large for the specified datatype.
Action:Define a larger datatype or correct the data.
ORA-01456 may not perform insert/delete/update operation inside a READ ONLY transaction

Cause:A non-DDL INSERT/DELETE/UPDATE or SELECT FOR UPDATE operation was attempted.
Action:Commit or roll back the current transaction, then retry the operation.
ORA-01457 converting column overflows decimal datatype

Cause:The converted form of the specified expression was too large for the specified type. The problem also occurs in COBOL programs when using COMP-3 in the picture clause, which is acceptable to the Pro*COBOL Precompiler and to COBOL but results in this error.
Action:Define a larger datatype or correct the data.
ORA-01458 invalid length inside variable character string

Cause:An attempt was made to bind or define a variable character string with a buffer length less than the two-byte minimum requirement.
Action:Increase the buffer size or use a different type.
ORA-01459 invalid length for variable character string

Cause:The buffer length was less than the minimum required (two bytes) or greater than its length at bind time minus two bytes.
Action:None. Buffer length is set correctly by Oracle at fetch time.
ORA-01460 unimplemented or unreasonable conversion requested

Cause:The requested format conversion is not supported.
Action:Remove the requested conversion from the SQL statement. Check the syntax for the TO_CHAR, TO_DATE, and TO_NUMBER functions to see which conversions are supported.
ORA-01461 can bind a LONG value only for insert into a LONG column

Cause:An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed.
Action:Do not try to insert LONG datatypes into other types of columns.
ORA-01462 cannot insert string literals longer than 2000 characters

Cause:The longest literal supported by Oracle consists of 2000 characters.
Action:Reduce the number of characters in the literal to 2000 characters or fewer or use the VARCHAR2 or LONG datatype to insert strings exceeding 2000 characters.
ORA-01463 cannot modify column datatype with current constraints

Cause:An attempt was made to modify the datatype of a column that has referential constraints or that has check constraints that only allow changing the datatype from CHAR to VARCHAR or vice versa.
Action:Remove the constraint(s) or do not perform the offending operation.
ORA-01464 circular grant (granting to grant ancestor) of table or view

Cause:The user in the TO clause of the GRANT statement has already been GRANTed privileges on this table.
Action:Do not GRANT privileges on a table to the user who originally GRANTed privileges on that table. The statement in error is probably unnecessary.
ORA-01465 invalid hex number

Cause:In an UPDATE statement following a SELECT FOR UPDATE, part of the ROWID contains invalid characters. ROWID must be expressed in the proper and expected format for ROWID and within quotes.
Action:Enter the ROWID just as it was returned in the SELECT FOR UPDATE.
ORA-01466 unable to read data -- object definition has changed

Cause:This is a time-based read consistency error for a database object, such as a table or index. Either of the following may have happened:

Action:If the cause is
ORA-01467 sort key too long

Cause:A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement.
Action:Reduce the number of columns or group functions involved in the operation.
ORA-01468 a predicate may reference only one outer-joined table

Cause:A predicate in the WHERE clause has two columns from different tables with "(+)".
Action:Change the WHERE clause so that each predicate has a maximum of one outer-join table.
ORA-01469 PRIOR can only be followed by a column name

Cause:An invalid column name was specified after the PRIOR keyword.
Action:Check syntax, spelling, use a valid column name, and try again.
ORA-01471 cannot create a synonym with the same name as object

Cause:An attempt was made to create a private synonym with the same name as the object to which it refers. This error typically occurs when a user attempts to create a private synonym with the same name as one of their objects.
Action:Choose a different synonym name or create the synonym under a different username.
ORA-01472 cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.

Cause:CONNECT BY cannot be used on a view where there is not a correspondence between output rows and rows of the underlying table.
Action:Remove the DISTINCT or GROUP BY from the view or move the CONNECT BY clause into the view.
ORA-01473 cannot have subqueries in CONNECT BY clause

Cause:Subqueries cannot be used in a CONNECT BY clause.
Action:Remove the subquery or move it to the WHERE clause.
ORA-01474 cannot have START WITH or PRIOR without CONNECT BY

Cause:START WITH and PRIOR are meaningful only in connection with CONNECT BY.
Action:Check the syntax for the SQL statement and add a CONNECT BY clause, if necessary.
ORA-01475 must reparse cursor to change bind variable datatype

Cause:After executing a statement, an attempt was made to rebind a bind variable with a datatype different from that of the original bind.
Action:Reparse the cursor before rebinding with a different datatype.
ORA-01476 divisor is equal to zero

Cause:An expression attempted to divide by zero.
Action:Correct the expression, then retry the operation.
ORA-01477 user data area descriptor is too large

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-01478 array bind may not include any LONG columns

Cause:An attempt was made to use array bind on a column whose maximum size is greater than 2000 bytes. This is not permitted.
Action:Do not use array bind for a LONG column. Use an ordinary bind instead.
ORA-01479 last character in the buffer is not Null

Cause:A bind variable of type 97 does not contain NULL at the last position.
Action:Make the last character a NULL.
ORA-01480 trailing null missing from STR bind value

Cause:A bind variable specified as type SQLT_STR is not terminated with an ASCII NULL (0) character.
Action:Check maximum lengths and contents of string bind variables.
ORA-01481 invalid number format model

Cause:An invalid format parameter was used with the TO_CHAR or TO_NUMBER function.
Action:Correct the syntax, then retry the operation.
ORA-01482 unsupported character set

Cause:The second or third parameter to the CONVERT function is not a supported character set.
Action:Use one of the supported character sets.
ORA-01483 invalid length for DATE or NUMBER bind variable

Cause:A bind variable of type DATE or NUMBER is too long.
Action:Check your Oracle7 operating system-specific documentation for the maximum allowable length.
ORA-01484 arrays can only be bound to PL/SQL statements

Cause:You tried to bind an array to a non-PL/SQL statement.
Action:Rewrite the offending code being careful to bind arrays only to PL/SQL statements.
ORA-01485 compile bind length different from execute bind length

Cause:You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length, given in the bind call. The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.
Action:Ensure that the buffer size is sufficiently large to contain the array plus two bytes for the buffer length.
ORA-01486 size of array element is too large

Cause:An attempt was made to bind a data value that was either too large for the datatype, for example, NUMBER, or was greater than 2000 bytes, for example, VARCHAR or LONG.
Action:Find a way to convert or truncate the data value so that its length is acceptable.
ORA-01487 packed decimal number too large for supplied buffer

Cause:A conversion request cannot be performed because the buffer is too small to hold the result.
Action:Increase the size of the buffer.
ORA-01488 invalid nibble or byte in the input data

Cause:A conversion request cannot be performed because a digit was invalid.
Action:Fix the number and retry.
ORA-01489 result of string concatenation is too long

Cause:The result of a string concatenation was larger than the maximum length of a string (2000 characters).
Action:Reduce the size of one or both of the strings to be concatenated. Make certain the total length of the concatenation result is less than 2000 characters.

01490-01499: Miscellaneous, ANALYZE, SQL Parsing, Execution

ORA-01490 invalid ANALYZE command

Cause:The syntax of the ANALYZE command was incorrect.
Action:Check the syntax and enter the command using the correct syntax.
ORA-01491 CASCADE option not valid

Cause:The CASCADE option should be used only for tables or clusters.
Action:Do not use the CASCADE option in this manner. Check the syntax of the statement and then retry.
ORA-01492 LIST option not valid

Cause:The LIST option can be used only for tables or clusters.
Action:Do not use the LIST option in this manner. Check the syntax of the statement and then retry.
ORA-01493 invalid SAMPLE size specified

Cause:The specified SAMPLE size is out of range
Action:Specify a value within the proper range.
ORA-01494 invalid SIZE specified

Cause:The specified histogram SIZE value was out of range.
Action:Specify a value within the proper range.

ORA-01495 specified chain row table not found

Cause:The specified table does not exist, or the user does not have the proper privileges to access it.
Action:Specify an existing table or obtain the privileges to access the desired table.
ORA-01496 specified chain row table form incorrect

Cause:The specified table does not have the proper field definitions.
Action:Check the spelling of the table name and specify the correct table to use.
ORA-01497 illegal option for ANALYZE CLUSTER

Cause:The FOR COLUMNS <column list> clause cannot be used with ANALYZE CLUSTER.
Action:Retry with a legal syntax.

ORA-01498 block Check Failure - see trace file

Cause:An error occurred while checking a block with the ANALYZE command.
Action:Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to recreate the object. See also your operating system-specific Oracle documentation.
ORA-01499 table/Index Cross Reference Failure - see trace file

Cause:An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.
Action:Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to recreate the object. See also your operating system-specific Oracle documentation.

01500-01699: Oracle Commands

ORA-01500 failure in getting date/time

Cause:In executing a CREATE DATABASE or ALTER TABLESPACE statement, there was a failure in getting the date and time.
Action:Contact customer support.
ORA-01501 CREATE DATABASE failed

Cause:An error occurred while executing the CREATE DATABASE statement.
Action:Refer to the diagnostic information in the accompanying message stack.
ORA-01502 index str.name is in direct load state

Cause:The specified index was marked invalid by a direct load.
Action:Drop the specified index.
ORA-01503 CREATE CONTROLFILE failed

Cause:An error occurred during CREATE CONTROLFILE.
Action:See accompanying messages.
ORA-01504 database name name does not match parameter DB_NAME str

Cause:The name in a CREATE DATABASE or START UP command does not match the name given in the initialization parameter DB_NAME.
Action:Determine which name is correct, then resubmit the command after correcting the name in the appropriate place.
ORA-01505 error in adding log files

Cause:In executing a CREATE DATABASE or ALTER DATABASE statement, an error occurred when adding new redo log files. The user issuing the command must CONNECT INTERNAL. The database must be mounted but closed in order to add redo log files.
Action:Check the accompanying message stack for detailed information and ensure that the session is connected as INTERNAL with the database mounted but closed.
ORA-01506 missing or illegal database name

Cause:No database name was specified in the ALTER DATABASE statement, nor was the initialization parameter DB_NAME specified.
Action:The database name must be given either in the ALTER DATABASE statement or as the value for the initialization parameter DB_NAME. Note that the SQL*DBA command START UP issues an ALTER DATABASE statement using the database name, if any, specified as part of START UP.
ORA-01507 database not mounted

Cause:An ALTER DATABASE statement specified the name of a database to alter, but no database is currently mounted.
Action:If issuing an ALTER DATABASE command via the SQL*DBA START UP command, specify the MOUNT option. If directly issuing an ALTER DATABASE DISMOUNT command, do nothing. Otherwise, reissue the ALTER DATABASE command specifying the MOUNT option.
ORA-01508 cannot create database; error in file name at line num

Cause:A CREATE DATABASE statement was unable to process the named file because an error occurred at the given line number.
Action:Check the offending line in the specified file, correct the error, then re-execute the CREATE DATABASE statement. If the error is in an Oracle-supplied file, contact customer support.
ORA-01509 specified name name does not match actual name

Cause:The database name specified in an ALTER DATABASE statement does not match the name of the currently mounted database.
Action:Correct the database name spelling or DISMOUNT the mounted database.
ORA-01510 error in deleting log files

Cause:In executing an ALTER DATABASE statement, an error occurred while dropping redo log files.
Action:Check the accompanying message stack for detailed information.
ORA-01511 error in renaming log/datafiles

Cause:In executing an ALTER DATABASE statement, an error occurred while renaming log or datafiles.
Action:Check the accompanying message stack for detailed information.
ORA-01512 error renaming log file name - new file name not found

Cause:An attempt to change a redo log file's name in the control file failed because no file was found with the new name.
Action:Check that the redo log file has been properly renamed by the operating system and retry.
ORA-01513 invalid current time returned by operating system

Cause:The operating system returned a time that was not between the years 1988 and 2121.
Action:Correct the time kept by the operating system.
ORA-01514 error in log specification; no such log

Cause:A redo log filename or list of member names did not correspond to an existing redo log file.
Action:Specify the name of an existing redo log file, check the spelling and capitalization of the names, and then re-execute the statement.
ORA-01515 error dropping log group num: no such log

Cause:An attempt was made to drop a redo log file that does not exist.
Action:Specify the name of an existing redo log file, then issue the statement again.
ORA-01516 nonexistent log/datafile name

Cause:An ALTER DATABASE statement is attempting to rename a log file or a datafile that is not known to the database control file.
Action:Specify the name of an existing redo log file, then re-execute the statement.
ORA-01517 log member: str

Cause:This message indicates the filename involved with other messages.
Action:See the accompanying messages and take appropriate action.
ORA-01518 CREATE DATABASE must specify more than one log file

Cause:Only one redo log file was specified in the CREATE DATABASE statement.
Action:Specify at least two redo log files, then re-execute the statement.
ORA-01519 error while processing file name near line num

Cause:A CREATE DATABASE statement encountered a problem while processing the named file, probably because of a system installation error.
Action:Try the system installation procedure again or contact customer support. See also your operating system-specific Oracle documentation.
ORA-01520 number of datafiles to add num exceeds limit of num

Cause:A CREATE TABLESPACE statement specifies more files than are permitted for this database.
Action:Use fewer files. To exceed the limit, recreate the database with a larger value of MAXDATAFILES.
ORA-01521 error in adding datafiles

Cause:During a CREATE or ALTER TABLESPACE, an error was detected while adding datafiles.
Action:Check the accompanying message stack for detailed information.
ORA-01522 file name to be renamed does not exist

Cause:During an ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.
Action:Specify the correct filename, then re-execute the statement.
ORA-01523 cannot rename datafile to name - file already part of database

Cause:During an ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.
Action:Rename the file to a name not already in use as part of the database.
ORA-01524 cannot create datafile as name - file already part of database

Cause:During an ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.
Action:Use a name that is not already in use in the database.
ORA-01525 error in renaming datafiles

Cause:An error occurred when renaming files as part of ALTER TABLESPACE.
Action:Check the accompanying message stack for detailed information. All files were renamed except those mentioned in the message stack.
ORA-01526 error in opening file name

Cause:A CREATE DATABASE was not able to open the file identified in the message. This is probably due to a system installation error.
Action:Try the system installation procedure again or contact customer support. See also your operating system-specific Oracle documentation.
ORA-01527 error while reading file

Cause:A CREATE DATABASE statement was not able to read the specified file, probably because of a system installation error.
Action:Try the system installation procedure again or contact customer support. See also your operating system-specific Oracle documentation.
ORA-01528 EOF while processing SQL statement

Cause:A CREATE DATABASE statement unexpectedly encountered an end-of-file marker while reading the specified file, probably because of a system installation error.
Action:Try the system installation procedure again or contact customer support. See also your operating system-specific Oracle documentation.
ORA-01529 error closing file name

Cause:A CREATE DATABASE was not able to close the file identified in the message.
Action:Try the system installation procedure again or contact customer support. See also your operating system-specific Oracle documentation.
ORA-01530 a database already mounted by the instance

Cause:During an ALTER DATABASE MOUNT, an attempt was made to mount a database by an instance for which there is already a mounted database.
Action:To mount the database, shut down the instance, then start up the instance and try the operation again.
ORA-01531 a database already open by the instance

Cause:During an ALTER DATABASE, an attempt was made to open a database by an instance for which there was already an open database.
Action:To open a new database, shut down the instance, then start up the instance and try the operation again.
ORA-01532 cannot create database; instance being started elsewhere

Cause:During a CREATE DATABASE, another user appears to be simultaneously starting the instance.
Action:Retry the operation. If the error recurs, contact customer support.
ORA-01533 cannot rename file name; file does not belong to tablespace

Cause:During an ALTER TABLESPACE RENAME, a file to be renamed was not found in the named tablespace.
Action:Check syntax and spelling and correctly specify the filename and tablespace name.
ORA-01534 rollback segment name doesn't exist

Cause:During an ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name was not found.
Action:Correct syntax and spelling and correctly specify the rollback segment name or specify a different rollback segment.
ORA-01535 rollback segment name already exists

Cause:During a CREATE ROLLBACK SEGMENT, the specified rollback segment was found to exist already.
Action:Correct syntax and spelling and correctly specify the rollback segment name or specify a different rollback segment.
ORA-01536 space quota exceeded for tablespace "name"

Cause:The space quota in the tablespace is already used up and the operation attempted the creation of a new extent in the tablespace.
Action:Either

ORA-01537 cannot add datafile name - file already part of database

Cause:During a CREATE or ALTER TABLESPACE, a file being added is already part of the database.
Action:Correct spelling of the datafile name or use a different file.
ORA-01538 failed to acquire any rollback segment

Cause:An instance failed to acquire the SYSTEM rollback segment, or an instance failed to acquire one rollback segment in addition to the SYSTEM rollback segment during start up in parallel mode.
Action:Check that the SYSTEM rollback segment is available. Before starting an instance in parallel mode, either create one more public rollback segment or specify an available private rollback segment in the initialization parameter ROLLBACK_SEGMENTS.
ORA-01539 tablespace "name" is not online

Cause:An attempt was made to bring a tablespace off line normally, but it is not online.
Action:Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files off line. Also, the database must be in ARCHIVELOG mode.
ORA-01540 tablespace "name" is not offline

Cause:A tablespace could not be brought online or made read-only because it is not offline.
Action:Check the status of the tablespace, then retry the operation. You can also use the options IMMEDIATE or TEMPORARY to force all files offline. If your intention is to make the file read-only, bring the tablespace online first.
ORA-01541 system tablespace cannot be brought offline; shut down if necessary

Cause:An attempt was made to bring tablespace SYSTEM offline.
Action:Do not attempt to take the tablespace SYSTEM offline because it must always be online. Shut down if necessary to do a recovery.
ORA-01542 tablespace "name" is offline, cannot allocate space in it

Cause:An attempt was made to allocate space in an offline tablespace.
Action:Bring the tablespace online or create the object in another tablespace.
ORA-01543 tablespace "name" already exists

Cause:An attempt was made to create a tablespace that already exists.

Action:Use a different name for the new tablespace.
ORA-01544 cannot drop system rollback segment

Cause:An attempt was made to drop the rollback segment SYSTEM.
Action:No action required.
ORA-01545 rollback segment "name" specified not available

Cause:Either:

Action:Either:
ORA-01546 tablespace contains active rollback segment "name"

Cause:You tried to bring offline or make read-only a tablespace that contains active rollback segments.
Action:Shut down the instances that use the active rollback segments in the tablespace. Then bring it offline or make it read-only.
ORA-01548 active rollback segment "name" found, terminate dropping tablespace

Cause:An attempt was made to drop a tablespace that contains active rollback segments.
Action:Shut down instances that use the active rollback segments in the tablespace and then drop the tablespace.
ORA-01549 tablespace not empty, use INCLUDING CONTENTS option

Cause:An attempt was made to drop a non-empty tablespace.
Action:To drop all the objects in the tablespace, use the INCLUDING CONTENTS option with DROP TABLESPACE.
ORA-01550 cannot drop system tablespace

Cause:An attempt was made to drop the tablespace SYSTEM.
Action:No action required.
ORA-01551 extended rollback segment, pinned blocks released

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-01552 cannot use system rollback segment for non-system tablespace "name"

Cause:An attempt was made to use the SYSTEM rollback segment for operations involving a non-system tablespace.
Action:Create one or more rollback segments and then use ALTER ROLLBACK SEGMENT 'name' online. It may be necessary to modify the initialization parameter ROLLBACK_SEGMENTS to acquire one of the new private rollback segments. Before creating a rollback segment outside the SYSTEM tablespace, it is necessary to first create and activate a non-system rollback segment in the SYSTEM tablespace.
ORA-01553 MAXEXTENTS must be no smaller than the num extents currently allocated

Cause:The number of extents allocated is greater than the MAXEXTENTS specified.
Action:Specify a larger MAXEXTENTS value.
ORA-01554 out of transaction slots in transaction tables

Cause:There were too many concurrent transactions.
Action:Shut down Oracle, modify initialization parameters TRANSACTIONS and ROLLBACK_SEGMENTS, then restart Oracle. The TRANSACTIONS parameter must be high enough to handle any possible rollbacks.
ORA-01555 snapshot too old (rollback segment too small)

Cause:One of the following:

Action:For the above causes:
ORA-01556 MINEXTENTS for rollback segment must be greater than 1

Cause:A MINEXTENTS of less than two was specified for rollback segment.
Action:Specify a larger MINEXTENTS.
ORA-01557 rollback segment extents must be at least num blocks

Cause:An extent of less than num blocks was specified for the rollback segment.
Action:Specify extents of at least num blocks, then retry the operation.

ORA-01558 out of transaction ID's in rollback segment num

Cause:All the available transaction IDs have been used.
Action:Shut down the instance, restart it using another rollback segment, then drop the rollback segment that has no more transaction IDs.
ORA-01559 MAXEXTENTS for rollback segment must be greater than 1

Cause:An invalid value for MAXEXTENTS was specified; the value must be greater than 1.
Action:Specify a MAXEXTENTS value of at least 2 and try again.
ORA-01560 global hash table size mismatch for GC_name (num != num)

Cause:This message is only relevant for systems running the Parallel Server and occurs at instance start up. The value of the GC_name initialization parameter does not match that of an instance already mounted.
Action:Ensure correct initialization parameter files are being used. If necessary, modify the GC_name parameter in the offending initialization files, then shut down and restart those instances with corrected initialization parameter files.
ORA-01561 failed to remove all objects in the tablespace specified

Cause:A user failed to remove all objects when dropping a tablespace.
Action:Repeat DROP TABLESPACE until all objects have been dropped.
ORA-01562 failed to extend rollback segment ID = num

Cause:A failure occurred while trying to extend the rollback segment. The problem is usually lack of space in the database to extend the rollback segment.
Action:This is usually followed by another message stating the cause of the failure. Shut down and take appropriate action for the error that caused the failure. If no other messages follow this message, the cause is probably lack of space in the database.
ORA-01563 rollback segment is PUBLIC, need to use the keyword PUBLIC

Cause:The keyword PUBLIC was not used to identify a public rollback segment.
Action:Use the keyword PUBLIC when identifying a public rollback segment.
ORA-01564 rollback segment is not PUBLIC

Cause:The identified rollback segment is not public.
Action:Do not use the keyword PUBLIC when identifying a private rollback segment.
ORA-01565 error in identifying file name

Cause:An error occurred while trying to identify a file.
Action:Check the accompanying message stack for detailed information.
ORA-01566 file specified more than once in DROP LOGFILE

Cause:For an ALTER DATABASE, the list of files for the DROP LOGFILE option contains at least one duplicate.
Action:Remove the duplicate file specification, then re-execute the statement.
ORA-01567 dropping log name would leave less than two log files in thread num

Cause:Dropping all the files specified would leave fewer than the required two redo log files. It may be possible to clear the log rather than drop it.
Action:Either drop fewer logs or disable the thread before deleting the logs.
ORA-01568 cannot set space quota on PUBLIC

Cause:An attempt was made to set a space quota for PUBLIC on a tablespace.
Action:To grant system-wide or tablespace-wide space privileges to all users, use the statement

GRANT UNLIMITED TABLESPACE [ON tablespace] TO PUBLIC;

ORA-01569 datafile too small for system dictionary tables

Cause:The datafile specified during creation of the database is too small to hold the system dictionary tables.
Action:Re-create the database specifying a larger file or more files.
ORA-01570 MINEXTENTS must be no larger than the num extents currently allocated

Cause:The number of extents already allocated is smaller than the MINEXTENTS specified in the command.
Action:Enter the command again specifying the number of extents given in the message as the value for MINEXTENTS.
ORA-01571 redo version num incompatible with Oracle Version num

Cause:This software version cannot read the current redo logs. Either crash recovery is required or there are offline database files that need media recovery. If a filename is listed then it needs media recovery.
Action:Shut down and start up using the compatible software. Do any required media recovery and open the database. Shut down and then start up using current software. If the file is going to be dropped, then take it offline with the DROP option to skip this check.
ORA-01572 global hash table size num for rollback segments is too small for rollback segment ID num

Cause:An operation requested a resource that was unavailable. On a Parallel Server system, the maximum number of systemwide rollback segments is specified by the GC_ROLLBACK_SEGMENTS parameter. When this maximum is reached, no more requests are processed.
Action:Use fewer rollback segments or increase the initialization parameter GC_ROLLBACK_SEGMENTS to a number greater than rollback segment ID num in every initialization parameter file of the Parallel Server. This change will not take effect until Oracle is shut down and restarted.
ORA-01573 shutting down instance, no further change allowed

Cause:A process attempted to make changes while the database was being shut down.
Action:No action required.
ORA-01574 maximum number of concurrent transactions exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of concurrent transactions is specified by the TRANSACTIONS initialization parameter. When this maximum is reached, no more requests are processed.
Action:Try the request again later or increase the TRANSACTIONS parameter in the initialization parameter file. This change will not take effect until Oracle is shut down and restarted.
ORA-01575 time-out waiting for space management resource

Cause:The system timed out before it could acquire the necessary resources to do space management.
Action:Wait a few minutes, then retry the operation.
ORA-01576 instance locking protocol version num incompatible with Oracle Version num

Cause:The version of Oracle is incompatible with the given locking protocol version.
Action:Upgrade the version of Oracle used to start up instances so that they use a compatible locking protocol.
ORA-01577 cannot add log file name - file already part of database

Cause:While executing a CREATE or ALTER DATABASE statement, a file being added was found to already exist on the database.
Action:Check syntax and spelling, specify a valid filename, and try again.
ORA-01578 Oracle data block corrupted (file # num, block # num)

Cause:The given data block was corrupted, probably due to program errors.
Action:Try to restore the segment containing the given data block. This may involve dropping the segment and recreating it. If there is a trace file, report the messages recorded in it to customer support.
ORA-01579 write error occurred during recovery

Cause:A write error occurred during media recovery.
Action:Check the trace file for the type of the write error, then take appropriate action.
ORA-01580 error creating control backup file name

Cause:An operating system error occurred while attempting to create the referenced control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01581 attempt to use rollback segment name new extent name which is being allocated

Cause:Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent, which has not been completely allocated.
Action:The rollback segment extending itself will be rollbacked by the system. No more extension will be possible until the next extent is freed up by the rolling back or committing of other transactions.
ORA-01582 unable to open control file for backup

Cause:An operating system error occurred while attempting to open a control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01583 unable to get block size of control file to be backed up

Cause:An operating system error occurred while attempting to get the block size of a control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01584 unable to get file size of control file to be backed up

Cause:An operating system error occurred while attempting to get the file size of a control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01585 error identifying backup file name

Cause:An operating system error occurred when attempting to identify the referenced control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01586 unable to open destination file name for backup

Cause:An operating system error occurred while attempting to open a control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01587 error during control file backup file copy

Cause:An operating system error occurred while attempting to copy a control file for backup.
Action:Check the accompanying message stack for detailed information, then take appropriate action.
ORA-01588 must use RESETLOGS option for database open

Cause:An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup.
Action:Retry the operation making sure to specify the RESETLOGS option.
ORA-01589 must use RESETLOGS or NORESETLOGS option for database open

Cause:Either cancel-based or time-based recovery has been performed. After these types of recovery, it is necessary to specify either the RESETLOGS or NORESETLOGS option to open the database.
Action:Specify the appropriate option.
ORA-01590 number of segment free list num exceeds maximum of num

Cause:The value of the storage clause FREELIST GROUPS is greater than the maximum allowed for the block size.
Action:Specify a number for FREELIST GROUPS less than or equal to the maximum when creating the table or index. The block size specified in the initialization parameter DB_BLOCK_SIZE cannot be changed after the database is created.
ORA-01591 lock held by in-doubt distributed transaction num

Cause:An attempt was made to access a resource locked by a dead two-phase commit transaction that is in prepared state.
Action:Match the transaction number in the message with the GLOBAL_TRAN_ID column of the DBA_2PC_PENDING table to determine the database link and the state of the transaction. Attempt to repair network connections to the coordinator and commit point, if necessary. If timely repair is not possible, contact the database administrator at the commit point, if known, to resolve the pending transaction.
ORA-01592 error converting Version 6 rollback segment "num" to Oracle7 format

Cause:Oracle encountered an error while converting a Version 6 rollback segment into the format used by Oracle7.
Action:Investigate the accompanying internal error message. The Version 6 database may not have shut down cleanly. It may be necessary to reload the Version 6 database from backup and shut it down, ensuring it shuts down cleanly.
ORA-01593 rollback segment optimal size num blocks is smaller than the computed initial size num blocks

Cause:The specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.
Action:Specify a larger OPTIMAL size.
ORA-01594 attempt to wrap into rollback segment name extent num which is being freed

Cause:Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents or too many extents to free.
Action:Increase the optimal size of the rollback segment. The rollback segment shrinking will be rolled back by the system.
ORA-01595 error freeing extent num of rollback segment name

Cause:An error occurred while freeing inactive rollback segment extents.
Action:Check the trace file and check for prior messages.
ORA-01596 cannot specify system in name parameter

Cause:The system rollback segment is specified in the INIT.ORA parameter referred to in the error message.
Action:Change the INIT.ORA parameter.
ORA-01597 cannot alter system rollback segment online or offline

Cause:An attempt was made to online or offline the SYSTEM rollback segment.
Action:No action required.
ORA-01598 rollback segment "name" is not online

Cause:The rollback segment was taken offline either manually or by SMON.
Action:Check the status of the rollback segment in DBA_ROLLBACK_SEGS.
ORA-01599 failed to acquire rollback segment "name", cache space is full (currently has num entries)

Cause:The amount of allocated space is not enough.
Action:Take the rollback segment offline.
ORA-01600 at most one str in clause str of GC_FILES_TO_LOCKS

Cause:The initialization parameter GC_FILES_TO_LOCKS was not specified properly.
Action:Refer to the proper specifications of the GC_FILES_TO_LOCKS parameter and specify it correctly in the initialization parameter file. If other instances are currently accessing the database, use the value that they are using.
ORA-01601 illegal bucket size in clause str of GC_FILES_TO_LOCKS

Cause:The number of locks specified in a clause of the initialization parameter GC_FILES_TO_LOCKS is not a positive integer.
Action:Refer to the proper specifications of the GC_FILES_TO_LOCKS parameter and specify it correctly in the initialization parameter file. If other instances are currently accessing the database, use the value that they are using.
ORA-01602 more locks in GC_FILES_TO_LOCKS than reserved in GC_DB_LOCKS

Cause:The total number of PCM locks specified to all database files in the initialization parameter GC_FILES_TO_LOCKS is greater than the number specified in GC_DB_BLOCKS.
Action:Correct the value of either the GC_FILES_TO_LOCKS parameter or the GC_DB_LOCKS parameter before starting the instance. If other instances are currently accessing the database, use the values that they are using.
ORA-01603 illegal grouping in clause str of GC_FILES_TO_LOCKS

Cause:The initialization parameter GC_FILES_TO_LOCKS is specified incorrectly; if a clause specifies more than one range of file numbers, each range must be separated with commas.
Action:Correct the value of the GC_FILES_TO_LOCKS parameter before starting the instance. If other instances are currently accessing the database, use the value they are using. Use the following syntax:

ORA-01604 illegal file number range in clause str of GC_FILES_TO_LOCKS

Cause:The range of file numbers specified in a clause of the initialization parameter GC_FILES_TO_LOCKS is invalid. The first file number must be smaller than the second file number, and a hyphen must separate the numbers. All numbers in the range must be valid file numbers.
Action:Correct the value of the GC_FILES_TO_LOCKS parameter before starting the instance. If other instances are currently accessing the database, use the value that they are using.
ORA-01605 missing file numbers in clause str of GC_FILES_TO_LOCKS

Cause:The initialization parameter GC_FILES_TO_LOCKS is specified incorrectly. Each clause should have one or more file numbers or ranges of file numbers, as listen in V$DBFILE, separated by commas. Use the following syntax: 

GC_FILES_TO_LOCKS = "{filenum[-filenum]
	[,filenum[-filenum]]...=  num_of_locks[EACH]}[:]..."

Action:Correct the value of the GC_FILES_TO_LOCKS parameter before starting the instance. If other instances are currently accessing the database, use the value that they are using.
ORA-01606 GC_FILES_TO_LOCKS not identical to that of another mounted instance

Cause:The initialization parameter GC_FILES_TO_LOCKS is not the same as another instance mounted in parallel mode. This parameter must be the same as that for all shared instances.
Action:Modify the parameter to be compatible with the other instances, then shut down and restart the instance.
ORA-01607 GC_LCK_PROCS num is not the same as other instances num

Cause:The initialization parameter GC_LCK_PROCS is not the same in other instances that have the database open.
Action:Modify the parameter to be compatible with the other instances, then shut down and restart the instance.
ORA-01608 cannot bring rollback segment "name" online, its status is status

Cause:The rollback segment may have been brought online previously by the database administrator or could have been left online after a process crashed. The above status can be one of the following: INVALID, IN USE, AVAILABLE, OFFLINE, NEEDS RECOVERY.
Action:Check the status of the rollback segment in the view DBA_ROLLBACK_SEGS. Take the segment offline, if necessary.
ORA-01609 log name is the current log for thread num - cannot drop members

Cause:A member of the current redo log for the given thread cannot be dropped.
Action:If the thread is opened, request a log switch by the instance that is using the thread. If the thread is not open, disable the thread manually, archive the log or clear it.
ORA-01610 recovery using the BACKUP CONTROLFILE option must be done

Cause:Either an earlier database recovery session specified BACKUP CONTROLFILE or the control file was recreated with the RESETLOGS option. Only BACKUP CONTROLFILE recovery is allowed, and it must be followed by resetting the online redo log files when the database is next opened.
Action:Perform recovery using the BACKUP CONTROLFILE option.
ORA-01611 thread number num is invalid - must be between 1 and num

Cause:A thread number in a command is greater than the number of threads supported by the control file.
Action:Use a thread number that is valid.
ORA-01612 thread num is already enabled

Cause:An attempt was made to enable a thread that is already enabled.
Action:No action is required or enable another thread, if desired.
ORA-01613 thread num only has num logs - at least 2 logs required to enable

Cause:The thread cannot be enabled because it has less than two online redo log files associated with it.
Action:Add logs to the thread or pick another thread to enable.
ORA-01614 thread num is busy - cannot enable

Cause:The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread.
Action:Wait and try again or find another thread to enable.
ORA-01615 thread num is mounted - cannot disable

Cause:Some instance, possibly this one, has allocated the thread for use. The thread may not be disabled while in use.
Action:To disable this thread, cleanly shut down the instance using it.
ORA-01616 thread num is open - cannot disable

Cause:The thread is not closed. The last instance to use the thread crashed and left the thread open. A thread cannot be disabled until it is closed. The thread is still needed for crash or instance recovery.
Action:If the database is open, instance recovery should close the thread soon. Wait a few minutes until instance recovery frees the thread. Otherwise, open the database. Crash recovery will close the thread.
ORA-01617 cannot mount: num is not a valid thread number

Cause:The initialization parameter THREAD is not between 1 and the maximum number of threads allowed when the database was created.
Action:Shut down the instance, change the initialization parameter to a valid value, then restart the instance.
ORA-01618 thread num is not enabled - cannot mount

Cause:The initialization parameter THREAD requests a thread that is not enabled. A thread must be enabled before it can be mounted.
Action:Shut down the instance, change the initialization parameter to an enabled thread number, then restart the instance. If the database is open in another instance, then the thread may be enabled.
ORA-01619 thread num is mounted by another instance

Cause:The initialization parameter THREAD requests a thread that has been mounted by another instance. Only one instance may use each thread.
Action:Shut down the instance, change the initialization parameter to an unused thread, then restart the instance.
ORA-01620 no public threads are available for mounting

Cause:The initialization parameter THREAD is zero, its default value. There are no available threads that have been publicly enabled.
Action:Shut down the instance, change the initialization parameter to a thread that is privately enabled and not mounted, then restart the instance. If the database is open in another instance, then a thread may be publicly enabled.
ORA-01621 cannot rename member of current log if database is open

Cause:This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done.
Action:Wait until the log is not current or mount the database exclusively.
ORA-01622 thread number must be specified - default not specific

Cause:The thread was not specified when adding a log, and the currently mounted thread was chosen by default. Because the current thread was not specified explicitly, the user cannot know to which thread the log will be added.
Action:Explicitly specify the thread number either in the initialization parameter THREAD or in the ADD LOGFILE command.
ORA-01623 log num is current log for thread num - cannot drop

Cause:A thread's current log cannot be dropped, even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again.
Action:If the database is not open, disable the thread. If the database is open and an instance has the thread open, then switch logs in the instance with the thread open.
ORA-01624 log name needed for crash recovery of thread num - cannot drop

Cause:A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log.
Action:If the database is not open, then open it. Crash recovery will advance the checkpoint. If the database is open, force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do an incomplete recovery until this log is cancelled.
ORA-01625 rollback segment name does not belong to this instance

Cause:An attempt was made to take a rollback segment offline that does not belong to this instance.
Action:Take only those rollback segments offline that belong to the current instance. To take the rollback segment offline, connect to the instance containing it.
ORA-01626 rollback segment number num cannot handle more transactions

Cause:There are too many transactions in this segment.
Action:Choose a different rollback segment or reduce the number of concurrent transactions.
ORA-01627 rollback segment number num is not online

Cause:This rollback may have been taken offline by the database administrator or cleaned up by SMON.
Action:Check the status of the rollback segment in DBA_ROLLBACK_SEGMENTS to make sure the rollback segment is actually online.
ORA-01628 max # of extents num reached for rollback segment num

Cause:An attempt was made to extend a rollback segment that already has reached its maximum size or space could not be allocated in the data dictionary to contain the definition of the object.
Action:If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters or find the data dictionary table lacking space and alter the storage parameters, as described in the Oracle7 Server Administrator's Guide.
ORA-01629 max # of extents num reached saving undo for tablespace name

Cause:The maximum amount of space allowed for saving undo entries has been reached for an offline tablespace.
Action:Check the storage parameters for the SYSTEM tablespace. The tablespace named needs to be brought online so that the undo information can be applied.
ORA-01630 max # of extents num reached in temp segment in tablespace name

Cause:The maximum amount of space allowed for saving undo entries has been reached for a temporary segment in the named tablespace, or space could not be allocated in the data dictionary to contain the definition of the object.
Action:If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters or find the data dictionary table lacking space and alter the storage parameters as described in the Oracle7 Server Administrator's Guide.
ORA-01631 max # of extents num reached in table name

Cause:The maximum amount of space allowed for saving undo entries has been reached for the named table.
Action:If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters.
ORA-01632 max # of extents num reached in index name

Cause:The maximum amount of space allowed for saving undo entries has been reached for the named index.
Action:If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters.
ORA-01633 Parallel Server option needed for this operation

Cause:The system is not configured to use the Parallel Server option, so the feature is not available.
Action:Contact Oracle Corporation to obtain the Parallel Server option.
ORA-01634 rollback segment number str is about to go offline

Cause:The rollback segment specified was marked to go offline by the DBA.
Action:Bring the rollback segment online before continuing, or choose another rollback segment. If using SET TRANSACTION, use ROLLBACK SEGMENT 'name'.
ORA-01635 rollback segment #num specified not available

Cause:Either

Action:For the above, either:
ORA-01636 rollback segment "name" is already online

Cause:A rollback segment can only be used by one instance and an instance is trying to bring a rollback segment online that is already in use.
Action:Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See the Oracle7 Server Administrator's Guide for more information about using rollback segments in parallel mode.
ORA-01637 rollback segment "name" is being used by another instance #name

Cause:A rollback segment can only be used by one instance, and an instance is trying to access a rollback segment online that is already in use.
Action:Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See Oracle7 Parallel Server Concepts & Administration for more information about using rollback segments in parallel mode.
ORA-01638 parameter name does not allow Oracle Version num to mount parallel

Cause:The recovery compatible initialization parameter is set too low to allow this software version to do a parallel mount.
Action:Either use an earlier software release or advance the RECOVERY_COMPATIBLE parameter. If this happens when no RECOVERY_COMPATIBLE parameter has been specified, then set it to the current software release.
ORA-01639 database cannot be mounted parallel with no lock processes

Cause:The value of GC_LCK_PROCS is 0, and the database is being mounted in parallel mode.
Action:Change GC_LCK_PROCS to a value between 1 and 10 or leave it undefined to use the default.
ORA-01640 cannot make tablespace read-only with active transactions

Cause:An attempt to make a tablespace read-only encountered active transactions in the database. All transactions must be committed or rolled back to ensure consistency. This includes any transactions that are in doubt.
Action:Put the database in restricted mode to prevent any new transactions from being started and commit and/or rollback all active transactions, resolving all in-doubt transactions.
ORA-01641 tablespace name is not online - cannot add datafile

Cause:An attempt was made to add a datafile to a tablespace that was set to read only or offline.
Action:Make the tablespace online, read-write, and add the datafile.

ORA-01642 begin backup not needed for read-only tablespace name

Cause:An attempt was made to use the BEGIN BACKUP or END BACKUP statement for a tablespace that has been made read-only.
Action:Start the backup without using the BEGIN BACKUP or END BACKUP statement. Read-only files cannot be modified and therefore will be consistent.
ORA-01643 system tablespace cannot be made read-only

Cause:An attempt was made to make the system tablespace read-only. The system tablespace must be read-write for database operations.
Action:Do not attempt this operation.
ORA-01644 tablespace name is already read-only

Cause:An attempt was made to make read-only a tablespace that is already read-only.
Action:This operation is unnecessary.
ORA-01645 previous attempt to make read-write is half complete

Cause:A failure while making a tablespace read-write occurred leaving the tablespace read-only, however the checkpoint was advanced. The tablespace will not be usable after a RESETLOGS if it's files are offline.
Action:Attempt to make the tablespace read-write again.
ORA-01646 tablespace name is not read-only - cannot make read-write

Cause:An attempt was made to make read-write a tablespace that is already read-write.
Action:This operation is unnecessary.
ORA-01647 tablespace "name" is read-only, cannot allocate space in it

Cause:An attempt was made to allocate space in a read-only tablespace, which is not possible.
Action:Create the object in a read-write tablespace.
ORA-01648 log name is the current log of disabled thread name

Cause:An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Because a log switch cannot be done until the thread is enabled, the log cannot be cleared or archived.
Action:Complete the thread enable by issuing the enable command again.
ORA-01649 operation not allowed with a backup control file

Cause:An attempt was made to perform a command that does not make sense when the control file is a restored backup.
Action:Wait until after the database has been opened and try again.
ORA-01650 unable to extend rollback segment name by num in tablespace name

Cause:Failed to allocate extent for the rollback segment in tablespace.
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.
ORA-01651 unable to extend save undo segment by num in tablespace name

Cause:Failed to allocate extent for saving undo entries for the specified offline tablespace.
Action:Check the storage parameters for the system tablespace. The tablespace must be brought back online so the undo can be applied.
ORA-01652 unable to extend temp segment by num in tablespace name

Cause:Failed to allocate extent for temp segment in tablespace.
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace or create the object in another tablespace.
ORA-01653 unable to extend table name.name by num in tablespace name

Cause:Failed to allocate extent for table segment in tablespace.
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.
ORA-01654 unable to extend index name.name by num for tablespace name

Cause:Failed to allocate extent for index segment in tablespace.
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.
ORA-01655 unable to extend cluster name.name by num for tablespace name

Cause:Failed to allocate extent for cluster segment in tablespace.
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.
ORA-01656 max num extents num reached in cluster name.name

Cause:A cluster tried to extend past the value specified for MAXEXTENTS.
Action:If MAXEXTENTS is less than the system maximum, specify a higher value. Otherwise, you must recreate with larger INITIAL, NEXT, or PCTINCREASE parameters.
ORA-01658 unable to create INITIAL extent for segment in tablespace name

Cause:Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.
Action:Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL.
ORA-01659 unable to allocate MINEXTENTS beyond size in tablespace name

Cause:Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.
Action:Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT, or PCTINCREASE.
ORA-01660 tablespace name is already permanent

Cause:An attempt was made to make a tablespace permanent that was already permanent.
Action:Leave tablespace permanent.

ORA-01661 tablespace name is already temporary

Cause:An attempt was made to make a tablespace temporary that was already temporary.
Action:Leave tablespace permanent.

ORA-01662 tablespace name is non-empty and cannot be made temporary

Cause:An attempt was made to convert a non-empty tablespace to a temporary tablespace.
Action:Drop all the objects in the tablespace.

ORA-01663 the contents of tablespace name is constantly changing

Cause:The contents of the tablespace always changed between PERMANENT and TEMPORARY.
Action:Decide what the tablespace contents should be and stay with it.

ORA-01664 transaction which has expanded the Sort Segment has aborted

Cause:Internal Error.
Action:Contact Oracle Support.
ORA-01665 controlfile is not a standby controlfile

Cause:An attempt was made to mount, recover, or activate a standby database without a standby controlfile.
Action:Create a standby controlfile before attempting to use the database as a standby database.

ORA-01666 controlfile is for a standby database

Cause:An attempt was made to mount, recover, or open a standby database without the appropriate command option to designate a standby database.
Action:Use the standby option or appropriate commands, or mount with the primary controlfile.

ORA-01667 redo log is incompatible with standby database

Cause:Recovery of a standby database encountered redo in primary database that did not support the standby database option.
Action:Change the compatible initialization parameter for the primary database to be 7.3.0 or greater, open the primary database, and rebuild the standby database.

ORA-01668 standby database requires DROP option for offline of datafile

Cause:An attempt was made to take a datafile offline in a standby database without specifying the DROP option. Files that were offline in a standby database were not recovered, and were likely to be unusable if the standby was activated. Note that specifying DROP does not prevent bringing the file online later.
Action:Specify the DROP option or leave the file online.

ORA-01669 standby database control file not consistent

Cause:An attempt was made to activate a standby database with a control file that was not recovered to the same point as the datafiles. Most likely the control file was just copied in primary database and was not used for recovery.
Action:Recover the standby database until all the files are consistent.

ORA-01670 new datafile name needed for standby database recovery

Cause:Standby database recovery noticed that a file was added to the primary database but was not available on the standby.
Action:Either copy the file in primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover.

ORA-01671 controlfile is a backup, cannot make a standby controlfile

Cause:The currently mounted control file was a backup control file and attempted to create a control file for a standby database.
Action:Complete any needed recovery and open the database with the RESETLOGS option.

ORA-01672 controlfile may be missing files or have extra ones

Cause:An attempt was made to create a standby control file, but the controlfile was either recently created by using CREATE CONTROLFILE or an incomplete recovery was done. Therefore, the datafiles in the controlfile and the ones in the data dictionary may not match.
Action:Open the database and retry the operation.

ORA-01673 datafile name has not been identified

Cause:The datafile was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header was needed for standby database recovery, a standby controlfile cannot be created.
Action:Find the file and bring it online. If desired, it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error.

ORA-01674 datafile name is an old incarnation rather than current file

Cause:Recovery encountered redo that indicates this file was dropped in database, and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file.
Action:Rebuild the controlfile using CREATE CONTROLFILE, and give the correct file.

ORA-01675 attempting a secondary mount of a standby database

Cause:An attempt was made to mount a standby database as a secondary.
Action:The standby database is already mounted. Do a dismount first before attempting to mount the standby database.

ORA-01676 standby file name convert of num exceeds maximum length of num

Cause:When the given file name was converted to the name used for the standby database, the converted name was bigger than the maximum allowed file name.
Action:Change the initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name.

ORA-01677 standby file name convert parameters differ from other instance

Cause:The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT initialization parameters were not the same as in other instances that already have the database mounted.
Action:Change initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances.

ORA-01678 parameter name must be two strings, a pattern and a replacement

Cause:The specialized initialization parameter did not have 2 strings for its value. The first string is a pattern to be found in file names. The second string is used to replace the pattern when found in file names.
Action:Specify two strings for the parameter, or omit the parameter.
ORA-01679 database must be mounted EXCLUSIVE and not open to activate

Cause:An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open.
Action:Mount the database EXCLUSIVE and retry the ACTIVATE command.

ORA-01680 gc_db_locks cannot be zero if gc_files_to_locks is used

Cause:Setting gc_db_locks to zero makes data blocks in all files releasable, so specifying gc_files_to_locks is redundant.
Action:Remove either gc_db_locks or gc_files_to_locks.

01700-01799: SQL Parsing

ORA-01700 duplicate username in list

Cause:A username was listed twice in a GRANT or REVOKE statement. Usernames must be unique and may only be specified once in a GRANT or REVOKE statement.
Action:Remove the duplicate username and retry the statement.
ORA-01701 a cluster is not appropriate here

Cause:The name of a cluster was specified in a statement in which clusters are not permitted.
Action:Enter a valid CLUSTER statement or change the cluster name to the name of a valid object for the statement, such as table, view, index, or synonym.
ORA-01702 a view is not appropriate here

Cause:The name of a view was specified in a statement in which views are not permitted.
Action:Enter the name of a valid object for the statement, such as table, cluster, synonym, or index.
ORA-01703 missing SYNONYM keyword

Cause:The keyword SYNONYM is required in this context.
Action:Check the statement syntax and insert the keyword SYNONYM.
ORA-01704 string literal too long

Cause:A quoted string specified as a constant was too long.
Action:Quoted strings may not contain more than 2000 characters.
ORA-01705 an outer join cannot be specified on a correlation column

Cause:A correlation column, that is, a column in a subquery from a table referenced in the outer query's FROM clause, was followed by an outer-join indicator (+). This is not allowed.
Action:Revise the query. Refer to the syntax for subqueries. The outer-join indicator may follow only columns in the same query block in which their table is included in the FROM clause.
ORA-01706 user function result value was too large

Cause:The user-written SQL function has generated a result that is larger than the maximum defined in the function table.
Action:Change the maximum in the function table or correct the user-written function.
ORA-01707 missing LIST keyword

Cause:The keyword LIST is required in this context, for example, when using the ARCHIVE LOG statement to display the set of redo log files.
Action:Check the statement syntax, insert the keyword LIST where required, and retry the statement.
ORA-01708 ACCESS or SESSION expected

Cause:An AUDIT or NOAUDIT statement contained the keyword BY followed by something other than ACCESS or SESSION.
Action:Check the statement syntax and make sure to follow the keyword BY with ACCESS or SESSION.
ORA-01709 program does not exist

Cause:This feature is not currently implemented.
Action:No user action is required.
ORA-01710 missing OF keyword

Cause:The keyword OF was not specified in a SELECT FOR UPDATE statement.
Action:Check and correct the statement syntax. To specify SELECT FOR UPDATE, add the following clause to the end of the SELECT statement: 

FOR UPDATE OF column-list

ORA-01711 duplicate privilege listed

Cause:A privilege was listed twice in a GRANT or REVOKE statement. A privilege may be specified only once in these statements.
Action:Remove the duplicate privilege from the list and retry the statement.
ORA-01712 cannot grant a privilege grantor does not have

Cause:The grantor could not grant a privilege to another user because the grantor does not have the privilege. A grantor can grant only privileges that the grantor has or is authorized to grant.
Action:Either

ORA-01713 GRANT OPTION does not exist for that privilege

Cause:A GRANT statement specified a privilege that the granting user has but is not authorized to grant to other users. When the user was granted the privilege, the user was not given the GRANT OPTION needed to grant those privileges to others.
Action:Change the GRANT statement to specify only authorized privileges or ask the user who granted the privileges to grant the GRANT OPTION also.
ORA-01714 error in execution of user function

Cause:The user-written SQL function indicated that an error occurred during its execution. The meaning of the message is function-dependent.
Action:Ensure proper usage of the function or correct the function.
ORA-01715 UNIQUE may not be used with a cluster index

Cause:An attempt was made to create a cluster index with the UNIQUE attribute. This is not permitted.
Action:Remove the keyword UNIQUE from the CREATE INDEX statement and retry the statement.
ORA-01716 NOSORT may not be used with a cluster index

Cause:An attempt was made to create a cluster index using the NOSORT option. This is not permitted.
Action:Check the statement syntax, remove the keyword NOSORT from the CREATE INDEX statement, and retry the statement.
ORA-01717 seccta invalid access mode token passed

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-01718 BY ACCESS | SESSION clause not allowed for NOAUDIT

Cause:A BY ACCESS or BY SESSION clause was used in a NOAUDIT statement. BY ACCESS and BY SESSION are valid clauses in AUDIT statements, but are not permitted in NOAUDIT statements.
Action:Remove the BY ACCESS or BY SESSION clause from the NOAUDIT statement.
ORA-01719 outer join operator (+) not allowed in operand of OR or IN

Cause:An outer join appears in an OR clause.
Action:If A and B are predicates, to get the effect of (A(+) OR B), try using the following: 

(SELECT WHERE (A+ AND NOT B)) UNION ALL (SELECT WHERE (B));

ORA-01720 grant option does not exist for str

Cause:A grant was being performed on a view, and the grant option was not present for an underlying object.
Action:Obtain the grant option on all underlying objects of the view.
ORA-01721 USERENV (COMMITSCN) invoked more than once in a transaction

Cause:The USERENV function can be used only once in a transaction.
Action:Rewrite the transaction to use USERENV (COMMITSCN) only once.
ORA-01722 invalid number

Cause:The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.
Action:Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.
ORA-01723 zero-length columns are not allowed

Cause:During CREATE TABLE, a zero-length column was specified, for example, CHAR(0).
Action:Correct the column declaration so that the length is at least 1 and try the operation again.
ORA-01724 floating point precision is out of range 1 to 126

Cause:Floating point precision is too small or large.
Action:Correct and retry.
ORA-01725 USERENV (COMMITSCN) not allowed here

Cause:The function USERENV (COMMITSCN) is allowed only as a top-level expression in the VALUES clause of an INSERT statement and on the right side of an assignment in an UPDATE statement.
Action:Correct the use of this function.
ORA-01726 a table is not appropriate here

Cause:A table name was used in a statement in which tables are not permitted.
Action:Enter a valid table statement or use the current statement on the appropriate object.
ORA-01727 numeric precision specifier is out of range 1 to 38

Cause:The precision specified for a number column in a CREATE/ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If no precision is specified, a default precision of 22 digits is used.
Action:Specify numeric precision between 1 and 38 and retry the statement.
ORA-01728 numeric scale specifier is out of range -84 to 127

Cause:The scale specified for a numeric field in a CREATE/ALTER TABLE or CREATE CLUSTER statement is not in the valid range. It should be between -84 and 127.
Action:Specify a numeric scale between -84 and 127. If a number is not specified, the default scale of the column is 0 decimal places.
ORA-01729 database link name expected

Cause:A database link name does not follow the at-sign (@) in a reference to a table in a remote database.
Action:Correct the reference and retry the operation. The correct syntax for denoting a table in a remote database follows: 

username.table_name@ database_name

ORA-01730 invalid number of column names specified

Cause:The number of column names specified in a CREATE VIEW statement did not correspond to the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause.
Action:Specify one view column name for each column in the SELECT clause.
ORA-01731 circular view definition encountered

Cause:Through a series of CREATE and DROP VIEW statements, a view was defined that refers to itself. For example, VIEW1 might include a column from VIEW2 that is defined as a column in VIEW1. View definitions may be seen by querying the data dictionary.
Action:Check the view definitions, remove any circular references, and retry the statements.
ORA-01732 data manipulation operation not legal on this view

Cause:An attempt was made to use an UPDATE, INSERT, or DELETE statement on a view that contains expressions or functions or was derived from more than one table. If a join operation was used to create the view or the view contains virtual columns derived from functions or expressions, then the view may only be queried.
Action:UPDATE, INSERT, or DELETE rows in the base tables instead and restrict the operations on the view to queries.
ORA-01733 virtual column not allowed here

Cause:An attempt was made to use an INSERT, UPDATE, or DELETE statement on an expression in a view.
Action:INSERT, UPDATE, or DELETE data in the base tables, instead of the view.
ORA-01734 illegal parameters - EXTENT MIN higher than EXTENT MAX

Cause:The value of the lower parameter EXTENT MIN was higher than the value of the upper parameter EXTENT MAX.
Action:Select a value for EXTENT MIN that is smaller than EXTENT MAX.
ORA-01735 invalid ALTER TABLE option

Cause:An invalid option was specified in an ALTER TABLE statement.
Action:Check the statement syntax, specify a valid option, and retry the statement.
ORA-01736 [NOT] SUCCESSFUL expected

Cause:An AUDIT or NOAUDIT statement contained WHENEVER followed by something other than SUCCESSFUL or NOT SUCCESSFUL.
Action:Correct the WHENEVER clause and retry the statement.
ORA-01737 valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE

Cause:The lock mode entered was not recognized.
Action:Enter one of the following: SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, SHARE ROW EXCLUSIVE, or SHARE UPDATE.
ORA-01738 missing IN keyword

Cause:In a LOCK TABLE statement, the keyword IN was missing.
Action:Place the keyword IN and lock mode directly after the table name in the LOCK TABLE statement and retry the statement.
ORA-01739 missing MODE keyword

Cause:In a LOCK TABLE statement, the keyword MODE was missing. The keyword MODE must directly follow the specified lock mode.
Action:Check the statement syntax, insert the keyword MODE where required, and retry the statement.
ORA-01740 missing double quote in identifier

Cause:An initial double quote (") was found without a closing quote. If an identifier contains a blank or special characters other than $, #, or _, it must be enclosed in double quotes.
Action:Add a closing double quote (") to the end of the identifier.
ORA-01741 illegal zero-length identifier

Cause:An attempt was made to use two double quotes ("") as an identifier. An identifier must be at least one character long.
Action:Insert at least one character between the double quotes in the identifier. If a blank identifier is required, specify a blank space between the double quotes (" ").
ORA-01742 comment not terminated properly

Cause:The indicated comment or hint beginning with a /* token is not terminated with a closing */ token.
Action:Check that the comment or hint is terminated properly.
ORA-01743 internal inconsistency; illegal user function index

Cause:This is not currently implemented.
Action:No user action is required.
ORA-01744 inappropriate INTO

Cause:The INTO clause may not be used in a subquery.
Action:Check the syntax, place the INTO clause in the top-level query, and retry the statement.
ORA-01745 invalid host/bind variable name

Cause:A colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word.
Action:Change the variable name and retry the operation.
ORA-01746 indicator variable not permitted here

Cause:An indicator variable is not permitted in this context.
Action:Remove the indicator variable and retry the operation.
ORA-01747 invalid user.table.column, table.column, or columns specification

Cause:A column name was specified improperly in the current SQL statement.
Action:Check the statement's syntax, especially references to column names, and retry the statement.
ORA-01748 only simple column names allowed here

Cause:This SQL statement does not allow a qualified column name, such as username.table.column or table.column.
Action:Remove the qualifications from the column and retry the operation.
ORA-01749 may not GRANT/REVOKE privileges to/from self

Cause:Grantor is not allowed to grant or revoke object or system privileges to self.
Action:Issue the GRANT or REVOKE of system privileges from another database administrator account.
ORA-01750 UPDATE/REFERENCES may only be revoked from the whole table, not by column

Cause:Although it is possible to GRANT update privileges on a column-by-column basis, it is only possible to REVOKE them for an entire table.
Action:Do not identify specific columns. To revoke update privileges for certain columns, use REVOKE for the entire table and GRANT the user privileges for specific columns.
ORA-01751 invalid dump undo option

Cause:An invalid option was specified in the ALTER SYSTEM DUMP UNDO command.
Action:Check the syntax for spelling errors or invalid option names and reenter the command.

ORA-01752 cannot delete from view without exactly one key-preserved table

Cause:The deleted table either had no key-preserved tables, had more than one key-preserved table, or the key-preserved table was an unmerged view or a table from a read-only view.
Action:Redefine the view or delete it from the underlying base tables.

ORA-01753 column definition incompatible with clustered column definition

Cause:When adding a table to a cluster, the definition of the column in the table was inconsistent with the definition of the column in the cluster.
Action:The table cannot be added to the cluster until all cluster column definitions are consistent.
ORA-01754 a table may contain only one column of type LONG

Cause:Only one column per table may be defined with datatype LONG.
Action:Remove the LONG datatype from all but one column and retry the operation.
ORA-01755 must specify an extent number or block number

Cause:An extent number or block number was not specified.
Action:Specify the proper extent number or block number.

ORA-01756 quoted string not properly terminated

Cause:A quoted string must be terminated with a single quote mark (').
Action:Insert the closing quote and retry the statement.
ORA-01757 must specify an object number

Cause:An object number was not specified.
Action:Specify the proper object number.

ORA-01758 table must be empty to add mandatory NOT NULL column

Cause:It is not possible to define a new column as NOT NULL if rows already exist in the table being modified.
Action:Retry the statement without the NOT NULL specification.
ORA-01759 user function is incorrectly defined

Cause:A user function has been improperly defined.
Action:Contact customer support.
ORA-01760 illegal argument for function

Cause:The argument or arguments specified for the function are not valid in this context.
Action:Check the definition of the function and correct the arguments.
ORA-01761 DML operation does not map to a unique table in the join

Cause:The primary table is the base table against which the update, insert or delete operation is ultimately performed. If the operation is a delete, either there is no primary table in the join or there is more than one primary table. If the operation is an update or an insert, the specified columns map to more than one base table.
Action:Modify the join specification so that the situations described above do not occur.
ORA-01762 vopdrv: view query block not in FROM

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-01763 update or delete involves outer joined table

Cause:If the operation is a delete, the table being deleted from is outer-joined to some other table. If the operation is an update, either the table being updated is outer-joined to some other table, or a table that is reachable from the primary table is being outer-joined to a table not reachable from the primary table.
Action:Modify the join specification so that the situations described above do not occur.
ORA-01764 new update value of join is not guaranteed to be unique

Cause:A row of a join query table is being updated using a row of a table that is not guaranteed to have only one value for the row being updated.
Action:Modify the join specification, so that the situation described above does not occur.
ORA-01765 specifying table's owner name is not allowed

Cause:A table or view name was specified with a period (.) or identified with an invalid prefix.
Action:Check that the object is identified correctly and if necessary remove the period from the name.
ORA-01766 dictionary table not allowed in this context

Cause:The name of a data dictionary object was used outside the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object is to SELECT from it.
Action:Restrict operations on data dictionary objects to queries.
ORA-01767 UPDATE ... SET expression must be a subquery

Cause:An attempt was made to use a single expression without a subquery to update a list of columns.
Action:Check the syntax for using subqueries to update data and add the necessary subquery.
ORA-01768 number string too long

Cause:A number entered exceeds the limit of 255 characters, including digits, sign, decimal point, and exponent.
Action:Shorten the number string, perhaps by expressing it in scientific notation, for example, 1.85E9 instead of 1,850,000,000.
ORA-01769 duplicate CLUSTER option specifications

Cause:During a CREATE of a clustered table, an attempt was made to specify more than one CLUSTER option.
Action:Remove the extra CLUSTER option and retry the statement.
ORA-01770 CLUSTER option not allowed in CREATE CLUSTER command

Cause:An attempt was made to use the CLUSTER option within a CREATE CLUSTER statement.
Action:Remove the CLUSTER clause and try again.
ORA-01771 illegal option for a clustered table

Cause:CLUSTER option conflicts with MAXTRANS option.
Action:Choose one option and retry the statement.
ORA-01772 must specify a value for LEVEL

Cause:A value for LEVEL was not specified.
Action:Specify a proper value for LEVEL and reissue the command.

ORA-01773 may not specify column datatypes in this CREATE TABLE

Cause:Column datatypes were specified in a SELECT statement used to create and load a table directly.
Action:Remove column datatypes. The datatypes of the SELECT list expressions are automatically used as the column datatypes.
ORA-01774 dump undo option specified more than once

Cause:The same option was specified more than once in the ALTER SYSTEM DUMP UNDO command.
Action:Check the syntax, remove the redundant specification of the option, and reissue the command.

ORA-01775 looping chain of synonyms

Cause:Through a series of CREATE synonym statements, a synonym was defined that referred to itself. For example, the following definitions are circular: 

CREATE SYNONYM s1 for s2
CREATE SYNONYM s2 for s3
CREATE SYNONYM s3 for s1

Action:Change one synonym definition so that it applies to a base table or view and retry the operation.
ORA-01776 cannot modify more than one base table through a join view

Cause:Columns belonging to more than one underlying table were either inserted into or updated.
Action:Phrase the statement as two or more separate statements.

ORA-01777 WITH GRANT OPTION not allowed in this system

Cause:This version of Oracle does not support the WITH GRANT OPTION.
Action:Remove the WITH GRANT option.
ORA-01778 maximum subquery nesting level exceeded

Cause:An attempt was made to use more than 255 levels of nested subqueries.
Action:Merge some of the subqueries into their containing queries, until there are less than 255 levels of nesting.
ORA-01779 cannot modify a column which maps to a non-key-preserved table

Cause:An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.
Action:Modify the underlying base tables directly.

ORA-01780 string literal required

Cause:In a COMMENT statement, the comment following the keyword IS must be a quoted string literal.
Action:Check that the comment is a string literal.
ORA-01781 UNRECOVERABLE cannot be specified without AS SELECT

Cause:UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.
Action:Do not specify UNRECOVERABLE.
ORA-01782 UNRECOVERABLE cannot be specified for a cluster or clustered table

Cause:A CREATE CLUSTER or clustered CREATE TABLE statement specified UNRECOVERABLE.
Action:Do not specify UNRECOVERABLE.
ORA-01783 only one RECOVERABLE or UNRECOVERABLE clause may be specified

Cause:RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX statement.
Action:Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.
ORA-01784 RECOVERABLE cannot be specified with database media recovery disabled

Cause:A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.
Action:Do not specify RECOVERABLE, or restart the database with media recovery enabled.
ORA-01785 ORDER BY item must be the number of a SELECT-list expression

Cause:Either an ORDER BY item for a set expression is not a column number, or the ORDER BY item is not the number of a SELECT list column.
Action:The ORDER BY item must be a number between 1 and the number of columns in the SELECT list. Check the column number and retry the statement.
ORA-01786 FOR UPDATE of this query expression is not allowed

Cause:An attempt was made to use a FOR UPDATE clause on the result of a set expression involving GROUP BY, DISTINCT, UNION, INTERSECT, or MINUS.
Action:Check the syntax, remove the FOR UPDATE clause, and retry the statement.
ORA-01787 only one clause allowed per query block

Cause:An attempt was made to use more than one WHERE, GROUP BY, CONNECT BY, or HAVING clause in the query.
Action:Combine the duplicate clauses into a single clause and retry the statement.
ORA-01788 CONNECT BY clause required in this query block

Cause:A START WITH clause was specified without a CONNECT BY clause.
Action:Check the syntax, specify a CONNECT BY clause, and retry the statement.
ORA-01789 query block has incorrect number of result columns

Cause:All of the queries participating in a set expression do not contain the same number of SELECT list columns.
Action:Check that all the queries in the set expression have the same number of SELECT list columns.
ORA-01790 expression must have same datatype as corresponding expression

Cause:A SELECT list item corresponds to a SELECT list item with a different datatype in another query of the same set expression.
Action:Check that all corresponding SELECT list items have the same datatypes. Use the TO_NUMBER, TO_CHAR, and TO_DATE functions to do explicit data conversions.
ORA-01791 not a SELECTed expression

Cause:There is an incorrect ORDER BY item. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands are constants or SELECT list expressions.
Action:Remove the inappropriate ORDER BY item from the SELECT list and retry the statement.
ORA-01792 maximum number of columns in a table or view is 254

Cause:While creating a table or view, more than 254 columns were specified.
Action:Remove some columns from the table or view definition. If all the information is required, split the columns into two tables or views and join the columns when querying.
ORA-01793 maximum number of index columns is 16

Cause:While creating an index, more than 16 columns were specified.
Action:Remove some columns from the index definition. If all the columns indexed are required, split them into two indexes.

ORA-01794 maximum number of cluster columns is 16

Cause:More than 16 columns were specified in the cluster key.
Action:Remove some of the columns from the cluster key definition. Consider concatenating multiple character strings into a single column.
ORA-01795 maximum number of expressions in a list is 254

Cause:More than 254 columns or expressions were specified in a list.
Action:Remove some of the expressions from the list.
ORA-01796 this operator cannot be used with lists

Cause:A relational operator is not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN.
Action:Rephrase the query so that it only compares lists for equivalence. For example, the following clause is invalid: 

WHERE (A,B) > ((C,D), (E,F))

ORA-01797 this operator must be followed by ANY or ALL

Cause:The keyword ANY or ALL was missing.
Action:Check the statement syntax and add ANY or ALL where appropriate.
ORA-01798 missing EXCEPTION keyword

Cause:The EXCEPTION keyword is missing from the ENABLE clause.
Action:Correct the syntax.
ORA-01799 a column may not be outer-joined to a subquery

Cause:An expression is not permitted to be joined to a subquery.
Action:Either remove the join or convert the subquery to a view.

01800-01899: The Date Function

ORA-01800 a literal in the date format was too large to process

Cause:A literal specified in a date format was too large. If a literal is entered as a date, it must be less than 220 characters long.
Action:Use only literals less than 220 characters long in the date format.
ORA-01801 date format is too long for internal buffer

Cause:The date format string was too long to process. This should occur only if several long literals are specified as part of a date.
Action:Remove long literals from the date format string.
ORA-01802 Julian date is out of range

Cause:An invalid Julian date was entered. Valid Julian dates run from 1 to 3,442,447.
Action:Enter a valid Julian date between 1 and 3,442,447.
ORA-01803 failure in getting date/time

Cause:This is an internal error message that is not likely to occur. It is usually caused by a failure in the system clock.
Action:Investigate the system clock and the process that requested the date or time. If necessary, contact customer support.
ORA-01810 format code appears twice

Cause:A format code was listed twice in a date specification. Each format code may be specified only once in the function TO_DATE.
Action:Remove the duplicate format code from the date specification, then retry the operation.
ORA-01811 Julian date precludes use of day of year

Cause:Both a Julian date and a day of the year were specified in the TO_DATE function. If a Julian date is specified, the day of the year (DDD) may not be specified, as it is contained in the Julian date.
Action:Remove the day of the year or the Julian date from the specification, then retry the operation.
ORA-01812 year may only be specified once

Cause:More than one year format code was listed in a date specification. Only one of the following year format codes may be specified in a date: YYYY, YYY, YY, Y.
Action:Remove all but one year format from the date specification.
ORA-01813 hour may only be specified once

Cause:More than one hour format code was listed in a date specification. Only one of the following hour format codes may be specified in a date: HH, HH12, HH24.
Action:Remove all but one hour format from the date specification.
ORA-01814 AM/PM conflicts with use of A.M./P.M.

Cause:Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified.
Action:Use one meridian indicator format, with or without periods, consistently.
ORA-01815 BC/AD conflicts with use of B.C./A.D.

Cause:Both types of BC/AD indicators were listed in a date specification. If one of the BC/AD indicator format masks, such as BC or B.C., is specified in the date, the other may not be specified.
Action:Use one BC/AD indicator format, with or without periods, consistently.
ORA-01816 month may only be specified once

Cause:More than one month format code was listed in a date specification. Only one of the following month format codes may be specified in a date: MM, MON, MONTH.
Action:Remove all but one month format from the date specification.
ORA-01817 day of week may only be specified once

Cause:More than one day-of-the-week format code was listed in a date specification. Only one of the following day-of-the-week format codes may be specified in a date: D, DY, DAY.
Action:Remove all but one day-of-the-week format from the date specification.
ORA-01818 HH24 precludes use of meridian indicator

Cause:A date specification contained both a 24-hour time format code and a meridian indicator code. If hours are specified using the 24-hour time format (HH24), a meridian indicator, AM or PM, may not be specified.
Action:Remove the meridian indicator format code, AM/PM or A.M./P.M., or the 24-hour time format code, HH24, from the date specification.
ORA-01819 signed year precludes use of BC/AD

Cause:A date specification contained both a signed year and a B.C./A.D. indicator. If the year is specified with a sign, such as SYYYY, then B.C. or A.D. is implicit in the date and must not be entered.
Action:Remove the B.C./A.D. indicator from the date specification.
ORA-01820 format code cannot appear in date input format

Cause:A date specification contained an invalid format code. Only the following may be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D.
Action:Remove the invalid format code from the date specification.
ORA-01821 date format not recognized

Cause:A date specification contained an invalid format code.
Action:Check that only valid date format codes are specified.
ORA-01830 date format picture ends before converting entire input string

Cause:A valid date format picture included extra data. The first part of the format picture was converted into a valid date, but the remaining data was not required.
Action:Check the specifications for date format pictures and correct the statement.
ORA-01831 year conflicts with Julian date

Cause:The wrong year was specified with a Julian day. If a year is specified with a Julian date, it must be the year in which the Julian date occurs.
Action:Remove the year value from the date specification or enter the correct year for the Julian date.
ORA-01832 day of year conflicts with Julian date

Cause:A Julian date was specified with the day of the year but the day did not correspond to the Julian date. If the day of the year is specified with a Julian date, it must be the same day as the Julian date.
Action:Remove the day of the year value from the date specification or enter the correct day for the Julian date.
ORA-01833 month conflicts with Julian date

Cause:The wrong month was specified with a Julian date. If a month is specified with a Julian date, it must be the month in which the Julian date occurs.
Action:Remove the month value from the date specification or enter the correct month for the Julian date.
ORA-01834 day of month conflicts with Julian date

Cause:A Julian date was specified with the day of the month, but the month day did not correspond to the Julian date. If the day of the month is specified with a Julian date, it must be the same day of the month as the Julian date.
Action:Remove the day of the month value from the date specification or enter the correct day of the month for the Julian date.
ORA-01835 day of week conflicts with Julian date

Cause:A Julian date was specified with the day of the week, but the weekday did not correspond to the Julian date. If the day of the week is specified with a Julian date, it must be the same day of the week as the Julian date.
Action:Remove the day of the week value from the date specification or enter the correct day of the week for the Julian date.
ORA-01836 hour conflicts with seconds in day

Cause:The wrong hour was specified with seconds in the day. If an hour is specified with seconds past midnight (SSSSS), it must be the hour in which the seconds value falls.
Action:Remove the hour value from the date specification or specify the correct hour for the seconds past midnight.
ORA-01837 minutes of hour conflicts with seconds in day

Cause:A date specification contained both minutes of the hour and seconds in the day but the values did not correspond. If both minutes in the hour (MI) and seconds past midnight (SSSSS) are specified, the minutes value must be the minute in which the seconds value will occur.
Action:Remove the minutes value from the date specification or enter the correct minute value for the specified seconds value.
ORA-01838 seconds of minute conflicts with seconds in day

Cause:A date specification contained both seconds of the minute and seconds in the day but the values did not correspond. If both types of seconds are specified, the seconds of the minute value (SS) must be the second in which the seconds past midnight value (SSSSS) will fall.
Action:Remove the seconds of the minute value from the date specification or enter a value that corresponds to the given seconds in the day.
ORA-01839 date not valid for month specified

Cause:The day of the month specified in the date is invalid for the given month. The day of the month (DD) must be between 1 and the number of days in the month.
Action:Enter a valid day of the month for the specified month.
ORA-01840 input value not long enough for date format

Cause:The data to be converted to date format was incomplete; the date format picture was longer than the input data.
Action:Either add more input or shorten the date picture format, then retry the operation.
ORA-01841 (full) year must be between -4713 and +9999

Cause:A date specified a year that is not in the valid date range. A valid date is any date between January 1, 4712 B.C. and December 31, 4712 A.D.
Action:Enter a valid date value between 4712 B.C. and 4712 A.D.
ORA-01842 quarter must be between 1 and 4

Cause:An invalid value was specified for the quarter of the year in a date. The quarter (Q) must be between 1 and 4.
Action:Enter a value for quarter between 1 and 4.
ORA-01843 not a valid month

Cause:A date specified an invalid month. Valid months are: January-December, for format code MONTH, and Jan-Dec, for format code MON.
Action:Enter a valid month value in the correct format.
ORA-01844 week of year must be between 1 and 52

Cause:An invalid value was specified for the week of the year in a date. Week of the year (WW) must be between 1 and 52.
Action:Enter a week of the year value between 1 and 52.
ORA-01845 week of month must be between 1 and 5

Cause:An invalid value was specified for the week of the month in a date. Week of the month (W) must be between 1 and 5.
Action:Enter a week of the month value between 1 and 5.
ORA-01846 not a valid day of the week

Cause:A date specified an invalid day of the week. Valid days are

Action:Enter a valid day of the week value in the correct format.
ORA-01847 day of month must be between 1 and last day of month

Cause:The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.
Action:Enter a valid day value for the specified month.
ORA-01848 day of year must be between 1 and 365 (366 for leap year)

Cause:An invalid day of the year was specified in a date. Day of the year (DDD) must be between 1 and 365 for a non-leap year or 1 and 366 for a leap year.
Action:Enter a day of the year value between 1 and 365 (or 366).
ORA-01849 hour must be between 1 and 12

Cause:An invalid hour was specified for a date using the 12-hour time format. If a 12-hour format code (HH or HH12) is used, the specified hour must be between 1 and 12.
Action:Enter an hour value between 1 and 12.
ORA-01850 hour must be between 0 and 23

Cause:An invalid hour was specified for a date using the 24-hour time format. If the 24-hour format code (HH24) is listed, the specified hour must be between 0 and 23.
Action:Enter an hour value between 0 and 23.
ORA-01851 minutes must be between 0 and 59

Cause:An invalid minute value was specified in a date. Minutes must be between 0 and 59.
Action:Enter a minute value between 0 and 59.
ORA-01852 seconds must be between 0 and 59

Cause:An invalid seconds value was specified in a date. Seconds must be between 0 and 59 if the seconds format code (SS) is used.
Action:Enter a seconds value between 0 and 59.
ORA-01853 seconds in day must be between 0 and 86399

Cause:An invalid value for seconds in the day was specified in a date. Seconds must be between 0 and 86399 if the seconds past midnight format code (SSSSS) is used.
Action:Specify a seconds value between 0 and 86399.
ORA-01854 Julian date must be between 1 and 5373484

Cause:An invalid Julian date was entered.
Action:Correct and retry.
ORA-01855 AM/A.M. or PM/P.M. required

Cause:A date specification contained a meridian indicator format code but a valid meridian indicator was not specified. If a meridian indicator code, A.M./P.M. or AM/PM, is included in a date format, the date must include a valid meridian indicator.
Action:Specify the meridian indicator in the correct format, A.M./AM or P.M./PM.
ORA-01856 BC/B.C. or AD/A.D. required

Cause:A date specification contained a BC/AD format code but a valid BC/AD indicator was not specified. If one of the BC/AD format codes, BC/AD or B.C./A.D., is specified in a date format, the date must include BC/B.C. or AD/A.D.
Action:Specify the BC/AD indicator in the date using the correct format.
ORA-01857 not a valid time zone

Cause:An incorrect time zone code was specified for the NEW_TIME function.
Action:Correct the invalid time zone code, then retry the operation.
ORA-01858 a non-numeric character found where a digit was expected

Cause:The input data to be converted using a date format model was incorrect. The format model expected a number but found a non-numeric character.
Action:Check the input data and the date format model to make sure the elements match in number and type, then retry the operation.
ORA-01859 a non-alphabetic character was found where a letter was expected

Cause:The input data to be converted using a date format model was incorrect. The format model expected a letter but found a non-alphabetic character.
Action:Check the input data and the date format model to make sure the elements match in number and type, then retry the operation.
ORA-01860 week of year must be between 1 and 53

Cause:A week number outside the range 1 to 53 was specified.
Action:Use only a value within the valid range for the week number.
ORA-01861 literal does not match format string

Cause:Literals in the input string must be the same length as the literals in the format string, except for the leading white space characters. If the "FX" modifier is specified, the literal must match exactly, including the leading white space.
Action:Correct the format string to match the string literal.
ORA-01862 wrong number of digits for this format item

Cause:The number of digits in this format item is not equal to the number required for the format. This error usually occurs when the "FX" modifier (format exact) has been specified.
Action:Resubmit the command using the required amount of numbers for the format mask.
ORA-01898 too many precision specifiers

Cause:While trying to truncate or round dates, extra data was found in the date format picture.
Action:Check the syntax of the date format picture and retry.
ORA-01899 bad precision specifier

Cause:An invalid precision code was specified in a date.
Action:Enter a valid precision code in the date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds.

01900-02039: SQL Parsing

ORA-01900 LOGFILE keyword expected

Cause:The keyword LOGFILE is required in this context.
Action:Check the syntax, insert the keyword LOGFILE where required, then re-execute the statement.
ORA-01901 ROLLBACK keyword expected

Cause:The keyword ROLLBACK is required in this context.
Action:Check the syntax, insert the keyword ROLLBACK where required, and re-execute the statement.
ORA-01902 SEGMENT keyword expected

Cause:The keyword SEGMENT is required in this context.
Action:Check the syntax, insert the keyword SEGMENT where required, and re-execute the statement.
ORA-01903 EVENTS keyword expected

Cause:The keyword EVENTS is required in this context.
Action:Check the syntax, insert the keyword EVENTS where required, and re-execute the statement.
ORA-01904 DATAFILE keyword expected

Cause:The keyword DATAFILE is required in this context.
Action:Check the syntax, insert the keyword DATAFILE where required, and re-execute the statement.
ORA-01905 STORAGE keyword expected

Cause:The keyword STORAGE is required in this context.
Action:Check the syntax, insert the keyword STORAGE where required, and re-execute the statement.
ORA-01906 BACKUP keyword expected

Cause:The keyword BACKUP is required in this context.
Action:Check the syntax, insert the keyword BACKUP where required, and re-execute the statement.
ORA-01907 TABLESPACE keyword expected

Cause:The keyword TABLESPACE is required in this context.
Action:Check the syntax, insert the keyword TABLESPACE where required, and re-execute the statement.
ORA-01908 EXISTS keyword expected

Cause:The keyword EXISTS is required in this context.
Action:Check the syntax, insert the keyword EXISTS where required, and re-execute the statement.
ORA-01909 REUSE keyword expected

Cause:The keyword REUSE is required in this context.
Action:Check the syntax, insert the keyword REUSE where required, and re-execute the statement.
ORA-01910 TABLES keyword expected

Cause:The keyword TABLES is required in this context.
Action:Check the syntax, insert the keyword TABLES where required, and re-execute the statement.
ORA-01911 CONTENTS keyword expected

Cause:The keyword CONTENTS is required in this context.
Action:Check the syntax, insert the keyword CONTENTS where required, and re-execute the statement.
ORA-01912 ROW keyword expected

Cause:The keyword ROW is required in this context.
Action:Check the syntax, insert the keyword ROW where required, and re-execute the statement.
ORA-01913 EXCLUSIVE keyword expected

Cause:The keyword EXCLUSIVE is required in this context.
Action:Check the syntax, insert the keyword EXCLUSIVE where required, and re-execute the statement.
ORA-01914 invalid auditing option for sequence numbers

Cause:AUDIT or NOAUDIT on a sequence number specifies an auditing option that is legal for tables but is not legal for sequence numbers.
Action:The following options may not be used for sequence numbers and should be removed from the statement: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, and EXECUTE.
ORA-01915 invalid auditing option for views

Cause:AUDIT or NOAUDIT on a view specifies an auditing option that is legal for tables but is not legal for views.
Action:The following options may not be used for views and should be removed from the statement: ALTER, INDEX, REFERENCES, and EXECUTE.
ORA-01916 ONLINE keyword or OFFLINE keyword expected

Cause:The keyword ONLINE or OFFLINE is required in this context.
Action:Check the syntax, insert the keyword ONLINE or OFFLINE where required, and re-execute the statement.
ORA-01917 user or role name does not exist

Cause:An invalid user or role name was specified.
Action:Check that a valid user or role name is used.
ORA-01918 user name does not exist

Cause:The user name specified cannot be found in the system.
Action:Check that a valid user or role name is used.
ORA-01919 role name does not exist

Cause:An invalid role name was specified.
Action:Check that a valid role name is specified.
ORA-01920 user name name conflicts with another user or role name

Cause:A user or role by that name already exists.
Action:Choose a different user name.
ORA-01921 role name name conflicts with another user or role name

Cause:A user or role by that name already exists.
Action:Choose a different role name.
ORA-01922 CASCADE must be specified to drop name

Cause:The user owns objects that need to be dropped along with the user.
Action:Use the CASCADE command.
ORA-01923 CASCADE aborted, objects locked by another user

Cause:A CASCADE operation was aborted because the specified user owns objects that are locked and thus cannot be dropped.
Action:Use the lock monitor to determine who locked the objects. The objects must be unlocked before the specified user can be dropped.
ORA-01924 role name not granted or does not exist

Cause:The grantor attempted to use a SET ROLE command to enable a role not granted to the grantor, or to enable a subrole, or the grantor did not have the SET ROLE system privilege.
Action:To use the SET ROLE command, check that the grantor has the SET ROLE system privilege and is granted the role to be passed on.
ORA-01925 maximum of num enabled roles exceeded

Cause:The specified number of enabled roles exceeds the value specified in the initialization parameter MAX_ENABLED_ROLES.
Action:Increase MAX_ENABLED_ROLES and restart the instance.
ORA-01926 cannot grant WITH GRANT OPTION to a role

Cause:Privileges with GRANT OPTION cannot be granted to a role.
Action:Perform the grant without the GRANT OPTION.
ORA-01927 original grantor must REVOKE privileges

Cause:Only the original grantor of privileges can REVOKE those privileges.
Action:Ask the database administrator for the grantor of the privileges and ask that person to revoke the privileges.
ORA-01928 GRANT option not granted for all privileges

Cause:The grantor does not have the GRANT OPTION for some or all of the privileges specified. These privileges are not granted.
Action:Check that grantor has the GRANT OPTION for privileges to be granted to a user or role.
ORA-01929 no privileges to GRANT

Cause:The grantor attempted to grant privileges using the object privilege ALL, but was not granted privileges to do so via the GRANT OPTION.
Action:Check that the grantor has the necessary privileges via the GRANT OPTION and try again.
ORA-01930 no privileges to REVOKE

Cause:The REVOKE ALL command was issued against a user when there were no privileges to revoke.
Action:This action is unnecessary.
ORA-01931 cannot grant UNLIMITED TABLESPACE, REFERENCES, or INDEX to a role

Cause:The UNLIMITED TABLESPACE, REFERENCES, or INDEX privileges cannot be granted to a role.
Action:Grant these privileges directly to the user.
ORA-01932 WITH ADMIN option not granted for role name

Cause:Grantor attempted an operation on a role, but does not have the necessary privileges via the ADMIN OPTION.
Action:Obtain the necessary privileges via the ADMIN OPTION and try again.
ORA-01933 cannot create a stored object using privileges from a role

Cause:An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles.
Action:Grant the required privileges to the user directly.
ORA-01934 circular role grant detected

Cause:A role, the primary role, cannot be granted to itself or another role that is granted via one or more roles to the primary role. This would cause a circular definition. See Oracle7 Server SQL Reference for more detail.
Action:Analyze the role and user structure to be used and check that no attempt is made to grant roles circularly.
ORA-01935 missing user or role name

Cause:The entered statement required a user or role name, and it was not specified.
Action:Specify a user or role name in the statement.
ORA-01936 cannot specify owner when creating users or roles

Cause:An attempt was made to specify an owner while creating a user or a role. Users and roles do not have owners.
Action:Do not specify an owner when creating a user or a role.
ORA-01937 missing or invalid role name

Cause:A valid role name was expected.
Action:Specify a valid role name.

ORA-01938 IDENTIFIED BY must be specified for CREATE USER

Cause:An attempt was made to create a user without using the IDENTIFIED EXTERNALLY clause or the IDENTIFIED BY password clause.
Action:In the CREATE USER statement, either assign the user a password using the IDENTIFIED BY password clause or use the IDENTIFIED EXTERNALLY clause, which allows the operating system to perform user authentication.
ORA-01939 only the ADMIN OPTION can be specified

Cause:An attempt was made to grant a system privilege or a role to a user using a GRANT statement with the GRANT OPTION (GRANT Form I). System privileges and roles must be granted using the WITH ADMIN OPTION (GRANT Form II).
Action:Use the WITH ADMIN OPTION, rather than the WITH GRANT OPTION, in the GRANT statement.
ORA-01940 cannot DROP a user that is currently logged in

Cause:An attempt was made to drop a user that was currently logged in.
Action:Make sure the user is logged out, then re-execute the command.
ORA-01941 SEQUENCE keyword expected

Cause:The keyword SEQUENCE is required in this context.
Action:Check syntax, insert keyword SEQUENCE as required, and try again.
ORA-01942 IDENTIFIED BY and EXTERNALLY cannot both be specified

Cause:A user was specified with an Oracle password and identified externally.
Action:Specify only one of these options. For details and syntax, see Oracle7 Server SQL Reference.
ORA-01943 IDENTIFIED BY already specified

Cause:The IDENTIFIED BY 'password' clause was specified more than once in a statement.
Action:Use the clause IDENTIFIED BY only once in the statement. If desired, change the user's password later with an ALTER USER command.
ORA-01944 IDENTIFIED EXTERNALLY already specified

Cause:The keyword IDENTIFIED EXTERNALLY was specified more than once in a statement.
Action:Use the keyword IDENTIFIED EXTERNALLY only once in the statement.
ORA-01945 DEFAULT ROLE[S] already specified

Cause:The keyword DEFAULT ROLE was used more than once in a CREATE USER or ALTER USER statement.
Action:Use the keyword DEFAULT ROLE only once in the statement. If desired, change the user's role later with an ALTER USER statement.
ORA-01946 DEFAULT TABLESPACE already specified

Cause:The keyword DEFAULT TABLESPACE was specified more than once in a CREATE USER or ALTER USER statement.
Action:Use the keyword DEFAULT TABLESPACE only once in the statement. If desired, change the user's tablespace later with an ALTER USER statement.
ORA-01947 TEMPORARY TABLESPACE already specified

Cause:The keyword TEMPORARY TABLESPACE was specified more than once in a CREATE USER or ALTER USER statement.
Action:Use the keyword TEMPORARY TABLESPACE only once in the statement. If desired, change the user's tablespace later with an ALTER USER statement.
ORA-01948 invalid DEFAULT ROLE specification

Cause:An invalid role name was specified.
Action:Check that the role name is correct.
ORA-01949 ROLE keyword expected

Cause:The context of the command or argument requires the use of the ROLE keyword; for example, DROP [ROLE], DEFAULT [ROLE], and so on.
Action:Check syntax and try again. For syntax rules, see Oracle7 Server SQL Reference.
ORA-01950 no privileges on tablespace "name"

Cause:The attempt to give the user a tablespace quota failed because the user does not have the necessary system privileges.
Action:Either grant the user the system privileges needed to create objects in the specified tablespace or grant the user a specific space resource in the tablespace.
ORA-01951 role not granted for ROLE: name, user: name

Cause:An attempt was made to revoke a role not granted to the user.
Action:Check that the user has the role.
ORA-01952 system privileges not granted to name

Cause:An attempt was made to revoke a system privilege not granted to the user.
Action:Check that the user has the system privilege.
ORA-01953 command no longer valid, see ALTER USER

Cause:The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to grant quotas on tablespaces.
Action:Use the ALTER USER command.
ORA-01954 DEFAULT ROLE clause not valid for CREATE USER

Cause:An attempt was made to grant a default role to a user in a CREATE USER statement. A DEFAULT ROLE clause cannot be used in a CREATE USER statement.
Action:Use a GRANT ROLE statement to grant an initial role to the user; then use the ALTER USER command to assign any desired default roles.
ORA-01955 user not granted DEFAULT ROLE name

Cause:An attempt was made to set the default role of a user to a role the user was not granted.

Action:Check that the user is granted the role before specifying it as the default.
ORA-01956 invalid command when OS_ROLES are being used

Cause:An attempt to grant a role to a user failed because Oracle database roles are disabled and operating system roles are enabled. This occurred because the OS_ROLES parameter in the initialization parameter file is set to TRUE.
Action:Ask the database administrator or security administrator how to set roles via the operating system. See also your Oracle7 operating system-specific Oracle documentation.
ORA-01967 invalid option for CREATE CONTROLFILE

Cause:An invalid CREATE CONTROLFILE option is present.
Action:Specify only valid CREATE CONTROLFILE options.
ORA-01968 only specify RESETLOGS or NORESETLOGS once

Cause:The keyword RESETLOGS or NORESETLOGS has appeared more than once in the CREATE CONTROLFILE statement.
Action:Specify RESETLOGS or NORESETLOGS only once.
ORA-01969 you must specify RESETLOGS or NORESETLOGS

Cause:The RESETLOGS or NORESETLOGS option is missing from the CREATE CONTROL FILE statement.
Action:Specify RESETLOGS or NORESETLOGS on the command line.
ORA-01970 you must specify a database name for CREATE CONTROLFILE

Cause:The CREATE CONTROLFILE statement issued is missing a database name.
Action:Issue the CREATE CONTROLFILE statement again with the appropriate database name for the DATABASE keyword.
ORA-01973 missing change number

Cause:The keyword CHANGE was specified on the command line, but the change number was not specified.
Action:Check the syntax of the command and retry it.
ORA-01974 illegal archive option

Cause:An invalid option to the ALTER SYSTEM ARCHIVE command was specified.
Action:Check the syntax of the command and retry it.
ORA-01975 illegal character in change number num

Cause:An invalid change number was supplied.
Action:Resubmit the command with a valid change number.
ORA-01976 missing change number

Cause:A change number was required, but not supplied.
Action:Check the syntax of the command, supply a change number where needed, then retry the command.
ORA-01977 missing thread number

Cause:The keyword THREAD was specified, but a thread number was not specified.
Action:Check the syntax of the command and retry it.
ORA-01978 missing sequence number

Cause:The keyword SEQUENCE was specified, but a sequence number was not specified.
Action:Check the syntax of the command and retry it.
ORA-01979 missing or invalid password for role name

Cause:An attempt was made to enable a role without giving the proper password.
Action:Use the IDENTIFIED BY clause in the SET ROLE command to specify the correct password.
ORA-01980 error during OS ROLE initialization

Cause:An operating system error occurred while loading a user's operating system roles.
Action:Check the operating system error and correct it.
ORA-01981 CASCADE CONSTRAINTS must be specified to perform this revoke

Cause:For this revoke, some foreign key constraints must be removed. To perform this automatically, CASCADE CONSTRAINTS can be specified as an option with the REVOKE command.
Action:Remove the constraints manually or specify CASCADE CONSTRAINTS.
ORA-01982 invalid auditing option for tables

Cause:The AUDIT or NOAUDIT command specified either REFERENCES or EXECUTE as an option. Those options are not legal for tables.
Action:Do not specify those auditing options on tables.
ORA-01983 invalid auditing option for DEFAULT

Cause:An illegal option was specified with DEFAULT.
Action:Do not specify the REFERENCES option with DEFAULT.
ORA-01984 invalid auditing option for procedures/packages/functions

Cause:An illegal option was specified with DEFAULT for a procedure, package, or function.
Action:The only legal auditing option with a default for procedures, packages, and functions is EXECUTE. Do not specify any option other than EXECUTE.
ORA-01985 cannot create user as LICENSE_MAX_USERS parameter exceeded

Cause:The maximum number of database users allowed by the database license has been created.
Action:Either drop existing users or contact your Oracle Corporation sales representative to upgrade your site license.
ORA-01986 invalid option for OPTIMIZER_GOAL

Cause:An invalid OPTIMIZER_GOAL option is present.
Action:Check the syntax for OPTIMIZER_GOAL, specify a valid option, and re-execute the statement.
ORA-01987 client O/S user name is too long

Cause:A client's O/S user name is too long for the O/S logon to succeed.
Action:Use a shorter O/S user name.
ORA-01988 remote O/S logon is not allowed

Cause:A remote O/S logon was attempted when it was not allowed.
Action:Use a local client or use the REMOTE_OS_AUTHENT initialization parameter to turn on remote O/S logon.
ORA-01989 role name not authorized by operating system

Cause:The specified operating system role does not exist, is not granted to you, or you did not provide the correct password.
Action:Retry the SET ROLE using a valid operating system role and password. See your DBA if you are not granted sufficient privileges.
ORA-01990 error opening password file name

Cause:An attempt to open the specified password file failed because of one of the following errors:

Action:Check for the above causes and correct as necessary.
ORA-01991 invalid password file name

Cause:The specified password file name is invalid.
Action:Specify a correct password file name.
ORA-01992 error closing password file name

Cause:The password file could not be closed because of an operating system error or because an authentication action failed.
Action:Check for the above causes and correct as necessary.
ORA-01993 error writing password file name

Cause:The password file could not be written to because of an operating system error or because an authentication action failed.
Action:Check for the above causes and correct as necessary.
ORA-01994 GRANT failed: cannot add users to public password file

Cause:A grant failed because a user could not be added to the password file. This is because the value of the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to PUBLIC.
Action:To add a user to the password file, shutdown the database, change the REMOTE_LOGIN_PASSWORDFILE initialization parameter to PRIVATE, and restart the database.
ORA-01995 error reading password file name

Cause:An operating system error occurred when trying to read the password file.
Action:Fix the operating system error.
ORA-01996 GRANT failed: password file name is full

Cause:The grant failed when a user could not be added to the password file, because all available slots in it were used already.
Action:Either recreate a larger password file or free up slots in the password file by revoking the SYSOPER and SYSDBA privileges from some of the remote users. You can determine which remote users are valid and their privileges by issuing the following query in SQL*DBA:

SELECT * FROM V$REMOTE_USERS;

ORA-01997 GRANT failed: user name is identified externally

Cause:You cannot grant the SYSOPER or SYSDBA privilege to a user created with the IDENTIFIED EXTERNALLY clause.
Action:If you wish to grant s6 the user the SYSOPER or SYSDBA privileges, drop paa and recreate the user without the IDENTIFIED EXTERNALLY clause.
ORA-01998 REVOKE failed: user SYS always SYSOPER and SYSDBA

Cause:You attempted to revoke one of the necessary privileges, SYSOPER or SYSDBA, from user SYS. These privileges cannot be revoked.
Action:Do not attempt this operation.
ORA-01999 password file mode has changed from mode to mode

Cause:Another instance has started with the FORCE_PASSWORD_FILEMODE initialization parameter, which is incompatible with the startup mode of your instance.
Action:Shut down your instance and start up later when the password file changes are completed for the other instance.
ORA-02000 missing keyword name

Cause:The statement entered requires the missing keyword.
Action:Use the specified keyword.
ORA-02002 user SYS is not permitted to create indexes with freelist groups

Cause:An attempt was made to create an index while connected as SYS.
Action:Connect as another user and retry the command.
ORA-02002 error while writing to audit trail

Cause:The auditing facility is unable to write to the AUDIT_TRAIL table. If this error occurs, SQL statements that are currently being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space.
Action:Add space to the SYSTEM tablespace or delete rows from the AUDIT_TRAIL table. If these operations fail or do not eliminate the problem, shut down and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE.
ORA-02003 invalid USERENV parameter

Cause:An invalid parameter was specified for the USERENV function.
Action:Specify one of the allowable parameters TERMINAL, SESSIONID, ENTRYID, or NLS_LANG.
ORA-02004 security violation

Cause:A user is attempting to perform an operation without the proper permission, and this fact is being recorded in the AUDIT_TRAIL table. This message only appears in the AUDIT_TRAIL table's return code column.
Action:For auditing information only; no action required.
ORA-02005 implicit (-1) length not valid for this bind or define datatype

Cause:A negative length for the define variable was passed to a define function.
Action:An explicit, non-negative, length parameter must be passed.
ORA-02006 invalid packed decimal format string

Cause:A packed decimal datatype was passed to a bind or define function, and the format string parameter was either not present or invalid.
Action:A valid format string parameter must be passed for a packed decimal variable. Check the programming manual for the definition of a packed decimal format string.
ORA-02007 can't use ALLOCATE or DEALLOCATE options with REBUILD

Cause:Allocate or deallocate storage and rebuild index are not compatible.
Action:Choose one or the other.

ORA-02008 non-zero scale specified for non-numeric column

Cause:A scale factor was specified for a bind or define of a non-numeric variable.
Action:Set the scale factor to zero, then retry the operation.
ORA-02009 the file size specified for a file must not be zero

Cause:A file specification included a SIZE clause with a zero value.
Action:If allowed, leave out the size clause or specify a valid value.
ORA-02010 missing host connect string

Cause:A quoted character string does not follow the keyword USING in the USING clause of a CREATE DATABASE LINK statement.
Action:Specify the host connect string, then retry the operation.
ORA-02011 duplicate database link name

Cause:The database link name specified in a CREATE DATABASE LINK statement already exists.
Action:Either specify a new name or drop the existing link.
ORA-02012 missing USING keyword

Cause:The keyword USING does not follow the CONNECT TO clause in a CREATE DATABASE LINK statement.
Action:Specify the USING clause after the CONNECT TO clause.
ORA-02013 missing CONNECT keyword

Cause:The keyword CONNECT does not follow the database link name in a CREATE DATABASE LINK statement.
Action:Specify the CONNECT clause after the database link name.
ORA-02014 cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.

Cause:An attempt was made to SELECT... FOR UPDATE from a view whose defining SELECT statement uses at least one of the following constructs in its outer block: outer join, GROUP BY clause, aggregate functions, SELECT DISTINCT, CONNECT BY clause, or set operation, UNION, INTERSECT, or MINUS.
Action:Do not use SELECT... FOR UPDATE on this view.
ORA-02015 cannot select FOR UPDATE from remote table

Cause:An attempt was made to SELECT... FOR UPDATE from a table in a remote database.
Action:It is not currently possible to SELECT... FOR UPDATE from a table in a remote database. Instead, log in or connect directly to the remote database before entering a SELECT... FOR UPDATE on its tables.
ORA-02016 cannot use a subquery in a START WITH on a remote database

Cause:An attempt was made to use a subquery in a START WITH clause. Such a subquery is not currently permitted if the table in the FROM clause of the tree query is in a remote database.
Action:It is necessary to connect directly to the remote database before using a subquery in the START WITH clause.
ORA-02017 integer value required

Cause:The specified value must be an integer.
Action:Specify an appropriate integer value, then retry the operation.
ORA-02018 database link of same name has an open connection

Cause:The user is currently connected to a PUBLIC database link with the same name as the database link name specified in a CREATE or DROP DATABASE LINK statement.
Action:Close the cursors that use the PUBLIC database link.
ORA-02019 connection description for remote database not found

Cause:The user attempted to connect or log in to a remote database using a connection description that could not be found.
Action:Specify an existing database link. Query the data dictionary to see all existing database links. See your operating system-specific SQL*Net documentation for valid connection descriptors.
ORA-02020 too many database links in use

Cause:The maximum number of active connections to remote databases per user login has been reached.
Action:If the user has no open cursors, the current SQL statement accesses more than the maximum allowed remote databases. Otherwise, the user may free remote database connections by closing all cursors that access the databases.

ORA-02021 DDL operations are not allowed on a remote database

Cause:An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname...".
Action:To alter the remote database structure, you must connect to the remote database with the appropriate privileges.
ORA-02022 remote statement has unoptimized view with remote object

Cause:The local view is unoptimized and contains references to objects at the remote database, and the statement must be executed at the remote database.
Action:Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote.
ORA-02023 START WITH or CONNECT BY predicate cannot be evaluated by remote database

Cause:The statement contains a tree query on a remote database, and the tree query's START WITH or CONNECT BY predicate contains a term that cannot be evaluated at the remote database. Such terms include calls to user functions, calls to USERENV, and references to ROWID.
Action:Remove the disallowed term, directly connect, or log on to the remote database.
ORA-02024 database link not found

Cause:The database link to be dropped is not found in the dictionary.
Action:Correct the database link name.
ORA-02025 all tables in the SQL statement must be at the remote database

Cause:A SQL statement referenced tables from multiple databases, and one or more of the remote databases are not Oracle7 Servers.
Action:Remote updates can be performed only if all databases in the SQL statement are Oracle7 Servers. Update the earlier version databases in a separate statement.
ORA-02026 missing LINK keyword

Cause:The keyword LINK is required in this context.
Action:Check syntax, insert keyword LINK as required, and try again.
ORA-02027 multi-row UPDATE of LONG column is not supported

Cause:A bind variable whose length is greater than 2000 bytes is being used to update a column, and the UPDATE statement affects more than one row.
Action:Check that each such bind variable updates only a single row.
ORA-02028 fetching an exact number of rows is not supported by the server

Cause:The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.
Action:Connect to a valid server or do not use an exact fetch.
ORA-02029 missing FILE keyword

Cause:The keyword FILE is required in this context.
Action:Check syntax, insert keyword FILE as required, and try again.
ORA-02030 can only select from fixed tables/views

Cause:An operation other than SELECT on a fixed dynamic performance table or view was attempted. It is only possible to select from fixed tables or views.
Action:Remove the fixed table or view name from the SELECT statement.
ORA-02031 no ROWID for fixed tables

Cause:An attempt was made to select the ROWID from a fixed table.
Action:Do not select ROWID from a fixed table.
ORA-02032 clustered tables cannot be used before the cluster index is built

Cause:An attempt was made to perform a DML operation on a clustered table for which no cluster index has yet been created.
Action:Create a cluster index before referencing clustered tables in a SQL statement.
ORA-02033 a cluster index for this cluster already exists

Cause:A cluster index already exists for the cluster.
Action:No action required.
ORA-02034 speed bind not permitted

Cause:Speed bind not allowed with supplied bind variables.
Action:No action required.
ORA-02035 illegal bundled operation combination

Cause:UPI bundled execution call was requested on an illegal combination of operations.
Action:Use a legal combination of operations and retry.
ORA-02036 too many variables to describe with automatic cursor open

Cause:UPI-bundled execution call tried to perform automatic cursor open and close on a describe operation. There were too many SELECT list items or bind variables to do this.
Action:Open and close cursor explicitly.
ORA-02037 universalized speed bind storage

Cause:A user attempted to perform a speed-execution call on a SQL statement containing host variables without first performing a speed-bind call.
Action:Perform a speed-bind call before performing a speed-execution call.
ORA-02038 define is not allowed for array type

Cause:A user attempted to define a select list variable of type "array". Arrays may serve only as host bind variables.
Action:Correct the offending code.
ORA-02039 bind by value is not allowed for array type

Cause:User attempted to bind an array host variable by value. Arrays may be bound only by reference.
Action:Correct the offending code.

02040-02099: Distributed Transactions

ORA-02040 remote database name does not support two-phase commit

Cause:A distributed update of more than one database was attempted, but the named database does not support the prepare phase of the two-phase commit, as determined by its logon transaction traits. The transaction was rolled back.
Action:Do not attempt to update the named database, unless it is the only database updated in the transaction. Distributed updates of more than one database in a single transaction can be performed only if all databases support the two-phase commit mechanism.
ORA-02041 client database did not begin a transaction

Cause:An update occurred at a coordinated database without the coordinator beginning a distributed transaction. This may happen if a stored procedure commits and then performs updates, and the stored procedure is invoked remotely. It could also happen if an external transaction monitor violates the XA protocol.
Action:If the cause is the former, check that any commit is not followed by an update.
ORA-02042 too many distributed transactions

Cause:The distributed transaction table is full because too many distributed transactions are active.
Action:Increase the DISTRIBUTED_TRANSACTIONS parameter in the initialization parameter file, shut down and restart Oracle, or run fewer transactions. If it is certain there are not too many concurrent distributed transactions, this may be an internal error. In this case, contact customer support. Shutting down and restarting the instance could be a work-around.
ORA-02043 must end current transaction before executing command

Cause:A transaction is in progress and one of the following commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.
Action:COMMIT or ROLLBACK the current transaction and retry the command.
ORA-02044 transaction manager login denied: transaction in progress

Cause:A remote transaction manager tried to log in while a distributed transaction is in progress. A protocol error occurred in the remote transaction manager.
Action:End the current transaction.
ORA-02045 too many local sessions participating in global transactions

Cause:There are too many sessions at this site to accommodate this transaction.
Action:Use an existing database link so that another session need not be created at the remote site.
ORA-02046 distributed transaction already begun

Cause:This is an internal error not normally encountered. A server session received a BEGIN_TRAN remote procedure call before finishing with a previous distributed transaction.
Action:Contact customer support.
ORA-02047 cannot join the distributed transaction in progress

Cause:This can happen only when attempting to update an Oracle Version 6 and an Oracle7 database in the same transaction, because either

Action:Complete the current transaction before attempting the action that caused the error.
ORA-02048 attempt to begin distributed transaction without logging on

Cause:The client program did not issue a distributed transaction login.
Action:This is an internal error, contact customer support.

ORA-02049 time-out: distributed transaction waiting for lock

Cause:The time to wait on a lock in a distributed transaction has been exceeded. This time is specified in the initialization parameter DISTRIBUTED_LOCK_TIMEOUT.
Action:This situation is treated as a deadlock and the statement was rolled back. To set the time-out interval to a longer interval, adjust the initialization parameter DISTRIBUTED_LOCK_TIMEOUT, then shut down and restart the instance.
ORA-02050 transaction num rolled back, some remote DBs may be in-doubt

Cause:There was a network failure or a remote failure during the two-phase commit.
Action:Notify the database administrator. The remote databases will automatically resynchronize when the failure is repaired.
ORA-02051 another session in same transaction failed

Cause:A session at the same site with the same global transaction identification failed.
Action:No action is necessary; the transaction will automatically recover.
ORA-02052 remote transaction failure at name

Cause:There was some error in a remote transaction at the named database link.
Action:More descriptive messages will follow. Correct the problem specified in the following messages and retry the operation.
ORA-02053 transaction num committed, some remote DBs may be in-doubt

Cause:There was a network failure or a remote failure during the two-phase commit.
Action:Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired.
ORA-02054 transaction num in-doubt

Cause:There was a network failure or a remote failure in the two-phase commit.
Action:Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. Monitor the DBA_2PC_INDOUBT and DBA_2PC_INCONSISTENT tables for the outcome and resubmit the transaction, if necessary.
ORA-02055 distributed update operation failed; rollback required

Cause:A failure during a distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent with others, the transaction must roll back to a savepoint or roll back entirely.
Action:Roll back to a savepoint or roll back the entire transaction and resubmit the rolled-back statements.
ORA-02056 2PC: str: bad two-phase command number num from name

Cause:There was a two-phase commit protocol error.
Action:The transaction may automatically recover. Monitor the DBA_2PC_INDOUBT and DBA_2PC_INCONSISTENT tables to determine the resolution. Enter the transaction again, if necessary. Contact customer support, if necessary.
ORA-02057 2PC: str: bad two-phase recovery state number num from name

Cause:An internal error in the two-phase recovery protocol occurred.
Action:Contact customer support.
ORA-02058 no prepared transaction found with ID num

Cause:A COMMIT FORCE was attempted on a transaction, but the transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID was not found in the DBA_2PC_INDOUBT table in prepared state.
Action:Check the DBA_2PC_INDOUBT table to ensure the proper transaction ID is used and attempt the commit again.
ORA-02059 ORA-CRASH-TEST-n in commit comment

Cause:This is a special comment used to test the two-phase commit.
Action:Do not use this special comment unless working with customer support.
ORA-02060 SELECT FOR UPDATE specified a join of non-collocated tables

Cause:An attempt was made to join tables in different remote databases in a SELECT... FOR UPDATE statement.
Action:Joined tables in a SELECT statement with the FOR UPDATE clause must reside at the same database. Simplify the SELECT... FOR UPDATE statement so that it joins only tables in the same database.
ORA-02061 lock table specified list of non-collocated tables

Cause:An attempt was made to lock more than one table in different remote databases in a LOCK TABLE statement. Tables in a LOCK TABLE statement must reside at the same database.
Action:Issue multiple LOCK TABLE commands.
ORA-02062 distributed recovery received DBID num, expected num

Cause:A database link at the coordinator point no longer points to the expected database. The database link may have been redefined, or a different database may have been mounted.
Action:Check the database link at the coordinator point to see if it was redefined. If so, contact the database administrator for the remote database to check whether the link still references a valid database. If the link changed, recreate it to reference a valid database at the remote site.
ORA-02063 preceding str from name

Cause:An Oracle error message was received from a remote database link.
Action:Refer to the preceding messages. Correct the problem mentioned in the preceding messages and try the operation again.
ORA-02064 iterated or long remote update with subquery not supported

Cause:One of the following unsupported operations was attempted:

Action:Simplify the remote update statement.
ORA-02065 illegal option for ALTER SYSTEM

Cause:The option specified for ALTER SYSTEM is not supported.
Action:Refer to Oracle7 Server SQL Reference for the proper syntax of the ALTER SYSTEM command.
ORA-02066 missing or invalid MTS_DISPATCHERS text

Cause:A character string literal was expected, but not found, in the ALTER SYSTEM SET MTS_DISPATCHERS command.
Action:Place the string literal containing the dispatcher's specification in the ALTER SYSTEM SET MTS_DISPATCHERS command.
ORA-02067 transaction or savepoint rollback required

Cause:A failure occurred, probably in a trigger or stored procedure with multiple remote updates. Some sites in the transaction may be inconsistent, so the previous Oracle call cannot be executed, and the transaction cannot be committed.
Action:Roll back to a previous savepoint or to the beginning of the transaction. Then resubmit the rolled-back statements.
ORA-02068 following severe error from name

Cause:A severe error, a disconnect or fatal Oracle error, was received from the given database link. See the accompanying messages for a more detailed description of the problem.
Action:Contact the remote system administrator to determine the cause of the remote problem and the estimated time of the problem's resolution.
ORA-02069 global_names parameter must be set to TRUE for this operation

Cause:A remote mapping of the statement is required but cannot be done because the parameter GLOBAL_NAMES is not set to TRUE.
Action:Issue the statement ALTER SESSION SET GLOBAL_NAMES = TRUE, if possible.
ORA-02070 database "name" does not support capability name in this context

Cause:The remote database does not support the named capability in the context in which it was used.
Action:Simplify the SQL statement.
ORA-02071 error initializing capabilities for remote database name

Cause:Oracle could not load the capability table from the named remote database.
Action:Contact customer support concerning the remote SQL*Connect product.
ORA-02073 sequence numbers not supported in remote updates

Cause:Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.
Action:Perform the operation without specifying a sequence number.
ORA-02074 cannot COMMIT or ROLLBACK in a distributed transaction

Cause:A COMMIT or ROLLBACK was attempted from a session other than the parent of a distributed transaction.
Action:Only the parent session can issue a COMMIT or ROLLBACK.
ORA-02076 sequence not co-located with updated or long column

Cause:All referenced sequences must be located on the same node as the updated table or the long column.
Action:Correct the problem and then reissue the statement.
ORA-02077 selects of long columns must be from co-located tables

Cause:All tables returning values of long columns in a SELECT statement must be located at the same node.
Action:Correct the problem, then reissue the statement.
ORA-02078 invalid setting for ALTER SYSTEM FIXED_DATE

Cause:An invalid value was used.
Action:Use a correct value.
ORA-02079 no new sessions may join a committing distributed transaction

Cause:A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch. That is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager.
Action:Contact customer support.
ORA-02080 database link is in use

Cause:A transaction is active or a cursor is open on the database link.
Action:Before closing a database link, you must first close all cursors and then end all transactions that use it.
ORA-02081 database link is not open

Cause:An attempt was made to use a database link that is not currently open.
Action:Resolve network problems or contact the remote database administrator to determine if the remote database's problem has been fixed. Contact the local database administrator to determine if network problems have been resolved. Wait until the link is open and try the operation again.
ORA-02082 a loop-back database link must have a connection qualifier

Cause:An attempt was made to create a database link with the same name as the current database.
Action:This database link needs a trailing qualifier to make the name unique. These qualifiers are operating system-specific. See your operating system-specific Oracle documentation for more information about creating database links.
ORA-02083 database name has illegal character str

Cause:The database name supplied contains an invalid character. For example, there can be no periods, semicolons, single quotes, double quotes, blanks, or non-printable characters in the database name. See Oracle7 Server Reference for naming rules.
Action:Specify a valid database name.
ORA-02084 database name is missing a component

Cause:The complete database name was not given
Action:Specify the full database name.
ORA-02085 database link name connects to name

Cause:The database link attempted to connect to a database with a different name. The name of the database link must be the same name as the name of the database.
Action:Create a database link with the same name as the database to which it connects.
ORA-02086 database link name is too long

Cause:The name of the database or database link is too long. Database and database link names can be no longer than 128 characters.
Action:Specify the correct database or database link name or specify a name with fewer characters.
ORA-02087 object locked by another process in same transaction

Cause:In a Parallel Server environment, a database link that loops back to the same instance is being used, and one session is trying to convert a lock that was obtained by the other session.
Action:Obtain a more restrictive lock first. For example if session 1 needs a SHARE lock, and session 2 needs an EXCLUSIVE lock, make sure that the EXCLUSIVE lock is obtained first. Otherwise, use the same session to access the object.
ORA-02088 distributed database option not installed

Cause:The distributed database option is not installed at this site, so the requested operation is not possible.
Action:Contact Oracle Corporation about obtaining the distributed database option.
ORA-02089 COMMIT is not allowed in a subordinate session

Cause:COMMIT was issued in a session that is not the two-phase commit global coordinator.
Action:Issue commits only at the global coordinator.
ORA-02091 transaction rolled back

Cause:The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.

Action:Complete the current transaction and then do the operation required.
ORA-02092 out of transaction table slots for distributed transaction

Cause:The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.

Cause:Add a rollback segment and do the operation again.
ORA-02093 TRANSACTIONS_PER_ROLLBACK_SEGMENT name more than maximum possible.

Cause:The value of the initialization parameter specified is greater than allowed on this port.
Action:Use the default value or reduce it to less than the maximum.
ORA-02094 replication option not installed

Cause:The replication option was not installed at this site. Updatable snapshots, deferred remote procedure calls, and other replication features were, therefore, unavailable.
Action:Install the replication option. The replication option is not part of the Oracle7 Server product and must be purchased separately. Contact an Oracle sales representative if the replication option needs to be purchased.
ORA-02095 specified initialization parameter cannot be modified

Cause:Specified initialization parameter is not modifiable with this option.
Action:Check the DBA guide for information about under what scope the parameter may be modified.

ORA-02096 specified initialization parameter is not modifiable with this option

Cause:Though the initialization parameter is modifiable, it cannot be modified using the specified command.
Action:Check the DBA guide for information about under what scope the parameter may be modified.

ORA-02098 error parsing index-table reference (:I)

Cause:An incorrect index-table (:I) syntax was encountered.
Action:This syntax is for Oracle internal use only.

02100-02139: Precompiler Runtime SQLLIB

02140-02299: SQL Parsing

ORA-02140 invalid tablespace name

Cause:A valid tablespace name does not follow ALTER TABLESPACE.
Action:Specify a valid tablespace name following ALTER TABLESPACE.
ORA-02141 invalid OFFLINE option

Cause:An option other than NORMAL or IMMEDIATE follows OFFLINE in an ALTER TABLESPACE statement.
Action:The user must either specify no option following OFFLINE or one of these options: NORMAL or IMMEDIATE.
ORA-02142 missing or invalid ALTER TABLESPACE option

Cause:An invalid option was specified after ALTER TABLESPACE.
Action:Use one of the valid options, such as ADD DATAFILE, RENAME DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, BEGIN BACKUP, or END BACKUP.
ORA-02143 invalid STORAGE option

Cause:An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, FREELISTS, FREELIST GROUPS, or PCTINCREASE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.
Action:Check syntax, specify only valid options, and try again.
ORA-02144 no option specified for ALTER CLUSTER

Cause:No valid ALTER CLUSTER options were specified.
Action:Specify one or more valid options, such as PCTFREE, PCTUSED, SIZE, INITRANS, MAXTRANS, or STORAGE.
ORA-02145 missing STORAGE option

Cause:No STORAGE options were specified following the keyword STORAGE.
Action:Check syntax, specify one or more valid STORAGE options, and try again.
ORA-02146 SHARED specified multiple times

Cause:The SHARED option was specified more than once in a CREATE DATABASE statement.
Action:Only specify the SHARED option once.
ORA-02147 conflicting SHARED/EXCLUSIVE options

Cause:Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.
Action:Specify SHARED or EXCLUSIVE, but not both.
ORA-02148 EXCLUSIVE specified multiple times

Cause:The EXCLUSIVE option was specified in a CREATE DATABASE statement more than once.
Action:Only specify the EXCLUSIVE option once.
ORA-02155 invalid DEFAULT tablespace identifier

Cause:A valid tablespace name does not follow DEFAULT TABLESPACE.
Action:Place a valid tablespace name after DEFAULT TABLESPACE and try again.
ORA-02156 invalid TEMPORARY tablespace identifier

Cause:A valid tablespace name does not follow TEMPORARY TABLESPACE.
Action:Place a valid tablespace name after TEMPORARY TABLESPACE and try again.
ORA-02157 no options specified for ALTER USER

Cause:No options were specified.
Action:Specify at least one ALTER USER option and try again.
ORA-02158 invalid CREATE INDEX option

Cause:An option other than PCTFREE, INITRANS, MAXTRANS, NOSORT, STORAGE, or TABLESPACE was specified.
Action:Specify one of the valid CREATE INDEX options and try again.
ORA-02159 installed DLM does not support releasable locking mode

Cause:The parameter file specified GC_*PARAMETERS that allow locks to be released by the LCK process when not in use. This mode required additional support in DLM that was not available.
Action:Specify configuration parameters that do not require the additional function.

ORA-02161 invalid value for MAXLOGFILES

Cause:A number does not follow MAXLOGFILES.
Action:Specify a number after MAXLOGFILES and try again.
ORA-02162 invalid value for MAXDATAFILES

Cause:A number does not follow MAXDATAFILES.
Action:Specify a number after MAXDATAFILES and try again.
ORA-02163 invalid value for FREELIST GROUPS

Cause:A number does not follow FREELIST GROUPS.
Action:Specify a number after FREELIST GROUPS and try again.
ORA-02164 DATAFILE clause specified more than once

Cause:The CREATE DATABASE statement contains more than one DATAFILE clause.
Action:Specify at most one DATAFILE clause and try again.
ORA-02165 invalid option for CREATE DATABASE

Cause:An invalid CREATE DATABASE option is present.
Action:Specify only valid CREATE DATABASE options and try again.
ORA-02166 ARCHIVELOG and NOARCHIVELOG specified

Cause:Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.
Action:Specify either of these two options, but not both, and try again.
ORA-02167 LOGFILE clause specified more than once

Cause:The CREATE DATABASE statement contains more than one LOGFILE clause.
Action:Specify at most one LOGFILE clause and try again.
ORA-02168 invalid value for FREELISTS

Cause:A number does not follow the FREELISTS storage option of the CREATE TABLE or CREATE INDEX statement.
Action:Specify a number after FREELISTS and try again.
ORA-02169 FREELISTS storage option not allowed

Cause:An attempt was made to specify the FREELISTS storage option when performing an operation other than CREATE TABLE or CREATE INDEX.
Action:Check the syntax of the statement, remove this option, then re-execute the statement.
ORA-02170 FREELIST GROUPS storage option not allowed

Cause:An attempt was made to specify the FREELIST GROUPS storage option. This option may be specified only when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file.
Action:Retry the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file.
ORA-02171 invalid value for MAXLOGHISTORY

Cause:A number does not follow MAXLOGHISTORY.
Action:Specify a number after MAXLOGHISTORY.
ORA-02172 the PUBLIC keyword is not appropriate for a disable thread

Cause:The PUBLIC keyword was specified when disabling a thread.
Action:Check the syntax of the command and retry.
ORA-02173 invalid option for DROP TABLESPACE

Cause:Something other than INCLUDING CONTENTS was found following the tablespace name, or text other than CASCADE CONSTRAINTS was found following INCLUDING CONTENTS.
Action:Place either nothing or only INCLUDING CONTENTS after the tablespace name, or place either nothing or only CASCADE CONSTRAINTS after INCLUDING CONTENTS and try again.
ORA-02174 missing required thread number

Cause:A thread number must be specified after THREAD keyword.
Action:Use correct syntax.
ORA-02175 invalid rollback segment name

Cause:In the CREATE or DROP ROLLBACK SEGMENT statements, a valid rollback segment name does not follow ROLLBACK SEGMENT.
Action:Place a valid rollback segment name after ROLLBACK SEGMENT and try again.
ORA-02176 invalid option for CREATE ROLLBACK SEGMENT

Cause:An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
Action:Specify one of the valid options, TABLESPACE or STORAGE, and try again.
ORA-02177 missing required group number

Cause:A group number must be specified after GROUP keyword.
Action:Check the syntax of the command, specify a group number after GROUP, and retry it.
ORA-02178 correct syntax is: SET TRANSACTION READ { ONLY | WRITE }

Cause:There is a syntax error in the user's statement.
Action:Correct the syntax as indicated and try again.
ORA-02179 valid options: ISOLATION LEVEL {SERIALIZABLE | READ COMMITTED}

Cause:There was a syntax error in the user's statement.
Action:Correct the syntax as indicated.
ORA-02180 invalid option for CREATE TABLESPACE

Cause:An invalid option follows CREATE TABLESPACE.
Action:Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, or OFFLINE, and try again.
ORA-02181 invalid option to ROLLBACK WORK

Cause:A word other than TO follows ROLLBACK [WORK].
Action:Place either nothing or TO SAVEPOINT after ROLLBACK [WORK] and try again.
ORA-02182 savepoint name expected

Cause:A valid savepoint name does not follow ROLLBACK [WORK] TO [SAVEPOINT].
Action:Place a savepoint name following TO [SAVEPOINT] and try again.
ORA-02183 valid options: ISOLATION_LEVEL {SERIALIZABLE | READ COMMITTED}

Cause:There was a syntax error in the user's statement.
Action:Correct the syntax as indicated.
ORA-02184 resource quotas are not allowed in REVOKE

Cause:In a revoke statement, a resource quota was specified.
Action:Specify the resource privilege without the quota and try again.
ORA-02185 a token other than WORK follows COMMIT

Cause:A token other than WORK follows COMMIT.
Action:Place either nothing or WORK after COMMIT and try again.
ORA-02186 tablespace resource privilege may not appear with other privileges

Cause:An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked.
Action:Use a separate GRANT or REVOKE statement for the resource quota privilege and try again.
ORA-02187 invalid quota specification

Cause:In a GRANT or REVOKE statement, an attempt was made to grant a tablespace quota above the upper limit.
Action:Grant a smaller tablespace quota and try again.
ORA-02189 required clause: ON <tablespace>

Cause:The GRANT or REVOKE statement specifying a tablespace quota requires the ON tablespace clause.
Action:Correct the syntax and try again.
ORA-02190 keyword TABLES expected

Cause:The keyword TABLES is expected following DROP CLUSTER cluster name INCLUDING.
Action:Place the keyword TABLES after INCLUDING and try again.
ORA-02191 correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT name

Cause:There is a syntax error in the SET TRANSACTION statement.
Action:Correct the syntax error and retry the statement.
ORA-02192 PCTINCREASE not allowed for rollback segment storage clauses

Cause:The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command.
Action:Retry the command without the PCTINCREASE clause.
ORA-02194 event specification syntax error num minor error num near name

Cause:There is a syntax error in an event specification.
Action:Check syntax and spelling and try again.
ORA-02195 attempt to create name object in a name tablespace

Cause:The object type was inconsistent with tablespace contents.
Action:Create the object in a different tablespace, or change the user defaults.

ORA-02196 PERMANENT/TEMPORARY option already specified

Cause:In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.
Action:Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.

ORA-02197 file list already specified

Cause:In a CREATE TABLESPACE statement, more than one DATAFILE clause was specified.
Action:Merge the DATAFILE clauses into a single clause specifying multiple files and try again.
ORA-02198 ONLINE/OFFLINE option already specified

Cause:In a CREATE TABLESPACE statement, the ONLINE and/or OFFLINE options were specified more than once.
Action:Specify either ONLINE or OFFLINE, but not both, and try again.
ORA-02199 missing DATAFILE clause

Cause:A CREATE TABLESPACE statement has no DATAFILE clause.
Action:Specify the missing DATAFILE clause and try again.
ORA-02200 WITH GRANT OPTION not allowed for PUBLIC

Cause:An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
Action:Remove either the PUBLIC or the WITH GRANT OPTION clause and try again.
ORA-02201 sequence not allowed here

Cause:An attempt was made to reference a sequence in a FROM list. This is not permitted. A sequence can only be referenced in a SELECT list.
Action:Check the statement syntax, correct the reference, and try again.
ORA-02202 no more tables permitted in this cluster

Cause:An attempt was made to create a table in a cluster that already contains 32 tables. No more than 32 tables may be stored in a cluster.
Action:Do not try to cluster more than 32 tables.
ORA-02203 INITIAL storage options not allowed

Cause:The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. This option may be specified only when the object is created.
Action:Remove the INITIAL option and try again.
ORA-02204 ALTER, INDEX, REFERENCE, and EXECUTE not allowed for views

Cause:An attempt was made to grant or revoke an invalid privilege on a view.
Action:Do not attempt to grant or revoke the privileges ALTER, INDEX, or REFERENCES on views.
ORA-02205 only SELECT and ALTER privileges are valid for sequences

Cause:An attempt was made to grant or revoke an invalid privilege on a sequence.
Action:Do not attempt to grant or revoke the privileges DELETE, INDEX, INSERT, UPDATE, REFERENCES, or EXECUTE on sequences.
ORA-02206 duplicate INITRANS option specification

Cause:INITRANS is specified more than once.
Action:Specify INITRANS only once and try again.
ORA-02207 invalid INITRANS option value

Cause:The INITRANS value is not an integer between 2 and 255, or it is not less than or equal to the MAXTRANS value.
Action:Specify a valid INITRANS value and try again.
ORA-02208 duplicate MAXTRANS option specification

Cause:The MAXTRANS option is specified more than once.
Action:Specify MAXTRANS only once and try again.
ORA-02209 invalid MAXTRANS option value

Cause:The MAXTRANS value is not an integer between 2 and 255, or it is not greater than or equal to the INITRANS value.
Action:Specify a valid MAXTRANS value and try again.
ORA-02210 no options specified for ALTER TABLE

Cause:No ALTER TABLE option was specified.
Action:Specify at least one ALTER TABLE option and try again.
ORA-02211 invalid value for PCTFREE or PCTUSED

Cause:The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.
Action:Specify an appropriate value for the option and try again.
ORA-02212 duplicate PCTFREE option specification

Cause:The PCTFREE option was specified more than once.
Action:Specify the PCTFREE option only once and try again.
ORA-02213 duplicate PCTUSED option specification

Cause:The PCTUSED option was specified more than once.
Action:Specify the PCTUSED option only once and try again.
ORA-02214 duplicate BACKUP option specification

Cause:The BACKUP option to ALTER TABLE was specified more than once.
Action:Specify the BACKUP option only once and try again.
ORA-02215 duplicate tablespace name clause

Cause:There is more than one TABLESPACE clause in one of the following statements: GRANT/REVOKE RESOURCE, CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.
Action:Check the statement syntax, specify only one TABLESPACE clause, and try again.
ORA-02216 tablespace name expected

Cause:A valid tablespace name is not present where required in one of the following statements: CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.
Action:Check the statement syntax, specify a valid tablespace name where required, and try again.
ORA-02217 duplicate storage option specification

Cause:A storage option, such as INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE, was specified more than once.
Action:Specify storage options only once and try again.
ORA-02218 invalid INITIAL storage option value

Cause:The specified value must be an integer.
Action:Specify an appropriate integer value and try again.
ORA-02219 invalid NEXT storage option value

Cause:The specified value must be an integer.
Action:Specify an appropriate integer value and try again.
ORA-02220 invalid MINEXTENTS storage option value

Cause:The specified value must be a positive integer that is less than or equal to MAXEXTENTS.
Action:Specify an appropriate integer value and try again.
ORA-02221 invalid MAXEXTENTS storage option value

Cause:The specified value must be a positive integer greater than or equal to MINEXTENTS.
Action:Specify an appropriate integer value and try again.
ORA-02222 invalid PCTINCREASE storage option value

Cause:The specified value must be a positive integer.
Action:Specify an appropriate integer value and try again.
ORA-02223 invalid OPTIMAL storage option value

Cause:The specified value must be an integer.
Action:Chose an appropriate integer value for the OPTIMAL storage option.
ORA-02224 EXECUTE privilege not allowed for tables

Cause:An attempt was made to GRANT or REVOKE an invalid privilege on a table.
Action:Do not attempt to GRANT or REVOKE the EXECUTE privilege on tables.
ORA-02225 only EXECUTE privilege is valid for procedures

Cause:An attempt was made to GRANT or REVOKE an invalid privilege on a procedure, function, or package.
Action:Do not attempt to GRANT or REVOKE any privilege other than EXECUTE on procedures, functions, or packages.
ORA-02226 invalid MAXEXTENTS value max allowed: num

Cause:The value specified for MAXEXTENTS is too large for the database block.
Action:Specify a value for MAXEXTENTS that is smaller than the number given in the message.
ORA-02227 invalid cluster name

Cause:A cluster name was not properly formed.
Action:Check the rules for forming object names and enter an appropriate cluster name.
ORA-02228 duplicate SIZE specification

Cause:The SIZE option is specified more than once.
Action:Specify the SIZE option only once and try again.
ORA-02229 invalid SIZE option value

Cause:The specified value must be an integer number of bytes.
Action:Specify an appropriate integer value and try again.
ORA-02230 invalid ALTER CLUSTER option

Cause:An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE was specified in an ALTER CLUSTER statement.
Action:Specify only valid options in the ALTER CLUSTER statement and try again.
ORA-02231 missing or invalid option to ALTER DATABASE

Cause:An invalid option was specified in the statement.
Action:Check the syntax of the ALTER DATABASE command. Specify only valid options in the ALTER DATABASE statement and try again.
ORA-02232 invalid MOUNT mode

Cause:A mode other than SHARED or EXCLUSIVE follows the keyword MOUNT in an ALTER DATABASE statement.
Action:Specify either SHARED, EXCLUSIVE, or nothing following the keyword MOUNT in the ALTER DATABASE statement and try again.
ORA-02233 invalid CLOSE mode

Cause:A mode other than NORMAL or IMMEDIATE follows the keyword CLOSE in an ALTER DATABASE statement.
Action:Specify either NORMAL, IMMEDIATE, or nothing following the keyword CLOSE in the ALTER DATABASE statement and try again.
ORA-02236 invalid filename

Cause:In a LOGFILE, DATAFILE, or RENAME clause, a character string literal was expected, but not found, in a filename list.
Action:Specify filenames using character string literals and try again.
ORA-02237 invalid file size

Cause:An integer file size does not follow SIZE in a LOGFILE or DATAFILE file list.
Action:Specify an appropriate file size following the keyword SIZE and try again.
ORA-02238 filename lists have different numbers of files

Cause:In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing filenames does not equal the number of new filenames.
Action:Make sure a new filename corresponds to each existing filename and try again.
ORA-02239 there are objects that reference this sequence

Cause:The sequence to be dropped is still referenced by other objects.
Action:Make sure the sequence name is correct or drop the constraint or object that references the sequence.
ORA-02240 invalid value for OBJNO or TABNO

Cause:A number does not follow OBJNO or TABNO.
Action:Specify a number after OBJNO or TABNO.
ORA-02241 must be of form EXTENTS FILE num BLOCK num SIZE num, ...

Cause:There was an error in the extent storage clause.
Action:Respecify the storage clause using the correct syntax and retry the command.
ORA-02242 no options specified for ALTER INDEX

Cause:No options were specified after ALTER INDEX.
Action:Specify the INITRANS, MAXTRANS, or STORAGE option in the ALTER INDEX statement and try again.
ORA-02243 invalid ALTER INDEX or ALTER SNAPSHOT option

Cause:An option other than INITRANS, MAXTRANS, or STORAGE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.
Action:Specify only valid options and try again.
ORA-02244 invalid ALTER ROLLBACK SEGMENT option

Cause:An option other than STORAGE was found.
Action:Specify the STORAGE option and try again.
ORA-02245 invalid ROLLBACK SEGMENT name

Cause:A rollback segment name was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.
Action:Place a rollback segment name after SEGMENT and try again.
ORA-02246 missing EVENTS text

Cause:A character string literal was expected, but not found, following the ALTER SESSION SET EVENTS command.
Action:Place the string literal containing the EVENTS text after the keyword EVENTS and try again.
ORA-02247 no option specified for ALTER SESSION

Cause:The option SET EVENTS was expected, but not found, following the ALTER SESSION command.
Action:Place the SET EVENTS option after the ALTER SESSION command and try again.
ORA-02248 invalid option for ALTER SESSION

Cause:An option other than SET EVENTS was found following the ALTER SESSION command.
Action:Specify the SET EVENTS option after the ALTER SESSION command and try again.
ORA-02249 missing or invalid value for MAXLOGMEMBERS

Cause:A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the operating system-specific maximum number of log file members.
Action:Specify a valid number after MAXLOGMEMBERS.
ORA-02250 missing or invalid constraint name

Cause:The constraint name is missing or invalid.
Action:Specify a valid constraint name and try again.
ORA-02251 subquery not allowed here

Cause:A subquery is not allowed at this point in the statement.
Action:Remove or relocate the subquery and try again.
ORA-02252 check constraint condition not properly ended

Cause:The specified search condition for the check constraint is not properly ended.
Action:Check and correct the search condition's syntax. Then retry the operation.
ORA-02253 constraint specification not allowed here

Cause:A constraint specification is not allowed at this point in the statement.
Action:Remove or relocate the constraint specification and try again.
ORA-02254 DEFAULT <expression> not allowed here

Cause:A default-value expression is not allowed for the column at this point in the statement.
Action:Remove or relocate the default-value expression and try again.
ORA-02255 NOT NULL not allowed after DEFAULT NULL

Cause:A NOT NULL specification conflicts with the NULL default value.
Action:Remove either the NOT NULL or the DEFAULT NULL specification and try again.
ORA-02256 number, type, and size of referencing columns must match referenced columns

Cause:The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list, or the datatype or size of at least one referencing column is not equal to the datatype or size of its referenced column.
Action:Ensure that the referencing columns match the referenced columns.
ORA-02257 maximum number of columns exceeded

Cause:The number of columns in the key list exceeds the maximum number.
Action:Reduce the number of columns in the list.
ORA-02258 duplicate or conflicting NULL and/or NOT NULL specifications

Cause:A duplicate or conflicting NULL and/or NOT NULL was specified.
Action:Remove one of the conflicting specifications and try again.
ORA-02259 duplicate UNIQUE/PRIMARY KEY specifications

Cause:A duplicate unique or primary key was specified.
Action:Remove the duplicate specification and try again.
ORA-02260 table can have only one primary key

Cause:Two or more primary keys were specified for the same table.
Action:Remove the extra primary keys and try again.
ORA-02261 such unique or primary key already exists in the table

Cause:A unique or primary key was specified that already exists for the table.
Action:Remove the extra key and try again.
ORA-02262 ORA-num occurs while type-checking column default value expression

Cause:An attempt to alter a column's datatype caused a type-checking error because the new datatype conflicted with the existing column's default value expression.
Action:Remove the default value expression or do not alter the column's datatype, and try again.
ORA-02263 need to specify the datatype for this column

Cause:The required datatype for the column is missing.
Action:Specify the required datatype and try again.
ORA-02264 name already used by an existing constraint

Cause:The specified constraint name is not unique.
Action:Specify a unique constraint name for the constraint and try again.
ORA-02265 cannot derive the datatype of the referencing column

Cause:The datatype of the referenced column is not defined as yet.
Action:Make sure that the datatype of the referenced column is defined before referencing it.
ORA-02266 unique/primary keys in table referenced by enabled foreign keys

Cause:An attempt was made to drop or truncate a table with unique or primary keys referenced by foreign keys enabled in another table.
Action:Before dropping or truncating the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command:

SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";

ORA-02267 column type incompatible with referenced column type

Cause:An attempt was made to perform an operation on a pair of columns with incompatible datatypes.
Action:Specify a compatible datatype for the referencing column.
ORA-02268 referenced table does not have a primary key

Cause:The referenced table does not have a primary key.
Action:Do not attempt to reference the table using a unique key, or create a unique key for the table.
ORA-02269 key column cannot be of LONG datatype

Cause:An attempt was made to define a key column of datatype LONG. This is not allowed.
Action:Change the datatype of the column or remove the LONG column from the key, and try again.
ORA-02270 no matching unique or primary key for this column-list

Cause:An attempt was made to reference a unique or primary key in a table with a CREATE or ALTER TABLE statement when no such key exists in the referenced table.
Action:Add the unique or primary key to the table or find the correct names of the columns with the primary or unique key, and try again.
ORA-02271 table does not have such a constraint

Cause:An attempt was made to reference a table using a constraint that does not exist.
Action:Check the spelling of the constraint name or add the constraint to the table, and try again.
ORA-02272 constrained column cannot be of LONG datatype

Cause:A constrained column cannot be defined as datatype LONG. This is not allowed.
Action:Change the datatype of the column or remove the constraint on the column, and try again.
ORA-02273 this unique/primary key is referenced by some foreign keys

Cause:A unique or primary key referenced by foreign keys cannot be dropped.
Action:Remove all references to the key before dropping it.
ORA-02274 duplicate referential constraint specifications

Cause:A referential constraint was specified more than once. This is not allowed.
Action:Remove the duplicate specification.
ORA-02275 such a referential constraint already exists in the table

Cause:An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and so is not allowed.
Action:Be sure to specify a constraint only once.
ORA-02276 default value type incompatible with column type

Cause:The type of the evaluated default expression is incompatible with the datatype of the column.
Action:Modify the default expression or change the column's datatype, and try again.
ORA-02277 invalid sequence name

Cause:An invalid sequence name was specified.
Action:Check syntax and spelling, specify a valid sequence name, and try again.
ORA-02278 duplicate or conflicting MAXVALUE/NOMAXVALUE specifications

Cause:Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications.
Action:Remove one of the conflicting specifications and try again.
ORA-02279 duplicate or conflicting MINVALUE/NOMINVALUE specifications

Cause:Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified.
Action:Remove one of the conflicting specifications and try again.
ORA-02280 duplicate or conflicting CYCLE/NOCYCLE specifications

Cause:Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified.
Action:Remove one of the conflicting specifications and try again.
ORA-02281 duplicate or conflicting CACHE/NOCACHE specifications

Cause:Duplicate or conflicting CACHE and/or NOCACHE clauses were specified.
Action:Remove one of the conflicting specifications and try again.
ORA-02282 duplicate or conflicting ORDER/NOORDER specifications

Cause:Duplicate or conflicting ORDER and/or NOORDER clauses were specified.
Action:Remove one of the conflicting specifications and try again.
ORA-02283 cannot alter starting sequence number

Cause:An attempt was made to alter a starting sequence number. This is not allowed.
Action:Do not try to alter a starting sequence number.
ORA-02284 duplicate INCREMENT BY specifications

Cause:A duplicate INCREMENT BY clause was specified.
Action:Remove the duplicate specification and try again.
ORA-02285 duplicate START WITH specifications

Cause:A duplicate START WITH clause was specified.
Action:Remove the duplicate specification and try again.
ORA-02286 no options specified for ALTER SEQUENCE

Cause:No ALTER SEQUENCE option was specified.
Action:Check the syntax. Then specify at least one ALTER SEQUENCE option.
ORA-02287 sequence number not allowed here

Cause:The specified sequence number reference, CURRVAL or NEXTVAL, is inappropriate at this point in the statement.
Action:Check the syntax. Then remove or relocate the sequence number.
ORA-02288 invalid OPEN mode

Cause:A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode.
Action:Remove the invalid mode from the statement or replace it with the keyword RESETLOGS, and try again.
ORA-02289 sequence does not exist

Cause:The specified sequence does not exist, or access privilege is required for this operation. Also, this error can occur if attempting to access a remote sequence through an invalid or non-existent database link.
Action:Check spelling of the sequence name or obtain the required access privilege. If necessary, create the sequence. All remote sequences accessed in a distributed transaction must be on the same node.
ORA-02290 check constraint str.name violated

Cause:The value or values attempted to be entered in a field or fields violate a defined check constraint.
Action:Enter values that satisfy the constraint.
ORA-02291 integrity constraint str.name violated - parent key not found

Cause:An attempt was made to INSERT or UPDATE a foreign key value. The result was a value that is not in the parent key.
Action:UPDATE to or INSERT a value that is in the parent key.
ORA-02292 integrity constraint str.name violated - child record found

Cause:An attempt was made to delete a row that is referenced by a foreign key.
Action:It is necessary to DELETE or UPDATE the foreign key before changing this row.
ORA-02293 cannot enable name - check constraint violated

Cause:An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values.
Action:Retry the ALTER TABLE statement, specifying a check constraint on a table containing complying values.

ORA-02294 cannot add referential constraint - parent keys not found

Cause:An attempt was made via an ALTERTABLE statement to add a referential constraint to a populated table that had no matching parent values.
Action:Retry the ALTER TABLE statement, specifying a valid primary key in a parent table.
ORA-02295 found more than one enable/disable clause for constraint

Cause:An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint.
Action:Only one ENABLE or DISABLE clause may be specified for a given constraint.
ORA-02296 cannot enable name - null values found

Cause:An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not satisfy the constraint.
Action:Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause.

ORA-02297 cannot disable constraint name.name - dependencies exist

Cause:An alter table disable constraint failed because the table has foreign keys that are dependent on the constraint.
Action:Either disable the foreign key constraints or use a DISABLE CASCADE command.
ORA-02298 cannot enable name - parent keys not found

Cause:An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records.
Action:Make sure that the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command.

ORA-02299 cannot enable name - duplicate keys found

Cause:An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values.
Action:Make sure that the table has no duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command.

02351-02375: SQL*Loader in Direct Path Mode

ORA-02351 record num: Rejected - Error on table name, column name

Cause:The indicated record caused an error on insert.
Action:Determine the error and correct the record.
ORA-02352 direct path connection must be homogeneous

Cause:The user-side to kernel-side connection is heterogeneous.
Action:Check that the connection is between identical hardware and operating systems.
ORA-02353 multi-byte character error

Cause:The text specified by POSITION or terminated by new lines is invalid.
Action:Edit the control file or the datafile to fix the alignment of the column.
ORA-02354 conversion initialization error occurred on field name

Cause:An error occurred during conversion initialization for a field.
Action:This is an internal error. Contact customer support.
ORA-02355 conversion error occurred on CONSTANT field str

Cause:A CONSTANT field caused an error. All rows will be rejected.
Action:Determine the Oracle error and correct the record.
ORA-02356 the database is out of space. The load cannot continue

Cause:The load was discontinued due to space exhaustion in the database.
Action:Add space for the specified table.
ORA-02357 packed decimal conversion error

Cause:The column could not be converted from packed decimal to character.
Action:Check the column and make it conform to packed decimal format.
ORA-02358 zoned decimal conversion error

Cause:The column could not be converted from packed decimal to character.
Action:Check the column and make it conform to packed decimal format.
ORA-02359 field in datafile exceeded maximum specified length

Cause:The field is too long for the specified column.
Action:Shorten the field so that the length of the field equals or is less than the column length.
ORA-02360 column not found before end of logical record (use TRAILING NULLCOLS)

Cause:A column started after the end of the logical record had been reached.
Action:Use the TRAILING NULLCOLS option or supply data for the column.
ORA-02361 initial enclosing character not found

Cause:The initial enclosing character of an enclosed field was not found.
Action:Supply the character before the start of the field.
ORA-02362 logical record ended - second enclosing character not present

Cause:The second enclosing character of an enclosed field was not found.
Action:Supply the character after the end of the field.
ORA-02363 no terminator found after TERMINATED and ENCLOSED field

Cause:No terminator was found after a terminated and enclosed field.
Action:Supply the terminator after the end of the field.
ORA-02364 record num: Discarded - failed all WHEN clauses

Cause:The record was not loaded because it failed the WHEN clauses of all the tables.
Action:No action required.
ORA-02365 index name was left in Direct Load State due to

Cause:The index was not loaded. The cause of the error is stated after the message.
Action:Correct the cause of the error, then reload.
ORA-02366 the following index or indexes on table name were processed

Cause:The indexes listed for the named table were loaded.
Action:No action required.
ORA-02367 index name was loaded

Cause:The index specified in the message was loaded.
Action:No action required.
ORA-02368 record num: Discarded - all columns null.

Cause:The record was not loaded because all of the columns in the table were null for that record.
Action:No action required.
ORA-02369 warning: Variable-length field was truncated

Cause:A variable-length field was truncated by the end of the logical record.
Action:Although this is a warning, a variable length field has the length embedded in the data for each row, so check the data.
ORA-02370 record num - Warning on table name, column num

Cause:The record indicated caused a warning.
Action:Determine the warning and correct the record, if necessary.
ORA-02371 loader must be at least version num for direct path

Cause:The version of SQL*Loader being used is incompatible with this version of Oracle.
Action:Upgrade the version of SQL*Loader to at least the specified version or use the conventional path.
ORA-02372 relative start position > absolute field end position

Cause:The relative start of a field specified as POSITION(*+n:y) occurred after the absolute position y.
Action:Check that the values of n and y are correct and that the statement was entered correctly. Also check that all opening delimiters have matching closing delimiters.
ORA-02373 Error parsing insert statement for table name

Cause:A parsing error occurred.
Action:Check the message following this parsing error message.
ORA-02374 No more slots for read buffer queue

Cause:There are no free read buffers.
Action:Use the READBUFFERS keyword in the loader to increase the number of read buffers.

02376-02399: Oracle Resources

ORA-02376 invalid or redundant resource

Cause:A resource that is not defined or that is specified twice appears in the CREATE or ALTER PROFILE statement.
Action:Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the statement to see that each resource is listed only once.
ORA-02377 invalid resource limit

Cause:An invalid resource limit of 0 was specified.
Action:Specify a resource limit greater than 0.
ORA-02378 duplicate resource name name

Cause:The same resource was specified twice in a CREATE or ALTER PROFILE statement.
Action:Issue the statement again, carefully checking that each resource is used only once.
ORA-02379 profile name already exists

Cause:An attempt was made to create a profile that already exists.
Action:Create the profile with a name not already used by another profile.
ORA-02380 profile name does not exist

Cause:An attempt was made to assign a user to a non-existent profile.
Action:Assign the user to an existing profile.
ORA-02381 cannot drop PUBLIC_DEFAULT profile

Cause:An attempt was made to drop the PUBLIC_DEFAULT profile.
Action:The PUBLIC_DEFAULT profile cannot be dropped.
ORA-02382 profile name has users assigned, cannot drop without CASCADE

Cause:An attempt was made to drop a profile that had users assigned to it without using the CASCADE option of the DROP PROFILE statement. A profile that has users assigned to it cannot be dropped, unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile.
Action:To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option.
ORA-02383 illegal cost factor

Cause:A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement.
Action:Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Issue the statement again, using a positive integer value for each resource specified.
ORA-02390 exceeded COMPOSITE_LIMIT, logoff in progress

Cause:The COMPOSITE_LIMIT for the profile is exceeded. That is, the weighted sum of the connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit set by the COMPOSITE_LIMIT clause set in the user profile.
Action:If this happens often, ask the database administrator to raise the COMPOSITE_LIMIT of the user profile, or determine which resource is used the most and raise the limit on that resource.
ORA-02391 exceeded simultaneous SESSIONS_PER_USER limit

Cause:An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile.
Action:End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile.

ORA-02392 exceeded session limit on CPU usage, logging off

Cause:An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile.
Action:If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile.
ORA-02393 exceeded call limit on CPU usage

Cause:An attempt was made to exceed the maximum CPU time for a call, a parse, execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile.
Action:If this happens often, ask the database administrator to increase the CPU_PER_CALL limit of the user profile.
ORA-02394 exceeded session limit on I/O usage, logging off

Cause:An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile.
Action:If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile.
ORA-02395 exceeded call limit on I/O usage

Cause:An attempt was made to exceed the maximum I/O for a call, a parse, execute, or fetch, allowed by the LOGICAL_READS_PER_CALL clause of the user profile.
Action:If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit of the user profile.
ORA-02396 exceeded max Idle Time, please connect again

Cause:A user has exceeded the maximum time allowed to remain idle.
Action:The user must reconnect to the database.
ORA-02397 exceeded PRIVATE_SGA Limit, logging off

Cause:This error occurs only when using a multi-threaded server.
Action:Contact the database administrator to expand the PRIVATE_SGA limit.
ORA-02398 exceeded procedure space usage

Cause:Stored procedures used up too much space in the SYSTEM tablespace.
Action:Use fewer stored procedures or add an additional file to the system tablespace.
ORA-02399 exceeded maximum connect time, logging off

Cause:A user has exceeded the maximum time allowed to be connected to the database.
Action:The user must reconnect to the database.

02400-02419: EXPLAIN PLAN Command

ORA-02401 cannot EXPLAIN view owned by another user

Cause:The view specified in the user's SQL statement belongs to another user and cannot be explained.
Action:Create a view that has the same definition but belongs to the current user.
ORA-02402 PLAN_TABLE not found

Cause:The PLAN_TABLE used by EXPLAIN to describe the SQL statement does not exist in the current schema.
Action:Create a PLAN_TABLE in the current schema or use the INTO clause to store the EXPLAIN results in a plan table with a different name.
ORA-02403 plan table does not have correct format

Cause:The plan table does not have the appropriate columns.
Action:Redefine the plan table with the appropriate columns.
ORA-02404 specified plan table not found

Cause:The specified plan table cannot be found.
Action:Create the specified plan table or use an existing one.

02420-02429: Schemas

ORA-02420 missing schema authorization clause

Cause:The schema AUTHORIZATION clause is missing in a CREATE SCHEMA statement.
Action:Check the syntax of the statement, provide a valid schema AUTHORIZATION clause, and retry the statement.
ORA-02421 missing or invalid schema authorization identifier

Cause:Either:

Action:If the cause is
ORA-02422 missing or invalid schema element

Cause:A statement other than a CREATE TABLE, CREATE VIEW, or GRANT appears in a CREATE SCHEMA statement.
Action:See Oracle7 Server SQL Reference for the valid elements of the CREATE SCHEMA statement.
ORA-02423 schema name does not match schema authorization identifier

Cause:A table definition with a schema name prepended to the table name does not match the schema name provided in the AUTHORIZATION clause of a CREATE SCHEMA STATEMENT.
Action:Check that the schema names match the one given in the CREATE SCHEMA statement.
ORA-02424 potential circular view references or unknown referenced tables

Cause:The CREATE SCHEMA statement contains a view that depends on other views contained in the CREATE SCHEMA statement, or they contain references to non-existing tables.
Action:Create the dependent views in a separate CREATE SCHEMA statement and ensure that all referenced tables are either defined in the CREATE SCHEMA statement or exist outside the statement.
ORA-02425 create table failed

Cause:A CREATE TABLE statement failed in the CREATE SCHEMA statement.
Action:The cause for failure will be presented below this message. Follow the appropriate actions as suggested by the subsequent messages.
ORA-02426 privilege grant failed

Cause:A GRANT statement failed in the CREATE SCHEMA statement.
Action:The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages.
ORA-02427 create view failed

Cause:A CREATE VIEW statement failed in the CREATE SCHEMA statement.
Action:The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages.
ORA-02428 could not add foreign key reference

Cause:Oracle could not add a foreign key reference because of an error in the declaration. Either the referenced table does not exist or the table does not have a unique key.
Action:Check that the referenced table exists and/or has a unique key.
ORA-02429 cannot drop index used for enforcement of unique/primary key

Cause:An attempt was made to drop an index that is being used as the enforcement mechanism for a unique or primary key.
Action:Drop the integrity constraint instead of dropping the index.

02430-02449: Constraint Enabling & Disabling

ORA-02430 cannot enable constraint name - no such constraint

Cause:The named constraint does not exist for this table.
Action:Check that a constraint exists before trying to enable it.
ORA-02431 cannot disable constraint name - no such constraint

Cause:The named constraint does not exist for this table.
Action:Check that a constraint exists before trying to disable it.
ORA-02432 cannot enable primary key - primary key not defined for table

Cause:An attempt was made to enable a primary key that is not defined for the table.
Action:Add a primary key definition for the table.
ORA-02433 cannot disable primary key - primary key not defined for table

Cause:An attempt was made to disable a primary key that is not defined for the table.
Action:Check that a primary key exists before trying to disable it.
ORA-02434 cannot enable unique(str) - unique key not defined for table

Cause:An attempt was made to enable a unique key that is not defined for the table.
Action:Check that a unique key exists before trying to enable it.
ORA-02435 cannot disable unique str - unique key not defined for table

Cause:An attempt was made to disable a unique key that is not defined for the table.
Action:Check that a unique key exists before trying to disable it.
ORA-02436 date or system variable wrongly specified in CHECK constraint

Cause:An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.
Action:Completely specify the date constant or system variable.
ORA-02437 cannot enable name - primary key violated

Cause:An attempt was made to enable a primary key constraint on a column that contains either duplicate values or null.
Action:Remove the duplicate values or null before enabling the primary key constraint.

ORA-02438 column check constraint cannot reference other columns

Cause:An attempt was made to define a column check constraint that references another column.
Action:This is not permitted for column check constraints. Create this constraint as a table check constraint.
ORA-02439 non-unique index exists on unique/primary key constraint

Cause:An attempt was made to enable a primary key or unique constraint on a column that has an existing non-unique index.
Action:Drop the non-unique index on the column or do not attempt to enable this constraint.
ORA-02440 create as select with referential constraints not allowed

Cause:Integrity constraints on a table cannot be created when creating the table using the CREATE TABLE... AS SELECT... form.
Action:First, create the table, and then alter the table to add the desired integrity constraints.
ORA-02441 cannot drop non-existent primary key

Cause:An attempt was made to drop the primary key constraint on a table, but there is no primary key constraint on this table.
Action:Ensure the correct table name is entered in the statement. Otherwise, no action required.
ORA-02442 cannot drop non-existent unique key

Cause:An attempt was made to drop a unique key constraint for a column that does not have a unique key constraint.
Action:Make certain the correct column name was entered. Otherwise, no action required.
ORA-02443 cannot drop constraint - non-existent constraint

Cause:An attempt was made to drop a constraint that does not exist.
Action:Make certain the constraint and table name are correct and attempt the procedure again.
ORA-02444 cannot resolve referenced object in referential constraints

Cause:An attempt was made to define a foreign key with a reference to a schema object that cannot be resolved to a base table reference.
Action:Define referential constraints only with schema objects resolving to a base table.
ORA-02445 exceptions table not found

Cause:The explicitly or implicitly declared exceptions table does not exist.
Action:If the correct exceptions table name was used, then create the table and retry the enable command.
ORA-02446 CREATE TABLE ... AS SELECT failed - check constraint violated

Cause:An attempt was made to use a CREATE TABLE... AS SELECT statement when some rows violated one or more CHECK constraints.
Action:Do not select rows that violate constraints.

02450-02475: Hash Cluster Commands

ORA-02450 invalid hash option - missing keyword IS

Cause:The IS keyword is missing from the CREATE CLUSTER command.
Action:Check the syntax of the command and retry the statement.
ORA-02451 duplicate HASHKEYS specification

Cause:The HASHKEYS option of the CREATE CLUSTER command is specified more than once.
Action:Check the syntax of the command, make certain to specify the HASHKEYS option only once, then retry the command.
ORA-02452 invalid HASHKEYS option value

Cause:The value specified for HASHKEYS must be an integer.
Action:Check the syntax of the command, make certain to specify an integer for the HASHKEYS option, then retry the command.
ORA-02453 duplicate HASH IS specification

Cause:The HASH IS option is specified more than once.
Action:Check the syntax of the command, make certain to specify the HASH IS option only once, then retry the command.
ORA-02454 number of hash keys per block num exceeds maximum of num

Cause:The SIZE option specified for this hashed cluster is to small.
Action:Retry the statement using a larger value for the SIZE option.
ORA-02455 the number of cluster key column must be 1

Cause:An attempt was made to create a cluster using the HASH IS option with a number of key columns other than 1. Specify only one key column when using the HASH IS option.
Action:Check the syntax of the command. Either specify only one key column or do not specify the HASH IS option, then retry the command.
ORA-02456 the HASH IS column specification must be NUMBER(*,0)

Cause:The column specification in the command must specify an integer.
Action:Check the syntax of the command, make certain to specify an integer for the column specification, then retry the command.
ORA-02457 the HASH IS option must specify a valid column

Cause:An attempt was made to create a cluster with the HASH IS option without specifying a valid column name.
Action:Check the syntax of the command. Specify a valid column name in the statement, then retry the statement.
ORA-02458 HASHKEYS must be specified for a HASH CLUSTER

Cause:An attempt was made to create a hash cluster without specifying the HASHKEYS option in the statement.
Action:Check the syntax of the command, specify the HASHKEYS option, and retry the command.
ORA-02459 hashkey value must be a positive integer

Cause:The value specified for HASHKEYS was not a positive integer.
Action:Check the syntax of the command, specify only positive integers for the HASHKEYS option, then retry the command.
ORA-02460 inappropriate index operation on a hash cluster

Cause:An attempt was made to create a cluster index on a hash cluster.
Action:Creation of cluster indexes on hash clusters is not allowed. Do not attempt to create this index.
ORA-02461 inappropriate use of the INDEX option

Cause:The INDEX option cannot be specified for hash clusters.
Action:Check the syntax of the command. Do not specify the INDEX option with hash clusters.
ORA-02462 duplicate INDEX option specified

Cause:The INDEX option is specified more than once.
Action:Check the syntax of the command, correct the problem, then retry the statement.
ORA-02463 duplicate HASH IS option specified

Cause:The HASH IS option is specified more than once.
Action:Check the syntax of the command, correct the problem, then retry the statement.
ORA-02464 cluster definition cannot be both HASH and INDEX

Cause:Both the HASH IS and INDEX option were specified. Clusters can be hash or indexed, but not both.
Action:Decide on which type of cluster is to be created, check the syntax of the command, then retry the statement.
ORA-02465 inappropriate use of the HASH IS option

Cause:The HASH IS option is valid only for clusters.
Action:Check the syntax of the command, use the HASH IS option only for clusters, then retry the command.
ORA-02466 the SIZE option is not allowed to be altered for HASH CLUSTERS

Cause:An attempt was made to change the SIZE option of a hash cluster after the cluster was created.
Action:The SIZE option can be specified only when creating the hash cluster. Do not attempt to alter the SIZE of the cluster.
ORA-02467 column referenced in hash expression not present in cluster

Cause:A column referenced in a hash expression is not present in the cluster definition.
Action:Recreate the cluster and correct the error in the hash expression.
ORA-02468 constant or system variable wrongly specified in expression

Cause:A constant or system variable is specified in the hash expression.
Action:Recreate the cluster and correct the error in the hash expression.
ORA-02469 hash expression does not return an Oracle Number

Cause:The result of evaluating a hash expression is not an Oracle Number.
Action:Recreate the cluster and correct the error in the hash expression.
ORA-02470 TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression

Cause:TO_DATE, USERENV, and SYSDATE are not allowed in hash expressions.
Action:Recreate the cluster and correct the error in the hash expression.
ORA-02471 SYSDATE, UID, USER, ROWNUM, OR LEVEL incorrectly used in hash expression

Cause:SYSDATE, UID, USER, ROWNUM, OR LEVEL are not allowed in hash expression(s).
Action:Recreate the cluster and correct the error in the hash expression.
ORA-02472 PL/SQL functions not allowed in hash expressions

Cause:A PL/SQL function is used in a hash expression.
Action:Recreate the cluster and remove the PL/SQL function.
ORA-02473 error while evaluating the cluster's hash expressions

Cause:An error occurred while evaluating the cluster's hash expression.
Action:Correct the query and retry.
ORA-02474 fixed hash area extents used num exceeds maximum allowed num

Cause:The number of extents required for creating the fixed hash area exceeded the maximum number allowed.
Action:Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.

02476-02479: Parallel Direct Loader

ORA-02476 cannot create index due to parallel direct load on table

Cause:A parallel direct load is occurring to the specified table.
Action:Retry the statement after the load is complete.
ORA-02477 cannot perform parallel direct load on object "name"

Cause:A parallel direct load is not possible because an index is being created on the table.
Action:Retry the load after the index creation is complete.
ORA-02478 merge into base segment would overflow MAXEXTENTS limit

Cause:Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temporary and base segments.
Action:Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger.
ORA-02479 error while translating file name for parallel load

Cause:The specified name of the database file to load with data was invalid.
Action:Specify a valid database filename.

02480-02489: Trace Facility

ORA-02480 too many event classes specified for events

Cause:Illegal trace enable string.
Action:Enter a legal trace enable control string.
ORA-02481 too many id ranges specified for events

Cause:Illegal trace enable string.
Action:Enter a legal trace enable control string.
ORA-02482 specified an event class but gave no events

Cause:Illegal trace enable string.
Action:Enter a legal trace enable control string.
ORA-02483 illegal ID value specified for events

Cause:Illegal trace enable string.
Action:Enter a legal trace enable control string.
ORA-02485 low ID value is greater than high ID value

Cause:Bad file name given in TRACE_DEST INIT.ORA parameter.
Action:Specify a valid name in the TRACE_DEST INIT.ORA parameter.
ORA-02486 error in file name. Check trace_dest init.ora parm

Cause:Bad file name given in TRACE_DEST INIT.ORA parameter.
Action:Specify a valid name in the TRACE_DEST INIT.ORA parameter.
ORA-02487 error in writing file name name. Check trace_dest init.ora parm

Cause:Bad file name given in TRACE_DEST INIT.ORA parameter.
Action:Specify a valid name in the TRACE_DEST INIT.ORA parameter.
ORA-02489 trace_block_size (num) must be divisible by num

Cause:The INIT.ORA parameter TRACE_BLOCK_SIZE was incorrectly set.
Action:Change the init.ora parameter and restart.

02490-02499: Resizeable Datafiles

ORA-02490 missing required file size in RESIZE clause

Cause:No value was specified for the RESIZE clause.
Action:Use correct syntax.
ORA-02491 missing required keyword ON or OFF in AUTOEXTEND clause

Cause:The keyword ON or OFF was not specified for the AUTOEXTEND clause.
Action:Use correct syntax.
ORA-02492 missing required file block increment size in NEXT clause

Cause:No value was specified for the NEXT clause.
Action:Use correct syntax.
ORA-02493 invalid file increment size in NEXT clause

Cause:A non-integer value was used for the NEXT clause of the DATAFILE list.
Action:Use correct syntax.
ORA-02494 invalid or missing maximum file size in MAXSIZE clause

Cause:UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value.
Action:Use correct syntax.
ORA-02495 cannot resize file name, tablespace name is read only

Cause:An attempt was made to resize a data file in a tablespace that is read only.
Action:Change the tablespace to read/write and retry the resize operation.

02500-02699: CTOS

02700-02874: UNIX Two Task

02875-02899: IBM RS/6000

03000-03099: Features Not Implemented

ORA-03001 unimplemented feature

Cause:An attempt was made to use a feature that is not currently implemented.
Action:Do not attempt to use the feature at this time.
ORA-03002 operator not implemented

Cause:An attempt was made to use an operator that is not currently implemented.
Action:Do not attempt to use the operator at this time.
ORA-03007 obsolete feature

Cause:An attempt was made to use a feature that is no longer supported.
Action:No action required.
ORA-03008 parameter COMPATIBLE >= val needed for feature_name

Cause:An attempt was made to use a feature for a later Oracle version than the setting of the initialization parameter, COMPATIBLE.
Action:Set COMPATIBLE to the value in the message, or higher, and retry the command, but be aware that this will limit your downgrade options.

03100-03199: Two-Task Interface

ORA-03100 communication area cannot be allocated; insufficient memory

Cause:An attempt to allocate stack space for communication purposes failed. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03106 fatal two-task communication protocol error

Cause:The communication path between Oracle and the user task has stopped. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03107 oranet buffer underflow

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03108 oranet: Oracle does not support this interface version

Cause:The version of Oracle connected to via SQL*Net does not support this version of the SQL*Net protocol.
Action:Upgrade the older version of Oracle and try again.
ORA-03109 oranet buffer overflow

Cause:Data being transferred between the user program and Oracle overflowed the buffer space available. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03110 oranet: Oracle does not support this SQL version

Cause:The version of Oracle connected to via SQL*Net does not support the version of the SQL*Net protocol.
Action:Upgrade the older version of Oracle and try again.
ORA-03111 break received on communication channel

Cause:A break was processed on the communications channel, but was not properly handled by SQL*Net software. This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03112 a server linked as single-task cannot use SQL*Net

Cause:A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.
Action:Do not use SQL*Net connect strings in a single-task environment.

ORA-03113 end-of-file on communication channel

Cause:An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the SQL*Net, two task, software. This message could occur if the shadow two-task process associated with a SQL*Net connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.
Action:If this message occurs during a connection attempt, check the setup files for the appropriate SQL*Net driver and confirm SQL*Net software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.
ORA-03114 not connected to Oracle

Cause:A call to Oracle was attempted when no connection was established. Usually this happens because a user-written program has not logged on. It may also happen if communication trouble causes a disconnection.
Action:Try again. If the message recurs and the program is user-written, check the program.
ORA-03115 unsupported network datatype or representation

Cause:A user bind or define, or an Oracle function, is not supported by this heterogeneous SQL*Net connection.
Action:Upgrade the older version of Oracle and try again.
ORA-03116 invalid buffer length passed to a conversion routine

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03117 two-task save area overflow

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03118 two-task coroutine has invalid state

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03120 two-task conversion routine: integer overflow

Cause:An integer value in an internal Oracle structure overflowed when being sent or received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application.
Action:Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767.
ORA-03121 no interface driver connected - function not performed

Cause:This message occurs usually because the SQL*Net driver is not loaded into memory or there is a mismatch of the version of the driver. A user program linked with an obsolete library may also cause this message. Only programs provided by Oracle Corporation should use this interface.
Action:If the message occurred during use of a program provided by Oracle Corporation, contact customer support. If a user program caused the message, relink the program with current versions of the Oracle libraries.
ORA-03122 attempt to close Oracle-side window on user side

Cause:This is an internal error message not usually issued.
Action:Contact customer support.
ORA-03123 operation would block

Cause:The attempted operation cannot complete now.
Action:Retry the operation later.
ORA-03124 two-task internal error

Cause:Internal error.
Action:Contact customer support.
ORA-03125 client-server protocol violation

Cause:The application received a bad escape sequence from the server which may indicate a problem with the client application user code.
Action:Contact your customer support representative.
ORA-03126 network drive does not support non-blocking operations

Cause:A non-block operation was attempted and the network driver does not support non-block operations.
Action:Use the default blocking operations or use a driver supporting non-blocking operations.
ORA-03127 no new operations allowed until the active operation ends

Cause:An attempt was made to execute a new operation before the active, non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.
Action:Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched.

ORA-03128 connection is in blocking mode

Cause:The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode.
Action:If non-blocking mode is required, use appropriate OCI calls to change the mode.
ORA-03129 the next piece to be inserted is required

Cause:The application performed a piecewise bind on a column.
Action:Provide the next piece of this bind variable.

ORA-03130 the buffer for the next piece to be fetched is required

Cause:The application performed a piecewise define on the column.
Action:Provide the next buffer for the next piece to be retrieved.

ORA-03131 an invalid buffer was provided for the next piece

Cause:The application either provided the length of the buffer for the next piece to be zero or provided a null pointer.
Action:Verify if the buffer pointer for the next piece is null or if the length is zero.

03200-03289: Extent Allocation and Other Space Management Errors

ORA-03200 the segment type specification is invalid

Cause:The segment type is not TABLE, INDEX, or CLUSTER.
Action:Use a correct segment type.
ORA-03201 the group number specification is invalid

Cause:The freelist group number is either negative or larger than the number of freelist groups in the segment.
Action:Use a correct group number.
ORA-03202 the scan limit specification is invalid

Cause:The scan limit does not have a positive integer value greater than the number of freelist groups in the segment.
Action:Use a correct scan limit.
ORA-03203 concurrent update activity makes space analysis impossible

Cause:High volume of user updates interfere with the space analysis.
Action:Retry the command or lock the underlying objects.
ORA-03230 segment only contains num blocks of unused space above high water mark

Cause:An attempt was made to preserve too many blocks.
Action:Reduce the KEEP amount.
ORA-03231 the INITIAL extent may not be deallocated

Cause:An attempt was made to deallocate space in segment which was truncated prior to the 7.3 release.
Action:Increase the KEEP amount, or truncate the segment, and reissue the command.

ORA-03274 both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified

Cause:The DEALLOCATE option and the ALLOCATE option were specified in the same command.
Action:Choose one of the options or issue two separate commands.

ORA-03275 duplicate DEALLOCATE option specification

Cause:The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX was specified more than once.
Action:Specify the option at most once.

ORA-03276 duplicate ALLOCATE EXTENT option specification

Cause:The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.
Action:Specify the option at most once.
ORA-03277 invalid SIZE specified

Cause:The value specified for the SIZE option of the ALTER TABLE... ALLOCATE EXTENT statement must be a positive integer.
Action:Choose an appropriate integer value.
ORA-03278 duplicate option specified for ALLOCATE EXTENT

Cause:An option, datafile, SIZE, or INSTANCE, was specified more than once in the ALTER TABLE... ALLOCATE EXTENT statement.
Action:Specify each option at most once.
ORA-03279 invalid INSTANCE specified

Cause:The value specified for the INSTANCE option of the ALTER TABLE... ALLOCATE EXTENT statement is not valid.
Action:Choose an appropriate INSTANCE specification.
ORA-03280 invalid datafile filename specified

Cause:A character-string literal is expected but not found for the DATAFILE option of the ALTER TABLE... ALLOCATE EXTENT statement.
Action:Specify the filename using a character-string literal enclosed in single quotes. Query the data dictionary view DBA_DATA_FILES to find the correct names of the datafiles.
ORA-03281 invalid ALLOCATE EXTENT option

Cause:An option other than DATAFILE, SIZE, or INSTANCE was specified in the ALTER TABLE... ALLOCATE EXTENT statement.
Action:Remove the invalid option and retry the command.
ORA-03282 missing ALLOCATE EXTENT option

Cause:No ALLOCATE EXTENT options were specified inside the parentheses of the ALTER TABLE... ALLOCATE EXTENT statement.
Action:If no options are required, do not use parentheses. Otherwise, specify one or more of the following options within parentheses: datafile, SIZE, or INSTANCE.
ORA-03283 specified datafile name does not exist

Cause:The datafile specified for the DATAFILE option in the ALTER TABLE... ALLOCATE EXTENT statement does not exist.
Action:Retry the option with the correct filename for the database file. Query the data dictionary view DBA_DATA_FILES to find the correct names of the datafiles.
ORA-03284 specified datafile name is not a member of tablespace name

Cause:The datafile specified in the ALTER TABLE... ALLOCATE EXTENT statement does not belong to the tablespace in which the table resides.
Action:Retry the option with the correct datafile or the correct table. Query the data dictionary view DBA_DATA_FILES to find the correct names of the datafiles in that tablespace or query DBA_TABLES to find the correct table name.
ORA-03286 ALLOCATE EXTENT not valid for HASH CLUSTERS

Cause:The cluster cannot use the allocate extent option because it is a hash cluster.
Action:Do not use this command on a hash cluster.
ORA-03287 invalid FREELIST GROUP specified

Cause:The specified FREELIST GROUP number is invalid.
Action:Choose a number between 1 and the number of freelist groups for this object.
ORA-03288 both FREELIST GROUP and INSTANCE parameters may not be specified

Cause:Both FREELIST GROUP and INSTANCE were specified in clause.
Action:Remove one of the two parameters.

03290-03295: TRUNCATE Command

ORA-03290 invalid truncate command - missing CLUSTER or TABLE keyword

Cause:An invalid object specification was given for the TRUNCATE command.
Action:Check the syntax of the command and retry the operation specifying either TRUNCATE CLUSTER or TRUNCATE TABLE.
ORA-03291 invalid truncate option - missing STORAGE keyword

Cause:The STORAGE keyword was not specified with the DROP or REUSE options of the TRUNCATE command.
Action:Check the syntax of the command and retry the operation.
ORA-03292 table to be truncated is a member of a cluster

Cause:An attempt was made to truncate a table that is a member of a cluster.
Action:Either truncate the entire cluster or drop and re-create the individual table.
ORA-03293 cluster to be truncated is a HASH CLUSTER

Cause:An attempt was made to truncate a hash cluster. This is not permitted; only index clusters can be truncated.
Action:Drop and re-create the cluster instead of using the TRUNCATE command.

03296-03299: Resizeable Datafiles

ORA-03296 cannot resize datafile - file name not found

Cause:The specified datafile was not available for resizing.
Action:Ensure that the datafile name is valid and, if so, ensure that the files is accessible.

ORA-03297 file contains num blocks of data beyond requested RESIZE value

Cause:Some portion of the file in the region to be trimmed is currently in use by a database segment.
Action:Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed region.
ORA-03298 cannot shrink datafile - file name is under hot backup

Cause:An attempt was made to shrink a datafile while it was under hot backup. This is not allowed.
Action:Retry shrinking the file after the hot backup completes.

ORA-03299 cannot create dictionary table name

Cause:A dictionary table is created upon the first execution of the command ALTER DATABASE AUTOEXTEND ON for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace.
Action:See the accompanying messages and take appropriate action.

03300-03499: Meiko

03500-03699: Macintosh

03700-03999: AOS/VS

04000-04019: Command Parameters

ORA-04000 the sum of PCTUSED and PCTFREE cannot exceed 100

Cause:The sum of the PCTUSED and PCTFREE values specified for a cluster or table exceeds 100.
Action:Create the table or cluster specifying values for PCTUSED and PCTFREE. The sum of these values cannot exceed 100.
ORA-04001 sequence parameter str must be an integer

Cause:The specified sequence parameter was not an integer.
Action:Create the sequence, giving the specified parameter an integer value.
ORA-04002 INCREMENT must be a non-zero integer

Cause:A sequence increment was specified as zero.
Action:Specify the increment as a non-zero value.
ORA-04003 sequence parameter num exceeds the maximum size allowed num digits

Cause:The specified sequence parameter has too many digits.
Action:Specify the parameter with the allowed number of digits and try again.
ORA-04004 MINVALUE must be less than MAXVALUE

Cause:MINVALUE was specified to be greater than or equal to MAXVALUE.
Action:Specify a MINVALUE that is less than MAXVALUE and try again.
ORA-04005 INCREMENT must be less than MAXVALUE minus MINVALUE

Cause:INCREMENT was specified as equal to or greater than MAXVALUE minus MINVALUE. This is not permitted.
Action:Specify INCREMENT as less than MAXVALUE minus MINVALUE and try again.
ORA-04006 START WITH cannot be less than MINVALUE

Cause:The given starting value is less than MINVALUE.
Action:Check that the starting value is not less than MINVALUE and try again.
ORA-04007 MINVALUE cannot be made to exceed the current value

Cause:The given MINVALUE is greater than the current value.
Action:Check that MINVALUE is not greater than the current value and try again.
ORA-04008 START WITH cannot be more than MAXVALUE

Cause:The starting value is larger than MAXVALUE.
Action:Check that the starting value is less than MAXVALUE and try again.
ORA-04009 MAXVALUE cannot be made to be less than the current value

Cause:The current value exceeds the given MAXVALUE.
Action:Check that the new MAXVALUE is larger than the current value and try again.
ORA-04010 the number of values to CACHE must be greater than 1

Cause:The value specified in the CACHE clause of a CREATE SEQUENCE statement is 1. The default value is 20.
Action:Specify NOCACHE or a value greater than 1 and try again.
ORA-04011 sequence name must range between num and num

Cause:The value specified for one of the sequence parameters exceeds limits.
Action:Specify a parameter within these limits.

ORA-04012 object is not a sequence

Cause:The object specified cannot have sequence operations performed on it.
Action:Re-enter the statement, making sure to spell the sequence name correctly.
ORA-04013 number to CACHE must be less than one cycle

Cause:The number to CACHE specified in a CREATE SEQUENCE statement exceeds the number of values in a cycle.
Action:Enlarge the cycle or cache fewer values, and try again.
ORA-04014 descending sequences that CYCLE must specify MIN VALUE

Cause:A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.
Action:Re-create the sequence, specifying the value at which it is to begin.
ORA-04015 ascending sequences that CYCLE must specify MAX VALUE

Cause:A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.
Action:Recreate the sequence, specifying the value at which it is to begin.
ORA-04016 sequence name no longer exists

Cause:Sequence was dropped while processing its next value.
Action:Recreate the sequence

04020-04029: Library Object Locks

ORA-04020 deadlock detected while trying to lock object name

Cause:While trying to lock a library object, a deadlock is detected.
Action:Retry the operation later.
ORA-04021 time-out occurred while waiting to lock object name

Cause:While trying to lock a library object, a time-out occurred.
Action:Retry the operation later.
ORA-04028 cannot generate diana for object name

Cause:A lock conflict prevented the generation of diana for an object.
Action:Check the syntax. If no syntax errors are found, report this error to Oracle World Wide Support.

ORA-04029 error ORA-num occurred when querying name

Cause:The table or view being queried might be missing. Look up the ORA-num indicated in the message.
Action:Fix the error.

04030-04039: System Memory

ORA-04030 out of process memory when trying to allocate num bytes str,str

Cause:Operating system process private memory has been exhausted.
Action:See the database administrator or operating system administrator to increase process memory quota. There may be a bug in the application that causes excessive allocations of process memory space.
ORA-04031 unable to allocate num bytes of shared memory num, num, num

Cause:More shared memory is needed than was allocated in the operating system process. SGA private memory has been exhausted
Action:Either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value set for the SHARED_POOL_SIZE initialization parameter.

04040-04069: Stored Procedures

ORA-04041 package specification must be created first before creating package body

Cause:An attempt was made to create a package body before creating its package specification.
Action:Create the package specification before trying to create the package body.
ORA-04042 procedure, function, package, or package body does not exist

Cause:An attempt was made to access a procedure, function, package, or package body that does not exist.
Action:Ensure the name specified is correct.
ORA-04043 object name does not exist

Cause:An object name was specified that was not recognized by the system. There are several possible causes:

Action:Check the spelling of the renamed object and rerun the code. Valid names of tables, views, functions, and so forth can be listed by querying the data dictionary.
ORA-04044 procedure, function, or package is not allowed here

Cause:An attempt was made to specify a procedure, function, or package in an inappropriate place in a statement.
Action:Refer to Oracle7 Server SQL Reference for the correct placement of procedures, functions, and packages in statements.
ORA-04045 errors during recompilation/revalidation of name.name

Cause:Errors occurred during the implicit recompilation/revalidation of the object named in the message.

Action:More descriptive messages follow this one. Check the causes mentioned in the messages that follow and take the appropriate actions.
ORA-04046 results of compilation are too large to support

Cause:An attempt to compile and store a large stored procedure resulted in compilation data that is too large for the system to support or store.
Action:Reduce the size of the store procedure by splitting it into smaller stored procedures.
ORA-04050 invalid or missing procedure, function, or package name

Cause:The required procedure, function, or package name is invalid or missing.
Action:Specify a valid name.
ORA-04051 user name cannot use database link name

Cause:An attempt was made to access a non-existent database link, or a link not owned by the user logging in or PUBLIC, while attempting to access a remote object.
Action:Change the database link structure, so all indirect remote access requests are done from the same user originating the request or PUBLIC.
ORA-04052 error occurred when looking up remote object name

Cause:An error occurred looking up a remote object.
Action:Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle7 Server Administrator's Guide.
ORA-04053 error occurred when validating remote object name

Cause:An error occurred trying to validate a remote object.
Action:Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle7 Server Administrator's Guide.
ORA-04054 database link name does not exist

Cause:During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.
Action:Use a different database link or create the database link.
ORA-04055 package STANDARD@name is incompatible to local package STANDARD

Cause:An attempt was made to compile a remote procedure call, but the remote procedure was compiled using a package STANDARD that has a different time-stamp from the one of the local package STANDARD. Therefore, those package STANDARDs are incompatible with each other and PL/SQL packages, procedures, and functions compiled against the remote package STANDARD are also incompatible with those compiled against the local package STANDARD.
Action:Upgrade either the local database or the remote database, whichever is older, to the same version.
ORA-04060 insufficient privileges to execute name

Cause:An attempt was made to execute a stored procedure without sufficient privileges.
Action:Obtain the necessary privileges through direct grants of the privileges, not through roles.
ORA-04061 existing state of name has been invalidated

Cause:An attempt was made to resume the execution of a stored procedure using the existing state, which has become invalid or inconsistent because the stored procedure has been altered or dropped.
Action:Attempt the action again. This action should cause the existing state of all packages to be reinitialized.
ORA-04062 name of name has been changed

Cause:An attempt was made to execute a stored procedure to service a remote procedure call stub that specifies a timestamp or signature that is different from the current timestamp or signature of the procedure.
Action:Recompile the caller to obtain the new timestamp.

ORA-04063 name has errors

Cause:An attempt was made to execute a stored procedure that has errors. For stored procedures, the problem could be syntax or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table.
Action:Fix the errors and create referenced objects as necessary.
ORA-04064 not executed, invalidated name

Cause:An attempt was made to execute a stored procedure that has been invalidated.
Action:Recompile the procedure and its dependents.
ORA-04065 not executed, altered, or dropped name

Cause:An attempt was made to execute a stored procedure that has been altered or dropped.
Action:Recompile the procedure's dependents.
ORA-04066 non-executable object, name

Cause:An attempt was made to execute an object that is not a package, procedure, or function.
Action:Check that a correct name is used.
ORA-04067 not executed, name does not exist

Cause:An attempt was made to execute a package, procedure, or function that does not exist.
Action:Check the name in the command.
ORA-04068 existing state of packages has been discarded

Cause:An error occurred when attempting to execute a stored procedure.
Action:Refer to the accompanying messages and fix the error mentioned. Try the procedure again after proper reinitialization of any application's state.

04070-04099: Triggers

ORA-04070 invalid trigger name

Cause:An invalid trigger name was specified.
Action:Check that the trigger name is not a reserved keyword.
ORA-04071 missing BEFORE or AFTER keyword

Cause:The trigger statement is missing the BEFORE/AFTER clause.
Action:Specify either BEFORE or AFTER.
ORA-04072 invalid trigger type

Cause:An invalid trigger type was given.
Action:Specify either INSERT, UPDATE, or DELETE as the trigger type.
ORA-04073 column list not valid for this trigger type

Cause:A column list was specified for a trigger type other than UPDATE.
Action:Remove the column list from the trigger.
ORA-04074 invalid REFERENCING name

Cause:An invalid name was given in the REFERENCING clause.
Action:Check that the REFERENCING name is not a reserved word.
ORA-04075 invalid trigger action

Cause:A statement was given for the trigger action.
Action:Specify another trigger action that is not a statement.
ORA-04076 invalid NEW or OLD specification

Cause:An invalid NEW or OLD specification was given for a column.
Action:Respecify the column using a correct NEW or OLD specification.
ORA-04077 WHEN clause cannot be used with table level triggers

Cause:The WHEN clause can only be specified for row-level triggers.
Action:Remove the WHEN clause or specify it for each row.
ORA-04078 OLD and NEW values cannot be identical

Cause:The REFERENCING clause specifies identical values for NEW and OLD.
Action:Specify the REFERENCING clause again with a different value for either NEW or OLD.
ORA-04079 invalid trigger specification

Cause:The CREATE TRIGGER statement is invalid.
Action:Refer to Oracle7 Server SQL Reference for the correct syntax of the CREATE TRIGGER statement.
ORA-04080 trigger name does not exist

Cause:The trigger name specified is invalid, or the trigger does not exist.
Action:Check the trigger name.
ORA-04081 trigger name already exists

Cause:The trigger name or type already exists.
Action:Use a different trigger name or drop the trigger that is of the same type.
ORA-04082 NEW or OLD references not allowed in table level triggers

Cause:The trigger is accessing NEW or OLD values in a table trigger.
Action:Remove any new or old references.
ORA-04083 invalid trigger variable name

Cause:The variable referenced in the trigger body is invalid.
Action:See Oracle7 Server SQL Reference for valid trigger variable types.
ORA-04084 cannot change trigger NEW values in after row triggers

Cause:New trigger variables can only be changed in before-row triggers.
Action:Change trigger type or remove the variable reference.
ORA-04085 cannot change the value of an OLD reference variable

Cause:OLD values can only be read and not changed.
Action:Do not attempt to change an OLD variable.
ORA-04086 trigger description too long, move comments into triggering code

Cause:The trigger description is limited to 2000 characters, for dictionary storage reasons. The description does not include the text of the "when" clause or the text of the PL/SQL code executed for the trigger.
Action:If the trigger description contains a large comment, move that comment into the PL/SQL code for the trigger.
ORA-04087 cannot change the value of ROWID reference variable

Cause:ROWIDs can only be read and not changed.
Action:Do not attempt to change a ROWID value.
ORA-04088 error during execution of trigger name.name

Cause:A runtime error occurred during execution of a trigger.
Action:Check the triggers that were involved in the operation.
ORA-04089 cannot create triggers on objects owned by SYS

Cause:An attempt was made to create a trigger on an object owned by SYS.
Action:Do not create triggers on objects owned by SYS.
ORA-04090 name specifies same table, event and trigger time as name

Cause:The named trigger has a duplicate event and trigger time as another trigger.
Action:Combine both triggers into one trigger.
ORA-04091 table name is mutating, trigger/function may not see it

Cause:A trigger or a user-defined PL/SQL function that is referenced in the statement attempted to query or modify a table that was in the middle of being modified by the statement that fired the trigger.
Action:Rewrite the trigger or function so it does not read the table.
ORA-04092 cannot COMMIT or ROLLBACK in a trigger

Cause:A trigger attempted to COMMIT or ROLLBACK. This is not permitted.
Action:Rewrite the trigger so that COMMIT or ROLLBACK statements are not used.
ORA-04093 references to columns of type LONG are not allowed in triggers

Cause:A trigger attempted to reference a LONG column in the triggering table.
Action:Do not reference the LONG column.
ORA-04094 table name is constraining, trigger may not modify it

Cause:A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement.
Action:Rewrite the trigger so that it does not modify that table.
ORA-04095 trigger name already exists on another table, cannot replace

Cause:An attempt was made to replace a trigger that exists on another table.
Action:Re-create the trigger on the other table using the CREATE OR REPLACE TRIGGER statement.
ORA-04096 trigger name has a WHEN clause that is larger than 2K

Cause:A trigger's WHEN clause is limited to 2K for dictionary storage reasons.
Action:Use a smaller WHEN clause. Note, the trigger body could perform the same limiting action as the WHEN clause.
ORA-04097 DDL conflict while trying to drop or alter a trigger

Cause:An attempt was made to concurrently perform two DDL operations on a trigger or trigger table.
Action:Investigate the new state of the trigger and retry the DDL operation, if still appropriate.

ORA-04098 trigger name is invalid and failed re-validation

Cause:A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.
Action:The options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger.

ORA-04099 trigger name is valid but not stored in compiled form

Cause:A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.
Action:Execute the ALTER <triggername> COMPILE command to compile the trigger. The trigger will then be in stored form. Also, you may want to review that a proper upgrade was done.

04100-04499: MVS

04500-04899: CMS

04900-04929: ICL DRS6000

05000-05899: Original Equipment Manufacturers

05900-05999: Wang

06000-06429: SQL*Net

06430-06499: NCR System 3000

06500-06599: PL/SQL

ORA-06500 PL/SQL: storage error

Cause:This is a rare internal error message. Memory has been exhausted or corrupted.
Action:Contact customer support.
ORA-06501 PL/SQL: internal error num, arguments [num], [num], [num], [num], [num], [num]

Cause:This is an internal error message. An error has been detected in a PL/SQL program.
Action:Contact customer support.
ORA-06502 PL/SQL: numeric or value error

Cause:An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).
Action:Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.
ORA-06503 PL/SQL: Function returned without value

Cause:A call to a PL/SQL function completed, but no RETURN statement was executed.
Action:Rewrite the PL/SQL function, making sure that it always returns a value of a proper type.
ORA-06504 PL/SQL: Return types of Result Set variables or query do not match

Cause:Number and/or types of columns in a query do not match the declared return type of a Result Set variable, or the declared types of two Result Set variables do not match.
Action:Change the program statement or declaration. Identify the query to which the variable, during execution, actually refers.
ORA-06508 PL/SQL: could not find program unit being called

Cause:An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.
Action:Check that all referenced programs, including their package bodies, exist and are compatible.
ORA-06509 PL/SQL: ICD vector missing for this package

Cause:This indicates a version clash between some package distributed with an Oracle product and the product executable.
Action:Contact customer support.
ORA-06510 PL/SQL: unhandled user-defined exception str

Cause:A user-defined exception was raised by PL/SQL code, but not handled.
Action:Fix the problem causing the exception or write an exception handler for this condition. It may be necessary to contact the application or database administrator.
ORA-06511 PL/SQL: cursor already open

Cause:An attempt was made to open a cursor that was already open.
Action:Close the cursor before attempting to reopen it.
ORA-06512 at str line num

Cause:This is usually the last of a message stack and indicates where a problem occurred in the PL/SQL code.
Action:Fix the problem causing the exception or write an exception handler for this condition. It may be necessary to contact the application or database administrator.
ORA-06513 PL/SQL: index for PL/SQL table out of range for host language array

Cause:An attempt was made to copy a PL/SQL table to a host language array, but an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, and so on. If a table entry was not assigned, then the corresponding element in the host language array is set to NULL.
Action:Increase the size of the host language arrays or decrease the size of the PL/SQL table. Also make sure that you do not use index values less than 1.
ORA-06514 PL/SQL: The remote call cannot be handled by the server

Cause:The remote call had parameters that were cursor variables. This cannot be handled by stored procedures on your server.
Action:Avoid using cursor variables as parameters for stored procedures on this server or upgrade your server to a version that supports this.

ORA-06540 PL/SQL compilation error

Cause:A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.
Action:See accompanying PLS-nnnnn error messages.
ORA-06541 PL/SQL: compilation error - compilation aborted

Cause:A PL/SQL compilation error occurred and the compilation was aborted. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.
Action:See accompanying PLS-nnnnn error messages.
ORA-06544 PL/SQL: internal error, arguments:arg1, arg2, arg3, arg4, arg5, arg6, arg7, arg8

Cause:A PL/SQL internal error occurred.
Action:Report this as a bug; the first argument is the internal error number.
ORA-06550 line num, column num: str

Cause:A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action:Refer to the following PL/SQL messages for more information about the error.
ORA-06554 package DBMS_STANDARD must be created before using PL/SQL

Cause:The data dictionary script required by PL/SQL has not yet been run.
Action:See the Oracle7 Server Administrator's Guide and your Oracle7 operating system-specific documentation for more information.
ORA-06555 this name is currently reserved for use by user SYS

Cause:An attempt was made to create a user-owned package named STANDARD, DBMS_STANDARD, or DBMS_OUTPUT. This is not allowed.
Action:Choose another name for the package.
ORA-06556 the pipe is empty, cannot fulfill the UNPACK_MESSAGE request

Cause:There are no more items in the pipe.
Action:Check that the sender and receiver agree on the number and types of items placed on the pipe.
ORA-06557 null values are not allowed for any parameters to pipe ICD's

Cause:Internal error from the DBMS_PIPE package.
Action:Contact customer support.
ORA-06558 buffer in DBMS_PIPE package is full. No more items allowed

Cause:The pipe buffer size has been exceeded.
ORA-06559 wrong datatype requested, type, actual datatype is type

Cause:The sender put a different datatype on the pipe than that being requested, package DBMS_PIPE. The recognized datatypes and the corresponding numbers are: 6 - number, 9 - char, 12 - date.
Action:Check that the sender and receiver agree on the number and types of items placed on the pipe.
ORA-06562 type of OUT argument must match type of column or bind variable

Cause:An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL. However, the type of the given out argument was different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN, for defining a column, or BIND_VARIABLE, for binding a bind variable, of package DBMS_SQL.
Action:Pass in an OUT argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable.
ORA-06560 pos, num, is negative or larger than the buffer size, num

Cause:Internal error from the DBMS_PIPE package.
Action:Contact customer support.
ORA-06563 top level procedure or function specified, cannot have subparts

Cause:The name to be resolved was specified with three parts, a.b.c, but the a.b part resolves to a top level procedure or function that does not have nested procedures. This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure.
Action:Specify a procedure or function within a package or a top level procedure or function.
ORA-06564 object name does not exist

Cause:The named object could not be found. Either it does not exist or you do not have permission to access it.
Action:Create the object or get permission to access it.
ORA-06565 cannot execute name from within stored procedure

Cause:The named procedure cannot be executed from within a stored procedure, function, or package. This function can only be used from PL/SQL anonymous blocks.
Action:Remove the procedure from the calling stored procedure.
ORA-06566 invalid number of rows specified

Cause:An invalid number of rows was specified in a call to the procedures DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows.
Action:Specify a number that matches the number for previously defined columns.
ORA-06567 invalid number of values specified

Cause:An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. For a given parsed statement in a given cursor, the same number of values must be bound for all bind variables, so all the calls to BIND_VARIABLE must specify the same number of values.
Action:Make sure that the same number of values are given for each of the bind variables.
ORA-06568 obsolete ICD procedure called

Cause:An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of Oracle.
Action:Ensure that all PL/SQL packages are upgraded to the latest release of Oracle by following the upgrade instructions noted in the README document or by running the CATPROC.SQL script.
ORA-06570 shared pool object does not exist, cannot be pinned

Cause:The specified shared pool shared cursor could not be found. Therefore, it cannot be pinned.
Action:Make sure that a correct shared cursor name is given. Names are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8-digit hex number from the 'address' column of V$SQLAREA, and the D's are a 1- to 10-digit decimal number with an optional leading sign from the 'hash_value' column.
ORA-06571 function name does not guarantee not to update database

Cause:There are two possible causes for this message:

Action:If the referenced function is a packaged PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma.
ORA-06572 function name has out arguments

Cause:A SQL statement references either a packaged or a stand-alone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.
Action:Recreate the PL/SQL function without the OUT parameter in the argument list.
ORA-06573 function name modifies package state, cannot be used here

Cause:There are two possible causes for this message:

Action:If the function is a packaged PL/SQL function: recreate the function and include a pragma containing the 'Write no Package State' (WNPS).
ORA-06574 function name references package state, cannot execute remotely

Cause:There are two possible causes for this message:

Action:If the function is a packaged function: Recreate the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments.
ORA-06575 function name is in an invalid state

Cause:A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.
Action:Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.
ORA-06580 Hash Join ran out of memory while keeping large rows in memory

Cause:Hash Join reserved 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.
Action:Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased.

06581-06591: European OEM Ports

06600-06699: SQL*Net

06700-06899: SQL*Net TLI

06900-06939: CMX

06950-06999: SQL*Net AppleTalk

07000-07099: SQL*Connect for DB2

07100-07199: SQL*Connect for IMS

07200-07499: UNIX

07500-07999: VAX/VMS

08000-08174: Accessing Data

ORA-08000 maximum number of session sequence lists exceeded

Cause:This is an internal error message not normally issued.
Action:Contact customer support.
ORA-08001 maximum number of sequences per session exceeded

Cause:An operation requested a resource that was unavailable. The maximum number of user sequences per session is specified by the initialization parameter DC_SEQUENCES. When this maximum is reached, no more requests are processed.
Action:Try the operation again in a few minutes. If this error occurs often, shut down Oracle, increase the DC_SEQUENCES parameter in the initialization parameter file, and restart Oracle.
ORA-08002 name.CURRVAL is not yet defined in this session

Cause:Sequence CURRVAL was selected before sequence NEXTVAL was referenced.
Action:Select NEXTVAL from the sequence before selecting CURRVAL.
ORA-08003 sequence name.NEXTVAL exceeds internal limits

Cause:The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal representation size.
Action:Alter or recreate the sequence number with legal limits.
ORA-08004 name.NEXTVAL str [MIN][MAX]VALUE and cannot be instantiated

Cause:The requested value of NEXTVAL is greater than MAXVALUE or less than MINVALUE.
Action:Alter the sequence so that a new value can be requested and try again.
ORA-08005 specified row does not exist

Cause:A row with the given ROWID does not exist in any of the specified tables.
Action:Check the query for a misspelled ROWID or table name and try again.
ORA-08006 specified row no longer exists

Cause:The row has been deleted by another user since the operation began.
Action:No action required.
ORA-08008 another instance is mounted with USE_ROW_ENQUEUES = num

Cause:The shared instance being started does not have the same value for the USE_ROW_ENQUEUES initialization parameter as already-running instances.
Action:Make sure all instances' initialization parameter files specify the same value for the USE_ROW_ENQUEUES parameter and try again.
ORA-08100 index is not valid - see trace file for diagnostics

Cause:There is an error in the index validated by VALIDATE INDEX.
Action:Check the relevant trace file. If the problem is not resolvable, contact customer support.
ORA-08101 index key does not exist root dba num, dba num num

Cause:The system detected a possible inconsistency in an index. This is an internal error message that is not normally issued.
Action:Send the trace file to customer support, along with a description of the circumstances that produced the error. Customer support will need the numbers given in the message.
ORA-08102 index key not found, obj# num, dba num num

Cause:The system detected a possible inconsistency in an index. This is an internal error message that is not normally issued.
Action:Send the trace file to customer support, along with a description of the circumstances that produced the error. Customer support will need the numbers given in the message.
ORA-08103 object no longer exists

Cause:The object has been deleted by another user since the operation began.
Action:Remove references to the object.

08175-08190: Discrete Transactions

ORA-08175 discrete transaction restriction violated name

Cause:An attempt was made to perform an action that is not currently supported in a discrete transaction.
Action:Rollback the transaction and retry it as a normal transaction.
ORA-08176 cannot continue consistent read for the table/index - no undo records

Cause:Oracle encountered an operation that does not generate undo records. For example, the operation might have been an attempt to create an index by performing a direct load or executing a discrete mode transaction.
Action:Retry the operation with a different snapshot time. If using an index, retry the operation without using the index.
ORA-08177 cannot serialize access for this transaction

Cause:Oracle encountered data changed by an operation that occurred after the start of this serializable transaction.
Action:In read/write transactions, retry the intended operation or transaction.

08200-08399: nCUBE

08401-08499: PL/SQL Utility Packages for Procedural Gateway

ORA-08401 invalid compiler name: name

Cause:An invalid compiler name was passed to a UTL_PG conversion routine.
Action:Correct the compiler name parameter in the PL/SQL code that called the conversion routine.
ORA-08412 error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message

Cause:The WMSGBSIZ is the maximum size for warning message block, it is recommended to be 1024 bytes to 8 kbytes.
Action:Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the size of WMSGBLK.
ORA-08413 invalid compiler type in FORMAT parameter at name

Cause:An invalid compiler type was defined in the format control block. The format control block is invalid.
Action:Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.
ORA-08414 error encountered in name

Cause:The function <routine> returned an error. Where <routine> may be: RAW_TO_NUMBER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT
Action:This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.
ORA-08429 raw data has invalid digit in display type data

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit.
Action:Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08430 raw data missing leading sign

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action:Correct the input raw data or the mask options so that they match.
ORA-08431 raw data missing zero as defined in picture

Cause:The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero.
Action:Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08432 raw data has invalid floating point data

Cause:The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.
Action:Correct the input raw data.
ORA-08433 invalid picture type in convert raw to number

Cause:The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action:Correct the picture mask parameter.
ORA-08434 raw data has invalid trailing sign

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign.
Action:Correct the input raw data or the mask options so that they match.
ORA-08435 PICTURE MASK missing the leading sign when SIGN IS LEADING specified

Cause:The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action:Correct the input raw data or the mask options so that they match.
ORA-08436 raw data has invalid sign digit

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign.
Action:Correct the input raw data or the picture mask so that they match.
ORA-08437 invalid picture type in picture mask

Cause:The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action:Correct the picture mask parameter.
ORA-08440 raw buffer is too short to hold converted data

Cause:The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask.
Action:Increase the raw buffer size to the size necessary to hold the entire result of the conversion.
ORA-08441 closed parenthesis missing in picture mask

Cause:A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
Action:Correct the picture mask.
ORA-08443 syntax error in BLANK WHEN ZERO clause in mask options

Cause:A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO, BLANK ZEROS, BLANK ZEROES, BLANK WHEN ZERO, BLANK WHEN ZEROS, and BLANK WHEN ZEROES.
Action:Correct the mask options parameter.
ORA-08444 syntax error in JUSTIFIED clause in mask options

Cause:A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST, JUST RIGHT, JUSTIFIED, and JUSTIFIED RIGHT.
Action:Correct the mask options parameter.
ORA-08445 syntax error in SIGN clause in mask options

Cause:A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN, LEADING SIGN, LEADING SEPARATE SIGN, LEADING SEPARATE CHARACTER SIGN, TRAILING SIGN, TRAILING SEPARATE SIGN, TRAILING SEPARATE CHARACTER SIGN IS LEADING, SIGN IS LEADING, SEPARATE SIGN IS LEADING, SEPARATE CHARACTER SIGN IS TRAILING, SIGN IS TRAILING, SEPARATE SIGN IS TRAILING, and SEPARATE CHARACTER.
Action:Correct the mask options parameter.
ORA-08446 syntax error in SYNCHRONIZED clause in mask options

Cause:A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC, SYNC LEFT, SYNC RIGHT, SYNCHRONIZED, SYNCHRONIZED LEFT, and SYNCHRONIZED RIGHT.
Action:Correct the mask options parameter.
ORA-08447 syntax error in USAGE clause in mask options

Cause:A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE, DISPLAY USAGE, COMP USAGE, COMP-3 USAGE, COMP-4 USAGE, COMPUTATIONAL USAGE, COMPUTATIONAL-3 USAGE, COMPUTATIONAL-4 USAGE IS, DISPLAY USAGE IS, COMP USAGE IS, COMP-3 USAGE IS, COMP-4 USAGE IS, COMPUTATIONAL USAGE IS, COMPUTATIONAL-3 USAGE IS, and COMPUTATIONAL-4.
Action:Correct the mask options parameter.
ORA-08448 syntax error in DECIMAL-POINT environment clause

Cause:A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA.
Action:Correct the environment clause parameter.
ORA-08449 invalid numeric symbol found in picture mask

Cause:An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine.
Action:Correct the picture mask parameter.
ORA-08450 invalid specification of CR in picture mask

Cause:The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask.
Action:Correct the picture mask parameter.
ORA-08451 invalid specification of DB in picture mask

Cause:The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask.
Action:Correct the picture mask parameter.
ORA-08452 specification of E in picture mask is unsupported

Cause:The floating point exponent symbol "E" was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines.
Action:Correct the picture mask parameter, and the data, if necessary.
ORA-08453 more than one V symbol specified in picture mask

Cause:The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator "V". Only one decimal point indicator is allowed in the picture mask.
Action:Correct the picture mask parameter.
ORA-08454 more than one S symbol specified in picture mask

Cause:The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator "S". Only one operational sign indicator is allowed in the picture mask.
Action:Correct the picture mask parameter.
ORA-08455 syntax error in CURRENCY SIGN environment clause

Cause:A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x, where x is a valid currency sign.
Action:Correct the environment clause parameter.
ORA-08456 no sign in picture mask but SIGN clause in mask options

Cause:The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol, "S", "+", or "-", but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause.
Action:Correct the picture mask parameter or the mask options parameter.
ORA-08457 syntax error in SEPARATE CHARACTER option of SIGN clause

Cause:A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE and SEPARATE CHARACTER.
Action:Correct the mask options parameter.
ORA-08458 invalid format parameter

Cause:The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.
Action:Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.
ORA-08459 invalid format parameter length

Cause:The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length.
Action:Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.
ORA-08460 invalid environment clause in environment parameter

Cause:The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.
Action:Correct the environment parameter.
ORA-08462 raw buffer contains invalid decimal data

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action:Correct the input data.
ORA-08463 overflow converting decimal number to Oracle number

Cause:The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number.
Action:Be sure that the input decimal number is valid, and be sure that the output variable is large enough to hold the Oracle number value.
ORA-08464 input raw decimal data contains more than 42 digits

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number.
Action:Correct the raw input buffer.
ORA-08465 input mask contains more than 32 characters

Cause:The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
Action:Correct the mask input buffer.
ORA-08466 raw buffer length num is too short for name

Cause:The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than num bytes long, but the picture mask parameter specified that num bytes of input data were to be converted.
Action:Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08467 error converting Oracle number to num

Cause:An error occurred when converting an Oracle number to a COBOL <type> of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format.
Action:Correct the call to the conversion routine. The input must be a valid Oracle number variable.
ORA-08468 mask option name is not supported

Cause:The mask option <clause> was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The <clause> can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER
Action:Remove the <clause> from the mask options parameter in the PL/SQL call to UTL_PG.
ORA-08498 Warning: picture mask name overrides picture mask option USAGE IS name to USAGE IS DISPLAY

Cause:Picture mask option is overridden by Picture mask
Action:no action need, just for information.
ORA-08499 Warning: picture mask options name ignored by UTL_PG

Cause:Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines.
Action:This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine.

08500-09099: SQL*Connect

09100-09199: Oracle Gateways

ORA-09100 target system returned following message:

Cause:A target system being accessed by an Oracle gateway returned an error that could not be handled by the gateway server. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09101 target system communication error

Cause:The gateway encountered an error when communicating with the target system. This message will generally be followed by a second message generated either by the target system or the gateway.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09102 gateway internal communication error

Cause:The Oracle gateway encountered an internal error during communication with a module that is part of the gateway.
Action:Contact customer support.
ORA-09103 gateway internal protocol error

Cause:The Oracle gateway encountered an internal error during communication with an internal module.
Action:Contact customer support.
ORA-09104 gateway internal cross-communication error

Cause:The Oracle gateway encountered an internal error during communication with a module that is part of the gateway but located in a different process.
Action:Contact customer support.
ORA-09105 failed to acquire storage space in target system

Cause:For an Oracle gateway, the amount of storage available within the target system was reached. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09106 target system could not obtain IO resource

Cause:The target system was unable to open a file, data set, or other resource needed to perform the I/O. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09107 definition of a target system object may have changed

Cause:In an Oracle transparent gateway, an attempt was made to execute a SQL statement whose definition in the GDDL source may be out of date. The timestamp in the gateway data dictionary is different from the timestamp in the target system.
Action:Use the Transparent Gateway Administrator utility to replace the table using the revised GDDL source.
ORA-09108 invalid record in target system

Cause:The Oracle gateway or the target system noticed that the record is not valid according to its definition. This message is followed by a second message generated by the gateway or the target system depending on the error.
Action:See the gateway documentation or the documentation for the target system for an explanation of the second error message.
ORA-09109 view "view_name" cannot be used in a subquery

Cause:The view definition contains a set operator, which makes it impossible to use that view definition in a subquery. This message can occur only in SQL-based gateways.
Action:Do not use the view in a subquery.
ORA-09110 view "view_name" defines operation not supported on the target system

Cause:In a user-developed gateway, the implementor defined a view that defines an Oracle table in terms of other data source tables, and this definition contains SQL elements not supported by that system.
Action:Contact the implementor to correct the view definition error.
ORA-09111 data manipulation operation not legal on this object

Cause:In an Oracle transparent gateway, the target system rejected an insert, delete, or update operation. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09112 target system check constraint violated

Cause:The values being inserted or updated do not satisfy the check constraint in the transparent gateway. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09113 target system integrity constraint violated

Cause:The values being inserted, updated, or deleted do not satisfy the integrity constraints defined in the target system in a transparent gateway. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09114 target system is out of memory

Cause:A target system being accessed by an Oracle gateway ran out of memory. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09115 target system has timed out

Cause:A target system being accessed by an Oracle gateway timed out. This error occurs when system resource usage is too high for the request to be served in a reasonable time or when a deadlock, or some other wait condition, occurred in the target system. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09116 definition of target system data object is inconsistent

Cause:In an Oracle transparent gateway, The target system was unable to perform the initial operations necessary to access the mapped table. The GDDL source specifies certain fields or options that are not supported for this gateway configuration.
Action:Correct the GDDL source and issue the Transparent Gateway Administrator command to CREATE OR REPLACE or DROP the table.
ORA-09117 bind-value cannot be translated into SQL text

Cause:For the SQL-based transparent gateway, the target system does not support binds, or binds are disabled using the RESOLVE_BINDS gateway initialization parameter.
Action:Enable binds or do not bind using datatypes not supported in SQL text.
ORA-09118 maximum number of savepoints exceeded

Cause:For the SQL-based transparent gateway, the target system was unable to set the savepoint because the maximum number of active savepoints was reached.
Action:Re-organize the transaction so that this limit is not reached or increase the maximum in the target system if that is possible.
ORA-09119 initialization file contains error

Cause:An Oracle gateway server encountered an error in the gateway server initialization file. This message is followed by a second message. If the second message did not follow, it can be found in the gateway log file.
Action:Refer to the second message to fix the initialization file.
ORA-09120 gateway has timed out access to target system

Cause:The Oracle Gateway request was not serviced within the specified time by the target system.
Action:See your Oracle7 operating system-specific documentation for an explanation of when this error can occur.
ORA-09121 fetch exceeds maximum number of records defined for table

Cause:The transparent gateway detected that a query will retrieve more rows than the maximum defined in the GDDL for mapped table.
Action:See your Oracle7 operating system-specific documentation for an explanation of when this error can occur.
ORA-09122 access to object "name" denied

Cause:An Oracle transparent gateway denied access to the specified object.
Action:Log in as a user with access to the object or change the access permission of the object.
ORA-09123 ROWID not found in gateway rowid cache

Cause:For the transparent gateway, the ROWID cache holds no entry that corresponds to the specified ROWID. Possibly, the ROWID entry was overwritten in the gateway ROWID cache.
Cause:Increase the size of the gateway ROWID cache by setting the value of the ROWID_CACHE_SIZE gateway initialization parameter to a higher value and restart the gateway server.
ORA-09124 in name argument name: Index out of range

Cause:The transparent gateway server detected that the index for a mapped table is bigger than allowed by the definition in the GDDL source.
Action:Modify the query or the GDDL source so that the index is in range.

09200-09499: DOS, OS/2, and Novell

09500-09699: MPE/XL

09700-09999: UNIX

10000-10999: Internal

11000-11999: SQL*Net MVS

12000-12019: Table Snapshots

ORA-12000 a snapshot log already exists on table name

Cause:An attempt was made to create a snapshot log on a table that already has a snapshot log. Each master table can have only one snapshot log.
Action:All snapshots on a table can use the same snapshot log for that table. To make changes to the existing log, use the ALTER SNAPSHOT LOG command or drop the snapshot log and create it again.
ORA-12001 cannot create log: table name already has a trigger

Cause:An attempt was made to create a snapshot log on a table when the table already had an AFTER ROW trigger. Snapshot logs are filled by an AFTER ROW trigger on the master table, so the trigger cannot be created.
Action:If it is necessary to create a snapshot log, drop the current trigger on the master table.
ORA-12002 there is no snapshot log on table name

Cause:An attempt was made to drop a snapshot that does not exist.
Action:Check spelling, syntax, and use an existing snapshot name.
ORA-12003 snapshot name does not exist

Cause:An attempt was made to reference a snapshot that does not exist.
Action:Check the name of the snapshot in the statement for typing errors. Retry the statement with an existing snapshot name.
ORA-12004 REFRESH FAST cannot be used

Cause:An attempt to fast refresh a snapshot was made when the master table for the snapshot has no snapshot log, or the snapshot log cannot be used.
Action:To REFRESH FAST, first create a snapshot log on the master table. Otherwise, use the REFRESH COMPLETE option of the ALTER SNAPSHOT command. If these options are omitted, Oracle decides the appropriate method for refreshing.

ORA-12005 may not schedule automatic refresh for times in the past

Cause:An attempt was made to schedule an automated snapshot refresh for a time in the past.
Action:Choose a time in the future for the automated snapshot refresh.
ORA-12006 a snapshot with the same user.name already exists

Cause:An attempt was made to create a snapshot with the name of an existing snapshot.
Action:Create the snapshot using a different name or drop the existing snapshot.
ORA-12007 snapshot reuse parameters are inconsistent

Cause:During Import or Export, the CREATE SNAPSHOT or CREATE SNAPSHOT LOG.. REUSE command was given inconsistent parameters immediately after the REUSE.
Action:Other messages will accompany this message. Examine the other messages for a more complete description of the problem.
ORA-12008 error in snapshot refresh path

Cause:Some problem is preventing the snapshot from reading the view on the master table. A number of events could cause this problem, among them the following:

Action:Other messages will accompany this message. Examine the other messages for a more complete description of the problem. The most likely solution to the problem will be to recreate the snapshot.
ORA-12009 snapshots may not contain long columns

Cause:An attempt was made to create a snapshot with a long column.
Action:Do not attempt to create snapshot logs with long columns.
ORA-12010 cannot create snapshot log on table owned by SYS

Cause:CREATE SNAPSHOT LOG attempts to create a trigger on the table, but triggers cannot be created on SYS tables.
Action:Do not create snapshot logs on SYS tables.
ORA-12011 execution of num jobs failed

Cause:Some kind of error was caught in DBMS_IJOB.RUN. One or more jobs that were due to be run produced errors that they could not handle.
Action:Look at the alert log for details on which jobs failed and why.
ORA-12012 error on auto execute of job num

Cause:Some kind of error was caught while doing an automatic execute of a job.
Action:Look at the accompanying errors for details on why the execute failed.
ORA-12013 updatable snapshots must be simple enough to do fast refresh

Cause:The updatable snapshot query statement is specified with a join, subquery, union, CONNECT BY, ORDER BY, or GROUP BY.
Cause:Specify a simpler snapshot statement. If a join is needed, create multiple simple snapshots, and then create a view on top of the multiple snapshots.

12100-12299: SQL*Net

12300-12399: Multiple Mount

ORA-12315 database link type is invalid for the ALTER DATABASE statement

Cause:The database link name specified on the ALTER DATABASE statement is not an ROM: link. Specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.
Action:Retry the ALTER DATABASE statement using a valid ROM: link to the database to be mounted or opened. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted Oracle7 Server Administrator's Guide for more information about creating database links using the ROM: link type.
ORA-12316 syntax error in database link's connect string

Cause:The connect string in the CREATE DATABASE LINK statement has a syntactical error.
Action:Drop the database link and recreate it using valid syntax. See Oracle7 Server SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement.
ORA-12317 logon to database (link name name) denied

Cause:Any of the following:

Action:Enter the correct information.
ORA-12318 database (link name name) is already mounted

Cause:An attempt was made to mount a secondary database already mounted by the instance.
Action:No additional action is required to mount the database. To establish access, use the ALTER DATABASE command to open the database.
ORA-12319 database (link name name) is already open

Cause:An attempt was made to open a secondary database that is already open.
Action:No additional action is required to establish access.
ORA-12321 database (link name name) is not open and AUTO_MOUNTING=FALSE

Cause:The instance attempted to mount the secondary database, but it is not open and it is not enabled for automatic mounting.
Action:Manually mount and open the secondary database using the ALTER DATABASE command with the OPEN and MOUNT options. To allow the instance to mount and open secondary databases automatically, set the AUTO_MOUNTING parameter in the initialization parameter file to TRUE.
ORA-12322 unable to mount database (link name name)

Cause:This message should be accompanied by additional messages that indicate the cause of the problem.
Action:Follow the steps outlined in the accompanying messages to resolve the problem.
ORA-12323 unable to open database (link name name)

Cause:This message should be accompanied by additional messages that indicate the cause of the problem.
Action:Follow the steps outlined in the accompanying messages to resolve the problem.
ORA-12324 cannot use the ROM: link type on a private database link

Cause:You can only specify the ROM: link type on a public, not on a private, database link.
Action:If there is an existing public database link to the secondary database, use that link. If not, and public access to the secondary database is desired, create a public database link to the secondary database using the CREATE DATABASE LINK command.
ORA-12326 database name is closing immediately; no operations are permitted

Cause:The operation attempted was terminated because the database is closing.
Action:Wait until the database reopens or contact the database administrator.
ORA-12329 database name is closed; no operations are permitted

Cause:The operation attempted was terminated because the database is closing.
Action:Wait until the database reopens or contact the database administrator.
ORA-12333 database (link name name) is not mounted

Cause:An attempt was made to open a database that is not mounted.
Action:Mount the database with the ALTER DATABASE command, then reattempt to open the database.
ORA-12334 database (link name name) is still open

Cause:An attempt was made to dismount a database that is still open.
Action:Close the database with the ALTER DATABASE command, then reattempt to dismount the database.
ORA-12335 database (link name name) is not open

Cause:An attempt was made to close a database that is not open.
Action:The database is closed; proceed with dismounting it.
ORA-12341 maximum number of open mounts exceeded

Cause:The number specified on the OPEN_MOUNTS parameter in the initialization parameter file exceeds 255, which is the maximum allowed.
Action:Change the value of this initialization parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.
ORA-12342 open mounts exceeds limit set on the OPEN_MOUNTS parameter

Cause:The number of currently open mounts exceeds the value specified in the OPEN_MOUNTS initialization parameter.
Action:Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.
ORA-12345 user name lacks CREATE SESSION privilege in database (link name name)

Cause:There are two causes of this message:

Action:The action you take depends upon the cause of the message:
ORA-12350 database link being dropped is still mounted

Cause:An attempt was made to drop a ROM: database link while it was still mounted and/or opened.
Action:Close and dismount the database. Then retry the drop statement.
ORA-12351 cannot create view using a remote object which has a remote object reference

Cause:An attempt was made to create a view that references a remote object that, in turn, references an object on another database. Because the view that you tried to create references a remote object, that object cannot reference an object on another database.
Action:Choose a different object to reference in your view or change the remote object so that it does not reference another database.
ORA-12352 object name is invalid

Cause:An attempt was made to reference, or compile against, an object in a secondary database. However, the object is invalid because it is in a secondary database. Therefore, the system cannot validate or recompile it.
Action:Recompile the invalid object in the secondary database.
ORA-12353 secondary stored object cannot reference remote object

Cause:You tried either to select from a remote view or execute a remote procedure that references an object on another database. Because the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.
Action:Choose a different object to reference or change the remote view or procedure so that it does not reference another database.
ORA-12354 secondary object being dropped

Cause:You tried to access an object, for example, a table or view, on a secondary database that was being dropped.
Action:Repeat the operation. If you receive the message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact customer support.

12400-12499: Trusted Oracle

ORA-12400 DBLOW is not a valid operating system label

Cause:The operating system label corresponding to DBLOW has become invalid due to a change in operating system label definitions.
Action:Use the operating system facilities to restore the definition of this label, or change the value of DBLOW to a valid label. To change the value of DBLOW, you must mount the database and switch to OSMAC mode.
ORA-12401 DBHIGH is not a valid operating system label

Cause:The operating system label corresponding to DBHIGH has become invalid due to a change in operating system label definitions.
Action:Use the operating system facilities to restore the definition of this label, or change the value of DBHIGH to a valid label. To change the value of DBHIGH, you must mount the database and switch to OSMAC mode.
ORA-12402 file: str

Cause:Reporting filename for detail of another message.
Action:Correct the underlying problems mentioned in the other messages.
ORA-12403 file label name must be equal to DBHIGH name

Cause:A datafile was found to have a label not equal to DBHIGH. This may be caused if DBHIGH is changed or if a file is relabeled.
Action:Either relabel the file to match DBHIGH or change DBHIGH to match the file.
ORA-12404 device low name must be dominated by DBLOW name

Cause:A datafile was found on a device with an authorized range insufficient to handle the lowest labeled data in the file.
Action:Lower the authorized minimum device label or move the file to a different device.
ORA-12405 device high name must dominate DBHIGH name

Cause:A datafile was found on a device with an authorized range insufficient to handle the highest labeled data in the file.
Action:Raise the authorized maximum device label or move the file to a different device.
ORA-12406 must be at DBHIGH name in O/S to add files to a tablespace

Cause:A file was added to a new or existing tablespace by a user whose operating system label was not equal to DBHIGH.
Action:Log in to the O/S at DBHIGH to add the file. If creating a new tablespace, set the session label to the label at the desired tablespace definition. If adding a file to an existing tablespace, either set the session label to match the tablespace or user WRITEDOWN privilege to alter the tablespace.
ORA-12407 cannot insert or update the ROWLABEL column of a view

Cause:You tried to insert into or update the ROWLABEL column of a view. Trusted Oracle7 does not allow you to modify the ROWLABEL column of a view.
Action:While you cannot modify the ROWLABEL column of a view, you can modify the ROWLABEL column in the base table(s) of the view. Use the INSERT or UPDATE commands to modify the base tables(s). Consequently, this modifies the view.
ORA-12408 tablespace previously existed at another label name

Cause:A tablespace by this name was previously created and dropped at another label. Part of the dictionary entry for the old tablespace remains, and the new tablespace is attempting to reuse the old entry.
Action:Either recreate the tablespace at the original label or choose a new name for this tablespace.
ORA-12409 DBLOW cannot be null in DBMS MAC mode

Cause:The database was started in DBMS MAC mode before resetting DBLOW.
Action:Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12410 DBHIGH cannot be null in DBMS MAC mode

Cause:The database was started in DBMS MAC mode before resetting DBHIGH.
Action:Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12411 DBHIGH must dominate DBLOW

Cause:DBHIGH does not dominate DBLOW.
Action:Restart the database in OS MAC mode and supply valid values for DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12412 cannot raise DBLOW above num

Cause:An attempt was made to raise DBLOW above its current value. DBLOW can only be lowered, it cannot be raised.
Action:Do not attempt to raise DBLOW.
ORA-12413 cannot lower DBHIGH below num

Cause:An attempt was made to lower DBHIGH below its current value. DBHIGH can only be raised.
Action:Do not attempt to lower DBHIGH.
ORA-12414 must be DBHIGH name to startup database

Cause:An attempt was made to open a database while at an O/S label not equal to DBHIGH.
Action:Log in at DBHIGH to start the database.
ORA-12415 session label must dominate the creation label of role name

Cause:An attempt was made to grant a privilege to a role while at a label that does not dominate the role's creation label. Your DBMS label must dominate the role's creation label to grant a privilege to the role.
Action:Check the creation label of the role and perform the grant while at a label that dominates the creation label of the role.
ORA-12416 label of audit must dominate user

Cause:An attempt was made to set statement audit options on a user below the label where the user was created.
Action:Check the label of the user and set the audit options at the user label or higher.
ORA-12418 label of index must equal table

Cause:An attempt was made to create an index on a table at a label different from where the table was created. It is necessary to be at the identical label and specifically at DBHIGH or DBLOW if the table was created at DBHIGH or DBLOW.
Action:Check the label of the table and create the index at the correct label.
ORA-12419 label of column must equal table

Cause:An attempt was made to add a column to a table at a different label than where the table was created.
Action:Check the label of the table and add the column at the correct label.
ORA-12420 label of stored object must dominate referenced object name

Cause:An attempt was made to create a stored object, such as a view, procedure, function trigger, that references some object not dominated by the current label. While the referenced object may be visible due to enabled MAC privileges, MAC privileges cannot be used for creating the stored object.
Action:Check the label of the indicated object and create the new object at a label that dominates all referenced objects.
ORA-12421 label of grant must dominate object

Cause:An attempt was made to grant privileges on an object at a label lower than where the object was created.
Action:Check the label of the object and perform the grant at the object label or higher.
ORA-12422 label of grant must dominate grantee name

Cause:An attempt was made to grant privileges to a user at a label lower than where the user was created.
Action:Check the label of the grantee and perform the grant at that label or higher.
ORA-12423 label of constraint must equal table

Cause:An attempt was made to add a constraint to a table at a label different from the label of the table.
Action:Check the label of the table and add the constraint at the label of the table.
ORA-12424 label of object must dominate tablespace

Cause:An attempt was made to create an object in a tablespace created at a label higher than the object.
Action:Check the label of the tablespace and create the object at that label or higher.
ORA-12425 label of table must dominate cluster

Cause:An attempt was made to create a table in a cluster created higher than the label of the table.
Action:Check the label of the cluster and create the table at that label or higher.
ORA-12426 label of user must dominate default or temporary tablespace

Cause:An attempt was made to give a user a default or temporary tablespace at a higher label.
Action:Check the label of the default and temporary tablespaces and create the user at that label or higher.
ORA-12427 label of object must dominate schema

Cause:An attempt was made to create an object in a schema defined at a label higher than the object.
Action:Check the label of the schema and create the object at that label or higher.
ORA-12428 insufficient MAC privileges

Cause:There are sufficient privileges to read the object, but no MAC write access to the object.
Action:Either retry the operation at the label of the object or see the system administrator for the needed MAC privilege.
ORA-12429 label of comment must equal table or view

Cause:An attempt was made to comment a table or view at a label different from the label at which the table or view was created.
Action:Check the label of the table or view and add the comment at that label.
ORA-12430 label of trigger must equal table

Cause:An attempt was made to create a trigger at a label different from where the table was created. Your DBMS label must match the table's creation label to create the trigger on the table. While the table may be visible due to enabled MAC privileges, MAC privileges cannot be used to create a trigger.
Action:Check the creation label of the table and create the trigger while at a label that matches the creation label of the table.
ORA-12431 label of user must dominate default profile

Cause:An attempt was made to give a user a default profile created at a label lower than the user.
Action:Check the label of the profile and create the user at that label or higher.
ORA-12432 label of grant must equal label of procedure

Cause:An attempt was made to assign MAC privileges to a procedure at a label other than the creation label of the procedure.
Action:Grant MAC privileges to the procedure at the procedure's creation label.
ORA-12433 label of default role name must dominate user

Cause:An attempt was made to assign a user a default role created at a label below where the user was created.
Action:Check the labels of the user and role and assign only roles higher than the user.
ORA-12434 label of child record must dominate parent

Cause:An attempt was made to insert a child record at a label lower than the corresponding parent record.
Action:Check the label of the parent key value and insert the child record at that label or higher.
ORA-12435 label of package body must equal package

Cause:An attempt was made to create a package body at a label different from the corresponding package.
Action:Check the label of the package and create the package body at that label.
ORA-12436 package body must exist to grant MAC privileges

Cause:An attempt was made to grant MAC privileges to a package when the package body does not exist.
Action:Create the package body for the package and then re-attempt the grant.

ORA-12437 cannot write down to a database at a lower label

Cause:An attempt was made to perform a write operation in a secondary database. Write operations are possible only in the primary database.
Action:Connect directly to the database to perform the operation.
ORA-12438 insufficient privileges to validate constraint on all rows

Cause:It is necessary to have access to all rows in a table to attempt to enable a constraint.
Action:To read all rows in the table, either enable MAC privileges or downgrade all rows in the table.
ORA-12439 cannot modify ROWLABEL column

Cause:An attempt was made to modify the ROWLABEL column.
Action:None. It is not possible to modify the ROWLABEL column.
ORA-12440 database has not been mounted in read-compatible mode

Cause:The requested secondary database was not last started in read-compatible mode.
Action:Set the DB_MOUNT_MODE initialization parameter to READ_COMPATIBLE in the secondary database and startup the secondary database.
ORA-12441 grant already exists at a different label

Cause:One of the granted privileges was previously granted at a different label.
Action:Check USER_SYS_GRANTS or USER_OBJ_GRANTS to locate the label at which the privilege was previously granted. Revoke the old grant and regrant it at the new label.
ORA-12442 must be at same label as user to modify default roles

Cause:An attempt was made to modify a user's default roles at a different label than where the user was created.
Action:Check the ALL_USERS view to see the label at which the user was created and alter the user at that label.
ORA-12443 audit option already exists at a different label

Cause:You tried to audit an event that was previously audited at a different label.
Action:Check the DBA_STMT_AUDIT_OPTS or DBA_PRIV_AUDIT_OPTS dictionary views to identify the label of the previous audit statement. If you want to audit the event at the new label, stop the old audit, using the NOAUDIT statement, and re-audit the event while at the new label.
ORA-12444 file label is lower than instance label

Cause:You tried to reuse a file with a label different from the database instance label.
Action:Examine the message stack for the filename. Remove the file or relabel it to match the database instance label.
ORA-12445 index/row label mismatch - see trace file

Cause:A label in an index has been found not to match the row to which that label points. This may indicate that index labels have been directly changed, which is inappropriate.
Action:To solve the immediate problem, you can drop and recreate the index. If you are unsure of the problem's cause, contact customer support and send them the trace file.
ORA-12446 file label is higher than instance label

Cause:You tried to reuse a file with a label different from the database instance label. You can reuse only files labeled at or below the instance label.
Action:Examine the message stack for the filename. Remove the file or relabel it to match the database instance label.
ORA-12447 non-secure protocol used; connection denied

Cause:You tried to connect to Trusted Oracle7 with a networking protocol that was not secure. You must use a secure networking protocol to connect via a remote location.
Action:Either connect to the database with a secure networking protocol or log in directly to the database.
ORA-12449 least upper bound resulted in an invalid operating system label

Cause:You tried to do an operation that generated a least upper bound (LUB) label, which is not a valid label on your operating system.
Action:Examine the message stack for a more specific message. See the Trusted Oracle7 Server Administrator's Guide for information on least upper-bound (LUB) functions. For more information on invalid label generation, see your operating system-specific Oracle documentation.
ORA-12450 label string could not be translated into binary label

Cause:The operating system could not translate given label string.
Action:Check that the specified string is a valid label and retry the operation.
ORA-12451 binary OS label could not be translated into string label

Cause:The operating system could not translate the specified binary label.
Action:Check that the specified string is a valid label and retry the operation.
ORA-12452 label format string could not be parsed; check format codes

Cause:An invalid format string on a label function was specified.
Action:Check that a valid format string is specified and retry the operation. See the Trusted Oracle7 Server Administrator's Guide for a complete list of valid format strings.
ORA-12453 missing quote in literal string

Cause:A literal string was specified with an incorrect number of quotes.
Action:Check that the string has matching quotes and retry the operation.
ORA-12454 punctuation supplied does not match specified input format

Cause:The punctuation supplied in the label string is inconsistent with the format specified.
Action:Change the punctuation in the label string or the format, whichever is appropriate, and retry the statement.
ORA-12455 OS format not allowed in this context

Cause:The label format string supplied has an OS format that is not allowed with the TO_LABEL function.
Action:Change the label format string to not use the OS format type.
ORA-12456 literal string supplied does not match specified input format

Cause:The literal string supplied is inconsistent with the format string specified.
Action:Change the literal in the label string or format, whichever is appropriate, and retry the statement.
ORA-12457 invalid length for MLSLABEL bind variable

Cause:A bind variable of type MLSLABEL is too long.
Action:Consult your documentation for proper datatype lengths.
ORA-12458 the input string could not be translated into a binary label

Cause:The input string you specified is not a valid binary label on your operating system.
Action:Check the input string, change any components so that they form a valid label, and retry the operation. Refer to your Oracle7 operating system-specific documentation for more information.
ORA-12459 maximum number of columns in a Trusted Oracle table is 253

Cause:A CREATE or ALTER TABLE statement tried to add more than 253 columns, not counting ROWLABEL, to a table.
Action:Specify no more than 253 columns in your CREATE or ALTER TABLE command.
ORA-12460 the value str for the MLS_LABEL_FORMAT parameter is not valid

Cause:The value for the MLS_LABEL_FORMAT initialization parameter you specified does not contain a valid format mask. You must have a valid MLS_LABEL_FORMAT parameter for the database to start up.
Action:Change this parameter setting in your initialization parameter file to a correct value.
ORA-12461 invalid binary label

Cause:You provided a binary label in an OCI program's bind statement that was not a valid operating system label.
Action:Replace the invalid binary label with one that is valid. Refer to your Oracle7 operating system-specific documentation for more information.
ORA-12470 process label could not be found

Cause:An error was encountered in translating the operating system process label into a label number.
Action:Examine the message stack for a more specific message. Refer to your Oracle7 operating system-specific documentation for more information.
ORA-12475 cannot log in below DBLOW name

Cause:An attempt was made to log in at a label dominated by DBLOW.
Action:Either log in at a higher label or lower DBLOW.
ORA-12476 cannot log in above DBHIGH name

Cause:The user attempted to log in at a label dominating DBHIGH.
Action:Either log in at a lower label or raise DBHIGH.
ORA-12478 cannot insert label above DBHIGH name

Cause:An attempt was made to insert a value explicitly above DBHIGH into the ROWLABEL column or to specify a value higher of datatype MLSLABEL. Any label inserted into a Trusted Oracle7 table must fall between DBLOW and DBHIGH, inclusive.
Action:Either raise the value of DBHIGH or specify a lower label on the INSERT or UPDATE statement.
ORA-12480 secondary database changing between OS MAC and DBMS MAC modes

Cause:An attempt was made to access a secondary database while the secondary database is changing between OS MAC and DBMS MAC modes.
Action:Retry the operation after the change is complete.
ORA-12485 cannot find file label for name

Cause:An error was encountered while reading the label of the specified file.
Action:Examine the message stack for an operating system message. Refer to your Oracle7 operating system-specific documentation for more information.
ORA-12487 insufficient privileges to set label to DBHIGH or DBLOW

Cause:It is only possible to set a label to DBHIGH or DBLOW when connected INTERNAL to Trusted Oracle7.
Action:Connect INTERNAL to Trusted Oracle7, then set the label DBHIGH or DBLOW. If this is not possible due to insufficient privileges, contact the database administrator.
ORA-12488 session label must be equal to name

Cause:An attempt was made to log in to an OS MAC database at other than the database label.
Action:Log in from an OS process at the specified label.
ORA-12489 insufficient MAC privilege to alter session

Cause:User does not have sufficient MAC privileges to alter session.
Action:Either change the OS label so ALTER SESSION is not needed or obtain MAC privileges.
ORA-12490 cannot connect at session label below user definition name

Cause:An attempt was made to alter a session label below the label at which the user was created.
Action:Either do not alter the session label below the specified label or recreate the user at a lower label.
ORA-12491 cannot change MAC mode when mounted in READ_COMPATIBLE mode

Cause:You tried to change between OS and DB MAC mode while the database was mounted in READ_COMPATIBLE mode.
Action:Set the DB_MOUNT_MODE initialization parameter to NORMAL and restart the database.
ORA-12494 cannot mount secondary database labeled above DBLOW

Cause:The secondary database requested was labeled above the DBLOW of the primary database.
Action:Check that that DBHIGH on the secondary database is below DBLOW of the primary database.
ORA-12495 multi-threaded server cannot be used with Trusted Oracle

Cause:The MTS_DISPATCHERS parameter is set in the initialization file, which initiated the configuration of the multi-threaded server.
Action:Remove the MTS_DISPATCHERS parameter from the initialization file and restart the instance.

12500-12699: SQL*Net

12700-12799: National Language Support

ORA-12700 invalid NLS parameter value name

Cause:An invalid NLS initialization parameter was specified.
Action:Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701 CREATE DATABASE character set is not known

Cause:The character set specified in the CREATE DATABASE command does not exist on the system.
Action:Refer to your Oracle7 operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
ORA-12702 invalid NLS parameter string used in SQL function

Cause:An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action:Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
ORA-12703 this character set conversion is not supported

Cause: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.
Action:Use character sets available on the system in the CONVERT function.
ORA-12705 invalid or unknown NLS parameter value specified

Cause: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.
Action:Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable.

ORA-12706 this CREATE DATABASE character set is not allowed

Cause: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.
Action:Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle7 operating system-specific documentation for more information about the type of character set supported.

12800-12849: Parallel Query/Index Creation

ORA-12800 system appears too busy for parallel query execution

Cause:The load on the system is too high to perform parallel queries.
Action:Re-enter the statements serially or wait until the system load is reduced.
ORA-12801 error signaled in parallel query server name

Cause:A parallel query server encountered an exception as described in the accompanying message(s).
Action:Correct the error described in the accompanying message.
ORA-12802 parallel query server lost contact with coordinator

Cause:A parallel query server was unable to communicate with the server coordinating the parallel query.
Action:Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.
ORA-12803 parallel query server lost contact with another server

Cause:A parallel query server was unable to communicate with another server involved in the parallel query.
Action:Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.
ORA-12804 parallel query server appears to have died

Cause:Process information for a parallel query server thread cannot be found.
Action:Check for operating system errors and retry the statement. If this problem persists, contact customer support.
ORA-12805 parallel query server died unexpectedly

Cause:The PMON process is cleaning up the process because a parallel query server terminated unexpectedly.
Action:Check for operating system errors and retry the statement. If this problem persists, contact customer support.
ORA-12806 could not get background process to hold enqueue

Cause:This is an internal error that is not usually issued.
Action:Contact customer support.
ORA-12807 process queue could not receive parallel query message

Cause:This is an internal error that is not usually issued.
Action:Contact customer support.
ORA-12808 cannot set [CACHE | SCAN]_INSTANCES greater than number of instances num

Cause:An attempt was made, using the ALTER SYSTEM command, to set CACHE_INSTANCES or SCAN_INSTANCES to a value greater than the number of available instances.
Action:See the accompanying message for the allowable maximum value or set SCAN_INSTANCES or CACHE_INSTANCES to ALL.
ORA-12809 cannot set [CACHE | SCAN]_INSTANCES when mounted in exclusive mode

Cause:An attempt was made to set CACHE_INSTANCES or SCAN_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.
Action:Only set CACHE_INSTANCES or SCAN_INSTANCES when the database is mounted in PARALLEL or SHARED mode.
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to num

Cause:An attempt was made to set the PARALLEL_MAX_SERVERS initialization parameter to a value higher than the maximum allowed by the system.
Action:See the accompanying message for the allowable maximum value.
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, num

Cause:An attempt was made to set the PARALLEL_WIN_SERVERS initialization parameter to a value higher than PARALLEL_MAX_SERVERS.
Action:See the accompanying message for the allowable maximum value.
ORA-12812 only one PARALLEL or NOPARALLEL clause may be specified

Cause:PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.
Action:Specify PARALLEL or NOPARALLEL only once.
ORA-12813 value for PARALLEL or DEGREE must be greater than 0

Cause:PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.
Action:Specify a value greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814 only one CACHE or NOCACHE clause may be specified

Cause:CACHE was specified more than once, NOCACHE was specified more than once, or CACHE and NOCACHE, were specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER, or a RECOVER command.
Action:Specify CACHE or NOCACHE only once.
ORA-12815 value for INSTANCES must be greater than 0

Cause:PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action:Specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12817 parallel query option must be enabled

Cause:You tried to attempt an operation that requires the parallel query option.
Action:Enable the parallel query option.
ORA-12818 invalid option in PARALLEL clause

Cause:An unrecognized option was specified with a PARALLEL clause.
Action:Specify any combination of DEGREE {<n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.
ORA-12819 missing options in PARALLEL clause

Cause:The PARALLEL clause was specified without an option.
Action:Specify any combination of DEGREE { <n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.
ORA-12820 invalid value for DEGREE

Cause:An invalid value for DEGREE was specified within a PARALLEL clause.
Action:Specify a positive integer or DEFAULT.
ORA-12821 invalid value for INSTANCES

Cause:An invalid value for INSTANCES was specified within a PARALLEL clause.
Action:Specify a positive integer or DEFAULT.
ORA-12822 duplicate option in PARALLEL clause

Cause:DEGREE or INSTANCE was specified more than once within a PARALLEL clause.
Action:Specify the option only once.
ORA-12823 default degree of parallelism may not be specified here

Cause:Either an ALTER DATABASE RECOVER command was specified with the DEGREE DEFAULT option in a PARALLEL clause or another command was specified with no option in the PARALLEL clause.
Action:Specify an explicit degree of parallelism.
ORA-12824 INSTANCES DEFAULT may not be specified here

Cause:An ALTER DATABASE RECOVER command was specified with the INSTANCES DEFAULT option.
Action:Specify an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825 explicit degree of parallelism must be specified here

Cause:An ALTER DATABASE RECOVER command was specified without the DEGREE option.
Action:Specify an explicit degree of parallelism.
ORA-12826 hung parallel query server was killed

Cause:Parallel query server was hung and subsequently killed.
Action:Re-execute query and report suspicious events noted in the trace file to customer support if error persists.
ORA-12827 insufficient parallel query slaves available

Cause:PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.
Action:Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.

13000-13199: Spatial Data Option

ORA-13000 dimension number is out of range

Cause:The specified dimension is either smaller than one or greater than the number of dimensions encoded in the HHCODE.
Action:Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.

ORA-13001 dimensions mismatch error

Cause:The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action:Make sure that the number of dimensions in the HHCODEs match.

ORA-13002 specified level is out of range

Cause:The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action:Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.

ORA-13003 the specified range for a dimension is invalid

Cause:The specified range for a dimension is invalid.
Action:Make sure that the lower bound (lb) is less than the upper bound (ub).

ORA-13004 the specified buffer size is invalid

Cause:The buffer size for a function is not valid.
Action:This is an internal error. Contact Oracle Worldwide Support.

ORA-13005 recursive HHCODE function error

Cause:An error occurred in a recursively called HHCODE function.
Action:This is an internal error. Contact Oracle Worldwide Support.

ORA-13006 the specified cell number is invalid

Cause:The cell identifier is either less than 0 or greater that (2^ndim - 1).
Action:Make sure that the cell identifier is between 0 and (2^ndim - 1).

ORA-13007 an invalid HEX character was detected

Cause:A character that is not in the range [0-9] or [A-Fa-f] was detected.
Action:Verify that all characters in a string are in [0-9] or [A-Fa-f].

ORA-13008 the specified date format has an invalid component

Cause:Part of specified date format is invalid.
Action:Verify that the date format is valid.

ORA-13009 the specified date string is invalid

Cause:The specified date string has a bad component or does not match the specified format string.
Action:Make sure that the components of the date string are valid and that the date and format strings match.

ORA-13010 an invalid number of arguments has been specified

Cause:An invalid number of arguments was specified for an HHCODE function.
Action:Verify the syntax of the function call.

ORA-13011 value is out of range

Cause:A specified dimension value is outside the range defined for that dimension.
Action:Make sure that all values to be encoded are within the defined dimension range.

ORA-13012 an invalid window type was specified

Cause:An invalid window type was specified.
Action:Valid window types are RANGE, PROXIMITY, POLYGON.

ORA-13013 the specified topology was not INTERIOR or BOUNDARY

Cause:A topology was specified that was not INTERIOR or BOUNDARY.
Action:Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.

ORA-13014 a topology identifier outside the range of 1 to 8 was specified

Cause:A topology identifier outside the range of 1 to 8 was specified
Action:Specify a topology in the range of 1 to 8.

ORA-13015 the window definition is not valid

Cause:The number of values used to define the window does not correspond to the window type.
Action:Verify that the number of values used to defined the window is correct for the window type and number of dimensions.

ORA-13016 bad partition definition

Cause:The partition common code was not correctly decoded.
Action:This is an internal error. Contact Oracle Worldwide Support.

ORA-13017 unrecognized line partition shape

Cause:The shape of a 2-D line partition could not be determined.
Action:This is an internal error. Contact Oracle Worldwide Support.

ORA-13018 bad distance type

Cause:The specified distance type is invalid.
Action:The only supported distance functions are EUCLID and MANHATTAN.

ORA-13100 badly formed request frame

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13101 partition name datatype should be varchar2

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13102 reply pipe name datatype should be varchar2

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13103 failed to acknowledge on pipe name due to timeout

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13104 failed to send reply on pipe name due to timeout

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13105 buffer overflow encountered on pipe name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13106 acknowledgment on pipe name interrupted

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13107 reply on pipe name interrupted

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13108 spatial table name not found

Cause:The specified spatial table does not exist.
Action:Check the Spatial Data option data dictionary to make sure that the table exists.

ORA-13109 spatial table name exists

Cause:The specified spatial table exists.
Action:Drop the existing table or use a different name.

ORA-13110 spatial table name is not partitioned

Cause:The specified spatial table is not partitioned.
Action:Check the Spatial Data option data dictionary and make sure that a high water mark is set.

ORA-13111 spatial table name has no partition key defined

Cause:The specified spatial table does not have a partition key defined.
Action:Check the Spatial Data option data dictionary and make sure that the table is partitioned.

ORA-13112 invalid count mode name

Cause:The specified count mode is not valid.
Action:Alter the count mode. Valid count modes are ESTIMATE or EXACT.

ORA-13113 Oracle table name does not exists

Cause:The specified Oracle table does not exist.
Action:Check the Oracle7 data dictionary and make sure that the table exists.

ORA-13114 tablespace name not found

Cause:The specified tablespace does not exist.
Action:Check the Spatial Data option data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.

ORA-13115 tablespace name is already allocated

Cause:The specified tablespace is already allocated to the spatial table.
Action:Allocate another tablespace name to the table.

ORA-13116 tablespace name is not allocated to table name

Cause:The specified tablespace is not allocated to the specified spatial table.
Action:Allocate the tablespace to the spatial table.

ORA-13117 partition name not found

Cause:The specified partition does not exist.
Action:Verify the name of the partition by checking the Spatial Data option data dictionary.

ORA-13118 partition name is offline

Cause:The specified partition is offline.
Action:Bring the partition online and then retry the operation.

ORA-13119 source and target tablespaces are identical

Cause:Identical source and target tablespaces were specified when trying to move partition.
Action:Specify different source and target tablespaces if you wish to move a partition.

ORA-13120 SD*POD is not listening on pipe name

Cause:There is no partition operation daemon listening on the specified pipe.
Action:Start a daemon listening on the pipe by using the LISTEN command line option of SD*POD.

ORA-13121 failed to create child partition

Cause:The creation of a child partition failed.
Action:Check for other errors that accompany this error and correct them first.

ORA-13122 child partition name not found

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13123 column name is already defined

Cause:The specified column is already defined for the spatial table.
Action:Use a different column name.

ORA-13124 unable to determine column id for column name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13125 partition key is already set

Cause:A partition key is already set for the spatial table.
Action:Only one partition key can be specified per spatial table.

ORA-13126 unable to determine class for spatial table name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13127 failed to generate target partition

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13128 failed to identify dimensions for column name

Cause:The dimension definitions could not be found for the specified column.
Action:Make sure that the specified column is a spatial column.

ORA-13129 HHCODE column name not found

Cause:The specified spatial column does not exist.
Action:Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.

ORA-13130 timed out waiting for reply on name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13131 record in pipe name is too big

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13132 pipe read on name was interrupted

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13133 archive request failed

Cause:The request to archive a partition failed.
Action:Check the log file and correct any errors indicated.

ORA-13134 restore request failed

Cause:The request to restore a partition failed.
Action:Check the log file and correct any errors indicated.

ORA-13135 duplicate offline path

Cause:The offline path specified is already being used by another spatial table.
Action:Use a different offline path.

ORA-13136 null common code generated

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13138 could not determine name of object name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13139 could not obtain column definition for name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13140 invalid target type

Cause:The specified target type is not valid.
Action:Substitute a valid target type. Valid target types are TABLE or VIEW.

ORA-13141 invalid RANGE window definition

Cause:The RANGE window specified is not correctly defined.
Action:A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.

ORA-13142 invalid PROXIMITY window definition

Cause:The PROXIMITY window specified is not correctly defined.
Action:A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.

ORA-13143 invalid POLYGON window definition

Cause:The POLYGON window specified is not correctly defined.
Action:A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.

ORA-13144 target table name not found

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13145 failed to generate range list

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13146 could not find table substitution variable name

Cause:The partition name substitution variable name was not found in the SQL filter.
Action:The substitution variable name must be in the SQL filter to indicate where that partition name should be placed.

ORA-13147 failed to generate MBR

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13148 failed to generate SQL filter

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13149 failed to generate next sequence number for spatial table name

Cause:This is an internal error.
Action:Document messages and contact Oracle Worldwide Support.

ORA-13150 failed to insert exception record

Cause:Operation failed to insert a record into the exception table
Action:Fix any other errors reported.

ORA-13152 invalid HHCODE type

Cause:Specified HHCODE type is not valid.
Action:Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.

ORA-13197 only MDSYS can execute name

Cause:You tried to execute a restricted procedure.
Action:Only MDSYS can execute the specified partition.

ORA-13198 Oracle error ORAname encountered

Cause:Specified Oracle error was encountered.
Action:Correct the Oracle error.

14000-14099: Partitioned Objects - Parsing

14400-14499: Partitioned Objects - Execution

14500-14999: Partitioned Objects - Analyze

19999-21000: Stored Procedures

ORA-19999 SKIP_ROW procedure was called

Cause:This message is raised when the SKIP_ROW procedure is called.
Action:This procedure should be called only within a trigger or a procedure called by a trigger.
ORA-20000 application_specific_message

Cause:The stored procedure RAISE_APPLICATION_ERROR was called, which causes this message to be generated.
Action:Correct the problem as described in the message or contact the application administrator or database administrator for more information.
ORA-21000 error number argument to RAISE_APPLICATION_ERROR of name is out of range, must be between -20000 and -20999, inclusive

Cause:An attempt was made to specify a number not in the range of -20000 to -20999.
Action:The valid range for user-specified error numbers is -20000 to -20999 inclusively. Do not specify numbers outside this range.

21100-21299: Internal Messages

23300-24299: DBMS PL/SQL Packages

ORA-23300 application_specific_message

Cause:The stored procedure RAISE_SYSTEM_ERROR was called to generate this message.
Action:Correct the problem described in the message or contact the application programmer or database administrator for more information.
ORA-23301 mixed use of deferred RPC destination modes

Cause:Replication catalog determined deferred remote procedure call destinations were mixed with destination determined by other mechanisms in the same transaction.
Action:Do not mix destination types in the same transaction.
ORA-23302 application raised communication failure during deferred RPC

Cause:An application declared a communication failure during a deferred remote procedure call.
Action:Retry the application when communication is restored.

ORA-23303 application raised generic exception during deferred RPC

Cause:An application declared a generic failure during a deferred remote procedure call.
Action:Dependent on application.
ORA-23304 malformed deferred RPC at arg name of name in call name, in tid name

Cause:A deferred remote procedure call was issued without the correct number of arguments as determined by the count parameter DBMS_DEFER.CALL.
Action:Ensure the number of arguments matches the count.
ORA-23305 internal deferred RPC error: str

Cause:An internal error occurred in the deferred remote procedure call.
Action:Contact customer support.
ORA-23306 schema "name" does not exist

Cause:The schema name was null or misspelled, or the schema does not exist locally.
Action:Specify the schema correctly, or create it with CREATE USER.
ORA-23307 replicated schema "name" already exists

Cause:The given database already replicates the given schema.
Action:Choose a different schema or a different database.
ORA-23308 object "name.name" does not exist or is invalid

Cause:The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.
Action:Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
ORA-23309 object "name.name" of type name exists

Cause:An object in the same namespace exists, perhaps with a different type or shape, or the same object has already been registered as a repobject in another object group.
Action:Remove the offending object with the SQL DROP command, unregistered the offending object with DBMS_REPCAT.DROP_MASTER_REPOBJECT(), or reinvoke the request using TRUE for a boolean parameter such as RETRY or USE_EXISTING_OBJECT.

ORA-23310 object group "name" is not quiesced

Cause:The requested operation requires the object group to be suspended.
Action:Invoke SUSPEND_MASTER_ACTIVITY at the repgroup's masterdef, wait until the status has changed to quiesced, and then retry the original request.

ORA-23311 object group "name" is quiesced

Cause:SUSPEND_MASTER_ACTIVITY has been called before the object group has resumed normal operation.
Action:If a RESUME_MASTER_ACTIVITY request is pending, wait until it completes, and then reinvoke SUSPEND_MASTER_ACTIVITY.

ORA-23312 not the masterdef according to name

Cause:The group name is null, the group name is misspelled, the invocation or given database is not the masterdef, or one of the masters does not believe the invocation database is the masterdef.
Action:If the given group name and masterdef were both correct, connect to the masterdef and retry the request, or relocate the masterdef at the errant databases using RELOCATE_masterdef.

ORA-23313 object group "name" is not mastered at name

Cause:The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master.
Action:If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with ADD_MASTER_DATABASE, or use SWITCH_SNAPSHOT_MASTER if the invocation database is a snapshot site.

ORA-23314 database is not a snapshot site for name

Cause:The invocation database is not a snapshot database for the given object group.
Action:Connect to the desired snapshot database and retry the request, or make the invocation database a snapshot site with CREATE_SNAPSHOT_REPSCHEMA or CREATE_SNAPSHOT_REPGROUP.
ORA-23315 repcatlog version or request name is not supported by version name

Cause:Either incompatible repcat versions are used, or a REPCATLOG record has been corrupted.
Action:Convert the master to a compatible version of repcat or retry the request.
ORA-23316 the masterdef is name

Cause:One of the masters to be removed is the masterdef.
Action:Relocate the masterdef to a master that will not be removed, and then reinvoke the REMOVE_MASTER_DATABASES request at the new masterdef.
ORA-23317 a communication failure has occurred

Cause:The remote database is inaccessible.
Action:Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present.
ORA-23318 a DDL failure has occurred

Cause:User-supplied or system-generated DDL did not execute successfully.
Action:Examine DDL, database state, REPCATLOG, and ALL_ERRORS to determine why the failure occurred.
ORA-23319 parameter value name is not appropriate

Cause:The given value of a parameter is either null, misspelled, or not supported.
Action:Refer to the documentation and use parameter values that are appropriate for the given situation.
ORA-23320 the request failed because of values name and name

Cause:A missing DDL record for a REPCATLOG record, or inconsistency in REPCAT views.
Action:Retry the request, or make the views consistent.
ORA-23323 parameter length exceeds deferred remote procedure call limits

Cause:A deferred remote procedure call parameter was longer than the deferred remote procedure call limit of 2000 bytes for CHAR/VARCHAR2 parameters and 255 bytes for raw parameters.
Action:Use smaller parameters.
ORA-23324 error num, while creating DEFERROR entry at name with error num

Cause:The given error was encountered while attempting to create a DEFEROR entry for the given error code and the given database.
Action:Correct the cause of the given error.
ORA-23325 parameter type is not type

Cause:A function in DBMS_DEFER_SYS_QUERY was called to retrieve a deferred remote procedure call parameter from the deferred remote procedure call queue, but the type of the parameter does not match the return type of the function.
Action:Use the function corresponding to the parameter type.
ORA-23326 the system is being quiesced

Cause:A deferred remote procedure call operation was attempted while the database was quiesced.
Action:Resume database activity with the DBMS_REPCAT.RESUME_MASTER_ACTIVITY call.
ORA-23327 imported deferred remote procedure call data does not match id of importing db

Cause:Deferred remote procedure call queues were imported from a database with a different global name or operating system than the importing database.
Action:Deferred remote procedure call data should only be imported into a database with the same global name and hardware and operating system.
ORA-23328 snapshot base table name.name must be same as replicated master table

Cause:When creating a snapshot through repcat, the snapshot base table did not match a replicated table name at the master.
Action:Change the snapshot DDL to use the same base table as the replicated table name at the master.

ORA-23329 successful user-provided ddl but no snapshot name.name.

Cause:The DDL provided by the user to create a snapshot was executed without error, but snapshot does not exist.
Action:Manually back-out the DDL, and re-register with matching ddl and snapshot.

ORA-23330 column group name already exists

Cause:The column group was already registered in the object group.
Action:Use a column group name not yet registered in the object group.
ORA-23331 column group name does not exist

Cause:The given column group is either null, misspelled or not registered.
Action:Use a registered column group.
ORA-23332 group name is in use; cannot drop

Cause:The given column group or priority group is being used to resolve conflicts.
Action:Call DBMS_REPCAT procedures DROP_UPDATE_RESOLUTION, DROP_DELETE_RESOLUTION, DROP_UNIQUE_RESOLUTION so that the column group or priority group is no longer in use before dropping.
ORA-23333 column name is already part of a column group

Cause:Attempted to add a column to a column group when the column was already a member of a column group.
Action:Drop the column from its existing column group before trying to add it to another.
ORA-23334 column name does nor exist in table or column group

Cause:The given column is either null, misspelled or is not part of the given table or column group.
Action:Use a column that is a member of the table or column group.
ORA-23335 priority group name already exists

Cause:The priority group was already registered in the object group.
Action:Use a column group name not yet registered in the object group.
ORA-23336 priority group name does not exist

Cause:The priority group was already registered in the object group.
Action:Use a priority group name not yet registered in the object group.
ORA-23337 priority or value not in priority group name

Cause:The specified value or priority has not been registered as part of the priority group.
Action:Either specify a different value or priority that is already part of the priority group, or add the value to the priority group.
ORA-23338 priority or value already in priority group name

Cause:The specified value or priority has already been registered as part of the priority group.
Action:Either specify a different value or priority that is not already part of the priority group, or drop the value from the priority group.
ORA-23339 duplicate conflict resolution information

Cause:The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered.
Action:Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first.
ORA-23340 incorrect resolution method name

Cause:User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods.
Action:If user function is specified when conflict resolution method was not "USER FUNCTION", either reregister function with method as "USER FUNCTION" or specify a NULL user function. Otherwise, specify one of the documented supported conflict resolution methods.
ORA-23341 user function required

Cause:A NULL user function was specified for the "USER FUNCTION" method.
Action:Provide user function name, e.g., "schema"."package"."function", that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods.
ORA-23342 invalid parameter column name

Cause:The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method.
Action:Specify a parameter column from the specified column group that has a correct type for the conflict resolution method.
ORA-23343 no match for specified conflict resolution information

Cause:The specified combination of column group, sequence, conflict type has not been registered, for example, for adding a comment.
Action:Specify a combination of column group, sequence, conflict type that has been registered.
ORA-23344 constraint name.name does not exist

Cause:A null, misspelled or nonexistent constraint was specified when registering a uniqueness conflict.
Action:Register a named constraint for the specified table.
ORA-23345 table name.name not registered to collect statistics

Cause:A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.
Action:Call DBMS_REPCAT.REGISTER_STATISTICS to register the table.
ORA-23346 primary key is undefined for table name

Cause:Trying to generate replication support for a table without a primary key as defined by a constraint or DBMS_REPCAT_COLUMNS.
Action:Add a primary key constraint to the table or define a primary key using DBMS_REPCAT_COLUMNS.
ORA-23347 datatype name for column name table name not supported

Cause:The table has a column whose datatype is not supported by repcat.
Action:Remove the column from the table, or alter the column to have one of the supported datatypes.
ORA-23348 cannot replicate procedure name; only IN parameters supported

Cause:Trying to generate replication support for a package that has a procedure with OUT or IN OUT parameters.
Action:Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure.
ORA-23349 cannot generate replication support for functions

Cause:Trying to generate replication support for a package that has a public function, or for a stand-alone function.
Action:Remove the public function from the package, or alter the function to be a procedure.
ORA-23350 maximum number of recursive calls exceeded

Cause:This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts.
Action:Re-execute the deferred transaction from DEFERROR using DBMS_DEFER_SYS.EXECUTE_ERROR.
ORA-23351 parameter datatype name for procedure name not supported

Cause:The procedure has a parameter whose datatype is not supported by repcat.
Action:Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes.
ORA-23352 duplicate destination for deferred transaction

Cause:A duplicate destination was specified for a deferred transaction either in a DBMS_DEFER.CALL call or an earlier DBMS_DEFER.TRANSACTION call or a DBMS_DEFER_SYS.ADD_DEFAULT_DEST call.
Action:Remove the duplicate entry.
ORA-23353 deferred RPC queue has entries for object group name

Cause:The requested action cannot be performed until the queue is empty for the given object group.
Action:Use DBMS_DEFER_SYS.EXECUTE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue.

ORA-23354 deferred RPC execution disabled for name

Cause:The execution of a deferred remote procedure call at the destination failed because its propagation was disabled.
Action:Enable deferred remote procedure call execution with the DBMS_DEFER_SYS.ENABLE call.
ORA-23355 object name.name does not exist or is invalid at master site.

Cause:The given name was null or misspelled; the given type was wrong; the object does not exist as a valid database object at the master site; or the object does not exist as a replicated object with the appropriate status.
Action:Ensure the object is valid in the master database and is visible to the user; and if appropriate, ensure the object is a valid object in all_repobject.

ORA-23360 only one snapshot for master table name can be created

Cause:An attempt to create more than one snapshot on a given master table in the same rep group.
Action:Create these other snapshots in a different rep group at another site.

ORA-23361 snapshot name does not exist at master site

Cause:The snapshot does not exist at the master site for offline instantiation of the snapshot.
Action:The correct procedure is to create the snapshot in a different schema at the master site, and then follow the instructions for offline instantiation of snapshots.

ORA-23363 mismatch of snap base table name at master and snap site

Cause:The name of the base table of the snapshot at the master site is different from the base table at the snapshot site. This error may arise during offline instantiation of snapshots.
Action:Retry offline instantiation with a snapshot name less than 24 bytes.

ORA-23364 replication option not installed

Cause:The replication option was not installed at this site. Updatable snapshots, deferred remote procedure calls, and other replication features were, therefore, unavailable.
Action:Install the replication option. The replication option is not part of the Oracle7 Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.
ORA-23365 site name does not exist

Cause:The site specified in argument REFERENCE_SITE or argument COMPARISON_SITE in call to DIFFERENCES() routine or RECTIFY() routine did not name an existing site.
Action:Make sure that database sites specified really do exist, and re-run the routine.

ORA-23366 integer value num is less than 1

Cause:The value of argument MAX_MISSING to routine DIFFERENCES() cannot be less than 1. Value of argument COMMIT_ROWS to routines DIFFERENCES() and RECTIFY() cannot be less than 1.
Action:Choose an integer value for those arguments to be 1 or greater.

ORA-23367 table name is missing the primary key

Cause:The table specified in argument ONAME1 or ONAME2 in call to DIFFERENCES() routine did not contain either a primary key or a virtual primary key (defined through DBMS_REPCAT package under symmetric replication).
Action:Make sure the tables specified have a primary key defined.

ORA-23368 name name cannot be null or the empty string

Cause:Argument SNAME1, SNAME2, ONAME1, ONAME2, MISSING_ROWS_SNAME, MISSING_ROWS_ONAME1, MISSING_ROWS_ONAME2 to DIFFERENCES() or RECTIFY() cannot be NULL or (EMPTY STRING).
Action:Change the argument to a non-null or a non-empty string.

ORA-23369 value of \"name\" argument cannot be null

Cause:Argument MAX_MISSING to DIFFERENCES() routine cannot be NULL.
Action:Legal values for MAX_MISSING are integers 1 or greater.

ORA-23370 table name and table name are not shape equivalent name

Cause:The tables specified were not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths were not the same. Specifically, the problem was in the parentheses and was one of the following: the number of columns were not equal, datatypes of columns with same name in different tables were different, lengths of VARCHAR2 and CHAR columns were not equal, precision and scale of number datatypes were not equal.
Action:Make sure the two tables being compared have the same number of columns, same column names, and same datatypes.

ORA-23371 column name unknown in table name

Cause:Some column in ARRAY_COLUMNS argument (or COLUMN_LIST argument) to DIFFERENCES() routine did not correspond to a column in the specified table.
Action:Make sure that all the columns in either ARRAY_COLUMNS or COLUMN_LIST are present in the specified table.

ORA-23372 type name in table name is unsupported

Cause:Certain types in the table comparison utility were not supported.
Action:Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication.

ORA-23373 object group name does not exist

Cause:The group name was null or misspelled, or the group did not exist locally.
Action:Specify the group correctly, or create it with DBMS_REPCAT.CREATE_MASTER_REGROUP().

ORA-23374 object group name already exists

Cause:The given database already replicated the given object group.
Action:Choose a different group or a different database.
ORA-23375 feature is incompatible with database version at num

Cause:A feature not compatible with the specified database was used.
Action:Set or raise the value of the COMPATIBLE parameter in the INIT.ORA file to match the necessary compatibility level.

ORA-23376 node name is not compatible with replication version \"name\"

Cause:A feature that was not compatible with the remote database was used.
Action:Upgrade the remote database and retry the operation.

ORA-23377 bad name name for missing_rows_oname1 argument

Cause:An attempt was made to use the name of the reference site table as the name of the MISSING_ROWS_ONAME1 argument.
Action:Provide a separately created table with a different name for MISSING_ROWS_ONAME1 argument. The separately created table will contain the differences between the tables being compared.

ORA-23378 connection qualifier name is not valid for object group name

Cause:The connection qualifier used in the database link for the specified object group does match the qualifier specified for the group in create_master_repgroup.
Action:Use or create a database link which contains the correct connection qualifier.

ORA-23379 connection qualifier name is too long

Cause:The maximum length of a database link, including the connection qualifier, is 128 bytes.
Action:Use a shorter connection qualifier, or shorten the name of the database link.

ORA-23380 propagation mode name is not valid

Cause:The specified propagation is misspelled, or is not supported.
Action:Refer to the manual on replicated data for valid propagation modes.

ORA-23381 generated object for base object name.name@name does not exist

Cause:The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support.
Action:Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure dbms_repcat.generate_replication_support() needs to be called from the master definition site for the base object.

ORA-23400 invalid snapshot name "name"

Cause:A null, misspelled, or badly formed snapshot name was given to DBMS_SNAPSHOT.REFRESH.
Action:Provide a valid snapshot name to DBMS_SNAPSHOT.REFRESH.
ORA-23401 snapshot "name.name" does not exist

Cause:A snapshot name was given to DBMS_SNAPSHOT.REFRESH that is not in SYS.SNAP$ or its associated views.
Action:Provide a snapshot name that is in SYS.SNAP$, ALL_SNAPSHOTS, or USER_SNAPSHOTS.
ORA-23402 refresh was aborted because of conflicts caused by deferred transactions

Cause:There are outstanding conflicts logged in the DEFERROR table at the snapshot's master.
Action:Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS set to TRUE, which will proceed with the refresh, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result with an updatable snapshot's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
ORA-23403 refresh group "name.name" already exists. Refresh group not a stored object?

Cause:Making a new refresh group when there is already a group of the same name in SYS.RGROUP$.
Action:Choose a different refresh group name.
ORA-23404 refresh group "name.name" does not exist

Cause:A refresh group name was given that is not in SYS.RGROUP$.
Action:Provide a refresh group name that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23405 refresh group number "name" does not exist

Cause:A refresh group number was given that is not in SYS.RGROUP$.
Action:Provide a refresh group number that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23406 insufficient privileges on user "name"

Cause:The caller is not the owner of the snapshot and does not have ALTER ANY SNAPSHOT privileges.
Action:Perform the operation as the owner of the snapshot or as a user with ALTER ANY SNAPSHOT privileges.
ORA-23407 object name "name" must be shaped like "SCHEMA.OBJECT" or "OBJECT"

Cause:The object name, for example, the rollback segment, the snapshot name, or the refresh group, was incorrectly specified.
Action:Retry the operation with the object name properly specified, like "SCHEMA.OBJECT" or "OBJECT".
ORA-23409 could not find an unused refresh group number

Cause:1000 consecutive refresh group numbers, as defined by the RGROUPSEQ number, were already used by rows in SYS.RGROUP$.
Action:Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups.
ORA-23410 snapshot "name.name" is already in a refresh group

Cause:A snapshot of the same name is already in a refresh group.
Action:Subtract the snapshot its the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group.
ORA-23411 snapshot "name.name" is not in refresh group "name.name"

Cause:The specified snapshot is not in the specified refresh group.
Action:Try again with the proper snapshot and refresh group names.
ORA-23420 interval must evaluate to a time in the future

Cause:The parameter INTERVAL evaluates to a time earlier than SYSDATE.
Action:Choose an expression that evaluates to a time later than SYSDATE.
ORA-23421 job number num is not a job in the job queue

Cause:There is no job visible to the caller with the given job number.
Action:Choose the number of a job visible to the caller.
ORA-23422 Oracle Server could not generate an unused job number

Cause:Oracle Server could not generate a job number that was not used to identify another job.
Action:Retry the operation.
ORA-23423 job number num is not positive

Cause:The given job number is less than 1.
Action:Choose a positive integer.
ORA-23430 argument name cannot be NULL or empty string

Cause:The caller has provided an argument whose value cannot be NULL or the empty string.
Action:Check that the VARCHAR2 value provided is not NULL or the empty string and retry the call.

ORA-23431 wrong state: name

Cause:The routine was executed against a replicated object group that was in the wrong state.
Action:Make sure that the replicated object group is in the state given in the error message.

ORA-23432 master site name already exists

Cause:An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group.
Action:If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and re-run the routine.

ORA-23433 executing against wrong master site name

Cause:An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine.
Action:Provide an argument to the routine that correctly indicates the site against which the routine should be executing.

ORA-23434 master site name not known for object group

Cause:The site name given as an argument to a routine was not already known to the replicated object group.
Action:Execute the DBMS_OFFLINE_SCHEMA.BEGIN_INSTANTIATION() routine to add a new site to the replicated schema.

ORA-24275 function name parameter name missing or invalid

Cause:The function <pkgname.funcname> was called with a parameter <parname> that was null, 0 length, or had an invalid value.
Action:Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation.
ORA-24276 function name output name maximum value exceeded

Cause:The function <pkgname.funcname> computed a value for the output <parname> that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.
Action:Correct the input values to produce a result that will comply with the limits as specified in the documentation.

24300-24999: UPI/OCI Messages

ORA-24300 bad value for mode

Cause:An undefined mode value was specified.
Action:Check that the correct mode is selected and that an allowed value for that mode is specified.

ORA-24301 null host specified in thread-safe logon

Cause:An HDA was not specified in the logon call while running in a thread safe environment.
Action:Make sure that HDA is not NULL when calling the logon routine.

ORA-24302 host connection in use by another thread

Cause:An attempt was made to use the host connection while it was in use by another thread.
Action:Wait for another thread to finish before using this connection.

ORA-24303 call not supported in non-deferred linkage

Cause:One of the calls that was supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.
Action:Use this call in deferred mode of linkage.

ORA-24304 datatype not allowed for this call

Cause:Data of this datatype cannot be sent or fetched in pieces.
Action:Use other bind or define calls for this datatype.

ORA-24305 bad bind or define context

Cause:The call was executed on a cursor for which this was invalid.
Action:Verify that this call is valid for this cursor. For example, GET PIECE INFORMATION and SET PIECE INFORMATION are valid on a cursor if appropriate binds and defines have been done on this cursor.

ORA-24306 bad buffer for piece

Cause:A zero length buffer or a null buffer pointer was provided.
Action:Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.

ORA-24307 invalid length for piece

Cause:The length of the piece exceeds the maximum possible size of the data.
Action:Verify that the length of this piece and the cumulative length of all the previous pieces are not more than the PROGVL parameter specified in the obindps call.

25000-25099: Trigger Errors

ORA-25000 invalid use of bind variable in trigger WHEN clause

Cause:A bind variable was used in the WHEN clause of a trigger.
Action:Remove the bind variable. To access the table columns, use (new/old).column_name.

25100-25199: Parse Errors

ORA-25100 TABLESPACE option can only be used with ALTER INDEX REBUILD

Cause:The TABLESPACE option to ALTER INDEX was used without the REBUILD option.
Action:Use ALTER INDEX REBUILD TABLESPACE <tablespace name>.

ORA-25101 duplicate REBUILD option specification

Cause:The REBUILD option to ALTER INDEX was specified more than once.
Action:Specify the option at most once.

ORA-25102 PARALLEL option can only be used with ALTER INDEX REBUILD

Cause:The PARALLEL option to ALTER INDEX was used without the REBUILD option.
Action:Use ALTER INDEX REBUILD.

ORA-25103 NOPARALLEL option can only be used with ALTER INDEX REBUILD

Cause:The NOPARALLEL option to ALTER INDEX was used without the REBUILD option.
Action:Use ALTER INDEX REBUILD.

ORA-25104 UNRECOVERABLE option can only be used with ALTER INDEX REBUILD

Cause:The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option.
Action:Use ALTER INDEX REBUILD.

ORA-25105 RECOVERABLE option can only be used with ALTER INDEX REBUILD

Cause:The RECOVERABLE option to ALTER INDEX was used without the REBUILD option.
Action:Use ALTER INDEX REBUILD.

ORA-25106 only one of PARALLEL or NOPARALLEL clause may be specified

Cause:PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement.
Action:Remove all but one of the PARALLEL or NOPARALLEL clauses.

ORA-25107 duplicate TABLESPACE option specification

Cause:The TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.
Action:Remove all but one of the TABLESPACE clauses.

ORA-25108 standby lock name space exceeds size limit of num characters

Cause:The lock name space for the standby database exceeded the maximum string length.
Action:Change initialization parameter STANDBY_LOCK_NAME_SPACE to a character string of less than the specified characters.

ORA-25109 standby lock name space has illegal character char

Cause:An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, '_', '#', '$', and '@' characters.
Action:Change initialization parameter STANDBY_LOCK_NAME_SPACE to a valid character string.

ORA-25110 NOSORT may not be used with a bitmap index

Cause:An attempt was made to create a bitmap index using the NOSORT option.
Action:Remove NOSORT from the CREATE BITMAP INDEX statement.

ORA-25111 BITMAP may not be used with a cluster index

Cause:An attempt was made to create a cluster index the the BITMAP attribute.
Action:Remove BITMAP from the CREATE INDEX statement.

ORA-25112 a bitmap index may index only one column

Cause:An attempt was made to create a bitmap index on more than one column.
Action:Remove all columns in the CREATE INDEX statement except one.

ORA-25113 DML operations for BITMAP indexes not implemented

Cause:A DML operation such as INSERT, UPDATE, DELETE was performed on a table that has at least one BITMAP index defined.
Action:Remove all BITMAP indexes defined on the table.

25200-25699: Advanced Queueing


Go to previous file in sequence Go to next file in sequence
Prev Next		 Oracle
Copyright © 1996 Oracle Corporation.
All Rights Reserved.		 Go to Product Documentation Library
Library		 Go to books for this product
Product		 Go to Contents for this book
Contents		 Go to Index
Index