Operations database

The operations database stores the monitoring data that is displayed by the IBM InfoSphere® DataStage® and QualityStage® Operations Console.

The operations database holds information about InfoSphere DataStage jobs that are running, or have been run, on one or more InfoSphere Information Server engine systems. The operations database also holds information about how system resources are used over time on those engine systems.

The Operations Console does not display all the information that is stored in the operations database. In particular, the contents of the JobRunStage, JobRunLink, and DataLocator tables, which are only populated if you set the MonitorLinks=1 configuration option, are not currently used by the Operations Console. Also, more detailed information about system resource usage is captured than is currently displayed in the Operations Console.

You must choose which database that you want to include the operations database:

Metadata repository database:
- For performance reasons, use the metadata repository database for production systems only after careful consideration.
- If the operations database schema does not exist in the metadata repository database, run the scripts that create the operations database schema, and set the configuration connection properties to point to it.
- If the operations database schema exists in the metadata repository database, configure the engine to point to it.
Another database that is specific to this InfoSphere Information Server engine:
- Run the scripts that create the operations database schema.
- Configure the engine to point to it.
Another database that is shared between InfoSphere Information Server engines:
- Collect details of where the existing schema is located, and configure the engine to point to it.