Monitor Graphical User Interface


Save Settings on Exit	Select this option to save all configuration settings when you close Monitor. Monitor saves both the settings on this dialog and the automatic refresh option on the various dialogs.
Save Window Layout on Exit	Select this option to save the state (open or closed) and screen location of all open dialogs. When you start Monitor again, the dialogs are automatically opened and positioned. This enables you easily to reproduce your preferred layout.
Refresh Rate (Seconds)	Specifies the time interval with which Monitor refreshes its display. The refresh rate is measured in seconds. The default setting is 4. You can specify integer numbers only. If you set this number too low, Monitor may refresh itself so frequently that it affects the performance of the database engine. This is especially true if monitoring the local database engine.

Click OK to save the settings.

Monitoring Transactional Interface Resources

This section describes the following options for monitoring the transactional interface (MicroKernel):

•

Setting Dialog Refresh Options

•

Viewing Active Files

•

Viewing Session Information

•

Viewing Resource Usage

•

Viewing Communications Statisticss

Setting Dialog Refresh Options

You can refresh the information in Monitor dialogs either automatically or manually, as follows.

•

Automatically: select the Automatic Refresh option. The utility updates the dialog at the Refresh Rate specified in the Monitor options (see Setting Monitor Options).

•

Manually: click Refresh.

Viewing Active Files

Click Active Files from the MicroKernel menu. The MicroKernel Active Files dialog displays and shows all of the files currently open by the MicroKernel.

Figure 5 Active MicroKernel Files Dialog

Files List

In the upper left of the dialog, Monitor displays the list of Active MicroKernel Files. This scrollable list contains the complete path of all open files in alphabetic order.

►

To view information about a file

Click on the desired file in the list.

View the information about the file in the lower left of the dialog, the File Information box.


Page Size	Indicates the size in bytes of each page in the file.
Read-Only Flag	Indicates whether the file is flagged as read-only by the operating system.
Record Locks	Indicates whether any of the active handles for the selected file have record locks. Any application can read a locked record, but only the application that placed the lock can modify or delete the record. A record lock exists only as long as the application that opened the file is updating a record. “Yes” indicates that one or more record locks are applied to the file. “No” indicates that no records are locked.
Transaction Lock	Indicates whether any of the active handles for the selected file have a transaction lock. A transactional file lock exists only as long as the application that opened the file is processing a transaction.
Physical File Size KB	Indicates the size of the file in kilobytes (KB). This information is particularly useful for the capacity-based license model if you want to review data in use on a file-by-file basis. See also Capacity-based License Model in Pervasive PSQL User's Guide. Note that Monitor uses kilobytes (KB) for the size of an individual file and megabytes (MB) as the units for resource usage (Viewing Resource Usage). License Administrator uses gigabytes (GB) as the units because that is how data in use is associated with a key. The different contexts require units appropriate for each context. Note that, if a file is immediately closed after you insert a large number of records, Monitor does not immediately reflect the changes in file size. For example, the statistics for “Physical File Size KB” are not refreshed for that file until the next time the file is opened for reading or writing.

File Handles List

In the upper right of the MicroKernel Active Files dialog, Monitor displays the list of Selected File’s Handles. This scrollable list contains the active handles associated with the selected file. Each handle is represented by a name (typically the login ID of the user), or by an index into the Client list of the database engine.

►

To view information about a file handle

Click on the desired handle in the list.

View the information about the handle in the lower right of the dialog, the Handle Information box.


Connection Number	Displays the network connection number of the client. If the client does not have a network connection, this field displays “NA” (for not applicable).
Task Number	Displays the process-supplied task number for processes originating at the server, or a Windows Client.
Site	Specifies the location of the user process (local or remote).
Network Address	Identifies the location of the calling process on the network. If the calling process is SPX, the network node/network address is preceded by S: such as S: 65666768 00000000001. If the calling process is TCP/IP, the address is preceded by T: such as T: 180.150.1.24, T: 1234:5678:0000:0000:0000:0000:9abc:def0, or T: <mymachine.mydomain.mycompany>.com.
Open Mode	Indicates the method the application uses to open the specified handle of the file. Valid open modes are: Normal – The application that opened the file has normal shared, read/write access to it. Accelerated – The application that opened the file has shared read/write access. Read-only – The application that opened the file has read-only access; it cannot modify the file. Exclusive – The application that opened the file has exclusive access. Other applications cannot open the file until the calling application closes it. Monitor also specifies all open modes as non-transactional or shared locking when applicable.
Record Lock Type	Displays the type of record lock(s) currently held by the handle. The possible record lock types are Single, Multiple, and None. Single-record locks enable a user to lock only one record at a time. Multiple-record locks enable a user to lock more than one record at a time.
Wait State	Indicates whether the user is waiting because of some type of lock on this handle: Waits for Record Lock, Waits for File Lock, or None.
Transaction State	Displays the state of the transaction lock currently held by the handle. The possible transaction types are Exclusive, Concurrent, or None.

