MONITOR_OUTPUT_DIRECTORY Option

String.

Same directory as the database.

Option can be set at the database (PUBLIC) or user level. At the database level, the value becomes the default for any new user, but has no impact on existing users. At the user level, overrides the PUBLIC value for that user only. No system privilege is required to set option for self. System privilege is required to set at database level or at user level for any user other than self.

Requires the SET ANY SYSTEM OPTION system privilege to set this option. Can be set temporary for an individual connection or for the PUBLIC role. Takes effect immediately.

MONITOR_OUTPUT_DIRECTORY controls the directory in which the IQ monitor output files are created, regardless of what is being monitored or what monitor mode is used. The dummy table used to start the monitor can be either a temporary or a permanent table. The directory can be on any physical machine.

All monitor output files are used for the duration of the monitor runs, which cannot exceed the lifetime of the connection. The output file still exists after the monitor run stops. A connection can run up to two performance monitors simultaneously, one for main buffer cache and one for temp buffer cache. A connection can run a monitor any number of times, successively.

The DBA can use the PUBLIC setting to place all monitor output in the same directory, or set different directories for individual users.

This example shows how you could declare a temporary table for monitor output, set its location, and then have the monitor start sending files to that location for the main and temp buffer caches.

declare local temporary table dummy_monitor (dummy_column integer)

set option Monitor_Output_Directory = "/tmp"
iq utilities main into dummy_monitor start monitor '-debug -interval 2'

set option Monitor_Output_Directory = "tmp/"

iq utilities private into dummy_monitor start monitor '-debug -interval 2'