Results 1 to 5 of 5

Thread: db2bp error

  1. #1
    Join Date
    Feb 2012
    Posts
    7

    Unanswered: db2bp error

    Hi,

    I could see the below error from db2diag.log.

    2012-02-14-08.39.57.257132-360 I121768G277 LEVEL: Severe
    PID : 11340 TID : 1454808000 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, db2GetAlertCfg, probe:40 RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"

    Please adivse on what this error mean and how can we resolve this.

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Could be coming from the health monitor... you didn't provide enough info. What else is logged in the db2diag.log? What do you execute when this error is logged in the diag.log

  3. #3
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  4. #4
    Join Date
    Feb 2012
    Posts
    7
    db2girl: Yes, this is from the health monitor... I dont see anything else running during that time. Providing the logs from db2diag.log 2 hours before and after the time when the issue occurred

    2012-02-14-05.07.26.299526-360 I120792G329 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:20
    START : Automatic reorg evaluation has finished successfully on database TIMLDAPP

    2012-02-14-07.07.26.034859-360 I121122G315 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:10
    START : Automatic reorg evaluation has started on database TIMLDAPP

    2012-02-14-07.07.26.189135-360 I121438G329 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:20
    START : Automatic reorg evaluation has finished successfully on database TIMLDAPP

    2012-02-14-08.39.57.257132-360 I121768G277 LEVEL: Severe
    PID : 11340 TID : 1454808000 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, db2GetAlertCfg, probe:40
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"

    2012-02-14-09.07.26.547553-360 I122046G315 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:10
    START : Automatic reorg evaluation has started on database TIMLDAPP

    2012-02-14-09.07.26.684930-360 I122362G329 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:20
    START : Automatic reorg evaluation has finished successfully on database TIMLDAPP

    2012-02-14-11.07.26.463338-360 I122692G315 LEVEL: Event
    PID : 20829 TID : 659131312 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Automatic Table Maintenance, db2HmonEvalReorg, probe:10
    START : Automatic reorg evaluation has started on database TIMLDAPP

    przytula_guy: The issue here is from the PROC db2bp and the link provided by you was a different one.

    Thanks for your replies.

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    The error from db2GetAlertCfg() could be from the health monitor, but we can't tell for sure. I was hoping to see some additional errors right before or after the one you pasted in your first post. This looks like a v8 instance? Are you executing any health snapshots at the time this error is logged in the diag.log? Is this instance part of HADR?

    If this error doesn't cause any real problem, then just ignore it. If you want to try and debug it, then you could increase diaglevel to 4 to see if db2 writes any additional informational messages (if you still have support, then open a pmr).

Posting Permissions

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