Cause: During create database or alter tablespace, there was a failure in getting the date and time.

Cause: An error occurred during create database

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

Cause: An error occurred during CREATE CONTROLFILE

Cause: The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name.

Cause: During create or alter database, error(s) occurred when adding new log files.

Cause: No db_name INIT.ORA aprameter was specified.

Cause: A command was attempted that requires the database to be mounted.

Cause: CREATE DATABASE was unable to process the specified file.

Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database.

Cause: During ALTER DATABASE, an error occurred while dropping log files.

Cause: An error occurred during the ALTER DATABASE RENAME FILE command.

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

Cause: The operating system returned a time that was not between 1988 and 2121.

Cause: A log file name, or list of member names, did not correspond to an existing log.

Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file.

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.

Cause: Used to print member names

Cause: Only one log file was specified in the CREATE DATABASE statement.

Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.

Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database.

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

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.

Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.

Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.

Cause: An error occurred when renaming files as part of ALTER TABLESPACE.

Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.

Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.

Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad.

Cause: CREATE DATABASE was not able to close the specified file.

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.

Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.

Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance.

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.

Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.

Cause: Specified rollback segment already exists or given name starts with _SYSSMU.

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.

Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database.

Cause: Failed to acquire any rollback segment during startup in shared mode

Cause: Failed to either make a tablespace read-only or offline because it is not online. A tblespace must be online before it can become read-only or offline normal.

Cause: Failed to bring a tablespace online because it is not offline

Cause: Tried to bring system tablespace offline

Cause: Tried to allocate space in an offline tablespace

Cause: Tried to create a tablespace which already exists

Cause: Tried to drop system rollback segment

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.

Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read-only

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.

Cause: Tried to drop a tablespace that contains active rollback segment(s)

Cause: Tried to drop a non-empty tablespace

Cause: Tried to drop system tablespace

Cause: Doing recursive extent of rollback segment, trapped internally by the system

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.

Cause: The number of extents allocated is greater than the MAXEXTENTS specified.

Cause: Too many concurrent transactions

Cause: rollback records needed by a reader for consistent read are overwritten by other writers

Cause: Specified MINEXTENTS of less than 2 for rollback segment

Cause: Specified extent of less than minimum size for rollback segment

Cause: All the available transaction id's have been used

Cause: Specified MAXEXTENTS of less than 2 for rollback segment

Cause: like pattern is not formed correctly

Cause: Failed to remove all objects when dropping a tablespace

Cause: Failure occurred when trying to extend rollback segment

Cause: Did not use the keyword PUBLIC to identified public rollback segment

Cause: The rollback segment segment identified is not public

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

Cause: The list of files supplied to the command contained at least one duplicate.

Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread.

Cause: Trying to set space quota on a tablespace for PUBLIC.

Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables.

Cause: The number of extents allocated is smaller than the MINEXTENTS specified.

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.

Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.

Cause: Some process tries to make changes while the db is being shutdown

Cause: the limit on the number of concurrent transactions has been hit

Cause: failed to acquire necessary resource to do space management.

Cause: The thread associated with instance is not enabled.

Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database.

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.

Cause: A write error occurred during recovery

Cause: An operating system error occurred while attempting to create a control file backup.

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.

Cause: An operating system error occurred while attempting to open a control file for backup.

Cause: An operating system error occurred while attempting to get the block size of a control file for backup.

Cause: An operating system error occurred while attempting to get the file size of a control file for backup.

Cause: An operating system error occurred when attempting to identify the file to be used for control file backup.

Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE.

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.

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.

Cause: storage parameter FREELIST GROUPS is too large.

Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state.

Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly.

Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.

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

Cause: Some error occurred while freeing inactive rollback segment extents.

Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message

Cause: Tried to online or offline the system rollback segment

Cause: Could have been taken offline before by DBA or cleaned up by SMON.

Cause: the amount statically allocated is not enough based on max_rollback_segments parameter.

Cause: The INIT.ORA parameter was mis-specified.

Cause: The bucket size was invalid for this parameter.

Cause: The grouping size was invalid for this parameter.

Cause: The number range was invalid for this parameter.

Cause: The numbers were missing for this parameter.

Cause: A parameter was different on two instances.

Cause: The limit on the number of instances supported by the control file has been reached.

