Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2002
    Posts
    58

    Unanswered: Memory error in DB2DIAG.LOG

    Hello,

    What can be the cause of this error ? It causes the whole server to 'hang'.
    Wich parameters are dependent ?

    Thanks for helping me out ...

    Peter



    Not enough memory available for a (private) sort heap of size 25000
    Trying smaller size...

    2004-06-03-11.25.51.382000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    SQO Memory Management MemAllocate Probe:202 Database:WILDSTEP

    Memory allocation failure. VirtualAlloc() returned an error:
    0x5537CBA0 : 0x00000008 ....

    2004-06-03-11.25.51.460000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    sort/list services sqlsAllocateSortMemory Probe:35 Database:WILDSTEP

    Not enough memory available for a (private) sort heap of size 25000
    Trying smaller size...

    2004-06-03-11.25.51.523000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    SQO Memory Management MemAllocate Probe:202 Database:WILDSTEP

    Memory allocation failure. VirtualAlloc() returned an error:
    0x5537CBA0 : 0x00000008 ....

    2004-06-03-11.25.51.601000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    sort/list services sqlsAllocateSortMemory Probe:35 Database:WILDSTEP

    Not enough memory available for a (private) sort heap of size 25000
    Trying smaller size...

    2004-06-03-11.25.51.664000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    SQO Memory Management MemAllocate Probe:202 Database:WILDSTEP

    Memory allocation failure. VirtualAlloc() returned an error:
    0x5537CBA0 : 0x00000008 ....

    2004-06-03-11.54.40.484000 InstanceB2 Node:000
    PID:924(db2dasstm.exe) TID:1232 Appid:none
    oper system services sqloSSemClose Probe:20

    Unexpected system error 0x6 has occurred.
    This has been mapped to ZRC 0x83000006.

  2. #2
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Some Observations

    Hi Peter,

    You need to mention your Operating System, Total Memory Available, DB2 Version and Fix Pak Applied.

    Please also post your DBM and DB Configurations that would really help.

    Looking at this below

    -------------------------------------------------------------------

    2004-06-03-11.25.51.460000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    sort/list services sqlsAllocateSortMemory Probe:35 Database:WILDSTEP

    Not enough memory available for a (private) sort heap of size 25000
    Trying smaller size...

    2004-06-03-11.25.51.523000 InstanceB2 Node:000
    PID:1680(db2syscs.exe) TID:3364 Appid:*LOCAL.DB2.00DA03084951
    SQO Memory Management MemAllocate Probe:202 Database:WILDSTEP

    Memory allocation failure. VirtualAlloc() returned an error:
    0x5537CBA0 : 0x00000008 ....
    --------------------------------------------------------

    The initial observation makes me think that you have allocated more memory to the instance and database than is available in the operating system, hence what happens is that when more memory is required to be allocated the system is not able to allocate that and the database hangs.

    However it would be to amature to comment on what is happening right now so after you post the above requested informartion the picture will get clearer.
    HTH

    Nitin

    Ask the experienced rather than the learned

  3. #3
    Join Date
    Dec 2002
    Posts
    58
    Sorry for the incomplete information.
    I am running DB2 v8.1 FP 5 on windows2000.
    2 CPUs, 3gig RAM (taks manager tells me 1.8 gig is used)

    Attached are the DB cfg and the DBM cfg.

    Thanks again for the quick response

    Peter
    Attached Files Attached Files

  4. #4
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Memory Limitation

    Hi Peter,

    I think there is a limitation of DB2 which does not allow it to use beyond 2 GB of Memory per instance on Windows 2000 Server, however if you have Windows 2003 Server you can go ahead and exploit upto 3GB of memory or more per instance.

    We were facing the same issues some time earlier so what we did was that we split our databases under 2 Instances and gave each instance a memory limitation of 1.5 Gb with leaving 10% overhead and that way not only was our RAM used properly but we were also able to exploit the box as well.

    See if you can do something similar. Try reducing a few parameters or monitor the bufferpools and as per the hit ratio decide on their new sizes. Do all of this keeping in mind your application/environment needs and that should do it fine.
    Last edited by nitingm; 06-03-04 at 08:20.
    HTH

    Nitin

    Ask the experienced rather than the learned

Posting Permissions

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