ODBC error Update to catalog index (Catalog index database) failed after a backup completes on a MMS server in a CASO environment.

Article:TECH189930

Created: 2012-05-29

Updated: 2013-01-04

Article URL http://www.symantec.com/docs/TECH189930

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

ODBC error Update to catalog index (Catalog index database) failed after a backup completes on a MMS server in a CASO environment. Restore selection and certain restore jobs many not run properly when run from certain media servers in the CASO/MMS environment after the ODBC errors have occurred.

Error

Update to catalog index (Catalog index database) failed.

Update to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY
KEY constraint 'PK_CatResourceNameNode'. Cannot insert duplicate key in object 'dbo.CatResourceNameNode'. cat_RecordSet::ExecuteBulkInsert()
e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113) sp_sproc_columns CatResourceNameNodeProc

Environment

Backup Exec 2010 R3

CASO/MMS option.

Backup jobs dispatched from CASO server to MMS servers.

ODBC Events appear on the CASO server after a job is run on a MMS server.

Cause

Catalog indexing corruption occurred on the CASO server.

Manual catalog indexing may have been performed with the Backup Exec service started.

Solution

Run Catrebuildindex on the server reporting ODBC errors with the Backup Exec services stopped.

1. Stop the Backup Exec services

2. Open a cmd prompt to folder "X:\Program Files\Symantec\Backup Exec\".

3. Issue the following command: catrebuildindex -r

NOTE: Catrebuildindex could take anywhere from several minutes to several hours.

4. Start the Backup Exec services.

Supplemental Materials

Source	ETrack
Value	2744758
Description	CASO: Cannot insert duplicate key in object 'dbo.CatResourceNameNode'cat_RecordSet::ExecuteBulkInsert() e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113) sp_sproc_columns CatResourceNameNodeProc