Spool Consistency Check in the
Background 
Use
You can use report RSPO1043 to check in the background whether tables that contain spool requests, output requests, and output data are inconsistent. You can list and delete inconsistencies that the report finds.
Checking the consistency in the background is preferable to performing the check in dialog, as you can avoid the following significant disadvantages of the online check:
¡ Deleting temporary inconsistencies if the check was only performed once.
Temporary inconsistencies are not actual inconsistencies and must not be deleted. Temporary inconsistencies may occur, for example, if a user is writing data to the TemSe during the consistency check. A check must be performed more than once to ensure that the inconsistency is not merely temporary.
¡ Timeouts
For optimal maintenance of the spool database, schedule report RSP01043 regularly.
As the spool consistency check in the background affects performance, you should schedule it either during the night or at the weekend.
Report Parameters
You can make the following specifications with report RSPO1043:
|
Required Entries |
Default Setting |
|
Number of minutes that an exclusive lock should last |
10080 |
|
Whether an exclusive lock should be checked |
activated |
|
Whether inconsistencies should be corrected or only listed |
activated
|
|
Number of days for which an inconsistent object is to be observed before it is deleted as inconsistent. |
7 |
You can change the default settings in transaction SE38.
Activities
...
1. All exclusive locks in table TSP01 that are older than the specified parameter value are reset.
2. The report then checks all objects for consistency. The objects found to be inconsistent are collected in an internal table.
3. The report then compares its results with the objects found during its last run:
- An object remains in the inconsistency table, if the inconsistent status has not changed.
- If a consistent status is found, the object is removed from the table of inconsistencies.
4. The report then deletes all inconsistent objects that have reached the Delete After n Days time limit.
An object is only deleted, if it is observed for n days AND is found three times: It is identified as inconsistent during the first run, recognized as an actual inconsistency during the second run, and, if it still exists during the third run, and is still inconsistent, it is deleted.
See also:
