Solution : https://service.sap.com/sap/support/notes/8307 (SAP Service marketplace login required)
Summary :
Customer requests a change of hostname for a central R/3 system involving specific steps due to reasons such as hostname length or system migration. SAP does not automatically support hostname changes in production environments. For test systems, SAP consultant assistance is required. Changes demand comprehensive reconfiguration, including DB and SAP license updates for Windows NT servers. Pre-change actions include completing and canceling jobs, checking updates, and system stoppage. Operational system adaptations involve network settings, IP name resolution, and updating SAP service definitions. SAP system reconfigurations encompass instance profiles, RFC destinations, and frontend configurations. Special steps are required for different databases and environments.
Key words :
startsap_<oldhost>_00 --> startsap_<newhost>_00 stopsap_<oldhost>_00 --> stopsap_<newhost>_00 change alias, operation modes - profiles - job definition - logon groups note, cd /usr/sap/<sid>/sys/profile check, check additionally bound db2/390 plans, /usr/sap/put/bin, terms hostname change reason, /usr/sap/trans/bin, control panel adapt ip, adapt saplogon/sapgui configurations, reschedule periodic batch jobs
Related Notes :
| 1503149 | Long hostname support for SAP systems on HP-UX |
| 757692 | Changing the hostname for J2EE Engine 6.40/7.0 installation |
| 611361 | Hostnames of SAP servers |
| 574310 | iSeries : specific actions when renaming DB host |
| 403708 | Changing an IP address |
| 88346 | Changing the RFC destination if IP changes are made |
| 70856 | DB2 specific actions when renaming DB host |