ORA-00404: Convert file not found: string

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-00403: %s (string) is not the same as other instances (string)

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-00402: database changes by release string cannot be used by release string

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-00401: the value for parameter string is not supported by this release

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-00400: invalid release value string for parameter string

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-00399: corrupt change description in redo log

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-00398: abort thread recovery due to reconfiguration

ORA-00398: abort thread recovery due to reconfiguration

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

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

ORA-00397: instance recovery process terminated with error

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-00396: error string required fallback to single-pass recovery

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-00395: online logs for the clone database must be renamed

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-00394: online log reused while attempting to archive it

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-00393: log string of thread string is needed for recovery of offline datafiles

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

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-00391: All threads must switch to new log format at the same time

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-00390: log string of thread string is being cleared, cannot become current log

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-00386: use_indirect_data_buffers not supported

ORA-00386: use_indirect_data_buffers not supported

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: cannot enable Very Large Memory with new buffer cache parameters

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-00384: Insufficient memory to grow cache

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-00383: DEFAULT cache for blocksize string cannot be reduced to zero

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_lamp;lt;lamp;nbsp;nlamp;gt;K_cache_size to zero while there were still online tablespaces with blocksize lamp;lt;lamp;nbsp;nlamp;gt;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-00382: %s not a valid block size, valid range (string..string(

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-00381: cannot use both new and old parameters for buffer cache size specification

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-00380: cannot specify db_stringk_cache_size since stringK is the standard block size

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-00379: no free buffers available in buffer pool string for block size stringK

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-00378: buffer pools cannot be created as specified

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 or number of lru latches or configure smaller buffer pools.

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

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-00376: file string cannot be read at this time

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-00375: unable to get default db_block_size

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-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range (string..string(

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-00373: online log version string incompatible with ORACLE version string

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-00372: file string cannot be modified at this time

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-00371: not enough shared pool memory, should be atleast string bytes

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-00370: potential deadlock during kcbchange operation

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-00369: Current log of thread string not useable and other log being cleared

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-00368: checksum error in redo log block

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-00367: checksum error in log file header

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-00366: log string of thread string, checksum error in the file header

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-00365: the specified log is not the correct next log

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

ORA-00364: cannot write header to new log member

Cause: An i or 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-00363: log is not the archived version

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-00362: member is required to form a valid logfile in group string

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-00361: cannot remove last log member string for group string

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-00360: not a logfile member: string

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-00359: logfile group string does not exist

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-00358: Too many file members specified, the maximum is string

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-00357: too many members specified for log file, the maximum is string

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-00356: inconsistent lengths in change description

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-00355: change numbers out of order

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-00354: corrupt redo log block header

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-00353: log corruption near block string change string time string

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-00352: all logs for thread string need to be archived - cannot enable

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-00351: recover-to time invalid

ORA-00351: recover-to time invalid

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

Action: Specify a time after January 1st 1988.

ORA-00350: log string of instance string (thread string) needs to be archived

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-00349: failure obtaining block size for string

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-00348: single-process redo failure. Must abort instance

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-00347: log string of thread string, expected block size string doesn t match string

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-00346: log member marked as STALE

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-00345: redo log write error block string count string

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 or incomplete recovery.

ORA-00344: unable to re-create online log string

ORA-00344: unable to re-create online log string

Cause: An I or 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 or device as indicated by accompanying errors.

ORA-00343: too many errors, log member closed

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-00342: archived log does not have expected resetlogs SCN string

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.