Viewing Session Information

You can view a list of current sessions and files, as well as file handles for each session. A “session” is defined as a client ID used by the transactional engine interface or a connection to the relational engine interface. “Client ID” is defined as a 16-byte structure that combines elements provided by the application, by the client platform, and by the database engine to uniquely identify a database transaction context.

Note that the session information reflects the sessions established through the transactional interface and through the relational interface. (If you want to view sessions established only through the relational interface, see Viewing SQL Active Sessions.)

►

To view sessions

Click Active Sessions from the MicroKernel menu. The MicroKernel Active Sessions dialog appears.

Figure 6 Active MicroKernel Sessions Dialog

Sessions List

In the upper left of the dialog, Monitor displays the list of Active MicroKernel Sessions. This scrollable list contains the names of active sessions in alphabetic order. Each session is represented by a name (typically the login ID of the user) or by an index into the Client list of the database engine.

►

To view information about a session

Click on the desired session.

View the information about the session in the lower left of the dialog, the Session Information box.


Connection Number	Displays the network connection number of the session. If the session does not have a network connection, this field displays NA (for not “applicable”).
Task Number	Displays the process-supplied task number for processes originating at the server, or from a Windows Client.
Site	Specifies the location of the session process (local or remote).
Network Address	Identifies the location of the calling process on the network. If the calling process is SPX, the network node/network address is preceded by S: such as S: 65666768 00000000001. If the calling process is TCP/IP, the address is preceded by T: such as T: 180.150.1.24, T: 1234:5678:0000:0000:0000:0000:9abc:def0, or T: <mymachine.mydomain.mycompany>.com. If multiple clients from a single machine connect by different TCP/IP addresses, each address is valid for that client. However, internally to the database engine, an address associated with a client may not be the actual address used by that client. This is because of the way the database engine identifies and manages multiple clients from the same machine. Consequently, since Monitor is reporting engine information, the utility may display an associated address instead of the actual address.
Locks Used	Indicates the number of locks the session is currently using.
Transaction State	Displays the type of transaction lock the session currently holds. The possible transaction types are Exclusive, Concurrent, or None.
Records Read	Displays the number of records read since the session first opened a file.
Records Inserted	Displays the number of records the session has inserted.
Records Deleted	Displays the number of records the session has deleted.
Records Updated	Displays the number of records the session has updated.
Disk Accesses	Indicates the number of times the session required a disk access. You will not see any information for disk accesses for files that have just been opened.
Cache Accesses	Indicates the number of times this client experiences a miss of the L1 cache and moves a page from either L2 cache or the disk into the L1 cache in order to fulfill the request.

Session File Handles

In the upper right of the dialog, Monitor displays the Selected Session’s Handles list. This scrollable list contains the active file handles associated with the selected session. The MicroKernel creates a handle each time a session opens a file. A single session can have several handles for the same file.

►

To view information about a session file handle

Click on the desired session file handle.

View the information about the handle in the center right portion of the dialog, the Handle Information box.


Open Mode	See Open Mode.
Record Lock Type	See Record Lock Type.
Wait State	See Wait State.
Transaction State	See Transaction State.

Deleting Current Sessions

Deleting a current session removes the session from the list of active sessions and terminates the session’s connection to the database engine. All open files for the session are closed and all allocated resources are freed.

Caution: Deleting a current session can result in incorrect data, incomplete records or aborted transactions depending on the what processing is currently occurring.

►

To delete a session

Click on the desired session name.

Perform one of the following actions:

•

Click Delete Current Session to delete the selected session.

•

Click Delete All Sessions to delete all of the current sessions.

Viewing Resource Usage

Click Resource Usage from the MicroKernel menu. The MicroKernel Resource Usage dialog box displays.

Figure 7 MicroKernel Resource Usage Dialog

This dialog displays the resources in use by the MicroKernel since it was last started. The MicroKernel Uptime lists the amount of time in weeks, days, hours, and minutes that the MicroKernel has been running.

The dialog shows the following statistics for each resource:

•

