Oracle Database Errors or Warnings from Error ORA-01621 to ORA-01630



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-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-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-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-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-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-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-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-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-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

Above are list of Oracle Database Errors or Warnings from Error ORA-01621 to ORA-01630 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *