-
ORA-00911: invalid character
-
Cause: identifiers may not start with any ASCII character other than letters and numbers. $#_ are also allowed after the first character. Identifiers enclosed by doublequotes may contain any character other than a doublequote. Alternative quotes (q'#...#') cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual.
-
Action: None
-
ORA-00980: synonym translation is no longer valid
-
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.
-
Action: Change the synonym definition so that the synonym points at a legal target object.
-
ORA-01002: fetch out of sequence
-
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.
-
Action: 1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then attempt to fetch again.
-
ORA-01010: invalid OCI operation
-
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.
-
Action: For the above causes: 1) Do not use the invalid OCI operation. 2) If you do not wish to use encrypted connect passwords in your distributed database, set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If you do not wish to use encrypted database links in your distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, you must upgrade all Oracle Servers to version 7.1 (or higher). 4) Do not attempt distributed autonomous transaction on version 9.0.1(or lower) Oracle Server.
-
ORA-01022: database operation not supported in this configuration
-
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers.
-
Action: You may need to upgrade one or more of your ORACLE servers or re-link your user side application with new libraries. Report the problem to Worldwide Customer Support.
-
ORA-01031: insufficient privileges
-
Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login.
-
Action: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label.
-
ORA-01034: ORACLE not available
-
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.
-
Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.
-
ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
-
Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.
-
Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
-
ORA-01038: cannot write database file version string with ORACLE version string
-
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.
-
Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation.
-
ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
-
Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.
-
Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one.
-
ORA-01083: value of parameter "string" is inconsistent with that of other instances
-
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.
-
Action: Change the value of the parameter in INIT.ORA file to match that of other cluster database instances.
-
ORA-01092: ORACLE instance terminated. Disconnection forced
-
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.
-
Action: Examine the alert log for more details. When the instance has been restarted, retry action.
-
ORA-01096: program version (string) incompatible with instance (string)
-
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.
-
Action: Either relink the program with the same version as the database or restart the database using the old version of code.
-
ORA-01108: file string is in backup or media recovery
-
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.
-
Action: Complete or cancel the media recovery session or backup.
-
ORA-01111: name for data file string is unknown - rename to correct file
-
Cause: The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.
-
Action: Rename the MISSING file to the name of the real file.
-
ORA-01114: IO error writing block to file string (block # string)
-
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.
-
Action: Restore access to the device or remove unnecessary files to free up space.
-
ORA-01124: cannot recover data file string - file is in use or recovery
-
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.
-
Action: Do not do media recovery.
-
ORA-01137: data file string is still in the middle of going offline
-
Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.
-
Action: Wait a bit and try to online the file again.
-
ORA-01138: database must either be open in this instance or not at all
-
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.
-
Action: Execute the operation in an open instance, open the datbase in this instance, or close the database in the other instances.
-
ORA-01145: offline immediate disallowed unless media recovery enabled
-
Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode.
-
Action: Take tablespace offline normally or shutdown abort. Reconsider your backup strategy. You could do this if you were archiving your logs.
-
ORA-01150: cannot prevent writes - file string has online backup set
-
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.
-
Action: End the backup of the offending tablespace and retry this command.
-
ORA-01152: file string was not restored from a sufficiently old backup
-
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.
-
Action: Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery.
-
ORA-01153: an incompatible media recovery is active
-
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
-
Action: Complete or cancel the other media recovery session or RMAN backup
-
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
-
Cause: Some operation is in progress that expects the opened/mounted state of this instance to remain the same.
-
Action: Wait for the operation to complete then retry. If attempting to do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown of a standby database that is operating in NO DATA LOSS mode, you must shutdown the primary database first.
-
ORA-01155: the database is being opened, closed, mounted or dismounted
-
Cause: The requested operation needs the instance to be in a particular state but the state is being changed.
-
Action: Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work.
-
ORA-01157: cannot identify/lock data file string - see DBWR trace file
-
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.
-
Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.
-
ORA-01159: file is not from same database as previous files - wrong database id
-
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.
-
Action: Please double check the list of files provided to the CREATE
-
ORA-01161: database name string in file header does not match given name of string
-
Cause: The database name given at the command line does not match the database name found in the file header.
-
Action: Chance are good that the database name specified at the command line is incorrect. Resolve the descepency, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option.
-
ORA-01162: block size string in file header does not match configured block sizes
-
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.
-
Action: Configure the appropriate cache for this block size using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.
-
ORA-01167: two files are the same file/group number or the same file
-
Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same 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.
-
Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the control_files parameter in the init.ora file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list.
-
ORA-01171: datafile string going offline due to error advancing checkpoint
-
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.
-
Action: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online.
-
ORA-01172: recovery of thread string stuck at block string of file string
-
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
-
Action: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem then restore the file from a backup and recover it.
-
ORA-01173: data dictionary indicates missing data file from system tablespace
-
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.
-
Action: For the former problem you need to recover the database from a more recent control file. For the latter problem, simply recreate the control file checking to be sure that you include all the datafiles in the system tablespace.
-
ORA-01174: DB_FILES is string buts needs to be string to be compatible
-
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.
-
Action: Change the value of the DB_FILES parameter to be compatible
-
ORA-01177: data file does not match dictionary - probably old incarnation
-
Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
-
Action: Do a CREATE CONTROLFILE with the correct file or none at all.
-
ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate
-
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.
-
Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.
-
ORA-01181: file string created before last known RESETLOGS, cannot recreate
-
Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS.
-
Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.
-
ORA-01186: file string failed verification tests
-
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.
-
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
-
ORA-01187: cannot read from file string because it failed verification tests
-
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.
-
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
-
ORA-01189: file is from a different RESETLOGS than previous files
-
Cause: In a CREATE CONTROLFILE command either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.
-
Action: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command.
-
ORA-01190: control file or data file string is from 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.
-
Action: Restore file from a more recent backup.
-
ORA-01193: file string is not the same file seen at start of recovery
-
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.
-
Action: Ensure the correct file is available, then retry recovery.
-
ORA-01194: file string needs more recovery to be consistent
-
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.
-
Action: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery.
-
ORA-01195: online backup of file string needs more recovery to be consistent
-
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.
-
Action: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery.
-
ORA-01196: file string is inconsistent due to a failed media recovery session
-
Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.
-
Action: Either apply more logs until the file is consistent or restore the backup again and repeat recovery.
-
ORA-01197: thread string only contains one log
-
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.
-
Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE.
-
ORA-01200: actual file size of string is smaller than correct size of string blocks
-
Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy.
-
Action: Restore a good copy of the data file and do recovery as needed.
-
ORA-01205: not a data file - type number in header is string
-
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.
-
Action: Restore a copy of the correct data file and do recovery as needed.
-
ORA-01206: file is not part of this database - wrong database id
-
Cause: The database ID in the file header does not match the database id in the control file. The file may be from a different database, or it may not be a 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.
-
Action: Restore a copy of the correct data file and do recovery as needed.
-
ORA-01207: file is more recent than control file - old control file
-
Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note 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.
-
Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.
-
ORA-01208: data file is an old version - not accessing current version
-
Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just 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.
-
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
-
ORA-01209: data file is from before the last RESETLOGS
-
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.
-
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
-
ORA-01210: data file header is media corrupt
-
Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the 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.
-
Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery.
-
ORA-01211: Oracle7 data file is not from migration to Oracle8
-
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.
-
Action: Have operating system make correct data file available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run.
-
ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE
-
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).
-
Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be recreated after the database is open.
-
ORA-01218: logfile member is not from the same point-in-time
-
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.
-
Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command.
-
ORA-01220: file based sort illegal before database is open
-
Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
-
Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory.
-
ORA-01221: data file string is not the same file to a background process
-
Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The 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.
-
Action: Look in the DBWR trace file for the error it recieved when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process.
-
ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
-
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.
-
Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
-
ORA-01223: RESETLOGS must be specified to set a new database name
-
Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
-
Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.
-
ORA-01226: file header of log member is inconsistent with other members
-
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.
-
Action: Find the correct log member or omit this member from the command.
-
ORA-01227: log string is inconsistent with other logs
-
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.
-
Action: Find the correct online logs or use the RESETLOGS option.
-
ORA-01228: SET DATABASE option required to install seed database
-
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
-
Action: Resubmit command with the SET DATABASE and RESETLOGS options.
-
ORA-01229: data file string is inconsistent with logs
-
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.
-
Action: Find the correct online logs or use the RESETLOGS option.
-
ORA-01232: cannot start online backup - file string is being made read-only
-
Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode.
-
Action: Wait for the transition to complete and then retry the command, if this is an ALTER DATABASE BEGIN BACKUP command, or take the backup without any begin or end commands, if this is an ALTER TABLESPACE BEGIN BACKUP command.
-
ORA-01233: file string is read only - cannot recover using backup control file
-
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.
-
Action: If the file really is read only, take it offline before the recovery, and bring the read only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one.
-
ORA-01234: cannot end backup of file string - file is in use or recovery
-
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.
-
Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation.
-
ORA-01235: END BACKUP failed for string file(s) and succeeded for string
-
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.
-
Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.
-
ORA-01239: database must be in ARCHIVELOG mode to use external cache
-
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.
-
Action: Change database to be in ARCHIVELOG mode or do not use an external cache.
-
ORA-01240: too many data files to add in one command
-
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.
-
Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands.
-
ORA-01241: an external cache has died
-
Cause: The external cache may have been restarted.
-
Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all data files through consistent external caches.
-
ORA-01244: unnamed datafile(s) added to control file by media recovery
-
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.
-
Action: Rename the files to valid file names and resume recovery. If necessary the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option.
-
ORA-01245: offline file string will be lost if RESETLOGS is done
-
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.
-
Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.
-
ORA-01246: recovering files through TSPITR of tablespace string
-
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.
-
Action: Restore more recent backups and recover them.
-
ORA-01247: database recovery through TSPITR of tablespace string
-
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.
-
Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery.
-
ORA-01248: file string was created in the future of incomplete recovery
-
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.
-
Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE.
-
ORA-01249: archiving not allowed in a clone database
-
Cause: Attempting to archive an online redo log or enable archiving for a clone database.
-
Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed then recreate database as not a clone.
-
ORA-01251: Unknown File Header Version read for file number string
-
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.
-
Action: Have the operating system make the correct file available to the database, or recover the file.
-
ORA-01252: cannot prevent writes - file string in recovery manager backup
-
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.
-
Action: Wait for the Recovery Manager backup to complete and retry this command.
-
ORA-01258: unable to delete temporary file string
-
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.
-
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
-
ORA-01259: unable to delete datafile string
-
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.
-
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
-
ORA-01260: warning: END BACKUP succeeded but some files found not to be in backup mode
-
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.
-
Action: Check the alert log for a list of the files that were found not to be in backup mode. If there is a possibility that those files have been modified during online backup, then replace their backups with new ones.
-
ORA-01266: Unable to create unique file name
-
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.
-
Action: Retry the operation. If that fails, also, it may be necessary to change the default destination directory for the file type and then retry.
-
ORA-01271: Unable to create new file name for file string
-
Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.
-
Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery.
-
ORA-01274: cannot add datafile 'string' - file could not be created
-
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is 'UNNAMEDnnnnn'.
-
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
-
ORA-01275: Operation string is not allowed if standby file management is automatic.
-
Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
-
Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed.
-
ORA-01276: Cannot add file string. File has an Oracle Managed Files file name.
-
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.
-
Action: Retry the operation with a new file name.
-
ORA-01288: cannot apply this DDL to the Logminer Dictionary
-
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.
-
Action: Do not execute unsupported commands when using Streams, Logical Standby, or Logminer. Turn off DDL tracking in order for Logminer to skip unsupported commands.
-
ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
-
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.
-
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
-
ORA-01307: no LogMiner session is currently active
-
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()
-
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
-
ORA-01311: Illegal invocation of the mine_value function
-
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.
-
Action: Rewrite the SQL statement with a legal invocation of mine_value
-
ORA-01312: Specified table/column does not exist
-
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.
-
Action: Create a LogMiner session at a start SCN at which the table definition is available.
-
ORA-01314: Name of the column to be mined should be a string literal
-
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
-
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in 'a.b.c.d'.
-
ORA-01321: No Logminer Dictionary for requested start SCN
-
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.
-
Action: Re-issue the start_logminer request with a start SCN for which a Logminer Dictionary is available.
-
ORA-01333: failed to establish Logminer Dictionary
-
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.
-
Action: If build() was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added. The following query, run on the system which build() was run, can be helpful in identifying the requried files. select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally a set of files beginning with one which has DICTIONARY_BEGIN = 'YES' and all following log files through one marked DICTIONARY_END = 'YES' must be added.
-
ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data
-
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.
-
Action: Specify a bigger max_sga for the given LogMiner session and try again.
-
ORA-01347: Supplemental log data no longer found
-
Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
-
Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.
-
ORA-01351: tablespace given for Logminer dictionary does not exist
-
Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
-
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
-
ORA-01352: tablespace given for Logminer spill does not exist
-
Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
-
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
-
ORA-01353: existing Logminer session
-
Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.
-
Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
-
ORA-01354: Supplemental log data must be added to run this command
-
Cause: An attempt was made to perform an operation that required that supplemental log data be enabled.
-
Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error.
-
ORA-01358: LogMiner version is less than mined dictionary version
-
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.
-
Action: Mine the logs using a newer version of the Oracle database having a version number that is equal to or greater than the dictionary version.
-
ORA-01361: global name mismatch
-
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.
-
Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file.
-
ORA-01364: waiting for branch at SCN string
-
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.
-
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files can be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
-
ORA-01365: waiting for new branch registration
-
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.
-
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files may be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
-
ORA-01373: insufficient memory for staging persistent LogMiner session
-
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.
-
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
-
ORA-01378: The logical block size (string) of file string is not compatible with the disk sector size (media sector size is string and host sector size is string)
-
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.
-
Action: Create file or move file to the proper disk.
-
ORA-01380: Instance string (thread string) has less than two string block size log files
-
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.
-
Action: Add log files to the thread that signals error, and try again.
-
ORA-01381: Dropping log string would leave less than two log files with block size string for instance string (thread string)
-
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.
-
Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.
-
ORA-01409: NOSORT option may not be used; rows are not in ascending order
-
Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split 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.
-
Action: Create the index without the NOSORT option, or ensure table is stored in one extent.
-
ORA-01438: value larger than specified precision allowed for this column
-
Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.
-
Action: Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.
-
ORA-01463: cannot modify column datatype with current constraint(s)
-
Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa.
-
Action: Remove the constraint(s) or do not perform the offending operation.
-
ORA-01485: compile bind length different from execute bind length
-
Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length (given in the bind call). The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.
-
Action: None