DB2 查询表时出现SQL0083C内存分配出错,该怎么处理?

1.数据库诊断日志如下2017-03-09-12.50.21.468027+480 I4080263355A2438   LEVEL: WarningPID     : 790574               TID  : 1        &nbs...显示全部

1.数据库诊断日志如下

2017-03-09-12.50.21.468027+480 I4080263355A2438   LEVEL: Warning

PID     : 790574               TID  : 1           PROC : db2agent (TWHIS)

INSTANCE: db2inst2             NODE : 000         DB   : TWHIS

APPHDL  : 0-125                APPID: *LOCAL.db2inst2.170309044955

AUTHID  : DB2ADMIN

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

12

DATA #3 : Memory pool handle pointer, PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes

0x0000000111c50608

DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes

18446744073708602920

DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 bytes

18446744073708602944

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

0x0000000111c91ae8

DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 11 bytes

sqlnq_ftb.C

DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes

15942

DATA #10: Resource binding pointer, PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes

0x0000000000000000

CALLSTCK:

  [0] 0x0900000002FDCED8 sqlogmblkEx + 0x4F4

  [1] 0x0900000003943340 populate_from_cd__9sqlnq_cstFP8sqlrg_cdP3loc + 0x870

  [2] 0x0900000003490398 need_statistics__9sqlnq_fcsFP3loc + 0x138

  [3] 0x09000000046CCF14 sqlno_global_cols_width__FP13sqlno_globals9sqlno_setP9sqlno_qtbP19sqlno_plan_functionP21sqlno_plan_propertiesPfN46 + 0xC8

  [4] 0x0900000004445AA8 sqlno_cols_width__FP13sqlno_globals9sqlno_setP9sqlno_qtbP19sqlno_plan_functionP21sqlno_plan_propertiesPfN46 + 0x7C

  [5] 0x0900000004740EC8 sqlno_get_buffer_size__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionP9sqlno_qtbfN25PfPdT8 + 0xC0

  [6] 0x090000000224B04C sqlno_cost_vrm_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionf + 0x588

  [7] 0x090000000224A180 sqlno_cost_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionf + 0x12C

  [8] 0x0900000002249CD4 sqlno_prop_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionP18sqlno_join_context + 0x728

  [9] 0x090000000225C900 TSCAN__FP13sqlno_globalsP13sqlno_contextP17sqlno_access_path9sqlno_setN34P20sqlno_qun2plan_arrayP10sqlno_partP16sqlno_dpart_eli + 0x100

2017-03-09-12.50.21.468665+480 I4080265794A2438   LEVEL: Warning

PID     : 790574               TID  : 1           PROC : db2agent (TWHIS)

INSTANCE: db2inst2             NODE : 000         DB   : TWHIS

APPHDL  : 0-125                APPID: *LOCAL.db2inst2.170309044955

AUTHID  : DB2ADMIN

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

12

DATA #3 : Memory pool handle pointer, PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes

0x0000000111c50608

DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes

18446744073708902744

DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 bytes

18446744073708902784

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

0x0000000111c91bd8

DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 11 bytes

sqlnq_ftb.C

DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes

15942

DATA #10: Resource binding pointer, PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes

0x0000000000000000

CALLSTCK:

  [0] 0x0900000002FDCED8 sqlogmblkEx + 0x4F4

  [1] 0x0900000003943340 populate_from_cd__9sqlnq_cstFP8sqlrg_cdP3loc + 0x870

  [2] 0x0900000003490398 need_statistics__9sqlnq_fcsFP3loc + 0x138

  [3] 0x09000000046CCF14 sqlno_global_cols_width__FP13sqlno_globals9sqlno_setP9sqlno_qtbP19sqlno_plan_functionP21sqlno_plan_propertiesPfN46 + 0xC8

  [4] 0x0900000004445AA8 sqlno_cols_width__FP13sqlno_globals9sqlno_setP9sqlno_qtbP19sqlno_plan_functionP21sqlno_plan_propertiesPfN46 + 0x7C

  [5] 0x0900000004740EC8 sqlno_get_buffer_size__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionP9sqlno_qtbfN25PfPdT8 + 0xC0

  [6] 0x090000000224B04C sqlno_cost_vrm_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionf + 0x588

  [7] 0x090000000224A180 sqlno_cost_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionf + 0x12C

  [8] 0x0900000002249CD4 sqlno_prop_scan__FP13sqlno_globalsP21sqlno_plan_propertiesP19sqlno_plan_functionP18sqlno_join_context + 0x728

  [9] 0x090000000225C900 TSCAN__FP13sqlno_globalsP13sqlno_contextP17sqlno_access_path9sqlno_setN34P20sqlno_qun2plan_arrayP10sqlno_partP16sqlno_dpart_eli + 0x100

收起
参与6

查看其它 2 个回答coilon的回答

coiloncoilon其它软件公司

能具体点么?

1.操作系统实际内存和虚拟内存足够

2.尝试杀死DB2所有进程,重启数据库,问题依旧

IT其它 · 2017-03-09
浏览3162

回答者

coilon
其它软件公司

coilon 最近回答过的问题

回答状态

  • 发布时间:2017-03-09
  • 关注会员:3 人
  • 回答浏览:3162
  • X社区推广