SAP Knowledge Base Article - Preview

2151620 - SQL Anywhere transaction log file size becomes extremely large and causes performance issue

Symptom

Transaction file becomes extremely large and causes performance issue.


Read more...

Environment

  • SAP BusinessObjects Enterprise (BOE) XI 3.1 Service Pack 5 or higher
  • SAP BusinessObjects Business Intelligence Platform (BI) 4.0 / 4.1 / 4.x
  • SAP SQL Anywhere (SQLA) 12

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 6.1.3 ; SAP BusinessObjects Enterprise XI 3.1

Keywords

XI31, BI40, sybase, sqlanywhere, Business_Objects_CMS.log, Business_Objects_CMS.db, Business_Objects_Audit.log, Business_Objects_Audit.db, anywhere, database size, cms.log, audit.log , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , 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.