ASCS Instance Move

The Software Update Manager offers the option of an ASCS instance move.

This feature enables an update procedure even if the ASCS instance is running on an unsupported operating system. For more information about the reduction of supported operating systems, see SAP Note 2620910 Information published on SAP site .

If the Software Update Manager detects an existing ASCS instance on a remote application server host in the Checks roadmap step, it prompts you in a dialog in phase ASCS_ASK to choose one of the following options:

I want the ASCS Instance Move during the SUM run
I want to keep the current instance setup

If you select the ASCS instance move, the Software Update Manager moves the existing ASCS instance from the remote application server host to the SUM application host during the update procedure.

The ASCS Instance Split is optionally possible because you can still change the ASCS instance manually before the production system is restarted. See also Important Entries for the Execution Roadmap Step Start of the navigation path Next navigation step Manual Actions for the ASCS Instance (Phase REQ_ASCS_SWITCH) End of the navigation path .

Note

The Software Update Manager automatically assigns the number of the shadow instance to the new ASCS instance. However, if you have switched on the expert mode at the beginning of the update procedure, you can manually enter an instance number for the new ASCS instance.
Note that you must delete the source ASCS instance manually after an ASCS move.
1. Stop the SAP Startservice and remove the corresponding file from the DIR_GLOBAL/sapcontrol directory.
2. If the old ASCS still appears in the SAP Management Console (SAP MMC), remove the outdated entries manually using Delete.
If you perform an ASCS instance move on a high availability (HA) system, contact your HA partner if you have questions regarding the changes of the cluster configuration.
The Software Update Manager does not offer the usage of the HA Maintenance Mode because the HA configuration is changed. This means that automation is not possible and manual action is required.
If you use the database migration option (DMO) in addition, and you reset the procedure, you must restart the SAP Startservice of the ASCS instance from the remote application server manually. For more information, see the chapter Reset Option in the DMO guide that is mentioned in the List of Referenced Documentation.