Learn about the System Overview (KUD_DB2_System_Overview)
attributes.
Important: The values of
the following attributes are only available when the monitored database
is multi-partitioned, or when the monitored database is single-partitioned
and the intra-partition parallelism is enabled by setting the intra_parallel
parameter to YES.
- Buff Max Used Percent
- Buff Used Percent
- CE Max Used Percent
- CE Used Percent
- MA Max Used Percent
- RB Max Used Percent
- RB Used Percent
Use the
System Overview attributes to monitor general information about the DB2® UDB subsystem in your environment. The
following traits are included:
- Agent-related high-water marks
- Local and remote connections
- Sorting
- Start time
- Status
Agents Created Empty Pool The number
of agents created because the agent pool was empty. It includes
the number of agents started at DB2 start
up. By using the Agents Assigned From Pool attribute, you can calculate
the ratio of the Agents Created Empty Pool attribute to the Agents
From Pool attribute. See the Agents From Pool attribute for information
about using this attribute. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Created Empty Pool Ratio The
percentage of agents that are created because the pool is empty. This
ratio is calculated by dividing the value of the Agents Created Empty
Pool attribute by the value of the Agents From Pool attribute. Use
this attribute to evaluate how often an agent must be created because
the pool is empty.
Agents from Pool The number of
agents assigned from the pool. Use this attribute with Agents
Created Empty Pool attribute to determine how often an agent must
be created because the pool is empty. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Registered The number of
agents that the database manager registered. The following value
is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Registered Top The maximum
number of agents that the database manager has ever registered, at
the same time, since it was started (coordinator agents and subagents). Use
this attribute to evaluate the setting of the MAXAGENTS configuration
parameter. The number of agents registered at the time the snapshot
was taken is recorded by the Agents Registered attribute. The following
value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Stolen The number of times
that agents are stolen from an application. Agents are stolen
when an idle agent associated with an application is reassigned to
work on a different application. Use this attribute with the Maximum
Number of Associated Agents attribute to evaluate the load that this
application places on the system. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Waiting on Token The number
of agents waiting for a token so they can run a transaction in the
database manager. Use this attribute to evaluate your setting
for the MAXCAGENTS configuration parameter. Each application has a
dedicated coordinator agent to process database requests (transactions)
within the database manager. Each agent must have a token to run a
transaction. The maximum number of coordinator agents is limited by
the MAXCAGENTS configuration parameter. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Agents Waiting on Token Percent The
percentage of agents waiting on a token. The percentage is calculated
by dividing the value of the Agents Waiting on Token attribute by
the number of local applications that are currently connected to a
database (Local Cons attribute). Use this attribute to assess the
number of agents
Agents Waiting Top The highest
number of agents waiting on a token, at the same time, since the database
manager was started. Use this attribute to evaluate the setting
of the MAXCAGENTS configuration parameter. In contrast, the Agents
Waiting on Token attribute records the number of agents waiting for
a token at the time the snapshot was taken. The following value is
valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Appl Support Layer Heap Size The
current value (in units of 4-KB pages) of the application support
layer heap size. This value is the amount of memory that is allocated
for the application support layer heap. This heap is used as a communication
buffer between the local application and its associated agent. In
addition, this value is used to determine the input and output block
size when a blocking cursor is opened. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Buff Free The number of Fast Communication
Manager (FCM) buffers that are free in the partitioned database server
during the monitoring interval. Use the returned value to determine
the current buffer pool utilization. Use this information to refine
the configuration of the number of FCM buffers. The following value
is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Buff Free Bottom The minimum number
of free connection entries. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
Buff Max Used Percent The percentage
of maximum FCM buffers used during processing within the partitioned
database server. If the percentage of maximum FCM buffers used
is high compared to normal operating levels, you can increase the
number of FCM buffers; if the percentage is low compared to normal
operating levels, you can decrease the value.
Buff Used Percent The percentage
of FCM buffers that are used within the partitioned database server
during the monitoring interval. If the percentage of FCM buffers
used is high compared to normal operating levels, you can adjust the
number of FCM buffers.
CE Free The number of connection
entries that are free in the partitioned database server during the
monitoring interval. Use the returned value to help determine
the current connection entry utilization. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
CE Free Bottom The minimum number
of free connection entries. The following value is valid:
| External value |
Internal value |
| Value_Exceeds_Maximum |
9223372036854775807 |
CE Max Used Percent The maximum
percentage of FCM connection entries used during processing within
the partitioned database server. If the percentage of maximum
FCM connection entries used is high compared to normal operating levels,
you can increase the number of FCM connections; if the percentage
is low compared to normal operating levels, you can decrease the value.
CE Used Percent The percentage
of FCM connection entries used during processing within the partitioned
database server. If the percentage of FCM connection entries
used is high compared to normal operating levels, you can increase
the number of FCM connections; if the percentage is low compared to
normal operating levels, you can decrease the value.
Committed Private Memory The amount
of private memory that the instance of the database manager currently
has committed at the time of the snapshot. Use this attribute
to assess the MIN_PRIV_MEM configuration parameter to ensure that
enough private memory is available. This attribute is returned for
all platforms, but tuning can be accomplished only on platforms where DB2 uses threads (such as OS/2 and Windows NT systems). Values
that are greater than or equal to 9223372036854775807 are indicated
with the
Value Exceeds Maximum text in the portal.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Conn Local Database The number
of local databases with current connections to the monitored DB2 instance. This value gives
an indication of how many database information records to expect when
gathering data at the database level. The applications can be running
locally or remotely, and might or might not be executing a unit of
work within the database manager. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Connection Status The status of
the communication connection between the database partition that is
specified by the DB2 Node Number
variable and the database partition where this monitor runs. Two
nodes can be active, but the connection between them remains inactive
unless there is active communication between them.
Cons in Exec Percent The percentage
of the maximum number of applications allowed that are connected to
a database and processing a unit of work during the monitoring interval.
Coordinating Agents Top The maximum
number of coordinating agents working at one time. The MAXCAGENTS
configuration parameter determines the number of coordinating agents
that can be executing concurrently. If the peak number of coordinating
agents results in a workload that is too high for this node, you can
reduce the MAXCAGENTS configuration parameter. The following value
is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
DB Partition The DB2 database partition node number, which can
range from 0 to 999. The Aggregated and Current Partition values can be used within
a query or situation filter. If you do not specify a db partition
filter, data is returned for either the current database partition
(single partition environment) or the aggregated database partitions
(multiple partition environment). If a db partition filter is set
to Aggregated, only aggregated partition data is returned. Historical
data collection includes both aggregated and individual partition
attribute data. In addition to numeric partition numbers in the 0
to 999 range, the following values are also valid:
| External value |
Internal value |
| Aggregated |
-1 |
| Current Partition |
-2 |
| All |
-3 |
DB2 Available The
amount of time (in seconds) the instance has been available since
a DB2START command was issued. The value format is an integer.
The value is derived through this formula:
snapshot time - db2start time
The
following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
DB2 Instance
Status The current status of the DB2 instance. The
following table shows the valid values:
| External value |
Internal value |
Description |
| Active |
Active |
The DB2 instance
is currently active. |
| Inactive/Busy |
Inactive/Busy |
The DB2 instance
is either not running or is too busy to respond. |
| Quiesce Pending |
Quiesce_Pending |
A quiesce is pending for the DB2 instance. |
| Quiesced |
Quiesced |
The DB2 instance
is currently quiesced. |
| Unknown |
Unknown |
The DB2 instance
is active, but the state is not recognized. |
Use this attribute to determine the state of your database
manager instance.
DB2 Server
Type The type of database manager being monitored. The
following values are valid:
| External value |
Internal value |
| Client with local databases |
Client_with_local_databases |
| Client/server |
Client/server |
| Host Database Server |
Host_Database_Server |
| MPP |
MPP |
| Requestor |
Requestor |
| Satellite |
Satellite |
| Standalone |
Standalone |
| UNKNOWN |
UNKNOWN |
DB2 Start
Timestamp The date and time that the database manager was
started using the DB2START command. Use this attribute with the
snapshot time attribute to calculate the elapsed time from the start
of the database manager until the snapshot was taken.
DB2 Version The
version of the server that is returning the data. For example:
6.1 or 7.1. The data structures used by the monitor might change between
releases. As a result, check the version of the data stream to determine
whether your applications can process the data. The following values
are valid:
| External value |
Internal value |
| 1 |
1 |
| 2 |
2 |
| 3 |
3 |
| 4 |
4 |
| 5 |
5 |
| 6 |
6 |
| 7 |
7 |
| 8 |
8 |
| 9 |
9 |
| UNKNOWN |
UNKNOWN |
DBPG Node Status The list of
failing local nodes. This is a list of integers, where each integer
represents the failed local nodes. Depending on the actual partitions
defined in the database partition group, it is not necessarily true
that all the nodes defined in the parallel environment are examined.
To ensure that all the nodes in the partitioned environment are examined,
define a partition group that contains at least one database partition
from each of the nodes in the partitioned environment.
FCM Num Anchors The number of FCM
message anchors for the DB2 instance
during the monitoring interval. Agents use the message anchors
to send messages among themselves. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
FCM Num Buffers The number of buffers
that are used for internal communications (messages) among the nodes
and within the nodes in a DB2 instance
during the monitoring interval. You might need to increase the
value of this parameter if you have either of the following conditions:
multiple logical nodes on a processor, or too many users, nodes, or
complex applications that exceed the buffer limit. The following value
is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
FCM Num Connect The number of FCM
connection entries for the DB2 instance
during the monitoring interval. Agents use connection entries
to pass data among themselves. Use the results from the fcm_num_rqb
attribute to help you refine the fcm_num_connect attribute. The following
value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
FCM Num Rqb The number of FCM
request blocks for the DB2 instance
during the monitoring interval. Request blocks are the media
through which information is passed between the FCM daemon and an
agent. The requirement for request blocks varies according to the
number of users on the system, the number of database partition servers
in the system, and the complexity of queries that are run. The following
value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Gateway Cons Wait Client For
host databases being handled by the DB2 Connect gateway, the current number
of connections that are waiting for the client to send a request. Because
this value can change frequently, take samples at regular intervals
over an extended period to obtain a realistic view of gateway usage.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Gateway Cons Wait Host For host
databases being handled by the DB2
Connect gateway, the current number of connections that are waiting
for a reply from the host. Because this value can change frequently,
take samples at regular intervals over an extended period to obtain
a realistic view of gateway usage. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Gateway Current Connections The
current number of connections to host databases being handled by the DB2 Connect gateway. Use
this attribute to help you understand the level of activity at the DB2 Connect gateway and the
associated use of system resources. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Gateway Total Connections The
total number of connections attempted from the DB2 Connect gateway since the last db2start
command or the last reset. Use this attribute to help you understand
the level of activity at the DB2
Connect gateway and the associated use of system resources. The
following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Idle Agents The number of agents
in the agent pool that are currently unassigned to an application. Use
this attribute to set the NUM_POOLAGENTS configuration parameter.
By having idle agents available to satisfy requests for agents, you
can improve performance. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Instance Name The name of the monitored DB2 instance. The valid format
is a text string with a maximum of 60 bytes.
Last Reset Timestamp The date and
time that the monitor counters were reset for the application requesting
the snapshot. Use this attribute to help you determine the scope
of information returned by the database system monitor.
Local Connections The number of
local applications that are currently connected to a database within
the database manager instance being monitored. By using this
number, you can determine the level of concurrent processing occurring
in the database manager. This value changes frequently. As a result,
you must sample the data at specific intervals over an extended period
of time to get a realistic view of system usage. This number includes
only applications that were initiated from the same instance as the
database manager. The applications are connected, but might or might
not be executing a unit of work in the database. The following value
is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Local Connection Executing The
number of local applications that are currently connected to a database
within the database manager instance being monitored and are currently
processing a unit of work. By using this number, you can determine
the level of concurrent processing occurring in the database manager.
This value changes frequently. As a result, you must sample the data
at specific intervals over an extended period of time to get a realistic
view of system usage. This number includes only applications that
were initiated from the same instance as the database manager. The
following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
MA Free Bottom The minimum number
of free message anchors. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
MA Max Used Percent The maximum
number of message anchors used as a percentage.
Max Agent Overflows The number
of attempts to create a new agent when the MAXAGENTS configuration
parameter had already been reached. If requests to create new
agents are received after reaching the MAXAGENTS configuration parameter,
the workload for this node might be too high. The following value
is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Max Agents The current value of
the maximum number of existing agents. This value is the maximum
number of database manager agents available at any given time to accept
application requests. This value limits the total number of applications
that can connect to all databases in the DB2 instance
at a given time. The value of the maxagents attribute must be the
sum of the values of the maxappls attribute in each database that
is allowed to be accessed concurrently. Increasing the value of the
maxagents attribute can increase resource use because resources for
each agent are allocated when the DB2 instance
is started. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Max Conc Agents The maximum number
of database manager coordinator agents that can concurrently run a
database manager transaction in the DB2 instance
during the monitoring interval. When this monitor is used with DB2 Universal database servers,
the maxcagents value is the default. This value is the maximum number
of database manager agents that can be concurrently executing a database
manager transaction. Use the maxcagents attributes to control the
load on the system during periods of high simultaneous application
activity. A value of -1 indicates that the limit is equal to the maximum
number of agents (the MAXAGENTS parameter). The maxcagents parameter
does not limit the number of applications that can have connections
to the database.
Max Coord Agents The maximum number
of database manager coordinating agents that can exist on a server
in a partitioned or nonpartitioned database environment. One
coordinating agent is acquired for each local or remote application
that connects to a database or attaches to an instance. Requests that
require an instance attachment include CREATE DATABASE, DROP DATABASE,
and Database System Monitor commands.
Mon Heap Size The current value
(in units of 4-KB pages) of the database system monitor heap size. This
value is the amount of memory that is allocated for database system
monitor data. A value of zero prevents the database manager from collecting
database system monitor data.
Node Name For new installations
of version 6, release 2, the format is instanceid:hostname:UD for
all operating systems. The format for version 6, release 1 of
the DB2 agent on Windows systems is instanceid:hostname:UD;
on UNIX and Linux® systems, the format is instanceid:hostname.
Piped Sort Hit Ratio Percent for Interval The
piped sort hit ratio (as a percentage) for the last monitoring interval. The
piped sort hit ratio is the ratio of piped sorts accepted to piped
sorts requested.
Piped Sorts Accepted The number
of piped sorts that have been accepted. When the number of accepted
piped sorts is low compared to the number requested, you can improve
sort performance by adjusting one or both of the following configuration
parameters:
If piped sorts are being rejected, consider decreasing your sort
heap or increasing your sort heap threshold. Be aware of the possible
implications of these options:
- If you increase the sort heap threshold, more memory might remain
allocated for sorting. This can cause the paging of memory to disk.
- If you decrease the sort heap, an extra merge phase (which can
slow down the sort) might be required.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Piped Sorts Accepted Percent The
percentage of piped sorts that have been accepted. The percentage
is calculated by dividing the value of the Piped Sorts Accepted attribute
by the value of the Piped Sorts Requested attribute. Use this attribute
to determine whether the value of the Piped Sorts Accepted attribute
is in an acceptable range.
Piped Sorts Rejected for Interval The
total number of piped sorts that were rejected during the monitoring
interval. In the return phase of sorting, if the sorted information
can return directly through the sort heap, it is a piped sort. However,
even if the optimizer requests a piped sort, this request is rejected
at run time if the total amount of sort heap memory for all sorts
on the database is close to exceeding the sheapthres value. If this
returned value is high compared to the total number of sorts requested,
consider decreasing your sort heap (using the sortheap configuration
parameter) or increasing your sort heap threshold (using the sheapthres
configuration parameter). However, be aware of the implications of
these options. If you increase the sort heap threshold, more memory
can remain allocated for sorting, causing the paging of memory to
disk. If you decrease the sort heap, you can require an extra merge
phase that can slow down the sort. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Piped Sorts Rejected Percent for Interval The
percentage of piped sort requests that were rejected for the DB2 instance during the monitoring
interval. In the sort return phase, if the sorted information
can return directly through the sort heap, it is a piped sort. However,
even if the optimizer requests a piped sort, this request is rejected
at run time if the total amount of sort heap memory for all sorts
on the database is close to exceeding the sheapthres value. If this
returned value is high compared to normal operating levels, consider
decreasing your sort heap (using the sortheap configuration parameter)
or increasing your sort heap threshold (using the sheapthres configuration
parameter). However, be aware of the implications of these options.
If you increase the sort heap threshold, more memory can remain allocated
for sorting, causing the paging of memory to disk. If you decrease
the sort heap, you can require an extra merge phase that can slow
down the sort.
Piped Sorts Requested The number
of piped sorts that have been requested. Because piped sorts
might reduce disk I/O, allowing more piped sorts can improve the performance
of sort operations and possibly the performance of the overall system.
A piped sort is not accepted if the sort heap threshold is exceeded
by allocating the requested sort heap. See the Piped Sorts Accepted
attribute for more information if piped sorts are being rejected.
The SQL EXPLAIN output shows whether the optimizer requested a piped
sort. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Post Threshold Hash Joins The
total number of times that a hash join heap request was limited due
to the concurrent use of shared or private sort heap space. If
this value is large (for example, greater than 5% of Hash Join Overflows),
you must consider increasing the sort heap threshold. The following
value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Post Threshold OLAP Funcs The
number of OLAP functions that have requested a sort heap after the
sort heap threshold has been exceeded. If the value of this attribute
is high, increase the sort heap threshold (sheapthres). The following
value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Post Threshold Sorts The number
of sorts that have requested heaps after reaching the sort heap threshold. By
modifying the sort heap threshold and sort heap size configuration
parameters, you can improve the performance of sort operations or
the overall system. If the value of this attribute is high, you can
do one of the following actions:
- Increase the sort heap threshold (sheapthres).
- Adjust applications to use fewer or smaller sorts by using SQL
query changes.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Priority of Agents The current value
of the priority of agents. This value is the priority that the
operating system scheduler gives to agent and other database manager
instance processes and threads. This priority determines how the operating
system gives CPU time to the DB2 processes
and threads relative to the other processes and threads running on
the system. A value of -1 indicates that no special action is taken
and the operating system schedules the database manager in the normal
way that it schedules all processes and threads. Any other value indicates
that the database manager creates its processes and threads with a
static priority set to this value.
Product Version The product and
version that is running on the DB2 instance. Valid
format is PPPVVRRM, where the following measures apply:
| Value |
Description |
| PPP |
SQL |
| VV |
2-digit version number (with high-order 0 in the
case of a 1-digit version) |
| RR |
2-digit release number (with high-order 0 in the
case of a 1-digit release) |
| M |
1-digit modification level |
Query Heap Size The maximum amount
of memory that can be allocated for the query heap within the DB2 instance during the monitoring
interval. Use a query heap to store each query in the private
memory of the agent. Use the results from the aslheapsz attribute
to refine the query heap size.
RB Free The number of request blocks
that are free in the partitioned database server during the monitoring
interval. Use the returned value with the fcm_num_rqb attribute
to determine the current request block utilization. You can use this
information to refine the fcm_num_rqb attribute. The following value
is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
RB Free Bottom The minimum number
of free request blocks. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
RB Max Used Percent The percentage
of maximum FCM request blocks used during processing within the partitioned
database server. If the percentage of maximum FCM request blocks
used is high compared to normal operating levels, you can adjust the
fcm_num_rqb attribute.
RB Used Percent The percentage
of FCM request blocks used within the partitioned database server
during the monitoring interval. If the percentage of FCM request
blocks used is high compared to normal operating levels, you can adjust
the fcm_num_rqb attribute.
Remote Connections The current
number of connections initiated from remote clients to the instance
of the database manager that is being monitored. This attribute
shows the number of connections from remote clients to databases in
this instance. This value changes frequently. As a result, you must
sample the data at specific intervals over an extended period of time
to get a realistic view of system usage. This number does not include
applications that were initiated from the same instance as the database
manager. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Remote Connections Executing The
number of remote applications currently connected to a database and
currently processing a unit of work within the database manager instance
being monitored. By using this number, you can determine the
level of concurrent processing occurring on the database manager.
This value changes frequently. As a result, you must sample the data
at specific intervals over an extended period of time to get a realistic
view of system usage. This number does not include applications that
were initiated from the same instance as the database manager. The
following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Req IO Blk The current value
(in byte units) of the client input and output block size. This
value is the amount of memory that is allocated for the communication
buffer between remote applications and their database agents on the
database server. When a database client requests a connection to a
remote database, this communication buffer is allocated on the client.
On the database server, a communication buffer of 32767 bytes is initially
allocated, until a connection is established and the server can determine
the value of the rqrioblk attribute at the client. In addition to
this communication buffer, this parameter is also used to determine
the input and output block size at the database client when a blocking
cursor is opened.
Snapshot Timestamp The date and
time when the database system monitor information was collected. Use
this attribute to help relate data chronologically if you are saving
the results in a file or database for ongoing analysis.
Sort Heap Allocated The total number
of allocated pages of sort heap space for all sorts at the level chosen
(database manager or database) and at the time the snapshot was taken. Memory
estimates do not include sort heap space. If excessive sorting occurs,
add the extra memory (used for the sort heap) to the base memory requirements
for running the database manager. Generally, the larger the sort heap,
the more efficient the sort. Appropriate use of indexes can reduce
the amount of sorting required. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Sort Heap Thres The current value
(in units of 4-KB pages) of the sort heap threshold. This value
is the maximum amount of memory that the database manager allocates
for piped sorts. Piped sorts perform better than non-piped sorts and
are used more often. However, their use can affect the performance.
The value of the sheapthres attribute must be at least two times the
largest sort heap that is defined for any database within the instance.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Sort Heap Used Percent The percentage
of the allocated sort heap that the DB2 instance
used during the monitoring interval.
Total Buffers Rcvd The total number
of FCM buffers received by the database node where this monitor runs. The
database node is specified in the DB2_node_number variable. Use the
returned value to measure the level of traffic between the node where
this monitor runs and another node. If the total number of FCM buffers
received from the other node is high compared to normal operating
levels, you can redistribute the database or move tables to reduce
the internode traffic. The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |
Total Buffers Sent The total number
of FCM buffers that are sent from the database node where this monitor
runs to the specified node. Use the returned value to measure
the level of traffic between the current node where this monitor runs
and the specified node. If the total number of FCM buffers sent to
the other node is high compared to normal operating levels, you can
redistribute the database or move tables to reduce the internode traffic.
The following value is valid:
| External value |
Internal value |
| Value Exceeds Maximum |
9223372036854775807 |