Catalog Error - ODBC access error. Possible lost connection to database or unsuccessful access to ca

Question

Catalog Error - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. V-280-2003 When I do the restore operation I cannot browse the backup set. I get the following error: Backup Exec Alert: Catalog Error Message: ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. V-280-2003 I installed all required Feature Packs but it is not fixed. The last Feature Pack that I installed is 20.5

thompsjh · Answer

I'm experiencing the same issue and error message. These are the three Events from the Application Log.

Log Name: Application
Source: Backup Exec CatErrorHandler Server
Event ID: 34326
Task Category: None
Level: Error
Keywords: Classic

Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount
r:\orcas\1188.2718r\becat\segodbc\seg_odbc.cpp(3631)
{CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)}

For more information, click the following link:
https://telemetry.community.veritas.com/entt?product=BE&module=eng-event&error=V-379-34326&build=retail&version=20.0.1188.2718&language=EN&os=Windows_V-6.1.7601_SP-1.0_PL-0x2_SU-0x112_PT-0x3

Log Name: Application
Source: Backup Exec CatErrorHandler Server
Event ID: 34326
Task Category: None
Level: Error
Keywords: Classic

Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount
r:\orcas\1188.2718r\becat\segodbc\seg_odbc.cpp(3631)
{CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)}

For more information, click the following link:
https://telemetry.community.veritas.com/entt?product=BE&module=eng-event&error=V-379-34326&build=retail&version=20.0.1188.2718&language=EN&os=Windows_V-6.1.7601_SP-1.0_PL-0x2_SU-0x112_PT-0x3

Log Name: Application
Source: Backup Exec
Event ID: 34338
Task Category: None
Level: Error
Keywords: Classic

Backup Exec Alert: Catalog Error
(Server: "NAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.

For more information, click the following link:
https://telemetry.community.veritas.com/entt?product=BE&module=eng-event&error=V-379-34338&build=retail&version=20.0.1188.2718&language=EN&os=Windows_V-6.1.7601_SP-1.0_PL-0x2_SU-0x112_PT-0x3

steve-young · Answer

You would have to go into the Application Event Log and look at the details of the Event.The details of the Event will determine the cause and possible solution.&nbsp;&nbsp;

rampant · Answer

we are having identical problem and errors in the event log. When doing a backup of Exchange, it dies on the catalog. The backup set doesn't appear under the machine, but it does appear in the list of backup sets under the Storage. If we try to catalog that file it does immediately with the ODBC errors and the detail shown above, ex:

Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount
r:\orcas\1188.2718r\becat\segodbc\seg_odbc.cpp(3631)

We've done the set trustworthy thing. Changed out catalog options (unchecking things), matched what we had in our older server, running out of options.

rogrubin · Answer

I think you probably best served by opening a support case.It sounds like that there might be an issue with the catalog folder at the same time you mentioned "old server" which indicates that you might have migrated the data to a new server which could be another reason of the above error.If you speak with support and the issue started post server migration, please mention this as this will help the technician to better understand your issue and provide you with a solution.

Forum Discussion

Catalog Error - ODBC access error. Possible lost connection to database or unsuccessful access to ca

Related Content

Catalog Backup - unsuccessful

Onprem Netbackup to AWS S3 Connection Err

unsuccessful cluster failover occured because of nic faulted

Unsuccessful BMR backup

Direct connect between 5200 and 5220 -- possible??