Monitor

Toggles between displaying or hiding the Handle Information grid at the bottom of the tab. The Handle Information grid includes different information, depending on the tab.

The Handle Information grid also has a Select Columns to Display icon, so that you can hide or display columns as desired.

Active Files
MicroKernel Sessions

Delete Selected Session

Removes a highlighted session from the tab. This icon becomes activated only after a session is selected.

Caution: This procedure actually terminates a session, so you are interrupting someone’s work in progress. Consequently, a message asks you to confirm that you actually want to do this.

MicroKernel Sessions
SQL Sessions

Delete All Sessions

Removes all sessions from the tab.

Caution: This procedure actually terminates all sessions, so you are interrupting work in progress. Consequently, a message asks you to confirm that you actually want to do this.

MicroKernel Sessions

Reset Deltas

Deletes a statistic and restarts the count at zero.

MicroKernel Communication Statistics

Monitored Server Activities

The following sections describe the activities displayed on the Monitor tabs:

•

Active Files

•

MicroKernel Sessions

•

Resource Usage

•

MicroKernel Communication Statistics

•

SQL Active Sessions

Active Files

This tab provides information about MicroKernel files that are currently open.


Path	Provides the directory and all subdirectories to the location of the file.
File	Indicates the name, including suffix, of the file.
Page Size	Indicates the size in bytes of each page in the file.
Read-Only	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	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. 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. 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.

You can view the handle information for any active file, if the Hide/Show Handles icon is set to display handles. Active file handles include the following information.

Client

Indicates the name (typically the login ID of the user) or an index to the Client list of the database server.

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 T4 for IPv4 addresses, T6 for IPv6 addresses, and T for the fully qualified domain name of a client machine. Examples:
T4: 180.150.1.24
T6: 1234:5678:0000:0000:0000:0000:9abc:def0
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 the following:

•

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.

MicroKernel Sessions

This tab provides information about current connections to the storage engine.


Session	Provides a unique identifier for the connection.
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 T4 for IPv4 addresses, T6 for IPv6 addresses, and T for the fully qualified domain name of a client machine. Examples: T4: 180.150.1.24 T6: 1234:5678:0000:0000:0000:0000:9abc:def0 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 Access	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 Access	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.

You can view the handle information for any MicroKernel session, if the Hide/Show Handles icon is set to display handles. MicroKernel session handles include the following information.


Path	Provides the directory and all subdirectories to the location of the file.
File	Indicates the name, including suffix, of the file.
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.

Resource Usage

This tab shows values for different aspects of MicroKernel operations in progress. In addition to the current values (defined in the following table), the grid on the tab provides peak and maximum values, enabling you to assess resource use and needs. “Peak” is the highest value for the resource since the MicroKernel was started. “Maximum”is the highest allowed value. The following table indicates which resources have unlimited maximum values.


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. “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 Viewing Session Information).
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 (also called the “session count limit”) shows the maximum permitted sessions as granted by a license agreement. Session count reflects all sessions whether established through the MicroKernel Engine or through the Relational Engine. 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. 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.

MicroKernel Communication Statistics

This tab displays information about communication with the data storage engine. It includes separate sections for communication statistics and resource usage information.

Communication statistics are calculated in terms of total number of occurrences processed since the database engine was started. “Delta” indicates the number of occurrences since you last accessed the MicroKernel Communications Statistics tab. To restart the count of the delta number, click Reset Deltas.


Total Requests Processed	Indicates the number of requests the database engine has handled from workstations or remote, server-based applications.
SPX Requests Processed	Indicates the number of SPX requests the database engine has handled from clients or remote, server-based applications.
TCP/IP Requests Processed	Indicates the number of TCP/IP requests the database engine has handled from clients or remote, server-based applications.
NetBIOS Requests Processed	Indicates the number of NetBIOS requests the database engine has handled from clients or remote, server-based applications.
Connection Timeouts	Indicates the number of times Auto Reconnect has timed out when attempting to reconnect to Clients. See also Auto Reconnect Timeout.
Connection Recoveries	Indicates the number of times the AutoReconnect feature has successfully recovered from a connection timeout.

Resource usage information provides current values, that is, number of occurrences. In addition, for comparison purposes, it provides a peak usage number (the highest number of occurrences for the resource since the MicroKernel was started) and a maximum allowed value. The following table defines the current value for each resource and explains the maximum value when necessary.


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 might 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.