02-08-16, 23:25 #1Registered User
- Join Date
- Oct 2011
Unanswered: DB2 out of memories error: DIA 8300C
I am running IBM Collabolation LifeCycle Management (CLM)5.0.1 with DB210.5.
The system has been up and running for over 2 years. Recently DB2 constantly ran into "Out of Memories" problem for database QM and JTS. db2diag.zip is attached.
In particular, on line 727268, timestamp 2016-02-09-11.50.53 and 2016-02-09-11.47.17, there are "no memory available" and "no memory available in 'Applications Shared Heap" error for JTS and QM database, they both yielded error " DIA8300C A memory heap error has occurred".
I restarted the database, and users were able to work for around 3 or 4 hours, then memory error crashed the application again.
Please see bottom of the db2diag, which indicates error: ADM4000W A catalog cache condition has occurred for database QM, JTS and RM. Could this be the root cause of the problem ? Please offer help on how to configue the database to make it function normally.
Thanks you so much in advance for your help.
02-09-16, 04:28 #2Registered User
Provided Answers: 1
- Join Date
- Sep 2012
Can you show us outputs from
db2 get dbm cfg | findstr /i memory
db2 get db cfg for DB_NAME | findstr /i mem
02-09-16, 05:40 #3Registered User
Provided Answers: 55
- Join Date
- Jul 2013
- Moscow, Russia
Seems you were working on 2 GB RAM when you got these errors:
2016-02-08-15.16.07.554000+660 E28127167F1070 LEVEL: Event ... FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. Physical Memory(MB): total:2046 free:1504 available:1504 Virtual Memory(MB): total:8190 free:7648 Swap Memory(MB): total:6144 free:6144
Then you got an error:
2016-02-09-18.104.22.168000+660 I37892177F1013 LEVEL: Warning PID : 1700 TID : 4932 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : JTS APPHDL : 0-5917 APPID: 127.0.0.1.56667.160209001927 AUTHID : DB2ADMIN HOSTNAME: WIN-INREFR92I8P EDUID : 4932 EDUNAME: db2agent (JTS) FUNCTION: DB2 UDB, SQO Memory Management, SqloMemController::requestMemory, probe:50 MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory Available" DIA8300C A memory heap error has occurred. DATA #1 : String, 28 bytes Attempt to get memory failed DATA #2 : unsigned integer, 8 bytes 1048576 DATA #3 : unsigned integer, 8 bytes 0 DATA #4 : String, 13 bytes APPL-JTS DATA #5 : unsigned integer, 8 bytes 1900544 DATA #6 : unsigned integer, 8 bytes 0 DATA #7 : unsigned integer, 8 bytes 1634336768 DATA #8 : unsigned integer, 8 bytes 1635000320 DATA #9 : unsigned integer, 8 bytes 65536
Then you restarted DB2 with much more memory in the system:
2016-02-09-11.58.37.017000+660 E38219284F1072 LEVEL: Event ... FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. Physical Memory(MB): total:8190 free:6910 available:6910 Virtual Memory(MB): total:14334 free:13054 Swap Memory(MB): total:6144 free:6144Regards,
02-09-16, 15:58 #4Registered User
Provided Answers: 6
- Join Date
- May 2012
- Canberra, Australia
Crikey, I wouldn't be running DB2 in anything less than 16gb these days. Memory is cheap!Andy
"All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you cant get them together again, there must be a reason. By all means, do not use hammer. IBM maintenance manual, 1975 "