Catalog Error "ODBC access error" after an upgrade of Backup Exec

Problem

After an Upgrade from Backup Exec for Windows 11d to Backup Exec 12 or 12.5 Catalog Error "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" when the Backup Exec Database (BEDB) is located on a remote SQL Server or not in the default named SQL (BKUPEXEC) Instance.

Error Message

Event Viewer Application Log:

Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Description:
Access to catalog index (Catalog index database) failed.
Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
procedure 'UpdateCatMediaInfo'. cat_RecordSet::Open()
r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(2404)
{CALL UpdateCatMediaInfo( ?, ?, ?, ?) }


Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34338
Description:
Backup Exec Alert: Catalog Error
(Server: "SERVERNAME") ODBC access error. Possible lost connection to database or
unsuccessful access to catalog index in the database.


Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Description:
Access to catalog index (Catalog index database) failed.
Reason:  Data type mismatch cat_RecordSet::SetField()
r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(3613)
sp_sproc_columns CatImageInfoProc

V-208-2003

Solution

NOTE: There are three possible solutions to resolve this issue.

Solution A

1) Download and install The Microsoft SQL 2005 Server Native Client and SQL 2005 command line query utility "sqlcmd" on the media server.

Feature Pack for Microsoft SQL Server 2005
 http://www.microsoft.com/downloads/details.aspx?FamilyID=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en

sqlncli.msi                                   (Microsoft SQL Server Native Client)
SQLServer2005_SQLCMD.msi      (Microsoft SQL Server 2005 Command Line Query Utility SQLcmd)


2) Stop the Backup Exec services using servicesmgr.exe

3) Open a command prompt on the Media Server to the Backup Exec install directory (C:\program
files\symantec\backup exec)

4) Issue the following command:

sqlcmd -E -S %COMPUTERNAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the remote SQL server name


Example:  C:\program files\symantec\backup exec\sqlcmd -E -S sqlserver01 -dbedb -icatupgrade_12_0.sql


Note: If the Backup Exec database (BEDB) is installed into a "named" SQL instance issue the following command:


sqlcmd -E -S %COMPUTERNAME%\%INSTANCENAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the remote SQL server name
Where %INSTANCENAME% is the named SQL instance name

Example:  C:\program files\symantec\backup exec\sqlcmd -E -S sqlserver01\sqlinstance -dbedb -icatupgrade_12_0.sql

5) Start the Backup Exec Services using servicesmgr.exe


OR


Solution B

1) Stop the Backup Exec Services using servicesmgr.exe

2) Copy the sql script catupgrade_12_0.sql from the Backup Exec for Windows Media Server (X:\program files\symantec\backup exec\catupgrade_12_0.sql) to C:\temp on the SQL server hosting the Backup Exec (BEDB) database.

3) Go to the SQL server and open a command prompt to c:\temp, then issue the following command:


osql -E -S %COMPUTERNAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the SQL server name


Example:  C:\temp\OSQL -E -S sqlserver01 -dbedb -icatupgrade_12_0.sql

(FIGURE B)
 


Note: If the Backup Exec database (BEDB) is installed into a "named" SQL instance issue the following command:


osql -E -S %COMPUTERNAME%\%INSTANCENAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the SQL server name
Where %INSTANCENAME% is the named SQL instance name

Example:  C:\temp\OSQL -E -S sqlserver01\sqlinstance -dbedb -icatupgrade_12_0.sql

4) Start the Backup Exec Services using servicesmgr.exe


If the ODBC access errors are still displayed in the Alerts, proceed with Solution C.

Solution C

1.From the Backup Exec interface go to Tools ->Backup Exec services ->Stop all services.
2.Go to the installation directory of Backup Exec (default location is C:\Program Files\Symantec\Backup Exec\) and rename the 'Catalogs' folder to 'Catalogs.Old'.
3.Open the Windows command prompt and browse to the installation directory \Program Files\Symantec\Backup Exec\ and run the command "CatRebuildIndex -r".
4.Start all Backup Exec services. A new 'Catalogs' folder will now be created on the Backup Exec installation directory.
5.Lauch the Backup Exec console and go to Tools ->Options ->Catalog -> Uncheck the option "Use Storage media-based catalogs".
6.Run catalog job on all media that are needed for the backup or restore job.
 

Applies To

The Backup Exec Database (BEDB) is located on a remote SQL Server or is not in the default named SQL (BKUPEXEC) Instance.

After an upgrade from Backup Exec 11d to Backup Exec 12.0 multiple Catalog Errors appear in the Application Log and the Backup Exec Alerts tab when the Backup Exec database (BEDB) is located on a remote SQL server or not in the default named (BKUPEXEC) SQL instance. The alerts appear when the Backup Exec Services Start and during a backup or catalog job.  Backup jobs and catalog jobs appear to complete successfully with the alerts and events generated. After a catalog job is performed the restore selections may show partial or no restore selections.



(FIGURE A)
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)