A fix is available
APAR status
Closed as program error.
Error description
SET CURRENT SQLID statement missing when RUN SQLID is blank using DB2 Object Comparison Tool for z/OS 10.1.0
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Object Comparison Tool for * * z/OS who add new objects from source to the * * target on DB2 9 New Function Mode (NFM) * * and above. * **************************************************************** * PROBLEM DESCRIPTION: When performing a DDL to Catalog * * compare the SET CURRENT SQLID * * statement is missing for added objects * * when the 'RUN SQLID' field is blank * * on panel GOC5 'Generate Compare Jobs'. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the objects are on source only, they will be added to the target after the compare. DB2 Object Compare will compare the OWNER and CREATOR value of an object, and if both have the same value, the 'SET CURRENT SQLID' statement is not generated.
Problem conclusion
Objects which are on source only will be added to the target after the compare. The newly added objects will have the same value for the OWNER and CREATOR. For an object that is added to the target after a compare, DB2 Object Compare will generate a 'SET CURRENT SQLID' statement before the CREATE statement for the added object if the SQLID is not the same as the SQLID used for the previous object. Based on the type of object being added, DB2 Object Compare will use the value of the OWNER as the CURRENT SQLID. On DB2 9 and above, when the source table, view, alias or index is created with a qualifier, executing the job to create the object on target may encounter SQLCODEN551 / SQLCODE=-551 error because DB2 uses the qualifier as the owner of the object, which may not have the appropriate privilege to create the object on target. To resolve this problem, please change the qualifier to an authorized SQLID or specify an authorized RUN SQLID on panel GOC5. SQLCODE=-551 auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT object-name According to DB2 SQL Reference Version 9 and Version 10 for DB2 9 New Function Mode (NFM), DB2 10 Conversion Mode (CM), and DB2 10 New Function Mode (NFM), the length of SQLID should not be greater than 8. If the length of the OWNER value is greater than 8, DB2 Object Compare will not generate a 'SET CURRENT SQLID' statement, nor issue any informational/warning/ error message in this case. If the length of the OWNER value is not greater than 8, DB2 Object Compare will generate a SQLID based on the OWNER value. This APAR does not address cases where objects are unqualified and will have different values for OWNER and CREATOR - see APAR PM67200 for the solution for that scenario.
Temporary fix
Comments
APAR Information
APAR number
PM59036
Reported component name
DB2 OBJECT COMP
Reported component ID
5697G6400
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-24
Closed date
2012-06-20
Last modified date
2012-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADB2CMR
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
RA10 PSY UK79702
UP12/06/27 P F206
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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 July 2012