cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in importing request

Former Member
0 Kudos

Hi All,

I installed new system ECC 6.0 with EHP1 ready on Windows 2008 cluster environment and Oracle 10g database.

The installation completed successfully and fail-over is also happening perfectly. I did STMS and there is no inconsistency as well. I made three system configuration in which my DEV system is Domain controller for this all 3 ERP system.

Today when I tried to import a request into PRD, it's not starting. Only the truck symbol is showing in status, but no progress. I guess tp is unable to write the file data into database.

The import monitor show 'import started' as a status. also there is no log file generated.

Because of this issue I am unable to start my EHP4 upgrade also.

Regards,

Ramesh.

Accepted Solutions (0)

Answers (7)

Answers (7)

patelyogesh
Active Contributor
0 Kudos

Are you using central location for TRANS directry?

If YES then make sure ass SAPServiceSID and sidadm users have full access to that directory.

I guess you must be using mountpoints as your drives make sure permissions are correctly setup on mounts and roots.

Make sure atleast one BG process available on all Application server to you can run transport job.

Please let me know if you still facing this issue.

Yogesh

Former Member
0 Kudos

Hi,

Please do check as note 642464 to check any possible reason, like

services file for sapms<SID>.

Besides, would you please double check the access rights on

".....
profile\DEFAULT.PFL"?

Please check parameter setting carefully according to note #449270

Regards

Bhuban

RKFL

Former Member
0 Kudos

Hi Bhuban,

I think my solution is hidden in the note 449270, can you please elaborate the settings in this note as I feel quite difficult to understand this note.

See I have HA installation on Windows 2008 cluster, and my systems are like this.

1. Virtual host - Vhost - having database and message server and ASCS instance on it.

2. Primary host - PRD1 - having CI and all resources of cluster in this host

3. Secondary host - PRD2 - Having DI on this host.

My parameters in default profiles shows below values

rdisp/mshost = Vhost

rdisp/msserv = sapmsEMP

Please provide me some detail explanation about my doubts, so that I can cross this tunnel with taking your suggestions as a torch.

Regards,

Ramesh.

patelyogesh
Active Contributor
0 Kudos

Go to STMS >> System Overview >> select system and double click on it >> Select Transport tool TAB >>

Make sure you have SYSTEM_PF parameters with
<HOSTNAME>\sapmnt\<SID>\SYS\profile\default.pfl

If you are able to see this parameter then add this to Transport profile.

Please let me know if you still have question.

Yogesh

Former Member
0 Kudos

Hi All,

The problem solved, it was because 2 days back windows firewall was switched on by our network administrator without informing us.

I switched it off and everything is working fine.

Thanks for your great contribution.

Regards,

Ramesh.

Former Member
0 Kudos

Hi,

Specify the virtual host name in the Windows Environment ( run-drivers-etc-hosts) there you specify the host name of CI and DB.

Regard,

Jeeva

Former Member
0 Kudos

Hi Ramesh,

1.Hanging transports are in most cases caused by either

Not correctly scheduled RDDIMDP jobs (ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=EMP, ERROR: Background jobs cannot be started.)

2.killed/died tp processes

Please also check sap note 556941

3.check for RDD* jobs is in active or sheduled in SM37

if not shedule it by running report RDDNEWPP in SE38/SA38, it will shedule the RDD* jobs

4.Please check the system and Host entries in /etc/hosts for CI & DB. and check the wp status for the jobs.

Regards

Jeeva

Former Member
0 Kudos

Check /usr/sap/trans/tmp/<SID>.LOB file

Please check note #12746 for this problem. Basically all you need to do is to stop any tp/R3trans process running on the OS level, move all .LOB or .LOC files from /usr/sap/trans/tmp to another location. Then restart the the process. Also refer to note #690449 and #132536 for more information.

Former Member
0 Kudos

Hi All,

Below are the log for tp

START TRANSMIT BUFFER ENTR EMP g 20110619131158 TMSADM PRD1EMS

STOP TRANSMIT BUFFER ENTR EMP g 0000 20110619131158 TMSADM PRD1EMS

START TRANSMIT BUFFER ENTR EMP g 20110621015838 BASIS PRD1EMS

STOP TRANSMIT BUFFER ENTR EMP g 0000 20110621015838 BASIS PRD1EMS

START imp single EMP 20110621015923 BASIS PRD1EMS 20110621015923130

INFO TBATG CONVERSION OF EMP N not needed BASIS PRD1EMS 20110621015923130

START MOVE NAMETABS EMP 6 20110621015923 BASIS PRD1EMS 20110621015923130

WARNING: System EMP. Warning. 20110621020224 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=EMP

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 EMP P 20110621020224 BASIS PRD1EMS 20110621015923130

WARNING: System EMP. Warning. 20110621020729 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=EMP

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

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

START imp single EMP 20110621020954 BASIS PRD1EMS 20110621020954646

INFO TBATG CONVERSION OF EMP N not needed BASIS PRD1EMS 20110621020954646

START tp_getprots EMP P 20110621020954 BASIS PRD1EMS 20110621020954646

WARNING: System EMP. Warning. 20110621021130 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=EMP

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 EMP. Warning. 20110621021230 :

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.)

WARNING: System EMP. Warning. 20110621021500 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=EMP

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

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

Regards,

Ramesh.

Former Member
0 Kudos

Have you scheduled the jobs RDDNEWPP in 000 and 100?

Also check your hostname if it is resolving correctly

Edited by: Venkatesh Koukuntla on Jun 21, 2011 11:54 AM

Former Member
0 Kudos

Hi Venkatesh,

I scheduled in SA38 on high priority, and its showing the message that job scheduled successfully.

But I couldn't find any job in SM37 for DDIC user.

Also, can you please elaborate where to check this host name settings, because this is cluster installation and instead of showing the virtual hostname, its showing me PRD1 system. I don't have idea where to change it.

Regards,

Ramesh.

Former Member
0 Kudos

Hi Ramesh,

I don't think this has anything to do with hostname. The reason you can't see the job in sm37 is because RDD* jobs are even controlled i think. So please put a * in the event field in SM37 1st screen and then search again.

Further, I think you should also check sap_evt log file to see why background jobs are not being triggered.

Now, search for the job and tell us what happened to it. Also, check availability of trans directoryand space availability in it. You should most probably get error info in sm21 also if the job is failing.

Regards,

Shitij

Former Member
0 Kudos

Hi Ramesh,

As Deepthi suggested please provide the import logs.

Also please check at OS level if multiple tp are running. You can check the same in task manager. If yes, please delete all the tp.exe in the process list in task manager. And start the import the import again.

Please check in Sm37 if RDD* jobs are getting triggered. If not, execute RDDNEWPP in 000 client and the client in which you are doing the import. Please use DDIC user id to execute RDDNEWPP report in both the client.

Please let us know if you are still stuck with the import.

Regards,

Vishi Rajvanshi

Former Member
0 Kudos

Hi Ramesh,

What is there in TMS alert log ??

Thanks,

Deepthi