DB2 Cpu Usage

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kelleram
    New Member
    • Sep 2008
    • 12

    DB2 Cpu Usage

    I want to know if my DB2 Server was configured to use the 2 CPUs on it. What do I need to do to figure this out? I have run db2licm -l and it doesn't provide the necessary information as it did on my peers server. I wasn't the person responsible for configuring it and I've asked the person who installed it if he set it up this way and he is unsure. Any suggestions on finding this out? We're running Federation Server and the server is beyond slow. We have a small windows server with 1 CPU that runs faster than this 64 bit AIX setup so I'm concerned as to what could be the cause.
  • cburnett
    New Member
    • Aug 2007
    • 57

    #2
    Try:

    db2pd -osinfo

    and look at the ConfigCPU column.

    Comment

    • kelleram
      New Member
      • Sep 2008
      • 12

      #3
      Thanks for the response. I was able to run the command and that particular column shows 8 but the column Online CPU says 4. Interestingly enough, when I look at the Control Center CA, I see 2.

      Comment

      • cburnett
        New Member
        • Aug 2007
        • 57

        #4
        In these days of LPARS and multi-cores, the definition of CPUs can be fuzzy. Both CA and db2pd -osinfo report on the number of CPU cores. Thus, I surmise that you have 2 quad-core CPUs on your server (making total and configCPU = 8). Check by looking at the Cores/socket column which I believe will be 4 in your case.

        OnlineCPU = 4 would then mean that DB2 is only using 1 CPU. Why would this be so? Two possibilities come to mind. 1.What version of DB2 are you running? (db2licm -l) Express-C is limited to a maximum of 2 cores; Express-C FTL is limited to a maximum of 4 cores. 2.You are running this on an LPAR which can only use 1 of the CPUs.

        As to why Config Advisor reports 2 processors, either you are running Express-C (limited to 2 cores) or you have a defect like APAR IY58451.

        Comment

        Working...