Impact Analysis at a Glance
This section deals with the impact analysis as a preparatory step for an update with ZDO.
Performing an update with a downtime-optimization approach can have a certain impact on the ongoing business operations of the bridge subsystem. Therefore, impact analysis is an important step in preparing the update procedure with ZDO.
-
Read-only restrictions for users on the bridge subsystem
-
Database triggers (such as SLT triggers) that have to be removed from certain tables, or an initial load is required after the update is complete
-
Additional free space on the database required for the cloned tables
-
Tables that are smart-switched but have a high number of changes
To identify these impacts in advance, you can export table statistics from your production system and provide them to Software Update Manager in the first test cycle run in the sandbox system. The impact analysis can predict what happens when the defined update scope is applied in the production system.
-
The defined scope (list of software components as well as source and target state of software component versions) must be identical in all systems. If the stack definition is changed, the result also changes.
-
The exported table statistics represent the business operations on the bridge subsystem. All relevant business processes are included according to the exported statistics file. For more information about project planning aspects, see Project Planning Aspects.
The analysis is based on statistical data from the production system as the user activities take place in this system. For this purpose, a tool must be provided in the production system that enables the export of the statistical data. This data is then analyzed either in a special phase in SUM or by a dialog report in the system.
Part of the update is the table classification in phase RUN_RSPTBFIL_ZDM_CLASSIFY, which calculates how the tables are handled during the update. Both customer-specific and SAP-delivered tables are included.
| Table Classification Type | Example | Comment |
|---|---|---|
|
Share |
The update does not change the table or only adds a new non-key field. |
The tables are not cloned. There are no restrictions. |
|
Clone |
The update provides table content or a structural change. |
Additional database space is needed for the table clone, and the change record and replay. There are no restrictions. |
|
Clone read-only |
The update provides a complex structural change, or an XPRA accesses the table. |
Additional database space is needed for the table clone, and the change record and replay. The table is read-only for users for the time when they work on the bridge subsystem. |
To identify ZDO-related table restrictions, the impact analysis combines table statistics exported from your production system with the ZDO table classification result in the system where SUM is running.
Overview on Reports and Tools Related to Impact Analysis
The following list contains all relevant reports and tools for the impact analysis and their main purpose.
| Report | Purpose |
|---|---|
|
RSUPG_RUN_IMPACT_ANALYSIS |
Used by the Software Update Manager in batch mode in phase RSUPG_RUN_IMPACT_ANALYSIS |
| Tool | Purpose |
|---|---|
|
Export data for impact analysis |
Export of table statistics of the production system to a compressed file (such as zdimpana.zip) |
|
Export of SUM classification data |
Export of table classification data of the Software Update Manager (such as puttb_shd.zip) |
|
Impact Analysis |
Dialog version of the impact analysis that can be used in the system upgraded with ZDO after phase RUN_RSPTBFIL_ZDM_CLASSIFY is completed |