Copyright: Copyright (c) 1994, Oracle Corporation.
Citation: Copyright (c) 1994, Oracle Corporation.


Entry Topic
Oracle7 Messages and Codes

00000-00999:Oracle7 Server

01000-01499:Oracle7 Server UPI

01500-02099:Oracle7 Server Oracle Commands

02140-03199:Oracle7 Server SQL Parsing

02140-03199:Oracle7 Server Extent Allocation

09200-09499:Oracle Workgroup Server

06100-06101:SQL*Net TCPIP

06220-06400:SQL*Net Named Pipes

06401-06429:SQL*Net NETCMN

06430-06449:SQL*Net NetBIOS

06450-06500:SQL*Net SPX


This help file created via:

Oracle Book to Microsoft Help Version 1.0w

© 1994 Oracle Corporation Inc.

Authored by KM .


00000-00999:Oracle7 Server

This section lists messages that might arise from running the Oracle7 Server.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-00000

ORA-00000	normal, successful completion

Cause:	An operation has completed normally, having met no exceptions.

Action:	No user action is required.


ORA-00001

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.

For Trusted ORACLE users, either re-attempt the operation using a different value, or contact the database administrator to resolve the conflict.


ORA-00018

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

ORA-00019	maximum number of session licenses exceeded

Cause:	All licenses are in use.

Action:	Call Worldwide Customer support before increasing the number of session licenses.


ORA-00020

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

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

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

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 and/or cursors. Detaching a session with operating system privileges is always disallowed.


ORA-00024

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, log off from the previous process before trying to log in from another one.


ORA-00025

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

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:	Attempt the command again with a valid session ID.


ORA-00027

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

ORA-00028	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 again available, log in again and resume work.


ORA-00029

ORA-00029	session is not a user session

Cause:	The session specified in the ALTER SYSTEM KILL SESSION command was not a user's session ID. For example, the session may be recursively started.

Action:	Enter the command again with a valid session ID.


ORA-00030

ORA-00030	session does not exist

Cause:	The session ID specified in the ALTER SYSTEM KILL SESSION command does not exist. The user may have logged out since the command was issued.

Action:	No user action is required.


ORA-00031

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 an non-interruptible operation (for example, rolling back a transaction, or 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 user action is 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-00034

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

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

ORA-00050	O/S message occurred while obtain an enqueue. See O/S message.

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 message in the system documentation and perform the needed action.


ORA-00051

ORA-00051	time-out occurred while waiting for resource

Cause:	This message is usually caused by an instance that has terminated abnormally.

Action:	Check for any non-recovered instances; then restart them.


ORA-00052

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

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

ORA-00054	resource busy and acquire with NOWAIT specified

Cause:	The NOWAIT keyword forced a return to the command prompt since a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.

Action:	Either, try the command after a few minutes, or, to wait for the resource, enter the command without the NOWAIT keyword.


ORA-00055

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

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, make sure it has no parse locks. Wait a few minutes before retrying the operation.


ORA-00057

ORA-00057	maximum number of DDL locks exceeded

Cause:	System has run out of DDL locks.

Action:	Increase DDL lock parameter and warm start.


ORA-00058

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.

 Potential reasons for this mismatch are:

 1) mounting the wrong database

 2) using the wrong initialization parameter file

 3) the DB_BLOCK_SIZE value was changed.

Action:	For one of the above causes, either:

 1) mount the correct database

 2) use the correct initialization parameter file

 3) correct the DB_BLOCK_SIZE parameter value


ORA-00059

ORA-00059	maximum number of DB_FILES exceeded

Cause:	An unavailable resource was requested. The maximum number of data files 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

ORA-00060	deadlock detected while waiting for resource

Cause:	The active session and another session are each waiting for a resource locked by the other. This condition is known as a deadlock. In order to resolve the deadlock, one or more statements were rolled back so the other session could continue work.

Action:	Either:

 1) issue a ROLLBACK statement and re-execute all statements since the last commit

 2) wait until the lock is released (possibly a few minutes) and re-execute the rolled back statements


ORA-00061

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:

 1) to not use DML_LOCKS, for all instances set DML_LOCKS to zero

 2) to use DML_LOCKS, for all instances set DML_LOCKS to a positive integer


ORA-00062

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:	Restart the instance with the DML_LOCKS parameter set to a non-zero value; then re-execute the statement.


ORA-00063

ORA-00063	LOG_FILES initialization parameter exceeded

Cause:	LOG_FILES initialization parameter was exceeded.

Action:	Increase the LOG_FILES parameter in the initialization parameter file and restart ORACLE.  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

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.


ORA-00065

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

ORA-00066	LOG_FILES is var buts needs to be var 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:	Ensure LOG_FILES initialization parameter is same for all instances.


ORA-00067

ORA-00067	invalid value var for parameter var, must be at least var

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

ORA-00068	invalid value var for parameter var, must be between var and var

Cause:	The value for the initialization parameter is invalid.

Action:	Choose a value as indicated by the message.

________________________________________


00100-00150: Multi-threaded Server

This section lists message generated by the multi-threaded server.


ORA-00100

ORA-00100	idle public server terminating

Cause:	There are too many idle shared servers waiting on the common dispatcher request queue.

Action:	No action required.


ORA-00101

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

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 the installation or user's guide for network protocols supported by the dispatchers.


ORA-00103

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

ORA-00104	deadlock detected; all public servers blocked waiting for resource

Cause:	This message occurs when a client locks a resource, and then the maximum number of shared servers are taken by other clients who are requesting a locked resource. The original client would then be unable to get a shared server, and thus be unable to 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 the maximum number of servers is reached, and if this problem occurs frequently, increase the limit for the initialization parameter MTS_SERVERS or MTS_MAX_SERVERS so that more shared servers are started up as the system restarts.


ORA-00105

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:	Either:

1..	include the network protocol in the MTS_DISPATCHERS initialization parameter and restart the system

2..	use the ALTER SYSTEM SET MTS_DISPATCHERS command with a network protocol that exists in the initialization parameter file


ORA-00106

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

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:

•	The network configuration file is not set up correctly.

•	The client side address is not specified correctly.

•	The listener initialization parameter file is not set up correctly.


ORA-00108

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 Worldwide Customer Support.


ORA-00110

ORA-00110	missing value for initialization parameter MTS_LISTENER_ADDRESS

Cause:	There is no value for the MTS_LISTENER_ADDRESS initialization parameter.

Action:	Specify one or more valid SQL*Net Version 2 addresses for the listener process.


ORA-00111

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; then restart the instance.


ORA-00112

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

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

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

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

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-00120

ORA-00120	dispatching mechanism not enabled or installed

Cause:	Either the dispatcher 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 the installation or user's guide for procedures for starting and configuring the dispatcher processes.

________________________________________


00150-00159: ORACLE*XA


ORA-00150

ORA-00150	duplicate transaction ID

Cause:	Attempted to start a new transaction with an ID already in use by an existing transaction.

Action:	Check your application.


ORA-00151

ORA-00151	invalid transaction ID

Cause:	The specified transaction ID does not correspond to an existing valid transaction.

Action:	Check your application.


ORA-00152

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 your application.

________________________________________


00200-00249: Control Files


ORA-00200

ORA-00200	cannot create control file 'name'

Cause:	The control file cannot be created, usually because of insufficient disk storage or file name conflicts.

Action:	Ensure that there is sufficient disk space and there are no conflicts in file names; then try to create the control file again.


ORA-00201

ORA-00201	control file version num incompatible with ORACLE version num

Cause:	The control file was created by incompatible software.

Action:	Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.


ORA-00202

ORA-00202	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

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 they are not the same files. The most likely cause is 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

ORA-00204	message 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:	Make sure the disk is online. If it is not, bring it online; then 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 Database Administrator's Guide for information about recovering from the loss of a control file.


ORA-00205

ORA-00205	message in identifying control file 'name'

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

Action:	Either:

 1) Ensure the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again.

 2) When using mirrored control files (that is, more than one control file is referenced in the initialization parameter file), remove the control file name listed in the message from the initialization parameter file, and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file.


ORA-00206

ORA-00206	message 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:	Make sure the disk is online. If it is not, bring it online; then 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. Refer to the ORACLE7 Server Administrator's Guide for information on recovering from the loss of a control file.


ORA-00207

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 file name listed in the message from the initialization parameter file, and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the c


ORA-00208

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 file names specified in the CONTROL_FILES parameter in the initialization parameter file, and restart ORACLE. Delete unused files.


ORA-00209

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; then try again.


ORA-00210

ORA-00210	cannot open control file 'name'

Cause:	The system was unable to open a control file.

Action:	Make sure the control file exists, that the storage device is online, and that the file is not locked by some other program; then try again. Also, check to see that the operating system limit on the number of open files per process has not been exceeded.

When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the parameter from the initialization parameter file referencing the control file name indicated in the message and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file.


ORA-00211

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 file name listed in the message from the initialization parameter file, and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy


ORA-00212

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; then retry the operation.


ORA-00213

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

ORA-00214	control file 'name' version num inconsistent with file 'name' version num

Cause:	An inconsistent set of control files, data files, and redo log files was used.

Action:	Use a consistent set of control files, data files, and redo log files. That is, all the files must be for the same database and from the same time period.


ORA-00215

ORA-00215	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; then retry the operation.


ORA-00216

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

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 re-create the database. When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the control file name listed in the message from the initialization parameter file, and restart the instance. If the message does not recur, remove the problem control file from the initialization paramete


ORA-00218

ORA-00218	control file 'name' was created with physical size num now is num

Cause:	The control file size specified in the file's header differs from the physical block size of the control file. This usually means that the control file has been corrupted.

Action:	Recover the control file as described in the ORACLE7 Server Administrator's Guide.


ORA-00219

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 re-create the database. In the CREATE DATABASE statement use lower for clauses such as MAXDATAFILES and MAXLOGFILES as described in the ORACLE7 Server Administrator's Guide.


ORA-00220

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

ORA-00221	error on write to control file

Cause:	An error occurred when writing to one or more of the control files.

Action:	More descriptive messages will follow this message.


ORA-00223

ORA-00223	conversion data file is invalid or incorrect version

Cause:	A Version 6 to ORACLE7 conversion data file 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

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 file name.

________________________________________


00250-00299: Archiving and Recovery

This section lists the messages generated when archiving or recovery of the database is in progress.


ORA-00250

ORA-00250	archiver not started

Cause:	An attempt was made to stop automatic archiving, but the archiver process was not running.

Action:	None.


ORA-00251

ORA-00251	archiving/media recovery requires OS DBA or OPER privileges

Cause:	An attempt was made to perform archiving or media recovery without having the required operating system DBA or OPER privileges.

Action:	Ask the database administrator to perform the operation or grant the necessary privileges.


ORA-00252

ORA-00252	log 'name' of thread num is empty, cannot archive

Cause:	The specified redo log has not been 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

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; then try again.


ORA-00254

ORA-00254	message in archive control string 'str'

Cause:	The specified archive string does not refer to a valid destination.

Action:	Make sure the archive string refers to a valid, online device; then retry the operation.


ORA-00255

ORA-00255	message archiving log 'name' of thread num, sequence # num

Cause:	An message occurred during archiving.

Action:	Check the accompanying message stack for more detailed information.


ORA-00256

ORA-00256	message occurred in translating archive text string 'str'

Cause:	An message occurred while translating the archive control string.

Action:	Check the accompanying message stack for more detailed information.


ORA-00257

ORA-00257	archiver is stuck. Connect internal only, until freed.

Cause:	The ARCH process received an message 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

ORA-00258	manual archiving in NOARCHIVELOG mode must identify log

Cause:	An attempt was made to manually archive a redo log file without specifying the sequence number, group number, or file name while the database is in NOARCHIVELOG mode.

Action:	The name, group number, or thread and sequence number of redo log files must be specified when manually archiving redo log files when the database is in NOARCHIVELOG mode.


ORA-00259

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

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 log might have been reused for another sequence number; it might have been dropped; the sequence number may be greater than the current log sequence number; or the thread may not have any logs.

Action:	Check the ARCHIVE statement; then specify a valid log sequence number.


ORA-00261

ORA-00261	log name of thread num is being archived, cannot archive

Cause:	The log sequence number specified in the ARCHIVE statement is currently being archived.

Action:	Check all operating archive processes; then specify a valid log sequence number.


ORA-00262

ORA-00262	current log name of closed thread num cannot switch for archiving

Cause:	The redo log file cannot be archived because it is the current log of a closed thread. It is not possible to switch redo log files so that another log is current. All other redo log files for this thread must be archived and cannot be reused.

Action:	Archive the other redo log files in this thread first.


ORA-00263

ORA-00263	there are no logs that need archiving for thread num

Cause:	An attempt was made to manually archive the unarchived logs in this thread, but no logs need archiving.

Action:	No user action is required.


ORA-00264

ORA-00264	no recovery required

Cause:	An attempt was made to perform media recovery on files which do not need any type of recovery.

Action:	Do not attempt to perform media recovery on the selected files. Check to see that the file names were entered properly; if not, issue the command again with the proper file names.


ORA-00265

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 data files.

Action:	Open the database and then issue the SHUTDOWN command with the NORMAL or IMMEDIATE options.


ORA-00266

ORA-00266	name of archived logfile needed

Cause:	During media recovery, the name of an archived redo log file was requested, but no name was entered.

Action:	Mount the correct redo log file and enter its name when it is requested.


ORA-00267

ORA-00267	name of archived logfile not needed

Cause:	During media recovery, the name of an archived redo log file was entered, but no name was requested.

Action:	Continue media recovery, but do not enter a new log name.


ORA-00268

ORA-00268	specified logfile does not exist name

Cause:	The given redo log file does not exist.

Action:	Check the spelling and capitalization of the file name and resubmit the command.


ORA-00269

ORA-00269	specified logfile is part of thread num not num

Cause:	The given redo log file is not part of the given thread

Action:	Check to make sure 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. Resubmit the command after correcting the error.


ORA-00270

ORA-00270	error creating archive log

Cause:	An error was encountered when either creating or opening the destination file for archiving.

Action:	Make certain the archive destination is valid, and that there is sufficient space on the destination device.


ORA-00271

ORA-00271	there are no logs that need archiving

Cause:	An attempt was made to manually archive the unarchived redo log files, but there are no files that need to be archived.

Action:	No user action is required.


ORA-00272

ORA-00272	error writing archive log

Cause:	An I/O error occurred while archiving a redo log file.

Action:	Make sure the output device is still available, and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.


ORA-00273

ORA-00273	media recovery of direct load data that was not logged

Cause:	A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.

Action:	The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.


ORA-00274

ORA-00274	illegal recovery option str

Cause:	An illegal option was specified for a recovery command.

Action:	Check the syntax of the command and resubmit the command using the correct syntax.


ORA-00275

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

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:	Resubmit the command using a valid change number after the CHANGE keyword.


ORA-00277

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

ORA-00278	logfile '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

ORA-00279	change num generated at name needed for thread num

Cause:	The requested log is required to proceed with recovery.

Action:	Please supply the requested log in the command, or cancel recovery.


ORA-00280

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 supply the required archived redo log files for other errors.


ORA-00281

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

ORA-00282	UPI var %s call not supported, use ALTER DATABASE RECOVER

Cause:	The given UPI call is no longer supported.

Action:	All recovery operations are made through parsing and executing the "ALTER DATABASE  RECOVER..." commands.  Refer to the ORACLE7 Server Administrator's Guide for the proper recovery procedures.


ORA-00283

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

ORA-00284	recovery session still in progress.

Cause:	An message 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

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


ORA-00286

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 offline, attempt to make it available. Make certain that the correct file names are being used, especially if the redo log file is being accessed from a remote location.


ORA-00287

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

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

Action:	Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.


ORA-00289

ORA-00289	suggestion : str

Cause:	This message reports the next redo log file name that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.

Action:	Consider using this file name for the next log needed for recovery.


ORA-00290

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

Cause:	While attempting to archive to a redo log file, the server encountered and unexpected operating system message.

Action:	Correct the operating system message (given in the messages) and retry the operation.

________________________________________


00300-00379: Redo Log Files

This section lists messages generated when the Redo Log Files are being accessed.


ORA-00300

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.


ORA-00301

ORA-00301	message in adding logfile 'name' - file cannot be created

Cause:	The creation of the redo log file failed.

Action:	Make sure 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.

Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.


ORA-00302

ORA-00302	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:	None required.


ORA-00304

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

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

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.


ORA-00307

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.


ORA-00308

ORA-00308	cannot open archived log 'name'

Cause:	The system cannot access a required archived redo log file.

Action:	Make certain that the offline log exists, the storage device is online and the archived file is in the correct location; then attempt to continue recovery or restart the recovery session.


ORA-00309

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

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 file name was specified during recovery.

Action:	Specify a valid redo log file; then retry the operation.


ORA-00311

ORA-00311	cannot read header from archived log

Cause:	An message 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

ORA-00312	online log name thread num: 'str'

Cause:	This message reports the file name for details of another message.

Action:	Other messages will accompany this message. See the associated messages for the appropriate action to take.


ORA-00313

ORA-00313	open failed for members of log group var of thread var

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

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:	Refer to the ORACLE7 Server Administrator's Guide for recovery procedures.


ORA-00315

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

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

ORA-00317	file type str in header is not logfile

Cause:	This is not an archived redo log file.

Action:	Refer to the ORACLE7 Server Administrator's Guide for recovery procedures.


ORA-00318

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

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

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

ORA-00321	log name of thread num, cannot update logfile 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

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

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

ORA-00324	logfile 'name' translated name 'name' too long, num characters exceeds num limit

Cause:	The translated name for a redo log file is too long.

Action:	Re-specify a redo log file name that on translation is shorter.


ORA-00325

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 correct archived redo log file; then retry the operation.


ORA-00326

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

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

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

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

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

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

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

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

ORA-00333	redo log read message block num count num

Cause:	An message 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

ORA-00334	archived log: 'name'

Cause:	This message reports the file name involved with other message messages.

Action:	See the associated messages for a description of the problem.


ORA-00335

ORA-00335	online log name: No log with this number, log does not exist

Cause:	This message reports the file name involved with other messages.

Action:	See the associated messages for a description of the problem.


ORA-00336

ORA-00336	logfile 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; then re-execute the statement.


ORA-00337

ORA-00337	logfile '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

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

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

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

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

ORA-00342	archived log was created before last RESETLOGS

Cause:	During recovery, a log was supplied that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another redo log file that was created since that time that contains the correct redo information.

Action:	Find and supply the correct redo log file for recovery.


ORA-00343

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

ORA-00344	unable to re-create log 'name' at the end of incomplete recovery

Cause:	At the end of manual recovery, all logs need reformatting. This message indicates that a log I/O failure occurred, probably because the file was not accessible or a device failed.

Action:	Check the accompanying messages; then make the file accessible, or restore the device.


ORA-00345

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

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

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

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

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

ORA-00350	log name of thread num needs to be archived - can not drop

Cause:	An attempt was made to drop an online redo log file that has not been archived, and media recovery has been enabled.

Action:	Archive the redo log file or disable media recovery.


ORA-00351

ORA-00351	recover-to time invalid

Cause:	The time specified in a RECOVER DATABASE ... UNTIL is after January 1, 1988.

Action:	Specify a time after January 1, 1988.


ORA-00352

ORA-00352	all logs for thread num need to be archived - can not enable

Cause:	An attempt was made to enable a thread when all of the online redo log files in the thread need 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

ORA-00353	log corruption near block num time stamp 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 time-based recovery up to the indicated time.


ORA-00354

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

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

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

ORA-00357	too many members specified for logfile, 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.


ORA-00358

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.


ORA-00359

ORA-00359	Logfile 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 issue the command again with a valid group number.


ORA-00360

ORA-00360	name is not a logfile member

Cause:	An invalid file name was given to drop a redo log group member. Either the file is not a part of the database, or it is a data file.

Action:	Supply a valid member name and issue the command again.


ORA-00361

ORA-00361	name is the last logfile member for 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 LOGFILE command.


ORA-00362

ORA-00362	member is required to form a valid logfile 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 LOGFILE command.


ORA-00363

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 supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.


ORA-00364

ORA-00364	can not write header to new log member

Cause:	An I/O message 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-00371

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

ORA-00372	file name can not be modified at this time

Cause:	An attempt was made to access a file being taken offline, or the database may be in the process of closing.

Action:	Access the file after it is taken offline.  Attempts will either succeed because the data file is back online, or fail with an message describing which file is offline. Repeat until successful.


ORA-00373

ORA-00373	online log version ver incompatible with ORACLE version ver

Cause:	The online log was written by incompatible version of ORACLE can occur when the redo log file was created by either a newer or older version of ORACLE.

Action:	Recover the database with the compatible software, shut it down cleanly; then restart with current software.


ORA-00374

ORA-00374	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

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.


ORA-00376

ORA-00376	file name can not 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 offline.

