E-REG-002-025 Region %0s , from directory %1s , has been recovered in a corrupt state: %2s

Explanation

The following example shows how this message is written to the log:
Error: E-REG-002-025: Region 'table_store',
 from directory '/opt/netcool/omnibus/db/NCOMS/',
 has been recovered in a corrupt state:
 Extent statistics mismatch

This error message indicates that the ObjectServer database is corrupted.

In the example error message, Extent statistics mismatch indicates that the NCOMS ObjectServer database is corrupted. The database can become corrupted when an ObjectServer is shut down abnormally, for example, due to a system crash or if the nco_objserv process is stopped.

System action

Not applicable.

User response

Not applicable.

Administrator response

To address the problem indicated by the example error message, you must restore the last uncorrupted ObjectServer.

Note: The restore procedures described below will result in some data loss. Data will be recovered in the state that the Object Server was in when the files were created.
If you have a recent backup of the ObjectServer (made, for example, using the ALTER SYSTEM BACKUP command), use the following steps:
  1. Make a backup of the $NCHOME/omnibus/db/ObjectServer_name directory.
  2. Remove all files from the $NCHOME/omnibus/db/ObjectServer_name directory.
  3. Copy the master_store.tab and table_store.tab files from the backup directory to $NCHOME/omnibus/db/ObjectServer_name.
  4. Start the ObjectServer.
If you do not have a recent backup of the ObjectServer, you can attempt to recover it using the current database files:
  1. Make a backup of the $NCHOME/omnibus/db/ObjectServer_name directory.
  2. In the $NCHOME/omnibus/db/ObjectServer_name directory, identify all files with the suffixes _0 and _1 that are 0 bytes in size and remove the corresponding .chk and .log files.
    For example, in the following database directory, files with the _1 suffix are 0 bytes in size so you must remove master_store_1.chk, master_store_1.log, table_store_1.chk, and table_store_1.log:
    root 126340 Dec 7 08:47 master_store_0.chk
root 126340 Dec 7 08:47 master_store_0.log
root 0 Dec 7 08:47 master_store_1.chk
root 0 Dec 7 08:47 master_store_1.log
root 2822144 Dec 7 08:45 master_store.tab
root 7656 Dec 7 08:47 table_store_0.chk
root 7656 Dec 7 08:47 table_store_0.log
root 0 Dec 7 08:47 table_store_1.chk
root 0 Dec 7 08:47 table_store_1.log
root 3543040 Dec 7 08:45 table_store.tab
  3. Start the ObjectServer.
  4. If the ObjectServer fails to start, use the following steps:
    1. Restore the $NCHOME/omnibus/db/ObjectServer_name directory that you backed up in Step 1.
    2. In the restored $NCHOME/omnibus/db/ObjectServer_name directory, remove any .chk and .log files that you did not remove in Step 2.

      For example, in the database directory in Step 2, you must remove master_store_0.chk, master_store_0.log, table_store_0.chk, and table_store_0.log.

    3. Start the ObjectServer.
  5. If the ObjectServer still does not start, use the following steps:
    1. Remove all .chk and .log files from the $NCHOME/omnibus/db/ObjectServer_name directory.

      Do not remove the table_store.tab and master_store.tab files.

    2. Start the ObjectServer.