Please find information about new functions here .

• Accelerator on IIAS-specific considerations

  If you plan to install or upgrade IBM Db2 Analytics Accelerator, please contact IBM support by opening a case.
  For an upgrade we would like you to create an Appliance trace and to upload it and the Transfer log to the support case for an offline health check of the system.
  Further, before you begin, please consider the description in APAR PH26946.

  The steps to be performed for an upgrade depend on your current maintenance level of the accelerator:

  Current Accelerator V7 maintenance level	Upgrade to 7.5.8 - required steps	Elapse time needed for applying (*) the software (Ballpark estimation)
  7.5.7.x	Perform a full upgrade to maintenance level 7.5.8. Note: An "essential" update is supported for the upgrade to 7.5.8, but will not save more than around 60 min.	5 h (when replication and accelerators are stopped)
  7.5.6.x   or 7.5.5.x   or 7.5.4.x   or 7.5.3      or 7.5.2.x   or 7.5.1	The upgrade consists of two steps: Step 1: Perform a full upgrade to maintenance level 7.5.7.x. This step will migrate the IDAA from docker to podman and is mandatory. Step 2: Perform a full or essential Upgrade to 7.5.8. Note: An "essential" update is supported for the upgrade to 7.5.8, but will not save significant time.	1 day
  7.5.0.1	The upgrade consists of three steps: Step 1: Upgrade from 7.5.0.1 to maintenance level 7.5.3. Step 2: Full upgrade to maintenance level 7.5.7.x (podman). Step 3: Full or essential Upgrade to 7.5.8. Note: Some firmware updates introduced with 7.5.1 require a full upgrade to 7.5.3, when skipping 7.5.1. Therefore an "essential" update is not possible. Further, before you begin, please consider the description in APAR PH27055.	1.5 day
  7.1.9.x	The upgrade consists of the following mandatory steps:   Step 1: Upgrade to maintenance level 7.5.0.1. Step 2: Upgrade from 7.5.0.1 to maintenance level 7.5.3. Step 3: Full upgrade from 7.5.3 to maintenance level 7.5.7.x (podman) Step 4: Full or essential Upgrade to 7.5.8   Note: We recommend to perform the first two required upgrade steps in the same maintenance window. To save some time the first upgrade to 7.5.0.1 can be an “essential” update, skipping firmware updates, followed by the mandatory full upgrade to 7.5.3.	2 days
  Prior to 7.1.9	The upgrade consists of the following mandatory steps:   Step 1: Upgrade to maintenance level 7.1.9.1. Step 2: Upgrade from 7.1.9.1  to maintenance level 7.5.0.1. Step 3: Full upgrade from 7.5.0.1  to maintenance level 7.5.3. Step 4: Full upgrade from 7.5.3 to maintenance level 7.5.7.x (podman) Step 5: Full or essential upgrade from 7.5.7.x to maintenance level 7.5.8.   Note: While step 2 can be an “essential” update skipping firmware updates, the upgrade to 7.5.3. in step 3 is a mandatory full upgrade.	2.5 days

  (*) The time required for downloading the upgrade packages and subsequent transfer to the Accelerator is not included.
• Accelerator on Z-specific considerations

  The steps to be performed for an upgrade depend on your current maintenance level of the accelerator:

  1. Current maintenance level: 7.5.7.x, 7.5.6.x, 7.5.5.x, 7.5.4.x, 7.5.3, 7.5.2.x, or 7.5.1
     • We recommend to migrate directly to maintenance level 7.5.8.
     • Important: Compared to previous product releases, the JSON configuration file syntax has changed considerably with product version 7.5.3 and later. Therefore, whenever you want to change the configuration of the accelerator, download the currently active configuration file for the accelerator using the Appliance Installer web user interface for modifications. The downloaded file contains the active configuration with the new JSON syntax.
  2. Current maintenance level: prior to 7.5.1
     • If you plan to install or upgrade IBM Db2 Analytics Accelerator, please contact IBM support by opening a case.
       For an upgrade we would like to know your current maintenance level of the accelerator software and the one you want to upgrade to.
• New mandatory settings for the setup of Integrated Synchronization
  • Excluding suspended tables from accelerated queries

    The administrator must grant the following privileges to the Db2 for z/OS user ID having been specified during enabling of the subsystem for replication using IBM Integrated Synchronization:

    • EXECUTE on the SYSPROC.ACCEL_SET_TABLES_ACCELERATION stored procedure
    • RACF ACCESS(READ) on the data set that contains the AQTENV file in the started task procedure of the Workload Manager (WLM) environment
    • RACF ACCESS(READ) on the data set that contains the AQTDEF6 file in the started task procedure of the Workload Manager (WLM) environment
    • Define an OMVS segment in the Resource Access Control Facility (RACF)

  • Support of schema changes (Add/Alter column)
    • If the schema change affects columns of the type TIMESTAMP, you must also install the PTF UI73158 for Db2 for z/OS (APAR PH31772)
    • The Db2 for z/OS user you specified when you enabled IBM Integrated Synchronization must have the following additional privileges:
      • SELECT privilege on SYSIBM.SYSTABLES, SYSIBM.SYSCOLUMNS
      • SELECT, UPDATE privilege on SYSIBM.SYSACCELERATEDTABLES

