A fix is available
APAR status
Closed as new function.
Error description
This PTF contains IBM DB2 Analytics Accelerator for z/OS Version 2 Refresh 6. IDAAV2R1/K
Local fix
n/a
Problem summary
USERS AFFECTED: All users of the IBM DB2 Analytics Accelerator for z/OS Version 2.1 PROBLEM DESCRIPTION: This PTF contains IBM DB2 Analytics Accelerator for z/OS Version 2 Refresh 6. Stored Procedures 20130610-1548 Server 20130613-1150 IDAAV2R1/K RECOMMENDATION: Before installing this PTF, make sure that all prerequisites are installed on your target system. For information, see: http://www.ibm.com/support/ docview.wss?uid=swg27022331 This PTF contains: Server version: 2.1.5 (build: 20130613-1150) Stored procedure build: 20130610-1548 ATTENTION: Prerequisite for activating this PTF: 1. The IBM DB2 Analytics Accelerator Studio version 3.1.2 was installed 2. Netezza: 6.0.8-0.F-1.P-8 was installed on the accelerator 3. DB2 PTFs must be installed: See the prerequisites site: http://www.ibm.com/support/ docview.wss?uid=swg27022331 or search for PTFs with the keyword IDAAV2R1/K ================================================================ # IBM DB2B. Analytics Accelerator for z/OS # # Closing Information for Version 2.1.0 PTF-6 # ================================================================ This PTF contains the following fixes: 1. Installation / Configuration console 1 Incremental update function is not available in the configuration console after migrating from V2.1 to V3.1 2. Maintenance and problem determination 1 DSNX881l message does not include information about the IDAA Accelerator 2 The organizing/distribution keys of a table cannot be changed 3. Data Load 1 Problem with loading tables returns wrong AQT10003I error message 2 SYSPROC.ACCEL_LOAD_TABLES returns error message: AQT10050I 3 SYSPROC.ACCEL_LOAD_TABLES returns error message: AQT10205I 4. Miscellaneous 1 A query using the LOCATE function might return an incorrect result 2 A query using alias table expressions where a column name is the same as a Standard SQL keyword returns an error message saying that an invalid object name is used 3 Unexpected Hardware events after pairing 4 Hardware event message DSNX881I is limited to maximum 256 characters 5 Client accounting string is truncated 6 Explain fails with ERROR: Bad timestamp external representation 7 DB2 time and Accelerator time differ 8 Saving trace is not possible 9 Query fails with "ERROR: Bad numeric input format 'U ' Details for each fix are described below: ############################################## ## 1. Installation / Configuration console ## ############################################## ================================================================ 1.1 Incremental update function is not available in the configuration console after migrating from V2.1 to V3.1 ================================================================ PROBLEM DESCRIPTION: Configuration options for the incremental update function are not displayed on the console. Although transfer and activation of the Access Server completes successfully, the configuration options for the incremental update function are not displayed on the IBM DB2 Analytics Accelerator Console. The error was caused by missing mappings of host names to IP addresses. Problem conclusion: The installation verification script now detects and reports the missing mappings. ############################################## ## 2. Maintenance and problem determination ## ############################################## ================================================================ 2.1 DSNX881l message does not include information about the IDAA accelerator ================================================================ PROBLEM DESCRIPTION: DSNX881l message does not include information about the IDAA appliance, only about the internal host where the problem was encountered. Fix in the DSNX881l message structure to include the name and the Wall IP of the accelerator. Problem conclusion: Identifying the source of hardware problems in scenarios with multiple IDAA appliances should become much easier.B ================================================================ 2.2 The organizing/distribution keys of a table cannot be changed ================================================================ PROBLEM DESCRIPTION: Alter key fails with AQT10050I, error contains the following diagnostic text: SQLSTATE: HY000 SQLCODE: 46' ERROR:B Transaction rolled back due to restart or failover' in some situations Problem conclusion: Code was fixed to allow changing the organizing/distribution keys of a table in all situations ############################################## ## 3. Data Load ## ############################################## ================================================================ 3.1 Problem with loading tables returns wrong AQT10003I error message ================================================================ PROBLEM DESCRIPTION: Internal error during load returned wrong AQT10003I error message. Important details about root cause of error were not returned. Problem conclusion: Error handling is fixed to return correct AQT10206I error message with correct diagnostic info. ================================================================ 3.2 SYSPROC.ACCEL_LOAD_TABLES returns error message: AQT10050I ================================================================ PROBLEM DESCRIPTION: SYSPROC.ACCEL_LOAD_TABLES returns the following error: AQT10050I - An internal error occurred on the '<accelerator-name>' accelerator: An assertion 'numBytesRead == availableReadSpace' failed. Problem could occur if the table that should be loaded contained BLOB, CLOB, DBCLOB, and XML columns. Problem conclusion: Problem is fixed. ================================================================ 3.3 SYSPROC.ACCEL_LOAD_TABLES returns error message: AQT10205I ================================================================ PROBLEM DESCRIPTION: Loads might fail with error AQT10205I which contains the following diagnostic text: "SQLSTATE: HY000 SQLCODE: 46 'ERROR: invalid directory for nzlog file: No such file or directory'" when the IDAA Stored Procedure version is 2 and IDAA Server version is 3 or 4. Problem conclusion: This fix is for migration scenarios ############################################## ## 4. Miscellaneous ## ############################################## ================================================================ 4.1 A query using the LOCATE function might return an incorrect result ================================================================ PROBLEM DESCRIPTION: The LOCATE function does not return a correct result if the first argument of the function is set by using the SUBSTR function. Problem conclusion: The query rewrite engine was adjusted, so that such queries now return the correct result. (Keywords: DB2, IDAA, LOCATE, SUBSTR ================================================================ 4.2 A query using alias table expressions where a column name is the same as a Standard SQL keyword returns an error message saying that an invalid object name is used ================================================================ PROBLEM DESCRIPTION: A query using alias table expressions where a column name is the same as a Standard SQL keyword returns error message DSNT408I SQLCODE = -904, SQLSTATE = 57011, RESOURCE NOT AVAILABLE OR OPERATOR INTERVENTION FROM IBM DB2 ANALYTICS ACCELERATOR TOKENS 00001080 00E7000E HY000: ERROR: Invalid object name - <keyword> Problem conclusion: Code was fixed so that queries using alias table expressions where a column name is the same as a Standard SQL keyword are successful. Workaround: For temporary workaround do not use any STANDARD SQL keyword as a column name in alias table expression (Keywords: DB2, IDAA, QUERY, ALIAS ================================================================ 4.3 Unexpected Hardware events after pairing ================================================================ PROBLEM DESCRIPTION: The last 50 hardware events will be displayed on a newly paired subsystem, even if these events occured before the pairing Problem conclusion: Code was changed to only report events that occurred since the new subsystem was added to the accelerator. ================================================================ 4.4 Hardware event message DSNX881I is limited to maximum 256 characters ================================================================ PROBLEM DESCRIPTION: Hardware event messages DSNX881I are truncated, not providing the full message text. Problem conclusion: Larger messages are now split into several pieces and the entire message will be reconstructed on zOS. (Keywords: DB2, IDAA, DIAGNOSTICS ================================================================ 4.5 Client accounting string is truncated ================================================================ PROBLEM DESCRIPTION: The client accounting string is truncated in IDAA query history Problem conclusion: No truncation will occur anymore. (Keywords: DB2, IDAA, CLIENT ACCOUNT, STATISTICS ================================================================ 4.6 Explain fails with ERROR: Bad timestamp external representation ================================================================ PROBLEM DESCRIPTION: EXPLAIN fails for a query if it contains an expression similar to TIMESTAMP(TO_CHAR(CURRENT_TIMESTAMP, 'YYYY-MM-DD-HH24.MI.SS.US' Problem conclusion: This particular SQL statement is working correctly now. (Keywords: DB2, IDAA, EXPLAIN, TIMESTAMP ================================================================ 4.7 DB2 time and Accelerator time differ ================================================================ PROBLEM DESCRIPTION: System time was not always synchronized between DB2 and IDAA and different DB2 subsystems may get different results in queries involving CURRENT TIMESTAMP, CURRENT DATE, and CURRENT TIME special registers between queries running in DB2 vs. queries running in IDAA Problem conclusion: IDAA now uses UTC as system time. For queries, it sets the timezone specific for the requesting DB2 subsystem to guarantee the same results between DB2 and IDAA for queries involving the mentioned special registers. (Keywords: DB2, IDAA, TIME, DATE, DIFFERENT, UTC ================================================================ 4.8 Saving trace is not possible ================================================================ PROBLEM DESCRIPTION: Symptom (1 : Saving Trace is not possible but ends with DRDATCPIPException: A network connection is gone. Symptom (2 : Save trace ending with DSNX880I TD06 DSNX8EKG DDF CONNECT FAILED These problems occured sporadically during the collection of IDAA traces. Problem conclusion: The problem was fixed (Keywords: DB2, IDAA, TIME, DATE, DIFFERENT, UTC ================================================================ 4.9 Query fails with "ERROR: Bad numeric input format 'U ' ================================================================ PROBLEM DESCRIPTION: Internal query transformation resulted in wrong sequence of operations, thus affecting several types of queries which could return this error. Problem conclusion: Internal query transformation was fixed to avoid this problem.
Problem conclusion
Temporary fix
Comments
--
APAR Information
APAR number
PM76973
Reported component name
SMRT ANL OPT DB
Reported component ID
5697AQT00
Reported release
210
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-13
Closed date
2013-06-25
Last modified date
2013-07-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK95393
Modules/Macros
AQTENV AQTNOTE AQTSCALL AQTSCI01 AQTSCI02 AQTSJI00 AQTSJI01 AQTSJI02 AQTSJI03 AQTSSCHK AQTSSCPY AQTSXADD AQTSXALT AQTSXCN0 AQTSXCN1 AQTSXCN2 AQTSXCN3 AQTSXCN4 AQTSXIM0 AQTSXQHI AQTSXSD1 AQTSXTCO AQTSXTSL AQTSXTSU AQTSXTS0 AQTTIJSP AQT02AAC AQT02ACC AQT02ACT AQT02ALT AQT02AP1 AQT02AP2 AQT02ATB AQT02CAC AQT02CAT AQT02CDC AQT02CFG AQT02CON AQT02C10 AQT02DYN AQT02ENQ AQT02FGV AQT02FRF AQT02GQD AQT02GQR AQT02GTI AQT02LTB AQT02MFS AQT02PSD AQT02QIT AQT02RAC AQT02RTB AQT02STA AQT02TCO AQT02TRC AQT02UCR AQT02UNL AQT02USW AQT02ZPR
Fix information
Fixed component name
SMRT ANL OPT DB
Fixed component ID
5697AQT00
Applicable component levels
R210 PSY UK95393
UP13/06/28 P F306
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 July 2013