Solution : https://service.sap.com/sap/support/notes/966752 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with J2EE Engine startup failures post-system copy using SAPinst and targets instance installation hiccups. The core problem lies in the ID change of instances during migration, driven by the Java Migration Toolkit which alters system-specific identifications such as SAPSID and host names. Missteps resulting in installation failures include not reloading the database after a failed installation attempt, inconsistencies between source and target systems, and incorrect source central instance IDs. Remedial steps include modifying directory-specific files to correct instance IDs and use configuration tools for validating and editing box numbers and host names to ensure consistency across installations.
Key words :
customer component bc-ins-mig db/os migrations priority recommendations / additional info category, /usr/sap/<sid>/sys/profile/<sid>_<instance>_<hostname>, __%pdfstyle%__ / } symptom target central instance installation aborts, error analysis validity software componentfrom rel, open configurations -> cluster_data -> property sheet instance, system copy sap netweaver 2004s 785848 hom, log file <installation directory>/jmt/system, properties file <installation directory>/jmt/cluster_id_switch, / __%pdfstyle%__font-size, terms java system copy reason
Related Notes :
| 871523 | Removing dialog instance from database after uninstallation |
| 870863 | (OUTDATED) Hom./Het.System Copy SAP NetWeaver 2004s |
| 785848 | Hom./Het.System Copy SAP Web AS 6.40 SR1 Java |