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
Category Archives: ORA Database Error Messages
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