During query or modification operations against a VARCHAR column
in a column organized table, one of several assertions
may be triggered or a trap could be encountered. These
assertions check the validity of on disk structures. You may
see
messages similar to one of the following in the db2diag.log:
FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:6275
DATA #1 : String, 162 bytes
AssertionFailedException: An assertion 'length <=
mType.getLength()' failed. Additional info: data length is too
big 44 40
Thrown at ../../types/Vector.hpp : 6275
DATA #2 : Function name in Library, 99 bytes
ibm_cde::types::Vector<ibm_cde::types::VarLenString,0,0>::update
ValueAt(Uint, const VarLenString &)
DATA #3 : File name, 22 bytes
../../types/Vector.hpp
FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:5532
DATA #1 : String, 162 bytes
AssertionFailedException: An assertion 'length <=
mType.getLength()' failed. Additional info: too long 119 34
T2(117,1208)
Thrown at ../../types/Vector.hpp : 5532
DATA #2 : Function name in Library, 99 bytes
ibm_cde::types::Vector<ibm_cde::types::VarLenString,0,0>::setLen
gthForValueAt(Uint64, Uint32) const
DATA #3 : File name, 22 bytes
../../types/Vector.hpp
A potential trap that you may encounter follows:
Stack #1 Signal #11 Timestamp
2013-09-28-09.02.09.078581
0 ossDumpStackTraceInternal
1 ossDumpStackTraceV98
2 OSSTrapFile::dumpEx
3 sqlo_trce
4 sqloEDUCodeTrapHandler
5 __PRETTY_FUNCTION__.5889
6 __intel_new_memset
7 ibm_cde::types::Vector<ibm_cde::types::VarLenString,
8
ibm_cde::query::ConcatEvaluator::processInputsSynchronously
9 ibm_cde::query::Evaluator::evaluate
10 ibm_cde::query::EvaluationRoutine::evaluate
11 ibm_cde::query::Scheduler::runThreadTask
12 ibm_cde::query::cdeEntryPointImpl
13 ibm_cde::query::cdeEntryPoint
14 sqlriInvokeCde |
