ORA-01184: logfile group string already exists

ORA-01184: logfile group string already exists

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

Action: Specify a different logfile number, or let the database choose an unused value.

ORA-01183: cannot mount database in SHARED mode

ORA-01183: cannot mount database in SHARED mode

Cause: Some other instance has the database mounted exclusive.

Action: Shutdown other instance then mount shared.

ORA-01182: cannot create database file string - file is in use or recovery

ORA-01182: cannot create database file string - file is in use or recovery

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

Action: Close database in all instances and end all recovery sessions

ORA-01181: file string created before last known RESETLOGS, cannot recreate

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-01180: can not create datafile 1

ORA-01180: can not create datafile 1

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

Action: Recover file from a backup or recreate database.

ORA-01179: file string does not exist

ORA-01179: file string does not exist

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

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

ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate

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-01177: data file does not match dictionary - probably old incarnation

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-01176: data dictionary has more than the string files allowed by the controlfie

ORA-01176: data dictionary has more than the string files allowed by the controlfie

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

Action: Recreate the control file with a larger MAXDATAFILES.

ORA-01175: data dictionary has more than the string files allowed by the instance

ORA-01175: data dictionary has more than the string files allowed by the instance

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

Action: Shutdown the instance and restart with a larger number of db_files

ORA-01174: DB_FILES is string buts needs to be string to be compatible

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-01173: data dictionary indicates missing data file from system tablespace

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-01172: recovery of thread string stuck at block string of file string

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-01171: datafile string going offline due to error advancing checkpoint

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-01170: file not found string

ORA-01170: file not found string

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

Action: The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit.

ORA-01169: DATAFILE number 1 not found. Must be present

ORA-01169: DATAFILE number 1 not found. Must be present

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

Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command.

ORA-01168: physical block size string does not match size string of other members

ORA-01168: physical block size string does not match size string of other members

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

Action: Use a physical device with matching block size.

ORA-01167: two files are the same file or group number or the same file

ORA-01167: two files are the same file or 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-01166: file number string is larger than string (string)

ORA-01166: file number string is larger than string (string)

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

Action: Increase the maximum specified on the command line.

ORA-01165: MAXDATAFILES may not exceed string

ORA-01165: MAXDATAFILES may not exceed string

Cause: MAXDATAFILES specified on the command line too large.

Action: Resubmit the command with a smaller MAXDATAFILES

ORA-01164: MAXLOGFILES may not exceed string

ORA-01164: MAXLOGFILES may not exceed string

Cause: MAXLOGFILES specified on the command line too large.

Action: Resubmit the command with a smaller MAXLOGFILES

ORA-01163: SIZE clause indicates string (blocks), but should match header string

ORA-01163: SIZE clause indicates string (blocks), but should match header string

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.

Action: Specify the correct filename and size ( in bytes ).

ORA-01162: block size string in file header does not match configured block sizes

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-01161: database name string in file header does not match given name of string

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-01160: file is not a string

ORA-01160: file is not a string

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

Action: Please double check the mentioned file.

ORA-01159: file is not from same database as previous files -wrong database id

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-01158: database string already mounted

ORA-01158: database string already mounted

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

Action: Find which instance is still running. Perhaps you have not lost the control files after all.

ORA-01157: cannot identify or lock data file string - see DBWR trace file

ORA-01157: cannot identify or 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-01156: recovery in progress may need access to files

ORA-01156: recovery in progress may need access to files

Cause: Either media recovery or instance recovery is in progress. It may need the files this operation is being applied to.

Action: Wait for recovery to complete.

ORA-01155: the database is being opened, closed, mounted or dismounted

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-01154: database busy. Open, close, mount, and dismount not allowed now

ORA-01154: database busy. Open, close, mount, and dismount not allowed now

Cause: Some operation is in progress that expects the opened or 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-01153: an incompatible media recovery is active

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-01152: file string was not restored from a sufficiently old backup

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-01151: use media recovery to recover block, restore backup if needed

