Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000.

Cause: The identifier name started with an ASCII character other than a letter or a number. After the first character of the identifier name, ASCII characters are allowed including "$", "#" and "_". Identifiers enclosed in double quotation marks may contain any character other than a double quotation. Alternate quotation marks (q'#...#') cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual.

Cause: one of your input strings was too long

Cause: An index name of the form [ identifier . ] identifier is expected but not present. If OIDINDEX clause, index name must be identifier

Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.

Cause: A column name in the order-by list matches more than one select list columns.

Cause: The group-by or order-by column list contain more than 1000 expressions.

Cause: The table name referred in the select list is not specified in the from list.

Cause: The statement is trying to alias the * expression in the select list which is not legal.

Cause: An identifier with more than 128 bytes was specified, or a password identifier longer than 30 bytes was specified.

Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or CONNECT_BY_ISCYCLE was specified at an illegal location.

Cause: AUDIT or NOAUDIT statement specifies an option more than once

Cause: A synonym did not translate to a legal target object. This could happen for one of the following reasons: 1. The target schema does not exist. 2. The target object does not exist. 3. The synonym specifies an incorrect database link. 4. The synonym is not versioned but specifies a versioned target object.

Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.

Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.

Cause: Object privileges or non-MAC system privileges were granted to the procedure.

Cause: This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.

Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You are using an Oracle client application linked with version 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0 (or lower) Oracle Server. 3) You are connected to a version 7.1 (or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or lower) Oracle Server. 4) You are connected to a version 9.0.2(or higher) Oracle Server and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous transaction.

Cause: Cursor in an invalid state.

Cause: The user side memory allocator returned error.

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

Cause: The cursor number is not a valid open cursor.

Cause: An integer parameter to a upi function is out of range.

Cause: More than one long buffer in the bind list.

Cause: An attempt was made to use a bind variable in a SQL data definition operation.

Cause: Received send long message but don't have the cursor context.

Cause: Received a request to send the long again when there is no long

Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.

Cause: An attempt was made to perform a database operation without the necessary privileges.

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

Cause: An attempt was made to log on while Oracle is being started up or shutdown.

Cause: Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it. - The operating-system variable pointing to the instance is improperly defined.

Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.

Cause: Unable to find bind context on user side

Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor.

Cause: Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version.

Cause: Attempting to explain plan on other people's view without the necessary privileges on the underlying objects of the view.

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

Cause: Pointer to hstdef extension in hstdef is null.

Cause: An attempt was made to detach a seesio n which had open cursors.

Cause: The application code corrupted some of the usr memory used by oracle

Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements)

Cause: A connect was attempted to a userid which does not have create session privilege.

Cause: The procedure user specified in deferred RPC doesn't exist.

Cause: A newer version of server is talking with this version requesting an operation not supported in this version.

Cause: The deferred rpc data in sys.def$_call is corrupted.

Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.

Cause: Bind or Define used for objects with an invalid mode

Cause: Attempt to delete non existant hstdef extension.

Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.

Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.

Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.

Cause: Exceeded the maximum buffer size for current plaform

Cause: The total number of rows requested from the server exceeded the maximum specified in MINSWORDMAXVAL.

Cause: A value other than RDBMS was specified for the INSTANCE_TYPE parameter in Oracle Database Express Edition (XE).

Cause: Using pre 7.0.10.1 version of oracle for server

Cause: Obvious

Cause: Obvious

Cause: An illegal internal operation was attempted.

Cause: Obvious

Cause: Attempt to login while logged in.

Cause: Obvious

Cause: Failure during initialization of ORACLE background processes.

Cause: Failure during processing of INIT.ORA parameters during system startup.

Cause: There was an error when the database or control file was created.

Cause: Failure during system shutdown.

Cause: Obvious

Cause: "row_locking = always" is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.

Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples.

Cause: The failing OCI call contains an argument with an invalid value.

Cause: Errors were encountered when the named procedure was executed as a deferred remoted procedure call.

Cause: An attempt was made to roll back to a savepoint that was never established in this session, or was invalid.

Cause: The SHUTDOWN command was used to shut down a running Oracle instance but the shutdown operation was not complete.

Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, or CLOSE IMMEDIATE was used to shut down a pluggable database, so your operations have been terminated.

Cause: The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE.

Cause: Unable to destroy the old SGA.

Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.

Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.

Cause: During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point.

Cause: A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed.

Cause: Obvious

Cause: Obvious

Cause: A database is already mounted in this instance.

Cause: Some other instance has the database of same name currently mounted and you are trying to create it.

Cause: Some other instance has the database mounted exclusive or shared.

Cause: The database name in the control file does not match your database name.

Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.

Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.

Cause: Obvious

Cause: An attempt to perform media recovery was made but the database is not mounted.

Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.

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

