Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2009
    Posts
    23

    Unanswered: While Running Runstats got an SQL2310N error

    I kicked off the Runstats on DB2 v9.1 and got some SQL2310N errors:

    SQL2310N The utility could not generate statistics. Error "-930" was
    returned.

    Here is what the db2diag.log looked like:

    2009-12-29-19.40.53.548871-360 E1353668A1692 LEVEL: Warning (OS)
    PID : 5927050 TID : 1 PROC : db2agent (PSFTPROD) 0
    INSTANCE: db2inst1 NODE : 000 DB : PSFTPROD
    APPHDL : 0-766 APPID: *LOCAL.db2inst1.100120181730
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, SQO Memory Management, sqloLogMemoryCondition, probe:100

    CALLED : OS, -, malloc
    OSERR : ENOMEM (12) "Not enough space"
    MESSAGE : Private memory and/or virtual address space exhausted, or data ulimit exceeded
    DATA #1 : Soft data resource limit, PD_TYPE_RLIM_DATA_CUR, 8 bytes
    251657728
    DATA #2 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes
    33624064
    DATA #3 : Current set size, PD_TYPE_SET_SIZE, 8 bytes
    200671232
    CALLSTCK:
    [0] 0x0900000002970218 sqloLogMemoryCondition + 0x270
    [1] 0x090000000296FEF0 sqloLogMemoryCondition@glue20D + 0x74
    [2] 0x09000000032C10E0 sqlogmblkEx + 0xC
    [3] 0x090000000460E9FC init_trace__FP17schs_cluster_data + 0x1E4
    [4] 0x09000000046CC404 sqlis_pre_process_epfis__FP9schs_data + 0x114
    [5] 0x0900000003D532AC sqliInitStatsStruct__FP9schs_dataP10SQLD_ISTATP10S QLD_CSTATP10SQLD_TSTATiP9SQLD_IDEFUl + 0x4B8
    [6] 0x0900000003DBB834 sqlischs__FP7SQLI_CBP10SQLD_ISTATP10SQLD_CSTATP10S QLD_TSTATi + 0xC0
    [7] 0x0900000003DBAE84 sqlistat__FP20sqle_agent_privatecbP8SQLD_CCBUiP9SQ LD_IXCBP10SQLD_ISTATP10SQLD_CSTATP10SQLD_TSTAT + 0x748
    [8] 0x0900000002F2BBC4 sqldIndexStats__FP20sqle_agent_privatecbUsT2UcT2iU iP10SQLD_ISTATP10SQLD_TSTATPcT6T10_T6 + 0x11E8
    [9] 0x09000000033C9A10 sqlrLocalRunstats__FP8sqlrr_cbP11sqlrrstringN22UcU sT6PP8sqlrg_pdiN39P16sqlrl_stats_colsPPsUiPPUsT15_
    dT15_T6PP20sqlr_runstats_re + 0x1130

    2009-12-29-19.40.53.550071-360 E1355361A685 LEVEL: Warning
    PID : 5927050 TID : 1 PROC : db2agent (PSFTPROD) 0
    INSTANCE: db2inst1 NODE : 000 DB : PSFTPROD
    APPHDL : 0-766 APPID: *LOCAL.db2inst1.100120181730
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions, probe:30
    DATA #1 : <preformatted>
    Out of memory failure for Private Heap on node 0.
    Requested block size : 33554408 bytes.
    Physical heap size : 157614080 bytes.
    Configured heap size : 1099511824384 bytes.
    Unreserved memory used by heap : 0 bytes.
    Unreserved memory left in set : 0 bytes.


    2009-12-29-19.40.53.550483-360 I1356047A447 LEVEL: Severe
    PID : 5927050 TID : 1 PROC : db2agent (PSFTPROD) 0
    INSTANCE: db2inst1 NODE : 000 DB : PSFTPROD
    APPHDL : 0-766 APPID: *LOCAL.db2inst1.100120181730
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, index manager, init_trace, probe:622
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF0B10 : 8B0F 0000


    Anyway, the I Googled this problem and read that I should increase the STAT_HEAP_SZ or set to Automatic to resolve this problem. Our Senior DBA says that STAT_HEAP_SZ of 75000 should be plenty.

    So now I don't know where to turn or what to do. Do you have any suggestions on these errors?

    Thank you.

    CC

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    If this is AIX, check user data limit of the instance owner id. The command is "ulimit -d". For DB2 v9, it's ok to set it to unlimited or some high value. Change it, restart the instance and then retry the runstats command.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •