SAP Note No. 71353 21.09.2004 Page 1[@more@]SAP Note No. 71353 21.09.2004 Page 1
________________________________________________________________________
Number 71353
Version 6 from 13.03.2002
Status Released for Customer
Set on 13.03.2002
Language EN
Master language DE
Short text Transports hang during background steps
Responsible SAP AG
Component BC-CTS
Change and Transport System
________________________________________________________________________
Long text
Symptom
This is a collective note regarding:
Transports and the interaction with background processing of the SAP
System.The symptoms of the problems described here superficially
resemble each other. Therefore this collective note was
entered.Nonetheless, the situations look differently in detail.
Common symptom of all problems described here:
1. During the export of a transport request in the Workbench or the
Customizing organizer (Transaction SE01, SE09, SE10):
A dialog box displays the message that the objects are
exported.However, the export does not close even after a longer
waiting period.When branching to the transport log display, you
receive the message that no logs were found or that the ADO export
has not yet been executed.
2. During the import of one or more transport requests on the operating
system level with tp:
tp does not close even after a longer waiting period.
In the section Solution you find a description on how the symptoms vary
in detail for the different error scenarios, and the suitable solution
for each case.
Examine the SLOG file in the transport directory first and compare your
error scenario with the situations described here before you consider
one of the solutions.
Other terms
RDDDIC0L, RDDEXECL, RDDMASGL, RDDDIC1L, RDDDIS0L, RDDGENBB, RDDGEN0L,
RDDVERSL, RDDVERSE, tp, TRBAT, TRJOB, RDDDIC3L,
Reason and Prerequisites
different
Solution
1. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
Page 2
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: S
This line can occur repeatedly.
Solution:
In this case, refer to Note 26966.
Page 3
2. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) If you log on as user DDIC in the client 000 of the SAP System
and start the report RDDIMPDP, the error message PU029 is
generated
Header ... : job ... is running
Solution:
Check with Transaction SM37 (job overview) whether all jobs
displayed as 'Active' are really active.
a) Log on as user DDIC to client 000.
b) Start Transaction SM37.
c) Choose the selections:
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with status 'Active'.
d) For the resulting list, check for every entry the status of the
job.You find this function under the option 'Job'.
e) If you find a job which does not run although it is displayed as
'Active' in the status, reset this job to 'Terminated'.
f) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Page 4
3. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: Y
This line can occur repeatedly.
Solution:
Log on to the SAP system as user DDIC. Start Transaction SM37.Enter
the following selection criteria.
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with status 'Ready'.
If an entry is found, position the cursor on the job name and use
the menu item 'Job -> Display' and on the following screen the menu
item 'Process -> Job details'. On the following screen you will find
the ID number of the job.Compare this number with the number which
is referred to as 'Jobcount' in the above SLOG message.(If several
jobs were selected, examine all jobs this way).If the ID number
should match the entered Jobcount, an unexpected status is contained
in the background-system.
This status could indicate a permanent error in the background
processing system. Refer to note: 37104.
If the unexpected status of the entire background processing system
was only temporary, then you can solve the problem for the transport
as follows:
a) To maintain table TRJOB use Transaction SM31.
b) Select the entry which matches the above SLOG message concerning
the value 'Function' and 'Jobcount'. Delete this entry.
c) If the transport control program continued running during these
examinations and did not make any progress due to the temporary
problem in the background-system, the transport control program
(tp) will continue its work as soon as you corrected the above
error.Otherwise, start the transport control program with the
same parameters as during the last call for which you noticed
hanging transports.If you do not know the parameters or are not
sure, start the following call:
Page 5
tp getprots
Page 6
4. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: P
This line can occur repeatedly.
Solution:
a) Check the authorizations of the user DDIC in client 000 and in
the client into which the transport should be imported.Logon to
both clients as user DDIC and execute the report RDDNEWPP
(Transaction SA38 or SE38).If the report does not end with the
success message
PU006 Background job ... was successfully scheduled... in the
client.
the authorizations of the user DDIC must then become enhanced in
the respective client.
b) To do this, logon in the respective client under a user that is
authorized for user maintenance.Change the authorizations of user
DDIC in user maintenance (Transaction SU01).Give the user DDIC
the authorization for scheduling and for starting the background
jobs. SAP delivers the authorization S_BTCH_ALL and S_BTCH_ADM
(depending on the release) for this.
Afterwards, the following correction steps are necessary in Release
3.0E or younger:
c) Log on to the SAP system as user DDIC. Start Transaction
SM37.Enter the following selection criteria.
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with statuses 'Scheduled'.
d) If an entry is found, position the cursor on the job name and use
the menu item 'Job -> Display' and on the following screen the
menu item 'Process -> Job details'. On the following screen, you
find the ID number of the job.Compare this number with the number
which is referred to as 'Jobcount' in the above SLOG message.(If
several jobs were selected, examine all jobs this way).If the ID
number should match the entered Job count, delete this job.
Page 7
e) Position the cursor in the list of the selected jobs on the job
to be deleted and choose 'Job ->Delete'.
f) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Page 8
5. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) If you log on as user DDIC in client 000 the SAP System and start
the report RDDIMPDP, the following message is generated PU014
Header ... : No actions currently required
Solution:
a) Log on as user DDIC to client 000.
b) To maintain the table TRBAT use Transaction SM31.
c) Check whether you find the following entries in table:
An entry, in the field 'Request' that has the value 'HEADER'
and in the field 'Ret.
At least one additional entry, which has the same value as the
first entry in the field 'Fct.', and which has the value
'8888' or '9999' in the field 'Return code'.
d) For the first entry ('HEADER') change the value in the field
'Ret. code' from 'F' to 'B' and save this change.
e) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Comment: This error scenario can no longer occur as of Release 3.0F.
Repairs in the Code
________________________________________________________________________
Note is release independent
________________________________________________________________________
Page 9
Reference to related Notes
Number Short text
____________________________________________________________
556941 Transport FAQ: Error scenarios
128835 Error when importing Safety Check 2000
37104 Error analysis: Background processing system
26966 Background jobs do not start when transporting
________________________________________________________________________
________________________________________________________________________
Number 71353
Version 6 from 13.03.2002
Status Released for Customer
Set on 13.03.2002
Language EN
Master language DE
Short text Transports hang during background steps
Responsible SAP AG
Component BC-CTS
Change and Transport System
________________________________________________________________________
Long text
Symptom
This is a collective note regarding:
Transports and the interaction with background processing of the SAP
System.The symptoms of the problems described here superficially
resemble each other. Therefore this collective note was
entered.Nonetheless, the situations look differently in detail.
Common symptom of all problems described here:
1. During the export of a transport request in the Workbench or the
Customizing organizer (Transaction SE01, SE09, SE10):
A dialog box displays the message that the objects are
exported.However, the export does not close even after a longer
waiting period.When branching to the transport log display, you
receive the message that no logs were found or that the ADO export
has not yet been executed.
2. During the import of one or more transport requests on the operating
system level with tp:
tp does not close even after a longer waiting period.
In the section Solution you find a description on how the symptoms vary
in detail for the different error scenarios, and the suitable solution
for each case.
Examine the SLOG file in the transport directory first and compare your
error scenario with the situations described here before you consider
one of the solutions.
Other terms
RDDDIC0L, RDDEXECL, RDDMASGL, RDDDIC1L, RDDDIS0L, RDDGENBB, RDDGEN0L,
RDDVERSL, RDDVERSE, tp, TRBAT, TRJOB, RDDDIC3L,
Reason and Prerequisites
different
Solution
1. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
Page 2
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: S
This line can occur repeatedly.
Solution:
In this case, refer to Note 26966.
Page 3
2. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) If you log on as user DDIC in the client 000 of the SAP System
and start the report RDDIMPDP, the error message PU029 is
generated
Header ... : job ... is running
Solution:
Check with Transaction SM37 (job overview) whether all jobs
displayed as 'Active' are really active.
a) Log on as user DDIC to client 000.
b) Start Transaction SM37.
c) Choose the selections:
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with status 'Active'.
d) For the resulting list, check for every entry the status of the
job.You find this function under the option 'Job'.
e) If you find a job which does not run although it is displayed as
'Active' in the status, reset this job to 'Terminated'.
f) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Page 4
3. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: Y
This line can occur repeatedly.
Solution:
Log on to the SAP system as user DDIC. Start Transaction SM37.Enter
the following selection criteria.
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with status 'Ready'.
If an entry is found, position the cursor on the job name and use
the menu item 'Job -> Display' and on the following screen the menu
item 'Process -> Job details'. On the following screen you will find
the ID number of the job.Compare this number with the number which
is referred to as 'Jobcount' in the above SLOG message.(If several
jobs were selected, examine all jobs this way).If the ID number
should match the entered Jobcount, an unexpected status is contained
in the background-system.
This status could indicate a permanent error in the background
processing system. Refer to note: 37104.
If the unexpected status of the entire background processing system
was only temporary, then you can solve the problem for the transport
as follows:
a) To maintain table TRJOB use Transaction SM31.
b) Select the entry which matches the above SLOG message concerning
the value 'Function' and 'Jobcount'. Delete this entry.
c) If the transport control program continued running during these
examinations and did not make any progress due to the temporary
problem in the background-system, the transport control program
(tp) will continue its work as soon as you corrected the above
error.Otherwise, start the transport control program with the
same parameters as during the last call for which you noticed
hanging transports.If you do not know the parameters or are not
sure, start the following call:
Page 5
tp getprots
Page 6
4. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) After the above line, you find in the SLOG file, in addition to
further messages, a line of the form:
Background job not running properly. Function: Jobcount,
...:Status, ...: P
This line can occur repeatedly.
Solution:
a) Check the authorizations of the user DDIC in client 000 and in
the client into which the transport should be imported.Logon to
both clients as user DDIC and execute the report RDDNEWPP
(Transaction SA38 or SE38).If the report does not end with the
success message
PU006 Background job ... was successfully scheduled... in the
client.
the authorizations of the user DDIC must then become enhanced in
the respective client.
b) To do this, logon in the respective client under a user that is
authorized for user maintenance.Change the authorizations of user
DDIC in user maintenance (Transaction SU01).Give the user DDIC
the authorization for scheduling and for starting the background
jobs. SAP delivers the authorization S_BTCH_ALL and S_BTCH_ADM
(depending on the release) for this.
Afterwards, the following correction steps are necessary in Release
3.0E or younger:
c) Log on to the SAP system as user DDIC. Start Transaction
SM37.Enter the following selection criteria.
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with statuses 'Scheduled'.
d) If an entry is found, position the cursor on the job name and use
the menu item 'Job -> Display' and on the following screen the
menu item 'Process -> Job details'. On the following screen, you
find the ID number of the job.Compare this number with the number
which is referred to as 'Jobcount' in the above SLOG message.(If
several jobs were selected, examine all jobs this way).If the ID
number should match the entered Job count, delete this job.
Page 7
e) Position the cursor in the list of the selected jobs on the job
to be deleted and choose 'Job ->Delete'.
f) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Page 8
5. Symptom:
a) The last line in the SLOG file, which starts with 'START' or
'STOP', has the form
START tp_getprot.......
b) If you log on as user DDIC in client 000 the SAP System and start
the report RDDIMPDP, the following message is generated PU014
Header ... : No actions currently required
Solution:
a) Log on as user DDIC to client 000.
b) To maintain the table TRBAT use Transaction SM31.
c) Check whether you find the following entries in table:
An entry, in the field 'Request' that has the value 'HEADER'
and in the field 'Ret.
At least one additional entry, which has the same value as the
first entry in the field 'Fct.', and which has the value
'8888' or '9999' in the field 'Return code'.
d) For the first entry ('HEADER') change the value in the field
'Ret. code' from 'F' to 'B' and save this change.
e) If the transport control program (tp) continued to run during
these examinations, the transport control program will continue
its work after this correction.Otherwise, start the transport
control program with the same parameters as during the last call
for which you noticed hanging transports.If you do not know the
parameters or are not sure, start the following call:
tp getprots
Comment: This error scenario can no longer occur as of Release 3.0F.
Repairs in the Code
________________________________________________________________________
Note is release independent
________________________________________________________________________
Page 9
Reference to related Notes
Number Short text
____________________________________________________________
556941 Transport FAQ: Error scenarios
128835 Error when importing Safety Check 2000
37104 Error analysis: Background processing system
26966 Background jobs do not start when transporting
________________________________________________________________________
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/792762/viewspace-993557/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/792762/viewspace-993557/
扫一扫
1438
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
