Solution : https://service.sap.com/sap/support/notes/1169995 (SAP Service marketplace login required)
Summary :
This SAP Note addresses multiple symptoms related to display and handling errors of condition records in certain table pools, specifically KAPOL. Issues include runtime errors like DBIF_RSQL_INVALID_RSQL, dictionary and nametab length inconsistencies, and errors in transaction SE11 where the data length exceeds maximum capacity. Dictionary checks reveal discrepancies in length and type, and a log error pertaining to incorrect pool tables is observed in client copies. A database error ORA-12899 is also reported. These issues arose post multiple executions of the UMG_POOL_TABLE program during a Unicode conversion, increasing the VARDATA field length. The suggested remedy involves running the report RATPONTC as detailed in Note 686357 to correct these inconsistencies.
Key words :
system issues message ddact 023, database error ora-12899 occurs, short dump reason, maximum data length, inconsistent database object, table pool kapol, runtime error dbif_rsql_invalid_rsql, display condition records, error occurs, database object
Related Notes :
| 1535660 | KONH-VADAT unusable after upgrade to Unicode system |
| 947291 | Pool tables too short on database after Unicode conversion |
| 686357 | Table pool length incorrect after Unicode conversion |