SAP Basis Tech Supports

Symptom
When you carry out aSystem Switch Upgrade,certain upgrade actions (modification adjustment, activation and distribution of the DDIC objects from Support Packages, add-ons …) are performed on a second instance (shadow instance). This instance can be operated either locally on the host of the central instance or on a second host, if there are resource bottlenecks.
If theshadow instance is operated locally, no user actions are required. In this case, the installation and configuration of the shadow instance is performed exclusively using R3up or SAPup.
If theshadow instance is operated on a host otherthan the host of the central instance, different user actions are required. For more information about the actions required when upgrading on Windows, see this note.
Other terms
Shadow instance, remote, System Switch Upgrade
Reason and Prerequisites
This note is divided into two sections, one that is generally valid on Windows and one that is database-specific.
Outline
==========================================================
1. Remote shadow instance on Windows
a. General information
b. Prerequisites of an existing dialog instance
c. Installing a new dialog instance
d. Manual adjustments for the shadow instance
e. Installing a license for the shadow instance
f. Actions for operating a dialog instance after the upgrade
g. Timeout due to copying of sapcpe
2. Remote shadow instance on the ORACLE database
3. Remote shadow instance on SAP DB database
4. Remote shadow instance on the INFORMIX database
Solution
1.Remote shadow instance on Windowsa)General information
The remote shadow instance represents a further instance of the original system that is operated during the upgrade with the kernel of the target release.
To operate this shadow instance, you require a dialog instance that can be adjusted for the operation as a shadow instance during the upgrade.
If you have already installed a dialog instance that is not required during the upgrade, you can use it under certain conditions for the operation as a shadow instance.
Note: This dialog instance is reconfigured during the PREPARE run, and cannot be started and used as normal dialog instance from the beginning of PREPARE until the upgrade is completed.
If you have not installed a dialog instance or cannot do without their operation during the upgrade, you must install a new dialog instance.
After the upgrade, you can use the dialog instance that was used as a shadow instance during the upgrade, as a dialog instance again (the change back into a normal dialog instance of the target release occurs automatically at the end of the upgrade).
b)Prerequisites of an existing dialog instance
If you want to configure an existing dialog instance as a shadow instance, make sure that the following prerequisites are met:The dialog instance was not installed before Release 4.5B (Reason: the new kernel, with which the shadow instance is operated, can only run with the SAP service with the DCOM interface).The instance number of the dialog instance is different to that of the central instance.
If these two prerequisites are met, the dialog instance can be modified during the upgrade as a shadow instance.
In the PREPARE module installation, the system asks you for the instance number of the shadow instance. Enter the instance number of this dialog instance.c)Installing a new dialog instance
For the installation of the dialog instance, choose a server within the system landscape which is located in the same domain as the central instance. Install a dialog instance with at least Release 4.5B – the required software is provided on the ‘SAP Kernel’ CD relevant for the release (you can also install a dialog instance of the target release, but you cannot start the instance before the START_SHDI_FIRST phase).
For the dialog instance, select an instance number that differs from the instance number of the central instance.
In the PREPARE module installation, the system asks you for the instance number of the shadow instance. Enter the instance number of this dialog instance.d)Manual adjustments for the shadow instance
On theshadow instance hostEnter the message server port of the shadow instance as follows in the %WINDIR%\system32\drivers\etc\services file:
sapmsSHD<SAPSID> 36<instance number of the shadow instance>/tcpWith target release 6.40, additional libraries are required for the SAP kernel. To install these, execute the R3dllins.exe program from the NT\I386\NTPATCH directory on the Upgrade Master CD.
As of Release 7.00, the R3dllins.exe program is in the UM<U/N>_WINDOWS_<Platform>\DBINDEP\NTPATCH directory on the Upgrade Master DVD.Before you upgrade to Release 7.10, you must execute the SAPMMC Installer instead of R3dllins. The SAPMMC Installer is located on the kernel DVD under <DVD>\DATA_UNITS\K_710_UI_WINDOWS_<PROZESSOR>\DBINDEP\sapmmc<prozessor>u.msi.
To execute the msi file that corresponds to your processor type, double-click the relevant file.Depending on the target release of the upgrade (for example, 64-bit with target release 7.01 or 7.10 and higher), C-runtime 8.0 must be installed on the host of the shadow instance (for more detailed information, see Note 684106).

