ORA-01653: unable to extend table string.string by string in tablespace string

ORA-01653: unable to extend table string.string by string in tablespace string

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.

ORA-01652: unable to extend temp segment by string in tablespace string

ORA-01652: unable to extend temp segment by string in tablespace string

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.

ORA-01651: unable to extend save undo segment by string for tablespace string

ORA-01651: unable to extend save undo segment by string for tablespace string

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.

ORA-01650: unable to extend rollback segment string by string in tablespace string

ORA-01650: unable to extend rollback segment string by string in tablespace string

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.

ORA-01649: operation not allowed with a backup control file

ORA-01649: operation not allowed with a backup control file

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.

ORA-01648: log string is the current log of disabled instance string (thread string)

ORA-01648: log string is the current log of disabled instance string (thread string)

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.

ORA-01647: tablespace string is read only, cannot allocate space in it

ORA-01647: tablespace string is read only, cannot allocate space in it

Cause: Tried to allocate space in a read only tablespace

Action: Create the object in another tablespace

ORA-01646: tablespace string is not read only - cannot make read write

ORA-01646: tablespace string is not read only - cannot make 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.

ORA-01645: previous attempt to make read write is half complete

ORA-01645: previous attempt to make read write is half complete

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.

ORA-01644: tablespace string is already read only

ORA-01644: tablespace string is already read only

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.

ORA-01643: system tablespace can not be made read only

ORA-01643: system tablespace can not be made read only

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.

ORA-01642: begin backup not needed for read only tablespace string

ORA-01642: begin backup not needed for read only tablespace string

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.

ORA-01641: tablespace string is not online - cannot add data file

ORA-01641: tablespace string is not online - cannot add data file

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.

ORA-01640: cannot make tablespace read only with active transactions

ORA-01640: cannot make tablespace read only with active transactions

Cause: Attempting to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions.

Action: Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved.

ORA-01639: instance string has no thread assigned to it

ORA-01639: instance string has no thread assigned to it

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.

ORA-01638: parameter string does not allow ORACLE version string to mount cluster database

ORA-01638: parameter string does not allow ORACLE version string to mount cluster database

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.

