R3LOAD Unicode import error

[Former Member]

Hi

We are running the import phase of the unicode CPC for a 6.4 R/3 ascii system. We are using the C64U0377 kernel.

We get the error....

ERROR 2011-11-03 18:54:11.701

CJS-30023 Process call '\usr\sap\T03\SYS\exe\run\R3load -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

The logfile R3LOAD.exe.log shows us

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

C64U0377/R3LOADDB4: START OF LOG: 20111103163159

C64U0377/R3LOADDB4: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

C64U0377/R3LOADDB4: version R6.40/V1.4 u00ACUNICODE|

Compiled Jun 28 2010 17:00:07

C64U0377/R3LOADDB4 -testconnect

When we check the SAPINST joblog in the TMKSVR00 *SBS we see

Message ID . . . . . . : CPF9801 Severity . . . . . . . : 40

Message type . . . . . : Escape

Date sent . . . . . . : 11/03/11 Time sent . . . . . . : 16:31:59

Message . . . . : Object R3LOAD in library TMKSVR00 not found.

Cause . . . . . : The object R3LOAD in library TMKSVR00 type *DTAARA not

found. The object name, library name, or the object type is not correct.

If the library name is not specified, the object may be in a library that is

not contained in the library list.

Recovery . . . : Correct the object name, library name, or object type. If

the library name was not specified, specify the library name and try the

request again

The version of R3LOAD in C64U0377 is dated 6/28/10

Anyone else seen this issue?

Thanks

[Former Member · Accepted solution]

Hi Matt,

in the log you do see, that R3load is in the kernel. The "misasing" dtaara in tmksvr00 is in my eyes just a "check thing", but not a problem ...

Is this the complete r3load log ? Or is the end missing ?

The logfile R3LOAD.exe.log shows us

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

C64U0377/R3LOADDB4: START OF LOG: 20111103163159

C64U0377/R3LOADDB4: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

C64U0377/R3LOADDB4: version R6.40/V1.4 ¬UNICODE|

Compiled Jun 28 2010 17:00:07

C64U0377/R3LOADDB4 -testconnect

???

I would hope, to see a bit more here ...

Could you try and run the following line just on the command line ?

C64U0377/R3LOADDB4 -testconnect

(I hope, the syntax is correct - I think, there is a bit misssing ...)

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[Former Member · Accepted solution]

Hi

The full r3load.exe.log is...

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

C64U0377/R3LOADDB4: START OF LOG: 20111103185420

C64U0377/R3LOADDB4: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

C64U0377/R3LOADDB4: version R6.40/V1.4 ¬UNICODE|

Compiled Jun 28 2010 17:00:07

C64U0377/R3LOADDB4 -testconnect

(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20

(DB) ERROR: DbSlErrorMsg rc = 20

C64U0377/R3LOADDB4: job finished with 1 error(s)

C64U0377/R3LOADDB4: END OF LOG: 20111103185420

Its interesting that there is NO r3loaddb4 in tmksvr00 but there IS a R3LOAD.

Thanks

[former_member188883 · Accepted solution]

Hi ,

Could you repeat the import process with an updated version of R3load.exe from SAP Service marketplace.

Let us know the results .

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Matt,

I can only agree with Deepak.

I would patch r3load & lib_dbsl ...

It is not a surprise, that r3loaddb4 is "missing" in tmksvr00 ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[dorothea_stein · Accepted solution]

Hi Matthew,

the DBSL error message (c = 20) indicates that R3load wasn't able to load LIB_DBSL. Frequent causes are that DBDB4SLIB *SRVPGM can't be found, or that is incompatible with the caller (wrong code page (ASCII versus Unicode), or wrong kernel version).

Best regards,

Dorothea

[Former Member · Accepted solution]

Thanks guys, the kernel patches fixed the problem!