recovery.
ORA-00366: log string of thread string, checksum error in the file header
原因： 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 解决： Find and install correct version of log or reset logs. ORA-00367: checksum error in log file header
原因： 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 解决： Find the correct file and try again.
ORA-00368: checksum error in redo log block
原因： The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.
解决： Restore correct file or reset logs.
ORA-00369: Current log of thread string not useable and other log being cleared
原因： 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. 解决： 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: potential deadlock during kcbchange operation
原因： Error code used internally by software. Should never be reported 解决： Treat as internal error. See error 600.
ORA-00371: not enough shared pool memory, should be atleast string bytes 原因： Init.ora parameter shared_pool_size is too small 解决： Increase the parameter value
ORA-00372: file string cannot be modified at this time
原因： 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.
解决： check the status of the file and its tablespace
ORA-00373: online log version string incompatible with ORACLE version string
原因： 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.
解决： Recover the database with the compatible software, shut it down cleanly, then restart with current software.
ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
原因： invalid value for db_block_size parameter 解决： adjust parameter and restart
ORA-00375: unable to get default db_block_size
原因： the system was unable to determine the default db_block_size
解决： see accompanying system specific error. As a workaround, specify the blocksize in the INIT.ORA file.
ORA-00376: file string cannot be read at this time
第26页
原因： attempting to read from a file that is not readable. Most likely the file is offline. 解决： Check the state of the file. Bring it online
ORA-00377: Frequent backups of file string causing write operation to stall
原因： 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.
解决： Increase the interval between begin hot-backup commands for this file. ORA-00378: buffer pools cannot be created as specified
原因： Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration.
解决： 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
原因： All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.
解决： Increase the number of buffers in the specified pool for the specified block size ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard block size
原因： 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.
解决： 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
原因： 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. 解决： Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don\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: %s not a valid block size, valid range [string..string]
原因： 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.
解决： Remove corresponding parameter from the \ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero
原因： User attempted to reduce db_cache_size to zero, or attempted to to reduce db_
解决： Offline any tablespaces with the corresponding blocksize and then perform the operation again.
ORA-00384: Insufficient memory to grow cache
第27页
原因： The system could not allocate sufficient memory to grow the cache to the specified size. 解决： Attempt a smaller increase in the value of the parameter.
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
原因： 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.
解决： Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters. ORA-00386: use_indirect_data_buffers not supported
原因： The system could not allocate sufficient memory to grow the cache to the specified size. 解决： Attempt a smaller increase in the value of the parameter.
ORA-00390: log string of thread string is being cleared, cannot become current log
原因： 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.
解决： 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
原因： 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.
解决： 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
原因： 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.
解决： 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
原因： 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.
解决： 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: online log reused while attempting to archive it
原因： It has been detected that an online log that is being archived has been reused 解决： Cannot archive the logfile anymore since it has been overwritten ORA-00395: online logs for the clone database must be renamed
原因： A clone database open forces logfile renaming to avoid overwriting the primary logfiles 解决： Rename the logfiles manually or using the log_file_name_convert initialization parameter ORA-00396: error string required fallback to single-pass recovery
原因： The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.
解决： Correct the cause of the indicated error (also recorded) so that future instance or crash
第28页
recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process.
ORA-00397: instance recovery process terminated with error 原因： The foreground process doing instance recovery died.
解决： Check the foreground trace file for the cause of recovery failure. ORA-00398: abort thread recovery due to reconfiguration
原因： Global enqueue service reconfiguration occurred during instance/crash recovery. 解决： This is used internally, no action is required. ORA-00399: corrupt change description in redo log
原因： A change vector in the redo log failed validation checks.
解决： 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
原因： The release level given for the specified init parameter is invalid. 解决： Correct the parameter value in the parameter file and retry.
ORA-00401: the value for parameter string is not supported by this release 原因： The value specified cannot be supported by this release of the software.
解决： 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
原因： Changes have been made to the database that require a newer software release or that violate the compatibility parameters.
解决： Use a version of the software that can understand the changes or relax the compatibility requirements in the init file.
ORA-00403: %s (string) is not the same as other instances (string)
原因： Another instance has set the compatible or compatible no recovery parameters differently than this instance.
解决： Change the parameters of the current instance to match other instances already running. ORA-00404: Convert file not found: \
原因： The file used for converting the database from V7 to V8 could not be found.
解决： Verify that the migration process has been started on this database and that the convert filename is accessable.
ORA-00405: compatibility type \
原因： Reporting a type associated with another error. 解决： See accompanying error
ORA-00406: COMPATIBLE parameter needs to be string or greater
原因： 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.
解决： Shutdown and startup with a higher compatibility setting.
ORA-00407: rolling upgrade from release string.string to string.string is not allowed
原因： Another instance executing software at a different point release already has the database mounted.
解决： Shutdown all instances then startup with the new software. ORA-00408: parameter string is set to TRUE
第29页
原因： Reporting the parameter that resulted in the compatibility error. 解决： Shutdown and startup with a higher compatibility setting.
ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
原因： 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.
解决： Shutdown and startup with the specified compatibility setting.
ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance 原因： ORACLE feature is not licensed. 解决： Contact ORACLE for assistance. ORA-00438: %s Option not installed
原因： The specified option is not installed. 解决： Purchase and install the option. ORA-00439: feature not enabled: string 原因： The specified feature is not enabled. 解决： Do not attempt to use this feature.
ORA-00443: background process \ 原因： The specified process did not start.
解决： Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory.
ORA-00444: background process \
原因： Usually due to a bad (or non-existent) background process image. 解决： Get a good background process image.
ORA-00445: background process \ 原因： The specified process did not start after the specified time. 解决： Ensure that the background did not die and leave a trace file. ORA-00446: background process started when not expected
原因： The background process specified started up AFTER the RDBMS was already running. 解决： If nobody at your site started the process, then this is an internal error. ORA-00447: fatal error in background process
原因： One of the background processes died unexpectedly. 解决： Warm start the system.
ORA-00448: normal completion of background process
原因： One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit. 解决： Warm start the system.
ORA-00449: background process \
原因： A foreground process needing service from a background process has discovered the process died.
解决： Consult the error code, and the trace file for the process. ORA-00450: background process \ 原因： The specified process did not start.
解决： Consult the error code, and the trace file for the process.
第30页