PH57670: MESSAGE "DSNX881I SYSTEM WENT FROM STATE UNKNOWN TO ONLINE" APPEARS IN DB2MSTR

APAR status

• Closed as documentation error.

Error description

• Customers using Accelerator the maintenance levels 7.5.11 or
  7.5.11.1 can face the following sequence of messages:
  - DSNX870I... ACCELERATOR ........ IS NOT ONLINE
  - DSNX881I... System went from state 'UNKNOWN' to 'ONLINE'
  Usually the status of the accelerator changes to ONLINE in less
  than a minute.
  
  The reason for this behavior can be a server crash and a
  following restart which occur under the following conditions:
  - Concurrent queries from user applications are running on the
    accelerator.
  - Two or more cancel query task operations are executed at
    nearly the same time.
  The probability of this occurrence seems to increase if
  - the accelerator customization parameters
    QUERY_RESULT_FETCH_MODE and QUERY_RESULTS_SPILL_HEURISTIC
    either have not been set explicitly (meaning: no values have
    been assigned to them in configuration file dwa.server.conf)
  or
  - the accelerator customization parameter
    QUERY_RESULT_FETCH_MODE has been set to
    'ASYNCHRONOUS_WITH_SPILL_TO_DISK'.
  
  The issue will be fixed with Accelerator maintenance level
  7.5.12.
  
  Additional keywords:
  TS014463144 SERVERCRASH #idaa7512 QUERY_RESULT_FETCH_MODE
  ASYNCHRONOUS_WITH_SPILL_TO_DISK
  DSNX870I DSNX881I UNKNOWN ONLINE
  GH/.../Customer-Cases/issues/598
  

Local fix

• Option 1:
  Contact IBM support to get the following settings applied in
  accelerator configuration file dwa.server.conf:
  QUERY_RESULT_FETCH_MODE = LEGACY and
  QUERY_RESULTS_SPILL_HEURISTIC = DEFAULT
  Then restart the accelerator server using the accelerator
  administration console.
  
  Option 2:
  Cancel only one query task at a time, wait until the
  cancellation completes before cancelling the next query task.
  

Problem summary

• Problem Summary:
  See Error Description.
  
  Users Affected:
  Users of Db2 Analytics Accelerator having asynchronous fetching
  of result sets enabled (either by default with 7.5.11 or
  7.5.11.x or by an explicit enabling in a previous maintenance
  level).
  
  Problem Scenario:
  See Error Description.
  
  Problem Symptoms:
  See Error Description.
  

Problem conclusion

• The issue has been fixed with Accelerator maintenance level
  7.5.12 by changing the default behavior from asynchronous result
  set fetching back to the legacy result set fetching mode.
  

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:

Fix information

Applicable component levels