IBM Support

V4.1 PTF-6 Release Notes

Release notes


Abstract

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

Content




================================================================
1. What's New                                                  v
================================================================
1.1 Improved throughput of incremental update related          v
    management and monitoring operations                       v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* FEATURE DESCRIPTION: Adding or removing tables from an       *
* accelerator and the monitoring of incremental update         *
* operations do not block each other anymore. The resulting    *
* delays led to outdated monitoring information when the       *
* adding or removal of tables took very long.                  *
****************************************************************
Additional information: This feature is readily available. You
need not install or configure it.                            

================================================================
1.2 Regularly consistency checks and enforcement of            v
    incremental update meta data                               v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* FEATURE DESCRIPTION: If parts of the incremental update      *
* component are temporarily unavailable, metadata might remain *
* when disabling incremental updates that is is not needed     *
* anymore. This metadata might inhibit future enabling of      *
* incremental updates (for example after a schema change) The  *
* new feature ensures that all incremental-update-related      *
* metadata is checked for consistency regularly and adjusted   *
* accordingly.                                                 *
****************************************************************
Additional information: The problem has been solved.          

================================================================
1.3 Save Trace - nzlogcollector                                v
================================================================
****************************************************************
* USERS AFFECTED: Product users with hardware or software      *
*                 problems who are in need of diagnostic       *
*                 information                                  *
****************************************************************
* FEATURE DESCRIPTION: The 'Save Trace' window in DB2          *
* Analytics Accelerator Studio and the underlying stored       *
* SYSPROC.ACCEL_CONTROL_ACCELERATOR stored procedure call the  *
* Netezza support tool nzlogcollector to collect additional    *
* diagnostic information. To provide service for an            *
* accelerator hardware or software problem, IBM service        *
* engineers need a lot of diagnostic information (traces) from *
* the customer system. In the past, this often required remote *
* access to the customer system over a Web-ex or Assist-on     *
* site screen-sharing session that blocked the customer's      *
* desktop while the service engineer was analysing the system. *
* Now customers can collect most of that information by        *
* themselves if they use the 'Save trace' function in IBM DB2  *
* Analytics Accelerator Studio or the corresponding stored     *
* procedure. A remote screen-sharing session is hardly         *
* required anymore.                                            *
****************************************************************
Additional information: The new function shows up in the 'Save
Trace' window of DB2 Analytics Accelerator Studio if both the
accelerator server and stored procedures are at level 4 PTF6  
(4.1.6) or higher and the version of the Netezza Performance  
Server (NPS) is 7.2.0.5 or higher. The 'Save Trace' window has
a new checkbox 'nzlogcollector'. If that checkbox is selected,
you can specify the details of the trace collection on the    
next page (click the 'Next' button) in the 'Save Trace'      
window. The details that you have to enter in the input      
fields, for example 'rack1.host' in the 'host' field, will be
provided by IBM support. The new trace content can also be    
collected by calling the SYSPROC.ACCEL_CONTROL_ACCELERATOR    
stored procedure directly and by embedding appropriate        
elements inside the getTraceData element of the command      
parameter, that is:
<?xml version='1.0' encoding='UTF-8'?>    
   <dwa:controlCommand
    xmlns:dwa='http://www.ibm.com/xmlns/prod/dwa/2011'            
    version='1.3'>
   <getTraceData keepConfiguration='true'>        
   <content component='spu' spec='<spuNOList>'>
      NZLOGCOLLECTOR
   </content>
   <content component='spa' spec='<spaNoList>'>
      NZLOGCOLLECTOR
   </content>  
   <content component='disk' spec='<diskIdList>'>
      NZLOGCOLLECTOR
   </content>
   <content component='host' spec='<hostnamelist>'>
      NZLOGCOLLECTOR
   </content>
   <content component='sasphy' spec='<spaNolist>'>
      NZLOGCOLLECTOR
   </content>
   <content component='plan' spec='<planList>'>
      NZLOGCOLLECTOR
   </content>
   <content component='database' spec='<dblist>'>
      NZLOGCOLLECTOR
   </content>
   <content component='network'>
      NZLOGCOLLECTOR
   </content>
   <content component='cluster'>
      NZLOGCOLLECTOR
   </content>
   <content symptom='<symptomspec>' >
      NZLOGCOLLECTOR
   </content>
   <content days='<N>'>
      NZLOGCOLLECTOR
   </content>
   <content from='<dateTime>'>
      NZLOGCOLLECTOR
   </content>
   <content to='<dateTime>'>
      NZLOGCOLLECTOR
   </content>
   </getTraceData>      
   </dwa:controlCommand>
