Managing NerveCenter - Managing the Database - Troubleshooting: Managing the NerveCenter Database -
ncdb2html.pl      Managing Management Information Bases (MIBs)

Troubleshooting: Managing the NerveCenter Database

The following list contains some common database problems that users encounter.

The server shut down gracefully, but event log said that the database was not found. Where did the updates to the database go?

Problem: The database was not available (if, for example, the network connection between the NerveCenter server and the SQL database went down) so NerveCenter couldn't write the changes to the database.

Solution: NerveCenter serializes the database information if the database is not available. The file is date_time.asc in the db directory. While the server is still shut down, import the contents of the file when the database is available again. See Restoring the Database.

Running SerializeDB from the command line keeps failing

Problem: The paths to your databases or the serialized files are not specified correctly.

Solution: If you are not in the db directory, make sure you include the paths in the command line options where appropriate. See Backing up the Database Using the SerializeDB Application or Restoring the Database from the Command Line.

SerializeDB won't work from the application or the command line

Problem: You must be an Administrator or root to run SerializeDB.

Solution: Make sure you are logged in correctly. See Managing the Database.

The data in the database is not what was imported from the serialized file

Problem: The server was running when you imported the file. The server overwrote the data you imported when it saved its changes to the database.

Solution: When you import or export data, make sure the server is not running. If it was, you must shut it down and reimport or export the data. See Backing up the Database or Restoring the Database.