IBM Db2 Analytics Accelerator for z/OS Version V5.1.0 PTF-7 Release Notes

Please find information about new functions here .

For recommendations and considerations concerning migration to IBM Db2 Analytics Accelerator for z/OS Version 5.1.0 read here.

1. IBM Netezza Analytics
   For known issues with the IBM Netezza Analytics stored procedure package in IBM Db2 Analytics Accelerator for z/OS Version 5.1.0, see:

   Known issues with IBM Netezza Analytics for System z for IBM Db2 Analytics Accelerator for z/OS Version 5.1.0

2. Encryption of Data in Motion
   For known issues with the network traffic encryption feature (encryption of data in motion) in IBM Db2 Analytics Accelerator for z/OS Version 5.1.0, see:

   Known Issues with Encryption of Data in Motion in IBM Db2 Analytics Accelerator for z/OS Version 5.1.0

3. Transfer of software update packages from IBM Db2 Analytics Accelerator Studio not possible
   Summary

   IBM Analytics Accelerator Studio does not allow users to transfer packages. A message hints at the fact that a newer version is already installed on the server. If the locale in the IBM Analytics Accelerator Data Studio is set to a value different from English or German, the transfer of software update packages might be blocked in rare cases.

   Solution or workaround

   The problem has been fixed with the stored procedures of IBM Db2 Analytics Accelerator for z/OS Version 5.1.0 maintenance level PTF-1. If you run the software transfer with a previous version of the stored procedures, use the following workaround:

   1. Use US English as the locale for IBM Db2 Analytics Accelerator Studio.
   2. 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

   3. Save and close the file. Then start the application.
4. If the system utilization is very high, the accelerator might restart automatically to recover from the overload situation
   Summary

   The accelerator goes online again after the recovery. Processes that were ended prematurely by the restart, such as load jobs or queries, must be restarted.
   Example of high system utilization: 30 parallel load threads with tables having 10 partitions

   Solution or workaround

   1. Check the system utilization.
   2. Adjust the system utilization as needed.
   3. Retry failed operations and continue.
5. The execution of an INSERT INTO ... SELECT ... FROM statement in an in-database transformation job might fail
   Summary

   In rare situations, INSERT INTO ... SELECT ... FROM statements in in-database transformation jobs can fail if the system utilization is very high and many processes are run in parallel.

   Solution or workaround

   This is an indication that the system limits were reached. Check the system utilization and adjust it to the capacity of the system.
6. Incremental update processing might stop and restart if the system utilization is very high (many parallel load and query operations). This is indicated by according console messages
   Summary

   If the system utilization is very high, with many processes running in parallel, the processing of incremental updates might stop. Processing resumes after some time and stalled operations are recovered automatically. If "continuous incremental updates" are enabled, tables that are being loaded at the time of the interruption go into the "suspended" state. You must reload such tables to get them back into the incremental update processing queue.

   Solution or workaround

   This is an indication that the system limits were reached. Check the system utilization and adjust it to the capacity of the system.
7. Insertion of integer and decimal values causes failure of IDT jobs
   Summary

   The insertion of integer and decimal values by an INSERT INTO ... VALUES statement might cause a failure of in-database transformation (IDT) jobs.

   For example, the following statement failed during tests:
   CREATE TABLE T1 (CDEC51 DECIMAL(5,1)) IN ACCELERATOR XYZ;
   INSERT INTO T1(CDEC51) VALUES(77247.04-69993);

   Symptoms: SQL codes like the following are returned:

   SQLCODE = -802, SQLSTATE = 22003, DATA EXCEPTION FROM IBM DB2 Analytics Accelerator TOKENS OVERFLOW ACCELERATOR NUMERIC DATA...

   Solution or workaround

   Use only decimal values instead of a mixture of integer and decimal values. The following statement, for example, will be successful:

   INSERT INTO T1(CDEC51) VALUES(77247.04-69993.0)

8. Tables cannot be added if their names contain special characters, such as tabs and newlines
   Summary

   Tables cannot be added if their names contain special characters, such as tabs and newline characters.

   Solution or workaround

   Fix will be delivered in a later release.
9. Large number of accelerator-shadow tables might extend time needed to activate incremental updates
   Summary

   If there is a large number of tables on an accelerator, that is, more than 30000 the activation of incremental updates for these tables might take longer. In this context, it does not matter whether the tables have already been enabled. The extra time needed is relevant if the number of table activations in one request exceeds 10 because this will lead to a premature end of the operation, which in turn leads to an automatic disablement of incremental updates for those tables. You must re-enable and reload such tables.

   Solution or workaround

   Reduce the number of tables that are activated in a single batch job to less than ten (<10).
10. If the system utilization is high, load operations might fail with a message "Failed to start child transaction in session " -LocksharedObjectWait: LockAcquire failed".
    Summary

    Under a high system load, load operations might fail with a message "Failed to start child transaction in session " -LocksharedObjectWait: LockAcquire failed".

    Solution or workaround

    Retry the load operation.
11. ALTER TABLE ALTER PARTITION is not blocked by a partition in PRO State (Db2 V11 only)
    Summary

    A partition can be altered by an ALTER TABLE ALTER PARTITION statement although the partition has been archived by the SYSPROC.ACCEL_ARCHIVE_TABLES stored procedure. Normally, SQLCODE -904 would be returned because the archived partition has been set to the PRO state.

    Solution or workaround

    Because a read-only partition was changed, a following restore operation will probably fail. The problem has been fixed in Db2 V12.

• Use the sample code (for a stored procedure) in the following technote:

  How to store information about accelerated tables in a Db2 for z/OS table

  to retrieve information about your accelerator-shadow tables. This information will be stored in a temporary Db2 table.

• Run a simple SQL query against the replicationStatus and the lastLoadTimestamp columns of this temporary table to identify tables that must be reloaded. Follow the diagram at the end of this note to determine whether a table must be reloaded.

• Immediately after the upgrade to V5.1.0 PTF-7, an automatic conversion of data structures takes place.
• Depending on the total amount of data to be converted, this might take more than 1 hour, during which the Netezza Platform Software (NPS) will be in the "Initializing" state. That is, the NPS cannot process requests.