Updating SAP ABAP Systems on UNIX and Linux: Oracle

Cleaning up Terminated Database Conversions

This topic deals with cleaning up terminated conversions in the database conversion phases.

Context

The Software Update Manager indicates terminated conversions with the following error messages:

  • WARNING: The following restart logs of database conversions were found

  • WARNING: The following unprocessed database conversion requests were found

The messages are followed by a list with the corresponding entries. These errors can occur in one of the phases
  • CNV_CHK_GEN
  • CNV_CHK_IMP
  • CNV_CHK_XT

Procedure

Cleaning up Terminated Conversions When Restart Logs of Database Conversions Were Found

  1. Call transaction SE14 (Database Utility) to determine the terminated conversions.
  2. Choose Start of the navigation pathDB Requests  Next navigation step  Terminated End of the navigation path.
  3. If terminated conversions are found, double-click a table name for more details.
  4. Check the meaning and status of the table.
    1. Find out whether the table is still needed. Sometimes the tables are test tables that are no longer needed. For SAP tables, contact SAP Support, which can assess if an SAP table is still needed.
    2. Ask the last person who changed the table, or the table owner, to find out its status.

      If the table is no longer needed, choose Unlock table in the detailed display. This prevents the conversion from being continued automatically. The table itself does not return to a consistent state. Any data that is still in the temporary table is lost during the next conversion. In some cases, however, the table was already corrected without the reset log being deleted. The function Unlock table is harmless in this case.

    3. You can determine the state of the table with Start of the navigation pathCheck Next navigation step Database object and Check  Next navigation step Runtime objectEnd of the navigation path.
    4. Check if the table contains the data you expect.

      You can do this with transaction SE16 (Data Browser), for example. If the data does not exist, it could still be in the temporary table. Contact your SAP consultant or SAP Support for help with saving this data.

  5. Determine the cause of the error.

    If you find out that the table is still needed, choose Object log. Look for error messages that explain why the conversions were terminated. You could encounter the following problems here:

    • You cannot find a log because it was deleted at some time in the past. Continue with step 6 (continue the conversion to the end).

    • The log does not contain an error message, but ends abruptly. This indicates that the conversion was stopped by an external event. Call transaction SM21 to read the system log and find out the approximate time the conversion was terminated, and to look for the cause of the error.

    • If the log clearly gives a reason for the error, you have to correct it.

  6. Continue the conversion to the end.

    In the detailed display, choose Continue adjustment. Since you do not know how long this takes, choose processing type Background.

    The situation can be as follows:

    • The conversion finished successfully. You can see this because the error message disappears, the Check function does not display any further problems, and there is a success message in the object log.

    • The conversion terminates again. A log now exists. Repeat the analysis from step 5 (Determine the cause of the error).

Cleaning up Terminated Conversions When Inprocessed Database Conversion Requests Were Found

  1. Determine the objects that are affected.
    1. Call transaction SE14 (Database Utility) and choose Start of the navigation pathDB Requests  Next navigation step  Mass ProcessingEnd of the navigation path.
    2. Choose All requests.

      The worklist of the conversion program is displayed. This worklist was generated by developments or modifications in your SAP system, but has not yet been processed.

    3. Choose Start of the navigation pathDB requests  Next navigation step  Created with importEnd of the navigation path.

      The worklist, which was not processed correctly during the last update, appears.

  2. Check the meaning and status of the requests.

    In contrast to the procedure for the message The following restart logs of database conversions were found, this procedure can also include requests for indexes, views, and matchcode objects. The requests that are found are not always terminated. They might not even have been started.

    1. Ask the last person who changed the object if the request should still be processed.
    2. If the user does not want it to be processed, select the request and choose Delete selected.

      This removes the objects from the worklist of the conversion program.

      Do not remove requests from the last update.

  3. Process the unprocessed requests.

    You can select the requests from the list of mass processing requests and schedule a job for execution with the function Schedule selections.

    1. In the list of requests created by the import, double-click on an object for a detailed display.
    2. Schedule the request, or continue it. Since you do not know how long this takes, choose processing type Background.