Cause: Reporting file name for details of another error. The reported name can be of the old file if a data file move operation is in progress.

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

Cause: An attempt to continue media recovery is being made but media recovery was not started.

Cause: An attempt was made to online or open a database with a file that is in need of media recovery.

Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.

Cause: Device on which the file resides is probably offline

Cause: Usually the file is not accessible.

Cause: An attempt was made to add a database file with a block size that was greater than the maximum block size allowed or less than the minimum block size allowed or an invalid value (that is, not power of 2) in the allowed range.

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

Cause: Usually due to not having enough space on the device.

Cause: Attempting to drop a datafile when it is online

Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.

Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason.

Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled.

Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file.

Cause: An attempt to disable media recovery found that an online backup is still in progress.

Cause: Obvious

Cause: Obvious

Cause: An attempt to start an online backup found that one of the files is offline.

Cause: The user's default or temporary tablespace was dropped.

Cause: Attempted to access a data file that is offline

Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed

Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.

Cause: The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open.

Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.

Cause: All the files were found to be offline or readonly when attempting to end an online backup.

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

Cause: None of the files were found to be in online backup when attempting to end an online backup.

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

Cause: Specified file size is larger than maximum allowable size value.

Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode.

Cause: When starting an online backup it was noticed that an online backup was already started for one of the data files.

Cause: A file belonging to the SYSTEM tablespace has been marked offline by the DBA. The database cannot be started until all SYSTEM tablespace files are online and openable.

Cause: An operating system or device error occurred when retrieving the file's size. The device on which the file resides may have been offline.

Cause: An attempt to shutdown normally found that an online backup is still in progress.

Cause: An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. It will be necessary to write the file header to end the backup, but that would not be allowed if this command succeeded.

Cause: Error 1172 occurred.

Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.

Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs

Cause: Some operation is in progress that expects the opened/mounted state of this instance to remain the same.

Cause: The requested operation needs the instance to be in a particular state but the state is being changed.

Cause: Either media recovery, instance recovery, or flashback was in progress. The recovery or flashback in progress may need the files to which this operation is being applied.

Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified.

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

Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified.

Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.

Cause: The database name provided in the DATABASE clause did not match the database name found in the file header.

Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file.

Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.

Cause: MAXLOGFILES specified on the command line too large.

Cause: MAXDATAFILES specified on the command line too large.

Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.

Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same control file appears more than once in the control_files parameter in the init.ora file. If this happens, check for additional error messages.

Cause: The file is located on a device with a different physical block size than the other members in the group

Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.

Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE.

Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block.

Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.

Cause: Either the database has been recovered to a point in time in the future of the control file or a datafile from the system tablespace was omitted from the create control file command previously issued.

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

Cause: The data dictionary is found to have more files than that which can be supported by this instance.

Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more data files than that supported by the control file.

Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.

Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROLFILE command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database.

Cause: During datafile recovery, a file was listed which was not part for the database.

Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE.

Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS.

Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered.

Cause: Some other instance has the database mounted exclusive.

Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use.

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

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

Cause: The data file did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified.

Cause: The block size specified in the BLOCKSIZE clause of the CREATE CONTROLFILE statement does not equate to the block size recorded in the log file header.

Cause: In a CREATE CONTROLFILE command either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.

Cause: Attempting to use a data file when the log reset information in the file does not match the control file. Either the data file or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS.

Cause: When attempting to do a normal tablespace offline it was discovered that one of the files in the tablespace was already offline.

Cause: You must specify at least two logfiles from at least one thread at the create contolfile command line.

Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.

Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.

Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended.

Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.

Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs.

Cause: File sizes must be given for all logfiles if doing a CREATE CONTROLFILE with the RESETLOGS option.

Cause: Attempting to end an online backup for a file that is not in online backup.

Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy.

Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.

Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.

Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped.

Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.

Cause: The file type in the header is not correct for a data file. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted.

Cause: The database ID in the file header does not match the database id in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected.

Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.

Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.

Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.

Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.

Cause: MAXLOGMEMBERS specified on the command line too large.

Cause: MAXINSTANCES specified on the command line too large.

Cause: MAXLOGHISTORY specified on the command line too large.

Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database.

Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).

Cause: A member of a multiple-member logfile group specified in a CREATE CONTROLFILE is not part of the same group as previous members.

Cause: A member of a multiple-member logfile group is from a different point in time. One of the members specified may be an older (backup) copy of the log.

Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database or pluggable database has been opened.

Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.

Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.

Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.

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

Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.

Cause: The log is for a thread greater than the MAXINSTANCES argument.

Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log.

Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistancy. All log files listed in the command must be the current versions of the online logs.

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

Cause: The data file in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs.

Cause: An attempt to make a tablespace read only found that one of its files is offline.

Cause: An attempt to make a tablespace read write found that one of its files is offline.

Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode.

Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read only files do not normally need to be recovered, but recovery with a backup control file must recover all online files.

Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.

Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.

