Forum Discussion

Borealis's avatar
Borealis
Level 4
10 years ago

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.

 

 

12 Replies

  • Hi VJware and thank you for the reply,

     

    YES, we do have the exact same error message (event ID 34326) with the one described in TECH231540 The only difference is the bold word.

    YES, we do perform MS Exchange (2010) backups

    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(?,?,?,?,?,?,?)}  

     For more information, click the following link:
    http://entced.symantec.com/entt?product=BE&module=eng-event&error=V-379-34326&build=retail&version=14.2.1180.1162&language=EN&os=Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3

    YES, I have tried the catrebuildindex -r. Rebuild completed with success but that didn't resolved my case.

    Symantec Enterpise Support Service at the initial session has run a couple of other CLI commands with success but again nothing have changed regarding my case.

    Alerts are logged every approx 1 hour in pairs and for every alerting pair there're 2 application events logs (34326, 34338).

  • Do you have the exact same error message as mentioned in the above KBs ?

    Have you tried running catrebuildindex -r ?