For example, to retrieve the default    
nzlogcollector content you can use the following input        
document for the SYSPROC.ACCEL_CONTROL_ACCELERATOR stored    
procedure:
<?xml version='1.0' encoding='UTF-8'?>            
  <dwa:controlCommand                                          
   xmlns:dwa='http://www.ibm.com/xmlns/prod/dwa/2011'            
   version='1.3'>
  <getTraceData keepConfiguration='true'>        
  <content>NZLOGCOLLECTOR</content>
  <content days='2'>NZLOGCOLLECTOR</content>
  </getTraceData>            
  </dwa:controlCommand>                                        

================================================================
1.4 TIMESTAMP_ISO query support                                v
================================================================
****************************************************************
* USERS AFFECTED: Product users whose database management      *
*                 system is DB2 10 for z/OS and who want to    *
*                 accelerate queries that contain              *
*                 TIMESTAMP_ISO expressions                    *
****************************************************************
* FEATURE DESCRIPTION: This feature supports the acceleration  *
* of queries that contain TIMESTAMP_ISO expressions. The       *
* expressions must be of the type DATE, TIME, or TIMESTAMP and *
* must not specify a timezone. The feature does not work for   *
* TIMESTAMP_ISO expressions consisting of character strings or *
* graphic strings.                                             *
****************************************************************
Additional information: This feature is automatically enabled
when a table is enabled for query acceleration.

================================================================
1.5 Incremental update - continuous replication                v
================================================================
****************************************************************
* USERS AFFECTED: Users of IBM DB2 Analytics Accelerator for   *
*                 z/OS Version 4.1 using the incremental       *
*                 update function                              *
****************************************************************
* FEATURE DESCRIPTION: The new function offers the capability  *
* to let the incremental update process continue while         *
* replicated tables are added, removed, initially loaded or    *
* re-loaded. There is no need to stop the incremental update   *
* process. For both, load and reload of replicated tables, the *
* additional capability is introduced to use the lock mode ROW *
* which uses SHRLEVEL CHANGE while unloading data from DB2.    *
* Changes to a load-in-progress table are kept separate and    *
* applied when the table joins replication. The time when the  *
* separate changes are applied to the table is indicated by    *
* the new table state REFRESHING.                              *
****************************************************************
Additional information: This function must be enabled from the
IBM DB2 Analytics Accelerator console and can also be disabled
from there.



================================================================
2. Solved Problems                                             v
================================================================
2.1 SYSPROC.ACCEL_RESTORE_ARCHIVE_TABLES fails with AQT10301I  v
================================================================
****************************************************************
* USERS AFFECTED: All users of the HPSS in IBM DB2 Analytics   *
*                 Accelerator for z/OS Version 4.1             *
****************************************************************
* PROBLEM DESCRIPTION: The                                     *
* SYSPROC.ACCEL_RESTORE_ARCHIVE_TABLES stored procedure fails  *
* with error AQT10301I - An error occurred in the              *
* SYSPROC.DSNUTILU service of your database management system  *
* (DBMS). The return code is 8.                                *
****************************************************************
Problem summary: If the REBUILD INDEX or CHECK DATA phase    
could not be completed, the SYSPROC.DSNUTILU utility might be
in the STOPPED state (in DB2). This state might prevent a    
successful call of the SYSPROC.ACCEL_RESTORE_ARCHIVE_TABLES  
stored procedure.                                            

Problem conclusion: The problem has been fixed.              

================================================================
2.2 Stored procedure SYSPROC.ACCEL_GET_QUERY_EXPLAIN fails     v
    with message AQT10050I                                     v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: Calling the stored procedure            *
* SYSPROC.ACCEL_GET_QUERY_EXPLAIN fails with the message       *
* AQT10050I and message text similar to this: ' ... SQLSTATE:  *
* HY000 SQLCODE: 46 'ERROR: Bad date external representation'. *
****************************************************************
Problem summary: If the user calls the                        
SYSPROC.ACCEL_GET_QUERY_EXPLAIN to obtain information about a
a query that contains a local date format (for example        
dd/mm/yyyy), and the query has not been run on the accelerator
before, the stored procedure returns an error.                

Problem conclusion: The problem has been fixed.              

================================================================
2.3 Important information missing from log file in Linux       v
    high-availabiliy environments                              v
================================================================
****************************************************************
* USERS AFFECTED: Users of IBM DB2 Analytics Accelerator for   *
*                 z/OS Version 4.1                             *
****************************************************************
* PROBLEM DESCRIPTION: Essential information for problem       *
* analysis in high-availability (HA) environments is missing   *
* from the log file.                                           *
****************************************************************
Problem summary: In error or failover situations, essential  
information cannot be collected because the Linux environment
uses a nonverbose configuration.                              

Problem conclusion: The problem has been fixed.              

================================================================
2.4 SYSPROC.ACCEL_LOAD_TABLES fails with AQT10205I, which      v
    indicates timeout for the start of an internal thread      v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_LOAD_TABLES stored    *
* procedure returns the internal error AQT10205I with the      *
* following diagnostic information: 'An assertion 'counter2 <  *
* START_CHECK_LIMIT' failed. Additional info: Can not create   *
* thread in time because of second setup phase.'               *
****************************************************************
Problem summary: When the system load is high, the            
SYSPROC.ACCEL_LOAD_TABLES stored procedure might fail with the
internal error AQT10205I, which means that an internal thread
could not be started within a one-second timeout.            

Problem conclusion: The problem has been fixed.              

================================================================
2.5 ACCEL_ADD_ACCELERATOR2 returns warning AQT10074I when      v
    accelerator is newer than stored procedures (and therefore v
    compatible)                                                v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_ADD_ACCELERATOR and   *
* the SYSPROC.ACCEL_ADD_ACCELERATOR2 stored procedures return  *
* incorrect MESSAGE output if the versions of the accelerator  *
* software and the stored procedures are not identical. A      *
* warning might be displayed despite a successful pairing.     *
****************************************************************
Problem summary: 1. If the version of the accelerator software
is lower than the version of the stored procedures, the      
expected compatibility warning AQT10074I is not returned by  
either stored procedure.
2. If the version of the accelerator software is higher than
the version of the stored procedures, warning AQT10074I is
returned by mistake.                    

Problem conclusion: The problem has been fixed.              

================================================================
2.6 Stored procedures and user-defined functions (UDFs) abend  v
    with U4036 RC2                                             v
================================================================
****************************************************************
* USERS AFFECTED: All IBM DB2 Analytics Accelerator for z/OS   *
*                 V4.1 users                                   *
****************************************************************
* PROBLEM DESCRIPTION: Calling stored procedures or            *
* user-defined functions, such as DSNAQT.ACCEL_GETVERSION,     *
* result in user completion code 4036.                         *
****************************************************************
Problem summary: The installation JCL job for IBM DB2        
Analytics Accelerator does not fully specify all runtime      
sub-options of the Language Environment STACK. If the default
values for dsinit_size (512K) and dsincr_size (128K) are      
overwritten by lower values (for example 4K), then stored    
procedure or UDF-calls, such as DSNAQT.ACCEL_GETVERSION,      
result in user completion code 4036.                          

Problem conclusion: To fix the problem, explicitly specify all
default STACK sub-options in AQTTIJSP, that is:              
STACK(128K,128K,ANYWHERE,KEEP,512K,128K)                      

================================================================
2.7 Query fails with SQLCODE:-904, SQLSTATE:57011              v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1 PTF-3 and Version 4.1   *
*                 PTF-4 using the failback option              *
****************************************************************
* PROBLEM DESCRIPTION: The query returns SQLCODE -904 and      *
* SQLSTATE 57011. This means that failback processing does not *
* take place.                                                  *
****************************************************************
Problem summary: The problem occurs if query errors are not  
detected during the preparation phase in Netezza. For example:
unsupported common table expressions or divisions by zero.    
Such errors are found no earlier than during the fetch time.  
At that time, the product cannot return a query to DB2 for    
failback processing.                                          

