IBM Support

V4.1 PTF-4 Release Notes

Release Notes


Abstract

This document describes enhancements and fixes in IBM DB2 Analytics Accelerator for z/OS Version 4.1, PTF-4

Content


Prerequisites

IBM DB2 Analytics Accelerator for z/OS Version 4.1 Refresh 4 has


removed SMP/E prerequisites of the base PTF on PTFs containing
Access Server, Replication Engine and NPS. The installation of
the following PTFs containing the latest levels of Access Server
and Replication Engine is not enforced by SMP/E means but must be
performed in addition to the PTFs of Refresh 4:






UI17101Replication Engine Base
UI20188Replication Engine Update
UI20187Access Server Update

================================================================

1. What's New

================================================================


1.1 Call Home                                                  v
================================================================
****************************************************************
* USERS AFFECTED: Users of IBM DB2 Analytics Accelerator       *
*                 interested in a more transparent handling of *
*                 hardware and software errors                 *
****************************************************************
* FEATURE DESCRIPTION: This function automatically opens       *
* PMRs in the event of failed hardware or other critical       *
* errors in case it is configured and activated,               *
* redundantizing the need to manually open PMRs for those      *
* problems.                                                    *
****************************************************************
Additional information: This function must be configured and  
enabled from the IBM DB2 Analytics Accelerator Console and can
also be disabled from there. Before the function can be
configured and enabled, you must set up an SMTP server on
System z and enable the z/OS FTP server and the FTP-to-JES  
interface. See "Using the call-home function" in the
"Installation Guide", SH12-7038-03.      

================================================================
1.2 Encryption of data at rest                                 v
================================================================
****************************************************************
* USERS AFFECTED: Users of the IBM PureData System for         *
*                 Analytics N300x                              *
****************************************************************
* FEATURE DESCRIPTION: The IBM PureData System for Analytics   *
* N300x is delivered with self-encrypting disks, unless this   *
* is prohibited by export regulations. That is, all data on    *
* the hard disks of the system is automatically encrypted. The *
* encryption keys are stored in a keystore. You can change     *
* the keystore password and the encryption keys from the       *
* IBM DB2 Analytics Accelerator Console. Prerequisites:        *
* - IBM N300x hardware                                         *
* - IBM Netezza 7.2.0.0 P1                                     *
* - an IBM support engineer must set up the initial keystore   *
*   password                                                   *
****************************************************************

================================================================
1.3 Support of new hardware N300x                              v
================================================================
****************************************************************
* USERS AFFECTED: Users of the IBM PureData System for         *
*                 Analytics N300x                              *
****************************************************************
* FEATURE DESCRIPTION: The IBM PureData System for Analytics   *
* N300x is supported with the provided NPS 7.2.0.0 P1          *
****************************************************************

================================================================

2. Solved Problems

================================================================


2.1 Missing ACCESS DATABASE authorization is handled           v
    incorrectly                                                v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: If the user calling the stored          *
* procedures SYSPROC.ACCEL_LOAD_TABLES,                        *
* SYSPROC.ACCEL_ARCHIVE_TABLES, SYSPROC.ACCEL_RESTORE_TABLES   *
* or SYSPROC.ACCEL_GET_TABLE_DETAILS does not have the         *
* authorization to call the ACCESS DATABASE command,           *
* the missing authorization is silently ignored and            *
* processing continues.                                        *
****************************************************************
Problem conclusion: The program logic has been changed. In      
case the caller of the stored procedure is not authorized      
to call the ACCESS DATABASE command, an error message
is shown by default. To guarantee compatibility,  
an environment variable called              
AQT_RTS_EXTERNALIZATION_AUTH_FAILURE has been introduced. The
variable can be set to the values
WARNING or IGNORE. In both cases, the stored procedure  
continues processing without accurate real-time statistics.    
Set this variable only after you have familiarized yourself with
the possible side-effects. See the description of the error
messages AQT10413I and AQT10414I in the
"Stored Procedures Reference", SH12-7039-03.                                                

================================================================
2.2 Transfer of large files with stored procedure              v
    SYSPROC.ACCEL_UPDATE_SOFTWARE fails                        v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Acclerator    *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: Transfer of large files (>2GB) with the *