Cause: The indicated error occurred while doing initialization processing of file headers.

Cause: An operating system error occurred during the resize.

Cause: An operating system error occurred during the resize.

Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this can not be allowed.

Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.

Cause: The external cache may have been restarted.

Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.

Cause: A system tablespace file was detected as inaccessible due to media failure.

Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files.

Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.

Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.

Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.

Cause: Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.

Cause: Attempting to archive an online redo log or enable archiving for a clone database.

Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error.

Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.

Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read-only, then the file header cannot be updated when the backup is complete.

Cause: The specified file is being backed up by Recovery Manager.

Cause: The specified file is being backed up by Recovery Manager.

Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress.

Cause: The file is in use by another database instance.

Cause: The size of the raw partion cannot be determined

Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database.

Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.

Cause: END BACKUP completed successfully for all files that were in online backup mode. However one or more modifiable files were found not to be in online backup mode. Backup of those files (if it was done) can be invalid and, if restored, can result in an inconsistent database.

Cause: The value for the specified parameter contained a destination string that could not be translated.

Cause: Unable to get information about an Oracle managed files destination directory.

Cause: The name given for an Oracle managed files destination does not correspond to a directory.

Cause: Unable to create an Oracle managed file name.

Cause: An error prevented the file from being deleted.

Cause: Unable to create a unique file name for an Oracle managed file. Oracle tried several names but each file name was already in use in the default destination directory for the file type.

Cause: Could not get date/time when trying to create unique file name.

Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace.

Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long.

Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true.

Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.

Cause: The REUSE parameter was specified in a command without a file name.

Cause: Automated standby file management was disabled, so an added file

Cause: The recovery failed to add the specified data file either because the recovery tried to create the specified data file but automated standby file management was disabled, or the recovery tried to look for the specified data file but the data file did not exist. In the former case, the recovery added a control file entry as 'UNNAMEDnnnnn'.

Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.

Cause: An attempt was made to add to the database a datafile, log file, control file, snapshot control file, backup control file, datafile copy, control file copy or backuppiece with an Oracle Managed Files file name.

Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' command specified a file name which is already in use.

Cause: An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'.

Cause: db_files has been set too high to be supported by the system.

Cause: An internal error occurred inside LogMiner.

Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.

Cause: startTime may be greater than endTime. startTime or endTime may be greater than year 2110. startTime may be less than year 1988.

Cause: The specified options parameter is invalid for the procedure.

Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds 256 characters.

Cause: The file or directory may not exist or is inaccessible.

Cause: Options were supplied which require a starting time or starting SCN

Cause: The logfile is produced by a different incarnation of the database.

Cause: A command that is not supported by Logminer was present in a logfile. Commands that change the character set of the database are not supported by Logminer. "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.

Cause: The logfile specified has already been added to the list of logfiles.

Cause: The user attempted to remove a logfile that is not present in the list.

Cause: Not all log files corresponding to the time or SCN range specified had been added to the LogMiner session.

Cause: A log file needed by LogMiner could not be found in v$archived_log.

Cause: Options were specified which required the database to be mounted

Cause: The dictionary file is corrupt.

Cause: The dictionary file is produced by a database that is different from that produced the logfiles.

Cause: The character set of the database that produced the dictionary file is different from the charatcter set of the database that produced the logfiles.

Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles.

Cause: More than one dictionary source was specified or DDL_DICT_TRACKING was specified with DICT_FROM_ONLINE_CATALOG.

Cause: The dictionary file was extracted from a different incarnation of the database.

Cause: Options were specified which required the database to be writable.

Cause: Error writing to file during flat file build

Cause: Missing dictionary build options or incorrectly specified options

Cause: A process subordinate to this Logminer process has exited with this error status.

Cause: A process subordinate to this Logminer process has exited with an error condition.

Cause: The database character set of the mining database was not a superset of the source database character set.

Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.

Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile()

Cause: The dictionary directory was not valid.

Cause: The specified Logminer session ID or session handle is invalid.

Cause: The return type requested by the user is not supported by lcr_mine"

Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table/view.

Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.

Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column.

Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.

Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.

Cause: A Logminer attach session was issued while already attached to a Logminer session.

Cause: A command or procedure was issued which requires an attached Logminer session.

Cause: The national character set of the mining database was not a superset of the source database national character set.

Cause: A session attribute was supplied which is invalid.

Cause: A Logminer dictionary attribute was supplied which is invalid.

Cause: The requested session start SCN is less than the SCN of any available Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the requested start SCN.

Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().

Cause: A Logminer routine was called from the wrong state.

Cause: The logfile is produced by a different database than other logfiles already added to the list.

Cause: Database does not have archivelog mode enabled.

Cause: Compatibility mode set to some value less than 9.0

Cause: Other users are performing DDL operations.

