Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01500 to ORA-01600
- ORA-01500: failure in getting date/time
Cause: During create database or alter tablespace, there was a failure in getting the date and time.
Action: Contact your customer support representative.
Cause: An error occurred during create database
Action: See accompanying errors.
Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation
Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition
Cause: An error occurred during CREATE CONTROLFILE
Action: See accompanying errors.
Cause: The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name.
Action: correct or omit one of the two names.
Cause: During create or alter database, error(s) occurred when adding new log files.
Action: Check error stack for detailed error information.
Cause: No db_name INIT.ORA aprameter was specified.
Action: The database name must be given in the db_name INIT.ORA parameter.
Cause: A command was attempted that requires the database to be mounted.
Action: If you are using the ALTER DATABASE statement via the SQLDBA startup command, specify the MOUNT option to startup; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database. If you are doing a FLASHBACK DATABASE, you must first mount the desired database.
Cause: CREATE DATABASE was unable to process the specified file.
Action: Check the offending line in the specified file.
Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database.
Action: Correct the database name spelling or DISMOUNT the mounted database.
Cause: During ALTER DATABASE, an error occurred while dropping log files.
Action: Check the error stack for detailed error information.
Cause: An error occurred during the ALTER DATABASE RENAME FILE command.
Action: Check the error stack for detailed error information.
Cause: An attempt to change a log file’s name in the control file failed because no file was found with the new name.
Action: Make sure that the log file has been properly renamed by the operating system and retry.
Cause: The operating system returned a time that was not between 1988 and 2121.
Action: Correct the time kept by the operating system.
Cause: A log file name, or list of member names, did not correspond to an existing log.
Action: Specify an existing log file.
Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file.
Action: Specify the name of an existing log file.
Cause: An attempt was made to use ALTER DATABASE to rename a log file, data file, or temporary file; or to change attributes of a data file or temporary file (for example, resize, autoextend, online or offline); or to re-create or move a data file. The attempt failed because the specified file is not known to the database’s control file or the current container or is not of a type supported by the request.
Action: Specify the name or number of an existing file of the correct type, as appropriate. Check the relevant V$ table for a list of possible files.
Cause: Used to print member names
Action: See top level error for information
Cause: Only one log file was specified in the CREATE DATABASE statement.
Action: Specify at least two log files.
Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.
Action: Retry your system installation procedure or contact your customer support representative.
Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database.
Action: Use fewer files or re-create the database with a larger value of MAXDATAFILES.
Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files.
Action: Check the error stack for detailed error information.
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.
Action: Specify the correct file name.
Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.
Action: Rename the file to a name not already being used as part of the database.
Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.
Action: Create the file as a name not already being used as part of the database.
Cause: An error occurred when renaming files as part of ALTER TABLESPACE.
Action: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack.
Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.
Action: Retry your system installation procedure or contact your customer support representative.
Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.
Action: Retry your system installation procedure or contact your customer support representative.
Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad.
Action: Retry your system installation procedure or contact your customer support representative.
Cause: CREATE DATABASE was not able to close the specified file.
Action: Retry your system installation procedure or contact your customer support representative.
Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted.
Action: If you wish to mount the database, shutdown the instance and then startup the instance and retry the operation.
Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.
Action: If you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation.
Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance.
Action: Make sure no one else is simultaneously altering the instance. If no one is, contact your customer support representative; otherwise, retry the operation.
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.
Action: Specify the correct file name or the correct tablespace name.
Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.
Action: Use the correct rollback segment name.
Cause: Specified rollback segment already exists or given name starts with _SYSSMU.
Action: Use a different name. Note that _SYSSMU is an illegal prefix to an RBU segment.
Cause: The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.
Action: Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner.
Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database.
Action: Use a different file name.
Cause: Failed to acquire any rollback segment during startup in shared mode
Action: Startup in exclusive mode to create one more public segment or specify available private segments in the INIT.ORA parameter rollback_segments_required, then startup in shared mode
Cause: Failed to either make a tablespace read-only or offline because it is not online. A tblespace must be online before it can become read-only or offline normal.
Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read-only.
Cause: Failed to bring a tablespace online because it is not offline
Action: Check the status of the tablespace
Cause: Tried to bring system tablespace offline
Action: Shutdown if necessary to do recovery
Cause: Tried to allocate space in an offline tablespace
Action: Bring the tablespace online or create the object in other tablespace
Cause: Tried to create a tablespace which already exists
Action: Use a different name for the new tablespace
Cause: Tried to drop system rollback segment
Action: None
Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.
Action: Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). 5) Remove the name from the _corrupted_rollback_segments parameter.
Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read-only
Action: Shutdown instances that use the active rollback segments in the tablespace and then make the tablespace offline or read-only
Cause: Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.
Action: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.
Cause: Tried to drop a tablespace that contains active rollback segment(s)
Action: Shutdown instances that use the active rollback segments in the tablespace and then drop the tablespace
Cause: Tried to drop a non-empty tablespace
Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option
Cause: Tried to drop system tablespace
Action: None
Cause: Doing recursive extent of rollback segment, trapped internally by the system
Action: None
Cause: Tried to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.
Action: Create one or more private/public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. If the non-system tablespace has AUTO segment space management, then create an undo tablespace.
Cause: The number of extents allocated is greater than the MAXEXTENTS specified.
Action: Specify a larger MAXEXTENTS value.
Cause: Too many concurrent transactions
Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again.
Cause: rollback records needed by a reader for consistent read are overwritten by other writers
Action: If in Automatic Undo Management mode, increase undo_retention setting. Otherwise, use larger rollback segments
Cause: Specified MINEXTENTS of less than 2 for rollback segment
Action: Specify larger MINEXTENTS
Cause: Specified extent of less than minimum size for rollback segment
Action: Specify larger extents
Cause: All the available transaction id’s have been used
Action: Shutdown the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction id’s.
Cause: Specified MAXEXTENTS of less than 2 for rollback segment
Action: Specify larger MAXEXTENTS
Cause: like pattern is not formed correctly
Action: make sure like pattern is specified correctly
Cause: Failed to remove all objects when dropping a tablespace
Action: Retry the drop tablespace until all objects are dropped
Cause: Failure occurred when trying to extend rollback segment
Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command to take the rollback segment offline.
Cause: Did not use the keyword PUBLIC to identified public rollback segment
Action: Use the keyword PUBLIC when identifying public rollback segment
Cause: The rollback segment segment identified is not public
Action: Do not use the keyword PUBLIC when identifying private rollback segment
Cause: An error occurred while trying to identify a file.
Action: Check the error stack for detailed information.
Cause: The list of files supplied to the command contained at least one duplicate.
Action: Remove the duplicate file specification and retry.
- ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string)
Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread.
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.
Cause: Trying to set space quota on a tablespace for PUBLIC.
Action: If trying to grant system-wide or tablespace-wide space priviledges to all users, use GRANT RESOURCE [ON tablespace] TO PUBLIC.
Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables.
Action: Recreate the database by specifying a larger file or more files.
Cause: The number of extents allocated is smaller than the MINEXTENTS specified.
Action: Specify a smaller MINEXTENTS value.
Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.
Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.
Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.
Action: Drop and recreate the rollback segment.
Cause: Some process tries to make changes while the db is being shutdown
Action: None
Cause: the limit on the number of concurrent transactions has been hit
Action: shutdown the system, increase the INIT.ORA parameter ‘transactions’ , and then restart the system.
Cause: failed to acquire necessary resource to do space management.
Action: Retry the operation.
Cause: The thread associated with instance is not enabled.
Action: Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command.
Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database.
Action: Use a different file name.
Cause: The data block indicated was corrupt. This was a physical corruption, also called a media corruption. The cause is unknown but is most likely external to the database. If ORA-26040 is also signaled, the corruption is due to NOLOGGING or UNRECOVERABLE operations.
Action: The general method to repair a media corrupt block is to restore a backup and recover the backup. For databases in ARCHIVELOG mode, use block media recovery or media recovery. In some situations, you can also drop the segment and re-create it. For example, you can drop an index and re-create the index.
Cause: A write error occurred during recovery
Action: Consult trace files for the nature of the write error, and correct error.
Cause: An operating system error occurred while attempting to create a control file backup.
Action: Check the error stack for more detailed information
Cause: Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated.
Action: The rollback segment extending will be rollbacked by the system, no more extension will be possible untill the next extent is freed up by rolling back or committing other transactions.
Cause: An operating system error occurred while attempting to open a control file for backup.
Action: Check the error stack for more detailed information
Cause: An operating system error occurred while attempting to get the block size of a control file for backup.
Action: Check the error stack for more detailed information
Cause: An operating system error occurred while attempting to get the file size of a control file for backup.
Action: Check the error stack for more detailed information
Cause: An operating system error occurred when attempting to identify the file to be used for control file backup.
Action: Check the error stack for more detailed information
Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE.
Action: Mount the database in EXCLUSIVE mode.
- ORA-01587: error during control file backup file copy
- ORA-01588: must use RESETLOGS option for database open
Cause: An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup, or a FLASHBACK DATABASE was done.
Action: Use the RESETLOGS option when opening the database.
Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.
Action: Specify the appropriate option.
Cause: storage parameter FREELIST GROUPS is too large.
Action: Reduce storage parameters FREELIST GROUPS
Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state.
Action: DBA should query the pending_trans$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, DBA should contact DBA at commit point if known or end user for correct outcome, or use heuristic default if given to issue a heuristic commit or abort command to finalize the local portion of the distributed transaction.
Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly.
Action: Investigate the internal error; may have to reload the Version 7 Investigate the internal error; may have to reload the Version 7 database (from backup) and shutdown the database cleanly.
- ORA-01593: rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.
Action: Specify a larger OPTIMAL size.
Cause: Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or too many extents to free
Action: The rollback segment shrinking will be rollbacked by the system; increase the optimal size of the rollback segment.
Cause: Some error occurred while freeing inactive rollback segment extents.
Action: Investigate the accompanying error.
Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message
Action: change the INIT.ORA parameter
Cause: Tried to online or offline the system rollback segment
Action: None
Cause: Could have been taken offline before by DBA or cleaned up by SMON.
Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online.
Cause: the amount statically allocated is not enough based on max_rollback_segments parameter.
Action: For now take another rollback segment offline or increase the parameter max_rollback_segments
Cause: The INIT.ORA parameter was mis-specified.
Action: Correct the INIT.ORA parameter and restart the instance.