Action:	Check the state of the file. Bring the file online, if necessary.

________________________________________


00400-00420: ORACLE Compatibility

This section lists messages generated when different versions of ORACLE communicate.


ORA-00400

ORA-00400	invalid release value val for parameter val

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

ORA-00401	the value for parameter "param" 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

ORA-00402	database changes by release rel cannot be used by release rel

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

ORA-00403	str (str) is not the same as other instances (str)

Cause:	The recovery compatibility initialization parameters for this instance are different than other instances.

Action:	Change the initialization parameters of the current instance to match other instances already running.


ORA-00404

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:	Verify that the conversion process has been started on this database and that the data file name is accessible.


ORA-00405

ORA-00405	compatibility type \name\

Cause:	Reporting a type associated with another message.

Action:	See accompanying message.

________________________________________


00436-00437: Licensing

This section lists messages generated when the installed Oracle product discovers a discrepancy in licensing codes.


ORA-00436

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:	Make sure ORACLE is installed correctly; then contact Worldwide Customer Support.


ORA-00437

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:	Make sure ORACLE is installed correctly; then contact Worldwide Customer Support.

________________________________________


00440-00485: Background Processes

This section lists messages generated when background processes of the ORACLE Server are started or shut down.


ORA-00444

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

ORA-00445	background process 'name' did not start

Cause:	The specified process did not start.

Action:	Check and, if necessary, correct problems indicated by one or more of the following:

 1) the size of the SGA, referring to the operating system specific installation and user's guide for the initialization parameters

 2) accompanying messages

 3) the background trace file

 4) the executable image is not in the right location with the correct protections


ORA-00446

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 Worldwide Customer Support.


ORA-00447

ORA-00447	fatal message in background process

Cause:	One of the background processes died unexpectedly.

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-00448

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

ORA-00449	background process 'name' unexpectedly terminated with message 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.


ORA-00470

ORA-00470	LGWR process terminated with message

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 messages, check the trace file for the mentioned process until the root message is found.


ORA-00471

ORA-00471	DBWR process terminated with message

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

ORA-00472	PMON process terminated with message

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

ORA-00473	ARCH process terminated with message

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

ORA-00474	SMON process terminated with message

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

ORA-00475	TRWR process terminated with message.

Cause:	The system tracing process died.

Action:	Warm start the instance.


ORA-00476

ORA-00476	RECO process terminated with message

Cause:	The distributed transaction (two-phase commit) recovery process died.

Action:	Warm start the instance.


ORA-00480

ORA-00480	LCK* process terminated with message

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-00481

ORA-00481	SMON process posting itself

Cause:	This is an internal message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00483

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

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

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


00600-00639: ORACLE Exceptions

This section lists messages generated when an internal exception is generated within ORACLE.


ORA-00600

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

Cause:	This is a catch-all internal message for ORACLE program exceptions. It indicates that a process has met a low-level, unexpected condition.

Various causes of this message include:

•	time-outs

•	file corruption

•	failed data checks in memory

•	hardware, memory, or I/O messages

•	incorrectly restored files

The first argument is the internal message number; other arguments are various numbers, names, and character strings. (See section "Reporting a Problem to Worldwide Customer Support" on page 1-12 for more information.) The numbers may change meanings between different versions of the ORACLE Server.

Action:	Report this error to Worldwide Customer Support after gathering the following information:

•	events that led up to the error

•	the operations that were attempted that led to the error

•	the conditions of the operating system and database at the time of the error

•	any unusual circumstances that occurred prior to receiving the ORA-00600 message.

•	contents of any trace files generated by the error

•	the relevant portions of the Alert file

NOTE:  The cause of this error may manifest itself as different errors at different times. Be aware of the history of errors that occurred prior to this internal error.


ORA-00601

ORA-00601	cleanup lock conflict

Cause:	The Process Monitor process encountered a lock conflict while trying to recover processes. This is an internal message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00602

ORA-00602	internal programming exception

Cause:	An internal programming exception has occurred.

Action:	Report this error as a program bug to Worldwide Customer Support.


ORA-00603

ORA-00603	ORACLE Server session terminated by fatal error

Cause:	An ORACLE Server session is in an unrecoverable state.

Action:	Login to ORACLE again so a new server session will be created automatically. Examine the session trace file for more information.


ORA-00604

ORA-00604	error occurred at recursive SQL level num

Cause:	An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Action:	If the situation described in the next message on the stack can be corrected, do so; otherwise, contact Worldwide Customer Support.


ORA-00606

ORA-00606	internal error code

Cause:	A call to deferred UPI functions was made in non-deferred mode.

Action:	Contact Worldwide Customer Support.

________________________________________


00640-00699: SQL*Connect

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


00700-00709: Dictionary Cache

This sections lists messages generated when the ORACLE dictionary cache is accessed.  (Note that row cache is a synonym for dictionary cache.)


ORA-00701

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

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 data files.


ORA-00703

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 Worldwide Customer Support.


ORA-00704

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 problem persists, contact Worldwide Customer Support.

________________________________________


00816-00816: Message Translation


ORA-00816

ORA-00816	message translation failed

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

Action:	Notify Worldwide Customer Support.

________________________________________


00900-00999: SQL Parsing

This section lists some of the messages generated when SQL statements are parsed by the ORACLE Server. Most, but not all, messages in this section indicate incorrect SQL syntax. For SQL syntax, refer to the ORACLE7 Server SQL Language Reference Manual.


ORA-00900

ORA-00900	invalid SQL statement

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

Action:	Correct the syntax.


ORA-00901

ORA-00901	invalid CREATE command

Cause:	The CREATE command was not followed by a valid CREATE option.

Action:	Correct the syntax.


ORA-00902

ORA-00902	invalid datatype

Cause:	The datatype entered in the CREATE or ALTER TABLE statement is not valid.

Action:	Correct the syntax.


ORA-00903

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 long and cannot be a reserved word.


ORA-00904

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 quotes. It may not be a reserved word.


ORA-00905

ORA-00905	missing keyword

Cause:	A required keyword is missing.

Action:	Correct the syntax.


ORA-00906

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 are also required around subqueries used in WHERE clauses and UPDATE table SET column = (SELECT ...) statements.

Action:	Check the command syntax, insert a left parenthesis where required; then re-execute the statement.


ORA-00907

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.


ORA-00908

ORA-00908	missing NULL keyword

Cause:	Either:

 1) In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that no null values are allowed in that column but the keyword NULL was omitted.

 2) In the IS [NOT] NULL logical operator, the keyword NULL was not found. For example, the following statement generates the message:

SELECT * FROM EMP WHERE DEPTNO IS NOT;

The keyword NULL must follow the keywords IS NOT.

Action:	Correct the syntax.


ORA-00909

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:	Check the syntax of the function and enter the required number of arguments.


ORA-00910

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

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 quotes ("), this message will be issued.

Action:	Remove the invalid character from the statement, or enclose the object name in double quotes.


ORA-00913

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

ORA-00914	missing ADD keyword

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

•	the keyword LOGFILE in an ALTER DATABASE statement

•	a column element or table constraint in an ALTER TABLE statement

•	the keyword DATAFILE in an ALTER TABLESPACE statement

Action:	Specify the keyword ADD in the ALTER statement.


ORA-00915

ORA-00915	network access of dictionary table not currently allowed

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00917

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

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

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

ORA-00919	invalid function

Cause:	An entry was formatted like a function call but not recognizable as an ORACLE function.

Action:	Check for valid syntax and ensure a valid function is used.


ORA-00920

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

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:	Check the command syntax; then enter all the required components.


ORA-00922

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:	Check syntax and spelling. Remove the erroneous option or length specification from the column or storage specification.


ORA-00923

ORA-00923	FROM keyword not found where expected

Cause:	In a SELECT or REVOKE statement the keyword FROM is 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:	Insert the keyword FROM where appropriate. The SELECT list itself may also be in error. If quotes were used in an alias, make sure double quotes enclose the alias. Also, check to see if a reserved word was used as an alias.


ORA-00924

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:	Check the syntax, insert the keyword BY where required, and then re-execute the statement.


ORA-00925

ORA-00925	missing INTO keyword

Cause:	An INSERT statement has been entered without the keyword INTO.

Action:	Check the syntax, insert the keyword INTO where required, and then re-execute the statement.


ORA-00926

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:	Enter either a VALUES clause or a subquery after the INSERT INTO clause.


ORA-00927

ORA-00927	missing equal sign

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

•	in the SET clause of an UPDATE statement

•	following "!" in a search condition to signify not equal

Action:	Check the syntax, insert the equal sign where required, then re-execute the statement.


ORA-00928

ORA-00928	missing SELECT keyword

Cause:	A SELECT subquery must be included in a CREATE VIEW statement.

Action:	Insert the required SELECT clause after the CREATE VIEW clause, and then re-execute the statement.


ORA-00929

ORA-00929	missing period

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00930

ORA-00930	missing asterisk

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00931

ORA-00931	missing identifier

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00932

ORA-00932	inconsistent datatypes

Cause:	Either:

•	An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields), or concatenating a character field with a long field.

•	An attempt was made to perform an operation on a database object (such as a table or view) that is not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object's name.

•	An attempt was made to use an undocumented view.

Action:	If the cause is:

•	different datatypes; then use consistent datatypes. For example, convert the character field to a numeric field using the TO_NUMBER function before adding it to the date field. Functions may not be used with long fields.

•	an object not intended for normal use; then do not access the restricted object.


ORA-00933

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

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.

The desired result may possibly be achieved by including the function in a subquery or HAVING clause.


ORA-00935

ORA-00935	group function is nested too deeply

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00936

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 enter the missing component.


ORA-00937

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

ORA-00938	not enough arguments for function

Cause:	The function was referenced with too few arguments.

Action:	Check the function syntax and supply the required number of arguments.


ORA-00939

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

ORA-00940	invalid ALTER command

Cause:	An invalid ALTER option was specified.

Action:	Correct the syntax.


ORA-00941

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

ORA-00942	table or view does not exist

Cause:	The table or view entered does not exist, or a synonym was used although not allowed here, 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 them.

For Trusted ORACLE configured in DBMS MAC mode, you may get this message if you attempt to access an object that you do not dominate.

Action:	Check, the spelling of the table or view name, that a view is not specified where a table is required, and that an existing table or view name exists. Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.

Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.

For Trusted ORACLE in DMBS MAC mode, if the cause is an object existing at a higher label, alter your current label to dominate the creation label of the object; then re-issue the command.


ORA-00943

ORA-00943	cluster does not exist

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

For Trusted ORACLE configured in DBMS MAC mode, you may get this message if you attempt to access an object that you do not dominate.

Action:	Specify a valid cluster name following the keyword CLUSTER, then re-execute the statement.

For Trusted ORACLE in DMBS MAC mode, if the cause is an object existing at a higher label, alter your current label to dominate the creation label of the object; then re-issue the command.


ORA-00944

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 an 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 re-execute it.


ORA-00945

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.

For Trusted ORACLE configured in DBMS MAC mode, you may get this message if you attempt to access an object that you do not dominate.

Action:	Re-execute the statement, using the names of columns defined for the table.

For Trusted ORACLE in DMBS MAC mode, if the cause is an object existing at a higher label, alter your current label to dominate the creation label of the object; then re-issue the command.


ORA-00946

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 re-execute the statement.


ORA-00947

ORA-00947	not enough values

Cause:	This error occurs when 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 ...)

Another common cause of this error is in an INSERT statement in which the VALUES or SELECT clause does not contain enough values needed for the INSERT as in:

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

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

ORA-00949	illegal reference to remote database

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-00950

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 re-execute the statement.


ORA-00951

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

ORA-00952	missing GROUP keyword

Cause:	Groups are not currently implemented.

Action:	No user action is required.


ORA-00953

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

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:

@MONOX = GRANT CONNECT TO user-list IDENTIFIED BY password-list;


ORA-00955

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

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

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

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, insert the keyword CHECK where required; then re-execute the statement.


ORA-00959

ORA-00959	tablespace 'name' does not exist

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

For Trusted ORACLE configured in DBMS MAC mode, you may get this message if you attempt to access an object that you do not dominate.

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, since the new tablespace is not the same as the dropped tablespace even though they have the same name.

For Trusted ORACLE in DMBS MAC mode, if the cause is an object existing at a higher label, alter your current label to dominate the creation label of the object; then re-issue the command.


ORA-00964

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, make sure each table name in the SELECT list matches a table name in the FROM list, and then re-execute the statement.


ORA-00965

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

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:	Check syntax, spelling, and use the keyword TABLE where required.


ORA-00967

ORA-00967	missing WHERE keyword

Cause:	The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.

Action:	Correct the syntax of the SQL statement; then re-execute it.


ORA-00968

ORA-00968	missing INDEX keyword

Cause:	The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.

Action:	Check the statement syntax; then re-execute the statement.


ORA-00969

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, spelling, and use the keyword ON where required.


ORA-00970

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 re-execute the statement.


ORA-00971

ORA-00971	missing SET keyword

Cause:	The keyword SET in an UPDATE statement is missing, misspelled, or misplaced.

Action:	Check syntax, spelling, and use the keyword SET after the name of the table to be updated.


ORA-00972

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

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 re-execute the statement.


ORA-00975

ORA-00975	date + date not allowed

Cause:	An attempt was made to add two date fields together. Dates may only be added 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

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

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

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

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

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

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 re-execute one or more AUDIT statements.


ORA-00982

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 re-execute the statement.


ORA-00984

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

ORA-00985	invalid program name

Cause:	Probably a syntax error.

Action:	Correct syntax.


ORA-00986

ORA-00986	missing or invalid group names(s)

Cause:	Probably a syntax error.

Action:	Correct syntax.


ORA-00987

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

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

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

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

ORA-00991	invalid format for GRANT command

Cause:	An invalid form of the GRANT command was entered. There are two forms of the GRANT command. The first form is used to grant a user database access privileges. The second form is used to grant a user object privileges.

Action:	Check the command syntax and re-execute the statement.


ORA-00993

ORA-00993	missing GRANT keyword

Cause:	The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. In order to grant privileges to a user and also the permission to grant those privileges to another user, the keywords WITH GRANT OPTION must be specified at the end of the GRANT statement.

Action:	Change the keyword WITH to the keywords WITH GRANT OPTION, then re-execute the statement.


ORA-00994

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 re-execute the statement.


ORA-00995

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

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 single bar (|) if concatenation was not intended.


ORA-00997

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

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

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


01000-01499:Oracle7 Server UPI

This section lists messages that might be generated by the Oracle7 Server when using the UPI.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-01000

ORA-01000	maximum open cursors exceeded

Cause:	A host language program attempted to open too many cursors. The maximum number of cursors per user is determined by the initialization parameter OPEN_CURSORS.

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

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

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

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

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:	Specify the complete username and password to log on to ORACLE.


ORA-01005

ORA-01005	null password given; logon denied

Cause:	An invalid password was given when logging on.

Action:	Provide a valid password.


ORA-01006

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

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 1 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

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

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 given in the Programmer's Guide to the ORACLE Precompilers.

Action:	Check the syntax for the call and enter all required parameters.


ORA-01010

ORA-01010	invalid OCI operation

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01011

ORA-01011	Cannot use ORACLE7 compatibility mode with an ORACLE Version 6 server

Cause:	An attempt was made to use ORACLE7 compatibility mode when accessing ORACLE Version 6.

Action:	Do not use ORACLE7 compatibility mode when accessing ORACLE Version 6.


ORA-01012

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

ORA-01013	user requested cancel of current operation

Cause:	The user interrupted an ORACLE operation by entering CTRL-C (ControlC) 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

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

ORA-01015	logon called recursively

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01016

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 prior to the offending function.


ORA-01017

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.

When Trusted ORACLE is configured in OS MAC mode, this error may occur if attempting to query a table/view in a secondary database when the username was not created or granted the CREATE SESSION privilege in the secondary database.

When Trusted ORACLE is configured in DBMS MAC mode, this error may occur if granted the CREATE SESSION system privilege at a higher label than that attempted at login.

Action:	Enter a valid username/password combination in the correct format.

For Trusted ORACLE users, if the cause of this error is that the username was either not created or not granted the CREATE SESSION system privilege in a secondary database, ask the database administrator to authorize the username to access the secondary database. Alternatively, if the cause of this error is that the username is granted the CREATE SESSION system privilege at a higher label than that of the attempted login, either login at that higher label or ask the database administrator to re-grant the privilege at the appropriate label.


ORA-01018

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

ORA-01019	unable to allocate memory in the user side

Cause:	The user side memory allocator returned an error.

Action:	Increase the process' heap size or switch to the old set of calls.


ORA-01020

ORA-01020	unknown context state

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01021

ORA-01021	invalid context size specified

Cause:	An invalid value was entered for the initial context area size. The initialization parameter CONTEXT_AREA specifies the context area size which, must be between 1024 and 131,072 bytes.

Action:	Specify an initial context area size between 1024 and 131,072 bytes.


ORA-01023

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

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 ORACLE Precompilers.

Action:	Check the datatype description and enter the correct number for the datatype.


ORA-01025

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 normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01026

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

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 re-execute the SQL statement.


ORA-01030

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 Worldwide Customer Support.


ORA-01031

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 attempting to install a database without the necessary operating system privileges.

When Trusted ORACLE is configured in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login.

Action:	Ask the database administrator to perform the operation or grant the required privileges.

For Trusted ORACLE users getting this error although granted the appropriate privilege at a higher label, ask the database administrator to re-grant the privilege at the appropriate label.


ORA-01032

ORA-01032	no such userid

Cause:	This is an internal error message related to Export/Import.

Action:	Contact Worldwide Customer Support.


ORA-01033

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

ORA-01034	ORACLE not available

Cause:	ORACLE was not started up. Possible causes are:

•	The SGA requires more space than was allocated for it.

•	The operating system variable pointing to the instance is improperly defined.

Action:	Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. Retry after ORACLE has been initialized. If ORACLE has been initialized, verify that ORACLE was linked correctly. Also, refer to the installation or user's guide for additional information about this error.


ORA-01035

ORA-01035	ORACLE only available to users with RESTRICTED SESSION privilege

Cause:	Logins are 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

ORA-01036	illegal variable name/number

Cause:	Unable to find bind context on user side.

Action:	Make sure that the variable being bound is in the SQL statement.


ORA-01037

ORA-01037	cannot allocate sort work area cursor; too many cursors

Cause:	The maximum number of cursors for the program has been exceeded.

Action:	Retry the operation using fewer open cursors.


ORA-01038

ORA-01038	cannot write data file version ver with ORACLE Version ver

Cause:	An attempt was made to write data file headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version.

Action:	Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened; then use the previous software release to do the operation.


ORA-01039

ORA-01039	insufficient privileges on underlying objects of the view

Cause:	An attempt was made to use explain plan on 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

ORA-01040	invalid character in password; logon denied

Cause:	There are multibyte characters in the password or some characters in the password are not in the US7ASCII range.

Action:	Resubmit password with valid characters.


ORA-01041

ORA-01041	internal error. HOSTDEF extension does not exist

Cause:	The pointer to the HSTDEF extension in HSTDEF is null.

Action:	Report as a bug to Worldwide Customer Support.


ORA-01042

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

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 Worldwide Customer Support.


ORA-01045

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

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.


ORA-01050

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.


ORA-01053

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

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

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-01070

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

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

ORA-01072	cannot stop ORACLE; ORACLE not running

Cause:	An attempt was made to stop ORACLE, but ORACLE was not running.

Action:	No user action is required.


ORA-01073

ORA-01073	fatal connection error: unrecognized call type

Cause:	An illegal internal operation was attempted. This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01074

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

ORA-01075	currently logged on

Cause:	An attempt was made to log on while already logged on.

Action:	No user action is required.


ORA-01076

ORA-01076	multiple logons per process not yet supported

Cause:	ORACLE does not support multiple logons per process.

Action:	No user action is required.


ORA-01077

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

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

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

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

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

ORA-01083	value of parameter var 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-01086

ORA-01086	savepoint 'name' never established

Cause:	An attempt was made to roll back to a savepoint that was never established.

Action:	No user action is required.


ORA-01087

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

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

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

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

ORA-01091	failure during startup force

Cause:	Unable to destroy the old SGA.

