SAP Knowledge Base Article - Preview

1645548 - Deadlock in database causes fatal errors in Audit and CMS.


Central Management Server (CMS) Trace log:

  • 2011/10/14 01:38:17.790|==| | |  216|8740| |||||||||||||||DatabaseSubsystem::HasLocksInDB: true (count: 1)
  • 2011/10/14 01:34:37.040|==| | | 5844|7184| |||||||||||||||(.\TransactionManager.cpp:154) DBConnectionHolder - Caught retryable error with Code 1205, Msg: Lock wait timeout exceeded; try restarting transaction.  Number of retryable errors on connection 3 is 1.
  • 2011/10/14 01:36:30.302|>>|A| | 6952|1904| |||||||||||||||assert failure: (.\dbq.cpp:702). (0 : Database access failure. Too many retries, going to reinit database

 Windows Event log:

  • “Database access failure”
  • “CMS is unstable, will be shutdown immediately.  The reason: Database access failure”
  • "Server IntelligenceAgent : Server <System>.CentralManagementServer stopped unexpectedly."
  • "All Connection to BusinessObjects Enterprise CMS : CMS Audit database BOE120_AUDIT:cms-db-host:3306 lost.  Unable to audit with CMS.  The reason: MySQL server has gone away“



  • BusinessObjects Enterprise (BOE) XI 3.1 Fix Pack (FP) 1.9
  • MySQL 5.0 bundled with BOE XI 3.1
  • CMS and Auditing database are hosted on a same server
  • Clustered with 4 CMS servers



SAP BusinessObjects Enterprise XI 3.1


KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.