Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

Erreurs ORA-00321 à ORA-00600 Cause et Action

ORA-00321 ORA-00321: log string of thread string, cannot update log file header
Cause Cannot write to the log file.
Action Restore the access to the file.

ORA-00322 ORA-00322: log string of thread string is not current copy
Cause Check of log file header at database open found that an online log appears to be an incorrectly restored backup.
Action Restore correct file or reset logs.

ORA-00323 ORA-00323: Current log of thread string 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-00324 ORA-00324: log file 'string' translated name 'string' too long, string characters exceeds string limit
Cause the translated name for a log file is too long.
Action Choose a untranslated name that yields a shorter translated name.

ORA-00325 ORA-00325: archived log for thread string, wrong thread # string in header
Cause The archived log is corrupted or for another thread. Can not use the log for applying redo.
Action Find correct archived log.

ORA-00326 ORA-00326: log begins at change string, need earlier change string
Cause The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo.
Action Find correct archived log.

ORA-00327 ORA-00327: log string of thread string, physical size string less than needed string
Cause A log file has shrunk in size. This is likely to have been caused by operator or operating system error.
Action Restore the log file from backup. If backup is not available, drop this log and re-create. If the database was shut down cleanly, no further action should be required; otherwise incomplete recovery may be required.

ORA-00328 ORA-00328: archived log ends at change string, need later change string
Cause The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo.
Action Find correct archived log.

ORA-00329 ORA-00329: archived log begins at change string, need change string
Cause The archived log is not the correct log. An earlier log is needed.
Action Restore the correct log file.

ORA-00330 ORA-00330: archived log ends at change string, need change string
Cause The archived log is not the correct log. A later log is needed.
Action Restore the correct log file.

ORA-00331 ORA-00331: log version string incompatible with ORACLE version string
Cause The log was written by incompatible version of Oracle.
Action Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00332 ORA-00332: archived log is too small - may be incompletely archived
Cause The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver.
Action Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived.

ORA-00333 ORA-00333: redo log read error block string count string
Cause An IO error occurred while reading the log described in the accompanying error.
Action Restore accessibility to file, or get another copy of the file.

ORA-00334 ORA-00334: archived log: 'string'
Cause Reporting filename for details of another error
Action See associated error messages

ORA-00335 ORA-00335: online log string: No log with this number, log does not exist
Cause Reporting filename for details of another error
Action See associated error messages

ORA-00336 ORA-00336: log file size string blocks is less than minimum string blocks
Cause The log file size as specified in create database is too small.
Action Increase the log file size.

ORA-00337 ORA-00337: log file 'string' does not exist and no size specified
Cause An attempt to add a log found neither an existing file nor a size for creating the file.
Action Specify a size for the log file.

ORA-00338 ORA-00338: log string of thread string is more recent than controlfile
Cause The controlfile change sequence number in the log file is greater than the number in the controlfile. This implies that the wrong controlfile is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the controlfile change sequence number until it is great enough.
Action Use the current controlfile or do backup controlfile recovery to make the controlfile current. Be sure to follow all restrictions on doing a backup controlfile recovery.

ORA-00339 ORA-00339: archived log does not contain any redo
Cause The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log.
Action Restore the correct log file.

ORA-00340 ORA-00340: IO error processing online log string of thread string
Cause An IO error occurred on the named online log.
Action Restore accessibility to file, or restore file from backup.

ORA-00341 ORA-00341: log string of thread string, wrong log # string in header
Cause The internal information in an online log file does not match the controlfile.
Action Restore correct file or reset logs.

ORA-00342 ORA-00342: archived log does not have expected resetlogs SCN string
Cause Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo.
Action Supply the correct log file.

ORA-00343 ORA-00343: too many errors, log member closed
Cause The maximum number of errors on this log member has been exceeded.
Action Correct the underlying problem by referring to the other error messages found with this one.

ORA-00344 ORA-00344: unable to re-create online log 'string'
Cause An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.
Action Correct the file/device as indicated by accompanying errors.

ORA-00345 ORA-00345: redo log write error block string count string
Cause An IO error has occurred while writing the log
Action Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.

ORA-00346 ORA-00346: log member marked as STALE
Cause A log file member no longer is complete.
Action Correct the underlying problem by referring to the other error messages found with this one.

ORA-00347 ORA-00347: log string of thread string, expected block size string doesn't match string
Cause On header read the blocksize indicated in the control file did not match the blocksize contained in the log file.
Action Restore correct file or reset logs.