Click here for the list of APARs having been fixed.

The SYSPROC.ACCEL_LOAD_TABLES stored procedure behaves differently if automatic change detection is enabled.
Before version 7.1.7, a load job with a setting of detectChanges=“DATA” sometimes did not capture the changes in all partitions if the lock mode NONE had been used for the previous load.
This was fixed with version 7.1.7.

The new behavior:
If you use lock mode NONE and detectChanges=“DATA”,

• it can happen that more changes are detected than are transferred to the accelerator. This is caused by the SKIP LOCKED DATA option, which is used implicitly by the Db2 Unload Utility. If parts of the data were locked by other processes, then this data is ignored and not unloaded to the accelerator.

• therefore, a partition in an accelerator-shadow table is always fully reloaded to ensure that all changes are finally transferred. A reload is started even if the partition had no further changes since then.

Starting with 7.5.7 the appliance database settings have been improved to increase the performance of queries. While most queries benefit from the change, some queries might face a performance decline. If you were affected, contact IBM support for a revert of the changed settings in a remote maintenance session.

General recommendations

• Under a high system load, the accelerator might appear slow or run into timeouts.

  Recommendation: Do not run more than 30 load threads in parallel.

Queries

• A query running during a partial reload of an incrementally updated table might be unable to access the new partitions.

  Recommendation: Rerun the query after the partial reload has finished.

• A query referencing several tables using union all views could run slower than V5.
  Example use cases are when union all views are used for collecting data from multiple branch offices and each branch-office has a schema-identical table that your are all referencing in a single query.

  Recommendation: Contact IBM support for assistance.

• An SQL statement that contains a CAST on a column with the time data type as a character data type may return with colon delimiters instead of dot delimiters once after a table is loaded.

  Example: For the following query "SELECT cast(c_time as char(8)) from T1": On Db2 12 for z/OS the value returned is "13.10.00" as a character string. On the accelerator the value returned is "13:10:00" as a character string. This occurs only once after a table is loaded.

Loading tables

• After running the REORG utility in Db2 12 for z/OS,  reloads might be wrongly recommended for partitions that have already been loaded on the accelerator.

  Recommendation: To receive correct reload recommendations, do not use interactive load recommendations and batch job change detection at the same time.

Incremental updates

• CDC-based replication: The time needed to reload a set of incrementally updated tables increases as well as the replication latency.

  Recommendation: Pause after each reload, as this allows the system to come back to normal throughput rates and latency levels.
  As an alternative: use Integrated Synchronization based replication.

• InSync-based replication: Log reader commands are stuck waiting for reply, leading to continuously timed out commands.
  In rare situations commands are returned with timeouts and latency grows continuously (if replication is running).

  Recommendation: Restart replication via configuration console.

• InSync-based replication: Possible missing data updates from Db2 13 for z/OS
  Due to a current limitation in Db2 13 data might not be updated in the Accelerator.

  Recommendation: Install PTF for Db2 13 for z/OS APAR PH45854 once it is available

Monitoring

• The values of the monitoring counter Q8STTMUD are too high, for example 0.18E+20.

  Recommendation: Ignore the high value. It will be corrected during the next collection of statistics.

• The monitoring values of the Q8STCQL, Q8STCQLS, and Q8STQUEW metrics might be displayed incorrectly.

Accelerator Studio GUI

• "Transfer certificates" for "Encryption of Data in Motion" in DataStudio based GUI only allows file extension ".crt" for certificate transfers, not ".p12".

  Recommendation: When transferring a certificate for "Encryption of Data in Motion", then locate the certificate file on your client and change the extension from ".p12" to ".crt". The certificate file will then become visible in the available certificates box of the GUI, so that you can transfer it.

Miscellaneous

• Under a very high system load caused by the parallel execution of various operations, such as 'Add Tables', 'Remove Tables', and 'Alter Keys', the accelerator might restart unexpectedly, leading to the abortion of running tasks or queries.
  Symptoms are aborted tasks, lock timeout exceptions, or messages with SQL code -911, SQLSTATE=40001, and rc=68.

  Recommendation: Reduce the task diversity of parallel jobs if you process large table sets with more than 100 tables. For example, do not run 'Alter Keys', 'Add Tables', and 'Remove Tables' operations at the same time. Reduce this to 'Alter Keys' and 'Add Tables' jobs or any other combination of just two different tasks.
  If a query failed, rerun the query.

• When a date literal in a LOCAL date format DD/MM/YYYY or YYYYMMDD is CAST as a CHAR or VARCHAR, the result is not the local date format but rather ISO.
  For example: CAST(DATE('22/11/2018') AS CHAR(10)) will return 2018-11-22 instead of '22/11/2018'.

  Recommendation: None