Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Problem when scheduled in background

Former Member
0 Likes
789

Hi i run a report thru a job which will update a z-table with the current time/date/pgm name/werks..

table is updated as below.

zsa0_batch_cnfg-rdate = sy-datum.

zsa0_batch_cnfg-rtime = sy-uzeit.

zsa0_batch_cnfg-repid = sy-cprog.

zsa0_batch_cnfg-werks = c_zero.

Last night we scheduled 4jobs. 3 jobs ran successfully and the last failed (dumped)with the following error arrow pointing at the modify stmt.key field of the table are REPID AND WERKS.

The program "ZBA0R_MRS_EXTRACT" was started as a background job.

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in the procedure "UPDATE_BATCH_CNGF" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.

now my question is when the first 3jobs are success y shud the 4th fail.and i dont understand that error given there.

any clues?

regds

kiran

Hi i run a report thru a job which will update a z-table with the current time/date/pgm name/werks..

table is updated as below.

zsa0_batch_cnfg-rdate = sy-datum.

zsa0_batch_cnfg-rtime = sy-uzeit.

zsa0_batch_cnfg-repid = sy-cprog.

zsa0_batch_cnfg-werks = c_zero.

Last night we scheduled 4jobs. 3 jobs ran successfully and the last failed (dumped)with the following error arrow pointing at the modify stmt.key field of the table are REPID AND WERKS.

The program "ZBA0R_MRS_EXTRACT" was started as a background job.

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in the procedure "UPDATE_BATCH_CNGF" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.

now my question is when the first 3jobs are success y shud the 4th fail.and i dont understand that error given there.

any clues?

regds

kiran

4 REPLIES 4
Read only

Former Member
0 Likes
673

Hi Kiran ,

Were all these 4 jobs running at the same time???...what i mean to say here is there might be a case that when one job is trying to update the database table the other job also tried to update the custom table which might have resulted in this dump. So inorder to avoid these you can use locks.

Regards,

Swaroop

Read only

Former Member
0 Likes
673

Hi swarup,

4 jobs are scheduled at different time with a span of 3hrs difference bt each job.

any more clues?

kiran

Read only

0 Likes
673

Kiran,

zsa0_batch_cnfg-rdate = sy-datum.

<b>get time.</b>

zsa0_batch_cnfg-rtime = sy-uzeit.

zsa0_batch_cnfg-repid = sy-cprog.

zsa0_batch_cnfg-werks = c_zero.

and can you show the modify statement which you are using to modify the ZTABLE.

Regards

Vijay

Read only

Former Member
0 Likes
673

hi vijay..

those sy-variables worked fine 4 the 1st 4jobs.

and its a simple modify stmt

zsa0_batch_cnfg-rdate = sy-datum.

zsa0_batch_cnfg-rtime = sy-uzeit.

zsa0_batch_cnfg-repid = sy-cprog.

zsa0_batch_cnfg-werks = c_zero.

modify zsa0_batch_cnfg.

any more info u req?

kiran