Results 1 to 2 of 2
  1. #1
    Join Date
    Aug 2002

    Question Unanswered: Is this deadlock occuring because of INITTRANS parameter?

    This is the Oracle trace generated for the deadlock. Can somebody tell me if it is caused due the INITTRANS/PCTFREE param.

    Current SQL statement for this session:
    update eb_status set fx_contract_ref = :1 where bank_reference = :2
    The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock:
    Deadlock graph:
    ---------Blocker(s)-------- ---------Waiter(s)---------
    Resource Name process session holds waits process session holds waits
    TX-0005000a-001ad0b0 50 89 X 38 28 X
    TX-000a000e-001ab5b1 38 28 X 50 89 S
    session 89: DID 0001-0032-00000002 session 28: DID 0001-0026-0006F930
    session 28: DID 0001-0026-0006F930 session 89: DID 0001-0032-00000002
    Rows waited on:
    Session 28: obj - rowid = 0000877C - AAAId8AAEAACm3UAAi
    Session 89: no row
    ================================================== =

    Please observe that the "Session 89:" line has a 'no row'.

    Thanks in advance!

  2. #2
    Join Date
    Aug 2002
    Chennai, India
    The value 'No row' for session 89 indicates that u have a problem with the initrans and the pctfree parametres. Also u have a problem with session 29 which indicates a problem with your application.

    But Iam not sure as to whether the deadlock can be caused by both the issues put together. So anyway ir resources are not a constraint, try altering the initrans and pctfree params,

    Hope this serves your purpose.



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts