Solution : https://service.sap.com/sap/support/notes/46077 (SAP Service marketplace login required)
Summary :
When performing a language import in SAP version 3.0E, ensure adherence to specific guidelines detailed across various document sections, particularly Sections 1 through 7 for upgrades, and Sections 2, 5, and 7 using SMLT. During an upgrade from 2.2x to 3.0E, it's natural to encounter insert error flags (RC=0001) in the import log, which can typically be disregarded if subsequent lines show successful imports for each table. The transport request SAPKL30E01 must be fetched for language supplementation post-upgrade, with specific directory instructions provided for FCS and non-FCS customers. Furthermore, ensure ample rollback segment space, minimally 500 MB, to prevent system errors during language imports.
Key words :
cd /usr/sap/put car -xvf /<lang-cd-mount-dir>/fixes/sapkl30e, 0e language import additional key words language import, r3up set stdpar der default batch host, 005230 message id 'tl' type 'i' number '108', 005330 005340 message id 'tl' type 'i' number '108', <machine>_<sid>_<systemnumber>, sap-language-import-job-3 run, jobs sap-language-import-job-1, job sap-language-import-job-3, job sap-language-import-job-1
Related Notes :
| 212876 | The new archiving tool SAPCAR |
| 76285 | 30F Japanese IMG title translation in table DSYAT |
| 65723 | Additional Info: Upgrading to Japanese 30F ADABAS |
| 50387 | After lang.supp., IMG & Rel.Notes in E (3.0D) |
| 48324 | Double entries in DD tables after language supplementation |
| 47976 | Additional Info: Upgrading to Japanese 30E ADABAS |
| 47975 | Additional Info: Upgrading to Japanese 30E INFORMIX |
| 47933 | Additional Info: Upgrading to Japanese 30E ORACLE |
| 46447 | Additional Info: Upgrading to 3.0E DB2/400 |
| 46079 | Space requirement for the language import 3.0E |
| 43288 | Additional Info: Upgrading to 3.0E |
| 12621 | SAPDBA: speeding up a reorganization |