Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
라이브 도움말 보기
등록 완료
로그인
가격 산정 요청
영업 담당자에게 문의
제품 번들을 선택했습니다. 귀하의 요청에 더 적합한 서비스를 제공해 드릴 수 있도록 개별 제품을 선택해 주십시오. *
지금은 채팅에 회신할 수 있는 기술 지원 엔지니어가 없습니다. 즉각적인 서비스를 받으려면 당사의 서비스 요청 양식을 사용하여 요청을 제출하십시오.
다음 문서의 설명에 따라 문제를 해결할 수 있습니다.
Tracks how instances use DB2 pureScale cluster caching facility (CF) resources.
INSTANCE
The name of the monitored instance.
ID
The ID of the CF component.
HOST
The name of the machine that hosts the CF component.
CPU_USAGE_TOTAL
Percentage of overall CPU usage of the CF machine.
MEMORY_FREE
Amount of free physical memory (MB).
MEMORY_SWAP_FREE
Amount of free swap space (MB).
MEMORY_SWAP_TOTAL
Total amount of swap space (MB).
MEMORY_TOTAL
Total size of physical memory (MB).
MEMORY_UTILIZATION
The percentage of free memory out of the total memory assigned to the CF machine.
VIRTUAL_MEMORY_FREE
Amount of reserved virtual memory.
VIRTUAL_MEMORY_TOTAL
Total amount of virtual memory on the system (MB).
The following table provides a list of the Current Agents Details metrics that are collected, and a description for each.
DB_NAME
The name of the monitored database.
DBPARTITIONNUM
The database partition from which the data was retrieved for this row.
AGENT_ID
The unique ID for the application. On a single-partitioned database, this ID consists of a 16-bit counter. On a multi-partitioned database, this ID consists of the coordinating partition number concatenated with a 16-bit counter. In addition, this ID is the same on every partition where the application may make a secondary connection.
APPL_CON_TIME
The date and time that an application started a connection request.
APPL_NAME
The name of the application running at the client.
APPL_ID
This ID is generated when the application connects to the database. It is unique across the network. There are different formats for the application ID, which depend on the communication protocol between the client and the server machine on which the database manager resides.
APPL_STATUS
The status of the application. This element can help you diagnose potential application problems.
Values:
BACKUP
COMMIT_ACT
COMP
CONNECTED CONNECTPEND
CREATE_DB
DECOUPLED
DISCONNECTPEND
INTR
IOERROR_WAIT
LOAD
LOCKWAIT
QUIESCE_TABLESPACE
RECOMP
REMOTE_RQST
RESTART
RESTORE
ROLLBACK_ACT
ROLLBACK_TO_SAVEPOINT
TEND
THABRT
THCOMT
TPREP
UNLOAD
UOWEXEC
UOWWAIT
WAITFOR_REMOTE
NUM_ASSOC_AGENTS
The number of subagents associated with an application.
COORD_NODE_NUM
In a multi-node system, the node number of the node where the application is connected or attached to the instance.
ACTIVE_TIME
The elapsed time (in seconds) spent processing an SQL request on a host database server.
EXECUTION_ID
The ID that the user specified when logging in to the operating system. This ID is distinct from AUTH_ID, which the user specifies when connecting to the database.
AUTHORITY_LVL
This interface returns a text identifier based on the database authorities defined in sql.h and their source.
Possible “authority” values:
BINDADD
CONNECT
CREATE_EXT_RT
CREATE_NOT_FENC
CREATETAB
DBADM
IMPLICIT_SCHEMA
LIBADM
QUIESCE_CONN
SECADM
SYSADM
SYSCTRL
SYSMAINT
SYSMON
SYSQUIESCE
Possible “source” values:
USER — authority granted to the user or to a role granted to the user
GROUP — authority granted to a group to which the user belongs or to a role granted to the group to which the user belongs
CLIENT_PID
The process ID of the client application that made the connection to the database.
COORD_AGENT_PID
The ID of the coordinator agent for the application.
STATUS_CHANGE_TIME
The date and time the application entered its status.
CLIENT_PLATFORM
This interface returns a text identifier based on the client platform definition in sqlmon.h.
CLIENT_PROTOCOL
This interface returns a text identifier based on the definition in sqlmon.h.
CPIC
LOCAL
NETBIOS
NPIPE
TCPIP (for DB2® UDB)
TCPIP4
TCPIP6
TERRITORY_CODE
The territory code of the database for which the monitor data is collected.
CODEPAGE_ID
The code page at the partition where the monitored application started.
PRIMARY_AUTH_ID
The authorization ID of the user who invoked the application that is being monitored.
SESSION_AUTH_ID
The current authorization ID for the session used by this application.
CLIENT_NNAME
Deprecated by IBM.
CLIENT_DB_ALIAS
The alias of the database, provided by the application, to connect to the database.
DB_PATH
The full path of the location where the database is stored on the monitored system.
STMT_TEXT
The SQL statement text.
FOREGROUND_BACKGROUND_TYPE
The foreground or background status of the application.
ROWS_READ
This is the number of rows read from the table.
ROWS_WRITTEN
The number of rows changed (inserted, deleted, or updated) in the table.
APPL_IDLE_TIME
The amount of time (in seconds) that has passed since an application has issued any requests to the server. Includes applications that have not terminated a transaction (for example, not issued a commit or rollback).
POOL_DATA_L_READS
The number of data pages that have been requested from the buffer pool (logical) for regular and large tablespaces.
POOL_INDEX_L_READS
The number of index pages that have been requested from the buffer pool (logical) for regular and large tablespaces.
POOL_INDEX_P_READS
The number of index pages read in from the tablespace containers (physical) for regular and large tablespaces.
POOL_TEMP_DATA_L_READS
The number of data pages that have been requested from the buffer pool (logical) for temporary tablespaces.
POOL_TEMP_DATA_P_READS
The number of data pages read in from the tablespace containers (physical) for temporary tablespaces.
POOL_TEMP_INDEX_L_READS
The number of index pages that have been requested from the buffer pool (logical) for temporary tablespaces.
POOL_TEMP_INDEX_P_READS
The number of index pages read in from the tablespace containers (physical) for temporary tablespaces.
LAST_RESET
The date and time when the monitoring counters were reset.
PACKAGE_CACHE_HIT_RATIO
A ratio that indicates how well the package cache is helping to avoid the reload of packages and sections for static SQL from the system catalogs and the recompilation of dynamic SQL statements.
The indicator is calculated using the formula:
(1-(db.pkg_cache_inserts/db.pkg_cache_lookups))*100
The following table provides a list of the Agents Summary metrics that are collected, and a description for each.
ACTIVE
The number of active agents.
ACTIVE_Rate
The number of active agents per second (average active sessions).
BACKGROUND_PROCESSES
The sum of background application agents.
BACKUP_AGENTS
Indicates that the application is performing a backup of the database.
BALANCE_AVERAGE_ACTIVE_SESSIONS
The balance of average active agents across the database partitions. If most of the activity is on one partition, for example, the activity is not balanced. If most of the activity is spread equally across the partitions, it is balanced.
COMMIT_ACT_AGENTS
Indicates that the unit of work is committing its database changes.
COMP_AGENTS
Indicates that the database manager is compiling an SQL statement or precompiling a plan on behalf of the application.
CONNECTPEND_AGENTS
Indicates that the application has initiated a database connection, but the request has not yet completed.
CREATE_DB_AGENTS
Indicates that the agent has initiated a request to create a database, but that request has not yet completed.
DECOUPLED_AGENTS
Indicates that there are no agents currently associated with the application. This is a normal state. When the Connection Concentrator is enabled, there is no dedicated coordinator agent, so an application can be decoupled on the coordinator partition. In non-concentrator environments, an application cannot be decoupled on the coordinator partition, because there is always a dedicated coordinator agent.
DISCONNECTPEND_AGENTS
Indicates that the application has initiated disconnection from the database, but the command has not yet completed running. The application may not have explicitly run the database disconnect command. The database manager disconnects from a database if the application ends without disconnecting.
FOREGROUND_PROCESSES
The sum of foreground application agents.
INACTIVE
Indicates that the application is in one of three states: connected, uowwait, or decoupled.
INTR_AGENTS
Indicates that an interrupt of a request is in progress.
IOERROR_WAIT_AGENTS
Indicates that the application has detected an I/O error and is attempting to disable a particular tablespace. The application has to wait for all other active transactions on the tablespace to complete before it can disable the tablespace.
LOAD_AGENTS
Indicates that the application is performing a “fast load” of data into the database.
LOCKWAIT_AGENTS
Indicates that the unit of work is waiting for a lock. After the lock is granted, the status is restored to its previous value.
QUIESCE_TABLESPACE_AGENTS
Indicates that the application is performing a quiesce tablespace request.
RECOMP_AGENTS
Indicates that the database manager is recompiling (that is, rebinding) a plan on behalf of the application.
REMOTE_RQST_AGENTS
Indicates that the application is waiting for results from a federated data source.
RESTART_AGENTS
Indicates that the application is restarting a database in order to perform crash recovery.
RESTORE_AGENTS
Indicates that the application is restoring a backup image to the database.
ROLLBACK_ACT_AGENTS
Indicates that the unit of work is rolling back its database changes.
ROLLBACK_TO_SAVEPOINT_AGENTS
Indicates that the application is rolling back to a savepoint.
TEND_AGENTS
Indicates that the unit of work is part of a global transaction that has ended, but has not yet entered the prepared phase of the two-phase commit protocol.
THABRT_AGENTS
Indicates that the unit of work is part of a global transaction that has been heuristically rolled back.
THCOMT_AGENTS
Indicates that the unit of work is part of a global transaction that has been heuristically committed.
TOTAL_AGENTS
The total number of agents of all types.
TOTAL_AGENTS_Rate
The rate of total agents per second.
UNLOAD_AGENTS
Indicates that the application is performing a “fast unload” of data from the database.
UOWEXEC_AGENTS
Indicates that the database manager is running requests on behalf of the unit of work.
UOWWAIT_AGENTS
Indicates that the database manager is waiting on behalf of the unit of work in the application. This status typically means that the system is running in the application's code.
WAITFOR_REMOTE_AGENTS
Indicates that the application is waiting for a response from a remote partition in a partitioned database instance.
OTHER
The agents not identified by one of the agent types we show at the workload agents.
The following table provides a list of the Current Locks Wait metrics that are collected, and a description for each.
LOCK_NAME
The ID of the lock.
A system-wide unique ID for the locked wait application. On a single-partitioned database, this ID consists of a 16-bit counter. On a multi-partitioned database, this ID consists of the coordinating partition number concatenated with a 16-bit counter. In addition, this ID is the same on every partition where the application may make a secondary connection.
The application handle can be used to uniquely identify an active application (application handle is synonymous with agent ID). It can also be used as input to the FORCE APPLICATION command or API. On multi-node systems, this command can be issued from any node where the application has a connection. Its effect is global.
The full statement text of the waited (locked) agent.
LOCK_MODE
The type of lock that is being held.
This mode can help in determining the source of the contention for resources.
This element indicates one of the following, depending on the type of monitoring information being examined:
Mode Types:
NON — No Lock
IS — Intention Share Lock
IX — Intention Exclusive Lock
S — Share Lock
SIX — Share with Intention Exclusive Lock
X — Exclusive Lock
IN — Intent None
Z — Super Exclusive Lock
U — Update Lock
NS — Next Key Share Lock
NX — Next Key Exclusive Lock
W — Weak Exclusive Lock
NW — Next Key Weak Exclusive Lock
LOCK_OBJECT_TYPE
The type of object against which the application holds a lock (for object-lock-level information), or the type of object for which the application is waiting to obtain a lock (for application-level and deadlock-level information).
This element can help in determining the source of the contention for resources.
The object type IDs are defined in sqlmon.h. The objects may be one of the following types:
AGENT_ID_HOLDING_LK
Agent ID of the blocker that holds the object or the application handle of the agent holding a lock for which this application is waiting. The lock monitor group must be turned on to obtain this information.
This element can help in determining which applications are in contention for resources.
If this element is 0 (zero) and the application is waiting for a lock, indicates that the lock is held by an in-doubt transaction.
APPL_ID_HOLDING_LK
The application ID of the application that is holding a lock on the object that this application is waiting to obtain.
LOCK_WAIT_START_TIME
The date and time that this application started waiting to obtain a lock on the object that is locked by another application.
This element can help in determining the severity of resource contention.
LOCK_MODE_REQUESTED
The lock mode requested by the application.
LOCK_ESCALATION
Indicates whether a lock request was made as part of a lock escalation.
Use this element to understand the cause of deadlocks. If you experience a deadlock that involves applications doing lock escalation, you may want to increase the amount of lock memory or change the percentage of locks that any one application can request.
DATA_PARTITION_ID
The ID of the data partition for which a lock occurred.
This element is only applicable to partitioned tables.
A value of -1 represents a lock of the whole table and not a specific partition.
TABNAME
The name of the table.
Along with TABSCHEMA, this element can help in determining the source of the contention for resources.
At the application level, application-lock level, and deadlock-monitoring level, this is the table that the application is waiting to lock, because it is locked by another application. For snapshot monitoring, this item is valid only when the “lock” monitor group information is turned on, and when LOCK_OBJECT_TYPE indicates that the application is waiting to obtain a table lock.
TABSCHEMA
The schema of the table.
Along with TABNAME, this element can help in determining the source of the contention for resources.
TBSP_NAME
The name of a tablespace.
It is equivalent to the TBSPACE column in the database catalog table SYSCAT.TABLESPACES.
This element is not returned for a table lock held on a partitioned table.
LOCK_ATTRIBUTES
The lock attributes of the lock wait. If there are no locks, the text identifier is NONE; otherwise, it is any combination of the following, separated by a '+' sign:
ALLOW_NEW
DELETE_IN_BLOCK
ESCALATED
INSERT
NEW_REQUEST
RR
RR_IN_BLOCK
UPDATE_DELETE
WAIT_FOR_AVAIL
LOCK_CURRENT_MODE
During a lock conversion operation, the type of lock held before the conversion is completed. The following is an example of a scenario that describes lock conversion: During an update or delete operation, it is possible to wait for an X lock on the target row. If the transaction is holding an S or V lock on the row, this would require a conversion. The LOCK_CURRENT_MODE element is assigned a value of S or V, while the lock waits to be converted to an X lock.
LOCK_RELEASE_FLAGS
The lock release flags.
Each release flag is based on a bit flag value defined in sqlmon.h. The following are possible release flag settings (API Constant Description):
SQLM_LOCKRELFLAGS_SQLCOMPILER — Locks by SQL compiler
SQLM_LOCKRELFLAGS_UNTRACKED — Non-unique untracked locks
SUBSECTION_NUMBER
Identifies the subsection associated with the returned information.
This number relates to the subsection number in the access plan that can be obtained with db2expln.
LOCK_DURATION
The duration of the lock wait.
계열사 지원 사이트에서 Quest *제품*에 대한 온라인 지원 도움말을 볼 수 있습니다. 올바른 *제품* 지원 콘텐츠 및 지원에 연결하려면 계속을 클릭하십시오.
The document was helpful.
평가 결과 선택
I easily found the information I needed.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center
Quest Software 포털은 더 이상 IE 8, 9, 10을 지원하지 않습니다. 브라우저를 최신 버전의 Internet Explorer나 Chrome으로 업그레이드하는 것이 좋습니다.
IE 11로 업그레이드 여기를 클릭
Chrome으로 업그레이드 여기를 클릭
IE 8, 9 또는 10을 계속 사용할 경우 당사가 제공하는 뛰어난 셀프서비스 기능 모두를 최대한으로 활용하실 수 없습니다.