Problem in run java migration toolkit phase

[Former Member]

Hi

We have ep 7 sp 10 on win2003 sp2 and mssql 2005 database .

We try to make a homogenous system copy to a new server .

We gave to the new system the same sid and instance id .

When we try to install the new system we get error massage in

java migration toolkit phase "ERROR 2007-08-13 16:33:48

FCO-00011 The step RunMigrationController with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController was executed with status ERROR .

Please Help

Amit

[Former Member]

Hi

I reinstall the server and it solved all the problems .

Thank You

Amit Zait

[Former Member]

Hi Brad

I solved the problem by deleting the log files from c:\program Files\sapinst_instdir\NW04s .

The process finish with O.K .

The problem now is that it look like it didn't install part of the instance .

I have now SCS that running but many files and directory from the instance

Are missing , of course that the system is unable to start .

Please read the following steps and look if i i'm doing something wrong ,

1. on the source system run the sapinst with database-independent method.

2. on the target system run sapinst and copy the database .

Do i need to do some more steps ?

Amit

[brad_landry2]

Hi amit,

you should not delete logs from the sapinst directory.

Sapinst use the logs to see if there are errors.

If you don't find a solution for the error, the system copy won't work.

If I remember well, you must install/restore the database on the target system with the offline backup before running sapinst.

I did my system copy with oracle 10. I used some dos program (orabrcopy, something like that) to change some database parameter that make the database compatible with the new target system. Maybe there is something similar with mssql server 2005.

Brad

[Former Member]

Hi Brad

Thank you for your quick reply.

If i try different SID i get the same error .

I try install the new system on win 2003 sp2 with mssql 2005 with the same patch

level.

Amit

[brad_landry2]

Hi amit,

same j2sdk?

Brad

[brad_landry2]

Hi amit,

do you get the same error if you try a sid that is not like the source system?

Is the target system win2003 sp2 and mssql 2005 with same patch level?

Brad