Hello all - Can some one pls look at my system rename scenario (I am using latest SWPM) and share your thoughts. I am working on system rename (distributed system option) and experiencing issues on the last step, that is during CI rename. My system is installed as dual stack system but Java stack is disabled since we don't use that functionality. ABAP part of CI rename steps seems to have completed successfully and the system is back up with no issues. However, remaining steps (Run Java migration tool kit, Extract bootstrap, Configure SDM, update secstore etc) are not executed yet because "Run Java Migration Toolkit" step is failing with error (see below sapinst log) . I believe these steps are specific to Java stack only, not sure how critical these are. Since I am not using Java stack, can these be disregarded and mark it as complete?. Has anybody experienced this before?.
id=ind-rel.ind-os.ind-db.j2ee-eng.jmt.jmtError27 errno=CJS-20087
Error when running the Java Migration Toolkit.
SOLUTION: Apply SAP Note https://service.sap.com/sap/support/notes/966752. Please review sap note 966752. If that doesn't help the please zip up
and attach to the incident the log files from SAP note 752505.
I had checked above note, but that didn't help.
Here is my system rename scenario, it is a distributed environment with NW7.0 CRM5.2 (dual stack) on Windows 2008 and Oracle 11 on SuSE Linux 10. I am renaming existing SAP system (SAP SID and DBSID) from L2X to S2N. This is what I did so far as part of system rename,
1.) Global Host preparation -- Completed successfully
2.) System rename for SCS instance -- Completed successfully
3.) System rename for database instance -- This step is not very clear to me even after referring to rename guide and couple of other notes. I assume this process will rename DBSID from L2X to S2N, right?. I tried to run this step on windows application server but ran into an error. Do I need to run this step directly on Linux database server instead?. What I did as a workaround is, asked DBA's to perform DB system copy from production to L2X and ran post system copy steps (i.e BDLS, table clean up, adapt RFC's etc).
4.) Now finally, I ran "System rename for Central Instance", this process seems to have completed all ABAP specific steps with no issues. I see rename process has updated files/folder structure on app server to the new SID (S2N), created required sidam users/groups, updated profiles, re-registered SAP services etc with no issues. I can even bring up ABAP system with no issues.
Pls let me know if you need any further info. Would appreciate your valuable input. Thanks in advance.
- Kumar