APAR status
Closed as fixed if next.
Error description
In a Federated environment, a Big SQL query that references a catalog lookup on a Federated object (for example, to access an index) may result in an sqlcode -901. You will see messages similar to the following in the db2diag.log. . In particular, look for the error "WITH HOLD but usage lock argument null" in the SQLCA structure. . db2diag.log: 2019-05-10-12.13.17.206177-240 I1195589E924 LEVEL: Severe PID : 1063744 TID : 140554524419840 PROC : db2sysc 0 INSTANCE: bigsql NODE : 000 DB : BIGSQL APPHDL : 0-32411 APPID: ***.**.*.***.****.****** AUTHID : BIGSQL HOSTNAME: test.test.com EDUID : 2754 EDUNAME: db2agent (BIGSQL) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:300 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 38 sqlerrmc: WITH HOLD but usage lock argument null sqlerrp : SQLRC034 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFFFB (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: The failing process will show the following stack: 0x00007FFFF1D28507 _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x00a7 0x00007FFFF1D28329 _Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x0199 0x00007FFFF0A26CCD sqlrrSqlCode + 0x00dd 0x00007FFFF1468EE8 _Z20sqlrlc_request_ulockP8sqlrr_cbP19sqlrlc_entry_commonP20sqlrl c_anchor_commonPbjjjPjP14SQLP_LOCK_INFOS8_S6_ + 0x0978 0x00007FFFF1467471 _Z30sqlrlc_find_request_usage_lockP8sqlrr_cbP10sqlrlc_keyjjjPP19 sqlrlc_entry_commonPjP14SQLP_LOCK_INFOS8_ + 0x0431 0x00007FFFF1492C6F _Z16sqlrlc_fed_fetchP8sqlrr_cbPhtS1_tS1_tjjjP13SQLO_MEM_POOLP14S QLP_LOCK_INFOP21sqlrlc_systables_info + 0x021f 0x00007FFFEF8B3D84 _Z15sqlnq_cat_look2P20sqlnq_multipart_namePP9sqlnq_ftbP3loc21sql nq_hierarchy_usagebPKjP12sqlnq_stringb + 0x17d4 _Z14sqlnq_cat_lookP20sqlnq_multipart_namePP9sqlnq_ftbP3loc21sqln q_hierarchy_usagebPKjP12sqlnq_stringb + 0x0204 0x00007FFFEF9C387A _Z27sqlnq_handle_qtb_extref_rec20sqlnq_multipart_namePP9sqlnq_qt biP3loc21sqlnq_hierarchy_usageP9sqlnq_pid + 0x00ca 0x00007FFFEF9BFA3D address: 0x00007FFFEF9BFA3D ; dladdress: 0x00007FFFE9497000 ; offset in lib: 0x0000000006528A3D ; 0x00007FFFEF9BF93B address: 0x00007FFFEF9BF93B ; dladdress: 0x00007FFFE9497000 ; offset in lib: 0x000000000652893B ; 0x00007FFFEF9BF93B address: 0x00007FFFEF9BF93B ; dladdress: 0x00007FFFE9497000 ; offset in lib: 0x000000000652893B ; 0x00007FFFEF9BE846 _Z29sqlnq_handle_named_ref_in_srcP12sqlnq_stringiPP9sqlnq_qtbPP9 sqlnq_qunPP9sqlnq_qncPP9sqlnq_pidP3loc21sqlnq_hierarchy_usageP20 sqlnq_multipart_nameSB_ + 0x0396 0x00007FFFEFA56037 _Z22sqlnq_handle_table_refP20sqlnq_multipart_namePP9sqlnq_qunP9s qlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usageP9sqlnq_pid + 0x0967 0x00007FFFEFA55050 _Z27sqlnq_handle_from_table_refP20sqlnq_multipart_namePhiPP9sqln q_qunP9sqlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usagePP8stknod e_ + 0x00a0 0x00007FFFEFA69AA3 _Z9sqlnq_semPP8stknode_i10actiontypePhP3loc + 0x9be3 0x00007FFFEF654BE3 _Z12sqlnp_smactnP8sqlnp_cbi + 0x06b3 0x00007FFFEF645C7E _Z12sqlnp_parserP8sqlnp_cb + 0x231e 0x00007FFFEF64CF64 _Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur + 0x06d4 0x00007FFFEF1BE4FB _Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq lrr_cmpl_enviiPP9sqlnq_qur + 0x19eb 0x00007FFFEF1BCB01 _Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq lrr_cmpl_env + 0x0021 0x00007FFFF0BCD2B4 _Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP _LOCK_INFOP16sqlra_cached_varPiS5_Pb + 0x10f4 0x00007FFFF0BE9ABE _Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj jPhjthP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK _INFOPP16sqlra_cached_varS8_bSA_Pb + 0x096e 0x00007FFFF0C8ACB1 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x0f11
Local fix
Problem summary
Please see problem description.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
PH12085
Reported component name
IBM BIG SQL
Reported component ID
5737E7400
Reported release
504
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-14
Closed date
2020-09-09
Last modified date
2020-09-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"504"}]
Document Information
Modified date:
10 September 2020