![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
The onstat, oninit, and onmode utilities
Major components of the server
IBM Informix Dynamic Server (IDS) consists of three major components, namely the oninit processes (virtual processors), the shared memory segments, and the disk space storage. Upon starting the server, an oninit process reads the necessary information from the configuration file and disk before creating the shared memory segments. The required virtual processors are then started, as specified in the configuration file.
Figure 1 shows the virtual processes interacting with the shared memory segments and disk susbsystem. Besides the buffer pool, which contains the data or index information, a large part of shared memory contains control data, which the virtual processes (or threads) use to coordinate and execute their activities. As for the disk subsystem, it contains the persistent information, which the virtual processes will read and write from. Persistent information is data that is not lost even after IDS has shut down .
Figure 1. Major component of IDS
IDS has four principle operating modes:
In this mode, the server is not running and no shared memory segments
or virtual processors are created. Using the following
onstat command, the below output will be
shown if the server is offline:
$ onstat - shared memory not initialized for INFORMIXSERVER 'ol_115fc3' |
In quiescent mode, the shared memory is initialized and the virtual processors are started. Administration that does not require SQL connection is allowed in this mode. No user connection is allowed in this mode.
Issuing the following onstat command will
show the below output when the server is in this mode:
$ onstat - IBM Informix Dynamic Server Version 11.50.FC3 -- Quiescent -- Up 00:21:42 -- 149504 Kbytes |
Any type of administration activity that requires SQL should use this mode. This mode is identical to online mode, except that only admin users can connect to the server. Virtual processors and shared memory is initialized.
In this mode, only user informix and DBSA group can connect to the
server by default. To enable other users to also connect, set the
onconfig parameter
ADMIN_USER_MODE_WITH_DBSA to 1 with the
permitted user listed in the configuration parameter
ADMIN_MODE_USERS. For example, the
configuration can look like this:
ADMIN_MODE_USERS jgyap, kohcf, jagena, nopavis |
At this mode, sending onstat will receive
the following output:
$ onstat - IBM Informix Dynamic Server Version 11.50.FC3 -- Single-User -- Up 00:23:07--149504 Kbytes |
This is the normal operating mode in which authorized activity of the various users is carried out. Virtual processors and shared memory is initialized.
Again, onstat will show you the online
mode:
$ onstat - IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 00:41:57 -- 149504 Kbytes |
It is possible for the server to be in a transitory mode, such as recovery mode and shutdown mode. Recovery mode is when the server is changing from offline to quiescent or online. Shutdown mode is when the server is going from online to quiescent.
In Microsoft® Windows®, the server runs as a service. Therefore, the server can be started (online mode) or stopped (offline mode) using the Services Tool accessible from your control panel or NET command. For example, you can issue the following command to start the server with the service name ol_115fc3:
NET start ol_115fc3 |
To stop the service:
NET stop ol_115fc3 |
The creation of shared memory segment is sometimes called shared memory initialization. There is another type of initialization that is called disk space initialization, where the initial chunk of the root dbspace is initialized in an internal format.
Disk space initialization is required to be done when a new instance is created. Use the following commands to do disk space initialization:
UNIX®:
oinit -i |
Windows:
starts dbservername -i |
Or use the Instance Manager program to create the new instance.
To skip the requirement to respond yes, use the
y option:
UNIX:
oninit -iy |
Windows:
starts dbservername -iy |
To get a verbose trace during the disk initialization, use the
v option:
UNIX:
oninit -ivy |
Windows:
starts dbservername -ivy |
To let the engine stay in quiescent mode after disk initialization,
add the s option:
UNIX:
oninit -ivys |
Windows:
starts dbservername -ivys |
The server will automatically do the shared memory initialization as well and bring the engine online during disk initialization.
Note: If disk initialization is done on an existing instance, all the data in the old instance will be lost.
When the engine is in offline mode, use the oninit utility to bring up the server to the desired mode. When it is no in offline mode, use the onmode utility.
Table 1 shows the oninit or onmode utility and its option to use in order to set the server to a desired mode.
Table 1. Mode management using oninit and onmode
| Target mode | Original mode: Offline | Original mode: Not offline |
|---|---|---|
| Offline | n/a | onmode -k |
| Quiescent | oninit -s | onmode -s or onmode -u |
| Administrative | oninit -j -U | onmode -j -U |
| Online | oninit | onmode -m |
Therefore, if the desired target mode is quiescent mode, and current mode of the server is offline, then issue the following command:
oninit -s |
However, if the engine is not in offline mode (It's either in quiescent or administrative mode), then issue one of the following two options:
For graceful shutdown:
onmode -s |
Fore Immediate shutdown:
onmode -u |
In graceful shutdown, existing user sessions are allowed to continue execution, but new connections are not allowed. However, in immediate shutdown, current sessions are terminated immediately and transactions are rolled back.
Use the -U option to allow users other than
informix and those belonging to DBSA group to connect to the server
when it is in administrative mode. For example, the following command
allows users jgyap, nopavis, and chinth to connect to the server when
it is in administrative mode:
onmode -j -U jgyap nopavis chinth |
To remove the users, issue this command:
onmode -U " " |
During start up, the server cleans up temporary tables that are left over from the last shutdown. To instruct the server not to carry out this clean up, you can use the following command:
oninit -p |
The server provides replication facilities such as HDR and Enterprise Replication (described in Part 9 of this series). To start up the server without initializing the HDR and Enterprise Replication, use the following command:
oninit -D |
To start the HDR server in standard mode, use this command:
oninit -S |
Use the following command to get the detail about the oninit itself:
Listing 1. oninit detail
$ oninit -version Program Name: oninit Build Version: 11.50.FC3 Build Number: N091 Build Host: apris Build OS: SunOS-sparc 5.9 Build Date: Tue Oct 28 00:17:11 CDT 2008 GLS Version: glslib-4.50.FC3 |
Besides using the onmode utility to change the server mode when it is not offline, the onmode utility has a number of others functions. Let's explore a few.
The server provides the capability to dynamically change some of the configuration. For example, the limit of the maximum number of sessions can be changed with this command:
$ onmode -wm LIMITNUMSESSIONS=200 Value of LIMITNUMSESSIONS has been changed to 200. |
The -wm option changes the memory content
but not the configuration file. This change will therefore be lost
upon reboot of the server.
To change it more permanently, use the following option:
$ onmode -wf LIMITNUMSESSIONS=200 Value of LIMITNUMSESSIONS has been changed to 200. |
Another interesting function that onmode utility can do is to dynamically turn on the SQL explain. For example, to turn on SQL explain for session 201, issue the following command:
onmode -Y 201 1 |
While session 201 is run, onstat -m shows
the location where the sqexplain file is located:
Listing 2.
onstat -m
output$ onstat -m IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 17 days 08:06:25 -- 522240 Kbytes Message Log File: /usr2/support/products/sr_11.50.FC3/tmp/online.log 10:55:58 Checkpoint Completed: duration was 0 seconds. 10:55:58 Fri Aug 7 - loguniq 21, logpos 0xe1f044, timestamp: 0x1c12d1 Interval: 3742 10:55:58 Maximum server connections 1 10:55:58 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2 , Llog used 1 11:11:01 Checkpoint Completed: duration was 0 seconds. 11:11:01 Fri Aug 7 - loguniq 21, logpos 0xe20044, timestamp: 0x1c12de Interval: 3743 11:11:01 Maximum server connections 1 11:11:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2 , Llog used 1 11:26:04 Checkpoint Completed: duration was 0 seconds. 11:26:04 Fri Aug 7 - loguniq 21, logpos 0xe27018, timestamp: 0x1c1355 Interval: 3744 11:26:04 Maximum server connections 1 11:26:04 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 23, Llog used 7 11:30:46 Explain file for session 201:/usr2/as_support/jgyap/sqexplain.out.201 In the sqexplain.out.201 file, you will able to check the query plain executed by the session 201. |
To turn off the SQL explain, issue the following command:
onmode -Y 201 0 |
IDS also allows the dynamic addition and removal of a virtual processor. To add two more cpu virtual processors, you can use the following command:
onmode -p +2 cpu |
Check the online.log to see that the operation is successfully executed:
Listing 3. Checking the online.log
$ onstat -m IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 17 days 22:30:38 -- 522240 Kbytes Message Log File: /usr2/support/products/sr_11.50.FC3/tmp/online.log 01:23:50 Checkpoint Completed: duration was 0 seconds. 01:23:50 Sat Aug 8 - loguniq 22, logpos 0xc34018, timestamp: 0x1c9916 Interval: 3808 01:23:50 Maximum server connections 1 01:23:50 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 26, Llog used 8 01:28:50 Checkpoint Completed: duration was 0 seconds. 01:28:50 Sat Aug 8 - loguniq 22, logpos 0xc35044, timestamp: 0x1c991f Interval: 3809 01:28:50 Maximum server connections 1 01:28:50 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2, Llog used 1 01:43:53 Checkpoint Completed: duration was 0 seconds. 01:43:53 Sat Aug 8 - loguniq 22, logpos 0xc36044, timestamp: 0x1c992b Interval: 3810 01:43:53 Maximum server connections 1 01:43:53 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2, Llog used 1 01:55:11 Dynamically added 2 cpu VPs |
To take the processors away when no they are no longer needed, issue the following command:
onmode -p -2 cpu |
Similarly, check the online.log using
onstat -m to determine if onmode operation
is successful.
Another way to check if the operation is successful is to use
onstat
-g glo. Listing
4 provides a sample of its output:
Listing 4.
onstat -g glo output
$ onstat -g glo
IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 17 days 23:16:17
-- 522240 Kbytes
MT global info:
sessions threads vps lngspins
0 24 11 157068
sched calls thread switches yield 0 yield n yield forever
total: 30052583 24391872 114838 18595853 104014
per sec: 52 42 0 31 0
Virtual processor summary:
class vps usercpu syscpu total
cpu 5 160.06 10.67 170.73
aio 2 0.53 5.69 6.22
lio 1 1.30 7.84 9.14
pio 1 0.03 1.26 1.29
adm 1 0.01 0.01 0.02
msc 1 0.02 0.01 0.03
total 11 161.95 25.48 187.43
Individual virtual processors:
vp pid class usercpu syscpu total Thread Eff
1 9258 cpu 38.60 3.87 42.47 3728.55 1%
2 9259 adm 0.01 0.01 0.02 0.00 0%
3 9260 cpu 44.39 2.66 47.05 8483.41 0%
4 9261 cpu 76.98 4.12 81.10 8657.88 0%
5 9262 lio 1.30 7.84 9.14 1357.97 0%
6 9263 pio 0.03 1.26 1.29 92.94 1%
7 9267 aio 0.41 3.72 4.13 328.48 1%
8 9268 msc 0.02 0.01 0.03 0.23 13%
9 9269 aio 0.12 1.97 2.09 258.58 0%
10 26623 cpu 0.03 0.01 0.04 11.39 0%
11 26624 cpu 0.06 0.01 0.07 10.37 0%
tot 161.95 25.48 187.43
|
By monitoring the number of virtual processors (vps column in the
"Virtual processor summary" section) for the cpu class before and
after the onmode -p command, you can verify
whether the onmode command was executed
successfully.
To list out all the options available, you can issue the following:
Listing 5. List of available options
$ onmode
usage: onmode [-abBCCcDdFIjklMmnOpQRrSsuWYyZz] |
[-wf <onconfig parameter>=<value>] |
[-wm <onconfig parameter>=<value>]
-a <kbytes> Increase shared memory segment size.
-b <version> Revert Dynamic Server disk structures.
-BC [1|2] Change server large chunk mode
-c [block | unblock] Do Checkpoint. Block or unblock server.
-C {start <count>|stop <count>|threshold <size>|
duration <seconds>|rangesize <size>|alice <mode>|
compression <low|med|high|default>} Tune B-tree scanner.
-D <max PDQ priority allowed>
-d {standard|{primary|secondary <servername>}} set DR server type
DR secondary only:
{idxauto {on|off}} set DR automatic index repair mode
{index <database>:[owner.]<tablename>#<indexname>} DR repair index
{add RSS <servername> <optional password>} add RSS server
{change RSS <servername> <password>} change RSS server password
{delete RSS <servername>} remove RSS server definition
{RSS <source Node> <optional password>} set RSS server type
{set SDS primary <alias> [force]} define SDS primary server alias
{clear SDS primary <alias> [force]} remove SDS primary server alias
{make primary <alias> [force]} make server into the MACH11 primary
-e {on|off|enable|flush} configure or flush shared statement cache.
-F Free unused memory segments
-I stop verbose error trapping
-I <iserrno> [<session ID>] trap specified error for session ID
-j Change to single-user mode
-k Shutdown completely
-l Force to next logical log
-M <decision support memory in kbytes>
-m Go to multi-user on-line
-n Set shared memory buffer cache to non-resident
-O Override space down blocking a checkpoint
-p <+-#> <class> Start up or remove virtual processors of
a specific class
-Q <max # decision support queries>
-R Rebuild the /INFORMIXDIR/etc/.infos.DBSERVERNAME file
-r Set shared memory buffer cache to resident
-S <max # decision support scans>
-s Change to quiescent mode
-u Change to quiescent mode and kill all attached sessions
-W {STMT_CACHE_NOLIMIT {0|1} | STMT_CACHE_HITS <#>} Sets ssc
parameters.
-wf <onconfig parameter>=<value> Update the value
of the specified configuration parameter and save
the new value to the onconfig file.
-wm <onconfig parameter>=<value> Update the value of
the specified configuration parameter without saving
the new value to the onconfig file. The new value is
written to server memory only and will not be retained
once the server is restarted.
-y Do not require confirmation
-Y <sid> <0|1|2> [filename] Set or unset dynamic explain
0=off 1=plan + statistics on 2=only plan on
filename is a valid argument only when setting the
dynamic explain or dynamic explain statistics on
-Z <address> heuristically complete specified transaction
-z <sid> Kill specified session id
|
Monitoring IDS using onstat utility
When the server starts, it creates structure control blocks in the shared memory segments. These control blocks are used internally by the server for the various operations. Thus, by reading the control structures, you are able to monitor the state or different events of the server. The onstat utility is primarily used for that purpose.
Figure 2 shows the onstat utility reading the different C language structures in the shared memory. These structures are information related to sessions, locks, buffers, logs, and so on. The onstat utility reads these structures and displays them in a readable format.
Figure 2. IDS shared memory overview
For a start, the simplest onstat command is as follows:
$ onstat - IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 17 days 08:12:09 -- 522240 Kbytes |
It shows that the version of IDS running is 11.50.FC3 and that it had been in online mode for 17 days, 8 hour, 12 minutes, and 9 seconds. The memory it is using is 522240KB.
To find out about sessions information, use the
-g ses option:
Listing 6.
-g ses option$ onstat -g ses IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 00:00:45 -- 149504 Kbytes session #RSAM total used dynamic id user tty pid hostname threads memory memory explain 21 informix - 0 - 0 12288 11688 off 20 informix 93 28925 acme 1 106496 84920 off 18 informix - 0 - 1 348160 329960 off 17 informix - 0 - 1 299008 274344 off 16 informix - 0 - 1 417792 344576 off 3 informix - 0 - 0 16384 13272 off 2 informix - 0 - 0 12288 11688 off |
As shown in Listing 6, a list of sessions and their information are displayed. Session id in the first column is a unique number used by the engine to track each session. The user id, pid of the client, and the hostname that the connection is from are also shown. One interesting column is the RSAM thread, which shows how many threads are spawned for that session. It is possible to have multiple threads associated with one session. Usually, for one client session, there will be one corresponding sqlexec thread at the database server end. This thread is responsible for receiving the instruction from the client and sending information back to it. The server might spawn additional threads for a session if required. One such example of additional thread is the scan thread, used for scanning disk for data.
You can obtain the details for a given session:
Listing 7. Getting info about session 20
$ onstat -g ses 20 IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 00:02:04 -- 149504 Kbytes session effective #RSAM total used dynamic id user user tty pid hostname threads memory memory explain 20 informix - 93 28925 acme 1 106496 84920 off tid name rstcb flags curstk status 47 sqlexec 1115375c8 Y--P--- 7839 cond wait netnorm - Memory pools count 2 name class addr totalsize freesize #allocfrag #freefrag 20 V 11258d040 102400 20768 94 12 20*O0 V 1125f1040 4096 808 1 1 name free used name free used overhead 0 6576 scb 0 144 opentable 0 3608 filetable 0 832 log 0 16536 temprec 0 21664 keys 0 176 gentcb 0 1584 ostcb 0 2816 sqscb 0 19112 sql 0 72 rdahead 0 1120 hashfiletab 0 552 osenv 0 2648 sqtcb 0 7128 fragman 0 352 sqscb info scb sqscb optofc pdqpriority sqlstats optcompind directives 1125be0c0 1125d5028 0 0 0 2 1 Sess SQL Current Iso Lock SQL ISAM F.E. Id Stmt type Database Lvl Mode ERR ERR Vers Explain 20 - db1 CR Not Wait 0 0 9.24 Off Last parsed SQL statement : select * from t1 |
The additional information you can obtain includes detail of the thread associated with the session, the detail of the memory used as in the "Memory pools section", and the detail of the SQL statement parsed or executed. The column "SQL ERR" and "ISAM err" shows you if this session encountered any errors when executing the SQL statement.
To view dbspace and chunk information, use the
-d option:
Listing 8.
-d option
$ onstat -d
IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 00:03:43
-- 149504 Kbytes
Dbspaces
address number flags fchunk nchunks pgsize flags owner name
111444028 1 0x40001 1 1 2048 N B informix rootdbs
1 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags pathname
1114441c0 1 1 0 100000 29151 PO-B- /support/rootchk
1 active, 32766 maximum
NOTE: The values in the "size" and "free" columns for DBspace chunks are
displayed in terms of "pgsize" of the DBspace to which they belong.
Expanded chunk capacity mode: always
|
This onstat displays the output into two main sections: dbspaces and chunks.
In the "Dbspaces" section, the important field to take note is "fchunk", which indicates the first chunk number (which is the identifier for the chunk in the "Chunks" section) of the dbspace. The "nchunks" tells you how many chunks this dbspace has altogether.
From the "Chunks" section, the size of the chunk and the amount of free space available are shown in the "siz" and "free" columns, respectively. As the special "NOTE" written at the bottom of the output indicates, the unit for "size" and "free" column are in pages of dbspace that it belongs to. For example, for the chunk 1 in this case, its size is 100000 pages, and size of each page for dbspace 1 is 2048 bytes, as shown in the pgsize column in the "Dbspace" section. Thus, the size of chunk 1 is 204 800 000 bytes.
There are many other options available. To list them, you can use the following command:
Listing 9. List of available options
$ onstat --
usage: onstat [ -abBcCdDfFgGhjklLmOpPRstTuxXz ] [ -i ] [ -r [<seconds>] ]
[ -o [<outfile>] ] [ <infile> ]
-- Print this help text
<infile>
Read shared memory information from specified dump file
-a Interpreted as onstat -mcuxskbPFhRtdGflLpO; onstat -g all; onstat -XC
-b Print buffers
-B Print all buffers
-c Print configuration file
-C Print b-tree scanner requests
-d [update]
Print spaces and chunks
update - Ask server to update BLOB chunk statistics
-D Print spaces and detailed chunk stats
-f Print dataskip status
-F Print page flushers
-g <cmd> MT COMMAND or ENTERPRISE REPLICATION COMMAND (see below)
MT COMMANDS:
act Print active threads
afr <pool name|session id>
Print allocated pool fragments
all Print all MT information
ath Print all threads
buf Print profile information related to buffer pools.
ckp Print checkpoint statistics
cmsm Print Connection Manager statistics
con Print conditions with waiters
cpu Print CPU info for all threads
dbc Print dbScheduler/dbWorker thread info
ddr Print DDR log post processing information
dic Print dictionary cache information
dis Print a list of database servers and the status of each
dll Print dynamic library statistics
dmp <address> <length>
Dump <length> bytes of shared memory starting at <address>
dri Print data replication information
dsc Print a list of distribution cache information
env [ all | [<session-id>] ] [<variable-name>[,<variable-name>...]]
Display environment variable settings.
ffr <pool name|session id>
Print free pool fragments
glo Print MT global information
his [<ntraces>]
Prints SQL statement tracing information for <ntraces>
no <ntraces> = Complete output from trace buffer
idxscan Print index scan profiles
imc Print information about connected MaxConnect instances
iob Print big buffer usage by IO VP class
iof Print disk IO statistics by chunk/file
iog Print AIO global information
iov Print disk IO statistics by vp
ipl Print index page logging status
lap Print light append information
lmx Print all locked mutexes
lsc Print Light Scan information
mem [<pool name>|<session id>]
Print pool statistics.
mgm Print Memory Grant Manager information
nbm Print block map for non-resident segments
nsc [<client id>]
Print net shared memory status
nsd Print net shared memory data
nss [<session id>]
Print net shared memory status
ntd Print net dispatch information
ntm Print net message information
ntt Print net user thread access times
ntu Print net user thread profile information
opn [<tid>]
Print open tables
plk Print partition lock profiles
pos Print /INFORMIXDIR/etc/.infos.DBSERVERNAME file
ppf [<partition number> | 0]
Print partition profiles
pqs [<session id>]
Print statistics for an active query
prc Print information about SPL routine cache
proxy [all | [<proxy id> [<txn id> [<op num>]]] ]
Print updatable secondary related information
qst Print queue statistics
rbm Print block map for resident segment
rea Print ready threads
rss [verbose | log | <RSS Srv name>] Print RSS server related
information
rwm print Read/Write Mutex lists
sch Print VP scheduler statistics
sds [verbose | <SDS server name>] Print SDS related information
seg Print memory segment statistics
ses [<session id>]
Print session information
sle Print all sleeping threads
smb Print smart-large-object usage
smx [ses] Print smx related information
spi Print spin locks with long spins
sql [<session id>]
Print SQL information
src <pattern> <mask>
Search memory for <pattern>, where <pattern>==(memory&<mask>)
ssc [pool|all]
Prints ssc pool summary, or statement cache summary and
entries, including key only entries (all)
stk <tid>
Dump the stack of a specified thread
stm [<sesson id>]
Prints all prepared statements approximate memory usage in a
session
stq [<session id>]
Print stream queue information
sts Print max and current stack sizes
tgp Print generic page thread profiles
tpf [<tid> | 0]
Print thread profiles
ufr <pool name|session id>
Print pool usage breakdown
vpcache Print CPU VP memory block cache statistics
wai Print waiting threads
wmx Print all mutexes with waiters
wst Print thread wait statistics
ENTERPRISE REPLICATION COMMANDS:
cat [scope | replname ]
Print Enterprise Replication global catalog information
cdr Print Enterprise Replication statistics
cdr config [parameter_name] [long]
cdr config CDR_ENV [variable_name] [long]
Print Enterprise Replication configuration information
Not specifying a parameter will display the name of and
information about all available parameters.
dtc Print statistics for the Enterprise Replication delete table
cleaner
dss [ UDR | UDRx ]
Print statistics about data sync threads and user-defined data
types
grp [ A|E|Ex|G|L|Lx|M|Mz|P|pager|R|S|Sl|Sx|T|UDR|UDRx ]
Print statistics about the Enterprise Replication grouper
nif [ all | sites | serverid | sum ]
Print statistics about the Enterprise Replication network
interface
que Print statistics for the Enterprise Replication high-level queues
rcv [serverid]
Print statistics about the Enterprise Replication receive manager
rep [replname]
Print events that are in the queue for the schedule manager
rqm [ ACKQ | CNTRLQ | RECVQ | SENDQ | SYNCQ | SBSPACES | FULL | BRIEF |
VERBOSE ]
Print statistics of the Enterprise Replication low-level queues
sync Print the Enterprise Replication synchronization status
-G Print global transaction ids
-h Print buffer hash chain info
-i Interactive mode
-j Print interactive status of the active onpload process
-k Print locks
-l Print logging
-L Print distribution of available locks on the lock free lists
-m Print message log
-o Put shared memory into specified file (default: onstat.out)
-O Print Optical Subsystem memory and staging cache information
-p Print profile
-P Print partition buffer summary
-r Repeat options every <seconds> seconds (default: 5)
-R Print LRU queues
-s Print latches
-t Print TBLspaces
-T Print tablespace information
-u Print user threads
-x Print transactions
-X Print entire list of sharers and waiters for buffers
-z Zero profile counts
|
Table of contents
- Before you start
- The onstat, oninit, and onmode utilities
- Data movement utilities
- Automatic monitoring, maintenance, and administrative tasks
- IDS user interfaces
- Conclusion
- Resources
- About the author
