GENERAL ERROR: The NBDB database transaction log (NBDB.log) may become too large or corrupt for proper NetBackup operation.
Problem occurs when NetBackup Relational Database Manager service failed to start. When running following command shows Database unavailable.
Database [NBDB] is not available.
There may be errors reported by the ASA database engine in the /usr/openv/db/log/server.log file as well. These errors would look similar to the following:
Error: Cannot open transaction log file -- Can't use log file "/usr/openv/db/data/NBDB.log" since it is shorter than expected
Problem occurs when transaction log for the ASA database that runs under NetBackup becomes corrupt or too large for proper operation. For example, in a file system that limits file size to 2GB, the transaction log will be truncated and corrupt once it reaches the 2Gb limit. The transaction log is truncated during online catalog backup, but it might be possible that catalog backups did not take place to prevent the log from growing too large.
- Catalog backups and regular backups can hang.
- Operator is unable to cancel queued jobs.
- The EMM database does not come back up after restarting NetBackup
1. Stop NetBackup if it is not already stopped:
2. To add the necessary environment variables to your shell, run the command:
If BMR is used, force recovery of the BMR database:
Note: If the command dbsrv11 -f /usr/openv/db/data/NBDB.db should fail with the error " A database server with that name has already started ", please check /usr/openv/tmp and rename the sqlany directory, and all the sqlany files. Restart recovery as per step 6 above and the dbsrv11 -f /usr/openv/db/data/NBDB.db should work.
Note: the NBDB.log will not be created until any transaction actually occurs, such as NetBackup making connection to the EMM DB:
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):