Financial - JDE1 (MOSC)

MOSC Banner

Deadlock caused by F0911 and F0011

edited Dec 7, 2019 4:02AM in Financial - JDE1 (MOSC) 1 commentAnswered

Hi all,

Is it possible that these table can cause a deadlock when updating each other? Could it be that the user cancels, closes JDE, etc.. which causes blocking?

Blocking process

UPDATE PRODDTA.F0011 SET ICICUT=:BND1,ICICU=:BND2,ICIST=:BND3,ICIAPP=:BND4,ICAICU=:BND5,ICUSER=:BND6,ICDICJ=:BND7,ICNDO=:BND8,ICBAL=:BND9,ICBALJ=:BND10,ICAME=:BND11,ICDOCN=:BND12,ICDRSP=:BND13,IC52PP=:BND14,ICCBP=:BND15

WHERE ( ICICUT = :KEY1

AND ICICU = :KEY2 )

Blocked process

DELETE FROM PRODDTA.F0011 WHERE ( ICICUT = :KEY1 AND ICICU = :KEY2 )

In other ocasions

INSERT INTO PRODDTA.F0911 (GLKCO, GLDCT, GLDOC, GLDGJ, GLJELN, GLEXTL, GLPOST, GLICU, GLICUT, GLDICJ, GLDSYJ, GLTICU, GLCO, GLANI, GLAM, GLAID, GLMCU, GLOBJ, GLSUB, GLSBL, GLSBLT, GLLT, GLPN, GLCTRY, GLFY, GLFQ, GLCRCD, GLCRR, GLHCRR, GLHDGJ, GLAA, GLU, GLUM, GLGLC, GLRE, GLEXA, GLEXR, GLR1, GLR2, GLR3, GLSFX, GLODOC, GLODCT, GLOSFX, GLPKCO, GLOKCO, GLPDCT, GLAN8, GLCN, GLDKJ, GLDKC, GLASID, GLBRE, GLRCND, GLSUMM, GLPRGE, GLTNN, GLALT1, GLALT2, GLALT3, GLALT4, GLALT5, GLALT6, GLALT7, GLALT8, GLALT9, GLALT0, GLALTT, GLALTU, GLALTV, GLALTW, GLALTX, GLALTZ, GLDLNA, GLCFF1, GLCFF2, GLASM, GLBC, GLVINV, GLIVD, GLWR01, GLPO, GLPSFX, GLDCTO, GLLNID, GLWY, GLWN, GLFNLP, GLOPSQ, GLJBCD, GLJBST, GLHMCU, GLDOI, GLALID, GLALTY, GLDSVJ, GLTORG, GLREG#,

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center