Db2 receiving DSNW133I -xxxxx DSNWVOPX - TRACE DATA LOST OP1 NOT ACCESSIBLE RC=08 related to Sysview for Db2 processing

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Noted a recent significant increase in Db2 activity and noticed following Db2 messages related to Sysview for Db2 for z/OS (IDB2) processing:

DSNW133I -xxxxx DSNWVOPX - TRACE DATA LOST, OP1 NOT ACCESSIBLE RC=08
DSNW123I -xxxxx DSNWVOPX - TRACE RECORDING HAS BEEN RESUMED ON OP1

Resolution

The dispatching priority specified for the IDB2 Data Collector must be set higher than Db2 or any connections to IDB2.

After IDB2 has started it's trace requests, Db2 collects and buffers the information as it occurs. IDB2 can then issue a READA request to move the Db2 buffered
data into the IDB2 Data Collector address space for reporting. Data loss occurs when the Db2 buffer fills before IDB2 can obtain the data.
Db2 does not wait for the buffers to be emptied but instead informs IDB2 on the next READA request the data has been lost.