Current – Shows the present value for the resource.

•

Peak – Shows the highest value for the resource since the MicroKernel was started.

•

Maximum – Shows the highest value allowed for the resource.

The database engine dynamically controls the maximum values for some of these resources. The maximum value for User Count, Session Count, and Data In Use depends on the product license. See License Models in Pervasive PSQL User's Guide.

If a resource does not apply to the type of Pervasive PSQL product being monitored, “n/a” (“not applicable”) appears for each statistic. For example, “User Count” does not apply to Pervasive PSQL Vx Server. Therefore, “n/a” appears as the Current, Peak, and Maximum value for “User Count” if Pervasive PSQL Vx Server is being monitored. Similarly, “n/a” appears as the Maximum value for “Session Count” and “Data in Use MB” if Pervasive PSQL Server is being monitored.

However, if you are considering using Pervasive PSQL Vx Server, you need the ability to estimate Current and Peak values for “Session Count” and “Data in Use MB”; consequently, those statistics are displayed for the PSQL Server without being enforced. No notifications are sent about them regardless of their values.

Usage information is displayed for the following resources.


Files	Indicates the number of files currently open by the MicroKernel.
Handles	Indicates the number of active handles. The MicroKernel creates a handle each time a user opens a file. A single session can have several handles for the same file.
Clients	Indicates the number of clients accessing the MicroKernel. A machine can have multiple clients accessing the database engine simultaneously. The engine dynamically manages the client list. The number of clients is limited only by the memory in the computer. Note that “client” indicates a session established by a client ID (transactional engine interface) or a connection to the relational engine interface. The database engine uses various client sessions for its own internal processes, such as for accessing Pervasive PSQL system files, metadata files, dbnames.cfg, and default system databases. The number of clients indicates both internal client sessions and non-internal client sessions (see Session Count).
Worker Threads	Indicates the number of concurrent MicroKernel processes.
User Count	Indicates the number of concurrently connected users. The maximum value shows the maximum permitted users as granted by a license agreement.
Session Count	Indicates the number of sessions in use by the database engine. For brevity, “number of sessions in use” is also referred to “session count.” The maximum value shows the maximum permitted sessions as granted by a license agreement. The maximum is also called the “session count limit.” Note that session count reflects all sessions whether established through the transactional interface or through the relational interface. Messages pertaining to session count are logged to the various Pervasive PSQL logging repositories. See Pervasive PSQL Message Logging in Pervasive PSQL User's Guide. The database engine uses various sessions for its own internal processes, such as for accessing Pervasive PSQL system files, metadata files, dbnames.cfg, and default system databases. These internal sessions do not consume any session counts.
Data In Use MB	Indicates in megabytes (MB) the size of all concurrently open data files. The maximum value is the maximum permitted amount of all concurrently open data files as granted by a license agreement. The maximum is also called the “data in use limit.” The value for data in use increases when a data file is first opened. Subsequent opens to an already open data file do not add to the total. Data in use also increases if an open file increases in size. Operations on an already open file continue to be permitted even if the size of the open file increases beyond the data in use limit. The value for data in use decreases when a data file is closed by the final user to have the file open. Since more than one user can access the same data file, all opens must be closed before data in use decreases. Messages pertaining to data are logged to the various Pervasive PSQL logging repositories. See Pervasive PSQL Message Logging in Pervasive PSQL User's Guide. The database engine uses various files for its own internal processes, such as Pervasive PSQL system files, metadata files, dbnames.cfg, and default databases. Files used for internal processes do not increase the value for data in use. Note that, if a file is immediately closed after you insert a large number of records, Monitor does not immediately reflect the changes in file size. For example, the statistics for “Data in Use MB” are not refreshed for that file until the next time the file is opened for reading or writing.
Transactions	Indicates the number of transactions. The maximum for this resource is unlimited.
Locks	Indicates the number of record locks. The maximum for this resource is unlimited.

Viewing Communications Statistics

Click Communications from the MicroKernel menu. The MicroKernel Communications Statistics dialog displays.

Figure 8 MicroKernel Communications Statistics Dialog

This dialog displays communications statistics for the database engine since the last time the MicroKernel was started. The MicroKernel Uptime lists the amount of time in weeks, days, hours, and minutes that the MicroKernel has been running.

Where applicable, the dialog shows the following statistics for a resource:

•

Current – Shows the most recent value for the resource.

•

Peak – Shows the highest value for the resource since the MicroKernel was started.

•

Maximum – Shows the highest value allowed for the resource.

