2551391 - SWPM: Import ABAP stuck due to different codepage issue. | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2551391 - SWPM: Import ABAP stuck due to different codepage issue.

Symptom

During a Unicode Conversion the import phase of SWPM stops with an error like below:



D:\usr\sap\Q79\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 50000 -force_repeat -loadprocedure dbsl

(PRC) INFO: working directory "C:\Program Files\sapinst_instdir\BS2005\ERP60SR3\LM\COPY\ADA\SYSTEM\CENTRAL\AS-ABAP"
DbSl Trace: different codepage: application=UNICODE, application data=ASCII

(DB) ERROR: db_connect rc = 256
DbSl Trace: different codepage: application=UNICODE, application data=ASCII

(DB) ERROR: DbSlErrorMsg rc = 29

D:\usr\sap\Q79\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)


Read more...

Environment

  • SAP Unicode Conversion
  • SWPM 

Keywords

Unicode Konversion, Unicode Migration, System Copy , KBA , BC-I18-UNI , I18N Unicode , BC-INS-MIG , OS/DB Migrations with SWPM and DB refresh , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.