Backup Exec Odbc Access Error. Possible Lost Connection
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 Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us odbc access error backup exec 2014 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas odbc access error backup exec 2012 Veritas PartnerNet An alert 'ODBC access error' is observed every time the Backup Exec services start and the restore selections are odbc access error backup exec 2010 not complete. Article:000040371 Publish: Article URL:http://www.veritas.com/docs/000040371 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 odbc access error possible lost connection to database Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Every time Backup Exec (BE) services start, the following Errors are observed in the Alerts tab. (Figure 1). In addition, the restore selections may not be able to be browsed or may not be displayed at all when trying to create a new
Backup Exec 15 Odbc Access Error
restore job. Error Message ODBC access error. Possible lost connection to database or unssuccessful access to catalog index in the database Figure 1: Cause This can occur due to connection issues to the Backup Exec database or corrupt catalogs in the Catalog folder. It can also occur after an upgrade of Backup Exec if the catalogs have not been upgraded completely from the past version. Solution 1. Backup Exec Database (BEDD) is hosted on an invalid SQL Instance. Solution: First make sure the SQL instance being used for the BEDB is a valid Instance. This by default is SQL Express but could be a full version of SQL. If the instance is a SQL MSDE 2000 instance that was not upgraded to SQL Express, this is the problem. Install another instance with SQL Express installer. Located in the BE install files WINNT\Install\SQLExpress\ Then use BEUtility to move BEDB to the SQL Express instance, Open BEUtility,Select All Media ServersOn the right column right click the Media Server name Select New Backup Exec Database locationIn the box enter the ServerName\NewSQLInstanceName 2. Corrupt database index of catalogs. Solution: Run CatRebuildIndex to rebuild the Catalog indexes. (Figure 2) Stop all BE ServicesOpen command prompt and browse to x:\Program F
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 Licensing
Backup Exec 2015 Odbc Access Error
Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange event id 34326 backup exec Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español catrebuildindex -r USA Site: Veritas Veritas PartnerNet ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database alert appears during setcopy https://www.veritas.com/support/en_US/article.TECH75279 of a GRT enabled set post Hotfix 159965 for 2010 R3 Article:000013561 Publish: Article URL:http://www.veritas.com/docs/000013561 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 https://www.veritas.com/support/en_US/article.000013561 Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Alert appears when GRT (Granular Restore Technology) set is duplicated from Deduplication folder or Backup to Disk Folder. Error Message Event Type: ErrorEvent Source: Backup Exec CatErrorHandler ServerEvent Category: NoneEvent ID: 34326Date: 8/30/2011Time: 1:35:45 PMUser: N/AComputer: SERVERX64 Backup Exec Alert:ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Cause This Issue was Introduced with Backup Exec 2010 R3 Hotfix 159965. The errors are cosmetic in nature. The backup completes and data can be restored from the duplicated set. Symantec recommends verifying this in your environment by performing a test restore from a duplicated set that generated this error message. Solution This issue has been resolved in Backup Exec 2010 R3 Service Pack 2http://www.symantec.com/docs/TECH178798 NOTE : The Alert can be Ignored Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x TranGovernance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/Backup-Exec/HELP-ODBC-access-error-Possible-lost-connection-to-database-or/td-p/311560 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : HELP!!! ODBC access error. Possible lost connecti... VOX : Backup and Recovery : Backup Exec : HELP!!! ODBC access error. Possible backup exec lost connecti... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page HELP!!! ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. fl Level 4 05-28-2010 11:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a odbc access error Friend Report Inappropriate Content We're having major issues with our backup solution. We have a single BE 12 server. We been receiving the following errors from all Windows, Linux and Mac servers. And also errors relating to "value out of range" When I try to restore the Backup Set Number that ends with a negative value (ie, -30577) and catalog File Name ending in a negative value (ie, ....._-30577.xml) are the ones that doesn't show the restore list after the backup job is successful. We trying everything from repair DB, renaming Catalog folders, etc... still no luck! Please help! As we are not able to do any kind of backups at this point we can not afford to start over and lose months of backups. Backup Exec Alert: Catalog Error ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. From application event log: Access to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver]Numeric value out of range cat_RecordSet:pen() r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(2404) SELECT distinct CatMedia.*, ImageObjectView.FragmentState FROM CatMedia, ImageObjectView WHERE CatMedia.MediaFamilyGuid = ImageObjectView.MediaFamilyGuid AND CatMedia.MediaNumber = ImageObjectView.MediaNumber AND CatMedia.PartitionID = ImageObjectView.PartitionID AND ImageObjectView.ImageNumbe