Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2002
    Location
    TX
    Posts
    13

    Unanswered: Internal v, p, l, c locks in db2 udb 7.1 (EE) on solaris v 5.8

    I can anybody explain me what is this locks? And how to avoid them. I don't know what is causing them. Here you can see them as

    Application handle = 40
    Application ID = 0A0B0A49.EB44.020821194232
    Sequence number = 0001
    Application name = java
    Authorization ID = wlscat
    Application status = Compiling
    Status change time = 08-21-2002 19:52:10.800363
    Application code page = 819
    Locks held = 2
    Total wait time (ms) = 0

    List Of Locks
    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal V Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal P Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO
    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal V Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal P Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Any recomandations to avoid this type locks will be appreciated.

    Thanks

    Hari Gosangi

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: Internal v, p, l, c locks in db2 udb 7.1 (EE) on solaris v 5.8

    Hari

    I know P lock is a package lock . I'm not sure about other locks , but, I do remember reading about them in comp.databases.ibm-db2

    These locks are internal to DB2 Objects and cannot be avoided AFAIK ..

    HTH

    Cheers

    Sathyaram

    Originally posted by hari gosangi
    I can anybody explain me what is this locks? And how to avoid them. I don't know what is causing them. Here you can see them as

    Application handle = 40
    Application ID = 0A0B0A49.EB44.020821194232
    Sequence number = 0001
    Application name = java
    Authorization ID = wlscat
    Application status = Compiling
    Status change time = 08-21-2002 19:52:10.800363
    Application code page = 819
    Locks held = 2
    Total wait time (ms) = 0

    List Of Locks
    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal V Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal P Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO
    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal V Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Lock Object Name = 0
    Node number lock is held at = 0
    Object Type = Internal P Lock
    Tablespace Name =
    Table Schema =
    Table Name =
    Mode = S
    Status = Granted
    Lock Escalation = NO

    Any recomandations to avoid this type locks will be appreciated.

    Thanks

    Hari Gosangi

  3. #3
    Join Date
    Apr 2002
    Location
    TX
    Posts
    13
    Thanks for your reply. And you can please provide me some more information on internal V, P, L, C locks. Any material on the net is also appreciated.

    Thanks

    Hari Gosangi.

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    An extract from a post on comp.database.ibm-db2 :



    Internal P Locks are for the RDS cached package/section. Any exection
    of SQL, whether static or dynamic, must be done while holding a
    'package lock'. This ensures that no-one can drop the package that is
    being executed. (EEE and EE)

    Internal V Locks are for the RDS cached variation. Any execution of
    dynamic SQL is done via an entry in the SQL cache known as a
    variation. In order to ensure that the variation remains valid during
    the execution, V locks are acquired on behalf of the entry. (EEE and
    EE)

    These locks are freed when the SQL statement is committed.

    HTH

    Cheers

    Sathyaram

    Originally posted by hari gosangi
    Thanks for your reply. And you can please provide me some more information on internal V, P, L, C locks. Any material on the net is also appreciated.

    Thanks

    Hari Gosangi.

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Internal C Lock - Catalog Cache Entry Lock

    Internal L Lock - Lock used for LOB processing

    Cheers

    Sathyaram

    Originally posted by sathyaram_s
    An extract from a post on comp.database.ibm-db2 :



    Internal P Locks are for the RDS cached package/section. Any exection
    of SQL, whether static or dynamic, must be done while holding a
    'package lock'. This ensures that no-one can drop the package that is
    being executed. (EEE and EE)

    Internal V Locks are for the RDS cached variation. Any execution of
    dynamic SQL is done via an entry in the SQL cache known as a
    variation. In order to ensure that the variation remains valid during
    the execution, V locks are acquired on behalf of the entry. (EEE and
    EE)

    These locks are freed when the SQL statement is committed.

    HTH

    Cheers

    Sathyaram

Posting Permissions

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