Action:	Manually remove the old SGA (see the installation or user's guide for instructions); then re-issue the STARTUP command.


ORA-01092

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

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 resubmit 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

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

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

ORA-01096	program version (num) incompatible with instance (num)

Cause:	The program was linked with a different version of the server than the instance it is attempting to connect to.

Action:	Re-link 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

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-01099

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

This sections lists messages generated when files are accessed by the ORACLE Server.


ORA-01100

ORA-01100	database already mounted

Cause:	An attempt was made to mount a database with the name of a currently mounted database.

Action:	No user action is required.


ORA-01101

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

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

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

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

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

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

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

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

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

ORA-01110	data file name: 'str'

Cause:	This message reports the file name involved with other messages.

Action:	See the associated messages for a description of the problem.


ORA-01111

ORA-01111	name for data file name is unknown - rename to correct file

Cause:	The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.

Action:	Rename the missing file to the name of the real file.


ORA-01112

ORA-01112	media recovery not started

Cause:	An attempt was made to continue media recovery, but media recovery had not been started.

Action:	No user action is required.


ORA-01113

ORA-01113	file name needs media recovery

Cause:	An attempt was made to open a data file that is in need of media recovery.

Action:	First apply media recovery to the data file identified in the message, then retry the operation.


ORA-01114

ORA-01114	IO message writing block to file name (block # num)

Cause:	The device on which the file resides is probably offline.

Action:	Restore access to the device, then retry the operation.


ORA-01115

ORA-01115	IO message reading block from file name (block # num)

Cause:	The device on which the file resides is probably offline.

Action:	Restore access to the device, then retry the operation.


ORA-01116

ORA-01116	message in opening data file name

Cause:	Usually the file is not accessible.

Action:	Make sure the data file is in the expected location and can be accessed properly, then retry the operation.


ORA-01117

ORA-01117	adding file 'name' with illegal block size num, limit is num

Cause:	An attempt was made to add a data file with a block size that is greater than the maximum block size allowed.

Action:	Retry the operation with a smaller block size.


ORA-01118

ORA-01118	cannot add any more data files: limit of num exceeded

Cause:	An attempt to add a data file 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 data files (and perhaps increased file size).


ORA-01119

ORA-01119	message in creating data file '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

ORA-01120	cannot remove online data file name; database is open or mounted parallel

Cause:	An attempt to remove an online data file 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 offline, or put the instance in restricted access mode.


ORA-01121

ORA-01121	cannot rename data file name - file is in use or recovery

Cause:	An attempt to rename an online data file failed because the file was not closed or was being recovered. Either the file is online and the data file 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

ORA-01122	data file name - failed verification check

Cause:	The information in the data file is inconsistent with information from the control file.  This could be because the control file is from a time earlier than the data files, or the data file size does not match the size specified in the control file, or the data file is corrupted.

Action:	Make certain that the data files and control files are the correct files for this database, then retry the operation.


ORA-01123

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

ORA-01124	cannot recover online file 'name' - must be offline to recover

Cause:	An attempt was made to recover an online file.

Action:	Take the file offline before recovery.


ORA-01125

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

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

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

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:

 1) Bring the file online for the online backup.

 2) Do an offline backup.


ORA-01129

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

ORA-01130	data file version num incompatible with ORACLE Version num

Cause:	The named data file 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 data file and make sure it exists.


ORA-01131

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

ORA-01132	length of data file name 'name' exceeds limit of num characters

Cause:	The specified data file name is too long.

Action:	Shorten the file name and retry the operation.


ORA-01133

ORA-01133	length of logfile name 'name' exceeds limit of num characters

Cause:	The specified redo log file name is too long.

Action:	Shorten the file name and retry the operation.


ORA-01134

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

ORA-01135	file name accessed for DML/query is offline

Cause:	A query failed because it referenced a data file 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

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 DATA FILE command that is smaller than the size needed.

Action:	Issue the statement again using the correct size for the file.


ORA-01137

ORA-01137	data file 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

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

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

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

ORA-01141	message renaming data file name - new file 'name' not found

Cause:	An attempt to change a data file's name in the control file failed because no file was found with the new name.

Action:	Make sure that the data file has been properly renamed by the operating system, then retry the operation.


ORA-01142

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

ORA-01143	cannot disable media recovery - file name is offline

Cause:	An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.

Action:	Recover the offending file or drop the tablespace to which it belongs, then retry the operation.


ORA-01144

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

ORA-01145	offline immediate disallowed unless media recovery enabled

Cause:	ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATA FILE ... OFFLINE is only allowed if database is in ARCHIVEREDO LOG mode.

Action:	Take the tablespace offline normally 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

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 data files.

Action:	End the first backup before beginning another.


ORA-01147

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

ORA-01148	database must be mounted exclusive for this operation

Cause:	Database was not mounted exclusive.

Action:	Mount the database in exclusive mode and retry the operation.


ORA-01149

ORA-01149	cannot shutdown - file name has online backup set

Cause:	A normal shutdown was attempted while online backup is in progress.

Action:	End the online backup and then shut down.


ORA-01150

ORA-01150	cannot offline tablespace - file name has online backup set

Cause:	Tablespace cannot be taken offline when online backup is running.

Action:	End the online backup and then take the tablespace offline.


ORA-01151

ORA-01151	use media recovery to recovery 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 DATA FILE 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-01152

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.

Note:  This message cannot always be caught.

Action:	Apply additional redo log files until the database is consistent or restore the data files from an older backup and repeat recovery.


ORA-01153

ORA-01153	an incompatible media recovery is active

Cause:	An attempt was made to start an incompatible media recovery or open and reset the redo log files during media recovery. Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or OPEN RESETLOGS is incompatible with any media recovery.

Action:	Wait for the completion of, or cancel, the other media recovery session.


ORA-01154

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

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

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

ORA-01157	cannot identify data file name - file not found

Cause:	The background process was not able to find one of the data files. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online data files. Accompanying messages from the operating system will describe why the file was not found.

Action:	Make the file available to database. Then either open the database or do ALTER SYSTEM CHECK DATA FILES.


ORA-01158

ORA-01158	database name already mounted

Cause:	Another instance has a database by this name mounted.

Action:	Find and shut down the instance that has this database mounted before issuing the CREATE CONTROLFILE statement.


ORA-01159

ORA-01159	file name is not from same database as previous files

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

ORA-01160	file name is not a str it is of type str

Cause:	The file in the DATA FILE or LOGFILE 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

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

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 are 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 not the first file find the correct version of the file.


ORA-01163

ORA-01163	file size in header num (bytes) does not match SIZE num (bytes)

Cause:	File size specified at CREATE CONTROLFILE does not match the size stored in the header. Most likely the specification is wrong.

Action:	Restore the file from a backup and issue the statement again.


ORA-01164

ORA-01164	MAXLOGFILES may not exceed num

Cause:	The value for MAXLOGFILES specified on the command line is greater than num.

Action:	Resubmit the command with a value of MAXLOGFILES that is num or less.


ORA-01165

ORA-01165	MAXDATAFILES may not exceed num

Cause:	The value for MAXDATAFILES specified on the command line is greater than num.

Action:	Resubmit the command with a value of MAXDATAFILES that is num or less.


ORA-01166

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 the parameter DB_FILES.


ORA-01167

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, insure they are in the same group file specification.


ORA-01168

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

ORA-01169	DATA FILE number 1 not found. Must be present

Cause:	Data file number 1 was not specified in a CREATE CONTROLFILE statement.

Action:	Locate data file number 1 and resubmit the CREATE CONTROLFILE statement, making certain to include data file 1 on the command line.


ORA-01170

ORA-01170	file not found 'name'

Cause:	A file specified in the CREATE CONTROLFILE statement was not found. All data files (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 file name, and check for the existence of all files. Then issue the statement again after correcting the file names.


ORA-01171

ORA-01171	data file string is going offline due to message advancing checkpoint

Cause:	The checkpoint in the file header could not be advanced. See accompanying messages for the reason. The data file will be taken offline the same as for a write message 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

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 DATA FILE 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

ORA-01173	data dictionary indicates missing data file from system tablespace

Cause:	Either:

 1) The database is recovered to a point in time in the future of the control file.

 2) A data file from the system tablespace is omitted from the issued CREATE CONTROLFILE statement.

Action:	Either:

 1) Recover the database from a more recent control file.

 2) Re-create the control file, ensuring all data files are included for the system tablespace in the command line.


ORA-01174

ORA-01174	DB_FILES is num but needs to be num to be compatible

Cause:	The maximum number of data files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

Action:	Change the value of the DB_FILES initialization parameter to be compatible.


ORA-01175

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

ORA-01176	data dictionary has more than the num files allowed by the controlfile

Cause:	After a CREATE CONTROLFILE statement, the data dictionary has more data files than supported by the control file.

Action:	Re-create the controlfile with a larger value for MAXDATA FILES.


ORA-01177

ORA-01177	data file does not match dictionary - probably old incarnation

Cause:	When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this data file 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 data file.

Action:	Do a CREATE CONTROLFILE with the correct file or none at all.


ORA-01178

ORA-01178	file name created before last CREATE CONTROLFILE, cannot re-create

Cause:	An attempt was made to use the ALTER DATABASE CREATE DATA FILE to re-create a data file 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

ORA-01179	file name does not exist

Cause:	During data file recovery, a file was listed that was not part of the database.

Action:	Recheck the file name. Remember to use double quotes at the SQL*DBA command line and remember that the file name is translated in the environment of SQL*DBA.


ORA-01180

ORA-01180	can not create data file 1

Cause:	Data file 1 cannot be created with the ALTERDATABASECREATEDATA FILE command.

Action:	Either recover the file from a backup, or re-create the database.


ORA-01181

ORA-01181	file name created before last RESETLOGS, cannot re-create

Cause:	An attempt was made to use the ALTER DATABASE CREATE DATA FILE command to re-create a data file 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

ORA-01182	cannot create data file name - file is in use or recovery

Cause:	An attempt was made to use the ALTER DATABASE CREATE DATA FILE command to re-create a data file 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

ORA-01183	cannot mount database in parallel mode

Cause:	The database is mounted in exclusive mode by another instance. It is not possible to mount a database in parallel mode if it is mounted in exclusive mode by another instance.

Action:	Shut down the other instance and try again.


ORA-01184

ORA-01184	logfile group num already exists

Cause:	An ALTER DATABASE ADD LOGFILE 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

ORA-01185	logfile group number num is invalid

Cause:	An ALTER DATABASE ADD LOGFILE command specified a redo log number for the new redo log which is too large.

Action:	Specify a valid redo log file number.


ORA-01186

ORA-01186	verification tests failed on file name

Cause:	The data file did not pass the checks to ensure it is part of the database. See the accompanying messages for the reason the verification did not succeed.

Action:	Make the correct file available to database. Then either open the database or do ALTER DATABASE CHECK.


ORA-01187

ORA-01187	can not read from file name because it failed verification tests

Cause:	The data file did not pass the checks to insure 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 do ALTER DATABASE CHECK.


ORA-01188

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

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 may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.

Action:	If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consist ant with the rest of the data files and resubmit the command.


ORA-01190

ORA-01190	control file or data file name is from before the last RESETLOGS

Cause:	An attempting was made to perform media recovery when the redo log reset information in a data file does not match the control file. Either the data file 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

ORA-01191	file name is already offline - cannot do a normal offline

Cause:	An attempt was made to take a tablespace offline normally, but the file named in the message is already offline.

Action:	Bring the data file online first, or use the IMMEDIATE option when taking the tablespace offline.


ORA-01192

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 resubmit the command with the newly found redo log files included in the command line.


ORA-01193

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

Action:	Find the correct version of the file, then retry media recovery.


ORA-01194

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

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 which 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 recovery.


ORA-01196

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

Cause:	A media recovery session failed while the named file was being recovered. The file is in an inconsistent state and no more recovery was successfully completed on this file.

Action:	Either apply more redo logs until the file is consistent, or restore the file from a backup again and repeat recovery.


ORA-01197

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 resubmit the command.


ORA-01198

ORA-01198	must specify size for 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:	Resubmit the command with the appropriate redo log file size.


ORA-01200

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 data file from a backup and perform recovery as needed.


ORA-01201

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 is probably corrupted.

Action:	Replace the corrupted file with a good copy and perform recovery as needed.


ORA-01202

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 data file and perform recovery as needed.


ORA-01203

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 data file and perform recovery as needed.


ORA-01204

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 data file and perform recovery as needed.


ORA-01205

ORA-01205	not a data file - type number in header is num

Cause:	The file type in the header is not correct for a data file. This is probably a redo log file or control file.

Action:	Restore a copy of the correct data file and perform recovery as needed.


ORA-01206

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 data file at all. If the database was rebuilt, this may be a file from before the rebuild.

Action:	Restore a copy of the correct data file and perform recovery as needed.


ORA-01207

ORA-01207	file is more recent than control file - old control file

Cause:	The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used.

Note:  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

ORA-01208	data file is an old version - not accessing current version

Cause:	The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just 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

ORA-01209	data file 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 onlined this file, 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

ORA-01210	data file header is media corrupt

Cause:	The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the 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 data file 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

ORA-01211	Version 6 data file is not from conversion to ORACLE7

Cause:	The file is not a copy of the file last used under Version6. When converting a database from Version 6 to ORACLE7, the conversion utility must be run the last time the database is opened under Version6. Only the data files that were current when the conversion was done may be accessed by ORACLE7. This data file is either a backup taken from before the conversion, or the database was opened by Version6 after the conversion.

Action:	Have the operating system make the correct data file available to the database, or repeat the Version 6 to ORACLE7 conversion.


ORA-01212

ORA-01212	MAXLOGMEMBERS may not exceed num

Cause:	The value specified for MAXLOGMEMBERS is too large.

Action:	Resubmit the command with a smaller value for MAXLOGMEMBERS.


ORA-01213

ORA-01213	MAXINSTANCES may not exceed num

Cause:	The value specified for MAXINSTANCES is too large.

Action:	Resubmit the command with a smaller value for MAXINSTANCES.


ORA-01214

ORA-01214	MAXLOGHISTORY may not exceed num

Cause:	The value specified for MAXLOGHISTORY is too large.

Action:	Resubmit the command with a smaller value for MAXLOGHISTORY.


ORA-01215

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

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 data files indicate that the thread should be disabled. This is probably due to the fact that 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. Resubmit the command without specifying the thread. If desired, the thread can be re-created after the database has been opened.


ORA-01217

ORA-01217	logfile 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

ORA-01218	logfile 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 pint 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

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:	Rephrase the query to include only fixed objects, or open the database.


ORA-01220

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, increase the SORT_AREA_SIZE parameter in the initialization parameter file to enable the sort to done in memory.


ORA-01221

ORA-01221	data file name is not the same file to a background process

Cause:	When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The 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 message it received when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process.


ORA-01222

ORA-01222	MAXINSTANCES of num requires MAXLOGFILES be at least num, not num

Cause:	Attempting to create 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

ORA-01223	RESETLOGS must be specified to set a new database nam

Cause:	The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.

Action:	Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.


ORA-01224

ORA-01224	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

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 resubmit the command.


ORA-01226

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:	The correct redo log member or omit this member from the command.


ORA-01227

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 since 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

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:	command with the SET DATABASE and RESETLOGS options.


ORA-01229

ORA-01229	data file name is inconsistent with logs

Cause:	The data file 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:	the correct online redo logs or use the RESETLOGS option.

________________________________________


01400-01489: SQL Execution

This section lists messages generated during SQL execution.


ORA-01400

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

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

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 into the underlying table rather than through the view.


ORA-01403

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

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 re-created if to do so would exceed the maximum index width.


ORA-01405

ORA-01405	fetched column value is NULL

Cause:	In an OCI program, a FETCH operation returned a NULL column value. The column buffer in the program remained unchanged and the cursor return code was +2.

Action:	Include program processing for this condition. This is only a warning.


ORA-01406

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

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

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

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. For non-unique indexes the ROWID is considered part of the index key. Therefore, if you create an index NOSORT and two of the rows in the table have the same key and are stored in ascending order, but get split across two extents where the data block address (dba) of the first block in the second extent is less than the data block address of the last block in the first extent, then the create index NOSORT may fail.

Action:	Create the index without the NOSORT option, or ensure table is stored in one extent.


ORA-01410

ORA-01410	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 '0001.000001F8.0006'.

Action:	Check the format, then enter the ROWID using the correct format.


ORA-01411

ORA-01411	cannot store the length of column in the indicator

Cause:	ORACLE tried to fetch a column more than 64K long and couldn't 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

ORA-01412	zero length not allowed for this datatype

Cause:	The length for data type 97 is 0.

Action:	Specify the correct length for the datatype.


ORA-01413

ORA-01413	illegal value in packed decimal number buffer

Cause:	The user buffer bound by the user as packed decimal number contained an illegal value.

Action:	Use a legal value.


ORA-01414

ORA-01414	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-01415

ORA-01415	outer-join (+) may not be applied to the label pseudo column

Cause:	The user specified an outer-join (+) following a reference to the label pseudo column.

Action:	Work around the problem by defining a view on the table and perform an outer join on the view column corresponding to a label.


ORA-01416

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

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

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-01419

ORA-01419	datdts: illegal format code

Cause:	During a date-to-character conversion, the internal representation of the conversion format was invalid. This is an internal message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01420

ORA-01420	datstd: illegal format code

Cause:	During a character-to-date conversion, the internal representation of the conversion format was invalid. This is an internal message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01421

ORA-01421	datrnd/dattrn: illegal precision specifier

Cause:	During a date truncate or round operation, the internal representation of the date precision was invalid. This is an internal message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01422

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

ORA-01423	message encountered while checking for extra rows in exact fetch

Cause:	An message was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages.

Action:	Take the appropriate action for the messages that follow.


ORA-01424

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 escape characters '%' or '_'.

Action:	Remove the escape character or specify the missing character.


ORA-01425

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

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 few operands than the 'overloaded' expression.


ORA-01427

ORA-01427	single-row query 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

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:	Refer to Chapter 4 of the ORACLE7 Server SQL Language Reference Manual for valid input and ranges of the mathematical functions.


ORA-01430

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

ORA-01431	internal inconsistency in GRANT command

Cause:	An internal message occurred while attempting to execute a GRANT statement.

Action:	Contact Worldwide Customer Support.


ORA-01432

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

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

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

ORA-01435	user does not exist

Cause:	This message is caused by any reference to a nonexistent 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

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

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

ORA-01438	value larger than specified precision allows for this column

Cause:	When inserting or updating records, a value was entered that exceeds the column width.

Action:	Enter a smaller value, or use the MODIFY option to increase the column width.


ORA-01439

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. In order to alter a column's datatype, the column must only contain NULL values.

Action:	To alter the datatype, first set all values in the column to NULL.


ORA-01440

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

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. In order to decrease the maximum size of a character column, the column must contain only NULL values.

Action:	Set all values in column to NULL before decreasing the maximum size.


ORA-01442

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 user action is required.


ORA-01443

ORA-01443	internal inconsistency; illegal datatype in resultant view column

Cause:	An internal message occurred in referencing a view.

Action:	Contact Worldwide Customer Support.


ORA-01444

ORA-01444	internal inconsistency; internal datatype maps to invalid external type

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01445

ORA-01445	cannot select ROWID from view of more than one 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

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

ORA-01447	ALTER TABLE does not operate on clustered columns

Cause:	An ALTER TABLE MODIFY statement specified a column that is used to cluster the table. Clustered columns may not be altered.

Action:	To alter the column, first re-create the table in non-clustered form. The column's size can be increased at the same time.


ORA-01448

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 and hence the index must be dropped before the modification.

Action:	Drop all indexes referencing the column before changing its datatype to LONG.


ORA-01449

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

ORA-01450	maximum key length exceeded

Cause:	The combined length of all the columns specified in a CREATE INDEX statement exceeds 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.

Action:	Select columns to be indexed so the total index length does not exceed the maximum index length for the operating system.


ORA-01451

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

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

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

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

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

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

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

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

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

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

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

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

ORA-01463	cannot modify column datatype with current constraints

Cause:	An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa.

Action:	Remove the constraint(s) or do not perform the offending operation.


ORA-01464

ORA-01464	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

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

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:

•	the query was parsed and executed with a snapshot older than the time the object was changed

•	the creation time-stamp of the object is greater than the current system time. This happens, for example, when the system time is set to a time earlier than the creation time of the object.

Action:	If the cause is:

•	an old snapshot, then commit or rollback the transaction and resume work.

•	a creation time-stamp in the future, then:

•	ensure the system time is correctly set

•	if the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, re-create the object (so it has a new creation time-stamp), import the object's data, and resume work.


ORA-01467

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

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

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

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 an object that he/she owns.

Action:	Choose a different synonym name, or create the synonym under a different username.


ORA-01472

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

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

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

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

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

ORA-01477	user data area descriptor is too large

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01478

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

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

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

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

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

ORA-01483	invalid length for DATE or NUMBER bind variable

Cause:	A bind variable of type DATE or NUMBER is too long.

Action:	Check the installation or user's guide for the maximum allowable length.


ORA-01484

ORA-01484	arrays can only be bound to PL/SQL statements

Cause:	You tried to bind an array to a non-PL/SQL statement.


ORA-01485

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.


ORA-01486

ORA-01486	size of array element is too large

Cause:	You tried to bind a data value which was either too large for the datatype (for example, NUMBER) or was greater than 2000 bytes (for example, VARCHAR or LONG).


ORA-01487

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

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

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

This section lists miscellaneous messages generated by among others, the ANALYZE command, SQL parser, and during the execution of ORACLE commands.


