Results 1 to 5 of 5
  1. #1
    Join Date
    Jul 2005
    Posts
    102

    Unanswered: DB2DETAILEDEADLOCK error

    Hi everybody

    I am getting this error in db2diag.log...

    2006-05-30-18.36.33.522344-300 I30773521A336 LEVEL: Warning
    PID : 966700 TID : 1 PROC : db2event (DB2DETAILDEADLOCK) 0
    INSTANCE: xyz NODE : 000
    FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:7
    MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc -2146631636

    the event monitor is disabled, even then I am getting this error..

    I don't understand why I am getting this error, can anybody help me in understanding this.

    Thanks
    Anks

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    It is automatically enabled each time you start the database ...

    If you don't want it, delete it

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338

    Cool

    go to the directory:
    $DB2HOME/NODE0000/SQL00001/db2event/db2detaildeadlock

    $ rm -rf *.evt

    after that you shouldnot receive this error.

    Thanks,
    Jayanta Datta
    New Delhi

  4. #4
    Join Date
    Jul 2005
    Posts
    102
    We were not getting these errors earlier, they just started like a day ago. Is there any particular reason for these errors and can we fix those things also?

    I hope I can safely delete it and it won't affect anything

    Thanks

    Anks

  5. #5
    Join Date
    Jul 2005
    Posts
    102
    I just checked the usage of .evt file. It is actually using only 62% of the memory that has been allocated to this file??? Then why these errors??

Posting Permissions

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