HOLDDATA FOR DB2 9.1 PUT Level ** Please read through all the holddata before acting on any of it. ** GENERAL

Transcription

1 HOLDDATA FOR DB2 9.1 PUT Level 0805 ** Please read through all the holddata before acting on any of it. ** GENERAL 1. Rebind all static DB2 application which match criteria. Member REBIND DSN910.SVSC.HOLDCNTL can be used to do that 2. The following PTFs require additional action: UK Run DSN910.SVSC.HOLDCNTL(D05TIJMS) to rebind packages UK Provides changes for the DB2 scheduler feature. If you have activated ADMIN Scheduler run job: DSN910.SVSC.HOLDCNTL(D05TIJSG) If you don't currently have the ADMIN schedule feature activated and want to, please execute DSN910.SVSC.HOLDCNTL(D#5TIJSG) ********************* HOLDDATA **************************************** SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 09, 2008 System: S0W1 Time: 13:04:11 ***************************************************************** * The following PTFs have HOLD Reason: ACTION * ***************************************************************** UK36794 Jul 09, :43 Jul 09, :56 UK36794 HDB HOLD(UK36794) SYS FMID(HDB9910) REASON(ACTION) DATE(08148) (After applying this PTF on DB2 V9.1 for z/os ============================================ This PTF supersedes PTF UK32047 that contains a wrong ++HOLD text. The following post-apply actions are required of all current V9 customers. If you have already applied UK32047 and have performed the action for it, you need to take the following post-apply action only: (0) Bind the scheduler packages as follows: (a) Make a work copy of your updated customized copy of job DSNTIJSG. (b) Remove all job steps except DSNTIAS. (c) In job step DSNTIAS, remove all CREATE statements and remove the BIND PACKAGE command for member DSNADMCD. (d) Run the modified job to bind the scheduler packages. (e) When finished, you can erase the work copy of the job. For data sharing, this action needs to be performed only once for the group. If you have not yet performed the post-apply actions for UK32047, you need to take the following post-apply actions for this PTF: (1) Update private copies of the installation CLIST This PTF modifies the DB2 installation CLIST members

2 DSNTINS1 and DSNTINS2 in the prefix.sdsnclst target library. After applying this PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of DSNTINS1 and DSNTINS2. You may also want to move them to the prefix.new.sdsnclst data set, where the CLISTs processed by job DSNTIJVC reside. (2) Update your customized copy of job DSNTIJSG (a) Edit your customized copy of DSNTIJSG (b) Add the following SQL statement under the SYSIN DD of job step DSNTICU. If DSNTICU is commented out then you should also comment out this statement: DROP PROCEDURE SYSPROC.ADMIN_TASK_ADD RESTRICT; (c) In job step DSNTIAS, make these changes to the CREATE statement for procedure SYSPROC.ADMIN_TASK_SCHEDULE: - Change the procedure name to SYSPROC.ADMIN_TASK_ADD - Change,IN TRIGGER_TASK_ID INTEGER to,in TRIGGER_TASK_NAME VARCHAR(128) - Change,OUT TASK_ID INTEGER to,inout TASK_NAME VARCHAR(128) (d) Also in job step DSNTIAS, make these changes to the CREATE statement for procedure SYSPROC.ADMIN_TASK_REMOVE - Change TASK_ID INTEGER to IN TASK_NAME VARCHAR(128) (e) Also in job step DSNTIAS, make these changes to the CREATE statement for function DSNADM.ADMIN_TASK_LIST: - Change,TRIGGER_TASK_ID INTEGER to,trigger_task_name VARCHAR(128) - Change,TASK_ID INTEGER to,task_name VARCHAR(128) (f) Also in job step DSNTIAS, make these changes to the CREATE statement for function DSNADM.ADMIN_TASK_STATUS: - Change TASK_ID INTEGER to TASK_NAME VARCHAR(128) - Add,SQLERRMC VARCHAR(70) between,sqlerrp VARCHAR(8) and,db2_ssid VARCHAR(4) (g) In job step DSNTIJG, change the GRANT EXECUTE statement on procedure SYSPROC.ADMIN_TASK_SCHEDULE to SYSPROC.ADMIN_TASK_ADD. If you do not already have the routines ADMIN_TASK_SCHEDULE, ADMIN_TASK_REMOVE, ADMIN_TASK_LIST and ADMIN_TASK_STATUS and the scheduler configured in your DB2 V9.1 for z/os, you can skip the following section. Otherwise, to activate the changes in this PTF you need to take the following additional actions: (3) Stop the scheduler for administrative tasks. (4) Replace the interface in DB2.

