topic Dead locks in Module pool program in Application Development and Automation Discussions

Dead locks in Module pool program

former_member213112 — Wed, 27 May 2015 12:26:40 GMT

Hi,

I have a Module Pool Program all the values will be modified into some ZTABLE, while going to this statement it is going to dump stating that Dead Locks with run time Error as DBIF_RSQL_SQL_ERROR and Exception as CX_SY_OPEN_SQL_DB. So what should I do now ? Should I Create locks in the table or is there any other solution. This case is there only in PRD so there is any test cases in QTY so please refer me the correct one.

Re: Dead locks in Module pool program

daniel_lippmann5 — Wed, 27 May 2015 12:37:57 GMT

Yes, you should create a locking/unlocking FM using the standard enqueue/dequeue mechanism.

Re: Dead locks in Module pool program

Former Member — Thu, 28 May 2015 06:33:49 GMT

Hi Avi,

From the best practice, yes, you always should lock one DBtable before you modify it. and handle this exception, like wait some seconds.

Are you sure above exception is related dead locks?

You can open TMG of that ztable with edit mode in QTY system, then run your program.

regards,

Archer

Re: Dead locks in Module pool program

former_member213112 — Fri, 12 Jun 2015 10:05:24 GMT

Hi Dengyong Zhang ,

Error text of the database: 'ORA-00060' deadlock detected while waiting for resource.

Regards,

Avinash

Re: Dead locks in Module pool program

MariaJooRocha — Fri, 12 Jun 2015 10:10:06 GMT

Hi,

Analyze the use of commits.

Regards,

Maria João Rocha

Re: Dead locks in Module pool program

RaymondGiuseppi — Fri, 12 Jun 2015 14:07:17 GMT

Welcome to the Oracle world of lock during insert, start reading 84348 - Oracle deadlocks, ORA-00060, then either ask basis/database admin or adapt your code.

Hint: Are multiple users inserting at same time, if yes use some lock concept to minimize concurrent usage of unique indexes.

Regards,

Raymond