The onstat -O option

The onstat -O option displays information about the staging-area blobspace and the Optical Subsystem memory cache. The totals shown in the display accumulate from session to session. The database server resets the totals to 0 only when you run onstat -z.

For an example of onstat -O output, see information about the onstat utility in the HCL OneDB™ Administrator's Reference.

The first section of the display describes the following system-cache totals information.

Column: Description
size: Size specified in the OPCACHEMAX configuration parameter
alloc: Number of 1 KB pieces that the database server allocated to the cache
avail: Portion of alloc (in KB) not used
number: Number of simple large objects that the database server successfully put into the cache without overflowing
kbytes: Number of KB of the simple large objects that the database server put into the cache without overflowing
number: Number of simple large objects that the database server wrote to the staging-area blobspace
kbytes: Number of KB of simple large objects that the database server wrote to the staging-area blobspace

Although the size output indicates the amount of memory that is specified in the configuration parameter OPCACHEMAX, the database server does not allocate memory to OPCACHEMAX until necessary. Therefore, the alloc output reflects only the number of 1 KB pieces of the largest simple large object that has been processed. When the values in the alloc and avail output are equal, the cache is empty.

The second section of the display describes the following user-cache totals information.

Column: Description
SID: Session ID for the user
user: User ID of the client
size: Size specified in the INFORMIXOPCACHE environment variable, if set
If you do not set the INFORMIXOPCACHE environment variable, the database server uses the size that you specify in the configuration parameter OPCACHEMAX.
number: Number of simple large objects that the database server put into cache without overflowing
kbytes: Number of KB of simple large objects that the database server put into the cache without overflowing
number: Number of simple large objects that the database server wrote to the staging-area blobspace
kbytes: Size of the simple large objects (in KB) that the database server wrote to the staging-area blobspace