SAP Knowledge Base Article - Preview

1776499 - Audit text files are not written to the Auditing database

Symptom

  • Audit backlogs are not transferred to SAP BusinessObjects Business Intelligence (BI) Platform 4.0 Auditing Data Source.
  • Instead, audit temp files sit untouched in the temporary Auditing directory for weeks or longer
  • The followin errors may be found in the CMS trace logs:
    • Error: "ODBC error found:  ErrorMessage([Microsoft][ODBC SQL Server Driver]String data, right truncation), ErrorCode(0)".
    • Error: "DBConnectionHolder - (AuditDB) - Caught retryable error with Code 0, Msg: [Microsoft][ODBC SQL Server Driver]String data, right truncation  Number of retryable errors on this connection is 1".
    • Error: "Auditor::CommitUncomittedAuditeesHelper: Failed to write auditee into audit db - database unreachable".
    • Error: "Auditor::PullAuditEvents - failed to commit uncommitted auditees".
    • There is a server in a node whose the total length of server name including node name, i.e. <NODE>.<SERVERNAME> exceeds 64 characters. 


Read more...

Environment

  • SAP Business Intelligence Platform 4.0

Product

SAP BusinessObjects Business Intelligence platform 4.0

Keywords

audit, auditing, ads, database injection, transfer, inject, injection, missing, backlog, audit text, text file, server name, corrupt, missing TE: 5000448171 , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-CRS , SAP Crystal Server , Bug Filed

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.