ORA-01490

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

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

ORA-01492	LIST option not valid

Cause:	The LIST option can only be used for tables or clusters.


ORA-01493

ORA-01493	invalid SAMPLE size specified

Cause:	The specified SAMPLE size is out of range

Action:	Specify a value within the proper range.


ORA-01495

ORA-01495	specified chain row table not found

Cause:	The specified table either 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

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

ORA-01497	unable to initialize statistics scan - see trace file.

Cause:	The first block checked in the object from the ANALYZE ... STATISTICS command was found to be corrupted.

Action:	Check the trace file for more descriptive messages about the problem. Correct these messages. The name of the trace file is operating system specific (for example, ORAxxxx.TRC) and 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 re-create the object.


ORA-01498

ORA-01498	block Check Failure - see trace file

Cause:	An message occurred while checking a block with the ANALYZE command.

Action:	Check the trace file for more descriptive messages about the problem. Correct these messages. The name of the trace file is operating system specific (for example, ORAxxxx.TRC) and 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 re-create the object.


ORA-01499

ORA-01499	table/Index Cross Reference Failure - see trace file

Cause:	An message 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 messages. The name of the trace file is operating system specific (for example, ORAxxxx.TRC) and 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 re-create the object.


01500-02099:Oracle7 Server Oracle Commands

This section lists messages that might be generated by the Oracle7 Server when issuing ORACLE commands.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-01500

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 Worldwide Customer Support.


ORA-01501

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

ORA-01502	index 'str.name' is in direct load state

Cause:	The specified index had been marked invalid by a direct load.

Action:	Drop the specified index.


ORA-01503

ORA-01503	CREATE CONTROLFILE failed

Cause:	An error occurred during CREATE CONTROLFILE.

Action:	See accompanying messages.


ORA-01504

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 gi

Cause:	ven 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

ORA-01505	error in adding logfiles

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

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

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, re-issue the ALTER DATABASE command specifying the MOUNT option.


ORA-01508

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 Worldwide Customer Support.


ORA-01509

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

ORA-01510	error in deleting logfiles

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

ORA-01511	error in renaming log/data files

Cause:	In executing an ALTER DATABASE statement, an error occurred while renaming log or data files.

Action:	Check the accompanying message stack for detailed information.


ORA-01512

ORA-01512	error renaming logfile '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:	Make sure that the redo log file has been properly renamed by the operating system and retry.


ORA-01513

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

ORA-01514	error in log specification; no such log

Cause:	A redo log file name, 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

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

ORA-01516	nonexistent log/data file 'name'

Cause:	An ALTER DATABASE statement is attempting to rename a log file or a data file 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

ORA-01517	log member: 'str'

Cause:	This message indicates the file name involved with other messages.

Action:	See the associated messages.


ORA-01518

ORA-01518	CREATE DATABASE must specify more than one logfile

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

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 Worldwide Customer Support.


ORA-01520

ORA-01520	number of data files 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, re-create the database with a larger value of MAXDATAFILES.


ORA-01521

ORA-01521	error in adding data files

Cause:	During a CREATE or ALTER TABLESPACE, an error was detected while adding data files.

Action:	Check the accompanying message stack for detailed information.


ORA-01522

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 file name, then re-execute the statement.


ORA-01523

ORA-01523	cannot rename data file 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 being used as part of the database.


ORA-01524

ORA-01524	cannot create data file 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 used in the database.


ORA-01525

ORA-01525	error in renaming data files

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

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 Worldwide Customer Support.


ORA-01527

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 Worldwide Customer Support.


ORA-01528

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 Worldwide Customer Support.


ORA-01529

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 Worldwide Customer Support.


ORA-01530

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

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 is 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

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 Worldwide Customer Support.


ORA-01533

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 file name and tablespace name.


ORA-01534

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

ORA-01535	rollback segment 'name' already exists

Cause:	The specified rollback segment already exists.

Action:	Correct syntax and spelling, and correctly specify the rollback segment name, or specify a different rollback segment.

ORA-e01536	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:

 1) Drop unnecessary objects in the tablespace to reclaim space.

 2) Ask the database administrator to increase the tablespace quota.


ORA-01537

ORA-01537	cannot add data file '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 data file name, or use a different file.


ORA-01538

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:	Make sure 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

ORA-01539	tablespace 'name' is not online

Cause:	An attempt was made to bring a tablespace offline normally, but it is not online.

Action:	Check the status of the tablespace, use IMMEDIATE or TEMPORARY options to force all files offline.  Also, the database must be in ARCHIVELOG mode.


ORA-01540

ORA-01540	tablespace 'name' is not offline

Cause:	A tablespace could not be brought online because it is not offline.

Action:	Check the status of the tablespace, then retry the operation.


ORA-01541

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

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

ORA-01543	tablespace 'name' already exists

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

When Trusted ORACLE is configured in DBMS MAC mode, it is possible to get this error if you attempt to create a tablespace using a name that was previously used by another tablespace. In DBMS MAC mode, it is not possible to reuse tablespace names, even if the old tablespace has been dropped.

Action:	Use a different name for the new tablespace.


ORA-01544

ORA-01544	cannot drop system rollback segment

Cause:	An attempt was made to drop the rollback segment SYSTEM.

Action:	No user action is required.


ORA-01545

ORA-01545	rollback segment #'name' was not available

Cause:	Either:

 1) A non-existent rollback segment was specified.

 2) An instance tried to acquire a rollback segment that is in use or offline.

 3) An attempt was made to drop a rollback segment that contains active transactions.

Action:	Either:

 1) Check spelling and specify a valid rollback segment name. If the name of the rollback segment to be changed is unknown, reopen the database and query the data dictionary for the names of existing rollback segments.

 2) To start up an instance that tried to acquire this rollback segment, specify another rollback segment in the initialization parameter ROLLBACK_SEGMENTS or bring the tablespace containing the rollback segment online.

 3) To drop a rollback segment that is in use, shut down the instance using it; or if it needs recovery, find out the errors that are preventing the rolling back of the transactions, and take appropriate actions.


ORA-01546

ORA-01546	tablespace contains active rollback segment 'name'

Cause:	An attempt was made to bring offline a tablespace that contains active rollback segments.

Action:	Make sure there are no active rollback segments in the tablespace to be brought offline, then retry the operation.


ORA-01547

ORA-01547	failed to allocate extent of size num in tablespace 'name'

Cause:	The tablespace does not have enough free space to allocate the requested extent of num ORACLE blocks. Either:

 1) Too many temporary segments are in the tablespace, or the temporary segments are too large.

 2) Current extents are not big enough because of disk fragmentation.

Action:	Either:

 1) Create another tablespace for temporary segments.

 2) For fragmentation, decrease the PCTINCREASE initialization parameter value because it is too high. If there is still not enough room in the tablespace, use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated, or create the object in another tablespace if this happens during a CREATE statement.


ORA-01548

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

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

ORA-01550	cannot drop system tablespace

Cause:	An attempt was made to drop the tablespace SYSTEM.

Action:	No user action is required.


ORA-01551

ORA-01551	extended rollback segment, pinned blocks released

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01552

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 private or public rollback segments, shut down the database, then start up again. 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. To activate a rollback segment, shut down the database, modify the initialization parameter file, and restart.


ORA-01553

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

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

ORA-01555	snapshot too old (rollback segment too small)

Cause:	Rollback records needed by a reader for consistent read were overwritten by other writers.

When Trusted ORACLE is configured in OS MAC mode, it is possible to get this error if the interval between checkpoints in a secondary database is too small, causing necessary rollback records to be overwritten.

Action:	To prevent the recurrence of this error, specify larger rollback segments.

For Trusted ORACLE users, if the cause of this error is that the necessary rollback records in an OS MAC secondary database were overwritten, decrease the value of the LOG_CHECKPOINT_TIMEOUT initialization parameter so that checkpoints are taken more frequently.


ORA-01556

ORA-01556	MINEXTENTS for rollback segment must be greater than 1

Cause:	A MINEXTENTS of less than 2 was specified for rollback segment.

Action:	Specify a larger MINEXTENTS.


ORA-01557

ORA-01557	rollback segment extents must be at least 3 blocks

Cause:	An extent of less than three blocks was specified for the rollback segment.

Action:	Specify extents of at least three blocks, then retry the operation.


ORA-01558

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

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

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

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

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

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

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

ORA-01565	message in identifying file 'name'

Cause:	An message occurred while trying to identify a file.

Action:	Check the accompanying message stack for detailed information.


ORA-01566

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

ORA-01567	dropping log name would leave less than two logfiles in thread num

Cause:	Dropping all the files specified would leave fewer than the required two redo log files.

Action:	Either drop fewer logs or disable the thread before deleting the logs.


ORA-01568

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

ORA-01569	data file too small for system dictionary tables

Cause:	The data file 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

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

ORA-01571	redo version ver incompatible with ORACLE Version ver

Cause:	This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.

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


ORA-01572

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 system-wide rollback segments is specified by the GC_ROLLBACK_SEGMENTS parameter. When this maximum is reached, no more requests are processed.

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

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 user action is required.


ORA-01574

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

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

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

ORA-01577	cannot add logfile '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 file name, and try again.


ORA-01578

ORA-01578	ORACLE data block corrupted (file # num, block # num)

Cause:	The given data block was corrupted, probably as a result of program errors.

Action:	Try to restore the segment containing the given data block. This may involve dropping the segment and re-creating it. If there is a trace file, report the messages recorded in it to Worldwide Customer Support.


ORA-01579

ORA-01579	write message occurred during recovery

Cause:	A write message occurred during media recovery.

Action:	Check the trace file for the type of the write message, then take appropriate action.


ORA-01580

ORA-01580	message creating control backup file 'name'

Cause:	An operating system message 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-01582

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

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

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

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

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

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

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

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

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

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

ORA-01592	message converting Version 6 rollback segment 'num' to ORACLE7 form

Cause:	ORACLE encountered an message while converting a Version6 rollback segment into the format used by ORACLE7.

Action:	Investigate the accompanying internal error message. The Version6 database may not have shut down cleanly. It may be necessary to reload the Version6 database from backup and shut it down ensuring it shuts down cleanly.


ORA-01593

ORA-01593	rollback segment optimal size (num blocks) is smaller than 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

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 and/or too many extents to free.

Action:	The rollback segment shrinking will be rolled back by the system, increase the optimal size of the rollback segment.


ORA-01595

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

ORA-01596	fail to coalesce extents because sort area size is too small

Cause:	There are too many entries of free extents to sort it in the in-memory sort area.

Action:	Increase the sort area size or reduce the fragmentation in the tablespace by doing a full export followed by an import.


ORA-01597

ORA-01597	cannot alter system rollback segment online or offline

Cause:	An attempt was made to online or offline the SYSTEM rollback segment.

Action:	None.


ORA-01598

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

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

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

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:	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-01602

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

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:

GC_FILES_TO_LOCKS = "{filenum[-filenum] [,filenum[-filenum]]...=  num_of_locks[EACH]}[:]..."

where filenum is a file number (as listed in V$DBFILE) and num_of_locks is the number of PCM locks.


ORA-01604

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

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]}[:]..."

Spaces are not allowed within the double quotation marks.

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

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

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

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

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.


ORA-01610

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 re-created 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

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

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

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

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

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

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

ORA-01617	num is not a valid thread number - cannot mount

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

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

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

ORA-01620	no public threads are available for mounting

Cause:	The initialization parameter THREAD is zero, its default value. There are no available threads which have been publicly enabled.

Action:	Shut down the instance, change the initialization parameter to a thread which 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

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

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 at. Since 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

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

ORA-01624	log name needed for crash recovery of thread num - cannot drop

Cause:	A log can not be dropped until the thread's checkpoint has advanced out of the log.

Action:	If the database is not open, open it. Crash recovery will advance the checkpoint. If the database is open, force a global checkpoint.


ORA-01625

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:	Only take rollback segments offline that belong to the current instance. To take the rollback segment offline, connect to the instance containing it.


ORA-01626

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

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

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.

Action:	If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters.


ORA-01629

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

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.

Action:	If possible, increase the value of either the MAXEXTENTS or PCTINCREASE initialization parameters.


ORA-01631

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

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

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

ORA-01634	rollback segment number 'string' is about to go offline

Cause:	The rollback segment specified was marked to go offline by DBA.

Action:	Bring the rollback segment online before continuing.


ORA-01635

ORA-01635	rollback segment #num specified not available

Cause:	Either:

 1)  You tried to acquire an offline rollback segment during start up.

 2)  You tried to drop a rollback segment that contains active transactions.

Action:	For the above, do either:

 1)  Bring the tablespace containing the rollback segment online or do not specify the rollback segment in initialization parameter file.

 2)  If the rollback segment is in use, shut down the instance using rollback segment, else if the rollback segment needs recovery, find out the errors that are holding back the rolling back of the transactions and take appropriate actions.


ORA-01636

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 incurring 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 Parallel Server Administrator's Guide for more information about using rollback segments in parallel mode.


ORA-01637

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:	See ORA-01636.


ORA-01638

ORA-01638	init parameter does not allow ORACLE Version ver 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

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.

________________________________________


01700-01799: SQL Parsing

This section lists some of the messages generated when SQL statements are parsed by the ORACLE Server. Most, but not all, messages in this section indicate incorrect SQL syntax. For SQL syntax and refer to the ORACLE7 Server SQL Language Reference Manual.


ORA-01700

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, then re-execute the statement.


ORA-01701

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

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

ORA-01703	missing SYNONYM keyword

Cause:	The keyword SYNONYM is required in this context.

Action:	Check the statement syntax, then insert the keyword SYNONYM.


ORA-01704

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

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:	Reword or reform the query. Refer to the syntax for subqueries. The outer-join indicator may only follow columns in the same query block in which their table is included in the FROM clause.


ORA-01706

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

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 and insert the keyword LIST where required, then re-execute the statement.


ORA-01708

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

ORA-01709	program does not exist

Cause:	This feature is not currently implemented.

Action:	No user action is required.


ORA-01710

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

ORA-01711	duplicate privilege listed

Cause:	A privilege was listed twice in a GRANT or REVOKE statement. A privilege may only be specified once in these statements.

Action:	Remove the duplicate privilege from the list, then re-execute the statement.


ORA-01712

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 only grant privileges that the grantor has or is authorized to grant.

Action:	Either:

 1) Specify only authorized privileges in the GRANT statement.

 2) Ask the database administrator to grant the user the required privileges.

 3) Ask the database administrator for the required privileges and then grant the other user the privileges.


ORA-01713

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

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

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, then re-execute the statement.


ORA-01716

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 and remove the keyword NOSORT from the CREATE INDEX statement, then re-execute the statement.


ORA-01717

ORA-01717	seccta: invalid access mode token passed

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01718

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

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

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-01722

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; make sure they contain only numbers, a sign, a decimal point, and the character "E" or "e", then retry the operation.


ORA-01723

ORA-01723	zero-length columns are not allowed

Cause:	During CREATE TABLE, a zero-length column was specified (CHAR(0), for example).

Action:	Correct the column declaration so that length is at least 1 and try the operation again.


ORA-01724

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-01726

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

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, then re-execute the statement.


ORA-01728

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

ORA-01729	database link name expected

Cause:	A database link name does not follow the "@" in a reference to a table in a remote database.

Action:	Correct the reference, then retry the operation. The correct syntax for denoting a table in a remote database follows:

username.table_name@ database_name

Spaces before and after the at-sign are optional.


ORA-01730

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

ORA-01731	circular view definition encountered

Cause:	Through a series of CREATE and DROP VIEW statements, a view became defined in terms of 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 and remove any circular references, then re-execute the statements.


ORA-01732

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

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-01735

ORA-01735	invalid ALTER TABLE option

Cause:	An invalid option was specified in an ALTER TABLE statement.

Action:	Check the statement syntax and specify a valid option and then re-execute the statement.


ORA-01736

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, then re-execute the statement.


ORA-01737

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

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, then re-execute the statement.


ORA-01739

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 and insert the keyword MODE where required, then re-execute the statement.


ORA-01740

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

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-01743

ORA-01743	internal inconsistency; illegal user function index

Cause:	This is not currently implemented.

Action:	No user action is required.


ORA-01744

ORA-01744	inappropriate INTO

Cause:	The INTO clause may not be used in a subquery.

Action:	Check the syntax and place the INTO clause in the top-level query, then re-execute the statement.


ORA-01745

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, then retry the operation.


ORA-01746

ORA-01746	indicator variable not permitted here

Cause:	An indicator variable is not permitted in this context.

Action:	Remove the indicator variable, then retry the operation.


ORA-01747

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 and especially references to column names, then re-execute the statement.


ORA-01748

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, then retry the operation.


ORA-01749

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

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, then GRANT the user privileges for specific columns.


ORA-01753

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

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, then retry the operation.


ORA-01756

ORA-01756	quoted string not properly terminated

Cause:	A quoted string must be terminated with a single quote mark (').

Action:	Insert the closing quote, then re-execute the statement.


ORA-01758

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:	Re-issue the statement without the NOT NULL specification.


ORA-01759

ORA-01759	user function is incorrectly defined

Cause:	A user function has been improperly defined.

Action:	Contact Worldwide Customer Support.


ORA-01760

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-01762

ORA-01762	vopdrv: view query block not in FROM

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-01765

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:	Verify that the object is identified correctly, and if necessary remove the period from the name.


ORA-01766

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

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

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

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, then re-execute the statement.


ORA-01770

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

ORA-01771	illegal option for a clustered table

Cause:	CLUSTER option conflicts with MAXTRANS option.

Action:	Choose one option and re-execute the statement.


ORA-01773

ORA-01773	may not specify column datatypes in this CREATE TABLE

Cause:	Column datatypes were specified in a SELECT statement used to directly create and load a table.

Action:	Remove column datatypes. The datatypes of the SELECT list expressions are automatically used as the column datatypes.


ORA-01775

ORA-01775	looping chain of synonyms

Cause:	Through a series of CREATE synonym statements, a synonym was defined in terms of 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, then retry the operation.


ORA-01777

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

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-01780

ORA-01780	string literal required

Cause:	In a COMMENT statement, the comment following the keyword IS must be a quoted string literal.

Action:	Make sure the comment is a string literal.


ORA-01785

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, then re-execute the statement.


ORA-01786

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 and remove the FOR UPDATE clause, then re-execute the statement.


ORA-01787

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 then re-execute the statement.


ORA-01788

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 and specify a CONNECT BY clause, and then re-execute the statement.


ORA-01789

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:	Make sure all the queries in the set expression have the same number of SELECT list columns.


ORA-01790

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:	Make sure all corresponding SELECT list items have the same datatypes. The functions TO_NUMBER, TO_CHAR, and TO_DATE can be used to do explicit data conversions.


ORA-01791

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 either 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, then re-execute the statement.


ORA-01792

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

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

ORA-01794	maximum number of cluster columns is 16

Cause:	More than sixteen 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

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

ORA-01796	this operator cannot be used with lists

Cause:	A relational operator is not allowed in this context. When comparing lists, only use 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))

It may be necessary to compare individual columns separately. For example, to see if A and B are respectively greater than C and D, use WHERE A>B AND C>D instead of WHERE (A,B)>(C,D).


ORA-01797

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 adding ANY or ALL where appropriate.


ORA-01798

ORA-01798	missing EXCEPTION keyword

Cause:	The EXCEPTION keyword is missing from the ENABLE clause.

Action:	Refer to the ORACLE7 Server SQL Language Reference Manual for the appropriate syntax of the ENABLE clause.


ORA-01799

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 make a view out of the subquery.

________________________________________


01800-01899: The Date Function

This section lists messages generated when the ORACLE date function is naccessed.


ORA-01800

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

ORA-01801	date format is too long for internal buffer

Cause:	The date format string was too long to process. This should only occur if several long literals are specified as part of a date.

Action:	Remove long literals from the date format string.


ORA-01802

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

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 Worldwide Customer Support.


ORA-01810

ORA-01810	format code appears twice

Cause:	A format code was listed twice in a date specification. Each format code may only be specified once in the function TO_DATE.

Action:	Remove the duplicate format code from the date specification, then retry the operation.


ORA-01811

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

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

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

ORA-01814	AM/PM conflicts with use of A.M./P.M.

Cause:	Both types of meridian indicator 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:	Remove one type of meridian indicator from the date.


ORA-01815

ORA-01815	BC/AD conflicts with use of B.C./A.D.

Cause:	Both types of BC/AD indicator 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:	Remove one type of BC/AD indicator from the date specification.


ORA-01816

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

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

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/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

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

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

ORA-01821	date format not recognized

Cause:	A date specification contained an invalid format code.

Action:	Ensure only valid date format codes are specified.


ORA-01830

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

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 correct year for the Julian date.


ORA-01832

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

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 correct month for the Julian date.


ORA-01834

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

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

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

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

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

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

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

