Background jobs are all cancelled on some specific App Servers

[former_member211576]

Hi expert,

We found background jobs are all cancelled on some specific additional application servers. First, tccap51_tp1_06 and then tccap57_tp1_21. There is nosm36-1.jpgsm36-2.jpg job logs in SM36. It might need to analyze dev_wxx trace files but I don't know how to get started. Please check the attachments and help ASAP, thanks.

[alichtenau]

Hi Dennis,

please attach the log of a broken job and the respective dev_w* file for further analysis.

Cheers,
Andreas

[Sriram2009]

Hi Dennis.

Thanks for you info, Could you share the bg job log and at same time what is the error message in sm21 log?

Regards

SS

[Sriram2009]

Hi Dennis.

1. For BG job is not require to check the dev_wXX files, you can check in the Transaction code SM37 to see the job log

2. Still if you want to see the dev_wxx files, using the transaction code AL11 on App instance select the DIR_HOME in that you can find tall work process files

Regards

SS

[former_member211576]

Hi SS,

Yes, I know AL11 and I know to read the dev_wXX files. The problem is I can't understand the messages here.

Sometimes search notes and google helps for error messages in dev_wXX trace files but most of the time it does not.

[Sriram2009]

Hi Lee.

1. check the cancelled BG jobs log? & SM21 log reason details

2. Is this BG Job scheduled in those app server to execute? check the released BG jobs.

3. Why you are not created BG job grouping? Refer the SAP Wiki link about the Batch server grouping.

https://wiki.scn.sap.com/wiki/display/SI/SM61+-+Batch+Server+Group

Regards

[former_member211576]

Hi SS,

1 & 2: I have answered above.

3. We do. You mean SM61 -> "Job-Servergruppen", right? We do create a few job server groups but most of jobs scheduled with assgining a server group. So it can run on any available SAP instances.

[FredericGirod]

When you click on the job line, you did not have a log ?

Did you check transaction SLG1 ?

Did you check transcation SM21 ?

[former_member211576]

Thanks for your reply.

Ans1: Yes, No log entries are available for the selected job. I think SAP disp+work.exe failed to create TEMSE objects in SAP directories(/sapmnt).

Ans2: No, I don't even know this transaction code but I did it just now and the information is related to transaction code: CS02. No information is jobs related.

Ans3: No. Why do I miss this very basic transaction code. I check it just now. Unfortunately, there is no related information.

--------------

I find the source of the problem somehow. I restart one SAP instance and I found it failed at sapcpe.exe. I am shocked. I try to access SAP directories using <Domain>\<sid>adm and it is okay.

The solution is to restart SAPTP1_06 and start SAP instance again and everything is normal right now.

[FredericGirod]

Good news

thanks for feedback