ORA-00351 recover-to time invalid

Cause: The time specified in a recover-until statement must be after January 1st 1988.

Action: Specify a time after January 1st 1988.


ORA-00352 all logs for thread string need to be archived - cannot enable

Cause: An attempt was made 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-00353 log corruption near block string change string time string

Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.

Action: Perform recovery with a good version of the redo log or do incomplete recovery up to the indicated change or time.


ORA-00354 corrupt redo log block header

Cause: The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message.

Action: Perform recovery with a good version of the redo log or perform cancel-based recovery up to, but not including, the corrupted redo log file. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.


ORA-00355 change numbers out of order

Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one.

Action: Perform recovery with a good version of the log or perform time-based recovery up to the indicated time.


ORA-00356 inconsistent lengths in change description

Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way.

Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time.


ORA-00357 too many members specified for log file, the maximum is string

Cause: An ADD LOGFILE or ADD LOGFILE MEMBER command would result in a log with too many members. The number of members is set when the database is created.

Action: Use fewer log file members.


ORA-00358 Too many file members specified, the maximum is string

Cause: A CREATE or ALTER statement specified too many members in a parenthesised file list.

Action: Specify a number of file members that is within the port-defined limit.


ORA-00359 logfile group string does not exist

Cause: An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist.

Action: Check the configuration of the log files and reissue the command.


ORA-00360 not a logfile member: string

Cause: A file name was given to DROP LOGFILE MEMBER command that is not a part of the database, or which is a datafile.

Action: Supply a valid log file member name.


ORA-00361 cannot remove last log member string for group string

Cause: An attempt has been made to remove the last member of a log file group.

Action: If desired, delete the entire log, by using DROP LOGFILE.


ORA-00362 member is required to form a valid logfile in group string

Cause: A request to drop a log file member was denied because it would remove data required to form a complete log file.

Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE.


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-00364 cannot write header to new log member

Cause: An I/O error occurred when attempting to write the header to a log member that is being added to an existing group.

Action: See accompanying errors. Fix the problem or use another file.


ORA-00365 the specified log is not the correct next log

Cause: The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database.

Action: Find the log that was generated by this copy of the database and give that file name to recovery.


ORA-00366 log string of thread string, checksum error in the file header

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.

Action: Find and install correct version of the log or reset the logs.


ORA-00367 checksum error in log file header

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.

Action: Find the correct file and try again.


ORA-00368 checksum error in redo log block

Cause: The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents.

Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Restore the correct file or reset logs.


ORA-00369 Current log of thread string not useable and other log being cleared

Cause: An attempt to open the 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-00371 not enough shared pool memory

Cause: The SHARED_POOL_SIZE initialization parameter is too small.

Action: Increase the parameter value.


ORA-00372 file string cannot be modified at this time

Cause: An attempt was made to modify the contents of a file that cannot be modified. The file is most likely part of a read-only tablespace but may be in the process of going offline, or the database may be in the process of closing.

Action: Check the status of the file and its tablespace.


ORA-00373 online log version string incompatible with ORACLE version string

Cause: The online log was written by an incompatible version of Oracle. This can occur when the log file was created by either a new or older version of Oracle.

Action: Recover the database with the compatible software, shut it down cleanly, and then restart with current software.


ORA-00374 parameter db_block_size = string invalid; must be a multiple of string in the range [string..string]

Cause: An invalid value was specified for the DB_BLOCK_SIZE parameter.

Action: Adjust the value of the parameter and restart the instance.


ORA-00375 unable to get default db_block_size

Cause: The system was unable to determine the default value for DB_BLOCK_SIZE.

Action: See the accompanying system-specific error. As a workaround, specify the block size in the initialization parameter file.


ORA-00376 file string cannot be read at this time

Cause: An attempt was made to read from a file that is not readable. Most likely the file is offline.

Action: Check the state of the file. Bring it online.


ORA-00377 Frequent backups of file string causing write operation to stall

Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.

Action: Increase the interval between begin hot-backup commands for this file.


ORA-00378 buffer pools cannot be created as specified

Cause: The number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration.

Action: Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools.


ORA-00379 no free buffers available in buffer pool string for block size stringK

Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.

Action: Increase the number of buffers in the specified pool for the specified block size.


ORA-00380 cannot specify db_numberk_cache_size since numberK is the standard block size

