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 > Question about application support layer heap size

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-11-08, 17:49
sundaram sundaram is offline
Registered User
 
Join Date: Mar 2006
Posts: 104
Question about application support layer heap size

Hi,

We use db2 8.2.6 on windows


We get following error in our prod env (frequency roughly 1 in 2-3 weeks).

The Application Support Layer heap cannot be allocated. SQLSTATE=57011


Initially the applheapsz for the instance was 1280 (4K pages). We increased it to 2560, but still getting this error.

The error affects only 2 of our applications. These use fderated access to tables from another database running in the same same instance. Other applications (mainly online apps) continue to work OK after this error.


Any idea what is causing this error. will it help if we raise the applheapsize further. Why applheapsize exceed error only occurs with the 2 apps that use federated access to another database running within same instance?

The extract from db2diag is as follows....
---------------------------------------------
2008-09-11-15.46.48.378000+600 E309767H566 LEVEL: Error (OS)
PID : 5344 TID : 5304 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmshr3, probe:100
CALLED : OS, -, MapViewOfFileEx
OSERR : 8 "Not enough storage is available to process this command."
DATA #1 : Memory set type, PD_TYPE_SET_TYPE, 4 bytes
4
DATA #2 : Actual allocated set size, PD_TYPE_REAL_SET_SIZE, 4 bytes
20987904
DATA #3 : Memory set address, PD_TYPE_SET_ADDRESS, 4 bytes
<NULL pointer>

2008-09-11-15.46.48.487000+600 I310335H455 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, drda wrapper, report_error_message, probe:10
MESSAGE : DRDA Server:
DATA #1 : Hexdump, 8 bytes
0x496A0910 : 4158 4953 4853 444C AXISHSDL

2008-09-11-15.46.48.487000+600 I310792H461 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, drda wrapper, report_error_message, probe:20
MESSAGE : Function name:
DATA #1 : Hexdump, 13 bytes
0x2F9C1298 : 4472 6976 6572 436F 6E6E 6563 74 DriverConnect

2008-09-11-15.46.48.487000+600 I311255H452 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, drda wrapper, report_error_message, probe:30
MESSAGE : ODBC native err:
DATA #1 : Hexdump, 5 bytes
0x42A168C8 : 2D31 3232 31 -1221

2008-09-11-15.46.48.487000+600 I311709H453 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, drda wrapper, report_error_message, probe:40
MESSAGE : ODBC sqlstate:
DATA #1 : Hexdump, 6 bytes
0x42A172ED : 3537 3031 3100 57011.

2008-09-11-15.46.48.487000+600 I312164H898 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, drda wrapper, report_error_message, probe:50
MESSAGE : ODBC error txt:
DATA #1 : Hexdump, 101 bytes
0x42A16EEC : 5B49 424D 5D5B 434C 4920 4472 6976 6572 [IBM][CLI Driver
0x42A16EFC : 5D20 5351 4C31 3232 314E 2020 5468 6520 ] SQL1221N The
0x42A16F0C : 4170 706C 6963 6174 696F 6E20 5375 7070 Application Supp
0x42A16F1C : 6F72 7420 4C61 7965 7220 6865 6170 2063 ort Layer heap c
0x42A16F2C : 616E 6E6F 7420 6265 2061 6C6C 6F63 6174 annot be allocat
0x42A16F3C : 6564 2E20 2053 514C 5354 4154 453D 3537 ed. SQLSTATE=57
0x42A16F4C : 3031 310D 0A 011..

2008-09-11-15.46.48.565000+600 I313064H397 LEVEL: Error
PID : 5344 TID : 4512 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
APPHDL : 0-586 APPID: G15DC767.N913.028701054651
FUNCTION: DB2 UDB, Query Gateway, sqlqgFedRollback, probe:130
MESSAGE : sqlqgFedrollback: skip rollback because not connected!
-------------------------------------------------------------------
Reply With Quote
  #2 (permalink)  
Old 09-12-08, 09:10
ARWinner ARWinner is offline
Registered User
 
Join Date: Jan 2003
Posts: 3,575
The Application Support Layer heap is controlled by aslheapsz not applheapsz.

http://publib.boulder.ibm.com/infoce...n/r0000264.htm

Andy
Reply With Quote
  #3 (permalink)  
Old 09-14-08, 17:36
sundaram sundaram is offline
Registered User
 
Join Date: Mar 2006
Posts: 104
I typed it wrong. please read it as 'aslheapsz' instead od applheapsz.

We increased aslheapsz from 1280 pages to 2560 pagesand is still getting the above mentioned error.


Any idea what is causing this error. will it help if we raise the aslheapsize further. Why aslheapsize exceed error only occurs with the 2 apps that use federated access to another database running within same instance?
Reply With Quote
  #4 (permalink)  
Old 09-15-08, 08:15
ARWinner ARWinner is offline
Registered User
 
Join Date: Jan 2003
Posts: 3,575
Look at the error closely. It is saying that it cannot allocate the asl heap, not that it is too small. It looks like you are running out of memory.



SQL1221N The Application Support Layer heap cannot be
allocated.

Explanation:

The Application Support Layer heap could not be allocated. The
cause of this error may be insufficient memory resources either
for the database manager or the environment in which its
operations are being attempted. Memory resources that can cause
this error include:

o The number of shared memory identifiers allocated in the
system

o The amount of paging or swapping space available in the
system

o The amount of physical memory available in the system



User Response:

One or more of the following:

o Validate that sufficient memory resources are available to
satisfy the database manager's requirements, and those of the
other programs running on the system.

o Reduce the aslheapsz configuration parameter.

o Where appropriate, stop other programs using the system.



sqlcode : -1221

sqlstate : 57011


Andy
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