Cause: Could have been brought online before by DBA or left as a result of process crash.

Cause: A member of the current log for a thread cannot be dropped.

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.

Cause: A thread number in a command is greater than the number of threads supported by the control file.

Cause: An attempt was made to enable a thread that is already enabled.

Cause: The thread cannot be enabled because it only has two online log files associated with it.

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.

Cause: Some instance, possibly this one, has allocated the thread for its use. The thread can not be disabled while in use.

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.

Cause: The INIT.ORA parameter "thread" is not between 1 and the number of threads allowed by the control file.

Cause: The INIT.ORA parameter "thread" requests a thread that is not enabled. A thread must be enabled before it can be mounted.

Cause: The INIT.ORA parameter "thread" requests a thread that has been mounted by another instance. Only one instance may use a thread.

Cause: The INIT.ORA parameter "thread" is zero, its default value. There are no threads which have been publicly enabled, and not mounted.

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.

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.

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.

Cause: A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log.

Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance.

Cause: Too many transactions in this segment.

Cause: Could have been taken offline before by DBA or cleaned up by SMON.

Cause: An attempt was made to extend a rollback segment that was already at the MAXEXTENTS value.

Cause: Save undo for the offline tablespace at max extents

Cause: A temp segment tried to extend past max extents.

Cause: A table tried to extend past maxextents

Cause: An index tried to extend past maxextents

Cause: System doesn't have Real Application Clusters configured

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

Cause: (same as 1545)

Cause: The instance is trying to online an already online RS

Cause: The instance is trying to online a RS already in use by another instance

Cause: The recovery compatible parameter is set too low to allow this software version to mount in cluster database mode.

Cause: There is no mapping from instance to thread for this instance in the control file.

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.

Cause: Attempting to add a datafile to a tablespace that has been set to read-only or offline.

Cause: Attempting to begin or end a backup for a tablespace that has been set to read-only.

Cause: Attempting to set the system tablespace to read-only. The system tablespace must remain read write for database operation.

Cause: Attempting to make tablespace read-only that is already read-only.

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.

Cause: Attempting to make a tablespace read write that is not read-only. It may be either online or offline.

Cause: Tried to allocate space in a read-only tablespace

Cause: An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log can not be cleared or archived.

Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup.

Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace.

Cause: Failed to allocate an extent of the required number of blocks for saving undo entries for the indicated offline tablespace.

Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated.

Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated.

Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.

Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated.

Cause: A cluster tried to extend past maxextents

Cause: The specified value must be an integer.

Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.

Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.

Cause: Attempting to make tablespace permanent that is already permanent.

Cause: Attempting to make tablespace temporary that is already temporary.

Cause: Tried to convert a non-empty tablespace to a temporary tablespace

Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY.

Cause: Internal Error.

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.

Cause: Attempting to mount, recover, or open a standby database without the appropriate command option to designate a standby database.

Cause: There is no more room in the control file for adding tablespaces.

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.

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.

Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby.

Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database.

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.

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.

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.

Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent with those in other instances.

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.

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.

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.

Cause: An attempt was made to activate a standby database when the database was in the middle of being opened.

Cause: Failed to allocate an extent of the required number of blocks for a LOB segment in the tablespace indicated.

Cause: A LOB segment tried to extend past max extents.

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.

Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated.

Cause: A table tried to extend past maxextents

Cause: An index tried to extend past maxextents

Cause: The number of files for a given tablespace has reached its maximum value

Cause: Attempting to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute

Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated.

Cause: There was a syntax in the INIT.ORA parameter.

Cause: sort area size too small to fit two records in memory

Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.

Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.

Cause: A LOB segment tried to extend past maxextents

Cause: A LOB segment tried to extend past maxextents

Cause: Version 8.0.1 database may not have shutdown cleanly

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.

Cause: Attempting to mount a clone database without the appropriate command option to designate a clone database.

Cause: Attempting to online a rollback segment in a clone database.

Cause: Attempting to online a tablespace or begin another point in time import while a point in time import is already in progress

Cause: Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view.

Cause: The string literal is longer than 4000 characters.

Cause: An attempt was made to create a cluster index with the UNIQUE attribute.

Cause: An attempt was made to create a cluster index using the NOSORT option.

Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.

Cause: An outer join appears in an or clause.