* SYSPROC.ACCEL_UPDATE_SOFTWARE fails with the following error *
* message: AQT10050I - An internal error occurred on the       *
* 'VM509' accelerator: Parsing of an XML document failed in    *
* line 1 and column 214 with error 'Datatype error:            *
* Type:InvalidDatatypeValueException, Message:Value            *
* '18446744073709551615' must be less than or equal to         *
* MaxInclusive '4294967295' . '. The XML document being        *
* processed is: <?xml version='1.0' encoding='UTF-8'           *
* ?><dwaup:softwareUploadInternalCommand                       *
* xmlns:dwaup='http://www.ibm.com/xmlns/prod/dwa/2011'         *
* version='1.0'><upload name='test.tar.gz'                     *
* size='18446744073709551615'                                  *
* type='HOST'/></dwaup:softwareUploadInternalCommand>          *
****************************************************************
Problem conclusion: The problem has been fixed.              

================================================================
2.3 Identifiers that start with an                             v
    underscore lead to SQL error                               v
================================================================
****************************************************************
* USERS AFFECTED: Customers who use IBM DB2 Analytics          *
*                 Accelerator for z/OS Version 4.1 in          *
*                 conjunction with SPSS                        *  
****************************************************************
* PROBLEM DESCRIPTION: An accelerated query fails with SQL     *
* error: SQLCODE = -904, SQLSTATE = 57011 with the following   *
* message text: ERROR: Invalid attribute '__Count' where       *
* 'Count' is a column name. The leading underscore in the      *
* column alias causes the problems.                            *
****************************************************************
Problem summary: This error occurred if users selected the      
'Reformat SQL' option in the SPSS Modeler client.                

Problem conclusion: The problem has been fixed. IBM DB2
Analytics Accelerator automatically replaces invalid
characters in delimited identifiers in the SQL statement text.

================================================================
2.4 An internal error occurred during: 'Save Trace...'.        v
================================================================
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator Studio for *
*                 z/OS Version 4.1 users                       *
****************************************************************
* PROBLEM DESCRIPTION: The Save Trace function returns the     *
* following error:                                             *
* An internal error occurred during: 'Save Trace...'. The      *
* Eclipse Error Log contains an entry with this content:       *
* java.lang.NullPointerException at                            *
* java.util.regex.Matcher.getTextLength(Matcher.java:1245) at  *
* java.util.regex.Matcher.reset(Matcher.java:319) at           *
* java.util.regex.Matcher.<init>(Matcher.java:239) at          *
* java.util.regex.Pattern.matcher(Pattern.java:1099) at        *
* com.ibm.datatools.aqt.dbsupport.trace.SpTraceFilenameFilter. *
* <init>(SpTraceFilenameFilter.java:63) at                     *
* com.ibm.datatools.aqt.dse.trace.SaveTraceJob.                *
* createZipFile(SaveTraceJob.java:1033) at                     *
* com.ibm.datatools.aqt.dse.trace.SaveTraceJob.                *
* run(SaveTraceJob.java:406) at                                *
* org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)    *
****************************************************************
Problem summary: The problem occurred when Save Trace was
selected from the context menu of the Accelerators folder in the            
Administration Explorer if IBM DB2 Analytics Accelerator Studio.                                    

Problem conclusion: The problem has been fixed.              

================================================================
2.5 IBM DB2 Analytics Accelerator shuts down under very high   v
    system load                                                v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1 PTF-3                   *
****************************************************************
* PROBLEM DESCRIPTION: If many concurrent jobs (queries,       *
* load operations, and so on) are running on a single          *
* accelerator, the server might shut down unexpectedly.        *
* As a result, all running jobs fail.                          *
****************************************************************
Problem summary: Under a very high workload, the accelerator
shuts down and all running jobs end before they can
be completed.                

Problem conclusion: The problem has been fixed. If too many    
jobs are sent to an accelerator, some of these can be rejected.    

================================================================
2.6 Fluctuating numbers of result rows and result              v
    sizes shown for running queries in the query history       v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: Frequently refreshing the query history *
* might lead to a display of increasing as well as decreasing  *
* numbers of result rows and result sizes (bytes) for          *
* currently running queries                                    *
****************************************************************
Problem summary: For running queries, the numbers of result    
rows and result sizes (bytes) in the query history could
decrease.

