ODBC access error - Catalog Error

[Mike_Ross]

I have a Win 2000 SP4 server running Backup Exec 10.0.5520 SP2
After every inventory of the tapes I get an error:

ODBC access error. Possible lost connection to database or un successful access to catalog index in the database.

I have tried rebuilding the catalogs by deleting it and reinstalling a new one.
I have looked at the registry and verified that the path in the registry matches the actual catalog path.

I have seen this problem posted several times with no clear answer.

[shweta_rege]

Hello,

Kindly perform the below given steps
.
1. Stop all the services of Backup Exec.

2. Rename the "Catalogs" folder to "Catalogsold" (C:\ProgramFiles\VERITAS\Backup Exec\NT)

3. Create a new Catalogs folder on the same location.

4. Start all the services of Backup Exec.

You need to catalog all the tapes

5. Perform the backup and observe the result.



Thank you..

[Mike_Ross]

I have tried rebuilding the catalogs. That did not work.

I have also looked at the registry and verified that the catalog path in the registry matched the actual catalog path. That also did not work.

[Amruta_Bhide]

Hello Mike,

- Please let us know if you get any other errors in the event logs?
- Also do you get this Problem ONLY by Inventoring the tapes?

Thanks
Regards,

[Russell_Kame]

Mike,
I am having the exact same problem. I put a post up yesterday but never received a response. I tried all the fixes I found from various posts but nothing has worked. This problem only comes up when I try to inventory my library. Below is a list of what I have tried.

1) This error is due to the catalog path in Backup Exec being different than the catalog path in the registry.

To resolve this issue follow steps below:

1. Open Backup Exec
2. Open Tools > Options
3. Click on Catalog
4. Verify the catalog path that appears here is accurate
5. Open regedit from Start > Run

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Nagvigate to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Misc
7. Double click on

Check if the path is C:\Programfiles\Veritas\BackupExec\NT\Catalogs

. Stop and Restart the Backup Exec Services by going to Tools > Backup Exec Services > Stop all services
10. After services stop, click on Start all services.


2) Reapplied MDAC to version 2.8

3) Try running a slow catalog job by unchecking "use storage based catalog" under tools -> options after having renamed the catalog folder

I am also receiving the following errors in the application event log - Error ID's 34338, 34327

I am running Backup Exec 10d Version 10.1 Rev. 5629 on a Windows 2003 SP1 Standard ServerMessage was edited by:
Russell Kame

[Mike_Ross]

I do get this error prior to ODBC access error:

Update to catalog index (Catalog index database) failed.
Reason: Invalid attribute/option identifier cat_RecordSet::Delete()
e:\caicosmp1\5520r\becat\beplugins\beimage\catmedia.cpp(780)

So far this error has only happened during the inventory process.

[Russell_Kame]

Mike,

I had a reply on the post that i made. This is what was written.

Try to repair the BEDB as per the link below and then do the catalog:

http://support.veritas.com/docs/265180

I tried it out and it fixed the problem i had. hope this helps

[shweta_rege]

Hello Mike,




Could you please Update us on the issue?



Thank You.....

[Mike_Ross]

My update on the situation is that the problem is still occuring. I am going to try the suggestion of repairing the database next.

[Mike_Ross]

I tried to repair the database without success. The BEUTILITY would not even shut down the services without an error.
I tried shutting down the services first and then running the DB repair but that failed also.

[Amruta_Bhide]

Hello,

You could run a Repair Installation:
Title:- Repairing Backup Exec 9.x and 10.x for Windows Servers http://seer.support.veritas.com/docs/253199.htm


Hope that helps.

Thanks
Regards

[Mike_Ross]

I just ran a repair of Backup Exec on the server that was giving me the ODBC error.
After running the repair and rebooting the server I got the same results,
ODBC error right after the inventory of the tapes finished

[shweta_rege]

Hello,



Could you check if you receive any events in the event logs?




Thank You,

Shweta

[Mike_Ross]

In the Application Event log, these errors appear:

Update to catalog index (Catalog index database) failed.
Reason: Invalid attribute/option identifier cat_RecordSet::Delete()
e:\caicosmp1\5520r\becat\beplugins\beimage\catmedia.cpp(780)

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