Cause: User specified the parameter DB_nK_CACHE_SIZE (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal.

Action: Specify the standard block size cache using DB_CACHE_SIZE (DEFAULT pool) (and DB_RECYCLE_CACHE_SIZE, DB_KEEP_CACHE_SIZE if additional buffer pools are required). Do NOT use the corresponding DB_nK_CACHE_SIZE parameter for the standard block size.


ORA-00381 cannot use both new and old parameters for buffer cache size specification

Cause: User specified one or more of {DB_CACHE_SIZE, DB_RECYCLE_CACHE_SIZE, DB_KEEP_CACHE_SIZE, DB_nK_CACHE_SIZE (where n is one of {2, 4, 8, 16, 32}) AND one or more of {DB_BLOCK_BUFFERS, BUFFER_POOL_KEEP, BUFFER_POOL_RECYCLE}. This is illegal.

Action: Use EITHER the old (pre-Oracle 9.0.0) parameters OR the new ones. Don't specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes.


ORA-00382 string not a valid block size, valid range [string..string]

Cause: User specified a value for DB_nK_CACHE_SIZE where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform.

Action: Remove corresponding parameter from the initialization parameter file and restart the instance.


ORA-00383 DEFAULT cache for blocksize string cannot be reduced to zero

Cause: User attempted to reduce DB_CACHE_SIZE to zero, or attempted to reduce DB_nK_CACHE_SIZE to zero while there were still online tablespaces with block size nK. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set DB_CACHE_SIZE to zero.

Action: Offline any tablespaces with the corresponding block size and then perform the operation again.


ORA-00384 Insufficient memory to grow cache

Cause: The system could not allocate sufficient memory to grow the cache to the specified size.

Action: Attempt a smaller increase in the value of the parameter.


ORA-00390 log string of thread string 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 usable 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 compatibility 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-00392 log string of thread string is being cleared, operation not allowed

Cause: An operation encountered this online log in the middle of being cleared. 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-00393 log string of thread string is needed for recovery of offline datafiles

Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped.

Action: Archive the log and then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.


ORA-00394 online log reused while attempting to archive it

Cause: An attempt was made to reuse an online log file that is being archived.

Action: The online log file has been overwritten; it cannot be archived.


ORA-00395 online logs for the clone database must be renamed

Cause: A clone database open forces log file renaming to avoid overwriting the primary log files.

Action: Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter.


ORA-00396 error string required fallback to single-pass recovery

Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.

Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the new algorithm. This usually requires making more main storage available to the recovery process.


ORA-00397 lost write detected for file string, block string

Cause: The specified block is missing changes that should have been written to disk, indicating a lost write by the file I/O subsystem or volume manager.

Action: Run diagnostic checks on the I/O subsystem and resolve any errors


ORA-00398 abort thread recovery due to reconfiguration

Cause: Global enqueue service reconfiguration occurred during instance/crash recovery.

Action: This is used internally, no action is required.


ORA-00399 corrupt change description in redo log

Cause: A change vector in the redo log failed validation checks.

Action: Do recovery with a good version of the log or do time based recovery up to the indicated time.


ORA-00400 invalid release value string for parameter string

Cause: The release level given for the specified initialization parameter is invalid.

Action: Correct the parameter value in the parameter file and retry.


ORA-00401 the value for parameter string is not supported by this release

Cause: The value specified cannot be supported by this release of the software.

Action: Choose an appropriate value, or remove the parameter value to use the default value.


ORA-00402 database changes by release string cannot be used by release string

Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters.

Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization file.


ORA-00403 string (string) is not the same as other instances (string)

Cause: Another instance has set the COMPATIBLE or COMPATIBLE NO RECOVERY parameters differently than this instance.

Action: Change the parameters of the current instance to match other instances already running.


ORA-00404 Convert file not found: 'string'

Cause: The file used for converting the database from V7 to V8 could not be found.

Action: Verify that the migration process has been started on this database and that the convert file name is accessible.


ORA-00405 compatibility type "string"

Cause: Reporting a type associated with another error.

Action: See the accompanying error.


ORA-00406 COMPATIBLE parameter needs to be string or greater

Cause: The value of the COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Action: Shut down and restart with a higher compatibility setting.


ORA-00407 rolling upgrade from release string.string to string.string is not allowed

Cause: Another instance executing software at a different point release already has the database mounted.

Action: Shut down all instances then restart with the new software.


ORA-00408 parameter string is set to TRUE

Cause: Reporting the parameter that resulted in the compatibility error.

Action: Shut down and restart with a higher compatibility setting.


ORA-00409 COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT

Cause: This is due to upgrading from an older release of Oracle with tablespaces created using automatic segment-space management. To open the database, the COMPATIBLE parameter needs to be set to the specified value or higher.

Action: Shut down and start up with the specified compatibility setting.


ORA-00436 ORACLE is not licensed. Contact Oracle Corp. for assistance

Cause: This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.

Action: Check that Oracle is installed correctly. Then contact Oracle Support Services.


ORA-00437 ORACLE feature is not licensed. Contact Oracle Corp. for assistance

Cause: This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.

Action: Check that Oracle is installed correctly. Then contact Oracle Support Services.


ORA-00438 string Option not installed

Cause: The specified option is not installed.

Action: Either avoid calling the option, or purchase and install the option.


ORA-00439 feature not enabled: string

Cause: The specified feature is not enabled.

Action: Do not attempt to use this feature.


ORA-00443 background process "string" did not start

Cause: The specified process did not start.

Action: Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory.


ORA-00444 background process "string" failed while starting

Cause: Usually due to a bad (or non-existent) background process image.

Action: Get a good background process image.


ORA-00445 background process "string" did not start after string seconds

Cause: The specified process did not start after the specified time.

Action: Ensure that the background did not die and leave a trace file.


ORA-00446 background process started when not expected

Cause: The background process specified started after Oracle was already running.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process, report the message to Oracle Support Services.


ORA-00447 fatal error in background process

Cause: One of the background processes died unexpectedly.

Action: Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST.


ORA-00448 normal completion of background process

Cause: One of the background processes completed normally as requested by the user.

Action: If you are solving a problem, check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle.


ORA-00449 background process 'string' unexpectedly terminated with error string

Cause: A foreground process needing service from a background process has discovered the process died.

Action: Refer to the message code given in the message and the trace file for the foreground and the background processes.


ORA-00470 LGWR process terminated with error

Cause: The Log Writer process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00471 DBWR process terminated with error

Cause: The Database Writer process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00472 PMON process terminated with error

Cause: The Process Monitor process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00473 ARCH process terminated with error

Cause: The Archiver process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00474 SMON process terminated with error

Cause: The System Monitor process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00475 TRWR process terminated with error

Cause: The system tracing process terminated abnormally.

Action: Restart the instance.


ORA-00476 RECO process terminated with error

Cause: The distributed transaction (two-phase commit) recovery process terminated abnormally.

Action: Restart the instance.


ORA-00477 SNP* process terminated with error

Cause: A materialized view refresh process terminated abnormally.

Action: PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle Support Services.


ORA-00478 SMON process terminated due to error string

Cause: SMON was unable to service the requests due to an error in cleanup of resources.

Action: Warm start the instance.


ORA-00480 LCK* process terminated with error

Cause: One Lock process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00481 LMON process terminated with error

Cause: The global enqueue service monitor process terminated abnormally.

Action: Restart the instance.


ORA-00482 LMD* process terminated with error

Cause: A global enqueue service daemon process terminated abnormally.

Action: Restart the instance.


ORA-00483 During shutdown a process abnormally terminated

Cause: One of the background processes did not exit normally at or near the time of shutdown.

Action: Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.


ORA-00484 LMS* process terminated with error

Cause: A global cache service process terminated abnormally.

Action: Warm start the instance.


ORA-00485 DIAG process terminated with error string

Cause: A global diagnostic process died.

Action: Wait for the process to restart.


ORA-00568 Maximum number of interrupt handlers exceeded

Cause: The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed.

Action: Reduce the number of registered interrupt handlers.


ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:

timeouts
file corruption
failed data checks in memory
hardware, memory, or I/O errors
incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.

Action: Report this error to Oracle Support Services after gathering the following information:

events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and databases at the time of the error
any unusual circumstances that occurred before receiving the ORA-00600 message
contents of any trace files generated by the error
the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.


ORA-00601 cleanup lock conflict

Cause: The Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-00602 internal programming exception

Cause: Internal programming exception occurred.

Action: Report this error as a program bug to Oracle Support Services.


ORA-00603 ORACLE server session terminated by fatal error

Cause: An Oracle Server session is in an unrecoverable state.

Action: Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.


ORA-00604 error occurred at recursive SQL level string

Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support Services.


ORA-00606 Internal error code

Cause: A call to deferred UPI functions was made in non-deferred mode.

Action: Contact Oracle Support Services.


ORA-00607 Internal error occurred while making a change to a data block

Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block.

Action: Contact Oracle Support Services.


ORA-00701 object necessary for warmstarting database cannot be altered

Cause: An attempt was made to alter or drop a database object (table, cluster, or index) defined in the control file's bootstrap segment and needed to warm start the database.

Action: Correct the spelling of the object name or remove it from the ALTER or DROP statement.


ORA-00702 bootstrap verison 'string' inconsistent with version 'string'

Cause: The version of the bootstrap data is incompatible with the current version of the software.

Action: Restore a version of the software that is compatible with the datafiles.


ORA-00703 maximum number of row cache instance locks exceeded

Cause: There are not enough row cache enqueues.

Action: Increase the value of the ROW CACHE ENQUEUE parameter and restart the system.


ORA-00704 bootstrap process failure

Cause: Failure in processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem.

Action: Correct the problems mentioned in the other messages. If the problem persists, contact Oracle Support Services.


ORA-00705 inconsistent state during start up; shut down the instance, then restart it

Cause: A previous attempt to start an instance was terminated.

Action: Shut down the instance completely and then restart it.


ORA-00706 error changing format of file 'string'

Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline.

Action: Make the file read-write or bring the file online and set the BLK0_FMTCHG event.


ORA-00816 error message translation failed

Cause: There is an internal error where a routine was unable to translate a message code.

Action: Contact Oracle Support Services.