Problem conclusion: Failback processing in DB2 is now        
possible.                                                    

================================================================
2.8 SYSPROC.ACCEL_GET_QUERIES returns error AQT10205I          v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_GET_QUERIES stored    *
* procedure returns a AQT10205I error, and and does not        *
* provide output. Error message:- An internal processing error *
* occurred in the stored procedure. Diagnostic information: An *
* assertion 'neededSize <=                                     *
* DBMSLimits::SP_OUTPUT_PARMS_LOB_SIZE[parameter]' failed.     *
* Additional info: Clob output parameter 3, of size 4194304    *
* not large enough for 7187122 bytes                           *
****************************************************************
Problem summary: The SYSPROC.ACCEL_GET_QUERIES stored        
procedure returns the internal error AQT10205I if the output  
size exceeds 4 MB.                                            

Problem conclusion: The problem has been fixed. The error    
information is now truncated if necessary. A new warning      
AQT20060W is returned if the output-size restriction led to a
truncation of the returned SQL text.                          

================================================================
2.9 Incremental updates stop after running the                 v
    SYSPROC.ACCEL_MIGRATE stored procedure                     v
================================================================
****************************************************************
* USERS AFFECTED: All users who have incremental updates       *
*                 enabled during a migration of table names    *
*                 from the product version 3 format to the     *
*                 product version 4 format.                    *
****************************************************************
* PROBLEM DESCRIPTION: Incremental updates stop completely as  *
* soon as data changes are supposed to go to the migrated      *
* tables. The events viewer for incremental updates lists      *
* severe errors with an ID of 6700.                            *
****************************************************************
Problem summary: During a table migration by the              
SYSPROC.ACCEL_MIGRATE stored procedure, incremental    
updates must be disabled for the DB2 subsystems that these    
tables originate from. If this does not happen, and          
incremental updates are restarted, the process tries to apply
changes to the tables with the old names. Since these tables  
cannot be found anymore, the process stops entirely. In this  
case, the replication events viewer in IBM DB2 Anayltics      
Accelerator Studio shows severe errors with an ID of 6700.    

Problem conclusion: The problem has been fixed.              

================================================================
2.10 SYSPROC.ACCEL_GET_TABLES_DETAILS always recommends a      v
     table reload if the underlying table space changes from   v
     segmented to partitioned-by-growth                        v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 Version 4.1                                  *
****************************************************************
* PROBLEM DESCRIPTION: The change detection mechanism produces *
* a misleading error message for tables whose table space has  *
* changed from segmented to partitioned-by-growth: 'table      *
* was loaded with a previous accelerator version and does not  *
* have the necessary information for change detection'         *
****************************************************************
Problem summary: After changing a table partition type in DB2
by altering the table space from segmented to partition-by-    
growth, IBM DB2 Analytics Accelerator detects the changed    
partitioning type and fails to provide proper change detection
information. The returned message was misleading.            

Problem conclusion: The problem has been fixed.              

================================================================
2.11 No error message if nzhealthcheck did not run             v
     successfully                                              v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: No confirmation is given whether the    *
* nzhealthcheck program ran successfully or whether it ran at  *
* all.                                                         *
****************************************************************
Problem summary: If IBM DB2 Analytics Accelerator could not  
run the nzhealthcheck program or if the execution failed      
without results, the program did not issue messages that      
indicated an accelerator hardware problem.                    

Problem conclusion: The problem has been fixed. A new DSNX881I
message with reason code 2003 is issued if the nzhealthcheck  
program did not run successfully.                            

================================================================
2.12 Incorrect data on accelerator when reloading a table with v
     incorrect parameters                                      v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: An accelerator tables might contain     *
* incorrect if incremental updates are applied to the table    *
* and if a load process on the same table is run with          *
* incorrect attribute settings in the XML input string of the  *
* SYSPROC.ACCEL_LOAD_TABLES stored procedure.                  *
****************************************************************
Problem summary: If the SYSPROC.ACCEL_LOAD_TABLES stored      
procedure is run without the attribute settings              
detectChanges='DATA' or forceFullReload='true' in the XML    
input string on a table that is enabled for incremental      
updates, it can happen that some of the partitions are not    
reloaded even though the original DB2 table did change. The  
incremental update function does not apply the changes either
because it usually stops when the load operation starts.      

