Fixing inconsistencies in TemSe and Spool systems

I have found some inconsistencies in TemSe and in the Spool system. Please let me know the causes of these inconsistencies. How can I analyze and rectify these inconsistencies?

    Requires Free Membership to View

    Login

There can be many different causes for the inconsistencies in TemSe. For example, if you manually delete table entries from the spool and TemSe tables, delete spool and TemSe objects from the file system. The terminations of report and transaction also cause these inconsistencies. Also an incorrectly executed client transport can also lead to inconsistencies in the TemSe and spool.

Check the memory distribution in TemSe:

-> Tools -> Administration
-> Spool -> TemSe administration (Transaction SP12)
-> TemSe data Storage -> Memory allocation

Check whether the number of your TemSe objects is very large. Also check whether many of your objects are stored with an unlimited retention period. Note that you cannot see the retention period of spool requests here as it is stored in Table TSP01 and can be read from Transaction SP01.

Delete any objects that are no longer required:

  1. Delete spool objects that are no longer required:

    (Transaction SPAD) -> Administration -> Clean-up spool

    You can also use the report RSPO0041 to delete out-of-date spool requests.

  2. Delete job logs no longer required using report RSBTCDEL
  3. To delete background input logs that are no longer needed, use the RSBDCREO report

There is another report RSTS0022 for deleting old Temse objects but I suggest not using this report as this report does not take into account dependencies between TemSe tables and other tables.

This was first published in June 2008

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top