If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Advise on "non-severe system error"

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Apr 2009
Posts: 42
Advise on "non-severe system error"

Hi, I often encounter this kind of error "non-severe system error".
Like, for example: when I try to connect to db, it listed
SQL0901N The SQL statement failed because of a non-severe system error.
Subsequent SQL statements can be processed. (Reason "".) SQLSTATE=58004


I issue "? SQLSQL0901N " to see if there is a solution, but the error I encountered missing a reason code. And I dont know how to trace this error both on DB2 level and OS level.
I suspect this is due to the lack of memory for db2 manager to active a database, should I adjust the db2 manager heap size or something else? Quite confused on this.
Can anybody advise on this? Thanks!

OS: Windows Server 2003
DB2: v9.1
db2dialog.log
Code:
2009-09-08-11.18.53.390000+480 I1H1021            LEVEL: Event
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START   : New Diagnostic Log file
DATA #1 : Build Level, 128 bytes
Instance "DB2" uses "32" bits and DB2 code release "SQL09015"
with level identifier "01060107".
Informational tokens are "DB2 v9.1.500.555", "s080512", "WR21408", Fix Pack "5".
DATA #2 : System Info, 1564 bytes
System: WIN32_NT PDCPBRSS06 Service Pack 2 5.2 x86 Family 6, model 15, stepping 11
CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1
Physical Memory(MB): total:3957 free:1027 available:11
Virtual  Memory(MB): total:6196 free:4419
Swap     Memory(MB): total:2239 free:3392
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2009-09-08-11.18.53.390000+480 E1025H653          LEVEL: Warning (OS)
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, SQO Memory Management, sqloLogMemoryCondition, probe:100
CALLED  : OS, -, VirtualAlloc
OSERR   : 8 "Not enough storage is available to process this command."
MESSAGE : Private memory and/or virtual address space exhausted
DATA #1 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 4 bytes
262144
DATA #2 : Current set size, PD_TYPE_SET_SIZE, 4 bytes
79298560

2009-09-08-11.18.53.390000+480 I1680H555          LEVEL: Severe
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, buffer pool services, sqlbinit, probe:500
MESSAGE : ZRC=0x8B0F0010=-1961951216=SQLO_NOMEM_BPH
          "No memory available in 'Buffer Pool Heap'"
          DIA8300C A memory heap error has occurred.
DATA #1 : String, 35 bytes
BufferPool memory allocation failed

2009-09-08-11.18.53.406000+480 E2237H491          LEVEL: Error (OS)
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, oper system services, sqloSpawnEDU, probe:30
MESSAGE : ZRC=0x83000008=-2097151992
CALLED  : OS, -, unspecified_system_function
OSERR   : 8 "Not enough storage is available to process this command."

2009-09-08-11.18.53.406000+480 I2730H382          LEVEL: Error
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPageCleanerGroup, probe:900
MESSAGE : ZRC=0x83000008=-2097151992

2009-09-08-11.18.53.406000+480 I3114H479          LEVEL: Severe
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPageCleanerGroup, probe:900
DATA #1 : String, 12 bytes
stepsDone: 
DATA #2 : Hexdump, 8 bytes
0x64DC363C : 0000 0000 0101 0000                        ........

2009-09-08-11.18.53.406000+480 I3595H365          LEVEL: Error
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, buffer pool services, sqlbinit, probe:550
MESSAGE : ZRC=0x83000008=-2097151992

2009-09-08-11.18.53.406000+480 I3962H416          LEVEL: Severe
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:160
DATA #1 : Hexdump, 4 bytes
0x64DC8CB0 : 0800 0083                                  ....

2009-09-08-11.18.53.406000+480 I4380H415          LEVEL: Error
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:160
DATA #2 : Hexdump, 4 bytes
0x64DC8CB0 : 0800 0083                                  ....

2009-09-08-11.18.53.406000+480 I4797H424          LEVEL: Severe
PID     : 4384                 TID  : 5124        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-818                APPID: *LOCAL.DB2.090908031853
AUTHID  : SS06_A
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:100
DATA #1 : Hexdump, 4 bytes
0x638FF9F0 : 7BFC FFFF                                  {...
Reply With Quote
  #2 (permalink)  
Old
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,733
For each database that you have, connect to the db and run the following query and post the results back here:

select * from syscat.bufferpools
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old
Registered User
 
Join Date: Apr 2009
Posts: 42
Quote:
Originally Posted by Marcus_A
For each database that you have, connect to the db and run the following query and post the results back here:

select * from syscat.bufferpools
Hi, Marcus, thanks for the reply!
Here is the result:

Code:
database1

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            -2          4096        N      0             0           -



database2

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            264188      4096        N      0             0            -



database3

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            25000       4096        N      0             0           -



database4

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            15000       4096        N      0             0           -
BUFFERPOOL32       2            -            512         32768       N      0             0           -
BUFFERPOOL32_1     3            -            512         32768       N      0             0           -
BUFFERPOOL32_2     4            -            512         32768       N      0             0           -



database5

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            266213      4096        N      0             0           -
BUFFPOOLREGULAR    2            -            100000      4096        N      0             0           -



database6

BPNAME             BUFFERPOOLID DBPGNAME     NPAGES      PAGESIZE    ESTORE NUMBLOCKPAGES BLOCKSIZE   NGNAME
------		   ------------ --------     ------      --------    ------ ------------- ---------   ------
IBMDEFAULTBP       1            -            172621      4096        N      0             0           -
Reply With Quote
  #4 (permalink)  
Old
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,733
DB2 does not use virtual memory. It must have real memory available to it. The primary use of memory in DB2 is typically bufferpools. For most systems, the bufferpools should be about 50% of the total installed real memory on the server.

Also, since you have 32 bit DB2, the maximum amount that can be allocated to instance memory is about 2 GB (3 GB if you use extended memory).

Bufferpool memory size is calculated as page size, multiplied times number of pages. So you need to calculate how much memory you are requesting and adjust the number of pages accordingly (using alter bufferpool SQL statement) so that the total of all databases is about 1 GB for the bufferpools (you will need to leave some memory available for other DB2 purposes). The -2 means that automatic memory is being used, but you might want to change that to a hard-coded number of pages unless you use automatic memory on all your databases.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On