Dear experts,
(NOTE 966752)
I've also got the quite famous bug of the Migration Controller Tool when doing PI system copy.
I am doing a sap PI dual stack system copy, and of course, it is NW700
SR3 version.
as the notes said:
__________________________________________________________________
Target central instance installation is repeated without reloading the database
If you reinstall the target central instance and you do not repeat the
database load, the Migration Controller will delete all instances in
thedatabase
(NW '04 SPS 16 and lower, NW 2004s SPS 07 and lower).
SOLUTION:
Repeat both database load and target central instance installation.
_________________________________________________________________________
here is my steps, everything is in one machine(central system
actually),but I installed as distributed way(under distributed system):
Install ASCS and SCS Instance(new install way)
DB Installation and recover database(database instance new install
firstand delete database and then restore/recover with old backup data
file)
Install Central Instance(central instance new install way)
after that ,everything is OK both to ABAP and JAVA.
everything is the same between source and target, SAP<SID>, Central instance Number....
and I do not think it must need change the Central instance Number e.g. from source = 11 change to target = 22
but after import JAVA using the tool , as the notes expect the JAVA part can't
start cause the Migration Controller bug. e.g. server0 directory deleted by the
migration tool.
Import Java stack - (I think it should be use the system copy way under
target system and use ABAP+JAVA based)
so how to how to Repeat both database load and target central instance?
edit SOURCE.PROPERTIES or whatever?
detailed steps preferred, since this bug solution(note 966752) is
really too simple and make confuse.
Thanks so much!
Jeffrey