Results 1 to 11 of 11
  1. #1
    Join Date
    Apr 2012
    Posts
    156

    Unanswered: DB2VEND / db2logmgr Consuming lots of memory

    I am running on both AIX and Linux, with DB2 V9.7 Fixpak 8. Logs are achiving to TSM. I noticed a high amount of memory being used on my hosts with a large chunk of the memory being used by db2vend, specifically:

    svmon -P -t 15 -O summary=basic
    Unit: page

    -------------------------------------------------------------------------------
    Pid Command Inuse Pin Pgsp Virtual
    28311720 db2sysc 2546723 10247 0 2546661
    27983932 db2vend 2467554 10048 0 2467374

    Then when I look at the underlying pid for db2vend:
    ps -ef | grep -i 27983932
    27983932 28311720 0 Jan 29 - 1:04 db2vend (db2logmgr.meth1 - 4014 (MNB))

    It seems strange that the db2logmgr is using almost as much memory as my database/instance. Has anyone else seen this issue? Any ideas on how to limit the amount of memory the db2logmgr is using? I can see it is slowing increasing the amount of memory it using almost like there is a memory leak. I am not receiving any errors, just lots of people questioning why this is using so much memory.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Apr 2012
    Posts
    156
    Unfortunately IC87173 does not apply to our system as we are on a later version of the client. We opened a ticket to DB2 support as well as Tivoli support, could be the leak was not fixed.

  4. #4
    Join Date
    Sep 2007
    Location
    Moscow
    Posts
    41
    Hmm.....have the same "issue" :

    # svmon -P -t 2 -O summary=basic,unit=MB
    Unit: MB

    -------------------------------------------------------------------------------
    Pid Command Inuse Pin Pgsp Virtual
    8847448 db2sysc 53687.55 40.1 1.06 53258.23
    22610028 db2vend 52734.35 39.1 1.06 52734.85

    But this is 64GB RAM LPAR

    In the same time "lsps -a" show only 1% of 20GB pagespace utilization.
    Look's like some "svmon" bug.

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    I see the same. If you do svmon -P for db2vend, you will see that most of the segments are shared memory (shmat/mmap). This means db2vend is not really consuming memory, just attaches to db memory set.

    Code:
    db2inst1 10158142  5439560   0   Nov 19      -  0:02 db2vend (db2logmgr.meth1 - 2829 (xxxxxxx))
    
    
    > svmon -P 10158142 | grep -i 'shmat/mmap'
      83854e  7000000d work default shmat/mmap           m   4096     0    0    4096
      850574  7000000e work default shmat/mmap           m   4096     0    0    4096
      820568  7000000f work default shmat/mmap           m   4096     0    0    4096
      840570  70000004 work default shmat/mmap           m   3666     0 2672    4096
      800560  70000005 work default shmat/mmap           m   3176     0 2967    4096
      804201  7000000c work default shmat/mmap           m   2254     0 1842    4096
      81c587  70000006 work default shmat/mmap           m   2047     0 3570    4096
      850594  70000010 work default shmat/mmap           m   1613     0    0    1613
      85c577  70000007 work default shmat/mmap           m   1129     0 2967    4096
      818506  77000000 work default shmat/mmap          sm   1541     0    0    1541
      83050c  7000000b work default shmat/mmap           m      0     0 4096    4096
      87459d  70000011 work default shmat/mmap           m      0     0    0       0
      818566  70000012 work default shmat/mmap           m      0     0    0       0
      84c393  70000009 work default shmat/mmap           m      0     0 4096    4096
      844571  7000000a work default shmat/mmap           m      0     0 4096    4096
      81c567  70000008 work default shmat/mmap           m      0     0 4096    4096
      86c57b  70000013 work default shmat/mmap           m      0     0    0       0
    
    
    > svmon -P 10158142 | grep -i 'process private'
      8044a1 f00000002 work process private              m      5     3    0       5

  6. #6
    Join Date
    Feb 2014
    Posts
    13
    Check for lsof value for the db2logmgr process.
    If any file descriptors are not closed then you may face memory leak issue.
    lsof -p 27983932 | wc -l

    For more info refer this link:
    Finding open files with lsof

  7. #7
    Join Date
    Feb 2014
    Posts
    13

    DB2VEND / db2logmgr Consuming lots of memory

    Check for lsof value for the db2logmgr process.
    If any file descriptors are not closed then you may face memory leak issue.
    lsof -p 27983932 | wc -l

    For more info refer this link:
    Finding open files with lsof

  8. #8
    Join Date
    Jul 2009
    Location
    USA
    Posts
    53
    We've got the same problem. What's the solution?

  9. #9
    Join Date
    Feb 2014
    Posts
    13
    Check for file descriptor values using lsof command for db2logmgr process.

    If value keeps on increasing then there is a chance for memory leak.

    Check with respective vendors if memory leak issue exists.

  10. #10
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    we have the same problem with db2 v10.1 and also when using db2adutl retrieve .. we get db2 killed by oom process (redhat ticket has been opened and noy corrected yet, but they suggested a kernel upgrade)
    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

  11. #11
    Join Date
    Apr 2012
    Posts
    156
    Sounds like you have a different issue. I heard back from IBM and they confirmed what dbgirl had posted:
    "in general all of the db2 processes in the database will be using the same set of
    shared memory segments and so the memory sets should only really exist
    once. Then the db2vend processes that consumed a lot memory you described really were not using much memory overall, but in reality, it just attached to memory segments that are used by that db2 process db2sysc."

Posting Permissions

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