Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / IBM DB2, WebSphere, IMS, U2, etc Новый топик    Ответить
 DIA8563C An invalid memory size was requested.  [new]
Oleg Kozlovski
Member

Откуда:
Сообщений: 8
может кто-то встречался с подобным?
что тут может быть не так?

db2diag.log


2010-01-22-04.16.14.672676+330 I1A1594 LEVEL: Event
PID : 8728 TID : 4398344299056PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SDB
APPHDL : 0-38290 APPID: *LOCAL.db2inst1.100121224424
AUTHID : DB2INST1
EDUID : 7730 EDUNAME: db2agent (SDB) 0
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09054"
with level identifier "06050107".
Informational tokens are "DB2 v9.5.0.4", "s090429", "MI00304", Fix Pack "4".
DATA #2 : System Info, 440 bytes
System: Linux g28lcihttp01 6 2 ppc64
CPU: total:2 online:2 Cores per socket:1 Threading degree per core:2
Physical Memory(MB): total:8048 free:1405
Virtual Memory(MB): total:16240 free:9597
Swap Memory(MB): total:8192 free:8192
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:1024
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:9223372036854775807 shmMin:1
shmIDs:4096 shmSegments:4096 semMap:256000 semIDs:1024
semNum:256000 semUndo:256000 semNumPerID:250 semOps:32
semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767
Cur data size (bytes) = 0xFFFFFFFF
Cur stack size (bytes) = 0x00800000
Cur core size (bytes) = 0x00000000
nofiles (descriptors) = 0x0000FFFE

Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2010-01-22-04.16.14.672594+330 I1596A2166 LEVEL: Warning
PID : 8728 TID : 4398344299056PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SDB
APPHDL : 0-38290 APPID: *LOCAL.db2inst1.100121224424
AUTHID : DB2INST1
EDUID : 7730 EDUNAME: db2agent (SDB) 0
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx, probe:1000
MESSAGE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt invalid size"
DIA8563C An invalid memory size was requested.
DATA #1 : String, 43 bytes
Memory management block allocation failure.
DATA #2 : Codepath, 8 bytes
2
DATA #3 : Memory pool handle pointer, PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes
0x000004001bfa0ce8
DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes
0
DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 bytes
0
DATA #6 : Options for requested block, PD_TYPE_GET_MEM_OPTIONS, 4 bytes
0x00000000
DATA #7 : Pointer to address that will be set by new allocation, PD_TYPE_PTR_TO_ADDRESS_OUT, 8 bytes
0x0000040011bf07b0
DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 13 bytes
sqlnr_rule5.C
DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes
3857
DATA #10: Resource binding pointer, PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes
0x0000000000000000
CALLSTCK:
[0] 0x0000040000F11A70 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0xEA8A70
[1] 0x0000040000F0FBC8 pdLog + 0xFFFFFFFFFBF00608
[2] 0x0000040002874FCC sqlogmblkEx + 0xFFFFFFFFFD7E33EC
[3] 0x000004000255B308 _Z16sqlnr_count_qncsP9sqlnq_qunPPiS1_ + 0xFFFFFFFFFD4D8D10
[4] 0x0000040002482F40 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x2419F40
[5] 0x0000040002484210 _Z20sqlnr_reorder_IJ_qgmP9sqlnq_qunP9sqlnq_oprPP13sqlnq_deplistPiP3loc + 0xFFFFFFFFFD404648
[6] 0x00000400025F506C _Z20sqlnr_qrwprep_phase2P3locPi + 0xFFFFFFFFFD570C2C
[7] 0x0000040002410BD4 _Z18sqlnr_prep2_actionP10sqlnr_qrwaPiP14sqlnr_progress + 0xFFFFFFFFFD39265C
[8] 0x00000400025A4B4C _Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progress + 0xFFFFFFFFFD52157C
[9] 0x00000400025A5054 _Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xFFFFFFFFFD521A6C

db2mtrk -i -d -v


Memory for instance

Other Memory is of size 14548992 bytes
FCMBP Heap is of size 851968 bytes
Database Monitor Heap is of size 327680 bytes
Total: 15728640 bytes

