| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Memory allocation failure - MQSI 2.0.2 on SunSolaris |
« View previous topic :: View next topic » |
| Author |
Message
|
| MVO |
 Posted: Fri Nov 30, 2001 11:41 am Post subject: |
 |
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
| I'm running MQSI 2.0.2 on Sun Solaris with DB2 V7.2, one broker, 11 message flows. In addition to the DB2 broker database, the broker is also accessing 3 other DB2 databases on the same server and instance. When I increased the number of add. instances for one (complex) message flow to 9 (i.e. 10 // threads), DB2 ran out of memory (db2diag.log). There were 46 db2sysc processes running with sizes ranging from 115M to 204M. Why there are so many db2sysc processes ? |
|
| Back to top |
|
 |
| zpat |
| Posted: Fri Nov 30, 2001 3:16 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
|
| Back to top |
|
|
| Outdesign |
| Posted: Mon Dec 03, 2001 4:08 am Post subject: |
|
|
Apprentice
Joined: 16 Sep 2001
Posts: 38
Location: Hampshire, UK
|
MQSIv2.0.2 does NOT support DB2v7.2 :
(*)DB2 V7.1 (GA Level) with ODBC driver.
Note: There are known problems with MQSI & DB2 V7.1 FixPack 2a and 3 on SUN Solaris.
There is a valid workaround documented which is supported & tested by the MQSI organisation.
Contact your local support team for details
As the previous poster indicated, refer to the website Supported Software pages at :
http://www-4.ibm.com/software/ts/mqseries/platforms/supported/mqseries_integ_for_solaris_2_02.html
HOWEVER, you have indicated "DB2 ran out of memory (db2diag.log)".
What extactly is recorded in the db2diag.log ?
What is the broker reporting in it's syslog ?
Is the broker reporting SQL0954C "Not enough storage is available in the
application heap to process the statement" errors ?
|
|
| Back to top |
|
|
| MVO |
| Posted: Mon Dec 03, 2001 6:32 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
db2diag.log:
2001-11-30-16.31.33.427813 Instance:db2inst1 Node:000
PID:1362(db2ipccm) Appid:none
common_communication sqlccGetIPCs Probe:1
DIA3605C Memory allocation failure occurred.
ZRC=FFFFD605
Data Title:IPC Shared Memory Size PID:1362 Node:000
0271 000c .q..
Data Title:SQLCA PID:1390 Node:000
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 3
sqlerrmc: 81
sqlerrp : sqlearcn
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x000000FF (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) ( (9) (10) (11)
sqlstate:
Where is the broker's system log?
By the way, I upgraded my DB2 to 7.2 (by applying FP3) and haven't seen any major problem yet. The memory problem happens before and after the upgrade.
[ This Message was edited by: MVO on 2001-12-03 06:42 ] |
|
| Back to top |
|
|
| mpuetz |
| Posted: Mon Dec 17, 2001 4:41 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
see my reply to BIP 2066E ...
on heap parameters for DB2.
Mathias Puetz
IBM-EMEA AIM Services
MQ/MQSI Specialist |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
