cancel
Showing results for 
Search instead for 
Did you mean: 

background job suddenly stop with Failed to create log for job

Former Member
0 Kudos

Dear Expert,

i checked SM21, error text: Failed to create log for job for job Z_WIBS_SAP_GR2

variable parts...Z_WIBS_SAP_GR2 09412801 %NEWSTEP.

how to check why this job failed?

Thanks & Regards,

Kelvin

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi ,

FIrst check on which client the background job is running.

Login to OS level and go to : /usr/sap/<SID>/SYS/global/<clientnumber>JOBLG.

a) first check the permissions for this folder and give 777

b) check and job log is created with size "0". if any log file is created delete that file and try to run the job again.

c) run the standard jobs to delete the OLD SPOOL logs and OLD JOG Logs .

Make sure the space is available in the /usr/sap/<SID>/ file system

Thanks & Regards

Yogesh

Former Member
0 Kudos

> i checked SM21, error text: Failed to create log for job for job Z_WIBS_SAP_GR2

> variable parts...Z_WIBS_SAP_GR2 09412801 %NEWSTEP.

> how to check why this job failed?

Hello,

Are you observing the same 'Failed to create log for job' error for all the jobs or only for job Z_WIBS_SAP_GR2 ?

Thanks

Former Member
0 Kudos

Hi,

It could be due to no disk space available. Check if there was any disk-space bottleneck during the time of Background job failure.

Regards,

Syed.

Former Member
0 Kudos

HI,

only for this particular Z_WIBS_SAP_GR2 job.

Thanks & Regards,

Kelvin

Former Member
0 Kudos

Hi Syed,

there is plenty of disk space.

Thanks & Regards,

Kelvin

JPReyes
Active Contributor
0 Kudos

Well, been a custom program have you tried to run it in dialog to check if error is spotted?... also you can do a full trace on the user running the step of the job to see if an error gets recorded.

Regards

Juan