Validating the Infrastructure Management database

The database validation process will indicate whether there is database corruption, such as table corruption or Index invalid page.

The amount of time required to validate the database depends on the amount of RAM available on the computer hosting the database, the database size, and the cache size specified for the server. (It is recommended to have 80% of memory available for the database on a separate computer.)

Any disturbance on the computer, such as other processes or virus checkers running against the CPU or hard disk, can slow the process down.

Note

You can validate the database on the local computer running the BMC TrueSight Infrastructure Management Server, or on a different computer, without shutting down the BMC TrueSight Infrastructure Management Server.

Validating the database without stopping the BMC TrueSight Infrastructure Management Server services or processes

  1. Archive the database
    # pw database archive 
  2. Copy the storm_hostName.db database, and the pronto.log transaction log from the installationDirectory/pw/dbarchive directory into a temporary directory, such as \DB_BackUp.
  3. Rename the storm_hostName.db file in the temporary directory to backup.db.
  4. If the operating system is Solaris, set the environment to run SAP SQL Anywhere commands:
    # cd /usr/pw/pronto/bin  
    # ../.tmprofile
    command.
  5. From a command prompt, start the database by entering the following command:
    # dbeng11 -qi "<temporary_location>\backup.db" -o "<temporary_directory>\databaseoutput.log"
  6. Validate the database by entering the following command:
    # dbvalid -c "uid=dba;pwd=pronet;eng=backup" > "<temporary_directory>\dbValidateOutput.log"
  7. Open the dbValidateOutput.log file and check the last line of the file.
    If there are no database errors during validation, the dbValidateOutput.log file ends with a "No errors reported" message.
    If validation fails and error messages are displayed, to validate the error messages, see Validate Database Failure.
  8. Stop the database by entering the following command:
    # dbstop -c "uid=dba;pwd=pronet;eng=backup"
  9. Delete the contents of the <temporary_directory> directory.

Validating the database and stopping the BMC TrueSight Infrastructure Management Server services or processes

  1. From a command line, stop all the BMC TrueSight Infrastructure Management Server processes or services:
    # pw sys stop 
  2. Verify that all the BMC TrueSight Infrastructure Management Server processes or services have stopped:
    # pw p l 
  3. Start only the database process:
    # pw p s dbsrv
  4. Validate the database and redirect the output to the log file:
    # pw database validate > dbValidateOutput.log
  5. Open the dbValidateOutput.log file and check the last line of the file.

    If there are no database errors during validation, the dbValidateOutput.log file ends with a "No errors reported" message.

    If error messages are displayed, see Validate Database Failure.

  6. Restart all the BMC TrueSight Infrastructure Management Server processes or services:
    pw sys start

Validating the database on a temporary host computer without stopping the BMC TrueSight Infrastructure Management Server services or processes

Assumptions:

  • There are two computers, Computer A and Computer B, both running the same version of Infrastructure Management.
  • Computer A is the computer on which your BMC TrueSight Infrastructure Management Server services or processes are running.
  • Computer B is a temporary host on which you will validate a copy of the database. Using a temporary host for validation prevents having to stop the BMC TrueSight Infrastructure Management Server services.

To validate the database on a temporary host computer without stopping the BMC TrueSight Infrastructure Management Server services or processes:

On Computer A

  1. Archive the database:
    # pw database archive
  2. Copy the storm_hostnameA.db> database and the pronto.log transaction log, from the installationDirectory/pw/dbarchive directory to Computer B's SAP SQL Anywhere directory, installationDirectory/pw/sybase/.

On Computer B

  1. Rename the database file in the Sybase directory from strom_hostnameA.db to storm_hostnameB.db.
  2. Start the database service:
    # pw p s dbsrv
  3. Validate the database:
    # pw database validate 
  4. Open the dbValidateOutput.log file and check the last line of the file.
    If there are no database errors during validation, the dbValidateOutput.log file ends with a "No errors reported" message. 
    If error messages are displayed, see Validate Database Failure.
  5. Stop the database:
    # pw p e dbsrv 
  6. Restart all the services:
    # pw sys start 

Validate Database Failure

If there are database errors, and the validate operation fails, the following error messages are displayed:

Error: Orphaned page (000a0cfb) found in database file "/usr/pw/sybase/storm_< hostname >.db"

Error: Assertion failed

If these error messages are displayed, contact BMC Software Customer Support at 800 537 1813 (United States or Canada) or call your local BMC Software Customer Support center.

Was this page helpful? Yes No Submitting... Thank you

Comments