IQ UTILITIES Statement

Starts a cache monitor that collects buffer cache statistics.

Quick Links:

Go to Parameters

Go to Examples

Go to Usage

Go to Standards

Go to Permissions

Syntax

IQ UTILITIESMAIN | PRIVATE }
   [ INTO ] table-nameSTART MONITOR ['monitor-options']
   | STOP MONITOR }

monitor-options-summary 
   | {-append | -truncate } -bufalloc 
   | -cache 
   | -cache_by_type 
   | -contention 
   | -debug 
   | -file_suffix suffix
   | -io 
   | -interval seconds 
   | -threads }...

Parameters

(back to top)

Examples

(back to top)

Usage

(back to top)

Issue separate commands to monitor each buffer cache. Keep each sessions open while the monitor collects results; a monitor run stops when you close its connection. A connection can run up to a maximum of two monitor runs, one for the main and one for the temp buffer cache.

To control the directory placement of monitor output files, set the MONITOR_OUTPUT_DIRECTORY option. If this option is not set, the monitor sends output to the same directory as the database. All monitor output files are used for the duration of the monitor runs. They remain after a monitor run has stopped.

Either declare a temporary table for use in monitoring, or create a permanent dummy table when you create a new database, before creating any multiplex query servers. These solutions avoid DDL changes, so that data stays up on query servers during production runs.

On UNIX-like operating systems, you can watch monitor output as queries are running. For example:

Starting the monitor with this command:
iq utilities main into monitor_tab 
start monitor “-cache -interval 2 -file_suffix iqmon”
sends the output to an ASCII file with the name dbname.conn#-[main|temp]-iqmon. So, for the iqdemo database, the buffer monitor would send the results to iqdemo.2-main-iqmon
The buffer cache monitor writes the results of each run to these logs:
  • dbname.connection#-main-iqmon //for main buffer cache results

  • dbname.connection#-temp-iqmon //for temp buffer cache results

The prefix dbname.connection# represents your database name and connection number. If you see more than one connection number and are uncertain which is yours, you can run the Catalog stored procedure sa_conn_info. This procedure displays the connection number, user ID, and other information for each active connection to the database. The -file_suffic clause to change the suffix iqmon to a suffix of your choice. Use a text editor to display or print a file. Running the monitor again from the same database and connection number, overwrites the previous results. To save the results of a monitor run, copy the file to another location or use the -append option.

Standards

(back to top)

  • SQL—Vendor extension to ISO/ANSI SQL grammar.
  • SAP Sybase Database product—Not supported in Adaptive Server.

Permissions

(back to top)

None