APAR status
Closed as program error.
Error description
When the session was aborted by "FORCE_DDL_EXEC" the jdbc program sometimes raises error "Invalid cursor received by sqlexec" in Non-ISTAR environment. The strange thing is the problem only happens in my stress test. I can not reproduce it when there is only one running program.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * FORCE_DDL users * **************************************************************** * PROBLEM DESCRIPTION: * * When executing cursory statement and ALTER FRAGMENT with * * enabled FORCE_DDL at the same time, ALTER can occasionally * * and incorrectly invalidate open cursor * **************************************************************** * RECOMMENDATION: * * Update to a patched version when available. * ****************************************************************
Problem conclusion
Keep the cursor valid if it was closed by FORCE_DDL. The fix is applicable to 11.50.xC7N132.
Temporary fix
Comments
APAR Information
APAR number
IC67705
Reported component name
IBM IDS ENTRP E
Reported component ID
5724L2304
Reported release
B15
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-07
Closed date
2011-01-20
Last modified date
2011-01-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
IBM IDS ENTRP E
Fixed component ID
5724L2304
Applicable component levels
RB15 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B15","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
20 January 2011