Mimer SQL System Management Handbook TOC PREV NEXT INDEX

Mimer Developer Site

www.mimer.com/developer


System Information - MIMINFO


The MIMINFO program is used to obtain information from a Mimer SQL database server which is useful for system control, system tuning and trouble-shooting analysis.

Information can be generated from an active Mimer SQL database server as well as from the SQLPOOL and Bufferpool dump files produced by using MIMCONTROL, see Controlling the Database Server - MIMCONTROL.

The output from MIMINFO can be displayed on the screen and may also be directed to a file.

The following reports may be obtained from MIMINFO (further details on each report can be found in the sub-sections that follow):

Report
Description

Users list

this lists details of all the users currently connected.

Performance report

this provides information useful for monitoring performance parameters (MIMSERV).

Bufferpool report

this produces a report which is useful to Mimer Support personnel when investigating system problems (MIMDUMP).

SQLPOOL report

display SQLPOOL parameters

MIMINFO Syntax

The MIMINFO program is controlled by flagged information specified on the command-line.

The overall syntax for MIMINFO (expressed in UNIX-style) is:

 miminfo [-o file] -u | -p | -s [database]
 miminfo [-o file] -u | -p | -m | -s   -f

MIMINFO Command-line Arguments

UNIX-style
VMS-style
Function
 -o file
 /OUTPUT = file
Send output to the specified file instead of to the screen
 -u
 /USERS
Display users list
 -p
 /MIMSERV
Produce Performance report (MIMSERV)
 -m
 /MIMDUMP
Produce Bufferpool report (MIMDUMP)
 -s
 /SQLPOOL
Display SQLPOOL parameters
 database
 database
Take information from the specified database.
If a database name is not specified, the default database will be accessed, see The Default Database.
 -f
 /FILE
Take information from a dump file (for a users list, a dump file called "sqlpool.mdmp" is expected to exist otherwise a dump file called "bpool.mdmp" is expected to exist)

UNIX: The UNIX-style command-line flags must be used on a UNIX machine.

VMS: Either the UNIX-style or the VMS-style command-line flags may be used on a VMS machine - see the Mimer SQL VMS Guide for more details.

Win: The UNIX-style command-line flags can be used if the miminfo program is run from a Command Prompt window.
The shortcut MIMER Info can also be used to run the program and interactive selections can then be made in the program.

A detailed description of each of the MIMINFO reports follows.

The Users List

 
 miminfo [-o file]  -u  [database] | -f
 

A users list can be generated from an active database or from a dump file produced using MIMCONTROL.

The users list shows the name of each ident connected to the database, the channel number used by the connection, the state of the connection, transaction number, the name of the operating user, the network communication protocol (or 'local') and node identification information for connected machine.

The channel number may be used in conjunction with MIMCONTROL to kill a user.

The following is an example of a users list report:

 Username        Channel State  Trans. no OS user      Prot   From
 ============ ========== ===== ========== ============ ====== ====
 SYSADM            16387 Busy           3              TCP    204.71.200.67
 SYSADM           16388 Busy          SARA          Local  00019120

The Performance Report

 
 miminfo [-o file]  -p  [database] | -f 
 

The Performance report (MIMSERV) can be used by the system administrator to monitor performance parameters during Mimer SQL use. The Performance report can be generated from an active database or from a dump file produced using MIMCONTROL.

The Performance report presents five kinds of statistical information which may be useful for system tuning (statistics for page management, transactions, background threads, databank and table usage).

Note: When a Performance report is used as an aid to system tuning, it is important that the report is generated when the database is in full use. The output from several executions over a period of a few hours or days can provide valuable information on fluctuations in system usage.

The Performance report contains the following information:

General Statistics

Page Management Statistics

Transaction Management Statistics

Background Threads

Databank Statistics

Note: After the DB-Check field, a field for additional information may show up. The values here can be the shadow state "offline", or the online backup states "backup in progress" or "backup completion".

Table Statistics

Performance Report Example

The following example output is from a Mimer SQL system which is not being limited by the bufferpool size (page faults, in 2K region, are only about 1% of page requests).

The number of transaction checks is low, indicating either that concurrent user update requests are infrequent or that transaction handling in application programs is well-designed.