Problem conclusion: The problem has been fixed.              

================================================================
2.7 Incremental updates stop after host failover               v
================================================================
****************************************************************
* USERS AFFECTED: Users of the incremental update function in  *
*                 IBM DB2 Analytics Accelerator for            *
*                 z/OS Version 4.1                             *
****************************************************************
* PROBLEM DESCRIPTION: Incremental updates stop after failover *
*                      due to time synchronization issues.     *
****************************************************************
Problem summary: Host failovers occur after hardware    
errors or severe software errors on the active host. If the
time difference between the system clocks of the active and the
passive host exceeds 15 minutes, incremental update operations
stop. Such time differences can develop because the system
clock of the active host is always synchronized with the system
time of one of the connected DB2 subsystems or members of a
connected data sharing group. The clock of the passive host,
however, is not synchronized.                                                

Problem conclusion: The problem has been fixed. Now the system
clocks of both hosts are synchronized.


================================================================
2.8 Problems when connecting to the IBM DB2 Analytics          v
Accelerator Console                                            v
================================================================
****************************************************************
* USERS AFFECTED: Users of the IBM DB2 Analytics Accelerator   *
*                 Console delivered with product version 4.1   *
*                 PTF UI22851                                  *
****************************************************************
* PROBLEM DESCRIPTION: The administrator cannot connect to the *
* IBM DB2 Analytics Accelerator Console.                       *
* The tso telnet command does not run to completion.           *
****************************************************************

Problem conclusion: The problem has been fixed.

================================================================
2.9 Time value 23:59:59.999999 is returned as 24:00:00         v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: Queries that access timestamp columns   *
* return 24:00:00.000000 as the time portion of a timestamp in *
* the results when the actual value is 23:59:59.999999.        *
****************************************************************
Problem summary: IBM DB2 Analytics Accelerator for z/OS Version
4.1 supports 24:00:00.00000 values for the time portion of a
timestamp. In previous versions, 24:00:00.00000 values were
converted to 23:59:59.999999 using an environment variable. In
version 4.1, 23:59:59.999999 values are automatically converted
to 24:00:00.00000. In certain scenarios the behavior in version
3.1., that is, a conversion of 24:00:00.00000 values to
23:59:59.999999 during a table load, is preferred over the
automatic conversion in version 4.1.

Problem conclusion: The problem has been fixed. An option has
been added to the IBM DB2 Analytics Accelerator Console that
activates the load-time conversion from 24:00:00.000000 to
23:59:59.999999.

================================================================
2.10 Incorrect load recommendation for partitioned-by-growth   v
     tables                                                    v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_GET_TABLES_DETAILS    *
* stored procedure returns a recommendation to fully reload a  *
* partitioned-by-growth table even if the table has just been  *
* reloaded.                                                    *
****************************************************************
Problem summary: IBM DB2 Analytics Accelerator does not always
properly detect those table partitions in a            
partition-by-growth table space that have truly changed in DB2
and therefore require a reload.

Problem conclusion: The problem has been fixed.

                                               


================================================================

3. Known issues

================================================================


****************************************************************
* Users affected: All product users running NPS version        *
*                 7.2.0.0 on the accelerator.                  *
****************************************************************
* Short summary: Disabling the call-home function always       *
*                displays a message that indicates an error    *
*                even if the operation was successful.         *
****************************************************************
* Details: If the call-home function is disabled from the      *
*          IBM DB2 Analytics Accelerator Console, the          *
*          following message is displayed even if the          *
*          operation was successful:                           *
*                                                              *
*             "Press 'y' to disable call home: y               *
*             Disabling call home failed. Contact IBM Support."*
*                                                              *
*          You can check that the operation was actually       *
*          successful. Use option (6) on the console:          *
*                                                              *
*          (6) - Display settings                              *
*                                                              *
*          Look for the following entry:                       *
*              Call Home Status                  : Disabled    *
****************************************************************



IBM DB2 Analytics Accelerator for z/OS Version 4.1 NPS Refresh 7.2.0.2

contains fixes for the following issues:



