search cancel

DB2 receiving DSNW133I -xxxxx DSNWVOPX - TRACE DATA LOST, OP1 NOT ACCESSIBLE RC=08

book

Article ID: 54196

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

User is seeing a recent significant increase in DB2 activity and has noticed they are now getting the following DB2 messages -

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

Solution:

The dispatching priority specified for the Insight data collector must be set higher than DB2 or any connections to the DB2 for CA Insight Performance Monitor for DB2 for z/OS.

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

Environment

Release:
Component: IDB2