Memory for database: SDB

Backup/Restore/Util Heap is of size 65536 bytes
Package Cache is of size 33816576 bytes
Other Memory is of size 196608 bytes
Catalog Cache Heap is of size 917504 bytes
Buffer Pool Heap (3) is of size 70451200 bytes
Buffer Pool Heap (2) is of size 8781824 bytes
Buffer Pool Heap (1) is of size 16056320 bytes
Buffer Pool Heap (System 32k buffer pool) is of size 851968 bytes
Buffer Pool Heap (System 16k buffer pool) is of size 589824 bytes
Buffer Pool Heap (System 8k buffer pool) is of size 458752 bytes
Buffer Pool Heap (System 4k buffer pool) is of size 393216 bytes
Shared Sort Heap is of size 1179648 bytes
Lock Manager Heap is of size 655360 bytes
Database Heap is of size 40566784 bytes
Application Heap (456) is of size 65536 bytes
Application Heap (455) is of size 65536 bytes
Application Heap (454) is of size 65536 bytes
Application Heap (453) is of size 65536 bytes
Application Heap (400) is of size 65536 bytes
Application Heap (317) is of size 65536 bytes
Application Heap (251) is of size 65536 bytes
Application Heap (113) is of size 65536 bytes
Application Heap (112) is of size 65536 bytes
Application Heap (111) is of size 65536 bytes
Application Heap (110) is of size 65536 bytes
Applications Shared Heap is of size 2162688 bytes
Total: 177864704 bytes
25 янв 10, 14:24    [8240899]     Ответить | Цитировать Сообщить модератору
 Re: DIA8563C An invalid memory size was requested.  [new]
Mark Barinstein
Member

Откуда: Москва
Сообщений: 4947
Oleg Kozlovski
может кто-то встречался с подобным?
что тут может быть не так?

db2diag.log


2010-01-22-04.16.14.672676+330 I1A1594 LEVEL: Event
PID : 8728 TID : 4398344299056PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SDB
APPHDL : 0-38290 APPID: *LOCAL.db2inst1.100121224424
AUTHID : DB2INST1
EDUID : 7730 EDUNAME: db2agent (SDB) 0
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09054"
with level identifier "06050107".
Informational tokens are "DB2 v9.5.0.4", "s090429", "MI00304", Fix Pack "4".
DATA #2 : System Info, 440 bytes
System: Linux g28lcihttp01 6 2 ppc64
CPU: total:2 online:2 Cores per socket:1 Threading degree per core:2
Physical Memory(MB): total:8048 free:1405
Virtual Memory(MB): total:16240 free:9597
Swap Memory(MB): total:8192 free:8192
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:1024
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:9223372036854775807 shmMin:1
shmIDs:4096 shmSegments:4096 semMap:256000 semIDs:1024
semNum:256000 semUndo:256000 semNumPerID:250 semOps:32
semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767
...
Дюже много цифр...
Поставьте в /etc/sysctl.conf
kernel.shmmax=1073741824
как указано в Modifying kernel parameters (Linux).
25 янв 10, 16:06    [8241811]     Ответить | Цитировать Сообщить модератору
 Re: DIA8563C An invalid memory size was requested.  [new]
Oleg Kozlovski
Member

Откуда:
Сообщений: 8
Mark Barinstein
Дюже много цифр...
Поставьте в /etc/sysctl.conf
kernel.shmmax=1073741824
как указано в Modifying kernel parameters (Linux).


попробовали - не помогает.
уж очень текст ошибки наводит на баг в самой DB2...
8 фев 10, 18:53    [8313543]     Ответить | Цитировать Сообщить модератору
 Re: DIA8563C An invalid memory size was requested.  [new]
Mark Barinstein
Member

Откуда: Москва
Сообщений: 4947
Oleg Kozlovski,

покажите опять тот же кусок из db2diag.log после исправлений и, если есть, последующие ошибки после DIA8563C.
10 фев 10, 13:55    [8323392]     Ответить | Цитировать Сообщить модератору
Все форумы / IBM DB2, WebSphere, IMS, U2, etc Ответить