3 (5) Stop and restart db2. (6) Migrate the currently defined scheduler tasks. (7) Adapt the applications. Each of these actions is detailed below. Note that DB2 must be running. (3) If the scheduler is running, stop it first by executing following console command: modify dsnadmt,appl=shutdown where dsnadmt is the name of the scheduler. (4) Create, bind, and grant access to the stored procedures and functions for the administrative scheduler. For data sharing, this action needs to be performed only once for the group: (a) Make a work copy of your updated customized copy of job DSNTIJSG. (b) Uncomment step DSNTICU, remove all job steps except DSNTICU, DSNTIAS and DSNTIJG. (c) Remove all DROP statements from step DSNTICU except the following: DROP PROCEDURE SYSPROC.ADMIN_TASK_SCHEDULE RESTRICT; DROP PROCEDURE SYSPROC.ADMIN_TASK_ADD RESTRICT; DROP PROCEDURE SYSPROC.ADMIN_TASK_REMOVE RESTRICT; DROP SPECIFIC FUNCTION DSNADM.ADMIN_TASK_LIST RESTRICT; DROP SPECIFIC FUNCTION DSNADM.ADMIN_TASK_STATUS RESTRICT; (d) In job step DSNTIAS: - remove the BIND PACKAGE command for member DSNADMCD - remove all CREATE statements, except the following: CREATE PROCEDURE SYSPROC.ADMIN_TASK_ADD... CREATE PROCEDURE SYSPROC.ADMIN_TASK_REMOVE... CREATE FUNCTION DSNADM.ADMIN_TASK_LIST... CREATE FUNCTION DSNADM.ADMIN_TASK_STATUS... (e) Remove all GRANT statements from step DSNTIJG except the following: GRANT EXECUTE ON PROCEDURE SYSPROC.ADMIN_TASK_ADD TO PUBLIC; GRANT EXECUTE ON PROCEDURE SYSPROC.ADMIN_TASK_REMOVE TO PUBLIC; GRANT EXECUTE ON FUNCTION DSNADM.ADMIN_TASK_LIST TO PUBLIC; GRANT EXECUTE ON FUNCTION DSNADM.ADMIN_TASK_STATUS TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNADMTA TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNADMTR TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNADMTU TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNADMTL TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNADMTS TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNA6DB2 TO PUBLIC; GRANT EXECUTE ON PACKAGE DSNADM.DSNA6THP TO PUBLIC; You can of course replace keyword PUBLIC with a more restrictive set of grantees, as they are currently defined in DB2. (f) Locate the WLM ENVIRONMENT clause in each of the CREATE PROCEDURE and CREATE FUNCTION statements in job step DSNTIAS and change WLMENV6 to the WLM environment for running these routines, as they are currently defined in DB2. Make sure that in the WLM procedure used to start the address space where these stored procedures are running, all libraries in the STEPLIB DD concatenation are APF authorized. (g) Run the modified job to create the new objects, bind

