Background job RDDIMPDP could not be started or terminated abnormally. - Solution Manager

[Former Member]

Hi everybody,

We've problems importing updates using SPAM transaction in our Solution Manager 7.1.

The process freeze during the import and the log show this:

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

WARNING: System S04. Warning.        20130206143745 :

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.

I was trying to see the RDDIMPDP Job using the SM37 transaction but I get this error message:

Runtime Error

Syntax error in program CL_ST22_TOOLS=======

The SPAM shows that the process stoped at this phase:

Import of queue for the SAP_BASIS IMPORT_PROPER

This is the information of my system:

Windows 2008 R2

SAP Solution Manager 7.1

Oracle 11.2.0.3.0

Kernel is 720, patch 401

SPAM / SAINT are updated to the latest level.

This is the Queue defined in SPAM:

SAPKB70210                        Basis Support Package 10 for 7.02

SAPKA70210                        ABA Support Package 10 for 7.02

SAPK-70210INPIBASIS          PI_BASIS Support Package 10 for 7.02

SAPKW70210                       BW Support Package 10 for 7.02

SAPK-70208INSAPBSFND     SAP_BS_FND 702: SP 0008

SAPK-70107INWEBCUIF        WEBCUIF 701: SP 0007

SAPKU70107                        BBPCRM 701: SP 0007

SAPK-25003INIWFND            IW_FND 250: SP 0003

SAPKITL705                          ST 710: SP 0005, CRT for SAPKB70210 and SAPKU70107

Any help is welcome,

Best regards,

Junior Vásquez

[Former Member · Accepted solution]

See the developer trace dev_evt to determine why the event hasn't been delivered. RDDIMPDP is triggered by an event sent by sapevt. You can send the event manually so that you can proceed with the SP update but make sure you fix the configuration in the long run.

[Former Member · Accepted solution]

Hi Samuli,

This is what the dev_evt have:

Thu Feb 07 07:52:10 2013

Trace File of External Event Raiser (Level=0, Append=0)

******* Complete Call: *******

sapevt.exe

SAP_TRIGGER_RDDIMPDP

name=S04

******* End of Call *******

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: SRVSSM00

SAP message server service (new): 3900

SAP message server service (old): sapmsS04

Event sent to server SRVSSM00_S04_00

It look's like the event has been triggered, what else do I need to check?

I was thinking that maybe if start SGEN transaction it could help, what do you think?

Thank you very much.

Junior Vasquez

[Former Member · Accepted solution]

Hi everybody,

This is what I get each time that I try to start a transaction. I was trying to start ST22, SM37, SM50, SM66 and the what I see is that the system start to compilate the programs in the bottom of the screen and after some compilatons I get the same error. That's why I think the problem can be solved executing the SGEN, but I'm not sure. What everybody think about it.

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

Hi,

Refer to this thread.

http://scn.sap.com/thread/3202223

Regards,

Mudasir.

[Former Member · Accepted solution]

Hi Mudasir,

I did try that with the same results.

Regards,

Junior Vasquez

[Former Member · Accepted solution]

Hi,

Please attach the ST22 Dump you are getting.

Please  click on goto menu -> import log -> TP system log . Please attach the screenshot too.

Secondly please attach ULOG as well as SLOG too.

The information you have provided doesn't have much information to provide any suggestions.

Thanks and Regards,

Vimal

[Former Member · Accepted solution]

Hi Maria,

I can't use ST22 transaction because of the syntax error dumb.

This is what I have in the SPAM log:

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

WARNING: System S04. Warning.        20130207084218 :

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.

This message repeat countless time.

This is what I have in the ULOG file:

APServiceS04 20130206143659 RFC: tp SHOWPARAMS S04 pf=\\SRVSSM00\sapmnt\trans\bin\TP_DOMAIN_S04.PFL -Dtransdir=\\SRVSSM00\sapmnt\trans  (pid=9548)

APServiceS04 20130206163036 RFC: tp SHOWPARAMS S04 pf=\\SRVSSM00\sapmnt\trans\bin\TP_DOMAIN_S04.PFL -Dtransdir=\\SRVSSM00\sapmnt\trans  (pid=5196)

APServiceS04 20130206163036 RFC: tp CONNECT S04 pf=\\SRVSSM00\sapmnt\trans\bin\TP_DOMAIN_S04.PFL -Dtransdir=\\SRVSSM00\sapmnt\trans  (pid=5196)

APServiceS04 20130206163039 RFC: tp IMPORT all S04 pf=\\SRVSSM00\sapmnt\trans\bin\TP_DOMAIN_S04.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Dwatchparallelprocesses=yes -Dparallel=0 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=\\SRVSSM00\sapmnt\trans  (pid=5196)

APServiceS04 20130207085314 RFC: tp SHOWPARAMS S04 pf=\\SRVSSM00\sapmnt\trans\bin\TP_DOMAIN_S04.PFL -Dtransdir=\\SRVSSM00\sapmnt\trans  (pid=14384)

And this is what I have in the SLOG file:

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

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

Hi,

Please try the following.

1. Update your kernel , as well as TP  to the latest version

2.Stop the SAP system & DB system.

3.Check in OS level,  whether any TP processes is running.If yes, please stop it.

4. Start the DB & SAP system.