================================================================
Solved Problems                                                
================================================================
1. SQL error -901 Password authentication failed for user      v
   'DWA_USER_*subsystem*                                       v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0             *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: Intermittently, the password            *
*                      authentication fails for queries and    *
*                      load operations with SQL error -901.    *
****************************************************************
Problem conclusion: The problem has been fixed.


================================================================
2. Different query results in connection with CAST             v
   expressions and multiple encoding                           v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0             *
****************************************************************
* PROBLEM DESCRIPTION: DB2 for z/OS and the accelerator return *
*                      different results if a query contains a *
*                      CAST expression that casts a numeric    *
*                      data type to the CHAR data type and if  *
*                      multiple encoding is enabled (the       *
*                      AQT_ENABLE_MULTIPLE_ENCODING environ-   *
*                      ment variable has been set to TRUE)     *
****************************************************************
Problem conclusion: The problem has been fixed.


================================================================
3. Query fails with SQLSTATE: HY000 SQLCODE: 46 'ERROR:        v
   Invalid UTF-8 sequence - bad continuation byte (0xCD) at    v
   byte offset 1'.                                             v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0             *           ****************************************************************
* PROBLEM DESCRIPTION: Some queries fail with message "ODBC    *
*                      operation SQLPrepare failed with code   *
*                      -1 when Preparing statement SELECT      *
*                      sessionid, relname FROM _t_pg_locks     *
*                      WHERE sessionid <> current_sid AND      *
*                      dbname =  'DWA_LOCATION_UT_005056BA0139 *
*                      _DWA_10759' : SQLSTATE: HY000 SQLCODE:  *
*                      46 'ERROR:  Invalid UTF-8 sequence -    *
*                      bad continuation byte (0xCD) at byte    *
*                      offset 1'."                             *
****************************************************************
Problem conclusion: The problem has been fixed.


================================================================
4. Performance degradation for queries containing "first fetch v
   n rows" expressions in connection with NPS 7.2.0.0          v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0             *
****************************************************************
* PROBLEM DESCRIPTION: Queries containing a "first fetch n     *    
*                      rows" expression run slower on systems  *
*                      with NPS 7.2.0.0 than on systems with   *
*                      NPS 7.1.0.2                             *
****************************************************************
Problem conclusion: The problem has been fixed.


================================================================
5. The call-home function cannot be disabled on systems with   v
   certain serial numbers                                      v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0             *
****************************************************************
* PROBLEM DESCRIPTION: The call-home function cannot be        *
*                      disabled from the IBM DB2 Analytics     *
*                      Accelerator Console if the serial       *
*                      number of the system starts with 78.    *
****************************************************************
Problem conclusion: The problem has been fixed.

IBM DB2 Analytics Accelerator for z/OS Version 4.1 NPS Refresh 7.2.0.3

contains fixes for the following issues:



================================================================
Solved Problems                                                
================================================================
1. SQL error -904: Bad timestamp external representation       v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.0.4.3, 7.1.0.2,   *
*                 7.2.0.0, 7.2.0.2                             *
****************************************************************
* PROBLEM DESCRIPTION: Query fails with SQL code -904 and the  *
*                      message "Bad timestamp external repre-  *
*                      sentationAQT" is displayed if the query *
*                      contains an expression like:            *
*                      "select TO_CHAR(CAST(<some value> AS    *
*                       TIMESTAMP),'SSSS')"                    *
****************************************************************
Problem conclusion: The problem has been fixed.

================================================================
2. Load job fails with ERROR:  pg_atoi: invalid input syntax   v
   for integer                                                 v
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 Version 4.1 installations running Netezza    *
*                 Performance Server (NPS) 7.2.0.0 or 7.2.0.2  *
****************************************************************
* PROBLEM DESCRIPTION: The load job fails during the execution *
*                      of an insert statement. The error       *
*                      message reads:                          *
*                        "SQLSTATE: HY000 SQLCODE: 46 'ERROR:  *
*                      pg_atoi: invalid input syntax for       *
*                      integer:"                               *
****************************************************************
Problem conclusion: The problem has been fixed.

[{"Product":{"code":"SS4LQ8","label":"Db2 Analytics Accelerator for z\/OS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"4.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 August 2018

UID

swg27043885

Page Feedback