ORA-01637: rollback segment string is being used by another instance (#string)

ORA-01637: rollback segment string is being used by another instance (#string)

Cause: The instance is trying to online a RS already in use by another instance

Action: none

ORA-01636: rollback segment string is already online

ORA-01636: rollback segment string is already online

Cause: The instance is trying to online an already online RS

Action: none

ORA-01635: rollback segment #string specified not available

ORA-01635: rollback segment #string specified not available

Cause: (same as 1545)

Action: (same as 1545)

ORA-01634: rollback segment number string is about to go offline

ORA-01634: rollback segment number string is about to go offline

Cause: The rollback segment specified was marked to go offline by DBA.

Action: Bring the rollback segment online first.

ORA-01633: Real Application Clusters Option needed for this operation

ORA-01633: Real Application Clusters Option needed for this operation

Cause: System doesn t have Real Application Clusters configured

Action: Obtain Real Application Clusters option

ORA-01632: max # extents (string) reached in index string.string

ORA-01632: max # extents (string) reached in index string.string

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.

ORA-01631: max # extents (string) reached in table string.string

ORA-01631: max # extents (string) reached in table string.string

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

ORA-01630: max # extents (string) reached in temp segment in tablespace string

ORA-01630: max # extents (string) reached in temp segment in tablespace string

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

ORA-01629: max # extents (string) reached saving undo for tablespace string

ORA-01629: max # extents (string) reached saving undo for tablespace string

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 .

ORA-01628: max # extents (string) reached for rollback segment string

ORA-01628: max # extents (string) reached for rollback segment string

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.

ORA-01627: rollback segment number string is not online

ORA-01627: rollback segment number string is not online

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.

ORA-01626: rollback segment number string cannot handle more transactions

ORA-01626: rollback segment number string cannot handle more transactions

Cause: Too many transactions in this segment.

Action: Choose a different rollback segment, or reduce the number of concurrent transactions.

ORA-01625: rollback segment string does not belong to this instance

ORA-01625: rollback segment string does not belong to this instance

Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance.

Action: none

ORA-01624: log string needed for crash recovery of instance string (thread string)

ORA-01624: log string needed for crash recovery of instance string (thread string)

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.

ORA-01623: log string is current log for instance string (thread string) - cannot drop

ORA-01623: log string is current log for instance string (thread string) - cannot drop

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.

ORA-01622: thread number must be specified - default not specific

ORA-01622: thread number must be specified - default not specific

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.

ORA-01621: cannot rename member of current log if database is open

ORA-01621: cannot rename member of current log if database is open

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.

ORA-01620: no public threads are available for mounting

ORA-01620: no public threads are available for mounting

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.

ORA-01619: thread string is mounted by another instance

ORA-01619: thread string is mounted by another instance

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.

ORA-01618: redo thread string is not enabled - cannot mount

ORA-01618: redo thread string is not enabled - cannot mount

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.

ORA-01617: cannot mount: string is not a valid thread number

ORA-01617: cannot mount: string is not a valid thread number

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 or checkpoint progress record sections of the control file.

ORA-01616: instance string (thread string) is open - cannot disable

ORA-01616: instance string (thread string) is open - cannot disable

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.

ORA-01615: instance string (thread string) is mounted - cannot disable

ORA-01615: instance string (thread string) is mounted - cannot disable

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.

ORA-01614: instance string (thread string) is busy - cannot enable

ORA-01614: instance string (thread string) is busy - cannot 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.

ORA-01613: instance string (thread string) only has string logs -at least 2 logs required to enable.

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

ORA-01612: instance string (thread string) is already enabled

ORA-01612: instance string (thread string) is already enabled

Cause: An attempt was made to enable a thread that is already enabled.

Action: Either use this thread or enable another thread.

ORA-01611: thread number string is invalid - must be between 1 and string

ORA-01611: thread number string is invalid - must be between 1 and string

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 or checkpoint progress record sections of the control file.

ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

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.

ORA-01609: log string is the current log for thread string - cannot drop members

ORA-01609: log string is the current log for thread string - cannot drop members

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.

ORA-01608: cannot bring rollback segment string online, its status is (string)

ORA-01608: cannot bring rollback segment string online, its status is (string)

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

ORA-01607: cannot add logfile to the specified instance

ORA-01607: cannot add logfile to the specified instance

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 or checkpoint progress record secions of the control file.

ORA-01606: gc_files_to_locks not identical to that of another mounted instance

ORA-01606: gc_files_to_locks not identical to that of another mounted instance

Cause: The gc_files_to_locks parameters were different on two instances.

Action: Modify the INIT.ORA parameter gc_files_to_locks and restart.

ORA-01605: missing numbers in clause string of string

ORA-01605: missing numbers in clause string of string

Cause: The numbers were missing for this parameter.

Action: Correct the INIT.ORA parameter and restart the instance.

ORA-01604: illegal number range in clause string of string

ORA-01604: illegal number range in clause string of string

Cause: The number range was invalid for this parameter.

Action: Correct the INIT.ORA parameter and restart the instance.

ORA-01603: illegal grouping size in clause string of string

ORA-01603: illegal grouping size in clause string of string

Cause: The grouping size was invalid for this parameter.

Action: Correct the INIT.ORA parameter and restart the instance.

ORA-01601: illegal bucket size in clause string of string

ORA-01601: illegal bucket size in clause string of string

Cause: The bucket size was invalid for this parameter.

Action: Correct the INIT.ORA parameter and restart the instance.

ORA-01600: at most one string in clause string of string

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.

ORA-01599: failed to acquire rollback segment (string), cache space is full

ORA-01599: failed to acquire rollback segment (string), cache space is full

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

ORA-01598: rollback segment string is not online

ORA-01598: rollback segment string is not online

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.

ORA-01597: cannot alter system rollback segment online or offline

ORA-01597: cannot alter system rollback segment online or offline

Cause: Tried to online or offline the system rollback segment

Action: None

ORA-01596: cannot specify system in string parameter

ORA-01596: cannot specify system in string parameter

Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message

Action: change the INIT.ORA parameter

ORA-01595: error freeing extent (string) of rollback segment (string))

ORA-01595: error freeing extent (string) of rollback segment (string))

Cause: Some error occurred while freeing inactive rollback segment extents.

Action: Investigate the accompanying error.

ORA-01594: attempt to wrap into rollback segment (string) extent (string) which is being freed

ORA-01594: attempt to wrap into rollback segment (string) extent (string) which is being freed

Cause: Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and or 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.

ORA-01593: rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)

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.