Program RSCROSS10, Performance problems with job EU_REORG
[db2 reorg] [EU_REORG] [list] [ok to program] [REORG] [reorg rebuild] [RSCROSS10] [RS_STOP_WHERE_USED] [where-used]
- Performance problems occur in connection with table WBCROSSISymptom Performance problems occur when a selection is made in table WBCROSSI. Update processes hang when table WBCROSSI is selected. Problems occur in Transaction SE54 Generate Table Maintenance. Class CL_WB_CROSSREFERENCE terminates with...
Symptom
The job EU_REORG has a long runtime in STEP 10 in the program RSCROSS10.
Program RSCROSS10 cleans up the incorrect entries in the where-used list index. This mainly involves deleting the entries in the where-used list tables WBCROSSGT, CROSS, and WBCROSSI.
Since these tables are very large, the program RSCROSS10 may run for a very long time.
Other terms
EU_REORG, RSCROSS10, where-used list, RS_STOP_WHERE_USED
Reason and Prerequisites
Performance problems
Solution
You can skip the update of the where-used list in systems in which the where-used list is not required, for example, in production systems. You can use the report RS_WHERE_USED_SWITCH_OFF to deactivate the where-used list update. Step 10 is then no longer executed in the job EU_REORG. Caution: This means that the where-used list can no longer function correctly. You may deactivate the switch only in systems that do not use the where-used list.
If you want to reactivate the where-used list, you must first rebuild the entire index. You must start the program SAPRSEUB or SAPRSEUC. Also refer to Notes 28022 and 18026. Both of these programs automatically reactivate the where-used list update.
If you want to deactivate the where-used list, proceed as follows:
Implement the advance correction or import the specified Support Package.
Then execute the report RS_WHERE_USED_SWITCH_OFF. This deactivates the update of the where-used list. The where-used list function still exists in the Workbench tools, but it may generate an incorrect list.