Errors in SPAM Steps 

If an error is recognized in a step, the SPAM transaction stops the processing until the error is corrected. You can get information about the reason the SPAM transaction was stopped and in which step by choosing Status.

Error Types

Here are the following types of error messages:

  1. Security checks for transaction SPAM
  2. A typical example is the step OBJECTS_LOCKED?. If objects are still locked requests that should be overwritten by the patch queue, the SPAM transaction stops processing.

  3. Error messages from the programs tp and R3trans
  4. You can always find the cause of the error in the relevant transport log. A typical example is the step TEST_IMPORT. A check is made whether there are unconfirmed repairs to objects that should be overwritten by the patch queue. The relevant objects are listed in the test import log.

  5. Incorrect setup of the transport system.

Often the errors here are not having the relevant authorizations to files of the transport system, or using old program versions of tp or R3trans . Check the correct function of the transport tools by choosing Utilities ® Check transport tools.

A typical example is the step DISASSEMBLE. If <sid>adm does not have write authorization for the directory /usr/sap/trans/data (UNIX), SPAM stops at the step DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE .

The SPAM transaction requires that the Workbench Organizer (WBO) and the transport system are set up. You can find more information on this topic under BC Change and Transport Organizer.

You can find more information on known problems in the Notes 97630 and 97620.

Known Problems

PROLOGUE

In this step, you are asked via a dialog box to confirm the patch application. If you are not authorized to execute the SPAM transaction or the current patch queue has not yet been confirmed, the SPAM transaction is stopped with a corresponding message.

CHECK_REQUIREMENTS

In this step, various requirements for the patch application are checked. The following messages explain why this step may be terminated:

- TP_CANNOT_CONNECT_TO_SYSTEM : tp cannot log onto the systemís database.

DISASSEMBLE

In this step, files from the corresponding EPS parcels are unpacked and stored in the directory /usr/sap/trans/data (UNIX). The command files (cofiles) from the accompanying files are generated and are stored in the directory /usr/sap/trans/cofiles (UNIX). The following messages explain why this step may be terminated:

- CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.

- CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must download the relevant patch again (for example, Hot Package).

- CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined, because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.

- CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).

- CANNOT_DISASSEMBLE_D_DATA_FILE : An ADO data file could not be unpacked. The reasons are the same as with the message CANNOT_DISASSEMBLE_R_DATA_FILE .

- CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One possible error source is that <sys>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).

You can find more information on this topic in Note 70752.

ADD_TO_BUFFER

In this step, the patch queue is put into the transport buffer of your system. The following messages explain why this step may be terminated:

- TP_INTERFACE_FAILURE : The tp interface could not be called. There is an RFC error.

- CANNOT_ADD_PATCH_TO_BUFFER : A patch could not be included in the transport buffer. You can find more information in the SLOG system log file in the directory /usr/sap/trans/log (UNIX).

- CANNOT_MODIFY_BUFFER : An unsuccessful attempt was made to modify the transport buffer.

TEST_IMPORT

In this step, the system checks if there are still objects in tasks which have not yet been released and are overwritten when the patch is applied. You can find the source of error in the log of the test import. For further information, see the Note 42379.

IMPORT_OBJECT_LIST

In this step, the object lists for the patches in the queue are imported in the system. The following messages explain why this step may be terminated:

- TP_INTERFACE_FAILURE : The tp interface could not be called.

- TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.

- COMMAND_FILE_IMPORT_FAILURE : The object list for one or several patches could not be imported. You can find the source of error in the log of the command file import.

OBJECTS_LOCKED_?

In this step, the system checks if there are still objects in requests that have not yet been released and are overwritten when the patch is applied. The following messages explain why this step may be terminated:

- CANNOT_GET_OBJECT_LIST : The object list for a patch could not be found, because the patch does not exist.

- CANNOT_CHECK_LOCKS : An error occurred when checking the locks of an object in the patch queue.

- OBJECTS_LOCKED_IN_REQUESTS : Objects were found that are still in requests that have not yet been released. Before continuing with applying the patch, release these requests.

SCHEDULE_RDDIMPDP

In this step, the transport daemon (program RDDIMPDP) is scheduled. The following messages explain why this step may be terminated:

- CANNOT_SCHEDULE_RDDIMPDP : The job RDDIMPDP could not be scheduled. Call Transaction SM37 (job selection), enter the following parameters and then choose Continue:

Job name

RDDIMPDP

User name

<User name>

Trigger event

SAP_TRIGGER_RDDIMPDP

Select the job that was terminated and display the job log.

- Problems with the SAP locking mechanism: Call Transaction SM12 and ensure that there are no programs listed with the name RDDIMPDP. For further information, see the Note 11677.

GENERATE_BACKUP

In this step, a backup copy of the objects is generated that are overwritten when the patch is applied. The following messages explain why this step may be terminated:

- CANNOT_FIND_BACKUP : Using the first patch in the patch queue, it is determined whether a backup already exists. If the step is terminated, the patch does not exist. Therefore the backup cannot be determined.

- CANNOT_CREATE_EMPTY_BACKUP : An unsuccessful attempt was made to generate a backup.

- CANNOT_COPY_PATCH_TO_BACKUP : For each list in the patch queue, the object list is copied to the backup. This action terminates for a particular patch.

- CANNOT_SORT_N_COMPRESS_BACKUP : The complete object list in the backup is sorted and compressed before the export. An error occurred here.

- CANNOT_EXPORT_BACKUP : The backup could not be exported successfully. The reason for the step being terminated is in the message that tp returns to the SAP Patch Manager.

- CANNOT_ANALYSE_EXPORT_RC : The tp return code could not be analyzed successfully.

- CANNOT_ADD_BACKUP_TO_BUFFER : After the backup has been generated, it is saved to the SAP transport buffer to protect it from being unintentionally deleted. The reason for the step being terminated is in the message that tp returns to the SAP Patch Manager.

ADDON_CONFLICTS_?

In this step, the system checks if there are conflicts between objects in the patch queue and installed add-ons. If there are any conflicts, SPAM terminates and asks you to import the relevant Conflict Resolution Transports (CRTs). The following messages explain why this step may be terminated:

- CANNOT_GET_OBJECT_LIST : The object list for a patch could not be determined, because the patch does not exist.

- CANNOT_GET_LAST_UPGRADE_INFO : The information about the last Repository switch upgrade could not be determined.

- UNRESOLVED_ADDON_CONFLICTS : Conflicts with add-ons could not be resolved, because the relevant CRTs are missing from the patch queue.

SPDD_SPAU_CHECK

In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).

DDIC_IMPORT

In this step, the ABAP Dictionary is imported. The following messages explain why this step may be terminated:

- TP_INTERFACE_FAILURE : The tp interface could not be called.

- TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.

- CANNOT_IMPORT_DDIC : The ABAP Dictionary could not be imported. You can find the source of error in the Dictionary import log.

AUTO_MOD_SPDD

In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.

RUN_SPDD_?

In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.

IMPORT_PROPER

In this step, the Repository including all table entries is imported The following messages explain why this step may be terminated:

- TP_INTERFACE_FAILURE : The tp interface could not be called.

- TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.

- TP_STEP_FAILURE : A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import or generation log. If the generation is terminated ( tp step G), you can correct the error either immediately or after the patch has been applied. In the second case, you must perform the following steps:

1. To ignore the generation errors, choose Extras ® Ignore gen. errors.

2. Continue applying the patch.

Generation errors can also be caused by buffer synchronization problems. For further information, see the Note 40584.

If a tp step is listed in a termination message, it concerns a step that is independent of the transport request. The stepís log cannot be displayed using the pushbutton Log. In this case, analyze the following files:

tp step 6: P<YY><MM><DD>.<SID>

tp step N: N<YY><MM><DD>.<SID>

tp step S: DS<YY><MM><DD>.<SID>

All the logs are located in /usr/sap/trans/log . You can display them using the report RSPUTPRT or Transaction AL11.

AUTO_MOD_SPAU

In this step, the system checks if modifications can be adjusted automatically.

RUN_SPAU_?

In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.

EPILOGUE

In this step, the patch application is ended. The system checks if the patch queue has been completely processed. In this case, there should be no more transport buffer entries for the queue. The following messages explain why this step may be terminated:

- TP_INTERFACE_FAILURE : The tp interface could not be called.

- TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.

- QUEUE_STILL_IN_BUFFER : The patch queue is not fully processed, because incomplete patches of the queue are still in the transport buffer.

- CANNOT_RESET_FCS_FLAG : If an FCS Final Delta Patch (FFDP) is in the patch queue, the system is marked as Final State after the patch is applied. In this case, this operation could not be successfully performed.