4 the new packages, and grant access. (h) When finished, you can erase the work copy of the job. (5) Stop and start DB2. This action will also start the DB2 administrative task scheduler if zparm ADMTPROC specifies a valid, non-null setting. (6) No task migration is needed. The tasks that were present in the scheduler before installing this PTF are still available afterwards. You can list them using the table function ADMIN_TASK_LIST, a task with a previous TASK_ID of 1 is listed under the TASK_NAME of "TASK_ID_0001". If you want to change the name of the task you have to remove the task and add it again with another name. (7) Modify any application that calls one of the stored procedures or functions of the scheduler. The changes in the interface are explained elsewhere in this PTF.). UK33985 Jul 07, :23 Jul 09, :01 UK33985 HDB HOLD(UK33985) SYS FMID(HDB9910) REASON(ACTION) DATE(08055) (This PTF contains performance enhancement for several DB2-provided DatabaseMetaData stored procedures, which are used by the DB2 Universal JDBC Driver and by the CLI Driver that was delivered with DB2 for Linux, Unix and Windows, Version 8 or higher. If your site does not use the DB2 Universal JDBC Driver or the CLI Driver shipped with DB2 for Linux, Unix, and Windows, then these stored procedures are likely not used so the following instructions would be unnecessary. However if these stored procedures are used at your site and the following instructions are not followed, SQL errors may result, particularly SQLCODE -805 or SQLCODE After applying this PTF, the packages associated with these stored procedures must be bound from the updated DBRMs. There are two ways to do this: 1. Re-run the installation job for those stored procedures. That installation job is named DSNTIJMS and it resides in db2-prefix.sdsnsamp. The customization instructions are inside the job itself. While this option can be more convenient, it may perform additional activity that can impact concurrently-running applications. The customization instructions in that job indicate that if you are re-running the job, you should uncomment the first step, which pre-drops all the objects (procedures, temporary tables, indexes). If there are application using the procedures, or that have statements or packages that are dependent on the indexes, the applications or the installation job might be unable to complete normally. 2. Create and submit a job to just bind the affected packages. Following is the BIND command that should be used. Replace the DSN!!0 in the command with your

5 high-level dataset qualifier for the target DB2 subsystem: BIND PACKAGE(DSNASPCC) MEMBER(DSNACPR8) - ACTION(REPLACE) ISOLATION(UR) QUALIFIER(SYSIBM) - RELEASE(COMMIT) SQLERROR(CONTINUE) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') BIND PACKAGE(DSNASPCC) MEMBER(DSNACOL8) - ACTION(REPLACE) ISOLATION(UR) QUALIFIER(SYSIBM) - RELEASE(COMMIT) SQLERROR(CONTINUE) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') BIND PACKAGE(DSNASPCC) MEMBER(DSNATBP8) - ACTION(REPLACE) ISOLATION(UR) QUALIFIER(SYSIBM) - RELEASE(COMMIT) SQLERROR(CONTINUE) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') BIND PACKAGE(DSNASPCC) MEMBER(DSNATBL8) - ACTION(REPLACE) ISOLATION(UR) QUALIFIER(SYSIBM) - RELEASE(COMMIT) SQLERROR(CONTINUE) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') These packages were built using the VERSION option. This means that submitting these binds after this PTF was applied, but before DB2 or the WLM address space has been restarted will create the new version of the packages but will leave the old version, allowing the stored procedures to continue running with the old procedure load modules and packages until DB2 or the WLM address space is restarted.). UK36397 Jul 07, :23 Jul 09, :01 UK36397 HDB HOLD(UK36397) SYS FMID(HDB9910) REASON(ACTION) DATE(08133) (This PTF fixes the problem of incorrect SQLCODE-206 being issued during incremental rebind of a native SQL procedure when it contains a MERGE or SELECT from MERGE statement and the source table of the MERGE statement references a SQL variable. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure could be SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 09, 2008 System: S0W1 Time: 13:04:11 ***************************************************************** * The following PTFs have HOLD Reason: DB2BIND * ***************************************************************** UK36661 Jul 07, :23 Jul 09, :01 UK36661 HDB HOLD(UK36661) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08142) (See PK60939 APAR/PTF text in the PTF cover letter for

6 PK60939 corrects a problem of an inaccurate index+data access cost estimate, which sometimes leads DB2 to pick a non-optimal access path. UK36661 Jul 07, :23 Jul 09, :01 UK34428 HDB HOLD(UK34428) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08142) (See PK58321 APAR/PTF text in the PTF cover letter for PK58321 corrects a problem where a less efficient join sequence is chosen due to inner table index access cost underestimation. UK36597 Jul 07, :23 Jul 09, :01 UK36597 HDB9910 PK HOLD(UK36597) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (***Action for PK63976: See PK63976 APAR/PTF text in the PTF cover letter for PK63976 corrects a problem of SQLCODE -332 from CCSID 1200 to CCSID being issued from DSNXRIHB when a LIKE predicate is referenced using a graphic matching expression and a string host variable or parameter marker pattern. It also corrects a problem of SQLCODE -332 from CCSID 1208 to CCSID being issued from DSNXODTR when a SET CURRENT SQLID statement is used to set a string constant into special register CURRENT SQLID. To make this fix effective for a static application or package, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications or packages could be UK36597 Jul 07, :23 Jul 09, :01 UK34883 HDB HOLD(UK34883) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (See PK60518 APAR/PTF text in the PTF cover letter for

7 PK60518 fixes a problem when a query contains an XMLEXISTS predicate. UK36585 Jul 07, :23 Jul 09, :01 UK36579 HDB HOLD(UK36579) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (See PK64783 APAR/PTF text in the PTF cover letter for APAR PK64783 corrects a problem that can cause SQLCODE -904 issued for an update/delete/merge statement. UK36585 Jul 07, :23 Jul 09, :01 UK35148 HDB HOLD(UK35148) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (See PK62865 APAR/PTF text in the PTF cover letter for PK62865 corrects an incorrect output problem that may occur for queries with host variables or parameter markers on a partitioned table space. UK36585 Jul 07, :23 Jul 09, :01 UK36585 HDB9910 PK HOLD(UK36585) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (***Action for PK59680: See PK59680 APAR/PTF text in the PTF cover letter for PK59680 corrects a problem of ABEND0C4 RC11 in DSNXOPG2+100C or ABEND0C4 RC11 in DSNSVBK+1118 or ABEND0C4 RC10 in DSNISPBM+1258 that may occur for a query using page range access.

8 UK36583 Jul 07, :23 Jul 09, :01 UK36583 HDB9910 PK HOLD(UK36583) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (***Action for PK64651: See PK64651 APAR/PTF text in the PTF cover letter for PK64651 corrects an ABEND04E DSNXRTIM:P016 failure that occurs when inserting a NULL value for a DATE column into NOT NULL CHAR column. UK36583 Jul 07, :23 Jul 09, :01 UK36581 HDB9910 PK HOLD(UK36581) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08140) (***Action for PK61657: See PK61657 APAR/PTF text in the PTF cover letter for PK61657 corrects a problem that can occur when using the DB2 DECRYPT scalar functions that can result in an ABEND0C4 rc b at location DSNXGSFN +29FE or an incorrect result. UK36457 Jul 07, :23 Jul 09, :01 UK31355 HDB HOLD(UK31355) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08134) (This PTF is to be applied on the DB2 for z/os requester system for an error that is reported at a remote DB2 for z/os server system. See PK54896 APAR/PTF text for the specific server error information.). UK36412 Jul 07, :23 Jul 09, :01 UK36412 HDB9910

9 ++ HOLD(UK36412) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK63350 APAR/PTF text in the PTF cover letter for APAR PK63350 corrects a problem that can cause incorrect output for a query that has an IN-subquery in the subselect under an update statement. UK36410 Jul 07, :23 Jul 09, :01 UK36410 HDB HOLD(UK36410) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK62566 APAR/PTF text in the PTF cover letter for PK62566 corrects a possible query performance problem during bind for queries with the OPTIMIZE-FOR-N-ROWS or FETCH-FIRST-N-ROWS-ONLY clause. UK36391 Jul 07, :23 Jul 09, :01 UK35040 HDB HOLD(UK35040) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK62278 APAR/PTF text in the PTF cover letter for PK62278 corrects a possible problem during bind process for queries with omnifind functions where the link among the execution plans for each table may be broken. UK36391 Jul 07, :23 Jul 09, :01 UK34882 HDB9910 PK HOLD(UK34882) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (***Action for PK60758: See PK60758 APAR/PTF text in the PTF cover letter for

10 PK60758 corrects the cardinality estimate for queries with the FETCH FIRST n ROWS ONLY clause. UK36391 Jul 07, :23 Jul 09, :01 UK33088 HDB HOLD(UK33088) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK56423 APAR/PTF text in the PTF cover letter for PK56423 corrects a DB2 incorrect output problem that may occur for PREPARE statements with FETCH FIRST clause. UK36391 Jul 07, :23 Jul 09, :01 UK32176 HDB HOLD(UK32176) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK56283 APAR/PTF text in the PTF cover letter for PK56283 corrects a problem of incorrect output being returned for a query which contains UNION or UNION ALL, and at least one union leg contains join and a GROUP BY, and a join column happens to be one of the grouping columns. UK36391 Jul 07, :23 Jul 09, :01 UK31472 HDB HOLD(UK31472) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK55235 APAR/PTF text in the PTF cover letter for PK55235 corrects a problem where an extra sort is added although there exists an index which can support the ORDER BY ordering. The extra sort may cause SQL code -670 to be issued, or poor query performance can occur.

11 UK36391 Jul 07, :23 Jul 09, :01 UK30023 HDB HOLD(UK30023) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08133) (See PK52927 APAR/PTF text in the PTF cover letter for PK52927 corrects a problem that an extra (unnecessary) sort for ORDER BY is added to the access path of a query when the query exploits an index on expression. It also fixes a problem that blocks index on expression from doing index-only in some cases. UK36366 Jul 07, :23 Jul 09, :01 UK35088 HDB HOLD(UK35088) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08130) (See PK61338 APAR/PTF text in the PTF cover letter for PK61338 corrects an under-estimated filter factor for an IS NULL local predicate, which may result in a bad access path and poor query performance. UK36366 Jul 07, :23 Jul 09, :01 UK35391 HDB HOLD(UK35391) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08130) (See PK61255 APAR/PTF text in the PTF cover letter for PK61255 corrects a bug where valid histogram statistics should be used for query optimization but were mistakenly discarded. UK36365 Jul 07, :23 Jul 09, :01 UK36365 HDB9910 PK65245

12 ++ HOLD(UK36365) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08130) (***Action for PK65245: See PK65245 APAR/PTF text in the PTF cover letter for PK65245 corrects a problem of an incorrect output or SQLCODE -304 (reported by SQLCODE -444) when a Unicode-bound application (e.g. using BIND option ENCODING(UNICODE)) calls an EBCDIC stored procedure and the stored procedure returns a datetime value as output under a system that is in V8 Enabling New Function Mode or higher. To make this fix effective for a static application or a package that contains the above CALL statement, the application and the package must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications or packages could be UK36365 Jul 07, :23 Jul 09, :01 UK35290 HDB9910 PK HOLD(UK35290) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08130) (***Action for PK63181: See PK63181 APAR/PTF text in the PTF cover letter for PK63181 corrects a problem of incorrect sqlcode -404 issued when NULL keyword is specified in THEN clause and an empty string is specified in THEN clause or ELSE clause in CASE expression. UK36329 Jul 07, :23 Jul 09, :01 UK36329 HDB9910 PK HOLD(UK36329) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08129) (***Action for PK64572: See PK64572 APAR/PTF text in the PTF cover letter for PK64572 corrects a problem of ABEND0C4 in DSNXRBND + 'D3A0'X.

13 UK36235 Jul 07, :23 Jul 09, :01 UK36235 HDB9910 PK HOLD(UK36235) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08127) (***Action for PK63845: See PK63845 APAR/PTF text in the PTF cover letter for PK63845 corrects a problem of underestimated cost of a table space scan for a small table which only has several data pages. The underestimated cost can lead to slow query performance. SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 09, 2008 System: S0W1 Time: 13:04:11 ***************************************************************** * The following PTFs have HOLD Reason: DOC * ***************************************************************** UK36464 Jul 07, :23 Jul 09, :01 UK36464 HDB HOLD(UK36464) SYS FMID(HDB9910) REASON(DOC) DATE(08134) (APAR PK63645 adds support for the WITH common-table-expression in the SELECT INTO statement. The SQL Reference will be updated as follows: Add the WITH common-table-expression clause to the syntax diagram for the SELECT INTO statement in Chapter 5 of the SQL Reference. >> select-clause--> , v '-WITH---common-table-expression-+-'.----, v >---INTO ---host-variable-+--from-clause > > >< For a description of the WITH common-table-expression clause, see the topic 'select-statement' in Chapter 4 of the SQL Reference.).