5. Try to start the import again and check whether it works.

Thanks and Regards,

Vimal

[Former Member · Accepted solution]

Hi Maria,

Before start the process I updated the system.

This is what I have:

SPAM/SAINT Version 7.02/0047

Kernel 720, patch 401

tp version 380.04.07 (release 720, unicode enabled)

I try restarting the system but nothing happen.

I also tried "tp import all" from the OS level without help.

What do you think about executing SGEN and after that try the import again?

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

Please login in as ddic user in 000 client and try to execute the report  RDDNEWPP, which will start the job RDDIMPDP.

Please give a try and check whether it works.

Also please go SM50 and see whether all the background jobs are running or in waiting status.

[Former Member · Accepted solution]

Hi Maria,

The report RDDNEWPP executed successfully. After that i try the import again.

Using the MMC to monitor the WP I can see that nothing is running on the system and the SLOG log show this:

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

START imp all              S04        20130207100020              JVA01        SRVSSM00 20130207100020040  

INFO: event SAP_IMPORT_START triggered successfully

INFO  TBATG CONVERSION OF  S04 N      not needed                  JVA01        SRVSSM00 20130207100020040  

START tp_getprots          S04 P      20130207100021              JVA01        SRVSSM00 20130207100020040  

WARNING: System S04. Warning.        20130207100231 :

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 S04. Warning.        20130207100427 :

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

Trying to monitor the process with SM50 give me the same syntax error mention before.

The Import is frozen and the status bar show "imp all" message.

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

Hi everybody,

What about executing SGEN transaction?

Can anybody advise me in this?

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

SGEN just complies the program so that compliation is not required at the run time

You can also give a try by running SGEN.

But it seems that SGEN is not the root cause for the issue.

Please try this way.

1. Start the import again.

2. parallel see what is the work processes running.

3. Check which work processes is failing.

4. Go to work directory and check that particular work process trace file and check whether we can find any useful information. I hope we can find it.

Number range for work processes starts from 0..

for example

0  dia

1 dia

2  dia

3 bgd

4 bgd

5 spo

SUpport work process 3 is failing. go to work directory, and check dev_w3 and see any information is available in the trace file.

Thanks and Regards,

Vimal

[Former Member · Accepted solution]

Hello Junior,

The support pack SAPKB70210 which you installing has a known

error where it dumps for most of the transactions. Check the below note and apply the corrections manually ( as SNOTE won't work ) and run the mentioned report.

Note 1700109 - System Dumps Due to New Inactive ALV BAdI Spots

Regards,

Mudasir.

[Former Member · Accepted solution]

Dear Mudasir,

I was trying to create the report in SE38 as the note say, but after pressing the create button I get the same DUMB "Syntax error in program CL_ST22_ TOOLS====".

I looks like this note is the answer for my problem, but I can't implement the correction.

I open a case with SAP I hope they can help me to solve this problem.

Best regards,

Junior Vasquez

[Former Member · Accepted solution]

I don't want to be rude or anything but I think no one so clueless of SAP BASIS should be doing what you are doing. Better get help from an experienced SAP BASIS consultant before proceeding. Unless there is an error in the SAP components, SAP support won't help you. SAP Consulting will, for a fee.

[Former Member]

Hi everybody,

I will let the discussion open until I get an answer from SAP. As soon as I get a solution from them I'll post it here.

Thanks to everyone for trying to help.

Regards,

Junior Vasquez

[Former Member]

Hi Junior Vasquez,

This error root cause will be noted in log file in transport tmp directory

/usr/sap/trans/tmp  ( Pl change the path accordingly to OS version)

See the latest file in time stamp and reason will mentioned their lie some objects could not be activated

or Database error.

I had same  error

"

Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running"

But after applying all the solutions which are already mentioned in this post not able to resolve the issue.

Later in  log file in /usr/sap/trans/tmp  find that 3 objects could not be activated which is related to SLO deletion objects which was left after SLO project finished last month and in DDIC phase could not activate those objects.

SAP notes mentioned to delete the object manually and then I was able to proceed with support package upgrade.

So error RDDIMPDP some time is misleading and nothing to do with it.

Pl check and paste the log here for further troubleshoot if issue still exist.

Thanks,

Anit

[vinod_menon4]

Hello Everyone,

Did you find the root cause of this error. We are also stuck in the same situation. Any suggestions!

Regards,

Vinod Menon

[Former Member]

Hi Vinod,

Please take a look at the note : Note 1700109 - System Dumps Due to New Inactive ALV BAdI Spots.

Best regards,

Junior V.

[Former Member]

HI,

can you please attach the complete DUMP?

Please check with the is the tp log saying...

Please attach the ULOG & SLOG from  the log directory.

Thanks and Regards,

Vimal

[shyam_dontamsetty]

Hi Vasquez ,

First see the status of your RDD* jobs in your system, goto SM37 -> filter out the jobs RDD* ,check here if they are in released or not. To find out what caused RDDIMPDP  not to trigger during import,you need to find the recent details form the trace file dev_evt from work directory,analyze SM21 logs during the time period of import.

Can you give post SM21 log details during the period and also dev_evt trace file for identifying the exact problem.

Best Regards,

Shyam

[Former Member]

Can you post the TP log please.

Thanks,

Santanu