APAR status
Closed as documentation error.
Error description
If data is inserted into in a replicated table, IBM DB2 IBM Db2 Analytics Accelerator Studio changes the status of that table to 'SUSPENDED'. Customers are affected if they upgraded to maintenance level 7.1.8 and have been using replication on their previous maintenance level of V7.1. Not affected are those customers who are starting - to use V7.1 on maintenance level 7.1.8 - to create subscriptions on maintenance level 7.1.8. . The z/OS SYSLOG shows: Action: Review the contents of the log files in /head/dwa/var/dwa-iu-refresh-loader/<SUBSCRIPTIONNAME>/load/err/ for more details on the cause of this error. . Symptoms: A SQL exception has occurred. The SQL error code is '-970'. The SQL state is: 55009. The error message DSNX881I -DBZ1 20 E 1588 (2019-06-27 15:27:53 UTC) 088 ... DB2 SQL Error: SQLCODE=-970, SQLSTATE=55009, SQLERRMC=null, DRIVER=4.26.1015 Originator: com.datamirror.ts.target.apply.bulkapply.ExecuteBulkApplyStateme ntJob
Local fix
The upgrade routine applies directory access permissions which are too strict. This prevents replication from creating temporary files for subscriptions that existed already before the upgrade. To correct this, IBM support has to change the directory permissions during a webex session. Corrective action: "find /head/dwa/var/dwa-iu-refresh-loader -type d -exec chmod 775 äü Ö;" and "find /head/dwa/var/dwa-iu-refresh-loader -type f -exec chmod 664 äü Ö;" in dashDB container. . The issue will be fixed with maintenance level 7.1.8.2.
Problem summary
The issue descibed was fixed in the IDAA V7 accelerator server. The fix became part of IDAA V7 maintenance level 7.1.8.2.
Problem conclusion
Upgrade your IDAA V7 maintenance level to 7.1.8.2 or higher.
Temporary fix
Comments
APAR Information
APAR number
PH14156
Reported component name
ANYTCS ACCLTR Z
Reported component ID
5697DA700
Reported release
710
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-07-04
Closed date
2020-05-28
Last modified date
2020-05-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
29 May 2020