Topic
2 replies Latest Post - ‏2013-09-27T07:54:18Z by carlolunghi
carlolunghi
carlolunghi
4 Posts
ACCEPTED ANSWER

Pinned topic Continuos warning in db2diag.log

‏2013-09-16T08:32:02Z |

Dear colleagues.

We started to use DB2 LUW for a php web application in order to get business with a company already using it on different technology. In our laboratory the application accesses to the DB2 v10.1 Express-c database for queries, reads, insert and update. The client has been cataloged both by ip address and fully qualified name. In db2diag.log with level debug 3 I found the trace of a single operation coming from the web server that opens a connection the the DD database and issues its operations.
Thanks to the command <<db2 list applications>>

[db2inst1@ddprod ~]$ db2 list applications

Auth Id  Application    Appl.      Application Id                                                 DB       # of
         Name           Handle                                                                    Name    Agents
-------- -------------- ---------- -------------------------------------------------------------- -------- -----
DB2INST1 httpd          3099       127.0.0.1.39750.130916074454                                   DD       1

I recognize the application id, for example <<APPID: 127.0.0.1.39750.130916074454>> because currently the web server is processed on the same Linux node of the DB2 server. After a short time the application list is empty. Therefore there is a continuos cycle of connect-query, etc.
I don't think it be a problem, but any way I ask for any best practice suggested in a similar web application model that accesses to DB2.

The second question refers to the warning issued by the db2sysc process in every cycle. Which is the reason of a such warning ?

Here is the trace. Thank to everybody for any comment.

Regards.

c.l.

2013-09-16-09.30.28.113775+120 I241211929E666        LEVEL: Event
PID     : 30374                TID : 139744205858560 PROC : db2sysc
INSTANCE: db2inst1             NODE : 000            DB   : DD
APPHDL  : 0-2208               APPID: 127.0.0.1.39424.130916073028
AUTHID  : DB2INST1             HOSTNAME: ddprod.cost.it
EDUID   : 2397                 EDUNAME: db2agent (DD)
FUNCTION: DB2 UDB, base sys utilities, sqleCalculateDbHeaps, probe:70
MESSAGE :  RLMS - DB Memory Set for Resident Member
DATA #1 : String, 10 bytes
totalBytes
DATA #2 : unsigned integer, 8 bytes
361103360
DATA #3 : String, 11 bytes
dbHeapBytes
DATA #4 : unsigned integer, 8 bytes
147193856

2013-09-16-09.30.28.401635+120 E241212596E758        LEVEL: Info
PID     : 30374                TID : 139744205858560 PROC : db2sysc
INSTANCE: db2inst1             NODE : 000            DB   : DD
APPHDL  : 0-2208               APPID: 127.0.0.1.39424.130916073028
AUTHID  : DB2INST1             HOSTNAME: ddprod.cost.it
EDUID   : 2397                 EDUNAME: db2agent (DD)
FUNCTION: DB2 UDB, data protection services, sqlpinit, probe:1500
DATA #1 : <preformatted>
Database is starting up with the following values:
                 Head Extent ID: 0
                  Log File Size: 1024
                    Startup Lso: 0
                       Base Lso: 26991141569
            Last Log Record Lso: 26986967993
 Current Write Log Extent Limit: 26995315393

2013-09-16-09.30.28.862712+120 E241213355E501        LEVEL: Event
PID     : 30374                TID : 139744205858560 PROC : db2sysc
INSTANCE: db2inst1             NODE : 000            DB   : DD
APPHDL  : 0-2208               APPID: 127.0.0.1.39424.130916073028
AUTHID  : DB2INST1             HOSTNAME: ddprod.cost.it
EDUID   : 2397                 EDUNAME: db2agent (DD)
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:1000
START   : DATABASE: DD       : ACTIVATED: NO

2013-09-16-09.30.29.108769+120 I241213857E550        LEVEL: Warning
PID     : 30374                TID : 139744205858560 PROC : db2sysc
INSTANCE: db2inst1             NODE : 000            DB   : DD
APPHDL  : 0-2208               APPID: 127.0.0.1.39424.130916073028
AUTHID  : DB2INST1             HOSTNAME: ddprod.cost.it
EDUID   : 2397                 EDUNAME: db2agent (DD)
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::StartBackgroundAgents, probe:14912
DATA #1 : <preformatted>
Perform ABP Start and cat_nodenum is 0, my node num is 0
 

  • p175
    p175
    43 Posts
    ACCEPTED ANSWER

    Re: Continuos warning in db2diag.log

    ‏2013-09-17T21:14:53Z  in response to carlolunghi

    Try ACTIVATING the database and / or setting the DIAGLEVEL = 2.

    DB2 UPDATE DBM CFG USING DIAGLEVEL 2;

    DB2 ACTIVATE DATABASE DD;

     

     

    • carlolunghi
      carlolunghi
      4 Posts
      ACCEPTED ANSWER

      Re: Continuos warning in db2diag.log

      ‏2013-09-27T07:54:18Z  in response to p175

      Hello p175,

      thank you for the response. I'll implement soon. Before reducing the volume of produced info into db2diag.log by putting level 2 may I ask for another clarification ?

      I find systematically such two messages:

      - CSC Initialization failed (Load default library /opt/ibm/db2/V10.1/pqcmx/pureQuery/lib64/libpqcmx.so failed with rc = 0)

      - db2dsdriver.cfg path: /home/db2inst1/sqllib/cfg/db2dsdriver.cfg.

      Both the library and the cfg file, that refer to db2cli, do not exist in my configuration. Does it depend on a wrong installation and /or configuration ?

      Thanks to everybody for any comment.

      Regards.

      c.l.