IBM Support

Import task failed with "DBO.DATASOURCE_ANALYSES_TRIGGER_UPDATE". Information returned for the error includes SQLCODE "-930", SQLSTATE "57011".

Technote (FAQ)


Question

Import task failed with "DBO.DATASOURCE_ANALYSES_TRIGGER_UPDATE". Information returned for the error includes SQLCODE "-930", SQLSTATE "57011".

Cause


Environment:

IEM v9.1 and ILMT v9.0 with DB2 Workgroup Server Edition v10.1 fixpack 3 installed on Linux with 16gig RAM.
TEMA version: 9.0.20140311-1626


The Import task suddenly failed with the following error in the tema.log:



2014-04-23 15:44:34 (+0:00:00.233) INFO: ETL from Data Source -
DatasourceAnalysis (0x00000000006119CE -0x000000000068BCA4): Failed
2014-04-23 15:44:34 (+0:00:00.015) ERROR: Sequel::DatabaseError:
NativeException: com.ibm.db2.jcc.am.SqlException: An error occurred in a
triggered SQL statement in trigger "DBO.DATASOURCE_ANALYSES_TRIGGER_UPDATE". Information returned for the
error includes SQLCODE "-930", SQLSTATE "57011" and message tokens ""..
SQLCODE=-723, SQLSTATE=09000, DRIVER=3.64.104
com/ibm/db2/jcc/am/bd.java:682:in `a'
com/ibm/db2/jcc/am/bd.java:60:in `a'
com/ibm/db2/jcc/am/bd.java:127:in `a'
com/ibm/db2/jcc/am/io.java:2706:in `c'
com/ibm/db2/jcc/am/io.java:2694:in `d'
com/ibm/db2/jcc/am/io.java:2077:in `b'
com/ibm/db2/jcc/t4/ab.java:225:in `i'
com/ibm/db2/jcc/t4/ab.java:48:in `c'
com/ibm/db2/jcc/t4/p.java:38:in `b'
com/ibm/db2/jcc/t4/qb.java:114:in `h'
com/ibm/db2/jcc/am/io.java:2072:in `fb'
com/ibm/db2/jcc/am/io.java:3227:in `a'
com/ibm/db2/jcc/am/io.java:1066:in `e'
com/ibm/db2/jcc/am/io.java:1049:in `execute'


The db2diag.log showed these errors:

2014-04-23-12.49.12.657357-300 I12915296E998 LEVEL: Warning
PID : 2359 TID : 140468033677056 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SUADB
APPHDL : 0-74 APPID: 127.0.0.1.55883.140423174831
AUTHID : DASUSR1 HOSTNAME: removed.com
EDUID : 84 EDUNAME: db2agent (SUADB)
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
2147549184
DATA #3 : unsigned integer, 8 bytes
0
DATA #4 : String, 7 bytes
PRIVATE
DATA #5 : unsigned integer, 8 bytes
86310912
DATA #6 : unsigned integer, 8 bytes
0
DATA #7 : unsigned integer, 8 bytes
8548843520
DATA #8 : unsigned integer, 8 bytes
8589934592
DATA #9 : unsigned integer, 8 bytes
1425408000



2014-04-23-12.49.12.657948-300 E12919911E781 LEVEL: Warning
PID : 2359 TID : 140468033677056 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SUADB
APPHDL : 0-74 APPID: 127.0.0.1.55883.140423174831
AUTHID : DASUSR1 HOSTNAME: removed.com
EDUID : 84 EDUNAME: db2agent (SUADB)
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions,
probe:30
DATA #1 : <preformatted>
Out of memory failure for User Data Private Heap.
Requested block size : 2147485632 bytes.
Physical heap size : 67764224 bytes.
Configured heap size : 1099511627776 bytes.
Unreserved memory used by heap : 0 bytes.
Unreserved memory left in set : 0 bytes.


2014-04-25-15.20.00.134484-300 E13623955E696 LEVEL: Warning
PID : 2361 TID : 140060951308032 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SUADB
APPHDL : 0-47 APPID: 127.0.0.1.59191.140425201914
AUTHID : DASUSR1 HOSTNAME: removed.com
EDUID : 60 EDUNAME: db2agent (SUADB)
FUNCTION: DB2 UDB, SQO Memory Management,
SqloMemController::getPartitionStats, probe:10
DATA #1 : <preformatted>
Instance Memory Controller statistics.
Instance Memory Automatic: Yes.
Maximum size = 8388608 KB <---8GB is maximum size
Current size = 8294592 KB < --Currently using 8GB
Usage HWM = 8296704 KB
Cached memory = 0 KB
Cached DB memory = 0 KB


=============


db2 => connect to SUADB

Database Connection Information

Database server = DB2/LINUXX8664 10.1.3
SQL authorization ID = DB2INST1
Local database alias = SUADB

db2 => GET DATABASE MANAGER CONFIGURATION


Size of instance shared memory (4KB) (INSTANCE_MEMORY) =
AUTOMATIC(2097152)


The above setting shows a limit of 8GB database_memory automatic assigned to this instance. This is based on the DB2 Workgroup Server Edition "Restricted" license type with pre-defined up to 8gig max memory.

db2licm -l


Product name: "DB2 Workgroup Server Edition"
License type: "Restricted"
Expiry date: "Permanent"
Product identifier: "db2wse"
Version information: "10.1"
Max amount of memory (GB): "8"


Answer

The ILMT v9.0 might support DB2 Workgroup Sever Edition v10.1.x as indicated below from the Installation Guide.



DB2 10.1 Fix Pack 2 or higher
DB2 10.5
(Workgroup Server Edition, Enterprise Server Edition, or Advanced Enterprise Server Edition)

However, upgrading to DB2 Workgroup Server Edition v10.5. fixpack 2 or higher will address this out of memory issue as it has predefined up to 128gig max memory.


Product name: "DB2 Workgroup Server Edition"
License type: "Restricted"
Expiry date: "Permanent"
Product identifier: "db2wse"
Version information: "10.5"
Max amount of memory (GB): "128"

Note: the ILMT v9.0 is bundled with DB2 Workgroup Server Edition v10.5 fixpack 2.

Document information

More support for: IBM License Metric Tool

Software version: 9.0

Operating system(s): Linux

Reference #: 1672740

Modified date: 04 June 2014