Problem conclusion: The problem has been fixed. If the        
required attributes are not set, the load operation fails now
with error message AQT20061E.                                

================================================================
2.13 Two entries for the same creator in the accelerator       v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Studio                              *
****************************************************************
* PROBLEM DESCRIPTION: When the lengths of creator names are   *
* different, the same value appears twice. When some tables    *
* were defined with a DB2 version lower than 8, and other      *
* tables with a later version, the creator names differ in     *
* that one of the two instances contains trailing blanks.      *
* Hence the system 'considers' these to be different names.    *
****************************************************************
Problem summary: The problem occurs if tables exist that were
defined with a DB2 version lower than version 8, and other    
tables that were defined with version 8 or a later version.  

Problem conclusion: The problem has been fixed.              

================================================================
2.14 A table with an error marker in the accelerator view can  v
     be selected for loading                                   v
================================================================
****************************************************************
* USERS AFFECTED: All users of DB2 Analytics Accelerator for   *
*                 z/OS Version 4.1                             *
****************************************************************
* PROBLEM DESCRIPTION: Although an error marker is displayed   *
* in the accelerator view, you can select a table and click    *
* the 'Load' button to open the Load window. However, you      *
* receive an error message as you try to do so.                *
****************************************************************
Problem summary: If you drop a DB2 table that also exists on  
an accelerator, the table is marked as 'impaired' with a red  
error marker in the accelerator view of IBM DB2 Analytics    
Accelerator Studio. However, it is still possible to select  
the table and click 'Load' to open the Load window. An error  
message is displayed in this case. If more than one table is  
selected, the operation is discarded for all tables.          

Problem conclusion: The problem has been fixed. It is no      
longer possible to click the 'Load' button if an error marker
is shown for a selected table in the accelerator view. If more
than one table is selected, the faulty table is automatically
removed from the selection so that the load operation can    
continue for the other tables. However, you must refresh the  
accelerator view after dropping the DB2 table, so that the    
error marker is shown. Otherwise, this enhancement does not  
work.                                                        

================================================================
2.15 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.              

================================================================
2.16 Tables with altered or added columns are not reported as  v
     ViolatedInDatabaseManagementSystem by                     v
     SYSPROC.ACCEL_GET_TABLES_INFO                             v
================================================================
****************************************************************
* USERS AFFECTED:  All users of IBM DB2 Analytics Accelerator  *
*                 for z/OS Version 4.1 PTF-5                   *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_GET_TABLES_INFO       *
* stored procedure reports integrityStatus='Unimpaired'        *
* instead of 'ViolatedInDatabaseManagementSystem'. As a        *
* consequence, the refresh function in IBM DB2 Analytics       *
* Accelerator Studio does not show that a problem exists with  *
* that table.                                                  *
****************************************************************
Problem summary: Although columns were added or changed in a  
DB2 table that also exists on an accelerator, the            
SYSPROC.ACCEL_GET_TABLES_INFO stored procedure reports        
integrityStatus='Unimpaired' instead of                      
'ViolatedInDatabaseManagementSystem'.                        

Problem conclusion: The problem has been fixed.              

================================================================
2.17 SYSPROC.ACCEL_MIGRATE stored procedure fails              v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 Version 4.1 migrating from previous versions *
****************************************************************
* PROBLEM DESCRIPTION: The SYSPROC.ACCEL_MIGRATE stored        *
* procedure returns the error message AQT20043I.               *
****************************************************************
Problem summary: Tables which have been added with IBM DB2    
Analytics Accelerator for z/OS Version 3.1 or previous        
versions are subject to migrate to the new version 4.1 naming
scheme. If there are a lot of tables to be migrated it might  
occur that tables will move to 'ERROR' or 'INITIAL LOAD      
PENDING' state and the SYSPROC.ACCEL_MIGRATE stored    
procedure fails because other processes interfere with the    
migration process.                                            

Problem conclusion: The problem has been fixed.

