Catalog Errors after Feature Pack 1 and Hotfix 232086 installation
Greetings everyone, 3 days ago I have installed the Feature pack 1 and the hotfix 232086 and also updated the remote agents. Symantec claims that the HotFix 232086 corrects the "cosmetic" error logs (ref. TECH228725, TECH231540, TECH232086) however, these error logs keep appearing every hour. The Backup and Cataloging jobs were performed with success, but, it's very annoying to have more than 130 "cosmetics" alerts in a WKD period. Although, I have already open a support case #09447003 with Symantec Enterprise Support, I thought to place the issue into the forum in case someone else has already deal with this issue Productive environment specs Backup Exec 15 with deduplication option running on a Physical box Windows Server 2012 R2 Std x64 with local SQL instance hosted by SQL 2008R2 Express x64. Any help is much appreciated.BE15 14.2 Catalog Error / ODBC access error
Hi everyone, I have Backup Exec 15 (v14.2) with Feature Pack 1 andHotfix 232086 installed. I'm getting constant ODBC access errors - Event ID 34326 and 34338: Backup Exec Alert: Catalog Error (Server: "BE2012") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Access to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_CatDlmProcessedImage'. Cannot insert duplicate key in object 'dbo.CatDlmProcessedImage'. The duplicate key value is (BE2012). CCatRecordSet::Open r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889) {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Access to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(3629) {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Itried to rebuild the catalog index with catrebuildindex -r , but it does not seems to help at all. Do you have any solution / hotfix for these errors? Regards!