Backgroud job failing

[Former Member]

Hi Guru's.

In HR-Production System one is job is running every 20min and it is canceling in a week twice.If i click job logs i am getting below error.

No log entries are available for the selected job

Could, you please suggest where i want to check.

Regards,

Deve

[Former Member]

Hello Deve,

1083841 note referts to the errors in the wp trace.

According to it this is not a big issue and can be ignored.

Are u still facing the backgroudn job failures

Rohit

[Former Member]

Hello Rohit,

The Sap note 1083841 is not usefull this problem.Every day background jobs are failing without logs.

I am still facing the backgroudn job failures

Regards,

Deve

[Former Member]

Hi,

Please got to Sm37

and double click on the job which got canceled.

and click on job details.It will show on which work process and application server the job has runned.

Take the PID and goto SM51 and double on the application server.

It will take you to the SM50

Please check the work process trace on which the job has runned

Here you can find the error log.

Regards

Sreedhar Reddy

[Former Member]

Hi Sreedhar,

The work process trace on which the job has runned. The error log is

L SXPG: 2009/02/17 08:07:39 978923

L

L Tue Feb 17 09:02:30 2009

L SXPG: start of SXPG_STEP_XPG_START

L SXPG: 2009/02/17 17:02:30 446280

M

M Tue Feb 17 20:27:11 2009

M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_C

OMMIT failed [thxxtool3.c 261]

B ComRolHook(BEFORE_COMMIT, free_all) failed

B db_con_commit received an error return code in before-commit action

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_C

OMMIT failed [thxxtool3.c 261]

...skipping...

L SXPG: 2009/02/17 08:07:39 978923

L

L Tue Feb 17 09:02:30 2009

L SXPG: start of SXPG_STEP_XPG_START

L SXPG: 2009/02/17 17:02:30 446280

M

M Tue Feb 17 20:27:11 2009

M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 261]

B ComRolHook(BEFORE_COMMIT, free_all) failed

B db_con_commit received an error return code in before-commit action

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 261]

B ComRolHook(BEFORE_COMMIT, free_all) failed

Regards

Deve

[Former Member]

Hi,

M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed

For the above, i could find snote 1083841 which may help to come out this issue.

As per the snote you can ignore this message.

check the tablespaces sizes, because it happens when there is no enough space,

Check the TemSe consistency and delete the inconsistent objects.

And follow the note.

Execute SP12 - Temse Data Storage->Consistency Check.

You can delete all show in red. Repeat this, till its Consistent.

Ensure there is enough space in the tablespace.

looks like you have Shared mem issue as well, to Clear the issue on Window server, just reboot the server.

Regards

Sreedhar Reddy

[Former Member]

Hi Sreedhar Reddy,

Thank you for quick response.The table space have enough free space and auto extended status.

Every weekend we are restarting the HR(AIX) System.I checked the spool consistency it was good.

Regards

Deve

[Former Member]

Hi,

As per as error messages in trace are concerned, i think you can ignore as per the following SAP note.

[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083841]

I assume you are checking these failed jobs in SM37. Could you post job log?

Hope this helps.

Manoj

[markus_doehr2]

SAP has about 550,000 programs - we can´t guess out of that mass which of those is failing if you don´t tell us.

Markus

[Former Member]

HI,

The following Production jobs were canceled today, and no job log are available ,

HR_SWEEPER_2.0_115

HR_SWEEPER_2.0_120

HR_SWEEPER_RETAIL_CA

HR_SWEEPER_RETAIL_CA

HR_SWEEPER_RETAIL_CA

HR_SWEEPER_RETAIL_CA

HR_SWEEPER_RETAIL_CENTRAL

HR_SWEEPER_RETAIL_CENTRAL

HR_SWEEPER_RETAIL_CENTRAL

SAP_CCMS_CPH_HRCOLL

SAP_COLLECTOR_FOR_PERFMONITOR

Z_HR_B_S_RECRUITMAX_OUTBOUND

Regards,

Deve

[markus_doehr2]

Hi Dave,

those are the job names but not the programs that are executed.

> HR_SWEEPER_2.0_115

> HR_SWEEPER_2.0_120

> HR_SWEEPER_RETAIL_CA

> HR_SWEEPER_RETAIL_CA

> HR_SWEEPER_RETAIL_CA

> HR_SWEEPER_RETAIL_CA

> HR_SWEEPER_RETAIL_CENTRAL

> HR_SWEEPER_RETAIL_CENTRAL

> HR_SWEEPER_RETAIL_CENTRAL

> SAP_CCMS_CPH_HRCOLL

> SAP_COLLECTOR_FOR_PERFMONITOR

> Z_HR_B_S_RECRUITMAX_OUTBOUND

According to your error message I would assume that writing to the filesystem (/usr/sap/<sid>/global) is not working. Is the filesystem available? maybe full?

Markus

[Former Member]

Hi Markus,

Thank you for quick replay. The file system /usr/sap is 21%.Only cancel jobs logs are not showing.

I am getting below error.

No log entries are available for the selected job

Can you please suggest.

Regards,

Deve

[Former Member]

Hi

Can you check what logs are being displayed in SM21 corresponding to that cancelled background jobs

Rohit

[Former Member]

Hi Rohit,

I checked in SM21 logs are not recoding. It is empty and logs are not genearting.

Regards,

Deve

[Former Member]

do you have application servers also in your SAP system?

If yes check on what host does the cancelled backgroudn jobs are running,then go to that host and check for the background job logs?

this might be helpful if you have app.servers

Let me know of the result

Rohit

[Former Member]

Hi,

Check the log for all remote hosts if u have more than one instance.

Since you said few times jobs getting cancelled, Check the time BG jobs are getting cancelled is the time stamp same for all jobs and on every day at same time or are they different. And monitor if there are enough BG process available when jobs getting cancelled.

U said no logs getting generated, check if the log parameters are properly set. Is this new installation.

regards,

Raju.

[Former Member]

Hello Deve,

Refer to the Note 963

This can be quite useful

Rohit

[Former Member]

Hi Rohit,

I go through the sapnote. As per SAP NOTE all parameters already exists.

Could, you please help me.

Regards,

Deve

[Former Member]

well u havent told me yet that do you have application servers in your production system

Rohit Goyal

[Former Member]

well I have come across a note 93732,though this is valid for a old release but still go through it once.

check for following things:

1. Look for the pattern of the cancelled jobs,do they particularly fail at around one time or is it distributed?

2. You can think of increasing the no. of background processes

3. do you have application servers in your system?

4. Check the note 37104 for error anaylsis of background system

do the following things and let me know the results

Rohit