Topic
  • 6 replies
  • Latest Post - ‏2014-08-18T21:46:46Z by sumithar
sumithar
sumithar
10 Posts

Pinned topic db2syscs

‏2014-08-15T12:36:45Z |

Hi,

I am running db2 express-c on win 7 64bit.  of late I have noticed a tendency for db2syscs CPU to spike periodically (it seems to run about 20% most of the time) and thus it makes my PC "freeze" for a moment.  For example when I am typing this, it will lose focus on this text area momentarily and then restore it.  Driving me demented.  Only option is to kill it, which of course stops by DB2.

Any thoughts?

I have googled db2syscs and seen posts where people complain about it using 100% CPU but those pertain to other older versions of DB2 and PTFs and so on that don't seem applicable to me.

Thanks!

  • mor
    mor
    577 Posts

    Re: db2syscs

    ‏2014-08-15T12:56:29Z  

     

    Normal practice would be to investigate why the db2-instance (db2syscs.exe) is using CPU. It is unwise to kill a db2-instance solely because of CPU spike.

    The db2 product includes various tools to help see what's happening: (such as snapshots, monitoring views/functions, diagnostic files (db2diag.log), and db2pd. All these are documented in the free on-line knowledge-centre, so start there...

    Typical reasons for the db2-instance using CPUs include running queries that are not optimised, performing housekeeping runstats that need better profiles , running user code that's not optimised etc.

  • sumithar
    sumithar
    10 Posts

    Re: db2syscs

    ‏2014-08-15T14:28:49Z  
    • mor
    • ‏2014-08-15T12:56:29Z

     

    Normal practice would be to investigate why the db2-instance (db2syscs.exe) is using CPU. It is unwise to kill a db2-instance solely because of CPU spike.

    The db2 product includes various tools to help see what's happening: (such as snapshots, monitoring views/functions, diagnostic files (db2diag.log), and db2pd. All these are documented in the free on-line knowledge-centre, so start there...

    Typical reasons for the db2-instance using CPUs include running queries that are not optimised, performing housekeeping runstats that need better profiles , running user code that's not optimised etc.

    Hi mor,

    This is a personal instance of DB2 running on my PC.  I use it primarily to connect to Db2 on the mainframe.  There are no processes or applications that run against it.  There is just 1 local database and that has just a couple of tables.   Only a bunch of nicknames to facilitate my mainframe access.  I understand about monitoring tools and logs and so on, just find it perplexing I need to go to all that trouble for this piddly little instance ;-)

    Thanks!

  • LukeNumrych
    LukeNumrych
    118 Posts

    Re: db2syscs

    ‏2014-08-18T15:09:29Z  
    • sumithar
    • ‏2014-08-15T14:28:49Z

    Hi mor,

    This is a personal instance of DB2 running on my PC.  I use it primarily to connect to Db2 on the mainframe.  There are no processes or applications that run against it.  There is just 1 local database and that has just a couple of tables.   Only a bunch of nicknames to facilitate my mainframe access.  I understand about monitoring tools and logs and so on, just find it perplexing I need to go to all that trouble for this piddly little instance ;-)

    Thanks!

    Still, it should be logging something either to Application Event Log or db2diag...  anything in there coinciding with the spikes?

  • sumithar
    sumithar
    10 Posts

    Re: db2syscs

    ‏2014-08-18T18:22:20Z  

    Still, it should be logging something either to Application Event Log or db2diag...  anything in there coinciding with the spikes?

    Hi Luke,

    I am seeing a series of messages like this every time there is a spike.

    2014-08-18-13.42.34.215000-240 E240023F3464         LEVEL: Warning
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:1001
    DATA #1 : String, 8 bytes
    Fmp Row:
    DATA #2 : sqlerFmpRow, PD_SQLER_TYPE_FMP_ROW, 536 bytes
     fmpPid: 45592
     fmpPoolList Ptr: 0x0000000000000000    fmpForcedList Ptr: 0x0000000000000000
     nextFmpCB Ptr: 0x00000000056afb00      prevFmpCB Ptr: 0x0000000000000000
     fmpIPCList Ptr: 0x00000000056aff80
     stateFlags: 0x00000010 numFmp32Attaches: 0
     numActiveThreads: 0    numPoolThreads: 0
     fmpCodePage: 0 fmpRowUseCount: 0
     active: 0x01   rowLoaderValidate: 0x00
     ipcLatch:
    0x00000000056AA2E4 : 0000 3C00                                  ..<.
     rowLatch:
    0x00000000056AA2E8 : 0000 BB01                                  ....
     fmpAgentList:
    0x00000000056AA2F0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA300 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA310 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA320 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA330 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA340 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA350 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA360 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA370 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA380 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA390 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3A0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3B0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA400 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA410 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA420 : 0000 0000 0000 0000 00F0 0000 0000 0000    ................
    0x00000000056AA430 : 0000 0000 08FE 0000 FE08 0000 0000 0000    ................
    0x00000000056AA440 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA450 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA460 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA470 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000056AA480 : 0000 0000 0000 0000 E0A2 6A05 0000 0000    ..........j.....
    0x00000000056AA490 : 00FE 6A05 0000 0000 00FF 6A05 0000 0000    ..j.......j.....
    0x00000000056AA4A0 : 0000 0000 0100 0000 0000 0000 0000 0000    ................
    0x00000000056AA4B0 : 0000 0000 0000 0000                        ........
    
    2014-08-18-13.42.34.218000-240 E243489F584          LEVEL: Warning
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:2000
    DATA #1 : String, 55 bytes
    Sending a signal to clean up NOT THREADED FMP process: 
    DATA #2 : Process ID, 4 bytes
    45592
    
    2014-08-18-13.42.34.221000-240 E244075F571          LEVEL: Error (OS)
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, oper system services, sqlossig, probe:1
    MESSAGE : ZRC=0x83000057=-2097151913
              
    CALLED  : OS, -, OpenProcess
    OSERR   : 87 "The parameter is incorrect."
    
    2014-08-18-13.42.34.225000-240 I244648F1089         LEVEL: Error
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerInvokeFencedRoutine, probe:99
    MESSAGE : ZRC=0xFFFFFB95=-1131
              SQL1131N  A stored procedure process has been terminated abnormally. 
              Routine name: "". Specific name: "".
    
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1131   sqlerrml: 36
     sqlerrmc: -2029060040 * * * *  SEMAPHORE WAIT 
     sqlerrp : SQLJCMN 
     sqlerrd : (1) 0x8136001C      (2) 0x0000001C      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
               (7)      (8)      (9)      (10)        (11)     
     sqlstate:     
    

    I looked up sqlcode -1131 and it says a Stored procedure was terminated abnormally which I can see in the diag log also.  I am not running any stored procs myself, so that doesn't help me.

     

    Any thoughts?

     

  • LukeNumrych
    LukeNumrych
    118 Posts

    Re: db2syscs

    ‏2014-08-18T18:31:51Z  
    • sumithar
    • ‏2014-08-18T18:22:20Z

    Hi Luke,

    I am seeing a series of messages like this every time there is a spike.

    <pre class="html dw" data-editor-lang="js" data-pbcklang="html" dir="ltr">2014-08-18-13.42.34.215000-240 E240023F3464 LEVEL: Warning PID : 10216 TID : 46720 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : GENDB APPHDL : 0-687 APPID: *LOCAL.DB2.140818173440 AUTHID : DB2ADMIN HOSTNAME: CNU2389XR4 EDUID : 46720 EDUNAME: db2agent (DUTP1033) FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:1001 DATA #1 : String, 8 bytes Fmp Row: DATA #2 : sqlerFmpRow, PD_SQLER_TYPE_FMP_ROW, 536 bytes fmpPid: 45592 fmpPoolList Ptr: 0x0000000000000000 fmpForcedList Ptr: 0x0000000000000000 nextFmpCB Ptr: 0x00000000056afb00 prevFmpCB Ptr: 0x0000000000000000 fmpIPCList Ptr: 0x00000000056aff80 stateFlags: 0x00000010 numFmp32Attaches: 0 numActiveThreads: 0 numPoolThreads: 0 fmpCodePage: 0 fmpRowUseCount: 0 active: 0x01 rowLoaderValidate: 0x00 ipcLatch: 0x00000000056AA2E4 : 0000 3C00 ..<. rowLatch: 0x00000000056AA2E8 : 0000 BB01 .... fmpAgentList: 0x00000000056AA2F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA300 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA310 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA320 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA330 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA340 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA350 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA360 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA370 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA380 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA390 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA420 : 0000 0000 0000 0000 00F0 0000 0000 0000 ................ 0x00000000056AA430 : 0000 0000 08FE 0000 FE08 0000 0000 0000 ................ 0x00000000056AA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000000056AA480 : 0000 0000 0000 0000 E0A2 6A05 0000 0000 ..........j..... 0x00000000056AA490 : 00FE 6A05 0000 0000 00FF 6A05 0000 0000 ..j.......j..... 0x00000000056AA4A0 : 0000 0000 0100 0000 0000 0000 0000 0000 ................ 0x00000000056AA4B0 : 0000 0000 0000 0000 ........ 2014-08-18-13.42.34.218000-240 E243489F584 LEVEL: Warning PID : 10216 TID : 46720 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : GENDB APPHDL : 0-687 APPID: *LOCAL.DB2.140818173440 AUTHID : DB2ADMIN HOSTNAME: CNU2389XR4 EDUID : 46720 EDUNAME: db2agent (DUTP1033) FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:2000 DATA #1 : String, 55 bytes Sending a signal to clean up NOT THREADED FMP process: DATA #2 : Process ID, 4 bytes 45592 2014-08-18-13.42.34.221000-240 E244075F571 LEVEL: Error (OS) PID : 10216 TID : 46720 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : GENDB APPHDL : 0-687 APPID: *LOCAL.DB2.140818173440 AUTHID : DB2ADMIN HOSTNAME: CNU2389XR4 EDUID : 46720 EDUNAME: db2agent (DUTP1033) FUNCTION: DB2 UDB, oper system services, sqlossig, probe:1 MESSAGE : ZRC=0x83000057=-2097151913 CALLED : OS, -, OpenProcess OSERR : 87 "The parameter is incorrect." 2014-08-18-13.42.34.225000-240 I244648F1089 LEVEL: Error PID : 10216 TID : 46720 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : GENDB APPHDL : 0-687 APPID: *LOCAL.DB2.140818173440 AUTHID : DB2ADMIN HOSTNAME: CNU2389XR4 EDUID : 46720 EDUNAME: db2agent (DUTP1033) FUNCTION: DB2 UDB, routine_infrastructure, sqlerInvokeFencedRoutine, probe:99 MESSAGE : ZRC=0xFFFFFB95=-1131 SQL1131N A stored procedure process has been terminated abnormally. Routine name: "". Specific name: "". DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1131 sqlerrml: 36 sqlerrmc: -2029060040 * * * * SEMAPHORE WAIT sqlerrp : SQLJCMN sqlerrd : (1) 0x8136001C (2) 0x0000001C (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: </pre>

    I looked up sqlcode -1131 and it says a Stored procedure was terminated abnormally which I can see in the diag log also.  I am not running any stored procs myself, so that doesn't help me.

     

    Any thoughts?

     

    Looks like a stored procedure called by db2agent is failing.  Look at one of the previous messages (for the same db2agent)

     

    2014-08-18-13.42.34.221000-240 E244075F571          LEVEL: Error (OS)
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, oper system services, sqlossig, probe:1
    MESSAGE : ZRC=0x83000057=-2097151913
              
    CALLED  : OS, -, OpenProcess
    OSERR   : 87 "The parameter is incorrect."
     

    It looks like it tried to start a process (hence "OpenProcess") with an invalid parameter.

    I'd investigate whatever was that db2agent doing... 

  • sumithar
    sumithar
    10 Posts

    Re: db2syscs

    ‏2014-08-18T21:46:46Z  

    Looks like a stored procedure called by db2agent is failing.  Look at one of the previous messages (for the same db2agent)

     

    2014-08-18-13.42.34.221000-240 E244075F571          LEVEL: Error (OS)
    PID     : 10216                TID : 46720          PROC : db2syscs.exe
    INSTANCE: DB2                  NODE : 000           DB   : GENDB
    APPHDL  : 0-687                APPID: *LOCAL.DB2.140818173440
    AUTHID  : DB2ADMIN             HOSTNAME: CNU2389XR4
    EDUID   : 46720                EDUNAME: db2agent (DUTP1033)
    FUNCTION: DB2 UDB, oper system services, sqlossig, probe:1
    MESSAGE : ZRC=0x83000057=-2097151913
              
    CALLED  : OS, -, OpenProcess
    OSERR   : 87 "The parameter is incorrect."
     

    It looks like it tried to start a process (hence "OpenProcess") with an invalid parameter.

    I'd investigate whatever was that db2agent doing... 

    Thanks Luke.  That is getting too deep into the weeds for me.  I think it's related to Data Studio and I am connected to a local database.  When I close out Datastudio then the messages stop appearing in my log.