73 ORA-01500 to ORA-02098
- ORA-01500: failure in getting date/time
-
Cause: During create database or alter tablespace, there was a failure in getting the date and time.
- ORA-01501: CREATE DATABASE failed
-
Cause: An error occurred during create database
- ORA-01502: index 'string.string' or partition of such index is in unusable state
-
Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation
- ORA-01503: CREATE CONTROLFILE failed
-
Cause: An error occurred during CREATE CONTROLFILE
- ORA-01504: database name 'string' does not match initialization parameter DB_NAME 'string'
-
Cause: The database name during create or mount did not match the name specified for the DB_NAME initialization parameter.
- ORA-01505: error in adding log files
-
Cause: During create or alter database, error(s) occurred when adding new log files.
- ORA-01506: missing or illegal database name
-
Cause: No db_name INIT.ORA parameter was specified.
- ORA-01507: database not mounted
-
Cause: A command was attempted that requires the database to be mounted.
- ORA-01508: cannot create database; error in file 'string' at line string
-
Cause: CREATE DATABASE was unable to process the specified file.
- ORA-01509: specified name 'string' does not match actual 'string'
-
Cause: The database name specified in the ALTER DATABASE statement does not match the name of the database that is currently mounted.
- ORA-01510: error in deleting log files
-
Cause: During ALTER DATABASE, an error occurred while dropping log files.
- ORA-01511: error in renaming log/data files
-
Cause: An error occurred during the ALTER DATABASE RENAME FILE command.
- ORA-01512: error renaming log file string - new file string not found
-
Cause: An attempt to change a log file's name in the control file failed because no file was found with the new name.
- ORA-01513: invalid current time returned by operating system
-
Cause: The operating system returned a time that was not between 1988 and 2121.
- ORA-01514: error in log specification: no such log
-
Cause: A log file name, or list of member names, did not correspond to an existing log.
- ORA-01515: error dropping log group string: no such log
-
Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file.
- ORA-01516: nonexistent log file, data file, or temporary file "string" in the current container
-
Cause: An attempt was made to use ALTER DATABASE to rename a log file, data file, or temporary file; or to change attributes of a data file or temporary file (for example, resize, autoextend, online or offline); or to re-create or move a data file. The attempt failed because the specified file is not known to the database's control file or the current container or is not of a type supported by the request.
- ORA-01517: log member: 'string'
-
Cause: Used to print member names
- ORA-01518: CREATE DATABASE must specify more than one log file
-
Cause: Only one log file was specified in the CREATE DATABASE statement.
- ORA-01519: error while processing file 'string' near line string
-
Cause: The CREATE DATABASE statement encountered a problem while processing the specified file. The specified file is invalid.
- ORA-01520: number of data files to add (string) exceeds limit of string
-
Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database.
- ORA-01521: error in adding data files
-
Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files.
- ORA-01522: file 'string' to be renamed does not exist
-
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.
- ORA-01523: cannot rename data file to 'string' - file already part of database
-
Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.
- ORA-01524: cannot create data file as 'string' - file already part of database
-
Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.
- ORA-01525: error in renaming data files
-
Cause: An error occurred when renaming files as part of ALTER TABLESPACE.
- ORA-01526: error in opening file 'string'
-
Cause: CREATE DATABASE was not able to open the specified file.
- ORA-01527: error while reading file
-
Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.
- ORA-01528: EOF while processing SQL statement
-
Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad.
- ORA-01529: error closing file 'string'
-
Cause: CREATE DATABASE was not able to close the specified file.
- ORA-01530: a database already mounted by the instance
-
Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted.
- ORA-01531: a database already open by the instance
-
Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.
- ORA-01532: cannot create database; instance being started elsewhere
-
Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance.
- ORA-01533: cannot rename file 'string'; file does not belong to tablespace
-
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.
- ORA-01534: rollback segment 'string' doesn't exist
-
Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.
- ORA-01535: rollback segment 'string' already exists or given name has prefix _SYSSMU
-
Cause: Specified rollback segment already exists or given name starts with _SYSSMU.
- ORA-01536: space quota exceeded for tablespace 'string'
-
Cause: The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.
- ORA-01537: cannot add file 'string' - file already part of database
-
Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database.
- ORA-01538: failed to acquire any rollback segment
-
Cause: Failed to acquire any rollback segment during startup in shared mode
- ORA-01539: tablespace 'string' is not online
-
Cause: Failed to either make a tablespace read-only or offline because it was not online. A tablespace must be online before it could become read-only or offline normal.
- ORA-01540: tablespace 'string' is not offline
-
Cause: Failed to bring a tablespace online because it is not offline
- ORA-01541: system tablespace cannot be brought offline; shut down if necessary
-
Cause: Tried to bring system tablespace offline
- ORA-01542: tablespace 'string' is offline, cannot allocate space in it
-
Cause: Tried to allocate space in an offline tablespace
- ORA-01543: tablespace 'string' already exists
-
Cause: Tried to create a tablespace which already exists
- ORA-01544: cannot drop system rollback segment
-
Cause: Tried to drop system rollback segment
- ORA-01545: rollback segment 'string' specified not available
-
Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.
- ORA-01546: tablespace contains active rollback segment 'string'
-
Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read-only
- ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
-
Cause: Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.
- ORA-01548: active rollback segment 'string' found, terminate dropping tablespace
-
Cause: Tried to drop a tablespace that contains active rollback segment(s)
- ORA-01549: tablespace not empty, use INCLUDING CONTENTS option
-
Cause: Tried to drop a non-empty tablespace
- ORA-01550: cannot drop system tablespace
-
Cause: Tried to drop system tablespace
- ORA-01551: extended rollback segment, pinned blocks released
-
Cause: Doing recursive extent of rollback segment, trapped internally by the system
- ORA-01552: cannot use system rollback segment for non-system tablespace 'string'
-
Cause: Tried to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.
- ORA-01553: MAXEXTENTS must be no smaller than the string extents currently allocated
-
Cause: The number of extents allocated is greater than the MAXEXTENTS specified.
- ORA-01554: transaction concurrency limit reached reason:string params:string, string
-
Cause: Too many concurrent transactions
- ORA-01555: snapshot too old: rollback segment number string with name "string" too small
-
Cause: rollback records needed by a reader for consistent read are overwritten by other writers
- ORA-01556: MINEXTENTS for rollback segment must be greater than 1
-
Cause: Specified MINEXTENTS of less than 2 for rollback segment
- ORA-01557: rollback segment extents must be at least string blocks
-
Cause: Specified extent of less than minimum size for rollback segment
- ORA-01558: out of transaction ID's in rollback segment string
-
Cause: All the available transaction id's have been used
- ORA-01559: MAXEXTENTS for rollback segment must be greater than 1
-
Cause: Specified MAXEXTENTS of less than 2 for rollback segment
- ORA-01560: LIKE pattern contains partial or illegal character
-
Cause: like pattern is not formed correctly
- ORA-01561: failed to remove all objects in the tablespace specified
-
Cause: Failed to remove all objects when dropping a tablespace
- ORA-01562: failed to extend rollback segment number string
-
Cause: Failure occurred when trying to extend rollback segment
- ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC
-
Cause: Did not use the keyword PUBLIC to identified public rollback segment
- ORA-01564: rollback segment is not PUBLIC
-
Cause: The rollback segment segment identified is not public
- ORA-01565: error in identifying file 'string'
-
Cause: An error occurred while trying to identify a file.
- ORA-01566: file specified more than once in ALTER DATABASE
-
Cause: The list of files supplied to the command contained at least one duplicate.
- ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string)
-
Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread.
- ORA-01568: cannot set space quota on PUBLIC
-
Cause: Trying to set space quota on a tablespace for PUBLIC.
- ORA-01569: data file too small for system dictionary tables
-
Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables.
- ORA-01570: MINEXTENTS must be no larger than the string extents currently allocated
-
Cause: The number of extents allocated is smaller than the MINEXTENTS specified.
- ORA-01571: redo version string incompatible with ORACLE version string
-
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.
- ORA-01572: rollback segment 'string' cannot be brought online, string extents exceeded
-
Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.
- ORA-01573: shutting down instance, no further change allowed
-
Cause: Some process tries to make changes while the db is being shutdown
- ORA-01574: maximum number of concurrent transactions exceeded
-
Cause: the limit on the number of concurrent transactions has been hit
- ORA-01575: timeout waiting for space management resource
-
Cause: failed to acquire necessary resource to do space management.
- ORA-01576: The instance string is not enabled
-
Cause: The thread associated with instance is not enabled.
- ORA-01577: cannot add log file 'string' - file already part of database
-
Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database.
- ORA-01578: ORACLE data block corrupted (file # string, block # string)
-
Cause: The data block indicated was corrupt. This was a physical corruption, also called a media corruption. The cause is unknown but is most likely external to the database. If ORA-26040 is also signaled, the corruption is due to NOLOGGING or UNRECOVERABLE operations.
- ORA-01579: write error occurred during recovery
-
Cause: A write error occurred during recovery
- ORA-01580: error creating control backup file string
-
Cause: An operating system error occurred while attempting to create a control file backup.
- ORA-01581: attempt to use rollback segment (string) new extent (string) which is being allocated
-
Cause: Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated.
- ORA-01582: unable to open control file for backup
-
Cause: An operating system error occurred while attempting to open a control file for backup.
- 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.
- 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.
- ORA-01585: error identifying backup file string
-
Cause: An operating system error occurred when attempting to identify the file to be used for control file backup.
- ORA-01586: database must be mounted EXCLUSIVE and not open for this operation
-
Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE.
- ORA-01587: error during control file backup file copy
-
- 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, or a FLASHBACK DATABASE was done.
- ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
-
Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.
- ORA-01590: number of segment free list (string) exceeds maximum of string
-
Cause: storage parameter FREELIST GROUPS is too large.
- ORA-01591: lock held by in-doubt distributed transaction string
-
Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state.
- ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format
-
Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly.
- ORA-01593: rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
-
Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.
- ORA-01594: attempt to wrap into rollback segment (string) extent (string) 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
- ORA-01595: error freeing extent (string) of rollback segment (string))
-
Cause: Some error occurred while freeing inactive rollback segment extents.
- ORA-01596: cannot specify system in string parameter
-
Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message
- ORA-01597: cannot alter system rollback segment online or offline
-
Cause: Tried to online or offline the system rollback segment
- ORA-01598: rollback segment 'string' is not online
-
Cause: Could have been taken offline before by DBA or cleaned up by SMON.
- ORA-01599: failed to acquire rollback segment (string), cache space is full
-
Cause: the amount statically allocated is not enough based on max_rollback_segments parameter.
- ORA-01600: at most one "string" in clause "string" of string
-
Cause: The INIT.ORA parameter was mis-specified.
- ORA-01601: illegal bucket size in clause "string" of string
-
Cause: The bucket size was invalid for this parameter.
- ORA-01602: The PDB string is in the wrong state for a role change to string.
-
Cause: A role change was requested for a pluggable database (PDB) that was either already in the requested state or, was not a member of a Data Guard configuration.
- ORA-01603: illegal grouping size in clause "string" of string
-
Cause: The grouping size was invalid for this parameter.
- ORA-01604: illegal number range in clause "string" of string
-
Cause: The number range was invalid for this parameter.
- ORA-01605: missing numbers in clause "string" of string
-
Cause: The numbers were missing for this parameter.
- ORA-01606: parameter not identical to that of another mounted instance
-
Cause: A parameter was different on two instances.
- ORA-01607: cannot add logfile to the specified instance
-
Cause: The limit on the number of instances supported by the control file has been reached.
- ORA-01608: cannot bring rollback segment 'string' online, its status is (string)
-
Cause: Could have been brought online before by DBA or left as a result of process crash.
- ORA-01609: log string is the current log for thread string - cannot drop members
-
Cause: A member of the current log for a thread cannot be dropped.
- ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
-
Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was recreated with the RESETLOGS option, or the control file being used is a backup control file. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open.
- ORA-01611: thread number string is invalid - must be between 1 and string
-
Cause: A thread number in a command is greater than the number of threads supported by the control file.
- ORA-01612: instance string (thread string) is already enabled
-
Cause: An attempt was made to enable a thread that is already enabled.
- ORA-01613: instance string (thread string) only has string logs - at least 2 logs required to enable.
-
Cause: The thread cannot be enabled because it only has two online log files associated with it.
- ORA-01614: instance string (thread string) 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.
- ORA-01615: instance string (thread string) is mounted - cannot disable
-
Cause: Some instance, possibly this one, has allocated the thread for its use. The thread can not be disabled while in use.
- ORA-01616: instance string (thread string) is open - cannot disable
-
Cause: The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery.
- ORA-01617: cannot mount: string is not a valid thread number
-
Cause: The INIT.ORA parameter "thread" is not between 1 and the number of threads allowed by the control file.
- ORA-01618: redo thread string is not enabled - cannot mount
-
Cause: The INIT.ORA parameter "thread" requests a thread that is not enabled. A thread must be enabled before it can be mounted.
- ORA-01619: thread string is mounted by another instance
-
Cause: The INIT.ORA parameter "thread" requests a thread that has been mounted by another instance. Only one instance may use a thread.
- ORA-01620: no public threads are available for mounting
-
Cause: The INIT.ORA parameter "thread" is zero, its default value. There are no threads which have been publicly enabled, and not mounted.
- 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.
- 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 mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to.
- ORA-01623: log string is current log for instance string (thread string) - 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.
- ORA-01624: log string needed for crash recovery of instance string (thread string)
-
Cause: A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log.
- ORA-01625: rollback segment 'string' does not belong to this instance
-
Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance.
- ORA-01626: rollback segment number 'string' cannot handle more transactions
-
Cause: Too many transactions in this segment.
- ORA-01627: rollback segment number 'string' is not online
-
Cause: Could have been taken offline before by DBA or cleaned up by SMON.
- ORA-01628: max # extents (string) reached for rollback segment string
-
Cause: An attempt was made to extend a rollback segment that was already at the MAXEXTENTS value.
- ORA-01629: max # extents (string) reached saving undo for tablespace string
-
Cause: Save undo for the offline tablespace at max extents
- ORA-01630: max # extents (string) reached in temp segment in tablespace string
-
Cause: A temp segment tried to extend past max extents.
- ORA-01631: max # extents (string) reached in table string.string
-
Cause: A table tried to extend past maxextents
- ORA-01632: max # extents (string) reached in index string.string
-
Cause: An index tried to extend past maxextents
- ORA-01633: Real Application Clusters Option needed for this operation
-
Cause: System doesn't have Real Application Clusters configured
- ORA-01634: rollback segment number 'string' is about to go offline
-
Cause: The rollback segment specified was marked to go offline by DBA.
- ORA-01635: rollback segment #string specified not available
-
Cause: (same as 1545)
- ORA-01636: rollback segment 'string' is already online
-
Cause: The instance is trying to online an already online RS
- ORA-01637: rollback segment 'string' is being used by another instance (#string)
-
Cause: The instance is trying to online a RS already in use by another instance
- ORA-01638: parameter string does not allow ORACLE version string to mount cluster database
-
Cause: The recovery compatible parameter is set too low to allow this software version to mount in cluster database mode.
- ORA-01639: instance string has no thread assigned to it
-
Cause: There is no mapping from instance to thread for this instance in the control file.
- ORA-01640: cannot make tablespace read-only with changes by in-doubt transactions
-
Cause: An attempt was made to alter a tablespace read-only while there were changes in the tablespace made by in-doubt distributed transactions. The in-doubt transactions must commit or rollback to ensure that there is no undo for a tablespace before it can be made read-only.
- ORA-01641: tablespace 'string' is not online - cannot add data file
-
Cause: Attempting to add a datafile to a tablespace that has been set to read-only or offline.
- ORA-01642: begin backup not needed for read-only tablespace 'string'
-
Cause: Attempting to begin or end a backup for a tablespace that has been set to read-only.
- ORA-01643: system tablespace can not be made read-only
-
Cause: Attempting to set the system tablespace to read-only. The system tablespace must remain read write for database operation.
- ORA-01644: tablespace 'string' is already read-only
-
Cause: Attempting to make tablespace read-only that is already read-only.
- ORA-01645: previous attempt to make read write is half complete
-
Cause: A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be useable after a resetlogs if its files are offline.
- ORA-01646: tablespace 'string' is not read-only - cannot make read write
-
Cause: Attempting to make a tablespace read write that is not read-only. It may be either online or offline.
- ORA-01647: tablespace 'string' is read-only, cannot allocate space in it
-
Cause: Tried to allocate space in a read-only tablespace
- ORA-01648: Log string is the current log of disabled instance string (thread string).
-
Cause: An attempt to enable the thread failed and a log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log cannot be cleared or archived.
- ORA-01649: operation not allowed with a backup control file
-
Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup.
- ORA-01650: unable to extend rollback segment string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace.
- ORA-01651: unable to extend save undo segment by string for tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for saving undo entries for the indicated offline tablespace.
- ORA-01652: unable to extend temp segment by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated.
- ORA-01653: unable to extend table string.string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated.
- ORA-01654: unable to extend index string.string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.
- ORA-01655: unable to extend cluster string.string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated.
- ORA-01656: max # extents (string) reached in cluster string.string
-
Cause: A cluster tried to extend past maxextents
- ORA-01657: invalid SHRINK option value
-
Cause: The specified value must be an integer.
- ORA-01658: unable to create INITIAL extent for segment in tablespace string
-
Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.
- ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string
-
Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.
- ORA-01660: tablespace 'string' is already permanent
-
Cause: Attempting to make tablespace permanent that is already permanent.
- ORA-01661: tablespace 'string' is already temporary
-
Cause: Attempting to make tablespace temporary that is already temporary.
- ORA-01662: tablespace 'string' is non-empty and cannot be made temporary
-
Cause: Tried to convert a non-empty tablespace to a temporary tablespace
- ORA-01663: the contents of tablespace 'string' is constantly changing
-
Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY.
- ORA-01664: Transaction which has expanded the Sort Segment has aborted
-
Cause: Internal Error.
- ORA-01665: control file is not a standby control file
-
Cause: An attempt was made to mount, recover, or activate either a standby multitenant container database (CDB) without a standby control file, or a pluggable database (PDB) that was not created as an Oracle Data Guard standby database.
- ORA-01666: control file is for a standby database
-
Cause: Attempting to mount, recover, or open a standby database without the appropriate command option to designate a standby database.
- ORA-01667: cannot add any more tablespaces: limit of string exceeded
-
Cause: There is no more room in the control file for adding tablespaces.
- ORA-01668: standby database requires DROP option for offline of data file
-
Cause: Attempting to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later.
- ORA-01669: standby database control file not consistent
-
Cause: Attempting to activate a standby database with a control file that has not been recovered to the same point as the data files. Most likely the control file was just copied from the primary database and has not been used for recovery.
- ORA-01670: new datafile string needed for standby database recovery
-
Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby.
- ORA-01671: control file is a backup, cannot make a standby control file
-
Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database.
- ORA-01672: control file may be missing files or have extra ones
-
Cause: Attempting to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match.
- ORA-01673: data file string has not been identified
-
Cause: This data file was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we can not create a standby control file.
- ORA-01674: data file string is an old incarnation rather than current file
-
Cause: Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file.
- ORA-01675: max_commit_propagation_delay inconsistent with other instances
-
Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent with those in other instances.
- ORA-01676: standby file name conversion of 'string' exceeds maximum length of string
-
Cause: When the given file name was converted to the name used for the standby database, the converted name was bigger than the maximum allowed file name.
- ORA-01677: standby file name conversion parameters differ from other instance
-
Cause: The DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameters were not the same as in other instances that already had the database mounted.
- ORA-01678: parameter string must be pairs of pattern and replacement strings
-
Cause: The initialization parameter does not have even number of strings for its value. The odd numbered strings are patterns to be found in file names. The even numbered strings are used to replace the corresponding patterns when found in file names.
- ORA-01679: database is being opened
-
Cause: An attempt was made to activate a standby database when the database was in the middle of being opened.
- ORA-01680: unable to extend LOB segment by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for a LOB segment in the tablespace indicated.
- ORA-01681: max # extents (string) reached in LOB segment in tablespace string
-
Cause: A LOB segment tried to extend past max extents.
- ORA-01682: read-only DB cannot allocate temporary space in tablespace string
-
Cause: Temporary space (usually for sorting) could not be allocated in either main storage or a tempfile. An attempt was made to allocate the space from the tablespace named, but the database is opened read-only. The database open requires a sort work space.
- ORA-01683: unable to extend index string.string partition string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated.
- ORA-01684: max # extents (string) reached in table string.string partition string
-
Cause: A table tried to extend past maxextents
- ORA-01685: max # extents (string) reached in index string.string partition string
-
Cause: An index tried to extend past maxextents
- ORA-01686: max # files (string) reached for the tablespace string
-
Cause: The number of files for a given tablespace has reached its maximum value
- ORA-01687: specified logging attribute for tablespace 'string' is same as the existing
-
Cause: Attempting to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute
- ORA-01688: unable to extend table string.string partition string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated.
- ORA-01689: syntax error in clause "string" of string
-
Cause: There was a syntax in the INIT.ORA parameter.
- ORA-01690: sort area size too small
-
Cause: sort area size too small to fit two records in memory
- ORA-01691: unable to extend lob segment string.string by string in tablespace string
-
Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.
- ORA-01692: Unable to extend the LOB segment string.string partition string by string in tablespace string.
-
Cause: Failed to allocate an extent of the required number of blocks for the LOB segment in the specified tablespace.
- ORA-01693: max # extents (string) reached in lob segment string.string
-
Cause: A LOB segment tried to extend past maxextents
- ORA-01694: max # extents (string) reached in lob segment string.string partition string
-
Cause: A LOB segment tried to extend past maxextents
- ORA-01695: error converting rollback segment string to version 8.0.2
-
Cause: Version 8.0.1 database may not have shutdown cleanly
- ORA-01696: control file is not a clone control file
-
Cause: Attempting to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current control file for a clone.
- ORA-01697: control file is for a clone database
-
Cause: Attempting to mount a clone database without the appropriate command option to designate a clone database.
- ORA-01698: a clone database may only have SYSTEM rollback segment online
-
Cause: Attempting to online a rollback segment in a clone database.
- ORA-01699: tablespace 'string' is being imported for point in time recovery
-
Cause: Attempting to online a tablespace or begin another point in time import while a point in time import was already in progress.
- ORA-01700: duplicate username in list
-
- ORA-01701: a cluster is not appropriate here
-
- ORA-01702: a view is not appropriate here
-
Cause: Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view.
- ORA-01703: missing SYNONYM keyword
-
- ORA-01704: string literal too long
-
Cause: The string literal is longer than 4000 characters.
- ORA-01705: an outer join cannot be specified on a correlation column
-
- ORA-01706: user function result value was too large
-
- ORA-01707: missing LIST keyword
-
- ORA-01708: ACCESS or SESSION expected
-
- ORA-01709: program does not exist
-
- ORA-01710: missing OF keyword
-
- ORA-01711: duplicate privilege listed
-
- ORA-01712: you cannot grant a privilege which you do not have
-
- ORA-01713: GRANT OPTION does not exist for that privilege
-
- ORA-01714: error in execution of user function
-
- ORA-01715: UNIQUE may not be used with a cluster index
-
Cause: An attempt was made to create a cluster index with the UNIQUE attribute.
- 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.
- ORA-01717: seccta: invalid access mode token passed
-
- ORA-01718: BY ACCESS | SESSION clause not allowed for NOAUDIT
-
Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.
- ORA-01719: outer join operator (+) not allowed in operand of OR or IN
-
Cause: An outer join appears in an or clause.
- ORA-01720: grant option does not exist for string.string
-
Cause: A grant was attempted on a view or a view was being replaced and the grant option was not present for an underlying object.
- ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction
-
Cause: The USERENV('COMMITSCN') function can only be used once in a transaction.
- ORA-01722: invalid number
-
Cause: The specified number was invalid.
- ORA-01723: zero-length columns are not allowed
-
Cause: Columns with zero length were not allowed.
- ORA-01724: floating point precision is out of range (1 to 126)
-
Cause: The specified number had an invalid range.
- ORA-01725: USERENV('COMMITSCN') not allowed here
-
Cause: The function USERENV('COMMITSCN') is only allowed as a top-level expression in the VALUES clause of an INSERT statement, and on the right-hand side of an assignment in an UPDATE statement.
- ORA-01726: a table is not appropriate here
-
Cause: A table name was used in a statement in which tables were not permitted.
- ORA-01727: numeric precision specifier is out of range (1 to 38)
-
Cause: The precision specified for a number column in a CREATE or ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If no precision was specified, a default precision of 22 digits was used.
- ORA-01728: numeric scale specifier is out of range (-84 to 127)
-
Cause: The scale specified for a numeric field in a CREATE or ALTER TABLE or CREATE CLUSTER statement was not in the valid range. It should be between -84 and 127.
- ORA-01729: database link name expected
-
Cause: A database link name did not follow the at-sign (@) in a reference to a table in a remote database.
- 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 were specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause.
- ORA-01731: circular view definition encountered
-
Cause: Through a series of CREATE and DROP VIEW statements, a view was defined that referred to itself. For example, VIEW1 might include a column from VIEW2 that was defined as a column in VIEW1. View definitions may be seen by querying the data dictionary.
- 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.
- 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.
- ORA-01734: illegal parameters - EXTENT MIN higher than EXTENT MAX
-
Cause: A wrong value is specified for the parameter.
- ORA-01735: invalid ALTER TABLE option
-
Cause: An invalid option was specified in an ALTER TABLE statement.
- ORA-01736: [NOT] SUCCESSFUL expected
-
Cause: An AUDIT or NOAUDIT statement contained WHENEVER followed by something other than SUCCESSFUL or NOT SUCCESSFUL.
- ORA-01737: valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE
-
Cause: The lock mode entered was not recognized.
- ORA-01738: missing IN keyword
-
Cause: In a LOCK TABLE statement, the keyword IN was missing.
- 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.
- 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.
- 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.
- ORA-01742: comment not terminated properly
-
Cause: The indicated comment or hint begun with the /* token did not have the terminating */.
- ORA-01743: only pure functions can be indexed
-
Cause: The indexed function uses SYSDATE or the user environment.
- ORA-01744: inappropriate INTO
-
Cause: The INTO clause may not be used in a subquery.
- 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.
- ORA-01746: indicator variable not permitted here
-
Cause: An indicator variable was not permitted in this context.
- ORA-01747: invalid column specification: string
-
Cause: A column name was specified improperly in the current SQL statement.
- ORA-01748: only simple column names allowed here
-
Cause: This SQL statement did not allow a qualified column name, such as username.table.column or table.column.
- ORA-01749: you may not GRANT/REVOKE privileges to/from yourself
-
Cause: Grantor was not allowed to grant or revoke object or system privileges to self.
- ORA-01750: UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column
-
Cause: Although it was possible to GRANT update privileges on a column-by-column basis, it was only possible to REVOKE them for an entire table.
- ORA-01751: Invalid dump undo option
-
Cause: An invalid option is specified in the ALTER DUMP UNDO command.
- ORA-01752: cannot delete from view without exactly one key-preserved table
-
Cause: The deleted table had - no key-preserved tables, - more than one key-preserved table, or - the key-preserved table was an unmerged view.
- ORA-01753: column definition incompatible with clustered column definition
-
Cause: An attempt was made to create a table in a cluster and one of the table's clustered columns is not compatible with the corresponding cluster key column.
- ORA-01754: a table may contain only one column of type LONG
-
Cause: An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.
- ORA-01755: Must specify an extent number or block number
-
Cause: Expecting an extent or block number but something else was specified.
- ORA-01756: quoted string not properly terminated
-
Cause: A quoted string must be terminated with a single quote mark (').
- ORA-01757: Must specify an object number
-
Cause: Expecting an object number but something else was specified.
- ORA-01758: table must be empty to add mandatory (NOT NULL) column
-
Cause: It was not possible to define a new column as NOT NULL if rows already existed in the table being modified.
- ORA-01759: user function is incorrectly defined
-
Cause: A user function was improperly defined.
- ORA-01760: illegal argument for function
-
Cause: The argument or arguments specified for the function were not valid in this context.
- ORA-01761: DML operation does not map to a unique table in the join
-
Cause: The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.
- ORA-01762: vopdrv: view query block not in FROM
-
Cause: This is an internal error message not normally issued.
- ORA-01763: update or delete involves outer joined table
-
Cause: For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table, or the underlying table being updated in a join view is referenced on the right side of an outer join or full outer join in the view.
- ORA-01764: new update value of join is not guaranteed to be unique
-
Cause: A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.
- ORA-01765: specifying owner's name of the table is not allowed
-
Cause: An attempt was made to rename the object with dotted object name.
- ORA-01766: dictionary table not allowed in this context
-
Cause: The name of a data dictionary object was used outside the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object was to SELECT from it.
- 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.
- ORA-01768: number string too long
-
Cause: A number entered exceeded the limit of 255 characters, including digits, sign, decimal point, and exponent.
- ORA-01769: duplicate CLUSTER option specifications
-
Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.
- 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.
- ORA-01771: illegal option for a clustered table
-
Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself.
- ORA-01772: Must specify a value for LEVEL
-
Cause: Expecting the value of LEVEL but something else was specified.
- ORA-01773: may not specify column datatypes in this CREATE TABLE
-
Cause: Column data types or virtual columns were specified in a SELECT statement used to create and load a table directly.
- ORA-01774: Dump undo option specified more than once
-
Cause: The same option for ALTER DUMP UNDO was specified twice.
- ORA-01775: looping chain of synonyms
-
Cause: Through a series of CREATE synonym statements, a synonym was defined that referred to itself. For example, the following definitions are circular: CREATE SYNONYM s1 for s2 CREATE SYNONYM s2 for s3 CREATE SYNONYM s3 for s1
- ORA-01776: cannot modify more than one base table through a join view
-
Cause: Columns belonging to more than one underlying table were either inserted into or updated.
- ORA-01777: WITH GRANT OPTION not allowed in this system
-
Cause: This version of Oracle did not support the WITH GRANT OPTION.
- ORA-01778: maximum subquery nesting level exceeded
-
Cause: An attempt was made to use more than 255 levels of nested subqueries.
- ORA-01779: cannot modify a column which maps to a non key-preserved table
-
Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.
- ORA-01780: string literal required
-
Cause: In a COMMENT statement, the Comment following the keyword IS must be a quoted string literal.
- ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT
-
Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.
- ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table
-
Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.
- ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified
-
Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.
- ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled
-
Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.
- ORA-01785: ORDER BY item must be the number of a SELECT-list expression
-
Cause: Either an ORDER BY item for a set expression was not a column number, or the ORDER BY item was not the number of a SELECT list column.
- 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.
- 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.
- ORA-01788: CONNECT BY clause required in this query block
-
Cause: A START WITH clause was specified without a CONNECT BY clause.
- 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.
- 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.
- ORA-01791: not a SELECTed expression
-
Cause: There was an incorrect ORDER BY item. The query was a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands were constants or SELECT list expressions.
- ORA-01792: maximum number of columns in a table or view is 1000
-
Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.
- ORA-01793: maximum number of index columns is 32
-
Cause: While creating an index, more than 32 columns were specified.
- ORA-01794: maximum number of cluster columns is 32
-
Cause: More than 32 columns were specified in the cluster key.
- ORA-01795: maximum number of expressions in a list is 1000
-
Cause: Number of expressions in the query exceeded than 1000. Note that unused column/expressions are also counted Maximum number of expressions that are allowed are 1000.
- ORA-01796: this operator cannot be used with lists
-
Cause: A relational operator was not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN.
- ORA-01797: this operator must be followed by ANY or ALL
-
Cause: The keyword ANY or ALL was missing.
- ORA-01798: missing EXCEPTION keyword
-
Cause: The EXCEPTION keyword was missing from the ENABLE clause.
- ORA-01799: a column may not be outer-joined to a subquery
-
Cause: expression(+) relop (subquery) is not allowed.
- 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 was entered as a date, it must be less than 220 characters long.
- ORA-01801: date format is too long for internal buffer
-
Cause: The date format string was too long to process. This occurred only if several long literals are specified as part of a date.
- ORA-01802: Julian date is out of range
-
Cause: An invalid Julian date was entered. Valid Julian dates ran from 1 to 3,442,447.
- ORA-01803: Failed to get system date and time.
-
Cause: An internal failure in the system clock occurred.
- ORA-01804: failure to initialize timezone information
-
Cause: The timezone information file was not properly read.
- ORA-01805: possible error in date/time operation
-
Cause: The timezone files on client and server do not match. Operation can potentially result in incorrect results based on local timezone file.
- ORA-01810: format code appears twice
-
Cause: A format code was listed twice in a date specification. Each format code may be specified only once in the function TO_DATE.
- 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.
- 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.
- 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.
- ORA-01814: AM/PM conflicts with use of A.M./P.M.
-
Cause: Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified.
- ORA-01815: BC/AD conflicts with use of B.C./A.D.
-
Cause: Both types of BC/AD indicators were listed in a date specification. If one of the BC/AD indicator format masks, such as BC or B.C., was specified in the date, the other may not be specified.
- 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.
- 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.
- ORA-01818: 'HH24' precludes use of meridian indicator
-
Cause: A date specification contained both a 24-hour time format code and a meridian indicator code. If hours are specified using the 24-hour time format (HH24), a meridian indicator, AM or PM, may not be specified.
- 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.
- 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.
- ORA-01821: date format not recognized
-
Cause: A date specification contained an invalid format code.
- ORA-01822: era format code is not valid with this calendar
-
Cause: An era format code, E or EE, was specified with a calendar which did not use era information.
- 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. The remaining data was not required.
- ORA-01831: year conflicts with Julian date
-
Cause: The wrong year was specified with a Julian day. If a year was specified with a Julian date, it must be the year in which the Julian date occurred.
- 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 was specified with a Julian date, it must be the same day as the Julian date.
- ORA-01833: month conflicts with Julian date
-
Cause: The wrong month was specified with a Julian date. If a month is specified with a Julian date, it must be the month in which the Julian date occurs.
- 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 was specified with a Julian date, it must be the same day of the month as the Julian date.
- ORA-01835: day of week conflicts with Julian date
-
Cause: A Julian date was specified with the day of the week, but the weekday did not correspond to the Julian date. If the day of the week was specified with a Julian date, it must be the same day of the week as the Julian date.
- ORA-01836: hour conflicts with seconds in day
-
Cause: The wrong hour was specified with seconds in the day. If an hour was specified with seconds past midnight (SSSSS), it must be the hour in which the seconds value fell.
- 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 occurred.
- 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) fell.
- ORA-01839: date not valid for month specified
-
Cause: The day of the month specified in the date was invalid for the given month. The day of the month (DD) must be between 1 and the number of days in the month.
- ORA-01840: input value not long enough for date format
-
Cause: The data to be converted to date format was incomplete; the date format picture was longer than the input data.
- ORA-01841: (full) year must be between -4713 and +9999, and not be 0
-
Cause: Illegal year entered
- 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.
- ORA-01843: An invalid month was specified.
-
Cause: You specified a date with an invalid month.
- ORA-01844: week of year must be between 1 and 52
-
Cause: An invalid value was specified for the week of the year in a date. Week of the year (WW) must be between 1 and 52.
- ORA-01845: week of month must be between 1 and 5
-
Cause: An invalid value was specified for the week of the month in a date. Week of the month (W) must be between 1 and 5.
- 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 - 1-7, for format code D
- ORA-01847: day of month must be between 1 and last day of month
-
Cause: The day of the month listed in a date was invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.
- ORA-01848: day of year must be between 1 and 365 (366 for leap year)
-
Cause: An invalid day of the year was specified in a date. Day of the year (DDD) must be between 1 and 365 for a non-leap year or 1 and 366 for a leap year.
- 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.
- 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) was listed, the specified hour must be between 0 and 23.
- ORA-01851: minutes must be between 0 and 59
-
Cause: An invalid minute value was specified in a date. Minutes must be between 0 and 59.
- 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) was used.
- 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) was used.
- ORA-01854: julian date must be between 1 and 5373484
-
Cause: An invalid Julian date was entered.
- 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., AM or PM, was included in a date format, the date must include a valid meridian indicator.
- 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.
- ORA-01857: not a valid time zone
-
Cause: An incorrect time zone code was specified for the NEW_TIME function.
- ORA-01858: A non-numeric character was found instead of a numeric character.
-
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.
- ORA-01859: a non-alphabetic character was found where an alphabetic was expected
-
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.
- ORA-01860: week of year must be between 1 and 53
-
Cause: A week number outside the range 1 to 53 was specified.
- ORA-01861: literal does not match format string
-
Cause: A literal was specified that did not match the the format string, excluding leading spaces.
- ORA-01862: the numeric value does not match the length of the format item
-
Cause: When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will.
- ORA-01863: the year is not supported for the current calendar
-
Cause: The year is not supported for the current calendar.
- ORA-01864: the date is out of range for the current calendar
-
Cause: Your calendar doesn't extend to the specified date.
- ORA-01865: not a valid era
-
Cause: Era input does not match a known era.
- ORA-01866: the datetime class is invalid
-
Cause: This is an internal error.
- ORA-01867: the interval is invalid
-
Cause: The character string you specified is not a valid interval.
- ORA-01868: the leading precision of the interval is too small
-
Cause: The leading precision of the interval is too small to store the specified interval.
- ORA-01869: reserved for future use
-
Cause: Not an error.
- ORA-01870: the intervals or datetimes are not mutually comparable
-
Cause: The intervals or datetimes are not mutually comparable.
- ORA-01871: the number of seconds must be less than 60
-
Cause: The number of seconds specified was greater than 59.
- ORA-01872: reserved for future use
-
Cause: Not an error.
- ORA-01873: the leading precision of the interval is too small
-
Cause: The leading precision of the interval is too small to store the specified interval.
- ORA-01874: time zone hour must be between -15 and 15
-
Cause: The time zone hour specified was not in the valid range.
- ORA-01875: time zone minute must be between -59 and 59
-
Cause: The time zone minute specified was not in the valid range.
- ORA-01876: year must be at least -4713
-
Cause: The specified year was not in range.
- ORA-01877: string is too long for internal buffer
-
Cause: This is an internal error.
- ORA-01878: specified field not found in datetime or interval
-
Cause: The specified field was not found in the datetime or interval.
- ORA-01879: the hh25 field must be between 0 and 24
-
Cause: The specified hh25 field was not in the valid range.
- ORA-01880: the fractional seconds must be between 0 and 999999999
-
Cause: The specified fractional seconds were not in the valid range.
- ORA-01881: timezone region ID is invalid
-
Cause: The region ID referenced an invalid region.
- ORA-01882: time zone region not found
-
Cause: The specified time zone region name was not found.
- ORA-01883: overlap was disabled during a region transition
-
Cause: The region was changing state and the overlap flag was disabled.
- ORA-01884: divisor is equal to zero
-
Cause: An attempt was made to divide by zero.
- ORA-01885: public synonym collides with Oracle-supplied schema name
-
Cause: The public synonym was the same as the Oracle-supplied schema name.
- ORA-01886: use CREATE PUBLIC SYNONYM statement to create a public synonym
-
Cause: An attempt was made to create a public synonym by issuing a CREATE SYNONYM statement naming PUBLIC as the name of the schema to which the synonym belongs.
- ORA-01887: use ALTER PUBLIC SYNONYM statement to alter a public synonym
-
Cause: An attempt was made to alter a public synonym by issuing an ALTER SYNONYM statement naming PUBLIC as the name of the schema to which the synonym belongs.
- ORA-01888: use DROP PUBLIC SYNONYM statement to drop a public synonym
-
Cause: An attempt was made to drop a public synonym by issuing a DROP SYNONYM statement naming PUBLIC as the name of the schema to which the synonym belongs.
- ORA-01890: NLS error detected
-
Cause: An NLS error was detected.
- ORA-01891: Datetime/Interval internal error
-
Cause: Internal error.
- ORA-01898: too many precision specifiers in date format model
-
Cause: While trying to truncate or round dates, too many format models (like 'YY' or 'MM') for ROUND or TRUNC were found in the call. Not all date format models can be combined in a call to TRUNC and ROUND.
- ORA-01899: bad precision specifier
-
Cause: An invalid precision code was specified in a date.
- ORA-01900: LOGFILE keyword expected
-
Cause: keyword missing
- ORA-01901: ROLLBACK keyword expected
-
Cause: keyword missing
- ORA-01902: SEGMENT keyword expected
-
Cause: keyword missing
- ORA-01903: EVENTS keyword expected
-
Cause: keyword missing
- ORA-01904: DATAFILE keyword expected
-
Cause: keyword missing
- ORA-01905: STORAGE keyword expected
-
Cause: keyword missing
- ORA-01906: BACKUP keyword expected
-
Cause: keyword missing
- ORA-01907: TABLESPACE keyword expected
-
Cause: keyword missing
- ORA-01908: EXISTS keyword expected
-
Cause: keyword missing
- ORA-01909: REUSE keyword expected
-
Cause: keyword missing
- ORA-01910: TABLES keyword expected
-
Cause: keyword missing
- ORA-01911: CONTENTS keyword expected
-
Cause: keyword missing
- ORA-01912: ROW keyword expected
-
Cause: keyword missing
- ORA-01913: EXCLUSIVE keyword expected
-
Cause: keyword missing
- ORA-01914: invalid auditing option for sequence numbers
-
Cause: AUDIT or NOAUDIT was specified as an auditing option that is not valid for sequence numbers.
- ORA-01915: invalid auditing option for views
-
Cause: AUDIT or NOAUDIT was specified on views that had audit options not valid for views.
- ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND, END, DROP, ENABLE, REMOVE, SUSPEND, ENCRYPT, or DECRYPT expected
-
Cause: An expected keyword was not used for the data file or the temporary file clause. Note the ENCRYPT and DECRYPT keywords are only applicable to the data file.
- ORA-01917: user or role 'string' does not exist
-
Cause: A user or role by that name did not exist.
- ORA-01918: user 'string' does not exist
-
Cause: User does not exist in the system.
- ORA-01919: role 'string' does not exist
-
Cause: A role by the specified name did not exist.
- ORA-01920: user name 'string' conflicts with another user or role name
-
Cause: There is already a user or role with that name.
- ORA-01921: role name 'string' conflicts with another user or role name
-
Cause: There is already a user or role with that name.
- ORA-01922: CASCADE must be specified to drop 'string'
-
Cause: Cascade is required to remove this user from the system. The user own's object which will need to be dropped.
- ORA-01923: CASCADE aborted, objects locked by another user
-
Cause: Cannot drop the user's objects; someone has them locked.
- ORA-01924: role 'string' not granted or does not exist
-
Cause: Either the role was not granted to the user, or the role did not exist.
- ORA-01925: unused error
-
- ORA-01926: cannot GRANT to a role WITH GRANT OPTION
-
Cause: Role cannot have a privilege with the grant option.
- ORA-01927: cannot REVOKE privileges you did not grant
-
Cause: You can only revoke privileges you granted.
- ORA-01928: GRANT option not granted for all privileges
-
Cause: In order to grant a privilege, you must first have the privilege with the grant option.
- ORA-01929: no privileges to GRANT
-
Cause: "ALL" was specified but the user doesn't have any privileges with the grant option.
- ORA-01930: auditing the object is not supported
-
Cause: The AUDIT or NOAUDIT commands were specified for an object that could not be audited.
- ORA-01931: cannot grant string to a role
-
Cause: An attempt to grant privileges to a role failed. UNLIMITED TABLESPACE, REFERENCES, INDEX, Administrative Privileges like SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, and SYSRAC cannot be granted to a role.
- ORA-01932: ADMIN option not granted for role 'string'
-
Cause: The operation requires the admin option on the role.
- 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.
- ORA-01934: circular role grant detected
-
Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself.
- ORA-01935: missing user or role name
-
Cause: A user or role name was expected.
- ORA-01936: cannot specify owner when creating users or roles
-
Cause: Users and roles do not have owners.
- ORA-01937: missing or invalid role name
-
Cause: A valid role name was expected.
- ORA-01938: IDENTIFIED BY must be specified for CREATE USER
-
Cause: Cannot create a user without specifying a password or "IDENTIFIED EXTERNALLY" for ASM instance.
- ORA-01939: only the ADMIN OPTION can be specified
-
Cause: System privileges and roles can only be granted with the admin option. The grant option cannot be used with system privileges and roles. The delegate option cannot be used with system privileges.
- ORA-01940: cannot drop a user that is currently connected
-
Cause: Attempt was made to drop a user that is currently logged in.
- ORA-01941: SEQUENCE keyword expected
-
Cause: keyword missing
- ORA-01942: IDENTIFIED BY and EXTERNALLY cannot both be specified
-
Cause: A user cannot be specified to have and not have a password.
- ORA-01944: Only one IDENTIFIED clause or one NO AUTHENTICATION clause is allowed.
-
Cause: Either the IDENTIFIED clause was specified twice, or the NO AUTHENTICATION clause was specified twice, or both the IDENTIFIED clause and NO AUTHENTICATION clause were specified together.
- ORA-01945: DEFAULT ROLE[S] already specified
-
Cause: The default roles clause has been given twice.
- ORA-01946: DEFAULT TABLESPACE already specified
-
Cause: The default tablespace clause has been given twice.
- ORA-01947: TEMPORARY TABLESPACE already specified
-
Cause: The temporary tablespace clause has been given twice.
- ORA-01948: identifier's name length (string) exceeds maximum (string)
-
Cause: A name has been specified that is too long. For example, dbms_session.is_role_enabled() specifies a role name that is too long.
- ORA-01949: ROLE keyword expected
-
Cause: The role keyword is required here.
- ORA-01950: no privileges on tablespace 'string'
-
Cause: User does not have privileges to allocate an extent in the specified tablespace.
- ORA-01951: ROLE 'string' not granted to 'string'
-
Cause: The role you tried to revoke was not granted to the user.
- ORA-01952: system privileges not granted to 'string'
-
Cause: A system privilege you tried to revoke was not granted to the user.
- 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 perform the functionality
- ORA-01954: DEFAULT ROLE clause not valid for CREATE USER
-
Cause: Default roles cannot be specified for create user.
- ORA-01955: DEFAULT ROLE 'string' not granted to user
-
Cause: The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the default role clause.
- ORA-01956: invalid command when OS_ROLES are being used
-
Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is TRUE.
- ORA-01957: Keyword MIN or MAX expected, not found
-
Cause: The keyword MIN or MAX was expected as an argument.
- ORA-01958: Must supply an integer for the LAYER option
-
Cause: An item other than an integer was entered for the LAYER option.
- ORA-01959: Must supply an integer for the OPCODE option
-
Cause: An item other than an integer was entered for the OPCODE option. The value in ALTER SYSTEM DUMP ... OPCODE value must be an integer.
- ORA-01960: Invalid dump logfile option
-
Cause: An invalid option was entered for the ALTER SYSTEM DUMP LOGFILE option command.
- ORA-01961: Invalid dump option
-
Cause: An invalid option was entered for the ALTER SYSTEM DUMP statement.
- ORA-01962: Must specify a file number or log sequence number
-
Cause: An invalid file number or log sequence number was specified.
- ORA-01963: Must specify a block number
-
Cause: An invalid block number was specified.
- ORA-01964: Must specify a time for the TIME option
-
Cause: A value was entered for the TIME option that could not be interpreted as a date.
- ORA-01965: Must specify a PERIOD
-
Cause: A period was missing between the file number and the block number.
- ORA-01966: DEFAULT COLLATION already specified
-
Cause: The default collation clause was specified twice.
- ORA-01967: invalid option for CREATE CONTROLFILE
-
Cause: An invalid CREATE CONTROLFILE option is present.
- ORA-01968: Only specify RESETLOGS or NORESETLOGS once
-
Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once
- ORA-01969: You must specify RESETLOGS or NORESETLOGS
-
Cause: Missing a RESETLOGS or a NORESETLOGS
- ORA-01970: You must specify a database name for CREATE CONTROLFILE
-
Cause: Missing a database name
- ORA-01971: Illegal ALTER TRACING option
-
Cause: An invalid ALTER TRACING option was present.
- ORA-01972: Must specify a string for ALTER TRACING ENABLE or DISABLE
-
Cause: Something other than a valid identifier was specified for ALTER TRACING ENABLE or DISABLE.
- ORA-01973: Missing change number
-
Cause: Keyword "CHANGE" found but change number not specified.
- ORA-01974: Illegal archive option
-
Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command
- ORA-01975: Illegal character in change number string
-
Cause: An invalid change number was supplied.
- ORA-01976: Missing change number
-
Cause: A change number was required, but not supplied.
- ORA-01977: Missing thread number
-
Cause: Keyword "THREAD" found but thread number not specified.
- ORA-01978: Missing sequence number
-
Cause: Keyword "SEQUENCE" found but sequence number not specified.
- ORA-01979: missing or invalid password for role 'string'
-
Cause: An attempt was made to enable a role without giving the proper password.
- ORA-01980: error during OS ROLE initialization
-
Cause: An OS error occurred while loading a users OS ROLES.
- ORA-01981: CASCADE CONSTRAINTS must be specified to perform this revoke
-
Cause: During this revoke some foreign key constraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified.
- ORA-01982: invalid audit option for table specified
-
Cause: An invalid AUDIT or NOAUDIT option, like REFERENCE or EXECUTE, was specified for a table.
- ORA-01983: invalid AUDIT or NOAUDIT operation while specifying ON DEFAULT
-
Cause: An invalid AUDIT or NOAUDIT operation was requested for the object (like REFERENCES) while specifying the ON DEFAULT clause.
- ORA-01984: invalid audit option specified for procedure, package, or function
-
Cause: An invalid AUDIT or NOAUDIT option was specified for the procedure, package, or function while using the DEFAULT clause.
- ORA-01985: cannot create user as LICENSE_MAX_USERS parameter exceeded
-
Cause: Maximum users in the database license limit exceeded.
- ORA-01986: OPTIMIZER_GOAL is obsolete
-
Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced.
- ORA-01987: client os username is too long
-
Cause: A client's os username is too long for the os logon to succeed.
- ORA-01988: remote os logon is not allowed
-
Cause: Remote os login attempted when not allowed.
- ORA-01989: role 'string' not authorized by operating system
-
Cause: The os role does not exist, is not granted to you, or you did not provide the correct password.
- ORA-01990: Error opening password file string.
-
Cause: The password file did not exist or was inaccessible.
- ORA-01991: invalid password file 'string'
-
Cause: The specified password file name is invalid.
- ORA-01992: error closing password file 'string'
-
Cause: The password file could not be closed because of an operating system error or because an authentication action failed.
- ORA-01993: Error writing to password file string.
-
Cause: The password file could not be written to because of an operating system error or because an authentication action failed.
- ORA-01994: Password file missing or disabled
-
Cause: The operation failed either because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the password file was missing.
- ORA-01995: error reading password file 'string'
-
Cause: An operating system error occurred when trying to read the password file.
- ORA-01996: GRANT failed: password file 'string' is full
-
Cause: The grant failed when a user could not be added to the password file, because all available slots in it were used already.
- ORA-01997: GRANT failed: user 'string' is IDENTIFIED GLOBALLY
-
Cause: An attempt was made to grant administrative privileges to a user account, which was created as IDENTIFIED GLOBALLY. This is only allowed in an ASM; not in a database instance.
- ORA-01998: REVOKE failed: user SYS always has SYSOPER and SYSDBA
-
Cause: An attempt was made to revoke SYSOPER or SYSDBA administrative privileges from the SYS user which is not allowed.
- ORA-01999: password file cannot be updated in SHARED mode
-
Cause: An attempt was made to perform one of the following operations, but none of these operations are allowed while the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE is set to SHARED and password file is in READ ONLY mode. - Attempting to change password for an administrative privileged user either using ALTER USER DDL statement or SQL*Plus PASSWORD command, or OCIPasswordChange API. - Attempting to grant administrative privileges to a user. - Attempting to revoke administrative privileges from a user. - Attempting to drop an administrative privileged user. If the password file was created in 12.2 format, then the following additional operations are disallowed when REMOTE_LOGIN_PASSWORDFILE parameter is set to SHARED. - An ALTER USER DDL statement making changes to an administrative privileged user's account status, password profile assignment, identification type, password expiration timestamp. - An ALTER PROFILE or DROP PROFILE CASCADE DDL statement for a password profile, which is assigned to an administrative privileged user.
- ORA-02000: missing string keyword
-
Cause: The statement entered requires the missing keyword.
- ORA-02001: user SYS is not permitted to create indexes with freelist groups
-
Cause: user tried to create an index while running with sys authorization.
- ORA-02002: error while writing to audit trail
-
Cause: The auditing facility was unable to write to the audit trail. SQL statements that were being audited may also fail. This error occurred because of one of the following reasons: 1. Designated audit tablespace ran out of disk space. 2. Operating system mount point where the audit files were located did not have enough free space to generate new files. 3. Some other underlying error caused the audit write failure.
- ORA-02003: invalid USERENV parameter
-
Cause: An invalid parameter was specified for the USERENV function.
- ORA-02004: security violation
-
Cause: This error code was never returned to a user. It was used as a value for column, UNIFIED_AUDIT_TRAIL.RETURN_CODE, to signal that a security violation occurred.
- ORA-02005: implicit (-1) length not valid for this bind or define data type
-
Cause: A negative length for the define variable was passed to a define function.
- 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.
- ORA-02007: can't use ALLOCATE or DEALLOCATE options with REBUILD
-
Cause: Allocate or deallocate storage and rebuild index are not compatible.
- ORA-02008: non-zero scale specified for nonnumeric column
-
Cause: A scale factor was specified for a bind or define of a non-numeric variable.
- ORA-02009: the size specified for a file must not be zero
-
Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification.
- ORA-02010: missing host connect string
-
Cause: A quoted character string did not follow the keyword USING in the USING clause of a CREATE DATABASE LINK statement.
- ORA-02011: duplicate database link name
-
Cause: The database link name specified in a CREATE DATABASE LINK statement already existed.
- ORA-02012: missing USING keyword
-
Cause: The keyword USING did not follow the CONNECT TO clause in a CREATE DATABASE LINK statement.
- ORA-02013: missing CONNECT keyword
-
Cause: The keyword CONNECT did not follow the database link name in a CREATE DATABASE LINK statement.
- 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 which had not been merged because the view used syntax (for example, DISTINCT or GROUP BY) preventing the merge, or because of initialization file parameter settings.
- ORA-02015: cannot select FOR UPDATE from remote table
-
Cause: An attempt was made to select FOR UPDATE on a remote table (directly, or via a view) that had abstract data type columns, and the view or select list contained abstract data type columns or non-column items.
- 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.
- ORA-02017: integer value required
-
Cause: The specified value must be an integer.
- ORA-02018: database link of same name has an open connection
-
Cause: The user was 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.
- ORA-02019: connection description for remote database not found
-
Cause: The referenced database link did not exist.
- ORA-02020: too many database links in use
-
Cause: The current session has exceeded the INIT.ORA open_links maximum.
- 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 ...".
- 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.
- ORA-02023: START WITH or CONNECT BY predicate cannot be evaluated by remote data base
-
Cause: The statement contained a tree query on a remote database, and the tree query's START WITH or CONNECT BY predicate contained a term that could not be evaluated at the remote database. Such terms included calls to user functions, calls to USERENV, and references to ROWID.
- ORA-02024: database link not found
-
Cause: Database link to be dropped is not found in dictionary
- ORA-02025: all tables in the SQL statement must be at the remote database
-
Cause: The user's SQL statement references tables from multiple databases. The remote database is not Oracle V7 or above, and can perform updates only if it can reference all tables in the SQL statement.
- ORA-02026: missing LINK keyword
-
Cause: keyword missing
- ORA-02027: multi-row UPDATE of LONG column is not supported
-
Cause: A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row.
- 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.
- ORA-02029: missing FILE keyword
-
Cause: keyword missing
- ORA-02030: can only select from fixed tables/views
-
Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view.
- ORA-02031: no ROWID for fixed tables or for external-organized tables
-
Cause: An attempt is being made to access rowid from a fixed table or from a external-organized table.
- ORA-02032: clustered tables cannot be used before the cluster index is built
-
Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.
- ORA-02033: a cluster index for this cluster already exists
-
Cause: A cluster index already exists for the cluster.
- ORA-02034: speed bind not permitted
-
Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system.
- ORA-02035: illegal bundled operation combination
-
Cause: User requested that the UPI bundled execution call perform an an illegal combination of operations.
- ORA-02036: too many variables to describe with automatic cursor open
-
Cause: User requested that the UPI bundled execution call perform automatic cursor open and close on a describe operation. There were too many select-list items or bind variables to do this.
- ORA-02037: uninitialized speed bind storage
-
Cause: User attempted a UPI bundled execution call containing a standalone execute operation without first performing a UPI bundled execution call containing a bind operation.
- ORA-02038: define is not allowed for array type
-
Cause: User attempted to define a select list variable of type "array". Arrays may only serve as host bind variables.
- 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.
- ORA-02040: remote database string does not support two-phase commit
-
Cause: the database was potentially updated but does not support prepare to commit (as determined by its logon transaction traits). The transaction was rolled back.
- ORA-02041: client database did not begin a transaction
-
Cause: internal error
- ORA-02042: too many distributed transactions
-
Cause: the distributed transaction table was full because too many distributed transactions were active.
- ORA-02043: must end current transaction before executing string
-
Cause: a transaction is in progress and one of the following commands commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.
- 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.
- ORA-02045: too many local sessions participating in global transaction
-
Cause: too many sessions at this site for this transaction.
- ORA-02046: distributed transaction already begun
-
Cause: internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran.
- ORA-02047: cannot join the distributed transaction in progress
-
Cause: Either a transaction is in progress against a remote database that does not fully support two phase commit, and an update is attempted on another database, or updates are pending and and an attempt is made to update a different database that does not fully support two phase commit.
- ORA-02048: attempt to begin distributed transaction without logging on
-
Cause: client program must issue a distributed transaction login.
- ORA-02049: timeout: distributed transaction waiting for lock
-
Cause: "The number of seconds specified in the distributed_lock_timeout initialization parameter were exceeded while waiting for a lock or for a begin transaction hash collision to end."
- ORA-02050: transaction string rolled back, some remote DBs may be in-doubt
-
Cause: network or remote failure in 2PC.
- ORA-02051: another session or branch in same transaction failed or finalized
-
Cause: A session at the same site with the same global transaction ID failed. The failure could also be caused by an application error if an attempt was made to update the database while another tightly coupled transaction branch with the same global transaction ID was finalized or aborted.
- ORA-02052: remote transaction failure at string
-
Cause: error in remote transaction at given DBLINK
- ORA-02053: transaction string committed, some remote DBs may be in-doubt
-
Cause: network or remote failure in 2PC.
- ORA-02054: transaction string in-doubt
-
Cause: network or remote failure in 2PC.
- ORA-02055: distributed update operation failed; rollback required
-
Cause: a failure during distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent, the transaction must roll back to a savepoint or entirely
- ORA-02056: 2PC: string: bad two-phase command number string from string
-
Cause: two-phase commit protocol error.
- ORA-02057: 2PC: string: bad two-phase recovery state number string from string
-
Cause: internal error in two-phase recovery protocol
- ORA-02058: no prepared transaction found with ID string
-
Cause: no transaction with local_tran_id or global_tran_id found in the pending_trans$ table in prepared state.
- ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment
-
Cause: This is a special comment used to test the two phase commit.
- ORA-02060: select for update specified a join of distributed tables
-
Cause: tables in a join with the for update clause must reside at the same DB.
- ORA-02061: lock table specified list of distributed tables
-
Cause: tables in a lock table statement must reside at the same DB.
- ORA-02062: distributed recovery received DBID string, expected string
-
Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted.
- ORA-02063: preceding stringstring from stringstring
-
Cause: an Oracle error was received from a remote database link.
- ORA-02064: distributed operation not supported
-
Cause: One of the following unsupported operations was attempted: 1. array execute of a remote update with a subquery that references a dblink, or 2. an update of a long column with bind variable and an update of a second column with a subquery that both references a dblink and a bind variable, or 3. a commit is issued in a coordinated session from an RPC procedure call with OUT parameters or function call.
- ORA-02065: illegal option for ALTER SYSTEM
-
Cause: The option specified for ALTER SYSTEM is not supported
- ORA-02066: missing or invalid DISPATCHERS text
-
Cause: A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS
- ORA-02067: transaction or savepoint rollback required
-
Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.
- ORA-02068: following severe error from stringstring
-
Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text.
- ORA-02069: global_names parameter must be set to TRUE for this operation
-
Cause: A remote mapping of the statement is required but cannot be achieved because global_names should be set to TRUE for it to be achieved
- ORA-02070: database stringstring does not support string in this context
-
Cause: The remote database does not support the named capability in the context in which it is used.
- ORA-02071: error initializing capabilities for remote database string
-
Cause: Could not load a remote-specified capability table.
- ORA-02072: distributed database network protocol mismatch
-
Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.
- ORA-02073: sequence numbers not supported in remote updates
-
Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.
- ORA-02074: cannot string in a distributed transaction
-
Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction.
- ORA-02075: another instance changed state of transaction string
-
Cause: A commit force or rollback force was issued from a session in another instance.
- ORA-02076: sequence not co-located with updated table or long column
-
Cause: all referenced sequences must be co-located with the table with the long column.
- ORA-02077: selects of long columns must be from co-located tables
-
Cause: if a select returns long columns from multiple tables, all the tables must be co-located
- ORA-02078: invalid setting for ALTER SYSTEM FIXED_DATE
-
Cause: An invalid value was used.
- ORA-02079: cannot join a committing distributed transaction
-
Cause: Once a transaction branch is prepared, no more new transaction branches are allowed to start, nor is the prepared transaction branch allowed to be joined.
- 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 link command.
- ORA-02081: database link is not open
-
Cause: dblink given is not currently open.
- ORA-02082: a loopback 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.
- ORA-02083: database name has illegal character 'string'
-
Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.
- ORA-02084: database name is missing a component
-
Cause: supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.
- ORA-02085: database link string connects to string
-
Cause: a database link connected to a database with a different name. The connection is rejected.
- ORA-02086: database (link) name is too long
-
Cause: database/database link name can have at most 128 characters.
- ORA-02087: object locked by another process in same transaction
-
Cause: A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session.
- ORA-02088: distributed database option not installed
-
Cause: Remote and distributed updates and transactions are a separately priced option in ORACLE V7.
- 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.
- ORA-02090: network error: attempted callback+passthru
-
Cause: internal error.
- ORA-02091: transaction rolled back
-
Cause: Also see error 2092. If the transaction is aborted at a remote site then you will only see 2091; if aborted at host then you will see 2092 and 2091.
- ORA-02092: out of transaction table slots for distributed transaction
-
Cause: The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back.
- ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
-
Cause: Value of parameter specified is greater than allowed on this port.
- ORA-02094: replication option not installed
-
Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.
- ORA-02095: specified initialization parameter cannot be modified
-
Cause: The specified initialization parameter is not modifiable
- ORA-02096: specified initialization parameter is not modifiable with this option
-
Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.
- ORA-02097: parameter cannot be modified because specified value is invalid
-
Cause: Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter.
- ORA-02098: error parsing index-table reference (:I)
-
Cause: An incorrect index-table (:I) syntax was encountered.