On thecentral instance host:Make sure that you can access the upgrade directory from the host of the shadow instance. To do this, you can create a share on the upgrade directory (for example, with share name SHARE_PUT). Ensure that the members of the SAP_LocalAdmin group on the host of the shadow instance “Full control” have authorization for this share. This access path is requested in the SHDINST_HOST phase in the PREPARE module installation.Make sure that the port numbers required for communicating with the shadow instance are not occupied on the central instance. To do this, check the following port numbers in the services file in the %WINDIR%\system32\drivers\etc directory:
36<Instance number Shadow instance> …Message Server Port
33<Instance number Shadow instance> …Gateway Port
32<Instance number Shadow instance> …Dispatcher Port
e)Installing a license for the shadow instance
No special license is required for operating a normal dialog instance.
However, since the dialog instance is converted into a shadow instance for the operation, and therefore a special message server is run under different hardware than the central instance, you must install a special temporary license for the shadow instance.
You can install this temporary license either before or after PREPARE – but you must install it before starting the upgrade.
Proceed as follows:Determine the HARDWARE_KEY on the host of the shadow instance by calling ’saplicense.exe -get’.Install a special temporary license for this HARDWARE_KEY on the host of the central instance by calling saplicense.exe -install’ or ’saplicense.exe -temp’.
f)Actions for operating a dialog instance after the upgrade
After the upgrade, the dialog instance used as a remote shadow instance is reconfigured for the operation as a dialog instance.
Also ensure that the following prerequisites are met:Operating system upgrade
The dialog instance as of Release 6.x is supported only on Windows 2000, Windows XP or Windows 2003. If you ran the upgrade on an earlier operating system version, you must now upgrade your operating system.Migration or upgrade of the database software
For further information refer to your database-specific upgrade or the migration guidelines.a)Timeout because sapcpe runs too longIn rare cases, a timeout may occur, as it takes too long to copy the kernel with sapcpe. In this case, you have to wait for the copying process to end and repeat the START_SHDI_FIRST phase2.Remote shadow instance on the ORACLE databasea)Controlling the NLS_LANG parameter in the registry
The environment variables of the SAP System contain the SYSTEM environment as well as all values that are stored in the registry under the key HKEY_LOCAL_MACHINE -> SOFTWARE -> SAP -> <SID> -> Environment.
The contents of the environment key are updated with every SAP system start and filled with the environment of the AdmUser referenced under HKEY_LOCAL_MACHINE -> SOFTWARE -> SAP -> <SID>.
The SAP kernel from Release 6.x, which is used to operate the shadow system, requires theNLS_LANGenvironment variable for its runtime.
You must therefore ensure that on the host of the shadow instance, the following value is contained in the registry under HKEY_LOCAL_MACHINE -> SOFTWARE -> SAP -> <SID> -> Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
If this value is not contained here, check whether the AdmUser value was set in the registry under the key HKEY_LOCAL_MACHINE -> SOFTWARE -> SAP -> <SID>.If the value was set under this key, set the NLS_LANG environment variable in the environment of the user referenced here.If the AdmUser value does not exist, extend the SAP environment directly by setting the NLS_LANG value under the following key: HKEY_LOCAL_MACHINE -> SOFTWARE -> SAP -> <SID> -> environmentb)Required version of the Oracle client software
Note that you must use the version of the ORACLE client software that is relevant for the database version you installed.
If required, upgrade the client software.
3.Remote shadow instance on SAP DB databasea)Required version of SAP DB client software
Note that you must use the version of the SAP DB client software that is relevant for the database version you installed.
If required, upgrade the client software.
The update of the client software is available on the relevant
SAP DB database software CD. On this CD, start
<CD-DRIVE>:\NT\I386\SDBINST -c
4.Remote shadow instance on the INFORMIX databasea)Required version of INFORMIX client software
Make sure that you use the correct version of the Informix front-end software (IConnect software), you must use the software that is relevant for the R/3 kernel of the target release (for a list specifying the relevant Informix front end software, see Note 115619).
Repairs in the Code

Attention: Do not enter source code here! Enter source code under
“Corrections” -> “Correction instructions”.
Lines entered here are deleted automatically when saving!