In NetBackup 7.5 through 188.8.131.52, the Sybase ASA(dbsrv11) (Adaptive Server Anywhere) database may not start properly, exiting with an assertion failure error: 200130, 200131, 200106 or 108701. When this happens, it is an indication of database corruption and NetBackup will no longer function until corrective action is taken.
An example of the error, from the nbemm log at DebugLevel=1:
04/20/13 01:54:45.195 [Debug] NB 51216 321 PID:2548 TID:4 File ID:111 [No context] 1 [DbConnection::Execute] SQL - retval=DB_ERROR_SQLGeneralError(2007087) retdal=-1 native=<-301> sqlerror=<[Sybase][ODBC Driver][SQL Anywhere] Internal database error *** ERROR *** Assertion failed: 108701[NBDB](184.108.40.20653)
Freeing page not in index -- transaction rolled back> sqlstate=<xxxxx>
The correlating error in the /usr/openv/db/log/server.log [UNIX] or <install_path>\NetBackupDB\log\server.log [Windows] file will appear similar to the following:
E. 04/20 01:54:45. *** ERROR *** Assertion failed: 108701[NBDB] (220.127.116.1153) Freeing page not in index I. 04/20 01:54:45. Connection terminated abnormally
This issue has been identified as Sybase defect, CR Number 689696. Additional information is available at the following Sybase link:
A catalog recovery will need to be completed in order to recover from any database corruption caused by this issue. Directions for recovery of the NetBackup catalog can be found in either the disaster recovery email, if configured in the Hot Catalog backup policy, or via the procedure enumerated in the NetBackup Troubleshooting Guide, version 7.5 (Related Article linked below) in Chapter 5, Disaster Recovery.
The formal resolution for this issue (Etrack 3165091) is inlcuded in the following release:
- NetBackup 7.5 Maintenance Release 5 (18.104.22.168)
NetBackup 22.214.171.124 is available via the Related Article linked below. This version contains an updated version of Sybase ASA which includes a resolution for the known issue.
Symantec strongly recommends the following best practices:
1. Always perform a full DR backup prior to making any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.
3. Perform periodic "test" restores.
4. Subscribe to technical articles.
How to Subscribe to Email Notification:
Directly to this Article:
Subscribe to this article by clicking on the Subscribe via email link on this page to receive notification when this article is updated with Release Information.
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alert, you may subscribe via email and/or RSS using the links provided at the following page:
All multicore platforms, both Unix and Windows may be impacted by this issue.
NetBackup versions impacted:
- 7.5 GA