Cause: A grant was being performed on a view or a view was being replaced and the grant option was not present for an underlying object.

Cause: The USERENV('COMMITSCN') function can only be used once in a transaction.

Cause: The specified number was invalid.

Cause: Columns with zero length were not allowed.

Cause: The specified number had an invalid range.

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.

Cause: A wrong value is specified for the parameter.

Cause: The indicated comment or hint begun with the /* token did not have the terminating */.

Cause: The indexed function uses SYSDATE or the user environment.

Cause: An invalid option is specified in the ALTER DUMP UNDO command.

Cause: The deleted table had - no key-preserved tables, - more than one key-preserved table, or - the key-preserved table was an unmerged view.

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.

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.

Cause: Expecting an extent or block number but something else was specified.

Cause: Expecting an object number but something else was specified.

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.

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.

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.

Cause: An attempt was made to rename the object with dotted object name.

Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.

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.

Cause: Expecting the value of LEVEL but something else was specified.

Cause: Column data types or virtual columns were specified in a SELECT statement used to create and load a table directly.

Cause: The same option for ALTER DUMP UNDO was specified twice.

Cause: Columns belonging to more than one underlying table were either inserted into or updated.

Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.

Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.

Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.

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.

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.

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.

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.

Cause: expression(+) relop (subquery) is not allowed.

Cause: The timezone information file was not properly read.

Cause: The timezone files on client and server do not match. Operation can potentially result in incorrect results based on local timezone file.

Cause: Illegal year entered

Cause: An invalid Julian date was entered.

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.

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.

Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace.

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.

Cause: The year is not supported for the current calendar.

Cause: Your calendar doesn't extend to the specified date.

Cause: Era input does not match a known era.

Cause: This is an internal error.

Cause: The character string you specified is not a valid interval.

Cause: The leading precision of the interval is too small to store the specified interval.

Cause: The intervals or datetimes are not mutually comparable.

Cause: The number of seconds specified was greater than 59.

Cause: The leading precision of the interval is too small to store the specified interval.

Cause: The time zone hour specified was not in the valid range.

Cause: The time zone minute specified was not in the valid range.

Cause: The specified year was not in range.

Cause: This is an internal error.

Cause: The specified field was not found in the datetime or interval.

Cause: The specified hh25 field was not in the valid range.

Cause: The specified fractional seconds were not in the valid range.

Cause: The region ID referenced an invalid region.

Cause: The specified region name was not found.

Cause: The region was changing state and the overlap flag was disabled.

Cause: An attempt was made to divide by zero.

Cause: The public synonym was the same as the Oracle-supplied schema name.

Cause: An NLS error was detected.

Cause: Internal error.

Cause: While trying to truncate or round dates, extra data was found in the date format picture

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: keyword missing

Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers.

Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views.

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.

Cause: There is not a user or role by that name.

Cause: User does not exist in the system.

Cause: Role by that name does not exist.

Cause: There is already a user or role with that name.

Cause: There is already a user or role with that name.

Cause: Cascade is required to remove this user from the system. The user own's object which will need to be dropped.

Cause: Cannot drop the user's objects; someone has them locked.

Cause: Either the role was not granted to the user, or the role did not exist.

Cause: Role cannot have a privilege with the grant option.

Cause: You can only revoke privileges you granted.

Cause: In order to grant a privilege, you must first have the privilege with the grant option.

Cause: "ALL" was specified but the user doesn't have any privileges with the grant option.

Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited.

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.

Cause: The operation requires the admin option on the role.

Cause: An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles.

Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself.

Cause: A user or role name was expected.

Cause: Users and roles do not have owners.

Cause: A valid role name was expected.

Cause: Cannot create a user without specifying a password or "IDENTIFIED EXTERNALLY" for ASM instance.

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.

Cause: Attempt was made to drop a user that is currently logged in.

Cause: keyword missing

Cause: A user cannot be specified to have and not have a password.

Cause: The identified clause has been given twice.

Cause: The identified externaly clause has been given twice.

Cause: The default roles clause has been given twice.

Cause: The default tablespace clause has been given twice.

Cause: The temporary tablespace clause has been given twice.

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.

Cause: The role keyword is required here.

Cause: User does not have privileges to allocate an extent in the specified tablespace.

Cause: The role you tried to revoke was not granted to the user.

