thread

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename.

Action: Specify log by filename, by group number or by thread and sequence number.

ORA-00259: log %s of open instance %s (thread %s) is the current log, cannot archive

Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.

Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.

ORA-00260: cannot find online log sequence %s for thread %s

Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.

Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.

ORA-00262: current log %s of closed thread %s cannot switch

Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused.

Action: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.

ORA-00263: there are no logs that need archiving for thread %s

Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.

Action: No action required.

ORA-00269: specified log file is part of thread %s not %s

Cause: The given redo log file is not part of the given thread

Action: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.

ORA-00323: Current log of thread %s not useable and all others need archiving

Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used.

Action: Archive the logs for the thread then retry open.

ORA-00352: all logs for thread %s need to be archived - cannot enable

Cause: Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread.

Action: Archive a log for the thread or disable media recovery.

ORA-00363: log is not the archived version

Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.

Action: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.

ORA-00369: Current log of thread %s not useable and other log being cleared

Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.

Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs.

ORA-00390: log %s of thread %s is being cleared, cannot become current log

Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.

Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.

ORA-00391: All threads must switch to new log format at the same time

Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.

Action: Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database.

ORA-01192: must have at least one enabled thread

Cause: You must specify at least two logfiles from at least one thread at the create contolfile command line.

Action: Find the missing logfiles and resubmit the command with the newly found logfiles included in the command line.

ORA-01197: thread %s only contains one log

Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs.

Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE.

ORA-01216: thread %s is expected to be disabled after CREATE CONTROLFILE

Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).

Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be recreated after the database is open.

ORA-01222: MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s

Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.

Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.

ORA-01225: thread number %s is greater than MAXINSTANCES %s

Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.

Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.

ORA-01567: dropping log %s would leave less than 2 log files for instance %s (thread %s)

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.

ORA-01576: The instance %s is not enabled

Cause: The thread associated with instance is not enabled.

Action: Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command.

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

ORA-01609: log %s is the current log for thread %s - 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-01611: thread number %s is invalid - must be between 1 and %s

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.

ORA-01612: instance %s (thread %s) 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-01613: instance %s (thread %s) only has %s 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-01614: instance %s (thread %s) 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-01615: instance %s (thread %s) 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-01616: instance %s (thread %s) 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-01617: cannot mount: %s 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 checkpoint progress record sections of the control file.

ORA-01618: redo thread %s 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-01619: thread %s 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-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-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 %s is current log for instance %s (thread %s) - 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-01639: instance %s has no thread assigned to it

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-01648: log %s is the current log of disabled instance %s (thread %s)

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-01977: Missing thread number

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-02174: Missing required thread number

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-02188: Cannot enable instance publicly

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-10007: log switch debug crash after new log select, thread %s

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-10008: log switch debug crash after new log header write, thread %s

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-10009: log switch debug crash after old log header write, thread %s

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-10333: dump MTTR statistics each time it is updated

Cause: Keyword "THREAD" found but thread number not specified.

Action: Fix command line and resubmit

ORA-16070: parameter %s contains an invalid REGISTER attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).

Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.

ORA-17613: Failed to initialize Oracle Disk Manager library: %s

Cause: ODM initialization for the thread failed due to insufficient previlige or memory.

Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library

ORA-18002: the specified outline does not exist

Cause: ODM initialization for the thread failed due to insufficient previlige or memory.

Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library

ORA-19621: archivelog range has already been specified

Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.

Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.

ORA-24301: null host specified in thread-safe logon

Cause: An HDA was not specified in the logon call while running in a thread safe environment.

Action: Make sure that HDA is not NULL when calling the logon routine.

ORA-24302: host connection in use by another thread

Cause: An attempt was made to use the host connection while it was in use by another thread.

Action: Wait for another thread to finish before using this connection.

ORA-24853: failed to connect thread to shared subsystem

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem.

Action: Contact Oracle Customer Support.

ORA-24911: Cannot start listener thread at specified port

Cause: Thread already running at a different port.

Action: Set the correct port in the environment handle or let the system choose the port.

ORA-24912: Listener thread failed. %s

Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message.

Action: The client needs to be restarted.

ORA-27165: tried to join thread that does not exist

Cause: The program tried to join a thread that does not exist.

Action: This is an internal error; contact Oracle support.

ORA-27166: tried to join current thread

Cause: A thread in the program tried to join itself.

Action: This is an internal error; contact Oracle support.

ORA-29665: Java thread deadlock detected

Cause: The Java VM has detected a thread deadlock.//

Action: Modify the Java program to avoid the deadlock condition.

ORA-30135: OCI Thread operation fails

Cause: An OCI Thread function call has failed. //

Action: Check the function call to make sure that the correct parameters are being passed and take the apropriate action.

ORA-38718: Invalid thread number specified in the DUMP FLASHBACK command.

Cause: An invalid thread number was used in dumping the flashback database log files for a thread.

Action: Specify a valid thread number.

ORA-38736: Wrong thread number %s in flashback log file header.

Cause: The thread number in the flashback database log file did not match the control file.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38851: cannot mark the current instance (redo thread) as disabled

Cause: The standby switchover or failover operation failed because it needs to mark the current instance (redo thread) as disabled.

Action: Shut down this instance and start up using a different instance name or redo thread number and retry.

ORA-38852: cannot mark the current instance (redo thread) as disabled

Cause: The open resetlogs or standby activation operation failed because it must use a different instance (redo thread) than the current instance (redo thread) to open the database.

Action: Shut down this instance and start up using a different instance name or redo thread number and retry.

ORA-38857: cannot mark redo thread %s as enabled

Cause: The standby switchover or failover operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread.

Action: Recreate the control file with a larger MAXINSTANCES value.

ORA-38858: cannot mark redo thread %s as enabled

Cause: The open resetlogs or standby activation operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread.

Action: Recreate the control file with a larger MAXINSTANCES value.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ thread ] on the Oracle FAQ.