Transport running

[Former Member]

Hi,

Transport is running since 2 days. pls find below the log

START imp single PRD 20100818103357 DDIC TEST 2010081810335

INFO TBATG CONVERSION OF PRD N not needed DDIC TEST 2010081810335

START MOVE NAMETABS PRD 6 20100818103357 DDIC TEST 2010081810335

WARNING: System PRD. Warning. 20100818103657 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

START tp_getprots PRD P 20100818103657 DDIC TEST 2010081810335

WARNING: System PRD. Warning. 20100818104202 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

This system is restored and all the Post installation activities are performed as per guide

Following checklist performed:

- RDDIMPDP already scheduled by DDIC in all clients from se38 and kernel patch is also latest

- dev_evt has *** ERROR *** : Cannot determine mshost so checked hosts file and services file

- hosts file has entry of this IP and hostname and services file has entry sapmsPRD with port number 3600

- in sm37, rdd* jobs has owner DDIC and jobs are Released status (RDDIMPDP_CLIENT_100 and for every other client also)

- tried changing the parameter SYSTEM_PF in transport tool but no use.

Pls suggest

Regards

[Former Member]

thNKSS

[Former Member]

Is your transport still running?

[Former Member]

Check if any RDD* job is still active or there is a old lock in SM12, Run you transport system check and see if you find any error there.

[anindya_bose]

James Bond

Check your TRBAT table from SM30. Check if you can see the same request there. Delete the request from TRBAT and save in your productive client.

Go to Client 000. Re -run RDDNEWPP in DIALOG mode and then Schedule it with "Highest Priority". Now come to your production client and try re-import.

Regards

Anindya

[Former Member]

Hi ,

please check the following..

1) check the availability of background jobs if they are occupied kill the long running jobs which are not active .

2)check whether their are lock waits in db01 if lock waits are there system will be slow and you have to wait till locks are cleared.

3)check in which step the jobs gets hanged and run the corresponding job STEP

Run the following corresponding STEPS from se38

J-Activation---- RDDMASGL with variant IMPACT21A

S-Distribution---RDDGENBB with variant DIST

N----

---

RDDGENBB '' '' conv

P----

---

RDDMNTAB

Y----

---

RDDGENBB conm

V----

---

RDDVERSI

R----

---

RDDEXECL

G----

---

RDDDIC3L

by running this manually the job gets cleared.

Regards

Zia

Regards

Zia

[Former Member]

Check tables trjob and trbat

[Former Member]

Hi,

- checked default profile, already deleted the entries from trbat & trjob and tp.exe entry deleted from task manager and restarted but same issue. already checked 642464 & 449270

- deleted STMS and re configured but no progress.

- checked hosts and services file required entries exist

- /usr/sap/trans has full permission for SIDadm and SAPServiceSD

- sufficient backgrnd workprocess availble.

Regards

[Former Member]

Hi,

Did you run the program RDDNEWPP in 000 client and what is the latest log in SLOG. Can you past that here now. Also, check in usr/sap/trans/tmp folder and if you find any entries there then either rename all of those or delete them.

Regards,

Sharath

[Former Member]

Hi,

already tried RDDIMPDP and RDDNEWPP in 000 with DDIC user ID. they are in released status.

pls find below the latest log

WARNING: (This warning is harmless if no further warnings follow.)

START tp_getprots PRD P 20100819104601 BASIS TEST 20100819104300

START imp single PRD 20100819104903 BASIS TEST 20100819104903

INFO TBATG CONVERSION OF PRD N not needed BASIS TEST 20100819104903

START MOVE NAMETABS PRD 6 20100819104904 BASIS TEST 20100819104903

WARNING: System PRD. Warning. 20100819105204 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

START tp_getprots PRD P 20100819105204 BASIS TEST 20100819104903

WARNING: System PRD. Warning. 20100819105709 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System PRD. Warning. 20100819110109 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System PRD. Warning. 20100819110209 :

Regards

[Former Member]

Hi,

Then please check the log in dev_evt and please check the below link which might resolve your issue. Kindly try by setting system_pf parameter.

Regards,

Sharath

[Former Member]

Hi

already checked with system_pf parameter, pls find below logs for 17 aug

START imp single PRD 20100817170647 BASIS TEST 20100817170647

INFO TBATG CONVERSION OF PRD N not needed BASIS TEST 20100817170647

START tp_getprots PRD P 20100817170648 BASIS TEST 20100817170647

START imp single PRD 20100817171520 DDIC TEST 20100817171519

INFO TBATG CONVERSION OF PRD N not needed DDIC TEST 20100817171519

START tp_getprots PRD P 20100817171520 DDIC TEST 20100817171519

WARNING: System PRD. Warning. 20100817172025 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD pf=K:usr\sap\PRD\SYS\Profile\Default.pfl

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System PRD. Warning. 20100817172425 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD pf=K:usr\sap\PRD\SYS\Profile\Default.pfl

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System PRD. Warning. 20100817172526 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

instead of below error

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

it was giving

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD pf=K:usr\sap\PRD\SYS\Profile\Default.pfl

Regards

[Former Member]

Did you schedule the jobs via RDDNEWPP in each client including 000 with DDIC? Please check.

[Former Member]

See if following help you.

First stop the running transport

Steps:

1.From import monitor cancel the import

2.End the tp.exe processes at os level

3.Clear the relevant entries from trjob abd trbat tables.

Finally check following

Parameters for transport domain:http://help.sap.com/saphelp_nw04s/helpdata/en/3d/ad5bf64ebc11d182bf0000e829fbfe/frameset.htm

rdisp/mshost parameter is maintained in default.pfl

Check SAP note Note 449270 - Job RDDIMPDP is not triggered by sapevt

Hope this helps.

Manoj

[Former Member]

Hi,

From the log it says error as below. So, go to 000 client and execute RDDNEWPP from SE38 which will schedule the trigerring of RDDIMPDP for transport and this shoud resolve your issue. Even after doing above you get the error then kill all the tp process at OS level, delete the request from the queue, delete entries of table TRBAT and TRJOB. After that add the request to the queue and then try to import. Also check if the sufficient backgroubd process are available.

Even after trying above two methods still you are facing the issue then paste the latest content of SLOG.

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

Regards,

Sharath

Edited by: sharath Babu on Aug 18, 2010 1:16 PM

[Former Member]

Hi,

Check RSDDNEWPP is running in 000 & in ur production client... if not schedule it ..both the clients...

check the write permissions for usr/sap/trans/ ...

Delete the tranport from STMS and add it again check any files for that transport in usr/sap/trans/tmp dir and check the log dir , if you observe delete them...

[Former Member]

I hope you have already searched on forums. Just to make sure.

1. Review SAP notes 642464 & 449270. Check if transport parameters are set correctly in the default profile DEFAULT.PFL.

2. Check for port opening in service file and name entries in host file

Restart the SAP instance after these changes and then try the import again.

This should resolve the issue.

[nirmal_konchada]

Hi Bond,

Please check whether your /usr/sap/trans allows SIDadm to create files/folder in it.

Also let me know your Transport Domain and in which system r u transporting now.

Nirmal.