ORA-01841	(full) year must be between -4713 and +4713

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

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

ORA-01843	not a valid month

Cause:	A date specified an invalid month. Valid months are: January-December (for format code MONTH), Jan-Dec (for format code MON).

Action:	Enter a valid month value in the correct format.


ORA-01844

ORA-01844	week of year must be between 1 and 52

Cause:	An invalid value was specified for 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

ORA-01845	week of month must be between 1 and 5

Cause:	An invalid value was specified for 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

ORA-01846	not a valid day of the week

Cause:	A date specified an invalid day of the week. Valid days are: Monday-Sunday (for format code DAY); Mon-Sun (for format code DY); and 1-7 (for format code D).

Action:	Enter a valid day of the week value in the correct format.


ORA-01847

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

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

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

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

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

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

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

ORA-01854	Julian date must be between 1 and 3442447

Cause:	An invalid Julian date was entered.

Action:	Correct and retry.


ORA-01855

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

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

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

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

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

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

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 (with the exception of 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

ORA-01862	wrong number of digits for this format item

Cause:	The number of digits used for 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

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

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

This section lists some of the messages generated when SQL statements are parsed by the ORACLE Server.


ORA-01900

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

ORA-01901	ROLLBACK keyword expected

Cause:	The keyword ROLLBACK is required in this context.

Action:	Check the syntax, insert the keyword ROLLBACK where required, then re-execute the statement.


ORA-01902

ORA-01902	SEGMENT keyword expected

Cause:	The keyword SEGMENT is required in this context.

Action:	Check the syntax, insert the keyword SEGMENT where required, then re-execute the statement.


ORA-01903

ORA-01903	EVENTS keyword expected

Cause:	The keyword EVENTS is required in this context.

Action:	Check the syntax, insert the keyword EVENTS where required, then re-execute the statement.


ORA-01904

ORA-01904	DATAFILE keyword expected

Cause:	The keyword DATAFILE is required in this context.

Action:	Check the syntax, insert the keyword DATAFILE where required, then re-execute the statement.


ORA-01905

ORA-01905	STORAGE keyword expected

Cause:	The keyword STORAGE is required in this context.

Action:	Check the syntax, insert the keyword STORAGE where required, then re-execute the statement.


ORA-01906

ORA-01906	BACKUP keyword expected

Cause:	The keyword BACKUP is required in this context.

Action:	Check the syntax, insert the keyword BACKUP where required, then re-execute the statement.


ORA-01907

ORA-01907	TABLESPACE keyword expected

Cause:	The keyword TABLESPACE is required in this context.

Action:	Check the syntax, insert the keyword TABLESPACE where required; then re-execute the statement.


ORA-01908

ORA-01908	EXISTS keyword expected

Cause:	The keyword EXISTS is required in this context.

Action:	Check the syntax, insert the keyword EXISTS where required, then re-execute the statement.


ORA-01909

ORA-01909	REUSE keyword expected

Cause:	The keyword REUSE is required in this context.

Action:	Check the syntax, insert the keyword REUSE where required, then re-execute the statement.


ORA-01910

ORA-01910	TABLES keyword expected

Cause:	The keyword TABLES is required in this context.

Action:	Check the syntax, insert the keyword TABLES where required, then re-execute the statement.


ORA-01911

ORA-01911	CONTENTS keyword expected

Cause:	The keyword CONTENTS is required in this context.

Action:	Check the syntax, insert the keyword CONTENTS where required, then re-execute the statement.


ORA-01912

ORA-01912	ROW keyword expected

Cause:	The keyword ROW is required in this context.

Action:	Check the syntax, insert the keyword ROW where required, then re-execute the statement.


ORA-01913

ORA-01913	EXCLUSIVE keyword expected

Cause:	The keyword EXCLUSIVE is required in this context.

Action:	Check the syntax, insert the keyword EXCLUSIVE where required, then re-execute the statement.


ORA-01914

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 not 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

ORA-01915	invalid auditing option for views

Cause:	AUDIT or NOAUDIT on a view specifies an auditing option that is legal for tables but not 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

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; then re-execute the statement.


ORA-01917

ORA-01917	user or role 'name' does not exist

Cause:	An invalid user or role name was specified.

Action:	Ensure a valid user or role name is used.


ORA-01918

ORA-01918	user name does not exist

Cause:	The user name specified cannot be found in the system.

Action:	Ensure a valid user or role name is used.


ORA-01919

ORA-01919	role 'name' does not exist

Cause:	An invalid role name was specified.

Action:	Ensure a valid role name is specified.


ORA-01920

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

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

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

ORA-01923	CASCADE aborted, objects locked by another user

Cause:	A CASCADE operation was aborted because the user specified 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

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 enable a subrole; or the grantor did not have the SET ROLE system privilege.

Action:	To use the SET ROLE command, ensure the grantor has the SET ROLE system privilege and is granted the role desired to be passed on.


ORA-01925

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

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

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

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:	Ensure grantor has the GRANT OPTION for privileges to be granted to a user or role.


ORA-01929

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:	Ensure the grantor has the necessary privileges via the GRANT OPTION and try again.


ORA-01930

ORA-01930	no privileges to REVOKE

Cause:	Grantor attempted to revoke privileges using the object privilege ALL, but does not have the necessary privileges.

Action:	Ensure grantor has the necessary privileges via the GRANT OPTION and try again.


ORA-01931

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

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

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

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 the ORACLE7 Server SQL Language Reference Manual for more detail.

Action:	Analyze the role and user structure to be used and ensure no attempt is made to grant roles circularly.


ORA-01935

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

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

ORA-01937	invalid role name

Cause:	An invalid role name was specified.

Action:	Choose a different role name.


ORA-01938

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

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 by 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

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 off; then re-execute the command.


ORA-01941

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

ORA-01942	IDENTIFIED BY and EXTERNALLY cannot both be specified

Cause:	A user was specified with an ORACLE password and as identified externally.

Action:	Specify only one of these options. For details and syntax, see the ORACLE7 Server SQL Language Reference Manual.


ORA-01943

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

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

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

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 desire, change the user's tablespace later with an ALTER USER statement.


ORA-01947

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 desire, change the user's tablespace later with an ALTER USER statement.


ORA-01948

ORA-01948	invalid DEFAULT ROLE specification

Cause:	An invalid role name was specified.

Action:	Make sure that the role name is correct.


ORA-01949

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], etc.

Action:	Check syntax and try again. For syntax rules, see the ORACLE7 Server SQL Language Reference Manual.


ORA-01950

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

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:	Ensure the user has the role.


ORA-01952

ORA-01952	system privileges not granted to 'name'

Cause:	An attempt was made to revoke a system privilege not granted to the user.

Action:	Ensure the user has the system privilege.


ORA-01953

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

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

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.

Note:  Subroles cannot be specified in a DEFAULT ROLE clause.

Action:	Ensure the user is granted the role before specifying it as the default.


ORA-01956

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. Refer to the operating system documentation for more information.


ORA-01966

ORA-01966	must have OS DBA privilege to CREATE CONTROLFILE

Cause:	The user issuing the CREATE CONTROLFILE statement does not have the appropriate operating system privilege.

Action:	This command can only be issued by a user with the appropriate operating system privilege.


ORA-01967

ORA-01967	invalid option for CREATE CONTROLFILE

Cause:	An invalid CREATE CONTROLFILE option is present.

Action:	Specify only valid CREATE CONTROLFILE options.


ORA-01968

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:	Be sure to specify RESETLOGS or NORESETLOGS exactly once.


ORA-01969

ORA-01969	must specify RESETLOGS or NORESETLOGS

Cause:	The RESETLOGS or NORESETLOGS option is missing from the CREATE CONTROL FILE statement.

Action:	Be sure to specify RESETLOGS or NORESETLOGS on the command line.


ORA-01970

ORA-01970	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

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 resubmit it.


ORA-01974

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 resubmit it.


ORA-01975

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

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 resubmit the command.


ORA-01977

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 resubmit it.


ORA-01978

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 resubmit it.


ORA-01979

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

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

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

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

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

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 default for procedures, packages, and functions is EXECUTE. Do not specify any option other than EXECUTE.


ORA-01985

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 Oracle Corporation to upgrade your site license.


ORA-01986

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

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

ORA-01988	remote O/S logon is not allowed

Cause:	Remote O/S login attempted when not allowed.

Action:	Use a local client, or use the REMOTE_OS_AUTHENT initialization parameter to turn on remote O/S logon.


ORA-02000

ORA-02000	missing keyword 'name'

Cause:	The statement entered requires the missing keyword.

Action:	Use the specified keyword.


ORA-02002

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

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

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 user action is required.


ORA-02005

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

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-02008

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 0; then retry the operation.


ORA-02009

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

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

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

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

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

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

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 on or connect directly to the remote database before entering a SELECT ... FOR UPDATE on its tables.


ORA-02016

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 a subquery in the START WITH clause can be used.


ORA-02017

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

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

ORA-02019	connection description for remote database not found

Cause:	The user attempted to connect or log on 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. Check your operating system specific SQL*Net documentation for valid connection descriptors.


ORA-02020

ORA-02020	too many database links in use

Cause:	The maximum number of active connections to remote databases per user logon 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.

If this occurs often, consider increasing a the value of the initialization parameter OPEN_LINKS, which controls the maximum number of concurrent open connections to remote databases per user process.


ORA-02021

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

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

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

ORA-02024	database link not found

Cause:	Database link to be dropped is not found in dictionary.

Action:	Correct the database link name.


ORA-02025

ORA-02025	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 only be performed if all databases in the SQL statement are ORACLE7 Servers. Update the earlier version databases in a separate statement.


ORA-02026

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

ORA-02027	multi-row UPDATE of LONG column is not supported

Cause:	A bind variable with length greater than 2000 bytes is being used to update a column, and the UPDATE statement affects more than one row.

Action:	Ensure such a bind variable only updates a single row.


ORA-02028

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

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

ORA-02030	can only select from fixed tables/views