You can monitor the activity of the following communications resources.


MicroKernel Uptime	Lists the amount of time in weeks, days, hours, and minutes that the MicroKernel has been running.
Total Requests Processed	Indicates the number of requests the database engine has handled from workstations or remote, server-based applications. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog. To reset this number to zero, click Reset Delta.
SPX Requests Processed	Indicates the number of SPX requests the database engine has handled from clients or remote, server-based applications. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog. To reset this number to zero, click Reset Delta.
TCP/IP Requests Processed	Indicates the number of TCP/IP requests the database engine has handled from clients or remote, server-based applications. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog box. To reset this number to zero, click Reset Delta.
NetBIOS Requests Processed	Indicates the number of NetBIOS requests the database engine has handled from clients or remote, server-based applications. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog. To reset this number to zero, click Reset Delta.
Connection Timeouts	Indicates the number of times Auto Reconnect has timed out when attempting to reconnect to Clients. See also Auto Reconnect Timeout. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog. To reset this number to zero, click Reset Delta.
Connection Recoveries	Indicates the number of times the AutoReconnect feature has successfully recovered from a connection timeout. Total – Indicates the number of requests processed since the database engine was started. Delta – Indicates the number of requests since you invoked the Communications Statistics dialog. To reset this number to zero, click Reset Delta.
Communications Threads	Indicates the number of remote requests that the MicroKernel is currently processing. Local requests are not included in this statistic. For the total number of remote and local threads being processed, see Viewing Resource Usage. The database engine dynamically increases the number of communications threads as needed up to the maximum allowed. For Windows and Linux platforms, the maximum is 1,024. Worker threads are also used to process Monitor requests, so you may not see the number of current worker threads drop below one. This is normal.
Total Remote Sessions	Indicates the number of remote clients connected to the database engine. The maximum number is dynamic and displays as zero.
SPX Remote Sessions	Indicates the number of remote clients connected through the SPX protocol to the database engine.
TCP/IP Remote Sessions	Indicates the number of remote clients connected through the TCP/IP protocol to the database engine.
NetBIOS Remote Sessions	Indicates the number of remote clients connected through the NetBIOS protocol to the database engine.

Monitoring Relational Interface Resources

This section describes monitoring of the relational interface.

•

Viewing SQL Active Sessions

•

SQL Session Information

Viewing SQL Active Sessions

The SQL active sessions displays only sessions established through a connection to the relational interface. To view all sessions—whether established through the transactional interface or through the relational interface—see Viewing Session Information.

►

To view SQL active sessions

Click Active Sessions from the SQL menu. The SQL Active Sessions dialog displays.

Figure 9 SQL Active Sessions Dialog

SQL Session Information

The Active Sessions label at the top of the dialog displays the number of SQL active sessions. The User Name box displays the list of user names connected to the database engine. User Name is set by default to the Windows login ID. If this is unavailable, User Name is set to “unknown.”

Additional information about the selected User Name is provided in the Session Information box.


Client Host Name	Identifies the name of the Client machine for the selected User Name. If unavailable, this is set to “Unknown.”
Network Address	Identifies the Client machine’s IP or SPX address for the selected User Name. If unavailable, this is set to “Unknown.” Values displayed include IP, SPX, Shared Memory and Unknown.
Client Application	Identifies the connected application or module. If unavailable, this is set to “Unknown.”
Data Source Name	Identifies the name of the DSN referenced by the Client application.
Connection Status	Specifies the connection status for the selected User Name. A status may be any of the following: Active – The session has files open. and that Idle means that the session has no files open. Idle – The session has no files open. Dying – A temporary status that indicates an active session has been deleted but has not finished processing the SQL code. At a suitable termination point, the session is no longer listed on the SQL Active Session dialog. Unknown – Status is unavailable.
Active/Idle Period	Displays the duration of time, in milliseconds, since the connection has been active or idle.
Total Connection Time	Displays the duration of time, in seconds, since the connection has been established.

►

To refresh the SQL active sessions list

Click Refresh Session List.

Another method is to ensure that the Automatic Refresh option is selected and wait for the refresh rate to activate the refresh. See To configure Monitor options.

►

To delete an SQL active session

Click on the desired user name in the User Name list.

Click Delete Session.

If a large SQL block is being processed by an active session when you delete the session, the session may have a temporary connection status of “Dying.” The session should disappear from the dialog when the database engine reaches an appropriate termination point.

Caution: Deleting an active session can result in incorrect data, incomplete records or aborted transactions depending on the what processing is currently occurring.