ORA-01151: use media recovery to recover block, restore backup if needed

Cause: Error 1172 occurred.

Action: This is additional information for error 1172.

ORA-01150: cannot prevent writes - file string has online backup set

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-01149: cannot shutdown - file string has online backup set

ORA-01149: cannot shutdown - file string has online backup set

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

Action: End the backup of the offending tablespace and retry this command.

ORA-01148: cannot refresh file size for datafile string

ORA-01148: cannot refresh file size for datafile string

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.

Action: Restore access to the device.

ORA-01147: SYSTEM tablespace file string is offline

ORA-01147: SYSTEM tablespace file string is offline

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.

Action: Bring the file online.

ORA-01146: cannot start online backup - file string is already in backup

ORA-01146: cannot start online backup - file string is already in backup

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

Action: End the first backup before beginning another.

ORA-01145: offline immediate disallowed unless media recovery enabled

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-01144: File size (string blocks) exceeds maximum of string blocks

ORA-01144: File size (string blocks) exceeds maximum of string blocks

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

Action: Specify a smaller size.

ORA-01143: cannot disable media recovery - file string needs media recovery

ORA-01143: cannot disable media recovery - file string needs media recovery

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

Action: Recover the offending file or drop the tablespace it belongs to and retry this command.

ORA-01142: cannot end online backup - none of the files are in backup

ORA-01142: cannot end online backup - none of the files are in backup

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

Action: None. Online backup does not need to be ended for this tablespace.

ORA-01141: error renaming data file string - new file string not found

ORA-01141: error renaming data file string - new file string not found

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

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

ORA-01140: cannot end online backup - all files are offline or readonly

ORA-01140: cannot end online backup - all files are offline or readonly

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

Action: None. Online backup does not need to be ended for this tablespace.

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

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

Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS

ORA-01138: database must either be open in this instance or not at all

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-01137: data file string is still in the middle of going offline

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-01136: specified size of file string (string blocks) is less than original size of string blocks

ORA-01136: specified size of file string (string blocks) is less than original size of string blocks

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

Action: Create the file with a larger size.

ORA-01135: file string accessed for DML or query is offline

ORA-01135: file string accessed for DML or query is offline

Cause: Attempted to access a data file that is offline

Action: Bring the data file back online

ORA-01129: user s default or temporary tablespace does not exist

ORA-01129: user s default or temporary tablespace does not exist

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

Action: Reassign the default or temporary tablespace.

ORA-01128: cannot start online backup - file string is offline

ORA-01128: cannot start online backup - file string is offline

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

Action: Bring the offending files online and retry this command or do a cold backup.

ORA-01127: database name string exceeds size limit of string characters

ORA-01127: database name string exceeds size limit of string characters

Cause: Obvious

Action: none

ORA-01126: database must be mounted in this instance and not open in any instance

ORA-01126: database must be mounted in this instance and not open in any instance

Cause: Obvious

Action: none

ORA-01125: cannot disable media recovery - file string has online backup set

ORA-01125: cannot disable media recovery - file string has online backup set

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

Action: End the backup of the offending tablespace and retry this command.

ORA-01124: cannot recover data file string - file is in use or recovery

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-01123: cannot start online backup; media recovery not enabled

ORA-01123: cannot start online backup; media recovery not enabled

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

Action: Enable media recovery and retry this operation.

ORA-01122: database file string failed verification check

ORA-01122: database file string failed verification check

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

Action: Make certain that the db files and control files are the correct files for this database.

ORA-01121: cannot rename database file string - file is in use or recovery

ORA-01121: cannot rename database file string - file is in use or recovery

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

Action: Close database in all instances and end all recovery sessions.

ORA-01120: cannot remove online database file string

ORA-01120: cannot remove online database file string

Cause: Attempting to drop a datafile when it is online

Action: Take file offline before dropping.