JR32247: FED: -902 STORED PROC NOT FOUND CASUED BY SQLRIFEDINVOKERTRUSTED

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• Hi all,
  For the second issue brought up by Wallace, the direct cause
  is that sqlqgDyload doesn't secure a valid return code for RDS.
  
  The current logic of Federation return code to RDS is: rc
  should be set to SQLQG_RC_CA_BUILT and sqlca->sqlcode is set to
  a negative value.  But when sqlqgDyload receive
  rc=SQLO_PROC_NOT_FOUND from lower layer, it doesn't setup
  correct rc and SQLCA, which causes crash in sqlrrMapZrc.
  I can recreate this error by forcing the return value of
  sqlqgDyload into SQLO_PROC_NOT_FOUND:
  0x09000000003A189C pthread_kill + 0x88
  0x090000000620E598 sqloDumpEDU + 0x38
  0x09000000063FDED0
  sqlzeMapZrc__FP8sqeAgentUiUlT2P5sqlcaiPC12sqlzeContext + 0xC10
  0x090000001D398C54 sqlrrMapZrc__FP8sqlrr_cbUiUli + 0xB4
  0x090000001DD7FA88
  sqlriFedInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntf
  + 0x188
  0x090000001DD7FEE0
  sqlriFedInvokeInvoker__FP10sqlri_ufobP14sqlqg_Fmp_Info + 0x1E0
  0x090000000B1C08AC
  sqlqg_Call_FMP_Thread__FP17sqlqg_FMP_RequestPP15sqlqg_FMP_Reply
  + 0x56C
  0x090000000B1C9D50 sqlqgFedStart__FP14UnfencedServerc + 0xA50
  0x090000000B179D50 sqlqgOpen__FP12sqlri_rquery + 0x4D0
  0x090000001E199214 sqlri_djx_rta__FP8sqlrr_cb + 0x774
  0x090000001D9F9BF4 sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm
  + 0x514
  0x090000001D9FA698 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm
  + 0x518
  0x090000001DC4CC78
  sqlrr_process_fetch_request__FP14db2UCinterface + 0xD78
  0x090000001DC50B68
  sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0xDA8
  As for why sqlqgDyload returns error, we need to do more
  investigation. But since this is a less severe problem(it can
  be invoked in very rare conditions), we will address it if it
  has severe impact on DB2 SVT.
  

Local fix

Problem summary

• Users affected:
    Users affected: Users of the DB2 for LUW Homogeneous
  Federation Feature or InfoSphere Federation Server
  Problem description and summary:
    See error description
  

Problem conclusion

• Problem was first fixed in Version 9.1, FixPak 7 (s090308). This
  fix should be applied on the federation server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR32250

Fix information

• Fixed component name

  FEDERATED RUNTI

• Fixed component ID

  5724N9703

Applicable component levels

• R910 PSN

     UP

• R911 PSN

     UP