Starting Db2 traces

Because the OMEGAMON Collector analyzes data for online monitoring collected by your Db2, the Db2 monitor trace must be started.

Before you begin

Ensure the following requirements are met:

MONITOR1 privilege to access the collected data, or
MONITOR2 privilege to access the collected data including sensitive data such as SQL statements

In most cases the Db2 traces are automatically started by the OMEGAMON Collector for each subsystem that is monitored. However, if they were not started for a Db2 subsystem, an error message is written to the OMEGAMON Collector log. Check the server log for the following message:
```
FPEV0128S db2ssid CONNECT TO DB2 FAILED. MONITOR TRACE IS NOT STARTED
```
where db2ssid is the Db2 subsystem ID for which the monitor traces are not started.
If you receive the message above, you need to start the Db2 traces manually by doing the following:
1. Stop the OMEGAMON Collector started task:
```
P IBMO2
```
2. Start the DB2 MONITOR trace using one of the following commands:
  - For local scope:
```
START TRACE(MON) CLASS(*)
```
  - For data sharing scope:
```
START TRACE(MON) CLASS(*) SCOPE(GROUP)
```
  Perform the command for each Db2 subsystem that caused the error message FPEV0128S. The command can be issued from a z/OS console, a DSN session, or a DB2I panel while Db2 is running.
Restart the OMEGAMON Collector started task with the following command:
```
S IBMO2
```
Optionally, you can start/stop all configured products by starting the composite IBMSTRT/IBMSTOP job in the SYS1.PROCLIB library. This job includes /START &&stc_name commands for all configured products. These jobs are copied in the step Copying started task definitions.