Solution : https://service.sap.com/sap/support/notes/29159 (SAP Service marketplace login required)
Summary :
Symptom: Multiple operational issues are detailed including system crashes and unexpected behavioral symptoms across various SAP modules due to issues in reading nametab (dbntab.c). Examples include execution errors like core dumps in dbntab.c functions such as db_pgntab() and SIF_alloc(), displaying incorrect values in DD_SHOW_NAMETAB, endless loops or crashes during data update transactions in modules like CO-PA or FI, and work process terminations during upgrades or mass activations. Root cause is linked to R/3 objects having excessive field counts or undergoing upgrades, affecting database interaction. Solution involves reactivating the problematic objects after clearing old nametab entries, adjusting FIELDSLG values, and buffer adjustments.
Key words :
memcmp sif_alloc fetch_entry procure_2 db_ntab, converting column overflows integer datatype, hp-ux export stub, normal procedure transaction se11, field ce8-zzzzz unknown, correction p30k022707/b11k017709/bink076079, additional key words nametab, abap runtime error getwa_not_assign, section 'stack back trace', dd_show_nametab shows unreasonable values
Related Notes :
| 315377 | Additional information about upgrading to 3.1I SR1 |
| 91594 | Additional Info: Upgrading to Release 3.1I |
| 76604 | Additional Info: Upgrading to 3.1H |
| 64570 | Additional Info: Upgrading to 3.1G |
| 48632 | Additional Info: Upgrading to 3.0F |
| 43288 | Additional Info: Upgrading to 3.0E |
| 37387 | Additional Info: Upgrading to 3.0D |
| 29346 | Additional Info: Upgrading to 3.0B |
| 25381 | RAISE_EXEPTION in ABAP for NAMETAB_GET |