Shadow (SHD) and Temporary (TMP) instances are additional instances, working with target kernel and target repository. They are set up by the Software Update Manager, and managed by it. They are not fully functional instances. For example, they are working on limited set of tables. Although they are listed in the SAP Management Console, a manual stop and start is only required in exceptional cases. The SHD instance or system is used in all Software Update Manager approaches and matured concept. The concept of shadow repository on target database is used for all migration scenarios with SUM 2.0 SP 08 (and higher).
The TMP instance is a reuse of this concept to enable conversion activities as well as dynamic customizing. More details regarding Customizing follow in Execute Uptime Customizing for FI Conversion on the Temporary Instance (TMP). On file system level, you can find the binaries, profiles and other system files in path ﹤DIR_PUT﹥/ABAP/SYSTEM/﹤SID﹥, where DIR_PUT refers to the Software Update Manager folder SUM and SID to the system identifier of the system.
Caution
Note
Comparison between SHD and TMP
| SHD | TMP |
|---|---|
| additional instances, working with target kernel and target repository | |
| use the same instance number, profile, directory and executables | |
| works on BASIS tables | works on BASIS and application tables relevant for the uptime conversion (after repository switch, phase EU_SWITCH_TEMP) |
| uses shadow schema on the target database | uses actual schema on the target database |
| start/stop by startshd, stopshd | start/stop bystarttmp, stoptmp |