The 64K region has not been used at all. It is possible to adjust the sizes of the different regions depending on the requirements of the system.

The error count has a value of 4 which indicates that 4 errors have been written to the database server log, see Database Server Log.

The databank SYMDB has an error status. The database server log will contain further information.

The shadow CASE5_S1 has been set offline as indicated at the end of the line describing the shadow.

 # miminfo -p hotel
 M I M E R / M I M I N F O
 Version 8.2.1A Oct  9 2000
 
 
 ***  MIMER/DB runtime statistics 2000-10-18 15:48:12 ***
 
 Hardware, operating system UNIX 32
 Current MIMER/DB version is 8.2.1A Oct  9 2000
 Database name: HOTEL
 System started at 2000-10-18 15:47:54
 System status is up
 
 Error count                    :          4
 No. of request threads         :          2
 No. of background threads      :          2
 No. of I/O threads             :          0
 
 Page management statistics
 ==========================
 No. of pages written to disk   :       1774
 No. of file extend operations  :          0
 
 Buffer size 2K
 --------------
 No. of page buffers            :       2614
 No. of page buffers per sorter :        135
 No. of remaining sorters       :          2
 No. of page partitions         :          9
 No. of page requests           :      40859
 No. of page faults             :        432     1 %
 No. of pages swapped out       :          0
 
 Buffer size 16K
 ---------------
 No. of page buffers            :        164
 No. of page buffers per sorter :         72
 No. of remaining sorters       :          2
 No. of page partitions         :          1
 No. of page requests           :      44817
 No. of page faults             :          7     0 %
 No. of pages swapped out       :          0
 
 Buffer size 64K
 ---------------
 No. of page buffers            :         54
 No. of page buffers per sorter :         17
 No. of remaining sorters       :          2
 No. of page partitions         :          1
 No. of page requests           :          0
 No. of page faults             :          0
 No. of pages swapped out       :          0
 
 Transaction management statistics
 =================================
 No. of transaction commits     :       1336
 No. of read commits            :          0
 No. of transaction checks      :       1436
 No. of transaction aborts      :        103
 No. of pending restarts        :         18
 
 Background threads
 =================
       SWA State             Trans-no Trans-count
       253 Inactive slave           0       11985
       267 Inactive                 0        1394
 
 Pending background thread requests :          0
 
 Databank statistics
 ===================
 Name                DBANKID  SEQNO Type    Users Access    DB-Check
 TESTDBM1                310      0 TRANS       1 Shared    Complete
 TESTDBM2                311      0 TRANS       1 Shared    Complete
 SYSDB                     1      0 LOG         2 Shared    Complete
 TRANSDB                   2      0 TRANS       1 Shared    Complete
 LOGDB                     3      0 LOG         1 Shared    Complete
 SQLDB                     4      0 WORK        1 Shared    Complete
 SYMDB                   285      0 TRANS       1 Shared    Complete
 Databank error status:       -16142
 CASE5                   279      0 LOG         1 Shared    Complete
 CASE5_S1                279      1 SHADOW      1 Shared    Init      Offline
 
 No. of databanks currently open          :          6
 Max number of databanks open concurrently:        100
 Databank verification count              :          0
 Running background verifications         :          0
 Pending background verifications         :          0
 Databank verification is performed on all pages
 
 Table statistics
 ================
 No. of tables currently open             :         36
 Max number of tables open concurrently   :       4000
 #

Bufferpool Report

 
 miminfo [-o file]  -m  -f
 

The Bufferpool report (MIMDUMP) is used by Mimer Support personnel for trouble-shooting when database problems are reported by customers.

SQLPOOL Report

 
 miminfo [-o file]  -s  [database] | -f
 

A SQLPOOL report is useful when the server is malfunctioning due to a memory problem. SQL pool memory allocated is the amount of memory allocated from the operating system for the SQLPOOL. A part of that memory is in use by the server and is displayed on the row SQL pool memory used.

The following is an example of a SQLPOOL report:

 SQLPOOL report
 ==============
 SQL pool memory allocated (KB):        1656
 SQL pool memory used      (KB):         554


Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
dbtechnology@upright.se
Mimer SQL System Management Handbook TOC PREV NEXT INDEX