ORA-00348 ORA-00348: single-process redo failure. Must abort instance
Cause A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation.
Action Shutdown abort and warmstart the database.

ORA-00349 ORA-00349: failure obtaining block size for 'string'
Cause The operating system was unable to determine the blocksize for the given filename.
Action Consult the accompanying error message, and correct the device or specify another filename.

ORA-00350 ORA-00350: log string of instance string (thread string) needs to be archived
Cause The command cannot be done because the log has not been archived, and media recovery has been enabled.
Action Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files.

ORA-00351 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 ORA-00352: all logs for thread string 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-00353 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 Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.

ORA-00354 ORA-00354: corrupt redo log block header
Cause The block header on the redo block indicated by the accompanying error, is not reasonable.
Action Do 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.

ORA-00355 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 Do recovery with a good version of the log or do time based recovery up to the indicated time.

ORA-00356 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 Do recovery with a good version of the log or do time based recovery up to the indicated time.

ORA-00357 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 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 ORA-00359: logfile group string does not exist
Cause An add logfile member or drop logfile request specified a logfile group number that does not exist.
Action Check the configuration of the log files and reissue the command.

ORA-00360 ORA-00360: not a logfile member: string
Cause A filename was given to drop logfile member that is not a part of the database, or which is a data file.
Action Supply a valid logfile member name.

ORA-00361 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 ORA-00362: member is required to form a valid logfile in group string
Cause A request to drop a logfile member was denied because it would remove data required to form a complete logfile.
Action If desired, delete the entire log (after archiving if required), by using DROP LOGFILE;

ORA-00363 ORA-00363: log is not the archived version
Cause d 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 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 problem or use another file.

ORA-00365 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 filename to recovery.

ORA-00366 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 log or reset logs.

ORA-00367 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 ORA-00368: checksum error in redo log block
Cause The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.
Action Restore correct file or reset logs.

ORA-00369 ORA-00369: Current log of thread string 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-00370 ORA-00370: potential deadlock during kcbchange operation
Cause Error code used internally by software. Should never be reported
Action Treat as internal error. See error 600.

ORA-00371 ORA-00371: not enough shared pool memory, should be atleast string bytes
Cause Init.ora parameter shared_pool_size is too small
Action Increase the parameter value

ORA-00372 ORA-00372: file string cannot be modified at this time
Cause attempting 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 ORA-00373: online log version string incompatible with ORACLE version string
Cause The online log was written by incompatible version of Oracle. 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, then restart with current software.

ORA-00374 ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
Cause invalid value for db_block_size parameter
Action adjust parameter and restart

ORA-00375 ORA-00375: unable to get default db_block_size
Cause the system was unable to determine the default db_block_size
Action see accompanying system specific error. As a workaround, specify the blocksize in the INIT.ORA file.

ORA-00376 ORA-00376: file string cannot be read at this time
Cause attempting 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 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 ORA-00378: buffer pools cannot be created as specified
Cause Either 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 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 ORA-00380: cannot specify db_stringk_cache_size since stringK 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 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), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal.
Action Use EITHER the old (pre-Oracle_8.2) 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. Cache advisory can only be enabled with the new cache parameters.

ORA-00382 ORA-00382: %s 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 "init.ora" file and restart the instance.

ORA-00383 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 to reduce db_K_cache_size to zero while there were still online tablespaces with blocksize K. 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 blocksize and then perform the operation again.

ORA-00384 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-00385 ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
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 use_indirect_data_buffers is set to TRUE. This is illegal.
Action Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters.

ORA-00390 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 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 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-00392 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 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 then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.

ORA-00394 ORA-00394: online log reused while attempting to archive it
Cause It has been detected that an online log that is being archived has been reused
Action Cannot archive the logfile anymore since it has been overwritten

ORA-00395 ORA-00395: online logs for the clone database must be renamed
Cause A clone database open forces logfile renaming to avoid overwriting the primary logfiles
Action Rename the logfiles manually or using the log_file_name_convert initialization parameter

ORA-00396 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 two-pass algorithm. This usually requires making more main memory available to the recovery process.

ORA-00397 ORA-00397: instance recovery process terminated with error
Cause The foreground process doing instance recovery died.
Action Check the foreground trace file for the cause of recovery failure.

