A fix is available
APAR status
Closed as program error.
Error description
Possible CKZ24621E SQL EXECUTE FAILED, SQLCODE: -904 SQLSTATE: 57011 and reason code 00D70001 in DB2SQL command on DB2 V10. When changing a STOGROUP name and there is a user defined index on DB2 catalog tables SYSIBM.SYSTABLEPART, SYSIBM.SYSINDEXPART, or SYSIBM.SYSDATABASE, if the user defined index needs to extend while the STOGROUP name is being changed by DB2SQL the extend can fail with reason code 00D70001 and give sqlcode -904. It is also possible when rerunning DB2SQL after the -904 error to get CKZ24621E SQL EXEC IMM FAILED, SQLCODE: -601 SQLSTATE: 42710. Also corrected a problem when there are multiple versions of a native SQL stored procedure. This caused: CKZ24606E ERROR CALLING CKZ01VV1 CKZ00246_WLMENV FUNCTION: PUT R15=0004 R0=00000000 LOC=GWED1
Local fix
Stop the target DB2 Make the user defined index data set bigger Start the target DB2 in SPECIAL MODE Delete the STOGROUPs created by DB2SQL Rerun DB2SQL
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Cloning Tool. * **************************************************************** * PROBLEM DESCRIPTION: Possible CKZ24621E SQL EXECUTE FAILED, * * SQLCODE: -904 SQLSTATE: 57011 and * * reason code 00D70001 in DB2SQL command * * on DB2 V10. When changing a STOGROUP * * name and there is a user defined index * * on DB2 catalog tables * * SYSIBM.SYSTABLEPART, * * SYSIBM.SYSINDEXPART, * * or SYSIBM.SYSDATABASE, if the user * * defined index needs to extend while the * * STOGROUP name is being changed by * * DB2SQL the extend can fail with reason * * code 00D70001 and give sqlcode -904. * * It is also possible when rerunning * * DB2SQL after the -904 error to get * * CKZ24621E SQL EXEC IMM FAILED, SQLCODE: * * -601 SQLSTATE: 42710. Also corrected a * * problem when there are multiple * * versions of a native SQL stored * * procedure. This caused: * * CKZ24606E ERROR CALLING CKZ01VV1 * * CKZ00246_WLMENV FUNCTION: PUT * * R15=0004 R0=00000000 LOC=GWED1 * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PI08649
Reported component name
DB2 CLONING TOO
Reported component ID
5655N1000
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-12-23
Closed date
2014-02-10
Last modified date
2016-09-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
CKZ00246
Fix information
Fixed component name
DB2 CLONING TOO
Fixed component ID
5655N1000
Applicable component levels
R310 PSY UI14980
UP14/02/13 P F402
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
16 September 2016