Backup Exec Catalog Error 34338
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs backup exec 11d catalog Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange
Backup Exec Catalog Files
Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português backup exec catalog vs inventory Español USA Site: Veritas Veritas PartnerNet Getting "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting
Backup Exec Catalog Media Password
Backup Exec Services. Article:000083813 Publish: Article URL:http://www.veritas.com/docs/000083813 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles backup exec catalog job queued Article Languages Subscribe to this Article Manage your Subscriptions Problem After restarting the Backup Exec services lots of "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" is received in the Application Log and also similar alerts are generated in Alerts tab in Backup Exec. Error Message Application Log Errors: Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failed.Reason: D:\Catalogs\SERVER-NAME\{86794C68-8397-4F24-A2EA-404B54FED371}_31.xml PerformBulkInsert() e:\nicobar\5204r\becat\catindex\dll\..\catdbupdatethread.cpp(447) Source: Backup ExecEvent ID: 34338Error : Backup Exec Alert: Catalog Error (Server: "SERVER-NAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failedReason:[Microsoft][ODBC SQL Server Driver][SQL Server]The INSERT statement conflicted with The FOREIGN KEY constraint "FK_CatImage_CatResource". The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'. cat_RecordSet::ExecuteBulkInsert() e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113) sp_sproc_columns CatImageInfoProc Source: Backup Exec CatErro
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community
Backup Exec Catalog Files Too Large
MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate
Backup Exec Catalog Cleanup
Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) backup exec catalog folder is growing too large English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet ODBC Access errors. Event ID 34338 and 34326 reported on CAS https://www.veritas.com/support/en_US/article.TECH167225 server. Article:000087955 Publish: Article URL:http://www.veritas.com/docs/000087955 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print https://www.veritas.com/support/en_US/article.TECH203788 Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem ODBC Access errors. Event ID 34338 and 34326 reported on CAS server. Error Message Log Name: ApplicationSource: Backup Exec CatErrorHandler ServerEvent ID: 34326Level: ErrorKeywords: Classic Description: Access to catalog index (Catalog index database) failed.Reason: [Microsoft][ODBC SQL Server Driver]Numeric value out of range cat_RecordSet::Open()r:\honshu\1798r\becat\segodbc\seg_odbc.cpp(2465){CALL UpdateCatMedia( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) } Source: Backup ExecEvent ID: 34338Keywords: Classic 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. 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 Documents at the end of this a
Follow one of those solutions: Link 1 http://www.symantec.com/business/support/index?page=content&id=TECH59749 Problem After an Upgrade from Backup Exec for Windows 11d to Backup Exec 12 or 12.5 Catalog Error "ODBC access https://centosbeginer.wordpress.com/2011/07/12/symantec-exec-backup-error-catalog-after-upgrade-from-10-5d-to-12-5/ 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 Event Viewer Application Log: Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Description: Access to catalog index backup exec (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. backup exec catalog 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 Environment The Backup Exec Database (BEDB) is located on a remote SQL Server or is not in the default named SQL (BKUPEXEC) Instance. Solution After an upgrade from Backup Exec 11d to Backup Exec 12.0 or 12.5 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) 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