SAP Note 16875 - TemSe objects do not match TemSe files

Symptom:

There are files of TemSe objects for which no TemSe objects exist.

Reason and Prerequisites

Only TemSe administration knows which files belong to which TemSe objects.
If you copy databases, restore from a data backup, delete clients without deleting their objects first, or copy clients using the improper tools, the relation may be lost.

Solution

When files are missing, you can use program RSTS0020 (TemSe consistency check) to delete the orphaned TemSe objects.

When there are too many files, there is no simple way, as the necessary information on the database no longer exists. The following method is relatively certain:

1.
->Tools -> Administration
->Spool ->TemSe administration (Transaction SP12)
->TemSe database ->Reorganization
deletes TemSe objects whose expiration date has passed. This will greatly reduce the number of objects you have to examine. Beforehand, the application objects that belong to the TemSe objects must be reorganized with the reports RSBTCDEL (old background logs) and RSPO0041 (old spool requests) as well as RPUTSR00 (HR TemSe objects Note 98995). If this is not carried out and only TemSe objects are deleted, entries can be stalled in the application tables which refer to the deleted TemSe objects.

2. Use
->Tools ->Administration
->Spool ->TemSe administration (Transaction SP12)
->TemSe database ->Consistency check (Program RSTS0020)
to force consistency by deleting objects whose files are missing.

Check the log. Depending on your authorization, the consistency check will run either only the current client or in all clients.

3.
->Tools ->Administration
->Spool ->TemSe administration (Transaction SP12)
->TemSe database ->Space assignment
shows the oldest TemSe object per client and name group.

4.
In general, the file names consist of:
/usr/sap/ }
+ system name }
+ /SYS/global/ }- Directory
+ client }
+ first 5 characters of TemSe object name }
+ /
+ four character part number }- file name
+ remaining characters of TemSe object name }

Example: /usr/sap/C11/SYS/global/003SPOOL/000122334 for TemSe object [003]SPOOL22334,1 for spool request 22334.
Each TemSe object can store its files in other places, however, this is not normally the case.

5.
Find the files that are too old and those which - according to the client and/or start of the name - belong to areas in which no TemSe objects should exist.

Move these files to a different directory.

6.

Run a new consistency check to make sure step 5 did not cause any damage.

7.
Delete the files.