Backup Exec 2010 Odbc Access Error
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER odbc access error backup exec 2014 Customer Center Support Community MyVeritas Customer Success Licensing
Backup Exec 15 Odbc Access Error
Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor catrebuildindex -r Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Getting "ODBC event id 34326 backup exec access error. Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting 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
Backup Exec 15 Catalog Error Odbc Access Error
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 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 un
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 v-280-2003 Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español 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 of a GRT enabled set post Hotfix 159965 for 2010 R3 https://www.veritas.com/support/en_US/article.TECH167225 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 Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your https://www.veritas.com/support/en_US/article.000013561 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 Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translatedGovernance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 https://vox.veritas.com/t5/Backup-Exec/quot-ODBC-access-error-Possible-lost-connection-to-database-or/td-p/423030 Developers Blogs Groups Vision 2016 Sign In 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 backup exec Exec : "ODBC access error. Possible lost connection to da... VOX : Backup and Recovery : Backup Exec : "ODBC access error. Possible lost connection to da... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to odbc access error Solution "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database." + Hotfix 164220 error atos Level 4 09-19-2011 12:49 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content After running Live update and installed 6 Update hotfix sucsessfully, and 1 unsuccsessfully i started to get the "ODBC access error .Possible lost connection to database or unsuccessful access to catalog index in the database." error. (the error started on the night after the updates were installed so i presume its somehow connected). Successfull updates: 159961 159965 160008 161270 161390 162830 Failed Update: 164220 Does anyone have a cause and/or a solution for the ODBC access error message? (and does the error cause any dataloss, corruption and so on?) Anyone else having problem installing Hotfix 164220? (Running backup exec 2010 R3 on Windows Server 2