IBM Support

IBM DB2 Analytics Accelerator for z/OS Version 6.1.0 PTF-1 Release Notes

Release Notes


Abstract

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

Content

Solved Problems

  1. Problem description
    Under rare circumstances, a load of a table which was previously removed and then added again, may abort.
    Problem conclusion
    The problem has been fixed.


Migration considerations

There are no migration considerations.



Conditions for query routing

Queries can be routed to an accelerator only if certain conditions are met. There are also adverse conditions that prohibit query acceleration.

For more information please see Conditions for query routing to an accelerator



Known issues

  1. Currently IBM DB2 Analytics Accelerator for z/OS Cloud Support cannot handle queries that reference system-temporal or business-temporal tables. This means that queries containing one or more of the following clauses cannot be accelerated:

    FOR SYSTEM_TIME AS OF
    FOR SYSTEM_TIME FROM ... TO ...
    FOR SYSTEM_TIME BETWEEN ... AND ...
    FOR BUSINESS_TIME AS OF
    FOR BUSINESS_TIME FROM ... TO ...
    FOR BUSINESS_TIME BETWEEN ... AND...

  2. Currently IBM DB2 Analytics Accelerator for z/OS Cloud Support cannot handle queries that reference timestamp columns encoded in EBCDIC.
    Workaround:
    If possible, use Unicode-encoded timestamp columns.
  3. In rare situations the accelerator could crash unexpectedly during a table load, but recovers automatically.
    Workaround:
    Restart load job.
  4. A reload of a table with the parameter setting forceFullReload=true fails and the internal error message AQT10050E is returned if a previous reload was interrupted by a command, such as dwa-admin stop.
    Workaround:
    1. Remove the table.
    2. Add the table again.
    3. Load the newly added table.
  5. If you run an INSERT INTO ... SELECT ... FROM statement to extract data from GRAPHIC or VARGRAPHIC columns of an accelerator-shadow table encoded in Unicode or EBCDIC and insert the resulting rows into a DB2 for z/OS table, the insertion fails and DB2 ends abnormally. The same applies to CHAR FOR MIXED DATA or VARCHAR FOR MIXED DATA columns of accelerator-shadow tables encoded in EBCDIC.
    Workaround:
    Avoid to execute insert statements of this type.

[{"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":"6.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 August 2018

UID

swg27049449