cancel
Showing results for 
Search instead for 
Did you mean: 

unicode migration via socket

Former Member
0 Kudos

Dear all,

I am converting an ECC system to unicode using the socket option. Shortly after the communication between the two server has been established and 2 jobs has been completed I can not see any procedure. And in sapinst gui I can read "RESPONSE: BUSY". Find below the export and import monitor logs.

Any idea what could cause the problem? Thanks in advance for any info provided.

This is short cut/past from export_monitor.log:

CONFIG: 2012-03-07 15:04:19

List of packages with table structure: 'SAP0000'.

CONFIG: 2012-03-07 15:04:19

List of packages with views: 'SAPVIEW'.

TRACE: 2012-03-07 15:04:19 com.sap.inst.migmon.exp.ExportSocketTask sendDataCodepage

Communication server request:

DTCP 4102

TRACE: 2012-03-07 15:04:19 com.sap.inst.migmon.exp.ExportSocketTask sendDataCodepage

Communication server response:

DONE

TRACE: 2012-03-07 15:04:19 com.sap.inst.migmon.exp.ExportSocketTask initServerPackages

Communication server request:

INIT

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask initServerPackages

Communication server response:

COUNT 460

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask readConversionPackageNames

Communication server request:

CONV

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask readConversionPackageNames

Communication server response:

NONE

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask processExportPackage

Communication server request:

LOAD ACCTIT

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask processExportPackage

Communication server response:

BUSY

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask processExportPackage

Communication server request:

LOAD SOFFCONT1-1

TRACE: 2012-03-07 15:04:20 com.sap.inst.migmon.exp.ExportSocketTask processExportPackage

Communication server response:

BUSY

And this is short cut/past from import_monitor.log:

REQUEST: DTCP 4102

RESPONSE: DONE

REQUEST: INIT

RESPONSE: COUNT 460

REQUEST: CONV

RESPONSE: NONE

REQUEST: LOAD ACCTIT

RESPONSE: BUSY

REQUEST: LOAD SOFFCONT1-1

RESPONSE: BUSY

REQUEST: LOAD SOFFCONT1-10

RESPONSE: BUSY

Rgrds

Muris

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member188883
Active Contributor
0 Kudos

Hi,

R3load option using Sockets requires a very stable network. Any glitch in the network could lead to problems like communication server busy etc. So ensure that you have stable communication between your source and target system and the dump location and restart the migration process.

Additionally please check whether you have updated R3load executable for your SAP kernel release.

Info:

R3load socket option:

You can use the socket option, if your R3load has at least patch level 73 (compile date: 12.01.2008)

Regards,

Deepak Kori

Former Member
0 Kudos

All requirements fulfilled. There source and target exchange also initial data (you can see as if the target is going to start importing, but short after that I got "BUSY" message...

yuri_shikunov
Explorer
0 Kudos

This is bug in MigMon fixed 3-4 months ago.

Try to use "old" 7.0x version from SMP or check if newest 7.10 vesrion is already uploaded in 2012.

Former Member
0 Kudos

What are the parameters in import_monitor_cmd.properties that you have maintained?

Paste it here.

Thanks

Srikanth M

Former Member
0 Kudos

"import_monitor_cmd.properties":

dbType=ORA

importDirs=/mnt/export/ABAP

installDir=/tmp/sapinst_instdir/ERPEhP4/LM/COPY/ORA/SYSTEM/CENTRAL/AS-ABAP

orderBy=

ddlMap=ddl_mapping.txt

r3loadExe=/usr/sap/SID/SYS/exe/run/R3load

tskFiles=yes

extFiles=yes

dbCodepage=4102

jobNum=14

monitorTimeout=30

taskArgs=-loadprocedure fast

loadArgs=-stop_on_error

socket

port=1025

trace=all