Product Documentation
Abstract
This document lists the APARs fixed with maintenance level 7.1.8 or higher
Content
APARs fixed by MCL updates
| APAR # | APAR description | Comments |
| PH55922 | After upgrading an accelerator multi-node cluster to maintenance level 7.5.11 (7.5.10) the data nodes fail to start. | Bundle S84 (z15), Bundle S32 (z16) |
| PH59572 | After Power On/Reset of an IBM z15 HW using DPM mode, a multi-node accelerator cluster using RoCE cards does not start. | Bundle S85 (z15) |
APARs fixed with updates of IBM Data Studio / IBM Db2 Analytics Accelerator Studio
| APAR # | APAR description | Comments |
| PH34329 | When using Data Studio to create an AOT, conveying a distribution key using the ACCOPTS keyword is not honored. | #AOT, #DataStudio |
| PH53684 | Query monitoring view of Accelerator Studio: context menu of a single query erroneously provides "Collect System Performance Data" | #DataStudio, #idaa7511 |
APARs fixed with maintenance level 7.5.12.2
| APAR # | APAR description | Comments |
| PH57311 (DT242744) |
WA (COGNOS-generated) query can be hung during query acceleration and needs to be cancelled. | #Query, #COGNOS |
| PH59061 (DT258120) |
Although a kernel crash causes on outage of all data nodes of a multi-node accelerator, there is no corresponding msg in DB2MSTR. | Applies only to IDAA V7 on IBM Z |
| PH59232 (DT258770) |
The fields AccessCount and LastAccessTimeStamp for an accelerator-shadow table are updated even without running a query on that table. | |
| PH59234 (DT258778) |
The Admin UI of the Accelerator on IBM Z times out prior to the time period specified in parameter admin_ui_timeout of the JSON configuration file. | Applies only to IDAA V7 on IBM Z |
| PH59297 (DT259026) |
Accelerated queries terminate abnormally: in Data Studio a state of "Failed(57011)" is shown, in QMF SQL00904N is noticed. | #Queries Applies only to IDAA V7 on IBM Z |
| PH59367 (DT259300) |
The capturing of query performance data or of an accelerator trace fails: the pop-window to save the trace is not displayed. | #Queries |
| PH60191 (DT271946) |
After a preceding reboot of the Accelerator LPAR(s) a subsequent start of replication can fail with message AQT20007E. | #InSync Applies only to IDAA V7 on IBM Z |
| PH60989 (DT380229) |
When running an accelerator on IBM Z with maintenance level 7.5.12.0 or 7.5.12.1, the triggering of an SSC dump may fill up the root directory of the installation. | #InSync Applies only to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.5.12.1
| APAR # | APAR description | Comments |
| PH59820 | With accelerator maintenance level 7.5.12, load operations can finish with RC 0 and a success message while the data loaded is not complete | #Load, #Query, #incorrout |
APARs fixed with maintenance level 7.5.12
| APAR # | APAR description | Comments |
| PH54569 | Running sample job AQTSJI03 returns error messages IEW2606S and IEW2456E. A JCL error occurs when running sample job AQTSJI05 | #Installation, #samplejobs |
| PH55263 | Accelerator-shadow tables are not set to Error state although apply errors have happened during replication using InSync. | #InSync |
| PH55508 | High Performance Storage Saver-archiving process fails with message "SQL30081N A communication error has been detected". | #HPSS |
| PH55926 | After having transferred an upgrade package to an accelerator, the verification process can face a timeout (msg AQT20107E). | Applies only to IDAA V7 on IIAS |
| PH56020 | A partial reload of accelerator tables followed by a start of the stored procedure ACCEL_COLLECT_TABLE_STATISTICS leads to SQLCODE -911. | #InSync |
| PH56218 | The analysis of a performance impact for loads unveiled wrong default configuration settings on the single node accelerator. | Applies only to IDAA V7 on IBM Z |
| PH56223 | DSNX881I msg indicates a failure of GetReplicationStatusRequest, another msg complains about missing replication status. | #InSync |
| PH56545 | After upgrade to maintenance level 7.5.11.1 (.2) the DB2 master log DB2MSTR shows DSNX881I message with unknown msgcode 4000 | #Monitoring |
| PH56594 | Options for configuration parameter "Allow or disallow queries to run if WAITFORDATA timeout is reached" lead to wrong system behavior. | |
| PH56977 | Accelerator Loader job seems to be hung; run of stor proc ACCEL_LOAD_TABLE is cancelled; occurrence of message AQT20121E and SQL0913N. | |
| PH56982 | An error message is received when looking at the replication events in Db2 Analytics Accelerator Studio. | |
| PH57166 | With accelerator maintenance level 7.5.11(.x) a call of stored procedure ACCEL_ARCHIVE_TABLES can end with message AQT20121E. | |
| PH57282 | The attaching of DASDs upon startup of the accelerator can randomly fail for some of the DASDs with an error message "An error occurred in the DASD device driver, reason=14". | Applies only to IDAA V7 on IBM Z |
| PH57521 | The display of 'organized percentage' for a table shows 100% although it has not been organized. | |
| PH57529 | An accelerator multi-node cluster is down and none of the data nodes is reachable. | Applies only to IDAA V7 on IBM Z |
| PH57620 | The activation of RoCE cards does not work if upper-case characters are used in the hex-values corresponding FIDs. | #RoCE |
| PH57670 | Message "DSNX881I System went from state UNKNOWN to ONLINE" appears in DB2MSTR. |
APARs fixed with maintenance level 7.5.11.1
| APAR # | APAR description | Comments |
| PH53015 | In rare situations an accelerated query joining at least three tables may return an incorrect result set. Repeating the query even leads to different results.. | #Query |
| PH54635 | A LOAD of an accelerator-only table is not blocked, subsequently leading to a catalog corruption and taking the accelerator down. | #AOT, #Load |
APARs fixed with maintenance level 7.5.11
| APAR # | APAR description | Comments |
| PH11495 | DSNX881I message reports "UNHEALTHY COMPONENT DETECTED", however the closure of the issue is not reported | Applies only to IDAA V7 on IIAS |
| PH38537 | PROCESSING OF A QUERY WITH A LARGE IN-LIST MAY END WITH SQLCODE=-954, SQLSTATE=57011 | #Query, #Db2wh |
| PH49824 | A query fails with -4742 RC12 after a corresponding table has been archived on two accelerators | #Query |
| PH51318 | A multi-row insert of a single row into an accelerator-only table (AOT) using a host variable / parameter marker to indicate the amount of rows to be inserted ends with SQLCODE -313. | #MRI, #AOT |
| PH52601 | Manual adaptations needed to support a different cipher for encryption of data in motion are not upgrade-persistent | |
| PH52603 | Configuration data defined for use of a proxy server with the acclerator's call-home function are not upgrade persistent. | #call-home |
| PH52981 DT188951 |
A query fails with error message "[IBM][CLI Driver][DB2/LINUXZ64] SQL0901N The SQL statement or command failed because of a database system error. (Reason "unexpected error at JoinSpillInfo.cpp:7731".) SQLSTATE=58004" | #Query |
| PH53052 | A transaction with a mixture of DDL & DML statements causes Integrated Synchronization to enter a restart loop. | #InSync |
| PH53307 | Using the monitor option in Db2 Analytics Accelerator Studio and clicking the "Finished Task" tab leads to an error. | #DataStudio |
| PH53921 | After having collected a CDE trace for a query the trace data are not completely part of the Accelerator trace. | #Trace, #Db2wh |
| PH53956 | Using the query monitoring section of Db2 Analytics Accelerator Studio to cancel a long-running query does not work. | #Query |
| PH55467 | When processing a multi-row insert statement without parameter markers on an AOT the accelerator server suddenly restarts | #MRI, #AOT |
| PH56021 | Integrated Synchronization fails with a NullPointerException after a system issue causing a restart of Db2 for z/OS | #InSync |
| PH56024 | A table enabled for replication using Integrated Syncronization table is repeatedly suspended from replication and set to error state. | #InSync |
| PH56056 | During the processing of a high number of table loads on the accelerator, hanging loads, high replication latency, and query performance degradation can be observed. | #InSync, #Load, #QryPerformance |
| PH60835 | When using "hyperpav": "auto" in the Accelerator configuration, the upload of the JSON file leads to an error message. | Applies only to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.5.10
| APAR # | APAR description | Comments |
| PH34713 | Large update transactions with compensation (e.g. a rollback to a syncpoint) may lead to high replication latency | #InSync |
| PH48647 | Replication events from Integrated Synchronization (InSync) shown in IBM DB2 Analytics Accelerator Studio have stopped responding or are outdated. | #InSync |
| PH49449 | The load of a table (that is replicated using Integrated Synchronization) to the accelerator fails with message AQT10082E after a preceding schema change. | #InSync |
| PH49539 | Massive updates on accelerated tables within a single unit of recovery (UR) cause failure of Integrated Synchronization | #InSync, #AQT20126E |
| PH50187 | CDC-replicated tables out of a sudden get suspended from replication ("Table ... was parked because of an error...") | #CDC |
| PH51010 | After upgrading or installing the Accelerator on IBM Z, the Admin UI cannot be opened. The SSH session cannot connect either. | Applies only to IDAA V7 on IBM Z |
| PH51085 | Accelerator trace is flooded with unspecific getSubscriptionName warnings | #InSync |
| PH51274 | The Db2 for z/OS accounting trace always contains a 0 for the accumulated accelerator CPU time in counter Q8ACACPU. | |
| PH51670 | Using Integrated Synchronization duplicate rows can be inserted on the accelerator under special workload circumstances. The issue is accompanied by message "DSNX881I ... 20 W 3004 ... Subscription (subscription name)... Message: xxx rows parsed, but apply changed yyy rows. Table (table name) is inconsistent, set table state to ERROR." The number of applied rows, yyy, is greater (!) than the number of parsed rows, xxx, typically by 1. |
#InSync |
| PH53680 | Enabling continuous replication fails with message CHC0959E: "Signal ... cannot be processed. Table "{schema}.{table name}" is in an incorrect state...". |
#CDC |
APARs fixed with maintenance level 7.5.9.2
| APAR # | APAR description | Comments |
| PH48832 | After migrating to Accelerator maintenance level 7.5.9 a query can terminate abnormally with ABEND04E RC00D35011 in DSNLZRCD | |
APARs fixed with maintenance level 7.5.9.1
| APAR # | APAR description | Comments |
| PH48343 | While the accelerator was busy with processing of load tasks Integrated Synchronization reported a severe error (E2030) | #InSync |
| PH48445 | Installation of Accelerator on IBM Z in a multi-node environment fails if the wrong data node password is specified | Applies only to IDAA V7 on IBM Z |
| PH48832 | After migrating to Accelerator maintenance level 7.5.9 a query can terminate abnormally with ABEND04E RC00D35011 in DSNLZRCD |
APARs fixed with maintenance level 7.5.9
| APAR # | APAR description | Comments |
| PH49539 | Massive updates on accelerated tables within a single unit of recovery (UR) cause failure of Integrated Synchronization | #InSync IBM Support needs to set parameter 'SingleUpdateRecordMetadata- ToDiskMigrationThreshold' in a remote maintenance session. |
| PH51433 | Replication using Integrated Synchronization reports an inconsistency for a table, has set the table to ERROR state and has disabled acceleration for it. | #InSync |
| PH52372 | An accelerated SQL query ends with SQLCODE 901 in Db2 for z/OS and msg "SQL30081N A communication error has been detected." For further details see Db2luw-APAR IT41211. |
#IT41211 |
APARs fixed with maintenance level 7.5.8
| APAR # | APAR description | Comments |
| PH42758 | Upgrading the accelerator maintenance level may fail with msg AQT20135E although replication had been stopped before | #InSync |
| PH46474 | When performing an ALTER ADD COLUMN schema change for a CHAR column with default 'blank', the rows contain ASCII blanks X'20' | #InSync |
| PH46585 | After having successfully archived a table to accelerator 1, the archiving of the table to accelerator 2 fails with message AQT20121E. | Fixed with PTF UI80135 delivering the Stored Procedures of maintenance level 7.5.8 |
| PH46629 | After updating accelerator maintenance level from 7.5.4 to 7.5.6 or 7.5.7 the IIDR/CDC-replication cannot be started. | #CDC |
| PH51671 | After having got suspended due to a crash in DB2WH, Integrated Synchronization does not restart automatically | #InSync |
APARs fixed with maintenance level 7.5.7
| APAR # | APAR description | Comments |
| PH31479 | Command "DIS ACCEL(<ACC NAME>), DETAIL TOTAL DISK STORAGE" results in "N/A"; "TOTAL DISK USAGE" shown in Analytics Accelerator plugin of DATA STUDIO also is not correct. | Applies only to IDAA V7 on IBM Z |
| PH31527 | Running job AQTTIJSP using INSTALL-PREFVIEW the list of AUTHIDS specified for GRANTTO is not processed completely. | Fixed with PTF UI78158 delivering the Stored Procedures of maintenance level 7.5.7 |
| PH36918 | AQTSCALL does not support functions "ARCHIVETABLES" and "RESTORETABLES". | Fixed with PTF UI78158 delivering the Stored Procedures of maintenance level 7.5.7 |
| PH38578 | Stopping or starting replication or loading of CDC-replicated tables mail fail with message AQT20009E | |
| PH38586 | Explaining an SQL statement can fail with messages AQT20001W and AQT20125E. | Fixed with PTF UI78158 delivering the Stored Procedures of maintenance level 7.5.7 |
| PH39057 | After having upgraded accelerator on IBM Z to maintenance level 7.5.6 the startup of the accelerator mail fail. | Applies only to IDAA V7 on IBM Z |
| PH39096 | Replication using Integrated Synchronization out of a sudden goes into 'ERROR' state and can no longer be started. | #InSync |
| PH40423 | A load job can fail with msg "AQT20121E ...Failed to acquire SQL transaction serialization lock". | |
| PH40464 | A query can fail with SQLCODE -904, message "ERROR: Unsuccessful execution caused by an unavailable resource." | |
| PH40918 | Loading of tables enabled for replication using Integrated Synchronization fails with messages AQT20009 and "TTLS ERROR RC: 456 SSL CONTROL DATA READ". | #InSync |
| PH41083 |
REST certificate expires on January 8, 2022!
High Availability checks won't work anymore due to stopped platform manager.
|
Applies only to IDAA V7 on IIAS |
| PH41388 | After failure of replication using Integrated Synchronization a subsequent restart can fail as well (DSNX881I 20 E and 3008 E). | #InSync |
| PH42138 | After replication using Integrated Synchronization out of a sudden has terminated abnormally, an automatic restart is suspended. | #InSync |
| PH42140 | Load jobs may be stuck in 'Initializing' state. | |
| PH42142 | Integrated Synchronization parameter EnableDDLReplication is gone after upgrading the maintenance level of the accelerator. | #InSync |
| PH42359 | Vulnerability scans of Accelerator maintenance levels up to 7.5.6.x may raise issues related to OPENSSH. |
Applies only to IDAA V7 on IIAS |
| PH46475 | Unable to unwrap the Encapsulation key. The appliance cannot be booted. | Applies only to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.5.6
| APAR # | APAR description | Comments |
| PH33677 | A query containing a CASE WHEN EXISTS-clause incl. a subquery using 'FETCH FIRST 1 ROWS ONLY' may deliver incorrect results. | |
| PH35721 | Operations such as Add, Remove, Load, CONTROL_ACCELERATOR do not finish and may lead to message AQT10050E. | |
| PH36219 | A load task may stall for several hours while the accelerator's transaction log continuously grows | |
| PH36364 | An HTAP query may end with SQLCDE -904 (accompanied by message text "Set of tables is empty or invalid.") | |
| PH36479 | The cancellation of a task (Load or Query) may result in a restart of the accelerator. | |
| PH36484 | The cancellation of a Load task may lead to a hang of this task | |
| PH36727 | Users of accelerator on IBM Z do not see encryption status in Data Studio | Applies only to IDAA V7 on IBM Z |
| PH36776 | WAITFORDATA queries seem to get a time penalty when Integrated Synchronization is used as replication method. | #InSync |
| PH38537 | Processing of a query with a large IN-LIST may end with SQLCODE=-954, SQLSTATE=57011 | |
| PH38542 | SQL lock events are no longer retrieved and purged from Db2wh |
APARs fixed with maintenance level 7.5.5.2
| APAR # | APAR description | Comments |
| PH36129 | ACCELERATOR ON IBM Z MANAGEMENT CONSOLE NOT ALLOWING SCROLLING DOWN | Applies only to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.5.5.1
| APAR # | APAR description | Comments |
| PH33711 | Upgrade to accelerator maintenance level 7.5.4 requires a restart after occurrence of a Disable-Webconsole-Timeout | |
| PH35210 | Custom thresholds in Db2 LUW (defined via CREATE THRESHOLD) may cause a crash of the accelerator with subsequent automatic restart | |
| PH35326 | Query Monitoring in IBM Db2 Analytics Accelerator Studio lists canceled queries with state 'FAILED' and SQLCODE 0. | |
| PH35370 | Multiple-row Insert (MRI) into an accelerator-only table using DB2 Connect inserts incorrect values | |
| PH35373 | Multiple-row Inserts (MRI) of a local application into an accelerator-only table my fail with a negative SQLCODE. |
|
| PH36450 | A query may return more rows compared to running it in DB2 for z/OS or using V5 of the accelerator. |
APARs fixed with maintenance level 7.5.5
| APAR # | APAR description | Comments |
| PH33419 | Table partitions in 'ARCHIVE INCOMPLETE' state cannot be re-archived. | |
| PH33950 | Data Studio shows wrong table size after full table reload. | |
| PH34319 | When working with the 'QUERY HISTORY' OF DB2 Analytics Accelerator Studio, the default "REFRESH" interval needs to be 'AUTOMATIC OFF'. | |
| PH34511 | Working with Query Monitoring leads to message "The entity name must immediately follow the '&' in the entity reference". | |
| PH34723 | Using stored procedure ACCEL_COLLECT_TABLE STATISTICS erroneously ends with message AQT20139E. |
|
| PH35160 | Replication using Integrated Synchronization can fail with SQLCODE=-20570, SQLSTATE=22551. |
#InSync |
| PH35591 | Queries on federated reference tables may end with SQLCODE -551. |
APARs fixed with maintenance level 7.5.4.2
| APAR # | APAR description | Comments |
| PH33657 | Queries conveyed using an ODBC/CLI driver end with SQL0902C, reason code "9", SQLSTATE=58005 |
APARs fixed with maintenance level 7.5.4.1
| APAR # | APAR description | Comments |
| PH33490 | Although having chosen to include the appliance trace, the accelerator trace archive does not include it. |
APARs fixed with maintenance level 7.5.4
| APAR # | APAR description | Comments |
| PH27585 | When enabling incremental updates for Integrated Synchronization, options asking to specify 'Y/N' are ending with garbled characters | #InSync |
| PH29689 | The 'Rows returned' value as shown in IBM DB2 Analytics Accelerator Studio for a query processing an AOT may be extraordinary (unreasonably) high. |
|
| PH29742 | Loading tables to the accelerator may end prematurely with message "SQL0954C Not enough storage is available in the application heap to process statement" | |
| PH30858 | An update of IBM DB2 Analytics Accelerator for z/OS 7.5 on IBM Z to maintenance level 7.5.3 fails if the accelerator environment is GDPS-enabled. | Applies only to IDAA V7 on IBM Z |
| PH31078 | After upgrading the accelerator on IBM Z to maintenance level 7.5.3 a restart can fail. | Applies only to IDAA V7 on IBM Z |
| PH31541 | The upgrade to maintenance level 7.5.3 is failing: the main Web GUI tab "Accelerator" is not responding and does not display the status. | Applies only to IDAA V7 on IBM Z |
| PH32431 | CPU cost value (for query execution) disappeared in IBM DB2 Analytics Accelerator Studio | |
| PH33421 | Integrated Synchronization commands can fail due to replication state 'PAUSED'
and InSync goes into error state (long running UR causes Java Heap OOM) |
#InSync |
| PH33491 | Using Integrated Synchronization replication latency may not be updated for a longer time. | #InSync |
| PH33835 | A load request can time out due to issues with the underlying 'create table'-request | |
| PH34322 | The accelerator trace may be flooded with messages containing 'getSubscriptionName()' but not specifying a subscription |
APARs fixed with maintenance level 7.5.3
| APAR # | APAR description | Comments |
| PH25997 | Definition of multiple IP addresses in the activation profile for the SSC LPAR currently is not supported | Applies only to IDAA V7 on IBM Z |
| PH27055 | When upgrading IDAA V7 maintenance level 7.5.0.x to 7.5.2 the installation log of the Apply process may show incorrect data | |
| PH27420 | When stopping the accelerator, for example in the context of an upgrade of the accelerator, a query may return incorrect data | |
| PH27626 | A full reload may end successfully although none of the data to be loaded were transferred to the accelerator | |
| PH27644 | IBM Db2 Analytics Accelerator Studio does not execute 'Alter Keys' if the keys are not changed |
Requires IBM Db2 Analytics Accelerator Studio 7.5.3 |
| PH27646 | IBM Db2 Analytics Accelerator Studio does not show the progress indicator correctly when altering or setting an organizing key | Requires JCC driver 4.27.26 |
| PH27771 | Stored Procedure SYSPROC.ACCEL_ADD_TABLES fails with assertion: an assertion '( MCCSID.GETVALUE() > 0 )' failed | PTF UI72071 |
| PH27773 | Stored Procedure SYSPROC.ACCEL_GET_TABLES_INFO fails with message AQT10402E: Error 'Invalid character encountered' | PTF UI72071 |
| PH27984 | When upgrading IDAA on IBM Z maintenance level 7.5.2(.1) to a higher level, an 'Error' message box will be displayed erroneously | Applies only to IDAA V7 on IBM Z |
| PH28293 | When running a load using stored procedure ACCEL_LOAD_TABLES, the load request may hang in Db2 warehouse. | |
| PH28404 | Using 'Reboot all appliance nodes' function on the accelerator console fails with an error message | |
| PH28723 | MSG DSNX881I ... Magneto Issue: ID 1384 Severity: MAJOR console_alerts ...Failed to collect status from resource manager | |
| PH28727 | IBM Db2 Analytics Accelerator Studio, Query monitoring: using "Show EXPLAIN details" can fail with messages AQT20001W and AQT20125E | |
| PH29288 | If load operations lead to a deadlock situation, the accelerator restarts itself. | |
| PH29409 | A query may end with message 'SQL0901N The SQL statement or command failed because of a database system error. SQLSTATE=58004' | |
| PH29940 | Integrated Synchronization stops and cannot be started again using the administration console. |
#InSync |
| PH30066 | Message DSNX881I "...901 Storage utilization above threshold ...SW://FS.SDA8/HADOMAIN1.NODE..." may occur in DB2MSTR | Applies only to IDAA V7 on IIAS |
| PH30147 | Upon or after saving an IDAA trace the system may go into a general hang state due to a 'File system full' condition | |
| PH30260 | Replication using Integrated Synchronization and involving members of a data sharing group may lead to incorrect data on the accelerator | #InSync |
| PH31550 | When using Integrated Synchronization for replication between Db2z and the accelerator, users may see an error message such as "X rows parsed, but apply changed Y rows. Table Z is inconsistent, set table state to ERROR." |
#InSync |
APARs fixed with maintenance level 7.5.2.2
| APAR # | APAR description | Comments |
| PH28026 | Using IBM DB2 Analytics Accelerator Studio a refresh of the accelerator view may lead to error message mentioning invalid XML | |
| PH28029 | A query may deliver wrong results if it contains a scalar subquery and 'FETCH FIRST 1 ROW' | |
| PH28030 | Queries may be running extremely slow if parallel calls of SP ACCEL_GET_QUERY_DETAILS2 hit the 15 minute processing timeout of EXPLAIN |
APARs fixed with maintenance level 7.5.2.1
| APAR # | APAR description | Comments |
| PH27523 | Initial installation of IBM DB2 ANALYTICS ACCELERATOR ON IBM Z with a multi-node setup can fail | Applies only to IDAA V7 on IBM Z |
| PH27593 | Accelerator tasks, for example LOAD, fail due to a 'Drop Table' statement hanging in the database engine | |
| PH27594 | Query fails when LENGTH function return NEGATIVE or 0; the accelerator database engine crashes subsequently |
|
| PH27596 | Long-running queries may finally fail with SQLCODE -904 | |
| PH27609 | A query requiring spill-to-disk for the result set may be hanging without the possibility to cancel it. | |
| PH27683 | IBM Integrated Synchronization (InSync): replication suddenly goes into state 'Error'. Attempts to restart replication by InSnyc are not successful and lead to message AQT20126E. | #InSync |
APARs fixed with maintenance level 7.5.2
| APAR # | APAR description | Comments |
| PH24437 | Special register values returned by Stored Procedure ACCEL_GET_QUERIES2 are truncated |
|
| PH25111 | In rare cases customers may experience repeated restarts of Integrated Synchronization which may suspend the subscription | |
| PH25253 | A load of a table on the accelerator failed with error message "Target table status conflict with detected LOAD status" |
|
| PH25302 | When enabling replication after initial load of a table, REORGs following subsequent loads to not remove old table versions | |
| PH25452 | Replication based on Integrated Synchronization may enter the 'ERROR' state followed by an 'OUT OF DISK SPACE' condition. | #InSync |
| PH25560 | Performance degradation may occur with queries on HPSS tables. Distribution/organizing keys are not applied to archived tables. | |
| PH25995 | SSC root disk may be filled up with diagnostic data | Applies only to IDAA V7 on IBM Z |
| PH25998 | Definitions of static network routes (attribute static_routes in the Accelerator configuration file) are currently not applied for bonding networks. | Applies only to IDAA V7 on IBM Z |
| PH26790 | Load tasks may be hanging after a failure in the corresponding stored procedure and cannot be cancelled. | |
| PH26946 | During operation of IDAA 7.5 or during an upgrade the message "201: Unhealthy component detected" may occur. | Applies only to IDAA V7 on IIAS |
| PH27055 | When upgrading IDAA V7 maintenance level 7.5.0.x to 7.5.2, the installation log of the apply process may show incorrect data | Applies only to IDAA V7 on IIAS |
| PH27097 | Inserting or updating of VARCHAR, VARGRAPHIC, or VARBINARY columns may result in a corruption on disk | |
| PH27635 | Cancelling of a load may lead to unintentional restart of the IDAA server. All currently running queries and loads will be aborted. |
|
| PH27793 | If Integrated Synchronization is forced to restart, an error message like "2 rows parsed, but apply changed 4 rows" may occur. | #InSync |
APARs fixed with maintenance level 7.5.1
| APAR # | APAR description | Comments |
| PH20898 | A query may end with SQLCODE -904 and resource name -1656 | |
| PH21932 | With customization parameter ENABLE_COPY_TABLE_STATISTICS set to TRUE users may see warning messages in IBM DB2 Analytics Accelerator Studio | |
| PH23578 | With customization parameter ENABLE_COPY_TABLE_STATISTICS set to TRUE a reload of a table may result in a restart of the accelerator | |
| PH23995 | (Re-)loading data to the accelerator may end with message AQT10420E or AQT10421E. |
|
| PH24432 |
Cancelling a long-running query is not successful.
Message "DSNX881I ...2001 W SQL statement with task ID nnnnnnn is running"
|
|
| PH24441 | Load requests to the accelerator are failing with SQLCODE 466, SQLSTATE 0100C and are accompanied by message AQT10050E | |
| PH24448 | Load tasks are hanging. Cancellation of those tasks using IBM Db2 Analytics Accelerator Studio won't work |
|
| PH24629 | When upgrading IDAA V7 maintenance level 7.5.0.x to 7.5.1, the installation log of the apply process may show incorrect data | Applies only to IDAA V7 on IIAS |
APARs fixed with maintenance level 7.5.0.2
| APAR # | APAR description | Comments |
| PH23674 | IBM DB2 Analytics Accelerator on IBM Z (maintenance level 7.5.0 or 7.5.0.1): Restart fails three months after initial installation | Applies only to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.5.0.1
| APAR # | APAR description | Comments |
| PH20394 | Using IDAA on IBM Z adding of DASDs to the accelerator using the JSON configuration file can fail | Only applies to IDAA V7 on IBM Z |
| PH20802 | Using Analytics Accelerator Studio the replication status of a subscription shows 'ERROR' without any preceding replication issues | Also known as CDC File handle issue - JR61803 |
| PH21308 | Stored Procedure SYSPROC.ACCEL_ARCHIVE_TABLES fails with error AQT10200E | |
| PH21562 | Default value for DB2WH configuration parameter AUTO_STMT_STATS is OFF |
APARs fixed with release 7.5
| APAR # | APAR description | Comments |
| PH19810 | USING IDAA V7 ON IBM Z, MAINTENANCE LEVEL 7.1.9, THE GDPS SERVER LOOKS OUT FOR A SYSTEM NAMED "SINGLE" WHICH IS NOT FOUND | Only applies to IDAA V7 on IBM Z |
APARs fixed with maintenance level 7.1.9.1
| APAR # | APAR description | Comments |
| PH19670 | UPGRADING IDAA V7.1 ON IIAS TO MAINTENANCE LEVEL '7.1.9' MAY BRING THE SYSTEM DOWN | Only applies to IDAA V7 on IIAS |
APARs fixed with maintenance level 7.1.9
| APAR # | APAR description | Comments |
| PH15516 | OUT OF THE SUDDEN REPLICATION GOES INTO STATE 'ERROR' AND MAY BE ACCOMPANIED BY MESSAGE CHC6503E. | |
| PH16538 | IDAA V7 CALL-HOME FUNCTION ON IIAS: TESTING OF THE CALL-HOME CONNECTIVITY INDICATES A FAILURE. | |
| PH17974 | AN ACCELERATOR MAY BECOME TEMPORARILY OFFLINE WHILE PREMATURELY SWITCHING INTO SYSTEM STATE 'UNKNOWN'. |
APARs fixed with maintenance level 7.1.8
| APAR # | APAR description | Comments |
| PH12496 | MULTIPLE ROW INSERT LEADS TO SQLCODE -254 (SQLSTATE 22530) | |
| PH12631 | IDAA V7 CUSTOMERS USING IIAS MAY RECEIVE MESSAGE "DSNX881I .. MAGNETO ISSUE ...TITLE: FAILED TO COLLECT STATUS" | |
| PH12632 | MESSAGE "DSNX881I ...MAGNETO ISSUE ....TITLE: STATEMENT PERFORMANCE ISSUE" APPEARS IN DB2MSTR | |
| PH12634 | A QUERY USING STRING MANIPULATION FUNCTION "UPPER" CAN FAIL WITH SQLCODE -904 (SQLSTATE 57011) | |
| PH12804 | LOADING A TABLE USING IDAA LOADER V2.1 MAY RESULT IN AN ERROR INDICATING "HLPPIPE API ERROR" | |
| PH13004 | USING DB2 12 WITH DSNHDECP PARM APPLCOMPAT SET TO V12R1M501 OR HIGHER MAY CAUSE ENABLING OF REPLICATION TO FAIL | |
| PH13804 | IDAA LOAD TABLES PERFORMANCE DECREASE AFTER INSTALL OF IDAA 7.1.8 | Fixed with 7.1.8.1 |
| PH14156 | STATUS OF REPLICATED TABLES CHANGES TO 'SUSPENDED' IN IBM DB2 ANALYTICS ACCELERATOR STUDIO | Fixed with 7.1.8.2 |
| PH15241 | ACCELERATOR BACKEND DATABASE MAY RESTART EVERY 10 MINUTES: ALSO ACCELERATOR STATUS FLIPS BETWEEN "ONLINE" & "MAINTENANCE" | Fixed with 7.1.8.3 |
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS4LQ8","label":"Db2 Analytics Accelerator for z\/OS"},"ARM Category":[{"code":"a8m0z0000000775AAA","label":"Db2 related products and functions-\u003EDb2 Analytics Accelerator for z\/OS"},{"code":"a8m0z000000072oAAA","label":"Install and Migrate"},{"code":"a8m0z000000073XAAQ","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
26 April 2024
UID
ibm10958189