Testing the migration key for OS/DB migration
I was thinking, that testing the migration key in advance isn't a bad idea. But I am really struggling
to perform this in practice. Looking through the different system copy guides and other documentation,
I can't find a real example on how exactly to do that, hence I am posting a couple of questions, to
which I didn't find the answers nowhere:
1) On what system one has to test the migration key ? Source or target ? (I think, on the target system)
2) Is it necessary to already have the export files ? Meaning - is it possible to test the migration key even
before performing the export of the source system ?
3) What is the EXACT COMMAND, meaning a REAL syntax example, without any placeholders like
<TASK_FILE>, etc. ?
4) If testing is performed on the target system, what do we need to have there, in order to test it ? Installed
database ? Unpacked R3load binary ? Unpacked kernel ? Installed NetWeaver system ? .CMD file ?
.TPL file ? Data file (.000), TEST_MIGKEY.CMD ?? Nobody says exactly what has to be done...
Many thanks for clarifying this to me!