ERROR SPAM/SAINT UPDATE 70041

[Former Member]

Hi Everyone, I need your help with a problem in the system:

I have ECC 6.0 with SPAM 70027, SAPBK70014 and SAPBA70014, when i try to update SPAM, the system shows the following error:

(This is the tp system LOG)

WARNING: System CBD. Warning. 20110321103515

ERROR: The following call returned with exit code 126:

ERROR: sapevt SAP_TRIGGER_RDDIMPDP -t name=CBD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

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

I checked the dev_evt log and it shows me this:

Mar 22 14:41:55 2010

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

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: cbides

SAP message server service (new): 3902

SAP message server service (old): sapmsCBD

Event sent to server cbides_CBD_02

The update of SPAM/SAINT continuos in a cycle and does not end until the process is canceled by the SM50. The same problem occurs with te Support Packages.

I ran reports to delete and reschedule jobs (RDDNEWPP) to start the routine. But the error still happens. This problem does not occur with transport orders only with the SP.

Please appreciate your help with this error.

Edited by: Damalys Gutierrez on Mar 23, 2011 4:18 PM

[Former Member]

Hi,

After changing the parameter to increase the no of work process, do you see 4 BTC process in SM50. If you have changed it only in instance profile then you need to restart the sap application or you can dynamically increase the BTC process using the operation mode.

Also when you are starting the SAINT update, check in SM37 do you see any finished RDDIMPDP job ?

Regards,

Neeraj

[Former Member]

Hi,

Can you check if you have enough number of free background work process when you are starting the spam/saint update?

Also run the report rddnewpp for 000 client also and see if it has schedule a job in SM37 for sap_trigger_rddimpdp event.

Regards,

Neeraj

[Former Member]

Hi

I was ran that report and does not solve the problem.

How I checked the free number of background process space?

The sap_trigger_rddimpdp event already exists. It was Applied also the note 1132422 for DEADLOCKS and the problem persists.

I do not know what else I can do.

[Former Member]

Damalys,

The error is "ERROR: Background jobs cannot be started."

Please check SM50 to see if there are more than 2 BTC processes free: no processes are running. You can also run SM37 and sort the jobs by "Delay" and see if there are any jobs waiting more than 60 sec. If so, you may have to increase the number of BTC processes.

Also, please check SM61 and see if a sever defined as a background controller. Is there are job server group defined? If so, is your host listed in that group?

If there are no issues with the BTC processes, could you please send the transport logs from /usr/sap/trans/log? Those may shed more light. Make sure that you ran RDDNEWPP at 000 at SE38 and the RDDIMPDP job is in the "Scheduled" status in SM37.

Neval

Edited by: Neval Ozturk on Mar 23, 2011 6:50 PM

Edited by: Neval Ozturk on Mar 23, 2011 6:51 PM

[Former Member]

Hi,

In TX: SM50 there is 3 BGD processes (1 on hold and 2 waiting). I have changed the parameter in profile to 4 processes now.

In TX: SE37 there is no delay jobs.

In TX: SM60 the server controller is defined and there is no group.

Thanks for your help.

[Former Member]

Damalys,

Could you please go to AL11 --> DIR_TRANS > log> find the latest ALOG and SLOG files and send the errors?

Thanks.

[Former Member]

Hi,

SLOG

START DD IMPORT CBD H 20110323151436 RCARTAYA cbides 20110323151335

STOP DD IMPORT CBD H 20110323151440 RCARTAYA cbides 20110323151335

START tp_getprots CBD J 20110323151440 RCARTAYA cbides 20110323151335

WARNING: System CBD. Warning. 20110323151449 :

ERROR: The following call returned with exit code 126:

ERROR: sapevt SAP_TRIGGER_RDDIMPDP -t name=CBD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

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

ALOG:

ALL CBD.ALL t 0000 20110323150214 RCARTAYA cbides

ALL CBD.ALL t 0000 20110323150214 RCARTAYA cbides

ALL CBD.ALL t 0000 20110323151106 RCARTAYA cbides

ALL CBD.ALL t 0000 20110323151144 RCARTAYA cbides

ALL CBD.ALL t 0000 20110323151330 RCARTAYA cbides

SAPKD70041 CBD.ALL m 0000 20110323151330 SAPUSER RCARTAYA cbides

SAPKD70041 CBD.ALL L 0004 20110323151333 SAPUSER RCARTAYA cbides 20110323151331

SAPKD70041 CBD.ALL P 0004 20110323151335 SAPUSER RCARTAYA cbides 20110323151334

SAPKD70041 CBD.ALL H 0004 20110323151440 SAPUSER RCARTAYA cbides 20110323151335

[Former Member]

Damalys,

OSS note "Note 449270 - Job RDDIMPDP is not triggered by sapevt" addresses this issue. Please check this note.

Neval

[Former Member]

Hi,

I can´t solve the problem with that note.

The import of SPAM still gives an error in the IMPORT PROPER phase.

Regards