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
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
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
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
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
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-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
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
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
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