Cause: A system privilege you tried to revoke was not granted to the user.

Cause: The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality

Cause: Default roles cannot be specified for create 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.

Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is TRUE.

Cause: The default collation clause was specified twice.

Cause: An invalid CREATE CONTROLFILE option is present.

Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once

Cause: Missing a RESETLOGS or a NORESETLOGS

Cause: Missing a database name

Cause: Keyword "CHANGE" found but change number not specified.

Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command

Cause: Keyword "THREAD" found but thread number not specified.

Cause: Keyword "SEQUENCE" found but sequence number not specified.

Cause: An attempt was made to enable a role without giving the proper password.

Cause: An OS error occurred while loading a users OS ROLES.

Cause: During this revoke some foreign key contraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified.

Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables.

Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT.

Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions.

Cause: Maximum users in the database license limit exceeded.

Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced.

Cause: A client's os username is too long for the os logon to succeed.

Cause: Remote os login attempted when not allowed.

Cause: The os role does not exist, is not granted to you, or you did not provide the correct password.

Cause: The password file either did not exist or was inaccessible.

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.

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.

Cause: An attempt was made to revoke SYSOPER or SYSDBA administrative privileges from the SYS user which is not allowed.

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.

Cause: user tried to create an index while running with sys authorization.

Cause: This error code is never returned to a user. It is used as a value for column, audit_trail.returncode, to signal that a security violation occurred.

Cause: Allocate or deallocate storage and rebuild index are not compatible.

Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification.

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.

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.

Cause: The current session has exceeded the INIT.ORA open_links maximum.

Cause: An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname ...".

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.

Cause: Database link to be dropped is not found in dictionary

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.

Cause: keyword missing

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.

Cause: The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.

Cause: keyword missing

Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view.

Cause: An attempt is being made to access rowid from a fixed table or from a external-organized table.

Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.

Cause: A cluster index already exists for the cluster.

Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system.

Cause: User requested that the UPI bundled execution call perform an an illegal combination of operations.

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.

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.

Cause: User attempted to define a select list variable of type "array". Arrays may only serve as host bind variables.

Cause: User attempted to bind an array host variable by value. Arrays may only be bound by reference.

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.

Cause: internal error

Cause: the distributed transaction table was full because too many distributed transactions were active.

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.

Cause: a remote transaction manager tried to log in while a distributed transaction is in progress.

Cause: too many sessions at this site for this transaction.

Cause: internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran.

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.

Cause: client program must issue a distributed transaction login.

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

Cause: network or remote failure in 2PC.

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.

Cause: error in remote transaction at given DBLINK

Cause: network or remote failure in 2PC.

Cause: network or remote failure in 2PC.

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

Cause: two-phase commit protocol error.

Cause: internal error in two-phase recovery protocol

Cause: no transaction with local_tran_id or global_tran_id found in the pending_trans$ table in prepared state.

Cause: This is a special comment used to test the two phase commit.

Cause: tables in a join with the for update clause must reside at the same DB.

Cause: tables in a lock table statement must reside at the same DB.

Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted.

Cause: an Oracle error was received from a remote database link.

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.

Cause: The option specified for ALTER SYSTEM is not supported

Cause: A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS

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.

Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text.

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

Cause: The remote database does not support the named capability in the context in which it is used.

Cause: Could not load a remote-specified capability table.

Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.

Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.

Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction.

Cause: A commit force or rollback force was issued from a session in another instance.

Cause: all referenced sequences must be co-located with the table with the long column.

Cause: if a select returns long columns from multiple tables, all the tables must be co-located

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.

Cause: a transaction is active or a cursor is open on the database link given in the alter session close database link link command.

Cause: dblink given is not currently open.

Cause: An attempt was made to create a database link with the same name as the current database.

Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.

Cause: supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.

Cause: a database link connected to a database with a different name. The connection is rejected.

Cause: database/database link name can have at most 128 characters.

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.

Cause: Remote and distributed updates and transactions are a separately priced option in ORACLE V7.

Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator.

Cause: internal error.

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.

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.

Cause: Value of parameter specified is greater than allowed on this port.

Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.

Cause: The specified initialization parameter is not modifiable

Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.

Cause: Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter.

Cause: An incorrect index-table (:I) syntax was encountered.