Cause: Another processes is simultaneously attempting to run build();

Cause: The table may be missing, or locked by another user.

Cause: Unexpected error condition

Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.

Cause: Unexpected internal error condition

Cause: The dictionary file or directory does not exist or is inaccessible.

Cause: The logfile has a different compatibility version then the rest of the logfile in the session"

Cause: Can not do this when other process is attached to LogMiner session.

Cause: Unexpected result while accessing system catalog metadata.

Cause: Could not load NLS package.

Cause: The LogMiner session requires more system resources than is currently available.

Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.

Cause: Log file is missing a range of scn values.

Cause: A coordinator process is already attached to the specified logminer context.

Cause: A LogMiner client attempted to perform a privileged operation.

Cause: Oracle LogMiner detected a new branch with reset log SCN information prior to redo already mined.

Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.

Cause: Invocation failed to specify a valid tablespace

Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.

Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.

Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.

Cause: An attempt was made to perform an operation that required that supplemental log data be enabled.

Cause: The tables used by logminer are in the process of being moved to another tablespace.

Cause: Logminer sessions are currently active.

Cause: LogMiner ran out of space in the transaction queue.

Cause: An attempt was made to mine a LogMiner dictionary from redo logs. The version of the Oracle database that created the logs was higher than the Oracle database version that attempted to mine the logs.

Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.

Cause: The specified input value for the parameter was not a valid number.

Cause: NULL was specified for input value of parameter.

Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. LogMiner reader is now waiting for logs from the new branch.

Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. The builder process is now waiting for logs from the new branch to be registered before continuing.

Cause: LogMiner failed to find all the expected log files required to complete the terminal apply, requested using the FINISH APPLY clause. During terminal apply, LogMiner does not wait for logs to be registered. It expects all logs between the starting point and the last log on any redo branch that it will or could mine through, to be present at the mining site.

Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.

Cause: One or more log files containing the LogMiner dictionary was not found.

Cause: The number of processes requested by the caller can not be allocated

Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.

Cause: LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1.

Cause: A corrupt logfile has been recovered by RFS

Cause: The redo compatibility setting of the log file was unsupported by LogMiner.

Cause: An invalid value was specified in the BLOCKSIZE clause.

Cause: One of the following occurred: (1) An attempt was made to create a file. (2) A file was moved to disks with different sector size.

Cause: One of the following occurred: (1) An attempt was made to switch to specified block size logs for all threads. (2) An attemp was made to open a thread.

Cause: The database was migrated to use a specified log block size. Dropping all the logs specified would leave fewer than the required two log files with the specified block size per enabled thread.

Cause: Log file was created on bigger sector disks, and moved to smaller sector disks.

Cause: Log file was copied from smaller sector disks to larger sector native-mode disks.

Cause: An attempt was made to automatically convert the control file created with maximum file name size value of 512 to 256. This could result in truncation of file names leading to loss of uniqueness among file names.

Cause: An attempt was made to insert NULL into previously listed objects.

Cause: The value inserted was too large for the given column.

Cause: No data was found from the objects.

Cause: The fetched column values were truncated.

Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail.

Cause: Tried to fetch a column of size more than 64K and couldn't store the length of the column in the given indicator of size 2 bytes.

Cause: The length for type 97 is 0

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

Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.

Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.

Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed

Cause: The number specified in exact fetch is less than the rows returned.

Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'.

Cause: Given escape character for LIKE is not a character string of length 1.

Cause: Evaluation of an value expression causes an overflow/underflow.

Cause: No overflow segment defined.

Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.

Cause: the column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint.

Cause: self-evident

Cause: A non-DDL insert/delete/update or select for update operation was attempted

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

Cause: Query parsed after tbl (or index) change, and executed w/old snapshot

Cause: Attempting to specify "PRIOR something" where something is not a column name.

Cause: Constants of different types are specified in an in-list.

Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes.

Cause: A bind variable of type 97 does not contain null at the last position

Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer.

Cause: The user is attempting to either convert a number to a string via TO_CHAR or a string to a number via TO_NUMBER and has supplied an invalid number format model parameter.

Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set.

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

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

Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length (given in the bind call). The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.

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

Cause: An impossible request for decimal to oracle number conversion was made

Cause: An impossible request for decimal to oracle number conversion was made

Cause: String concatenation result is more than the maximum size.

Cause: Incorrect syntax specified

Cause: The CASCADE option is only valid for tables or clusters.

Cause: The LIST option is only valid for tables or clusters.

Cause: The specified SAMPLE size is out of range

Cause: The specified histogram SIZE value was out of range.

Cause: The specified table either does not exist or user does not have the proper privleges.

Cause: The specified table does not have the proper field definitions.

Cause: The FOR COLUMNS column-list clause may not be used with ANALYZE CLUSTER.