odbc viewer

ODBC catalog errors with Event Ids 34326 and 34338 are generated in BE 15 FP2 periodically

November 26, 2021 – 01:56 pm

Embassy Software - edi to flat flat to edi odbc to edi edi to odbc

After installing Feature Pack 2 for Backup Exec 15, ODBC errors show in the Application hive of the Event Viewer with Event Ids 34326 and 34338. In some cases it has been observed that some backup sets are not expired properly. Stopping the services and running the "CatRebuildIndex -R" masks the issue in some cases but the problem reappears some time later.

Error Message

The following error messages are registered periodically in the Application hive of the Event Viewer on the affected Media Server.

Error AM Backup Exec 34338
Backup Exec Alert: Catalog Error
(Server: "MEDIASERVERNAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Error AM Backup Exec CatErrorHandler Server 34326
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(?, ?, ?, ?, ?, ?, ?)}

Error AM Backup Exec CatErrorHandler Server 34326
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 (MEDIASERVERNAME). CCatRecordSet::Open
r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889)
{CALL CATDLM_New_GetExpirableMedia(?, ?, ?, ?, ?, ?, ?)}

Solution

A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Articles section in this article to obtain the hotfix needed to resolve the issue.
Backup Exec 15 Rev 1180 Feature Pack 4

WORKAROUND:

Stop the Backup Exec Services

Save the attached 3859690.zip file to C:\TEMP on the Backup Exec server.
Extract the zip file to C:\TEMP

Open an Administrator/Elevated Command prompt to C:\TEMP

Run the following command (Case Sensitive)

C:\TEMP\osql -E -S localhost\BKUPEXEC -dbedb -i3859690.sql

Output results:
C:\TEMP>osql -E -S localhost\BKUPEXEC -dbedb -i3859690.sql
1> 2> 3> 4> 5> 6> 7> 1>
C:\TEMP>

Start the Backup Exec Services.

NOTE: The above command is valid if the Backup Exec database (BEDB) is located in the default SQL BKUPEXEC instance name.

If the Backup Exec database BEDB is located in another SQL intance name on the Backup Exec server, for example "SQLEXPRESS" the command would be: osql -E -S localhost\SQLEXPRESS -dbedb -i3859690.sql

If the Backup Exec database is on a remote SQL server "localhost" would need to be changed to the SQL servername.

osql -E -S \>SQL Instance Name>

The attached SQL script can be ran in SQL Management Studio and executed against the Backup Exec BEDB database.

Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
Veritas Technologies LLCcurrently plans to address this issue by way of a patch or hotfix to the current version of the software.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
NOTE: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

Source: www.veritas.com