Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01600 to ORA-01700
- ORA-01600: at most one “string” in clause “string” of string
Cause: The INIT.ORA parameter was mis-specified.
Action: Correct the INIT.ORA parameter and restart the instance.
Cause: The bucket size was invalid for this parameter.
Action: Correct the INIT.ORA parameter and restart the instance.
Cause: The grouping size was invalid for this parameter.
Action: Correct the INIT.ORA parameter and restart the instance.
Cause: The number range was invalid for this parameter.
Action: Correct the INIT.ORA parameter and restart the instance.
Cause: The numbers were missing for this parameter.
Action: Correct the INIT.ORA parameter and restart the instance.
Cause: A parameter was different on two instances.
Action: Modify the initialization parameter and restart.
Cause: The limit on the number of instances supported by the control file has been reached.
Action: Use an instance name supported by the control file, or resize the thread record and/or checkpoint progress record secions of the control file.
Cause: Could have been brought online before by DBA or left as a result of process crash.
Action: Check the status of rollback segment in undo$ or dba_rollback_segs
Cause: A member of the current log for a thread cannot be dropped.
Action: If the thread is opened, request a log switch by the instance that is using it. If it is not open, disable the thread, manually archive the log, or clear it.
Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was recreated with the RESETLOGS option, or the control file being used is a backup control file. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open.
Action: Perform recovery using the BACKUP CONTROFILE option.
Cause: A thread number in a command is greater than the number of threads supported by the control file.
Action: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file.
Cause: An attempt was made to enable a thread that is already enabled.
Action: Either use this thread or enable another thread.
- ORA-01613: instance string (thread string) only has string logs – at least 2 logs required to enable.
Cause: The thread cannot be enabled because it only has two online log files associated with it.
Action: Add logs to the thread or pick another thread to enable
Cause: The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread.
Action: Wait and try again, or find another thread to enable.
Cause: Some instance, possibly this one, has allocated the thread for its use. The thread can not be disabled while in use.
Action: Shut the instance down cleany using the thread.
Cause: The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery.
Action: If the database is open, instance recovery should close the thread soon – wait a few minutes. Otherwise open the database – crash recovery will close the thread.
Cause: The INIT.ORA parameter “thread” is not between 1 and the number of threads allowed by the control file.
Action: Shut down the instance, change the INIT.ORA parameter and startup, or resize the thread record and/or checkpoint progress record sections of the control file.
Cause: The INIT.ORA parameter “thread” requests a thread that is not enabled. A thread must be enabled before it can be mounted.
Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread. If the database is open in another instance then the thread may be enabled.
Cause: The INIT.ORA parameter “thread” requests a thread that has been mounted by another instance. Only one instance may use a thread.
Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread.
Cause: The INIT.ORA parameter “thread” is zero, its default value. There are no threads which have been publicly enabled, and not mounted.
Action: Shutdown the instance, change the INIT.ORA parameter to a thread which is privately enabled and not mounted. If the database is open in another instance, then a thread may be publicly enabled.
Cause: This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done.
Action: Wait until the log is not current, or mount the database exclusively.
Cause: The thread was not specified when adding a log, and the currently mounted thread was chosen by default at mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to.
Action: Explicitly specify the thread number either in the INIT.ORA parameter “thread”, or in the add command.
Cause: A thread’s current log cannot be dropped even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again.
Action: If the database is not open then disable the thread. If the database is open and an instance has the thread open, then the instance can be requested to switch logs. If the database is closed the log can be archived or cleared to force a switch.
Cause: A log cannot be dropped or cleared until the thread’s checkpoint has advanced out of the log.
Action: If the database is not open, then open it. Crash recovery will advance the checkpoint. If the database is open force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do incomplete recovery until cancel at this log.
Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance.
Action: n/a
Cause: Too many transactions in this segment.
Action: Choose a different rollback segment, or reduce the number of concurrent transactions.
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: An attempt was made to extend a rollback segment that was already at the MAXEXTENTS value.
Action: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value.
Cause: Save undo for the offline tablespace at max extents
Action: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied .
Cause: A temp segment tried to extend past max extents.
Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace
Cause: A table tried to extend past maxextents
Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params
Cause: An index tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.
Cause: System doesn’t have Real Application Clusters configured
Action: Obtain Real Application Clusters option
Cause: The rollback segment specified was marked to go offline by DBA.
Action: Bring the rollback segment online first.
Cause: (same as 1545)
Action: (same as 1545)
Cause: The instance is trying to online an already online RS
Action: n/a
Cause: The instance is trying to online a RS already in use by another instance
Action: n/a
Cause: The recovery compatible parameter is set too low to allow this software version to mount in cluster database mode.
Action: Either use an earlier software release or advance the recovery_compatible parameter. If this happens when no recovery_compatible parameter has been specified then set it to the current software release.
Cause: There is no mapping from instance to thread for this instance in the control file.
Action: Make sure that this instance has a thread assigned to it by adding logfiles to this instance or by starting the instance with an existing thread which will automatically create a mapping.
Cause: An attempt was made to alter a tablespace read-only while there were changes in the tablespace made by in-doubt distributed transactions. The in-doubt transactions must commit or rollback to ensure that there is no undo for a tablespace before it can be made read-only.
Action: Any in-doubt transactions that made changes to the tablespace must be resolved.
Cause: Attempting to add a datafile to a tablespace that has been set to read-only or offline.
Action: Make the tablespace online and read write then add the datafile.
Cause: Attempting to begin or end a backup for a tablespace that has been set to read-only.
Action: Take the backup without any begin or end commands. The files are not being modified so the backup will be consistent.
Cause: Attempting to set the system tablespace to read-only. The system tablespace must remain read write for database operation.
Action: Leave system tablespace read write.
Cause: Attempting to make tablespace read-only that is already read-only.
Action: Leave tablespace read-only, or make read write then make read-only again.
Cause: A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be useable after a resetlogs if its files are offline.
Action: Repeat the command to make the tablespace read write.
Cause: Attempting to make a tablespace read write that is not read-only. It may be either online or offline.
Action: Leave tablespace read write.
Cause: Tried to allocate space in a read-only tablespace
Action: Create the object in another tablespace
Cause: An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log can not be cleared or archived.
Action: Complete the thread enable by issuing the enable command again.
Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup.
Action: Wait until after the database has been opened and try again.
Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: Failed to allocate an extent of the required number of blocks for saving undo entries for the indicated offline tablespace.
Action: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied.
Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A cluster tried to extend past maxextents
Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.
Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL
Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.
Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE
Cause: Attempting to make tablespace permanent that is already permanent.
Action: Leave tablespace permanent.
Cause: Attempting to make tablespace temporary that is already temporary.
Action: Leave tablespace permanent.
Cause: Tried to convert a non-empty tablespace to a temporary tablespace
Action: To drop all the objects in the tablespace.
Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY.
Action: To decide what the tablespace contents should be and stay with it.
Cause: Internal Error.
Action: Contact Oracle Support.
Cause: Attempting to mount, recover or activate a standby database without a standby control file.
Action: Create a standby control file before attempting to use the database as a standby database.
Cause: Attempting to mount, recover, or open a standby database without the appropriate command option to designate a standby database.
Action: Use the standby option or appropriate commands, or mount with the primary control file.
Cause: There is no more room in the control file for adding tablespaces.
Action: Resize the control file or drop other tablespaces.
Cause: Attempting to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later.
Action: Specify the DROP option or leave the file online.
Cause: Attempting to activate a standby database with a control file that has not been recovered to the same point as the data files. Most likely the control file was just copied from the primary database and has not been used for recovery.
Action: Recover the standby database until all the files are consistent.
Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby.
Action: Either copy the file from the primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover.
Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database.
Action: Complete any needed recovery and open the database with the resetlogs option.
Cause: Attempting to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match.
Action: Open the database, then retry the operation.
Cause: This data file was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we can not create a standby control file.
Action: Find the file and bring it online. If desired it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error.
Cause: Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file.
Action: Rebuild the control file using CREATE CONTROLFILE, and give the correct file.
Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent with those in other instances.
Action: Make sure all instances have the same max_commit_propagation_delay.
Cause: When the given file name was converted to the name used for the standby database, the converted name was bigger than the maximum allowed file name.
Action: Change initialization parameter DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT to convert to a valid file name.
Cause: The DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameters were not the same as in other instances that already had the database mounted.
Action: Change initialization parameters DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT to match other instances.
Cause: The initialization parameter does not have even number of strings for its value. The odd numbered strings are patterns to be found in file names. The even numbered strings are used to replace the corresponding patterns when found in file names.
Action: Specify even number of strings for the parameter, or omit the parameter.
Cause: An attempt was made to activate a standby database when the database was in the middle of being opened.
Action: Wait for database open to finish and retry the ACTIVATE command.
Cause: Failed to allocate an extent of the required number of blocks for a LOB segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A LOB segment tried to extend past max extents.
Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace
Cause: Temporary space (usually for sorting) could not be allocated in either main storage or a tempfile. An attempt was made to allocate the space from the tablespace named, but the database is opened read-only. The database open requires a sort work space.
Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE initialization parameter), or create a temporary tablespace before making the database read-only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace.
Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A table tried to extend past maxextents
Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params
Cause: An index tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.
Cause: The number of files for a given tablespace has reached its maximum value
Action: Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace.
Cause: Attempting to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute
Action: Change the specified logging attribute
Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: There was a syntax in the INIT.ORA parameter.
Action: Fix the syntax error and restart the instance.
Cause: sort area size too small to fit two records in memory
Action: increase sort_area_size
Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
- ORA-01692: unable to extend lob segment string.string partition string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A LOB segment tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.
Cause: A LOB segment tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.
Cause: Version 8.0.1 database may not have shutdown cleanly
Action: May have to reload the 8.0.1 database and shutdown cleanly
Cause: Attempting to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current control file for a clone.
Action: Mount without the clone option or use a backup control file and shutdown the other instances before mounting as a clone.
Cause: Attempting to mount a clone database without the appropriate command option to designate a clone database.
Action: Use the clone option or appropriate commands, or mount with the primary control file.
Cause: Attempting to online a rollback segment in a clone database.
Action: Do not use this command.
Cause: Attempting to online a tablespace or begin another point in time import while a point in time import is already in progress
Action: Wait until the import complets