Symptom
- The following Error messages might appear in the Report Conversion tool trace log file
ORA-12899: value too large for column "<Schema Name>"."OBJ_G_MIGRATION"."G_MIG_C_SUBTYPE" (actual: 57, maximum: 40)
or ORA-12899: value too large for column "<Schema Name>"."OBJ_G_MIGRATION"."G_MIG_C_KEYWORD" (actual: 48, maximum: 40) - Cannot save the report conversion result into the audit table(OBJ_G_MIGRATION) with below error message
ERROR: UMPAuditDb::insertDatabase: Insert failed. [umpauditdb.cpp;420]
Note: KBA 1384138 described the same behavior for G_MIG_C_COMMENT in BO XI 3.1, but the column size of G_MIG_C_COMMENT in BI 4.x is defined as longer than it in BO XI 3.1.
1384138 - "ERROR: ORA-12899: value too large for column..." when Report Conversion Tool is saving the result into audit table
"."OBJ_G_MIGRATION"."<...>" appears in the trace log file of Report Conversion Tool"> Read more...
Environment
- SAP BusinessObjects Business Intelligence platform 4.0
- SAP BusinessObjects Business Intelligence platform 4.1
- Oracle Database using AL32UTF8 (or equivalent) as database character set
- Desktop Intelligence
- Report Conversion Tool
Product
Keywords
NLS_LANG, NLS_CHARACTERSET, JAPANESE_JAPAN.UTF8, UCS, octet, G_MIG_C_KEYWORD, ADAPT01203402, G_MIG_C_SUBTYPE, G_MIG_C_TYPE, column, NLS_LENGTH_SEMANTICS, alter session set nls_length_semantics , 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.