PH71861: CONNECTION IS NOT AVAILABLE FOR DB2ZAI FOR MANY CURRENT DEPLOYMENTS AND DEPLOYMENT ENHANCEMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Connection is not available for Db2ZAI for many current
  deployments and deployment enhancement
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2ZAI Customers.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR addresses the problems        *
  *                      described in the Problem summary.       *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  -When many deploy operations are scheduled concurrently, each
  operation opens its own database connection without throttling,
  which can exhaust the connection pool and result in
  "Connection is not available" errors.  In severe cases the
  Db2ZAI UI becomes blank and unresponsive until the Db2ZAI
  started tasks are restarted.
  
  -When the migration script inserts default regression
  resolution schedulers, the DB2 installation user ID is used
  instead of the Db2ZAI scheduler ID, causing the scheduler to
  fail with ERRORCODE=-4214 (connection authorization failure).
  
  -During migration, the script that inserts the default
  regression resolution schedulers may encode curly brace
  characters incorrectly. As a result, JSON parsing fails,
  causing excessive error messages to be written to the log.
  
  -A synchronization defect between performance history tables
  DSN_ML_SQL_PERF_HIST and DSN_ML_SQL_PERF_SUMMARY_BY_APID
  causes statements to be missing from the Aggregate AP list
  in the Db2ZAI UI.
  
  -Files are not tagged with ISO8859-1 encoding.
  
  -During SMP/E APPLY, the installation shell script fails
  with GIM39302E.
  
  -Scheduler and throttle-queue table rows stored with a
  non-Unicode encoding cause JSON parse exceptions during
  explore and system assessment processing.
  
  
  Db2ZAI SQL optimization enhancements:
  
  -Deploy operations are now routed through a throttle queue
  to limit the number of concurrent connections.
  
  -A new auto-deploy option allows explore recommendations to
  be deployed automatically without a separately initiated
  deploy process.
  
  - The process queue table for SQL Optimization now displays an
  error details link on rows that have errors. Clicking the link
  opens a pop-up modal with the full error details.
  

Problem conclusion

• This APAR resolves the problems described above.
  
  Additional keyword:
  
  DB2ZAIV1R6/K
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UO09295

Modules/Macros

• COYAKIRA COYIPC02 COYIRC02 COYMAIN  COYMPCM1 COYMPCM2 COYMPCR1
  COYMTEXT COYNOD02 COYREADM COYSHELL
  

Fix information

• Fixed component name

  DB2 AI FOR Z/OS

• Fixed component ID

  5698CGN00

Applicable component levels

• R160 PSY UO09295

     UP26/09/14 P F609

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.