on 11-23-2010 2:33 PM
Dear Guru's,
We are facing some issue while doing the transports from PRD system. We don't find any issue while doing transports from DEV to QAS.
Once it has been imported in QAS, it will be available in PRD queue but when we import the TR in PRD means its not completing, the status was showing the TRUCK symbol for long time and its not completing the import.
Error message we got :
-
The following call returned with exit code 7:
sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=P10
Background jobs cannot be started.
(This warning is harmless if no further warnings follow.)
Background job RDDIMPDP could not be started or terminated abnormally.
-
Could anyone suggest me.
regards,
Guna
Hi,
it seems that there is really a TP process running. Check and rename the files if you are not sure.
The TP program does not complete this means its waiting for another program to end.
Check also space...
Bst regards
HanseAtik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guna,
I would like you to check few things before you get into a conclusion.. Check in the directory DIR_TRANS subdirectory tmp whether the import process regularly updates a log file for a certain import phase. The last entries in this log file provide information about what the import process is currently doing. If the import hangs, you may find more error messages in the directory DIR_TRANS subdirectory log in the file SLOG<YY><WW>.<SID> (YY are the last 2 numbers of the year and WW is the calendar week). The lines at the end of the file often even contain detailed messages on the error, such as RDDIMPDP is not scheduled. The following notes should also be checked: 12746, 71353, 26966, 449270.
If no helpful information has been found in the SLOG, you should check in DIR_TRANS subdirectory tmp whether there is a file there with extension .LO and this should be compared with note 12746. You can also check the tables TRBAT and TRJOB via SE16 or SM30 to see if there are old entries there.
Also as venkat suggested please check the SAPnote Note 449270 - Job RDDIMPDP is not triggered by sapevt its quite possible that you may have multiple Instances or may be its OS issue.
All the best !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All,
As per Venkat suggestion all the entries available there in the sap system. Still we're unable to transport.
Note : we're running in the clustering environment, OS clustering has been made here. server01 and server02, when server01 act as master we dont find any issue. Once we down the server01 and it automatically switch to server02, the printing and transports are not working. once you start the server01 also means printing issue has been fixed but the transport issue having the same status.(hanging)
suggestions please
regards,
Guna
Hi Guna,
Follow the below step to overcome your problem.
1. Goto STMS
2. Goto you production system transport Que.
3. Select the request for which you are facing problem
4. press Ctrl+F8 ( you will get new windows as import Monitor)
5. In import monitor windows, right click on the request and delete it.
6. Login to SAP of your production system.
7. Goto SM31
8. Give table name as TRBAT
9. Click on Maintain Tab.
10. If there are any entry present in the table delete it.
11. Now again try to transport the request.
Thanks
Anil
Hi,
You are running on Microsoft Windows Cluster, correct?
If yes, you have to look at notes 943334 and 449270.
Note 943334 explains how you enable loadbalancing in the TMS RFC communication, by running a report on the Transport Domain controller.
Note 449270 explains how you add a parameter to the transport profile, telling the system where to find the default.pfl file.
You might have to kickstart the transport again, by running the tp import command at OS level on your PROD system.
Regards
Henrik
Check the job log for RDDIMPDP. Make sure you have free BTC work process.
also check the TP log from Import monitor --> go to --> display tp system logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
execute the program RDDNEWPP in 000 once and try again. Also check if there are any TP processes running at os level.
check the following note as well
Note 449270 - Job RDDIMPDP is not triggered by sapevt . Were you able to import it previously?
Edited by: venkatesh koukuntla on Nov 23, 2010 3:45 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.