cancel
Showing results for 
Search instead for 
Did you mean: 

WAS 6.40 Jload SystemCopy Error

benjamin_houttuin
Active Contributor
0 Kudos

Hi All,

I try to make a systemcopy of a VMWare Instance with:

- Win2k Server

- MsSql 2000

- Was 6.40 SP 16

- EP 6.40 SP 16

- CM 6.40 SP 16

- ADS 6.40 SP 16

To a new installed VMWare Instance (prepared with Win2k and sqlserver). I follow the documentation discribing the homogeneous system copy. If using Mssql on windows you have to use the Jload Procedure.

All 9 of 10 steps go fine accept the last one step 10 "Export java database content" It takes hours.

I looked at the log (jload.log) file and found the following error:

...

...

...

08.06.06 15:48:38 com.sap.inst.jload.Jload dbExport

INFO: J2EE_CONFIG meta data exported

08.06.06 15:48:38 com.sap.inst.jload.Jload dbExport

INFO: J2EE_CONFIG exported (7352 rows)

08.06.06 15:48:38 com.sap.inst.jload.Jload dbExport

INFO: J2EE_CONFIGENTRY meta data exported

<b>08.06.06 16:13:21 com.sap.inst.jload.db.DBTable unload

WARNING: Empty LOB in column FBLOB

This error is probably caused by a bug in an application

failing to comply with the rules of portability

CID = -9223372036854775196

NAMEHASH = -739536465

ISFILE = 1

NAME = secretkey

DTYPE = (null)

VBIGINT = (null)

VDOUBLE = (null)

VSTR= (null)

VBYTES = ?

FBLOB = ?</b>

Does anyone have a clue?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Did the processing finish and there was only this error reported?

If this did error not cause the program to abort then I would suggest it could be ignored.

benjamin_houttuin
Active Contributor
0 Kudos

Hi Nicholas,

The error didn't end the program...

The program just uses full 100% CPU for a while...

That's not a real scary thing with sap/java apps so I lett it continue.

After more then 8 hours it hasn't got any further so I looked in the log. There I found these errors.

So eventualy I just stopped the program as it didnt go any furher.

Maybe this gives a beter view on my problem.

Thanks

benjamin_houttuin
Active Contributor
0 Kudos

Guys,

It had to do with the JDK...

for everyone who is going to try use jdk1.4.2_12 or above

benjamin_houttuin
Active Contributor
0 Kudos

anyone????