|
Problem IC88618
|
Status: Closed |
DB2 TERMINATES ABNORMALLY WHEN A CURSOR CONSTRUCTOR IS ASSIGNED TO A PARAMETER MARKER |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DB2 may terminate abnormally when a cursor constructor is
assigned to a parameter marker in an anonymous block.
The stack trace looks like the following:
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002AAAB2F67B35 ossDumpStackTraceEx + 0x0301
(/home/hotel26/petrus/sqllib/lib64/libdb2osse.so.1)
0x00002AAAB2F621A6 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x0270
(/home/hotel26/petrus/sqllib/lib64/libdb2osse.so.1)
0x00002AAAAE6E1639 sqlo_trce + 0x04df
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAE7E4187 sqloEDUCodeTrapHandler + 0x0467
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAABD4D60 address: 0x00002AAAAABD4D60 ; dladdress:
0x00002AAAAABC7000 ; offset in lib: 0x000000000000DD60 ;
(/lib64/libpthread.so.0)
0x00002AAAADC2397F _ZN20sqlnq_multipart_name8name_catEPh +
0x006d
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD93E89F
_Z26sqlnq_psm_process_set_stmtP9sqlnq_pidS0_P3loc + 0x11ef
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD9498BC
_Z17sqlnq_psm_sem_actPP8stknode_i10actiontypePhP3loc + 0x79e0
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD8699A6 _Z12sqlnp_smactnP8sqlnp_cbi + 0x11a4
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD8591E5 _Z12sqlnp_parserP8sqlnp_cb + 0x159b
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD85F4C5
_Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur + 0x0c5d
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD4B480B
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_enviiPP9sqlnq_qur + 0x5c89
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
0x00002AAAAD4AE79E
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_env + 0x007c
(/home/hotel26/petrus/sqllib/lib64/libdb2e.so.1)
....... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fixpack 2 or above. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 Version 10.1 Fixpack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2012
15.01.2013
15.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