================================================================
2.18 Error message when trying to configure the call-home      v
     feature with a RACF user ID with a length of 8 characters v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 Version 4.1 PTF-4 and PTF-5 planning to con- *
*                 figure the call-home feature                 *
****************************************************************
* PROBLEM DESCRIPTION: An error message is raised when trying  *
* to configure the IBM DB2 Analytics Accelerator call-home     *
* feature with a RACF user ID with 8 a length of 8 characters. *
****************************************************************
Problem summary: The current implementation of the IBM DB2
Analytics Accelerator Version 4.1 PTF-4 and PTF-5 call-home
feature limits the supported length of RACF user IDs to 7
instead of 8 characters. As RACF user IDs support up to 8
characters, the limitation was adjusted.

Problem conclusion: The problem has been fixed.

================================================================
2.19 Error message AQT20021I when loading a table              v
================================================================
****************************************************************
* USERS AFFECTED: All users of IBM DB2 Analytics Accelerator   *
*                 for z/OS Version 4.1                         *
****************************************************************
* PROBLEM DESCRIPTION: You receive an AQT20021I error message  *
* in the following situation:                                  *
*                                                              *
* 1. A table exists on more than one accelerator. The original *
*    DB2 table contains columns with data types that are not   *
*    supported by IBM DB2 Analytics Accelerator.               *
* 2. Incremental updates for this table have been configured   *
*    successfully on at least one accelerator.                 *
* 3. You have enabled incremental updates for the same table   *
*    on an additional accelerator. The initial load of this    *
*    table is outstanding.                                     *
*                                                              *
* You receive the error before the initial load of the table.  *
*                                                              *
* The problem occurs only if the original DB2 table has        *
* columns with unsupported data types.                         *
****************************************************************
Problem summary: Error AQT20021I is returned before the initial
load of a table that has been enabled for incremental updates
if the table exists on multiple accelerators, is already
incrementally updated on at at least one accelerator, and is
related to a DB2 base table with unsupported column data types.    
                                                                   
Problem conclusion: The problem has been fixed.

================================================================
3. Migration considerations                                    v
================================================================
If you want to upgrade to the newest version of the incremental
update function from a version older than 4.1 PTF-5, you
must update the replication engine two times. The first time,

apply the base package (RE Base) of PTF-5, and then the update
package of PTF-6 (RE Update). Wait until RE Base has been applied
successfully before you continue with RE Update.

Attention: Make sure that a replication status other than
'Error' is displayed in the header of the Accelerator view in
IBM DB2 Analytics Accelerator Studio before you apply an update
of the replication engine. Otherwise, the accelerator might
stop working and enter a state that requires the help of IBM
support.

To avoid this issue, use
IBM DB2 Analytics Accelerator Studio Version 4.1.6.201509111418
or a higher version for the update because this version checks
the replication status before an update can be applied.

Known issues

================================================================
4. Known issues                                                v
================================================================
4.1 You might lose table updates if the function for a parallel
application of incremental updates is enabled, while the
function for continuous incremental updates is disabled. If you
want to apply incremental updates in parallel, make sure that
you also enable continuous incremental updates.

================================================================
4.2 Some packages might not be selectable in the Transfer window
of IBM DB2 Analytics Accelerator Studio even though they have not
yet been transferred. This was most likely caused by one of the
following conditions:

1. IBM DB2 Analytics Accelerator Studio was set to a locale other
than US English.

2. IBM DB2 Analytics Accelerator Studio was not set to any locale.
In this case, the program uses the locale of the operating
system. If that locale is different from US English, you end up
with the same issue.

To circumvent this problem, use US English as the locale for IBM
DB2 Analytics Accelerator Studio. On a Windows system, add
'-nl en_US' (without the quotes) to the start command that you
find in the properties of the shortcut that launches the
application ("Target" field on "Shortcut" tab). On a Linux
system, open the eclipse.ini file and add the following line:

-Duser.language=en -Duser.country=US

Save and close the file. Then start the application.
 


Document information

More support for: DB2 Analytics Accelerator for z/OS

Software version: 4.1.0

Operating system(s): z/OS

Reference #: 7046294

Modified date: 19 September 2017


Translate this page: