Caché Monitoring Guide - InterSystems Documentation

More documents

Recommendations

Info

Monitoring Caché Using the Management Portal Identifier Total SMH Pages Used Definition Total directly allocated shared memory heap (SMH) and string table allocated SMH memory, together with the total used/available memory in the static memory table (SMT) and the general string table (GST); the number of 64-KB pages is displayed parenthetically. 1.3 Monitoring Locks Caché locks are created when a Caché process issues a Lock command on a Caché entity, such as a local or global variable, as long as the entity is not already locked by another process. Entities need not exist in the database to lock them. To display or delete locks, navigate to the [System] > [Locks] page from the Operations section of the Management Portal home page. The table lists one row for each lock owner and lock waiter. If one lock is owned by more than one process, each owner has its own row. The Lock Table has the following column entries. Column Heading Owner Mode/Count Reference Directory System Remove Definition The process ID of the process holding or waiting for the lock. Contains the client system name if it is a remote lock. Lock mode and count of the lock item. If the lock count is 1 the count is not displayed. For details, see the Lock Modes table. Lock reference string of the lock item (does not include the database name). The database location of the lock item. The system name of where the lock is located, if it is the local system the column is blank. If this lock is removable, this option along with the Remove all locks for process option appears in the row. Click the appropriate option to remove the lock or remove all locks for the process. In most cases, the only time you need to remove locks is as a result of an application problem. For a more in-depth description of the Lock command and its features, see the Lock entry of the Caché ObjectScript Reference guide. You may need to enlarge the size of the lock table if your system uses a large number of locks. You can do this using the Management Portal: 1. Navigate to the [System] > [Configuration] > [Advanced Memory Settings] page. 2. In the locksiz (locksiz) row, click Edit. 3. In the locksiz box, update the amount of memory allocated on your system for locks (in bytes), and click OK. The minimum is 65536; the maximum value depends on the value of gmheap (Generic Memory Heap Size). Increase the heap size if you need more room for the lock table. Caché rounds up the value to the next multiple of 64 KB. The default range is from 65536 – 1769472. 4. Click Save and restart Caché for this information to take effect. The following table lists the possible values of the mode portion of the Mode/Count column. 8 Caché Monitoring Guide
Monitoring Log Files Table 1–10: Lock Modes Mode Exclusive Shared LockZA WaitExclusive WaitShared WaitLockZA LockPending SharePending DelockPending Lost Description Exclusive lock mode. Share lock mode. ZALLOCATE lock mode. Waiting for exclusive lock mode.* Waiting for share lock mode.* Waiting for ZALLOCATE lock mode.* Exclusive lock pending, waiting for server to grant the exclusive lock. Share lock pending, waiting for server to grant the share lock. Delock pending, waiting for server to release the lock. Lock lost due to network reset. * The Wait modes are followed by one of the following: Exact, Parent, or Child; for example, WaitShared Exact. For more detailed information and an alternative way to manage locks, see the SYS.Lock class documentation in the Caché Class Reference. You can also view and remove locks using the Caché ^LOCKTAB utility from the %SYS namespace: %SYS>Do ^LOCKTAB Node Name: DOC1 LOCK table entries at 02:13PM 07/09/2007 1174752 bytes usable, 1178448 bytes available. Entry Process X# S# Flg W# Item Locked 1) 4776 1 ^["^^c:\mycache\mgr\"]%SYS("CSP" ,"Daemon") 2) 3484 1 ^["^^c:\mycache\mgr\"]TASKMGR Command=> Enter a question mark () at the Command prompt to display the help for this utility. Important: You cannot delete a lock that is in a lock pending state. 1.4 Monitoring Log Files Caché reports general messages, system errors, certain operating system errors, and network errors through an operator console facility. For Caché Windows-based systems, there is no operator console as such and all console messages are sent to the cconsole.log file in the system manager directory, typically CacheSys\Mgr. For Caché systems on UNIX® or OpenVMS platforms, you can send operator console messages to the cconsole.log file or the console terminal. The cconsole.log file is a plain text file and may be viewed with any text editor or text viewer, or by using the Management Portal: 1. Navigate to the [System] > [System Logs] page by clicking System Logs in the Operations column of the home page. 2. Click View Console Log under the System Logs column to display the text output of the console log file. Caché Monitoring Guide 9
Page 1 and 2: Caché Monitoring Guide Version 201
Page 3 and 4: Table of Contents About This Book .
Page 5 and 6: B.4 Caché MIB Structure ..........
Page 7: About This Book This book describes
Page 10 and 11: Monitoring Caché Using the Managem
Page 18 and 19: Using the Caché Diagnostic Report
Page 24 and 25: Using the Caché Monitor The option
Page 26 and 27: Using the Caché Monitor Option 4)
Page 28 and 29: Using the Caché Monitor 3.2 Caché
Page 30 and 31: Using the Caché Monitor Option 3)
Page 32 and 33: Using the Caché Monitor Option 4 1
Page 34 and 35: Using the Caché Monitor Input Fiel
Page 36 and 37: Using the Caché Monitor 3.2.2.1 Ge
Page 38 and 39: Using the Caché Monitor { // Get f
Page 41 and 42: 4 Gathering Global Activity Statist
Page 43 and 44: Examples of ^GLOSTAT Output Statist
Page 45 and 46: Examples of ^GLOSTAT Output Map: 22
Page 47 and 48: Examples of ^GLOSTAT Output 4.3.6 E
Page 49 and 50: 5 Monitoring System Performance Usi
Page 51 and 52: Using ^PERFMON If you are running ^
Page 53 and 54: Using ^PERFMON Format: status = $$R
Page 55 and 56: Report Examples Metric Number 45 46
Page 57 and 58: 6 Monitoring Routine Performance Us
Page 59 and 60: Using ^PROFILE Option R X Descripti
Page 61: ^PROFILE Example There are 5 routin
Page 64 and 65:
Examining Routine Performance Using
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 73 and 74:
8 Monitoring Performance Using ^pBu
Page 75 and 76:
Scheduling the ^pButtons Utility wi
Page 77 and 78:
Customizing the ^pButtons Utility I
Page 79 and 80:
Customizing the ^pButtons Utility s
Page 81 and 82:
Performance Reports Created by ^pBu
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
9 Monitoring Performance Using ^mgs
Page 95 and 96:
Column RemRrefs * RouLaS RemRLaS *
Page 97:
Considering Seizes, ASeizes, and NS
Page 100 and 101:
Monitoring Caché Mirroring Perform
Page 102 and 103:
Monitoring Caché Mirroring Perform
Page 104 and 105:
Caché History Monitor • SYS.Hist
Page 107 and 108:
A Monitoring Caché Using BMC PATRO
Page 109 and 110:
Caché PATROL Knowledge Modules Arg
Page 111 and 112:
Caché Metrics Used with BMC PATROL
Page 113 and 114:
Caché Metrics Used with BMC PATROL
Page 115 and 116:
B Monitoring Caché Using SNMP This
Page 117 and 118:
Caché MIB Structure 3. When you ed
Page 119 and 120:
Caché MIB Structure The Caché sub
Page 121 and 122:
Sample User-defined SNMP Monitor Cl
Page 123:
Sample User-defined SNMP Monitor Cl
Page 126 and 127:
Monitoring Caché Using WMI 3. Sele
Page 128 and 129:
Monitoring Caché Using WMI %SYS>Do
Page 130 and 131:
Monitoring Caché Using Web Service
Page 132 and 133:
Page 134 and 135:
show all

Caché Monitoring Guide - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?