ORA-00398 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 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 ORA-00400: invalid release value string for parameter string
Cause The release level given for the specified init parameter is invalid.
Action Correct the parameter value in the parameter file and retry.

ORA-00401 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 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 init file.

ORA-00403 ORA-00403: %s (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 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 filename is accessable.

ORA-00405 ORA-00405: compatibility type "string"
Cause Reporting a type associated with another error.
Action See accompanying error

ORA-00406 ORA-00406: COMPATIBLE parameter needs to be string or greater
Cause 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 Shutdown and startup with a higher compatibility setting.

ORA-00407 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 Shutdown all instances then startup with the new software.

ORA-00408 ORA-00408: parameter string is set to TRUE
Cause Reporting the parameter that resulted in the compatibility error.
Action Shutdown and startup with a higher compatibility setting.

ORA-00409 ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
Cause This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value.
Action Shutdown and startup with the specified compatibility setting.

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

ORA-00438 ORA-00438: %s Option not installed
Cause The specified option is not installed.
Action Purchase and install the option.

ORA-00439 ORA-00439: feature not enabled: string
Cause The specified feature is not enabled.
Action Do not attempt to use this feature.

ORA-00443 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 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 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 ORA-00446: background process started when not expected
Cause The background process specified started up AFTER the RDBMS was already running.
Action If nobody at your site started the process, then this is an internal error.

ORA-00447 ORA-00447: fatal error in background process
Cause One of the background processes died unexpectedly.
Action Warm start the system.

ORA-00448 ORA-00448: normal completion of background process
Cause One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit.
Action Warm start the system.

ORA-00449 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 Consult the error code, and the trace file for the process.

ORA-00450 ORA-00450: background process 'string' did not start
Cause The specified process did not start.
Action Consult the error code, and the trace file for the process.

ORA-00470 ORA-00470: LGWR process terminated with error
Cause The log writer process died
Action Warm start instance

ORA-00471 ORA-00471: DBWR process terminated with error
Cause The database writer process died
Action Warm start instance

ORA-00472 ORA-00472: PMON process terminated with error
Cause The process cleanup process died
Action Warm start instance

ORA-00473
ORA-00473: ARCH process terminated with error
Cause The archive process died
Action Warm start instance

ORA-00474 ORA-00474: SMON process terminated with error
Cause The system cleanup process died
Action Warm start instance

ORA-00475 ORA-00475: TRWR process terminated with error
Cause The system tracing process died
Action Warm start instance

ORA-00476 ORA-00476: RECO process terminated with error
Cause The distributed transaction (two-phase commit) recovery process died.
Action Warm start instance

ORA-00477 ORA-00477: SNP* process terminated with error
Cause A materialized view refresh process died
Action PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle support.

ORA-00478 ORA-00478: SMON process terminated due to error string
Cause SMON was unable to service the requests due to error in cleanup of resources
Action Warm start instance

ORA-00479 ORA-00479: RVWR process terminated with error string
Cause The RVWR process died
Action Warm start instance

ORA-00480 ORA-00480: LCK* process terminated with error
Cause A system lock process died
Action Warm start instance

ORA-00481 ORA-00481: LMON process terminated with error
Cause The global enqueue service monitor process died
Action Warm start instance

ORA-00482 ORA-00482: LMD* process terminated with error
Cause A global enqueue service daemon process died
Action Warm start instance

ORA-00483 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 shutdown abort.

ORA-00484 ORA-00484: LMS* process terminated with error
Cause A global cache service process died
Action Warm start instance

ORA-00485 ORA-00485: DIAG process terminated with error string
Cause A global diagnostic process died
Action Wait for process to restart

ORA-00486 ORA-00486: ASMB process terminated with error
Cause An ASM background process died.
Action Warm start instance. Also check that ASM Instance is running.

ORA-00487 ORA-00487: CTWR process terminated with error
Cause The change tracking process died
Action Warm start instance

ORA-00488 ORA-00488: RBAL process terminated with error
Cause The ASM rebalance coordinator process died.
Action Warm start instance.

ORA-00489 ORA-00489: ARB* process terminated with error
Cause An ASM rebalance worker process died.
Action Wait for process to restart.

ORA-00568 ORA-00568: Maximum number of interrupt handlers exceeded
Cause User specified too many ^c handlers
Action Remove some old handlers.

ORA-00600 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. This indicates that a process has encountered an exceptional condition.
Action Report as a bug - the first argument is the internal error number

Partager cette page

Repost 0
Published by