[Shilpa_pawar_2]

Hi,

Before creating new catalogs, try following steps:
1) Stop all Backup Exec services from Tools --> Backup Exec services.
2) Quit Backup Exec.
3) OPen windows Explorer and navigate to C:\Program files\Veritas\Backup Exec\NT\Catalogs.
4) Delete all the temporary files from the CATALOGS folder:
a. *.TMP
b. *.SM (temporary CATALOG files)
c. *.FDD (temporary CATALOG files)
d. QTC*.* (temporary CATALOG files)
5) Restart Backup Exec services.


If the issue persists, perform extensive database repair:

Go to C:\ProgramFiles\VERITAS\BackupExec\NT- Execute file name- BEUtility.exe
Hit yes on following message.
Now, Right click on All media server, Click New media server.
Type in Backup Exec server name and hit Ok.

Now right click on the BackupExec server name and click Refresh.
Right click on BackupExec server name again and run following options:
(has to be executed in the exact sequence given below)
Repair Database
Rebuild database Indices
Compact Database
Age Database
Check Database Consistency


Thanks!

[Mike_Ross]

I tried deleting the TEMP files and the problem still existed.

When I try to run the database repair I get the following error:

Starting database repair.
Stopping Services
Stopping services for server:KCNTBAK3.
Server:KCNTBAK3, Service:BackupExecJobEngine stopped successfully or was not running.
Server:KCNTBAK3, Service:BackupExecRPCService failed to stop.
Error: (1051) - A stop control has been sent to a service that other running services are dependent on.

Server:KCNTBAK3, Service:BackupExecDeviceMediaService failed to stop.
Error: (1051) - A stop control has been sent to a service that other running services are dependent on.

Stopping Services for server KCNTBAK3 completed with errors.
Starting Services
Database repair for server KCNTBAK3 ended with errors.

[Mike_Ross]

I guess I need to go back a step now and figure out why the database repair will not run. This is the error I get when I try to repair the database:

Starting database repair.
Stopping Services
Stopping services for server:KCNTBAK3.
Server:KCNTBAK3, Service:BackupExecJobEngine stopped successfully or was not running.
Server:KCNTBAK3, Service:BackupExecRPCService failed to stop.
Error: (1051) - A stop control has been sent to a service that other running services are dependent on.

Server:KCNTBAK3, Service:BackupExecDeviceMediaService failed to stop.
Error: (1051) - A stop control has been sent to a service that other running services are dependent on.

Stopping Services for server KCNTBAK3 completed with errors.
Starting Services
Database repair for server KCNTBAK3 ended with errors.

[Mike_Ross]

I have not heard back from anyone on this issue.
Can you please give me any suggestions that you may have.

[Chris_Ginn]

Windows Server 2003 SP1 (Fully Updated)
MDAC 2.8
Backup Exec 10d SP2

I'm having exactly the problem, I've tried the full DB rebuild as described at the bottom of the last page but it hasn't made any difference!!
Checked the registry and the catalog path is correct and I have emptied the catalog directory after I rebuilt the db.

My inventories work fine only catalogs error.

When I try to catalog I get the following:

From Backup Exec:
-------------------------------------------------------------------------------------------------------------

Catalog 00105 -- The job failed with the following error: The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation.

-------------------------------------------------------------------------------------------------------------

ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.

-------------------------------------------------------------------------------------------------------------

From Event Viewer Application Log:

-------------------------------------------------------------------------------------------------------------

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

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

-------------------------------------------------------------------------------------------------------------

Update to catalog index (Catalog index database) failed.
Reason: Invalid attribute/option identifier cat_RecordSet::Delete()
e:\caicosmp2\5629r\becat\beplugins\beimage\catmedia.cpp(780)

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

-------------------------------------------------------------------------------------------------------------

I have found a work around though!
I used a vanilla install of Windows 2003 (no updates) and a vanilla install of Backup Exec 10d (no updates) on another box and I successfully cataloged and restored my disk based backups.Message was edited by:
Chris Ginn

[Chris_Ginn]

Any further news with this?

This is a real problem for me.