hi friends,
please tell me the which type of problems faced in applying support packs.
Thanks and regards,
Ram Gopal
applying support packs
-
- Posts: 4
Re: applying support packs
1. Security checks for Transaction SPAM
A typical example is the step OBJECTS_LOCKED?. If objects are still locked in requests
that are to be overwritten by the queue, the SPAM transaction stops processing.
2. Error messages from the programs tp and R3trans
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 to see whether there are
unconfirmed repairs to objects that are to be overwritten by the queue. The relevant
objects are listed in the test import log.
3. Incorrect configuration of the Change and Transport System
Often the errors here are not having the relevant authorizations to files of the Change
and Transport System, or using old program versions of tp or R3trans. Check the correct
function of the transport tools by choosing Utilities Check transport tool.
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.
Transaction SPAM requires that the Change and Transport System [Ext.] is configured
correctly.
You can find more information on known problems in the Notes 97630 and 97620.
A typical example is the step OBJECTS_LOCKED?. If objects are still locked in requests
that are to be overwritten by the queue, the SPAM transaction stops processing.
2. Error messages from the programs tp and R3trans
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 to see whether there are
unconfirmed repairs to objects that are to be overwritten by the queue. The relevant
objects are listed in the test import log.
3. Incorrect configuration of the Change and Transport System
Often the errors here are not having the relevant authorizations to files of the Change
and Transport System, or using old program versions of tp or R3trans. Check the correct
function of the transport tools by choosing Utilities Check transport tool.
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.
Transaction SPAM requires that the Change and Transport System [Ext.] is configured
correctly.
You can find more information on known problems in the Notes 97630 and 97620.