Cause:	An operation other than SELECT on a fixed table (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

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

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

ORA-02033	a cluster index for this cluster already exists

Cause:	A cluster index already exists for the cluster.

Action:	No user action is required.


ORA-02034

ORA-02034	speed bind not permitted

Cause:	Speed bind not allowed with supplied bind variables.

Action:	None.


ORA-02035

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

ORA-02036	too many variables to describe with automatic cursor open

Cause:	UPI bundled execution call requested 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

ORA-02037	uninitialized 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

ORA-02038	define is not allowed for array type

Cause:	A user attempted to define a select list variable of type "array". Arrays may only serve as host bind variables.


ORA-02039

ORA-02039	bind by value is not allowed for array type

Cause:	User attempted to bind an array host variable by value. Arrays may only be bound by reference.

________________________________________


02040-02099: Distributed Transactions

This section lists messages generated during distributed transactions.


ORA-02040

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 only be performed if all databases support the two-phase commit mechanism.


ORA-02041

ORA-02041	client database did not begin a transaction

Cause:	This is an internal error that is not normally encountered.

Action:	Contact Worldwide Customer Support.


ORA-02042

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, 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 Worldwide Customer Support. Shutting down and restarting the instance could be a work-around.


ORA-02043

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 resubmit command.


ORA-02044

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

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

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 Worldwide Customer Support.


ORA-02047

ORA-02047	cannot join the distributed transaction in progress

Cause:	 Either:

•	A transaction is in progress against a remote database that does not support two-phase commit.

•	Updates are pending and an attempt was made to update a different database that does not support two-phase commit.

Action:	Complete the current transaction before attempting the action that caused the error.


ORA-02048

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 Worldwide Customer Support.


ORA-02049

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

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

ORA-02051	another session in same transaction failed

Cause:	A session at the same site with same global transaction identification failed.

Action:	No action is necessary; the transaction will automatically recover.


ORA-02052

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

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 automatically resynchronize when the failure is repaired.


ORA-02054

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; remote DBs will automatically resynchronize when the failure is repaired. Monitor the DBA_2PC_INDOUBT and DBA_2PC_INCONSISTENT tables for the final outcome and resubmit the transaction, if necessary.


ORA-02055

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 statements that have been rolled back.


ORA-02056

ORA-02056	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 Worldwide Customer Support, if necessary.


ORA-02057

ORA-02057	str: bad two-phase recovery state number num from name

Cause:	An internal error in the two-phase recovery protocol occurred.

Action:	Contact Worldwide Customer Support.


ORA-02058

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-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 Worldwide Customer Support.


ORA-02060

ORA-02060	SELECT FOR UPDATE specified a join of non-colocated 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 only joins tables in the same database.


ORA-02061

ORA-02061	lock table specified list of non-colocated 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

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, re-create it so it references a valid database at the remote site.


ORA-02063

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

ORA-02064	iterated or long remote update with subquery not supported

Cause:	One of two cases occurred. An attempt was made to perform an array execute of a remote update with subquery to different database. Or, an attempt was made to perform an update of a long column using a bind variable and an update of a second column with a subquery to a different database, and the subquery has a bind variable.

Action:	Simplify the remote update statement.


ORA-02065

ORA-02065	illegal option for ALTER SYSTEM

Cause:	The option specified for ALTER SYSTEM is not supported.

Action:	Refer to the ORACLE7 Server SQL Language Reference Manual for the proper syntax of the ALTER SYSTEM command.


ORA-02066

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

ORA-02067	transaction or savepoint rollback required

Cause:	A failure occurred, typically 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

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

ORA-02069	remote sequences are not co-located

Cause:	The remote sequences referenced are not all in the same location.

Action:	All remote sequences referenced must be at the same location. Correct the problem and issue the statement again.


ORA-02070

ORA-02070	database name does not support str 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

ORA-02071	message initializing capabilities for remote database name

Cause:	ORACLE could not load the capability table from the named remote database.

Action:	Contact Worldwide Customer Support concerning the remote SQL*Connect product.


ORA-02074

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-02075

ORA-02075	remote sequence not co-located with any table

Cause:	All of the referenced sequences must be located on the same node as at least one table or view.

Action:	Correct the problem and then re-issue the statement.


ORA-02076

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 re-issue the statement.


ORA-02077

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 re-issue the statement.


ORA-02078

ORA-02078	invalid setting for ALTER SYSTEM FIXED_DATE

Cause:	An invalid value was used.

Action:	Use a correct value.


ORA-02079

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 Worldwide Customer Support.


ORA-02080

ORA-02080	database link is in use

Cause:	A transaction is active or a cursor is open on the database link given in the ALTER SESSION CLOSE DATABASE LINK statement.

Action:	Commit or roll back the transaction, or close the open cursors.


ORA-02081

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

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. Refer to the installation or user's guide for more information about creating database links.


ORA-02083

ORA-02083	database name has illegal character 'str'

Cause:	The database name supplied contains an invalid character. There can be no periods, semicolons, blanks, or non-printable characters in the database name.

Action:	Supply a different database name, and do not use any invalid characters.


ORA-02085

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

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

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

ORA-02088	distributed database option not installed

Cause:	The distributed database option is not installed at this site. The requested operation is therefore not possible.

Action:	Contact Oracle Corporation about obtaining the distributed database option.


ORA-02089

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

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, hence the transaction is rolled back.

If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site then both ORA-02091 and ORA-02092 will be seen.

Action:	Complete the current transaction and then do the operation required.


ORA-02092

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, hence the transaction is rolled back.

If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site then both ORA-2091 and ORA-2092 will be seen.

Cause:	Add a rollback segment and do the operation again.


ORA-02093

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.


02140-03199:Oracle7 Server SQL Parsing

This section lists messages that might be generated by the Oracle7 Server when SQL statements are parsed.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-02140

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

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

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

ORA-02143	invalid STORAGE option

Cause:	An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, FREELISTS, FREELIST GROUPS, or PCTINCREASE was specified in the STORAGE clause of a CREATE statement.

Action:	Check syntax, specify only valid options, and try again.


ORA-02144

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

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

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

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

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

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

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

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

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-02161

ORA-02161	invalid value for MAXLOGFILES

Cause:	A number does not follow MAXLOGFILES.

Action:	Specify a number after MAXLOGFILES, and try again.


ORA-02162

ORA-02162	invalid value for MAXDATAFILES

Cause:	A number does not follow MAXDATAFILES.

Action:	Specify a number after MAXDATAFILES, and try again.


ORA-02163

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

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

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

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

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

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

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

ORA-02170	FREELIST GROUPS storage option not allowed

Cause:	An attempt was made to specify the FREELIST GROUPS storage option. This option may only be specified 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

ORA-02171	invalid value for MAXLOGHISTORY

Cause:	A number does not follow MAXLOGHISTORY.

Action:	Specify a number after MAXLOGHISTORY.


ORA-02172

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


ORA-02173

ORA-02173	invalid option for DROP TABLESPACE

Cause:	Something other than INCLUDING was found following the tablespace name, or text was found following INCLUDING CONTENTS.

Action:	Place nothing or only INCLUDING CONTENTS after the tablespace name, and try again.


ORA-02174

ORA-02174	Missing required thread number

Cause:	A thread number must be specified after THREAD keyword.

Action:	Check the syntax of the command, specify a number after THREAD, then  resubmit it.


ORA-02175

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

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

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; then resubmit it.


ORA-02178

ORA-02178	correct syntax is: SET TRANSACTION READ {  ONLY | WRITE }

Cause:	There is a syntax message in the user's statement.

Action:	Correct the syntax as indicated, and try again.


ORA-02180

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

ORA-02181	invalid option to ROLLBACK WORK

Cause:	A word other than TO follows ROLLBACK [WORK].

Action:	Place nothing or TO SAVEPOINT after ROLLBACK [WORK], and try again.


ORA-02182

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-02184

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

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

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

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

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

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

ORA-02191	correct syntax is:  SET TRANSACTION USE ROLLBACK SEGMENT name

Cause:	There is a syntax message in the SET TRANSACTION statement.

Action:	Correct the syntax message and resubmit the statement.


ORA-02192

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:	Resubmit the command without the PCTINCREASE clause.


ORA-02194

ORA-02194	event specification syntax message num (minor message num) near 'name'

Cause:	There is a syntax message in an event specification.

Action:	Check syntax and spelling, and try again.


ORA-02197

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

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

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

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

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

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

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 only be specified when the object is created.

Action:	Remove the INITIAL option, and try again.


ORA-02204

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

ORA-02205	only SELECT and ALTER privilege is 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

ORA-02206	duplicate INITRANS option specification

Cause:	INITRANS is specified more than once.

Action:	Specify INITRANS only once, and try again.


ORA-02207

ORA-02207	invalid INITRANS option value

Cause:	The INITRANS value is not an integer between 2 and 255, and less than or equal to the MAXTRANS value.

Action:	Specify a valid INITRANS value, and try again.


ORA-02208

ORA-02208	duplicate MAXTRANS option specification

Cause:	MAXTRANS is specified more than once.

Action:	Specify MAXTRANS only once, and try again.


ORA-02209

ORA-02209	invalid MAXTRANS option value

Cause:	The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value.

Action:	Specify a valid MAXTRANS value, and try again.


ORA-02210

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

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

ORA-02212	duplicate PCTFREE option specification

Cause:	The PCTFREE option was specified more than once.

Action:	Specify PCTFREE only once, and try again.


ORA-02213

ORA-02213	duplicate PCTUSED option specification

Cause:	The PCTUSED option was specified more than once.

Action:	Specify PCTUSED only once, and try again.


ORA-02214

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

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

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

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

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

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

ORA-02220	invalid MINEXTENTS storage option value

Cause:	The specified value must be a positive integer less than or equal to MAXEXTENTS.

Action:	Specify an appropriate integer value, and try again.


ORA-02221

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

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

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

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

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

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

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

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

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

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

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

r	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

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-02234

ORA-02234	changes to this table are already logged

Cause:	The log table to be added is a duplicate of another.

Action:	Do not add this change log to the system; check that the product used to make copies is consistent.


ORA-02235

ORA-02235	this table logs changes to another table already

Cause:	The table to be altered is already a change log for another table.

Action:	Do not log changes to the specified base table to this table; check that the product used to make copies is consistent.


ORA-02236

ORA-02236	invalid file name

Cause:	In a LOGFILE, DATAFILE, or RENAME clause, a character string literal was expected, but not found, in a file name list.

Action:	Specify file names using character string literals, and try again.


ORA-02237

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

ORA-02238	file name lists have different numbers of files

Cause:	In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing file names does not equal the number of new file names.

Action:	Make sure a new file name corresponds to each existing file name, and try again.


ORA-02239

ORA-02239	there are objects which 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

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

ORA-02241	must be of form EXTENTS (FILE num BLOCK num SIZE num, ...)

Cause:	There was an error in the extent storage clause.

Action:	Re-specify the storage clause using the correct syntax and resubmit the command.


ORA-02242

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

ORA-02243	invalid ALTER INDEX option

Cause:	An option other than INITRANS, MAXTRANS, or STORAGE was specified in an ALTER INDEX statement.

Action:	Specify only valid options, and try again.


ORA-02244

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

r	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

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

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

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

ORA-02249	invalid value for MAXLOGMEMBERS

Cause:	A number does not follow MAXLOGMEMBERS.

Action:	Specify a number after MAXLOGMEMBERS.


ORA-02250

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

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

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

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

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

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

ORA-02256	number of referencing columns must be equal to number of referenced columns

Cause:	The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list.

Action:	Make sure there are no missing columns, and try again.


ORA-02257

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

ORA-02258	duplicate or conflicting NULL and/or NOT NULL specifications

Cause:	A duplicate or conflicting NULL and/or NOTNULL was specified.

Action:	Remove one of the conflicting specifications, and try again.


ORA-02259

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

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

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

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

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

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

ORA-02266	table has some unique/primary keys that are referenced by some foreign keys

Cause:	An attempt was made to drop a table while the table still has some unique or primary keys that are referenced by foreign keys.

Action:	Remove all references by foreign keys to unique or primary keys in a table before attempting to drop the table.


ORA-02267

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

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

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

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

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

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

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

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

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

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

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

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

r	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

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

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

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

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

ORA-02284	duplicate INCREMENT BY specifications

Cause:	A duplicate INCREMENT BY clause was specified.

Action:	Remove the duplicate specification, and try again.


ORA-02285

ORA-02285	duplicate START WITH specifications

Cause:	A duplicate START WITH clause was specified.

Action:	Remove the duplicate specification, and try again.


ORA-02286

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

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

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

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

ORA-02290	check constraint (str.name) violated

Cause:	The value or values attempted to be entered into a field or fields violate a defined check constraint.

Action:	Enter values that satisfy the constraint.


ORA-02291

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

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

ORA-02293	cannot add check constraint - found non-complying values

Cause:	An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values.

Action:	Reissue the ALTER TABLE statement specifying a check constraint on a table containing complying values.


ORA-02294

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:	Reissue the ALTER TABLE statement specifying a valid primary key in a parent table.


ORA-02295

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

ORA-02296	cannot enable constraint (str.name) - found non-complying values

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

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

ORA-02298	cannot enable constraint (name.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

ORA-02299	cannot enable constraint (name.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

This section lists messages generated when the direct path mode is used to load data into the database.


ORA-02351

ORA-02351	record num: Rejected - Error on table name, column name

Cause:	The record indicated caused an error on insert.

Action:	Determine the error and correct the record.


ORA-02353

ORA-02353	multibyte character error

Cause:	The text specified by POSITION or terminated by new lines is invalid.

Action:	Edit the control file or the data file to fix the alignment of the column.


ORA-02354

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 Worldwide Customer Support.


ORA-02355

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

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

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

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

ORA-02359	field in data file 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

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

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

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

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

ORA-02364	record num: Discarded - failed all WHEN clauses

Cause:	The record was not loaded because it failed the WHEN clauses of the table.

Action:	No user action is required.


ORA-02365

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 drop and re-create the index.


ORA-02366

ORA-02366	the following indexes on table name were processed:

Cause:	The indexes listed for the named table were loaded.

Action:	No user action required.


ORA-02367

ORA-02367	index name was loaded.

Cause:	The index specified in the message was loaded.

Action:	No user action required.


ORA-02368

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 user action required.


ORA-02369

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

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

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

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

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

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

This sections lists messages generated when resources within the ORACLE Server are altered.


ORA-02376

ORA-02376	invalid or redundant resource

Cause:	A resource that is not defined or 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

ORA-02377	invalid resource limit

Cause:	An invalid resource limit of 0 was specified.

Action:	Specify a resource limit greater than 0.


ORA-02378

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

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

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

ORA-02381	cannot drop PUBLIC_DEFAULT profile

Cause:	An attempt was made to drop PUBLIC_DEFAULT profile.

Action:	The PUBLIC_DEFAULT profile cannot be dropped.


ORA-02382

ORA-02382	profile name has users assigned, cannot drop without CASCADE

Cause:	An attempt was made to drop a profile that has 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

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

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

ORA-02391	exceeded simultaneous SESSIONS_PER_USER limit, maximum num

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

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

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

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

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

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

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

ORA-02398	exceeded procedure space usage

Cause:	Stored procedures used up too much space in the SYSTEM tablespace.

Action:	Use fewer stored procedures.


ORA-02399

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

This sections lists messages generated when using the SQL EXPLAIN PLAN command.


ORA-02401

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

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

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

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

This section lists messages generated when commands are used that alter schemas or schema objects.


ORA-02420

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 re-execute the statement.


ORA-02421

ORA-02421	missing or invalid schema authorization identifier

Cause:	Either:

•	The schema authorization identifier is not recognized.

•	An attempt was made to use a schema authorization identifier for a user while not connected as that user.

Action:	If the cause is:

•	an unrecognized identifier; then use an existing identifier.

•	connected with a different user name; then disconnect and connect with the correct user name.


ORA-02422

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 the ORACLE7 Server SQL Language Reference Manual for the valid elements of the CREATE SCHEMA statement.


ORA-02423

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:	Make sure the schema names match the one given in the CREATE SCHEMA statement.


ORA-02424

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 make sure all referenced tables are either defined in the CREATE SCHEMA statement or exist outside the statement.


ORA-02425

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

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

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

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:	Make sure the referenced table exists and/or has a unique key.


ORA-02429

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

This section lists messages generated when commands are used that affect constraints on a table.


ORA-02430

ORA-02430	cannot enable constraint (name) - no such constraint

Cause:	The named constraint does not exist for this table.

Action:	Make sure that a constraint exists before trying to enable it.


ORA-02431

ORA-02431	cannot disable constraint (name) - no such constraint

Cause:	The named constraint does not exist for this table.

Action:	Make sure that a constraint exists before trying to disable it.


ORA-02432

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

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:	Make sure that a primary key exists before trying to disable it.


ORA-02434

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:	Make sure that a unique key exists before trying to enable it.


ORA-02435

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:	Make sure that a unique key exists before trying to disable it.


ORA-02436

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

ORA-02437	cannot enable primary key - found duplicates or null values

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

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

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

ORA-02440	create as select with referential constraints not allowed

Cause:	Integrity constraints on 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

ORA-02441	cannot drop nonexistent 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 user action is required.


ORA-02442

ORA-02442	cannot drop nonexistent 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 user action is required.


ORA-02443

ORA-02443	cannot drop constraint - nonexistent 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

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:	Only define referential constraints with schema objects resolving to a base table.


ORA-02445

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 issue the enable command again.

________________________________________


02450-02479: Hash Cluster Commands

This sections lists messages that occur when commands are used that affect hash clusters.


ORA-02450

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 resubmit the statement.


ORA-02451

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 resubmit the command.


ORA-02452

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 resubmit the command.


ORA-02453

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 resubmit the command.


ORA-02454

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:	Resubmit the statement using a larger value for the SIZE option.


ORA-02455

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 one key column only 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 resubmit the command.


ORA-02456

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 resubmit the command.


ORA-02457

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 resubmit the statement.


ORA-02458

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 resubmit the command.


ORA-02459

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 resubmit the command.


ORA-02460

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

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

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 resubmit the statement.


ORA-02463

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 resubmit the statement.


ORA-02464

ORA-02464	cluster definition cannot be both HASH and INDEX

Cause:	Both the HASH IS and INDEX option were specified. Clusters can be either hash or indexed, but not both.

Action:	Decide on which type of cluster is to be created, check the syntax of the command; then resubmit the statement.


ORA-02465

ORA-02465	inappropriate use of the HASH IS option

Cause:	The HASH IS option is only valid for clusters.

Action:	Check the syntax of the command, use the HASH IS option only for clusters; then resubmit the command.


ORA-02466

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.

________________________________________


02500-02699: CTOS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


02700-02874: UNIX Two Task

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


02875-02899: IBM RS/6000

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


03000-03099: Features Not Implemented

This section lists messages generated when a user tries to access a feature that is not implemented in ORACLE.


ORA-03001

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

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

ORA-03007	obsolete feature

Cause:	An attempt was made to use a feature that is no longer supported.

Action:	No user action is required.

________________________________________


03100-03199: Two-Task Interface

This sections lists messages generated when the two-task interface to ORACLE is used.


ORA-03100

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 normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03106

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 normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03107

ORA-03107	oranet buffer underflow

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03108

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

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 normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03110

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

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 normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03112

ORA-03112	host string syntax error

Cause:	In a single-task operation, the internally-generated host string was invalid. This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03113

ORA-03113	end-of-file on communication channel

Cause:	An unexpected end-of-file was processed on the communication channel; bug 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 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 Worldwide Customer Support.


ORA-03114

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

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

ORA-03116	ttcxxx: invalid buffer length

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03117

ORA-03117	ttc save area overflow

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03118

ORA-03118	ttc coroutine has invalid state

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03120

ORA-03120	ttci2u: 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

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 Worldwide Customer Support. If a user program caused the message, relink the program with current versions of the ORACLE libraries.


ORA-03122

ORA-03122	attempt to close ORACLE-side window on user side

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-03123

ORA-03123	network read would block

Cause:	This is an internal error message not normally issued. The error indicates that no data is ready for a network read operation that was designated as non-blocking. The read operation will be retried later.

Action:	No action is necessary. The operation will automatically be retried later.


ORA-03124

ORA-03124	async operation interrupted

Cause:	A non-blocking network operation was in progress, and a new network operation was attempted before the non-blocking operation was completed.

Action:	The network connection must be reset, which will be done automatically; the user should retry the failed operation.


02140-03199:Oracle7 Server Extent Allocation

This section lists messages that might be generated by the Oracle7 Server during extent allocation.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-03276

ORA-03276	duplicate ALLOCATE EXTENT option specification

Cause:	The ALLOCATE EXTENT option to ALTER TABLE is specified more than once.

Action:	Specify the option at most once.


ORA-03277

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

ORA-03278	duplicate option specified for ALLOCATE EXTENT

Cause:	An option (DATA FILE, SIZE, or INSTANCE) was specified more than once in the ALTER TABLE ... ALLOCATE EXTENT statement.

Action:	Specify each option at most once.


ORA-03279

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

ORA-03280	invalid DATA FILE file name specified

Cause:	A character-string literal is expected but not found for the DATA FILE option of the ALTER TABLE ... ALLOCATE EXTENT statement.

Action:	Specify the file name using a character-string literal enclosed in single quotes. Query the data dictionary view DBA_DATA_FILES to find the correct names of the data files.


ORA-03281

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

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, within parentheses, specify one or more of the following options: DATA FILE, SIZE, or INSTANCE.


ORA-03283

ORA-03283	specified data file name does not exist

Cause:	The data file specified for the DATA FILE option in the ALTER TABLE ... ALLOCATE EXTENT statement does not exist.

Action:	Retry the option with the correct file name for the database file. Query the data dictionary view DBA_DATA_FILES to find the correct names of the data files.


ORA-03284

ORA-03284	specified data file name is not a member of tablespace name

Cause:	The data file 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 data file or the correct table. Query the data dictionary view DBA_DATA_FILES to find the correct names of the data files in that tablespace, or query DBA_TABLES to find the correct table name.


ORA-03286

ORA-03286	ALLOCATE EXTENT not valid for HASH CLUSTERS

Cause:	The cluster is a hash cluster, and cannot use the allocate extent option.

Action:	Do not use this command on a hash cluster.


ORA-03287

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

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

This section lists messages generated when the TRUNCATE command is used.


ORA-03290

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

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

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

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.

________________________________________


03300-03499: Meiko

See the "Related Publications" section in the Preface of this Manual  which indicates the Oracle manual containing the messages for this range.

________________________________________


03500-03699: Macintosh

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


03700-03999: AOS/VS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


04000-04109: Command Parameters

This section lists some of the messages generated when inconsistent values are used in a command.


ORA-04000

ORA-04000	the sum of PCTUSED and PCTFREE cannot exceed 100

Cause:	The sum of PCTUSED and PCTFREE specified for a cluster or table exceeds 100.

Action:	Create the table or cluster specifying values for PCTUSED and PCTFREE whose sum does not exceed 100.


ORA-04001

ORA-04001	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

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

ORA-04003	num exceeds the maximum size allowed (num digits) for sequences

Cause:	The specified sequence parameter has too many digits.

Action:	Specify the parameter with the allowed number of digits, and try again.


ORA-04004

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

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

ORA-04006	START WITH cannot be less than MINVALUE

Cause:	The given starting value is less than MINVALUE.

Action:	Make sure the starting value is not less than MINVALUE, and try again.


ORA-04007

ORA-04007	MINVALUE cannot be made to exceed the current value

Cause:	The given MINVALUE is greater than the current value.

Action:	Make sure MINVALUE is not greater than the current value, and try again.


ORA-04008

ORA-04008	START WITH cannot be more than MAXVALUE

Cause:	The starting value is larger than MAXVALUE.

Action:	Make sure the starting value is less than MAXVALUE, and try again.


ORA-04009

ORA-04009	MAXVALUE cannot be made to be less than the current value

Cause:	The current value exceeds the given MAXVALUE.

Action:	Make sure the new MAXVALUE is larger than the current value, and try again.


ORA-04010

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-04012

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

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

ORA-04014	[de][a]scending sequences that CYCLE must specify [NO][MIN][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:	Re-create the sequence, specifying the value at which it is to begin.

________________________________________


04020-04039: System Memory

This section lists messages generated when a library object is locked and cannot be accessed.


ORA-04020

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

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-04029

ORA-04029	error ORA-num occurred when querying 'string'

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

This section lists messages generated by an ORACLE Server when the operating system cannot allocate sufficient memory during an ORACLE session.


ORA-04030

ORA-04030	out of process memory when trying to allocate num bytes (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

ORA-04031	out of shared memory when trying to allocate num bytes (str)

Cause:	More shared memory is needed than was allocated in the SGA.

Action:	Reduce use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameter SHARED_POOL_SIZE.

________________________________________


04040-04069: Stored Procedures

This section lists some of the messages generated when stored procedures are accessed.


ORA-04040

ORA-04040	new time-stamp is not greater than existing one

Cause:	The given time-stamp is not greater than the current time-stamp of the existing object.

Action:	Specify a later time-stamp.


ORA-04041

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

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

ORA-04043	object name does not exist

Cause:	An attempt was made to access a table, view, sequence, procedure, function, package, or package body that does not exist.

Action:	Ensure the name of the object is correct.


ORA-04044

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 the ORACLE7 Server SQL Language Reference Manual for the correct placement of procedures, functions, and packages in statements.


ORA-04045

ORA-04045	errors during recompilation/revalidation of name.name

Cause:	Errors occurred during the implicit recompilation/revalidation of the object named in the message.

When Trusted ORACLE7 is configured in OS MAC mode, you may get this error if you attempt to select from a view that needs to be recompiled. In particular, if the view is on a lower database and a higher database selects from this view this error can occur.

Action:	More descriptive messages follow this one. Check the causes mentioned in the messages that follow and take the appropriate actions.

For Trusted ORACLE7 users, if the cause is that the view needs to be recompiled, ensure that it is recompiled before it is selected.


ORA-04050

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

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

ORA-04052	error occurred when looking up remote object name

Cause:	An error occurred looking up a remote object.

Action:	Fix the error. Make sure 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

ORA-04053	error occurred when validating remote object name

Cause:	An error occurred trying to validate a remote object.

Action:	Fix the error. Make sure 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

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:	Either use a different database link or create the database link.


ORA-04055

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

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

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

ORA-04062	time-stamp of name has been changed

Cause:	An attempt was made to execute a stored procedure to service a remote procedure call stub which specifies a time-stamp that is different from the current time-stamp of the procedure.

Action:	Recompile the caller to obtain the new time-stamp.


ORA-04063

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

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

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

ORA-04066	non-executable object, name

Cause:	An attempt was made to execute an object that is not a package, procedure, or function.

Action:	Ensure that a correct name is used.


ORA-04067

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

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 re-initialization of any application's state.

________________________________________


04070-04099: Triggers

This section lists messages generated when triggers are accessed.


ORA-04070

ORA-04070	invalid trigger name

Cause:	An invalid trigger name was specified.

Action:	Check to see that the trigger name is not a reserved keyword.


ORA-04071

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

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

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

ORA-04074	invalid REFERENCING name

Cause:	An invalid name was given in the REFERENCING clause.

Action:	Verify that the REFERENCING name is not a reserved word.


ORA-04075

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

ORA-04076	invalid NEW or OLD specification

Cause:	An invalid NEW or OLD specification was given for a column.

Action:	Specify the column again using a correct NEW or OLD specification.


ORA-04077

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

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

ORA-04079	invalid trigger specification

Cause:	The CREATE TRIGGER statement is invalid.

Action:	Refer to the ORACLE7 Server SQL Language Reference Manual for the correct syntax of the CREATE TRIGGER statement.


ORA-04080

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

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

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

ORA-04083	invalid trigger variable 'name'

Cause:	The variable referenced in the trigger body is invalid.

Action:	See the ORACLE7 Server SQL Language Reference Manual for valid trigger variable types.


ORA-04084

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

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-04087

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

ORA-04088	error during execution of trigger 'str.name'

Cause:	A runtime error occurred during execution of a trigger.

Action:	Check the triggers that were involved in the operation.


ORA-04089

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

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

ORA-04091	name is mutating, trigger may not read or modify it

Cause:	A trigger attempted to look at (or modify) a table that was in the middle of being modified by the statement that fired it.

Action:	Rewrite the trigger so that it does not call that table.


ORA-04092

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

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

ORA-04094	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

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.

________________________________________


04100-04499: MVS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


04500-04899: CMS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


05000-05899: Original Equipment Manufacturers

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


06000-06429: SQL*Net

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


06430-06429: NCR System 3000

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


06500-06599: PL/SQL

This section lists messages generated when ORACLE detects a problem with PL/SQL code. These ORA-nnnnn are usually followed by PLUS-nnnnn messages which are listed in Chapter3 of this Manual.


ORA-06500

ORA-06500	PL/SQL: storage error

Cause:	A rare internal error message; memory has been exhausted or corrupted.

Action:	Contact Worldwide Customer Support.


ORA-06501

ORA-06501	PL/SQL: internal error num, arguments [num], [num], [num], [num], [num], [num]

Cause:	Internal error message; an error has been detected in a PL/SQL program.

Action:	Contact Worldwide Customer Support.


ORA-06502

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

ORA-06503	PL/SQL: Function returned without value

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

Action:	Rewrite PL/SQL function, making sure that it always returns a value of a proper type.


ORA-06508

ORA-06508	PL/SQL: could not find program unit being called


ORA-06509

ORA-06509	PL/SQL: ICD vector missing for this package


ORA-06510

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

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

ORA-06512	at str line num

Cause:	This is usually the last of a message stack and indicates where in the PL/SQL code that a problem occurred.

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

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 PL/SQL table. Also make sure that you do not use index values less than 1.


ORA-06550

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

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 installation and user's guide for more information.


ORA-06555

ORA-06555	this name is currently reserved for use by use 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

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

ORA-06557	null values are not allowed for any parameters to pipe ICD's

Cause:	Internal error from the DBMS_PIPE package.

Action:	Call Worldwide Customer Support.


ORA-06558

ORA-06558	buffer in DBMS_PIPE package is full.  No more items allowed

Cause:	The pipe buffer size has been exceeded.


ORA-06559

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-06560

ORA-06560	pos, num, is negative or larger than the buffer size, num

Cause:	Internal error from the DBMS_PIPE package.

Action:	Call Worldwide Customer Support.

________________________________________


06600-06699: SQL*Net

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


07100-07199: SQL*Connect for DB2

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


07100-07199: SQL*Connect for IMS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


07200-07499: UNIX

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


07500-07999: VMS

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


08000-08174: Accessing Data

This section lists messages generated when ORACLE is accessing data or database objects.


ORA-08000

ORA-08000	maximum number of session sequence lists exceeded

Cause:	This is an internal error message not normally issued.

Action:	Contact Worldwide Customer Support.


ORA-08001

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

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-08004

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

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

ORA-08006	specified row no longer exists

Cause:	The row has been deleted by another user since the operation began.

Action:	No user action is required.


ORA-08008

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

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 Worldwide Customer Support.


ORA-08101

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 Worldwide 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

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 Worldwide 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

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

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

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 be create index performing a direct load or executing discrete mode transactions.

Action:	Retry the operation with a different snapshot time; if using an index retry the operation without using the index.


12000-12014: Table Snapshots

This section lists messages generated when table snapshots are accessed.


ORA-12000

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

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, thus 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

ORA-12002	there is no snapshot log on table name

Cause:	An attempt was made to drop a snapshot that doesn't exist.

Action:	Check spelling, syntax, and use an existing snapshot name.


ORA-12003

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. Issue the statement again with an existing snapshot name.


ORA-12004

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

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

ORA-12006	a snapshot with the same user.name already exists

Cause:	An attempt was made to create a snapshot with name of an already existing snapshot.

Action:	Create the snapshot using a different name, or drop the existing snapshot.


ORA-12007

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

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, such as the master table no longer exists or a column was added to the master table and the view was not altered.

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 re-create the snapshot.


ORA-12009

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

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 can not be created on SYS tables.

Action:	Do not create snapshot logs on SYS tables.

________________________________________


12100-12299: SQL*Net

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


12300-12499: Trusted ORACLE

This section lists messages generated by Trusted ORACLE.


ORA-12315

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:	Re-issue 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

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 re-create it using valid syntax. See the ORACLE7 Server SQL Language Reference Manual for more information about the connect string portion of the CREATE DATABASE LINK statement.


ORA-12317

ORA-12317	logon to database (link name name) denied

Cause:	Any of the following:

•	Either the user name or password was misspelled.

•	The user does not exist in the secondary database.

•	The user in the secondary database was not granted the CREATE SESSION system privilege.

•	The username/password in the database link definition is invalid for any of the above reasons.

•	If database verification of login information is active, then the username and password do not match in the primary and secondary databases.

•	If operating system verification of login information is active; then the username, do not match in the primary and secondary databases.

Action:	Enter the correct information.

•	Ask the database administrator for the secondary database to create the user.

•	Ask the database administrator for the secondary database to grant the CREATE SESSION system privilege to the user.

•	Correct the database link definition.

•	Ensure that username and password match in the primary and secondary databases.

•	Ensure that the username matches in the primary and secondary databases.

NOTE:  Always use operating system authentication in Trusted ORACLE (see the Trusted ORACLE7 Server Administrator's Guide for more information about the advantages of O/S authentication).


ORA-12318

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

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

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 automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the initialization parameter file to TRUE.


ORA-12322

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

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

ORA-12324	cannot use the ROM: link type on a private database link

Cause:	It is only possible to specify the ROM: link type on a public, not 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

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

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 is reopened, or contact the database administrator.


ORA-12333

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 re-attempt to open the database.


ORA-12334

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 re-attempt to dismount the database.


ORA-12335

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

ORA-12341	maximum number of open mounts exceeded

Cause:	The number specified on the OPEN_MOUNTS parameter in the initialization parameter file exceeds the maximum allowed (255).

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

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

ORA-12345	user name lacks CREATE SESSION privilege in database (link name %s)

Cause:	You tried to connect to a username in the secondary database which exists, but has not been granted the CREATE SESSION privilege.

Action:	Grant the CREATE SESSION privilege to the user in the secondary database.


ORA-12350

ORA-12350	database link being dropped is still mounted

Cause:	An attempt was made to drop a ROM: database link that was still mounted and/or opened.

Action:	Close and dismount the database and then re-issue the drop statement.


ORA-12351

ORA-12351	cannot create view using a remote object which has a remote object reference

Cause:	You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database.

Action:	Choose a different object to reference in your view or change the remote object so that it does not reference another database.


ORA-12353

ORA-12353	secondary stored object cannot reference remote object

Cause:	You tried to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.

Action:	Choose a different object to reference or change the remote view or procedure so that it does not reference another database.


ORA-12402

ORA-12402	file: str

Cause:	Reporting file name for detail of another message.

Action:	Examine the message stack for additional detail.


ORA-12403

ORA-12403	file label (name) must be equal to DBHIGH (name)

Cause:	A data file was found to have a label not equal to DBHIGH. This may be caused if DBHIGH is changed, or if a file is re-labeled.

Action:	Either re-label the file to match DBHIGH, or change DBHIGH to match the file.


ORA-12404

ORA-12404	device low (name) must be dominated by DBLOW (name)

Cause:	A data file 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

ORA-12405	device high (name) must dominate DBHIGH (name)

Cause:	A data file 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

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:	Login 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 WRITE-DOWN privilege to alter the tablespace.


ORA-12407

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 ORACLE 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

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 re-create the tablespace at the original label or choose a new name for this tablespace.


ORA-12409

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

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

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

ORA-12412	DBLOW must be dominated by name

Cause:	An attempt was made to set DBLOW higher than the greatest lower bound of existing data.

Action:	  Set DBLOW to the given label or lower.


ORA-12413

ORA-12413	DBHIGH must dominate name

Cause:	An attempt was made to set DBHIGH lower than the least upper bound of existing data.

Action:	Set DBHIGH to the given label or higher.


ORA-12414

ORA-12414	must be DBHIGH (var) to startup database

Cause:	You tried to open a database while at an O/S label not equal to DBHIGH.

Action:	Login at DBHIGH to start the database.


ORA-12415

ORA-12415	label of role grant must dominate role name

Cause:	An attempt was made to grant a privilege to a role below the label where the role was created.

Action:	Check the label of the role and perform the grant at the label of the role or higher.


ORA-12416

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

ORA-12418	label of index must equal table

Cause:	An attempt was made to create an index on a table at a label different than 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

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

ORA-12420	label of stored object must dominate referenced object name

Cause:	An attempt was made to create a stored object (view, procedure, function trigger) which references some object not dominated by the current label. While the referenced object may be visible due to enable 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 which dominates all referenced objects.


ORA-12421

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

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

ORA-12423	label of constraint must equal table

Cause:	An attempt was made to add a constraint to a table at a label different than the label of the table.

Action:	Check the label of the table and add the constraint at the label of the table.


ORA-12424

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

ORA-12425	label of table must dominate cluster

Cause:	An attempt was made to crate 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

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

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

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

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 than 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

ORA-12430	label of trigger must equal table

Cause:	An attempt was made to create a trigger at a label different than where the table was created.

Action:	Check the label of the table and create the trigger at that label.


ORA-12431

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

ORA-12432	label of default role name must dominate user

Cause:	An attempt was made to assign a user a default role list at a label higher than the user.

Action:	Check the label of the user and assign the default roles at that label.


ORA-12433

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

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

ORA-12435	label of package body must equal package

Cause:	An attempt was made to create a package body at a label different than the corresponding package.

Action:	Check the label of the package and create the package body at that label.


ORA-12437

ORA-12437	cannot to 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 only possible in the primary database.

Action:	Connect directly to the database to perform the operation.


ORA-12438

ORA-12438	insufficient privileges to validate constraint on all rows

Cause:	It is necessary to have access to all rows in a table in order 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

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

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

ORA-12441	grant already exists at a different label

Cause:	One of the privileges granted 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 re-grant it at the new label.


ORA-12442

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

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-12446

ORA-12446	file label is higher than instance label

Cause:	You tried to reuse a file with a label different than the database instance label. You can only reuse files labeled at or below the instance label.

Action:	Examine the message stack for the file name. Remove the file or re-label it to match the database instance label.


ORA-12447

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

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 messages. See your installation or user's guide for information on invalid label generation. See the Trusted ORACLE7 Server Administrator's Guide for information on least upper bound (LUB) functions.


ORA-12450

ORA-12450	label string could not be translated into binary label

Cause:	The operating system could not translate given label string

Action:	Ensure the string specified is a valid label and retry the operation.


ORA-12451

ORA-12451	binary OS label could not be translated into string label

Cause:	The operating system could not translate the specified binary label.

Action:	Ensure the string specified is a valid label, and retry the operation.


ORA-12452

ORA-12452	label format string could not be parsed; check format codes

Cause:	An invalid format string on a label function was specified.

Action:	Ensure 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

ORA-12453	missing quote in literal string

Cause:	A literal string was specified with an incorrect number of quotes.

Action:	Ensure the string has matching quotes and retry the operation.


ORA-12454

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 reissue the statement.


ORA-12455

ORA-12455	OS format not allowed in this context

Cause:	The label format string supplied has an O/S format which is not allowed with the TO_LABEL function.

Action:	Change the label format string to not use the OS format type.


ORA-12456

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 reissue the statement.


ORA-12457

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

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.


ORA-12459

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

ORA-12460	the value var 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

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.


ORA-12470

ORA-12470	process label could not be found

Cause:	An message was encountered in translating the operating system process label into a label number.

Action:	Examine the message stack for a more specific message.


ORA-12475

ORA-12475	cannot login below DBLOW (name)

Cause:	An attempt was made to login at a label dominated by DBLOW.

Action:	Either login at a higher label, or lower DBLOW.


ORA-12476

ORA-12476	cannot login above DBHIGH (name)

Cause:	The user attempted to login at a label dominating DBHIGH.

Action:	Either login at a lower label, or raise DBHIGH.


ORA-12478

ORA-12478	cannot insert label above DBHIGH (var)

Cause:	You tried to explicitly insert a value above DBHIGH into the ROWLABEL column, or tried to specify a value higher of datatype MLSLABEL. Any label you insert into a Trusted ORACLE 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

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 in the process of changing between OS MAC and DBMS MAC modes.

Action:	Retry the operation after the change is complete.


ORA-12485

ORA-12485	cannot find file label for name

Cause:	An message was encountered while reading the label of the specified file.

Action:	 Examine the message stack for an operating system message.


ORA-12487

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

Action:	Connect INTERNAL to Trusted ORACLE; then set the label DBHIGH or DBLOW. If this is not possible due to insufficient privileges, contact the database administrator.


ORA-12488

ORA-12488	session label must be equal to name

Cause:	An attempt was made to login to an OS MAC database at other than the database label.

Action:	Login from an OS process at the specified label.


ORA-12489

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

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 re-create the user at a lower label.


ORA-12491

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

ORA-12494	cannot mount secondary database labeled above DBLOW

Cause:	The secondary database requested was labeled above the DBLOW of the primary database.

Action:	Make sure that DBHIGH on the secondary database is below DBLOW of the primary database.

________________________________________


12500-12699: SQL*Net

See the "Related Publications" section in the Preface of this Manual which indicates the Oracle manual containing the messages for this range.

________________________________________


12700-12799: National Language Support

This section lists messages generated when the National Language Support feature of ORACLE is accessed.


ORA-12700

ORA-12700	Invalid NLS parameter value (var)

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

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 the installation or user's guide for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.


ORA-12702

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

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

ORA-12705	Invalid or unknown NLS parameter value specified

Cause:	An attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value.

Action:	Check the syntax of the ALTER SESSION command and the NLS_PARAMETER. Correct the syntax and re-issue the statement.


ORA-12706

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- or EBCDIC-based character sets depending on what is supported by the hardware. Refer to the installation or user's guide for more information about the type of character set supported.

________________________________________


19999-20000: Stored Procedures

This section lists some of the messages generated when stored procedures are accessed.


ORA-19999

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

ORA-20000	str

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

ORA-21000	message 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 message 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 of this range.


09200-09499:Oracle Workgroup Server

This section lists messages that might arise from running the Oracle Workgroup Server.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________

ORA-09200 	sfccf: error creating file

 Cause:	Disk space is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09201

ORA-09201	sfcopy: error copying file

 Cause:	Block sizes do not match.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09202

ORA-09202	sfifi: error identifying file

 Cause:	The DB_BLOCK_SIZE specified in the initialization parameter file is incorrect.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09203

ORA-09203	sfofi: error opening file

 Cause:	File attributes have changed.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09204

ORA-09204	sfotf: error opening temporary file

 Cause:	An incorrect file path has been specified.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09205

ORA-09205	sfqio: error reading or writing to disk

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09206

ORA-09206	sfrfb: error reading from file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09207

ORA-09207	sfsrd: error reading from file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09208

ORA-09208	sftcls: error closing file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09209

ORA-09209	sftget: error reading from file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09210

ORA-09210	sftopn: error opening file

 Cause:	An incorrect file path has been specified.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09211

ORA-09211	sfwfb: error writing to file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09212

ORA-09212	sfwfbmt: error writing to file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09213

ORA-09213	slgfn: error fabricating file name

 Cause:	The file is too long.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09214

ORA-09214	sfdone: I/O error detected

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09215

ORA-09215	sfqio: error detected in I/O completion routine

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09240

ORA-09240	smpalo: error allocating PGA memory

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09241

ORA-09241	smsalo: error allocating SGA memory

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09242

ORA-09242	smscre: error creating SGA

 Cause:	This is a OS/2 error.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09243

ORA-09243	smsget: error attaching to SGA

 Cause:	The database is not started;  consequently, the SGA has  not been created.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09244

ORA-09244	smprset: error setting memory protections

 Cause:	This is a OS/2 error.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09245

ORA-09245	smcstk: error switching stacks

 Cause:	This is a OS/2 error.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09246

ORA-09246	sfsmap: unable to map SGA

 Cause:	This is a OS/2 error.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09247

ORA-09247	smsdes: error destroying the SGA

 Cause:	This is a OS/2 error.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09260

ORA-09260	sigpidu: error obtaining process id

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09261

ORA-09261	spdcr: error creating detached (background) process

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09262

ORA-09262	spdde: error terminating detached (background) process

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09263

ORA-09263	spini: error initializing process

 Cause:	The amount of available resources  is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09264

ORA-09264	sptpa: error flagging process

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09265

ORA-09265	spwat: error temporarily suspending process

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09266

ORA-09266	spawn: error starting an oracle process

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09270

ORA-09270	szalloc: error allocating memory for security

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09271

ORA-09271	szlon: error verifying user name

 Cause:	The user name is too long.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09272

ORA-09272	remote OS login is not allowed

 Cause:	Remote  login to the operating system is not allowed.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09273

ORA-09273	szrfc: error verifying role name

 Cause:	An OS error was returned when verifying the role name.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09274

ORA-09274	szrfc: insufficient role name buffer space

 Cause:	An OS role name is too long.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09280

ORA-09280	sllfcf: error closing file

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation. Action:


ORA-09281

ORA-09281	sllfop: error opening file

 Cause:	The specified file path is incorrect.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09282

ORA-09282	sllfrb: error reading records

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09283

ORA-09283	sllfsk: error skipping records

 Cause:	The file has been truncated or corrupted.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09290

ORA-09290	sksaalo: error allocating memory for archival

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09291

ORA-09291	sksachk: invalid device specification for LOG_ARCHIVE_DEST

 Cause:	The directory is not accessible.

 Action:	Specify a valid device in the ARCHIVE control string.


ORA-09300

ORA-09300	osncon: unable to connect, DPMI not available

 Cause:	The presence of DPMI is not detected.

 Action:	Restart Windows and retry.


ORA-09301

ORA-09301	osncon: local kernel only supported in standard mode

 Cause:	An attempt was made to connect to S:  while in enhanced mode

 Action:	Restart Windows in standard mode.


ORA-09310

ORA-09310	sclgt: error freeing latch

 Cause:	This is an internal error, not normally expected to occur.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09311

ORA-09311	slsleep: error temporarily suspending process

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09312

ORA-09312	slspool: error spooling file to printer

 Cause:	The amount of available memory is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09313

ORA-09313	slsprom: error prompting user

 Cause:	The amount of available resources is insufficient.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09314

ORA-09314	sltln: error translating logical name

 Cause:	The internal buffer has overflowed.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09315

ORA-09315	sql2tt: two-task error translating ORACLE_EXECUTABLE

 Cause:	This is an internal error, not normally expected to occur.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09316

ORA-09316	szrpc: unable to verify password for role

 Cause:	OS roles are not supported for this platform.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09317

ORA-09317	szprv: insufficient privileges

 Cause:	An invalid password has been specified.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09318

ORA-09318	slkhst: error hosting out to operating system

 Cause:	There is insufficient memory to execute the command or hosting out is not supported on this platform

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09319

ORA-09319	slgtd: unable to obtain the current date and time

 Cause:	The system time is set incorrectly.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09320

ORA-09320	szrfc: unable to obtain the list of valid OS roles

 Cause:	OS roles are not supported on this platform.

 Action:	Check the operating system error code and consult the OS/2 documentation.


ORA-09330

ORA-09330	session terminated internally by Oracle or by an Oracle DBA

 Cause:	A client workstation is abnormally disconnected or a shutdown abort has been performed.

 Action:	Properly reconnect the client workstation.


ORA-09340

ORA-09340	specified ORACLE_SID is either invalid or too long

 Cause:	ORACLE_SID is invalid or too long.

 Action:	Correctly specify the ORACLE_SID parameter variable.


ORA-09350

ORA-09350	Windows NT two-task driver unable to allocate context area

 Cause:	This is a Windows NT error.

 Action:	Check the operating system error code and consult the Windows NT documentation.


ORA-09351

ORA-09351	Windows NT two-task driver unable to allocate shared memory

 Cause:	This is a Windows NT error.

 Action:	Check the operating system error code and consult the Windows NT documentation.


ORA-09352

ORA-09352	Windows NT two-task driver unable to spawn new ORACLE task

 Cause:	This is a Windows NT error.

 Action:	Check the operating system error code and consult the Windows NT documentation.


ORA-09353

ORA-09353	Windows NT two-task driver unable to open event semaphore

 Cause:	This is a Windows NT error.

 Action:	Check the operating system error code and consult the Windows NT documentation.


ORA-09354

ORA-09354	Windows NT two-task driver: ORACLE task unexpectedly died

 Cause:	This is a Windows NT error.

 Action:	Check the operating system error code and consult the Windows NT documentation.


06100-06101:SQL*Net TCPIP

This section lists messages that might arise from using SQL*Net TCPIP.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-06102

ORA-06102:	NETTCP:  cannot allocate context area

 Cause:	The dynamic memory available for the connection context area is insufficient.

 Action:	Contact your Oracle Customer Support representative.


ORA-06105

ORA-06105:	NETTCP:  remote host is unknown

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

 Action:	Verify the spelling of the host name. Make sure the name exists in the TCP/IP HOST file, and try again.


ORA-06106

ORA-06106:	NETTCP:  socket creation failure

 Cause:	The process open file quota was probably exceeded.

 Action:	Contact your Oracle Customer Support representative.


ORA-06107

ORA-06107:	NETTCP:  ORACLE network server not found

 Cause:	The entry for ORACLE server in the SERVICES file is missing.

 Action:	Add "orasrv" to the TCP/IP SERVICES file.


ORA-06108

ORA-06108:	NETTCP:  connect to host failed

 Cause:	The attempt to connect to a remote host has failed. The SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up. Check the latter possibility by targeting it with Telnet.

 Action:	Start the SQL*Net TCP/IP server process on the remote host.


ORA-06109

ORA-06109:	NETTCP:  message receive failure

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

 Action:	Contact your Oracle Customer Support representative.


ORA-06110

ORA-06110:	NETTCP:  message send failure

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

 Action:	Contact your Oracle Customer Support representative.


ORA-06111

ORA-06111:	NETTCP:  disconnect failure

 Cause:	An error occurred while attempting to close a socket.

 Action:	Contact your Oracle Customer Support representative.


ORA-06112

ORA-06112:	NETTCP:  invalid buffer size

 Cause:	The buffer size specified in the login string exceeds 4096.

 Action:	Specify the correct buffer size (4096 or less in length).


ORA-06113

ORA-06113:	NETTCP:  Too many connections

 Cause:	The number of concurrently open connections has exceeded the maximum.

 Action:	Close a connection by exiting an application with an open connection that is no longer needed.


ORA-06114

ORA-06114:	NETTCP:  SID lookup failure

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

 Action:	Add the appropriate SID entry to the parameter file on the remote host, then restart the SQL*Net TCP/IP server.


ORA-06115

ORA-06115:	NETTCP:  unable to create ORACLE logicals

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

 Action:	See the SQL*Net TCP/IP server log file for more information. Contact your system administrator.


ORA-06116

ORA-06116:	NETTCP:  unable to create ORASRV process

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

 Action:	See the SQL*Net TCP/IP server log file for more information. Contact your system administrator.


ORA-06117

ORA-06117:	NETTCP:  unable to create ORASRV:  quota exceeded

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

 Action:	Increase the quota allocations to the SQL*Net TCP/IP server process.


ORA-06118

ORA-06118:	NETTCP:  unable to complete handshake with ORASRV

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

 Action:	Contact your Oracle Customer Support representative.


ORA-06119

ORA-06119:	NETTCP:  spurious client request

 Cause:	The host's SQL*Net TCP/IP server was unable to recognize the connection request.

 Action:	See the SQL*Net TCP/IP server log file for more information. Contact your Oracle Customer Support representative.


ORA-06120

ORA-06120:	NETTCP:  network driver not loaded

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

 Action:	Verify that the TCP/IP driver loads correctly.


ORA-06121

ORA-06121:	NETTCP:  access failure

 Cause:	The host's SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in the configuration file) associated with this connection request.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06122

ORA-06122:	NETTCP:  setup failure

 Cause:	The host's SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06123

ORA-06123:	NETTCP:  cannot set KEEPALIVE

 Cause:	The host's SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06124

ORA-06124:	NETTCP:  timeout waiting for ORASRV

 Cause:	The ORACLE server process was started but failed to respond after a period of time (n seconds).

 Action:	This failure can occur on heavily-loaded systems. Increase the value of n (the default is 30) by adding the following entry in the initialization parameter file:

SQLNET ORASRV_WAIT = number


ORA-06125

ORA-06125:	NETTCP:  ORASRV exited unexpectedly

 Cause:	The ORACLE server process was started but exited unexpectedly.

Two possible causes:

1.  There were insufficient quotas to run ORASRV on the ORACLE server.

2.  ORACLE is not installed.

 Action:	See the ORASRV output file for more information. The ORASRV output file resides in the ORA_SQLNET directory and has a name in the following form:

ORA_SRVTnn_[SID].OUT

If the ORASRV output file does not indicate the appropriate action, contact your Oracle Customer Support representative.


ORA-06126

ORA-06126:	NETTCP:  ORASRV unable to open network connection

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

 Action:	Contact your Oracle Customer Support representative.


ORA-06127

ORA-06127:	NETTCP:  unable to change username

 Cause:	The host's SQL*Net TCP/IP server could not establish a Proxy login connection because the client username is unknown to the host operating system.

 Action:	Create new user account on the host and retry the connection.


ORA-06128

ORA-06128:	NETTCP:  unable to create mailbox

 Cause:	The host's SQL*Net TCP/IP server was unable to create a mailbox needed for IPC communication with the ORACLE server process.

 Action:	See the SQL*Net TCP/IP server log file for more information. Contact your Oracle Customer Support representative.


ORA-06129

ORA-06129:	NETTCP:  unable to transfer socket ownership to ORASRV

 Cause:	The host's SQL*Net TCP/IP server was unable to transfer the network communication handle to the ORACLE server process.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06130

ORA-06130:	NETTCP:  host access denied

 Cause:	The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have sufficient access privileges.

 Action:	To grant access, add the appropriate entry to the host's VNT.


ORA-06131

ORA-06131:	NETTCP:  user access denied

 Cause:	The host's SQL*Net TCP/IP server rejected this connection request because the client username does not have sufficient access privileges. Privileges are determined by the contents of the Username Mapping Table (UMT), a subset of the host's configuration parameters.

 Action:	To grant access, add the appropriate entry to the host's UMT.


ORA-06132

ORA-06132:	NETTCP:  access denied, wrong password

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

 Action:	To grant access, make sure the passwords are the same.


ORA-06133

ORA-06133:	NETTCP:  file not found

 Cause:	The host's SQL*Net TCP/IP server could not find the SID mapping file associated with this connection request.

 Action:	Verify the spelling and existence of the SID mapping file.


ORA-06134

ORA-06134:	NETTCP:  file access privilege violation

 Cause:	The host's SQL*Net TCP/IP server did not have READ/EXECUTE permissions for the SID mapping file associated with this connection request.

 Action:	Change the protection on the SID mapping file.


ORA-06135

ORA-06135:	NETTCP:  connection rejected; server is stopping

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

 Action:	Restart SQL*Net TCP/IP server.


ORA-06136

ORA-06136:	NETTCP:  error during connection handshake

 Cause:	A network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06137

ORA-06137:	NETTCP:  error during connection handshake

 Cause:	A network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06138

ORA-06138:	NETTCP:  error during connection handshake

 Cause:	A network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06140

ORA-06140:	NETTCP:  no such user

 Cause:	A Proxy login connect attempt failed because the client username is not defined on the host.

 Action:	Contact your network administrator.


ORA-06141

ORA-06141:	NETTCP:  no privilege for user

 Cause:	A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account.

 Action:	Change the account protection, change the server privileges, or both.


ORA-06142

ORA-06142:	NETTCP:  error getting user information

 Cause:	A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account.

 Action:	Check the log file for the operating system-specific error code. Contact your Oracle Customer Support representative.


ORA-06143

ORA-06143:	NETTCP:  maximum connections exceeded

 Cause:	The connect failed because the number of concurrent connections has exceeded the maximum supported by the host's SQL*Net TCP/IP server.

 Action:	Wait for a short period and retry the operation.


ORA-06144

ORA-06144:	NETTCP:  SID (database) is unavailable

 Cause:	The database administrator on the host has taken the database to which you are requesting access offline.

 Action:	Wait for it to be brought back online.


ORA-06145

ORA-06145:	NETTCP:  unable to start ORASRV:  images not installed

 Cause:	The host's SQL*Net TCP/IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed.

 Action:	Install the images.


06220-06400:SQL*Net Named Pipes

This section lists messages that might arise from using SQL*Net Named Pipes.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-06220

ORA-06220:	NETNMP:  Server not specified in command line

 Cause:	A server name is not specified in the DOS command-line after "p:".

 Action:	Specify the server name after the network prefix and retry, or set the LOCAL or REMOTE parameter in your configuration parameter file.


ORA-06221

ORA-06221:	NETNMP:  Named pipe busy

 Cause:	All available Named Pipes instances are in use.

 Action:	Close any unused connections and retry the operation.


ORA-06222

ORA-06222:	NETNMP:  Error allocating memory

 Cause:	The system is unable to allocate memory block.

 Action:	Resubmit the entry. If the error persists, contact your DBA.


ORA-06223

ORA-06223:	NETNMP:  Error receiving data from pipe

 Cause:	Oracle encountered an error when receiving data from the pipe.

 Action:	Check all LAN connections and cables. If any connections are loose, secure them and retry. Otherwise, reboot your machine and reload the SQL*Net Named Pipes driver. If the error persists, contact your DBA.


ORA-06224

ORA-06224:	NETNMP:  Error sending data to pipe

 Cause:	The system encountered an error sending data to the pipe.

 Action:	Check all LAN connections and cables. If any connections are loose, secure them and retry. Otherwise, reboot the machine and reload the SQL*Net Named Pipes driver. If the error persists, contact your DBA.


ORA-06225

ORA-06225:	NETNMP:  Invalid packet type

 Cause:	The system received erroneous data.

 Action:	Check all LAN connections and cables. If any connections are loose, secure them and retry. Otherwise, reboot the machine and reload the SQL*Net Named Pipes driver. If the error persists, contact your DBA.


ORA-06226

ORA-06226:	NETNMP:  Send byte count error

 Cause:	An error was encountered in sending data.

 Action:	Check all LAN connections and cables. If any connections are loose, secure them and retry. Otherwise, reboot the machine and reload the SQL*Net Named Pipes driver. If the error persists, contact your DBA.


ORA-06227

ORA-06227:	NETNMP:  Error resetting connection

 Cause:	The system encountered an error when resetting the connection.

 Action:	Check all LAN connections and cables. If any connections are loose, secure them and retry. Otherwise, reboot the machine and reload the SQL*Net Named Pipes driver. If the error persists, contact your DBA.


ORA-06228

ORA-06228:	NETNMP:  Unable to open named pipe

 Cause:	Either your workstation is not logged on to a valid account, or you are using the wrong version of LAN Manager software or the SQL*Net Named Pipes driver.

 Action:	Log onto a valid account (do not use the default guest account). If the problem reappears, contact your DBA.


ORA-06229

ORA-06229:	NETNMP:  Windows NT failed to create or access shared memory

 Cause:	Unable to open shared memory segment containing the connection status of Oracle Server.

 Action:	Ensure that Oracle Server has been started properly so that the shared memory segment is available.


ORA-06230

ORA-06230:	NETNMP:  SQL*Net handshake error

 Cause:	An error occurred during the SQL*Net handshake between the client and Oracle Server.

 Action:	Ensure pipe has been created successfully. Check SQL*Net versions on server and client machines and reinstall same versions if different.


ORA-06231

ORA-06231:	NETNMP:  Unable to put pipe into listening mode

 Cause:	Named pipe was not created properly.

 Action:	Re-start Oracle Server and attempt the connection again.


ORA-06232

ORA-06232:	NETNMP:  Unable to create a pipe instance

 Cause:	Named pipe could not be opened properly.

 Action:	Ensure that LAN Manager is installed properly and that client and server have both been started successfully.


ORA-06233

ORA-06233:	NETNMP:  SQL*Net Named Pipe server not running

 Cause:	Client is specifying a server name that does not exist on the network.

 Action:	Ensure that the client specifies a server name for a server that is running on the network.


06401-06429:SQL*Net NETCMN

This section lists messages that might arise from using SQL*Net.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-06401

ORA-06401:	NETCMN:  invalid driver designator

 Cause:	The specified driver is unknown.

 Action:	Check the last entry and resubmit the connect string using the designated name for the SQL*Net driver.


ORA-06402

ORA-06402:	NETCMN:  error receiving break message

 Cause:	The SQL*Net driver detected that its server has unexpectedly exited.

 Action:	Check the network operating system and resubmit the connect string.


ORA-06403

ORA-06403:	NETCMN:  cannot allocate context area

 Cause:	The SQL*Net driver could not allocate heap space for the context area.

 Action:	Re-submit the connect string. Contact your DBA.


ORA-06404

ORA-06404:	NETCMN:  invalid login string

 Cause:	The SQL*Net driver detected a syntax error in the database ID portion of the user's login string.

 Action:	Check the login string and then correct the syntax error.


ORA-06405

ORA-06405:	NETCMN:  reset protocol error

 Cause:	The SQL*Net driver detected an error while trying to reset the connection from a break state.

 Action:	Re-submit the connect string.


ORA-06406

ORA-06406:	NETCMN:  error sending break message

 Cause:	The SQL*Net driver could not correctly handle an incoming out-of-band message.

 Action:	Re-submit the connect string.


ORA-06407

ORA-06407:	NETCMN:  unable to set up break handling environment

 Cause:	The SQL*Net driver could not set up out-of-band break handler.

 Action:	Re-submit the connect string.


ORA-06408

ORA-06408:	NETCMN:  incorrect message format

 Cause:	A message from a partner contains a bad header.

 Action:	Contact your Oracle Customer Support representative.


ORA-06409

ORA-06409:	NETCMN:  message send failure

 Cause:	SQL*Net driver failed to send a message across the communication channel.

 Action:	Re-submit the connect string.


ORA-06410

ORA-06410:	NETCMN:  message receive failure

 Cause:	SQL*Net driver failed to receive a message across the communication channel.

 Action:	Re-submit the connect string. Contact the DBA if the error message persists.


ORA-06411

ORA-06411:	NETCMN:  message send failure

 Cause:	The SQL*Net driver failed to send a complete message across the communication channel.

 Action:	Re-submit the connect string. Contact the DBA if the error message persists.


ORA-06412

ORA-06412:	NETCMN:  message receive failure

 Cause:	The SQL*Net driver failed to receive a complete message from the communication channel.

 Action:	Re-submit the connect string. Contact the DBA if the error message persists.


ORA-06413

ORA-06413:	NETCMN:  connection not open

 Cause:	The SQL*Net driver was unable to open a connection with a remote node.

 Action:	Check node or wait for available connection to open, then resubmit the connect string.


ORA-06414

ORA-06414:	NETCMN:  disconnect failure

 Cause:	The SQL*Net driver was unable to close a connection.

 Action:	Check the node or wait for an available connection to close and then resubmit the connect string.


ORA-06415

ORA-06415:	NETCMN:  incompatible versions

 Cause:	The version of SQL*Net driver loaded on client workstation differs from SQL*Net listener process opened on the server.

 Action:	Check the installation of SQL*Net on both the server and the client PCs. Upgrade the software to the same version on both sides of the network.


ORA-06416

ORA-06416:	NETCMN:  error on test

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

 Action:	Contact your Oracle Customer Support representative.


ORA-06419

ORA-06419:	NETCMN:  server cannot start oracle

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

 Action:	Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator.


ORA-06420

ORA-06420:	NETCMN:  SID lookup failure

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

 Action:	Add the appropriate SID entry to the parameter file or oratab file on the remote host. Restart the remote server, if necessary.


ORA-06421

ORA-06421:	NETCMN:  error detected in the read-in data

 Cause:	An error occurred in the recomputation of checksum or CRC. There is a possible hardware failure in the communication nodes.

 Action:	Contact your system administrator.


ORA-06422

ORA-06422:	NETCMN:  error in sending data

 Cause:	SQL*Net was unable to transmit data to a remote host.

 Action:	Attempt to reconnect to the remote host. Contact your system administrator.


ORA-06423

ORA-06423:	NETCMN:  error in receiving data

 Cause:	SQL*Net was unable to receive data from a remote host.

 Action:	Attempt to reconnect to the remote host. Contact your system administrator.


06430-06449:SQL*Net NetBIOS

This section lists messages that might arise from using SQL*Net NetBIOS.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-06430

ORA-06430:	NETBIOS:  Unable to make connection

 Cause:	No listener process is present, the connection between the server and the client is broken, or the server is not accepting new connection requests because the maximum number of connections has been reached.

 Action:	Make sure the server process is running and specified by the correct server name; the server name is case-sensitive and must be the same name as the one specified as the argument to the command NTBSRV.  Other options are to check the network connection and to check the server machine for any warning or error messages.


ORA-06431

ORA-06431:	NETBIOS:  Error while listening

 Cause:	The local session table is full or the server name is invalid.

 Action:	Reboot the server machine or specify the legal server name.


ORA-06432

ORA-06432: 	NETBIOS:  Cannot terminate current session

 Cause:	The session ended abnormally or there was an adapter malfunction.

 Action:	Contact your DBA.


ORA-06433

ORA-06433: 	NETBIOS:  Error encountered while sending data

 Cause:	An error was encountered in attempting to send data.  The possible reasons include:  the command timed out, the message was incomplete, the session ended abnormally, the maximum number of connections was reached, or an adapter malfunctioned.

 Action:	First, check the server machine for any warning messages.  Next, try rebooting the machine.  If the problem persists, contact your DBA.


ORA-06434

ORA-06434:	NETBIOS:  Error encountered while receiving data

 Cause:	An error was encountered in receiving data.  The possible reasons include:  the command timed out, the message was incomplete, the session ended abnormally, or the adapter malfunctioned.

 Action:	Reboot the machine.  If the problem persists, contact your DBA.


ORA-06435

ORA-06435: 	NETBIOS:  Unable to add local name to name table

 Cause:	A duplicate locator is running, the last NetBIOS session was terminated abnormally, or the NetBIOS emulator was not loaded.

 Action:	Turn off any duplicate locators running on network, then reboot the client machine.  Make sure your client machine is properly configured for the correct network to support NetBIOS calls.  Check that the NetBIOS emulator has been loaded and is running.


ORA-06436

ORA-06436: 	NETBIOS:  Locator not responding

 Cause:	The network operating system locator is not responding.

 Action:	Check the network connection between your client and the server.  Make sure that there is one and only one locator service running on the network.  Make sure that the machine running the locator service is up and is properly connected to the network.  Contact your DBA for assistance.


ORA-06437

ORA-06437: 	NETBIOS:  Unusual network condition

 Cause:	An internal command was issued that it is not valid to cancel.

 Action:	This is an unusual network condition; contact your DBA.


ORA-06438

ORA-06438: 	NETBIOS:  Error invoking ORACLE shadow process

 Cause:	The server is unable to start a shadow process after receiving the connection request.

 Action:	If you are running against a Version 5.1 server, make sure that the CONFIG.ORA parameter ORACLE_EXECUTABLE is set to ORACLE5; the default is ORACLE6.  Otherwise, contact your DBA.


ORA-06441

ORA-06441: 	NETBIOS:  OS/2 failed to create or access shared memory

 Cause:	Unable to open shared memory segment containing the connection status of ORACLE Server.

 Action:	Ensure that ORACLE Server has been started properly so that the shared memory segment is available.


06450-06500:SQL*Net SPX

This section lists messages that might arise from using SQL*Net SPX.  Each message code has the format ORA- nnnnn, where nnnnn is an integer.  Each message description lists possible causes for the message and suggests correctve action.

The messages listed here are not duplicated in the Oracle7 Server Messages and Codes Manual.

________________________________________


ORA-06450

ORA-06450:	NETSPX:  IPX not loaded

 Cause:	The DOS network shell is not loaded.

 Action:	Run IPX.EXE and NET3.EXE.  If your MS-DOS version is 4.x, use NET4.EXE; for MS-DOS version 5.x, use NETX.EXE.


ORA-06451

ORA-06451:	NETSPX:  SPX socket open error

 Cause:	The SPX socket is unavailable.  It is possible that there are too many opened sockets.

 Action:	Increase the number of SPX sockets and IPX sockets in NET.CFG (OS/2) or SHELL.CFG (DOS).  If this error occurs, contact your DBA for assistance.


ORA-06452

ORA-06452:	NETSPX:  SPX connection failure

 Cause:	The system is unable to connect to the requested server.  It is possible that server is not allowing any more connections.

 Action:	Retry when connection is available.  Increase the SPX_MAX_CLIENTS parameter in the CONFIG.ORA file and restart server.


ORA-06453

ORA-06453:	NETSPX:  Send length error

 Cause:	The system encountered an error when sending data.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.


ORA-06454

ORA-06454:	NETSPX:  SPX connection broken/All database links used

 Cause:	The connection has been broken or a database link cannot be performed.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.


ORA-06455

ORA-06455:	NETSPX:  SPX Event Control Block error

 Cause:	Either no ECBs are available or there is an ECB parameter error.

 Action:	Reboot the server, reload the SQL*Net driver, and restart ORACLE.


ORA-06456

ORA-06456:	NETSPX:  SPX packet error

 Cause:	The system received an erroneous packet.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.


ORA-06457

ORA-06457:	NETSPX:  SPX Event Control Block error

 Cause:	Error initializing ECBs.  SPX is not functioning properly.

 Action:	Reboot the server, reload the SQL*Net driver, and restart ORACLE.  If error recurs, contact your DBA.


ORA-06458

ORA-06458:	NETSPX:  Connection reset error

 Cause:	An error occurred when resetting the connection.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.  If error recurs, contact your DBA.


ORA-06459

ORA-06459:	NETSPX:  Server name not specified in command line

 Cause:	A server name is not specified in the command line after "x:".

 Action:	Specify server name after the network prefix and retry, or set the LOCAL or REMOTE parameter in your CONFIG.ORA file.


ORA-06460

ORA-06460:	NETSPX:  Unknown server

 Cause:	The server name that was specified is not running.

 Action:	Ensure that the specified server is running on the network.


ORA-06461

ORA-06461:	NETSPX:  Unable to allocate memory

 Cause:	Not enough system memory or too many memory-resident programs are installed.

 Action:	Remove unnecessary memory-resident programs and retry the operation.


ORA-06462

ORA-06462:	NETSPX:  Unable to allocate/access memory

 Cause:	Not enough system memory, too many memory resident programs are installed, or server is no longer running.

 Action:	Remove unnecessary memory resident programs and restart the server.


ORA-06463

ORA-06463:	NETSPX:  Memory deallocation error/SQL*Net handshake error

 Cause:	Possibly incompatibility between SQL*Net versions on server and clients.

 Action:	Check SQL*Net versions on server and client machines and reinstall same versions if different.


ORA-06464

ORA-06464:	NETSPX:  SPX error

 Cause:	Network data corruption.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.  If error recurs, contact your DBA.


ORA-06465

ORA-06465:	NETSPX:  Error listening for SPX packets

 Cause:	Failed to receive packet from SPX.  It is possible that the client or server PC is no longer running, is detached from the Novell file server, or a network cable is broken.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.  If error recurs, contact your DBA.


ORA-06466

ORA-06466:	NETSPX:  Error sending SPX packets

 Cause:	Failed to send packet to SPX.  It is possible that the client or server PC is no longer running, is detached from the Novell file server, or a network cable is broken.

 Action:	Check all LAN connections and cables.  If any connections are loose, secure them and reconnect to the server.  Otherwise, reboot the server, reload the SQL*Net driver, and then reconnect to the server.  If error recurs, contact your DBA.


ORA-06467

ORA-06467:	NETSPX:  Not attached to Novell server

 Cause:	Workstation is not attached to Novell file server.

 Action:	If the workstation is running DOS, run IPX.COM and NETX.EXE (where x=3 for MS-DOS 3.x, x=4 for MS-DOS 4.x, and x=X for MS-DOS 5.x).  If the workstation is running OS/2, check CONFIG.SYS for the presence of the following two lines:

device = c:\netware\nwreq.sys

run = c:\netware\nwdaemon.exe

If the lines are not there, add them and then reboot the workstation.


ORA-06468

ORA-06468:	NETSPX:  SPX get local target error

 Cause:	SPX cannot locate the destination on the network.

 Action:	Reboot the server, reload the SQL*Net driver, and retry the operation.  If error recurs, contact your DBA.


ORA-06469

ORA-06469:	NETSPX:  Out of resource

 Cause:	Novell SPX is out of resources, e.g., SPX socket table full, connection table full, etc.

 Action:	Terminate some connections to free up the resources requested.


ORA-06470

ORA-06470:	NETSPX:  Partner died

 Cause:	Client or server PC is no longer running, e.g., powered down, rebooted, or a network connection is broken.

 Action:	Ensure that the client or server PC is working properly and is successfully communicating with the network.