A fix is available
APAR status
Closed as new function.
Error description
ODBC SQLFetch() returns SQLCODE =-4746 when IDAA offloading is in use Additional keywords and symptoms: ********************************** IDAAV5R1/K IDAAV7R1/K IDAAV7R5/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of Db2 12 for z/OS * * ODBC/CLI driver using IBM Data Analytics * * Accelerator (IDAA). * **************************************************************** * PROBLEM DESCRIPTION: * * ODBC SQLFetch() fails with SQLCODE * * = -4746 THE STATEMENT CANNOT BE * * PROCESSED FOR AN ACCELERATED QUERY. * * REASON CODE 1 * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** An ODBC application prepares and executes a query which is successfully offloaded to IDAA. SQLFetch() can fail with SQLCODE -4746 and Reason Code 1 "The only FETCH statement that is allowed for a rowset cursor that is run by the accelerator is FETCH NEXT ROWSET." This error occurs because ODBC defined the cursor as a rowset cursor, but used the single-row-fetch type which is incompatible with offloaded rowset cursors. The following example illustrates the problem: 1. Db2 already has setup for IDAA 2. SQLSQLExecDirect() to execute the following SQL statement: SET CURRENT QUERY ACCELERATION = ALL 3. Prepare and execute an accelerated query 4. SQLBindCols() to bind the columns 5. SQLFetch() to fetch the data. SQLCODE = -4746
Problem conclusion
ODBC adds support to SQLFetch() to successfully retrieve data from an accelerated query. Note that the PTF for APAR PH41051 must be applied on the Db2 for z/OS server in order to make this APAR fully functional. Additional keywords: IDAAV5R1/K IDAAV7R1/K
Temporary fix
Comments
×**** PE22/04/13 FIX IN ERROR. SEE APAR PH45680 FOR DESCRIPTION ×**** PE22/04/13 FIX IN ERROR. SEE APAR PH45680 FOR DESCRIPTION ×**** PE22/04/13 FIX IN ERROR. SEE APAR PH45680 FOR DESCRIPTION
APAR Information
APAR number
PH41045
Reported component name
DB2 ODBC/JDBC/S
Reported component ID
5740XYR02
Reported release
C17
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-10-01
Closed date
2021-12-08
Last modified date
2022-05-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI78451 PH45680
Modules/Macros
DSNAOC02 DSNAOC03 DSNAOC04 DSNAOC05 DSNAOC06 DSNAOG02 DSNAOC07 DSNAOG03 DSNAOC08 DSNAOG04 DSNAOC09 DSNAOG05 DSNAOCLI DSNAOC0C DSNAOC0E DSNAOG0A DSNAOC0F DSNAOC0G DSNAOG0C DSNAOSDK DSNAOG0E DSNAOG06 DSNAOG07 DSNAOG08 DSNAOG09 DSNAOC0A DSNAOC0R DSNAOC13 DSNAOC0S DSNAOC14 DSNAOG0O DSNAOC15 DSNAOG0P DSNAOC0U DSNAOG0Q DSN@LIC1 DSNAOC17 DSNAOG0R DSNAOG13 DSNAOC0W DSNAOG0S DSNAOG14 DSNAOC0X DSNAOG15 DSNAOG0U DSNAOC0J DSNAOG0F DSNAOG0G DSNAOG0J DSNAOC0O DSNAOC0P DSNAOC0Q DSNAOG17 DSNAOG0W DSNAOG0X DSNAOC1S DSNAOC24 DSNAOC25 DSNAOC1U DSNAOC26 DSNAOG22 DSNAOC27 DSNAOC28 DSNAOG1S DSNAOG24 DSNAOG25 DSNAOG1U DSNAOG26 DSNAOG27 DSN@LIMS DSNAOC22 DSN@LIV1 DSN@LIQR DSNAOG28
Fix information
Fixed component name
DB2 ODBC/JDBC/S
Fixed component ID
5740XYR02
Applicable component levels
RC17 PSY UI78451
UP21/12/17 P F112
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C17"}]
Document Information
Modified date:
12 May 2022