Download pdf - Informix KM

www.bmc.com

BMC Performance ManagerGetting Startedfor Informix

Supporting

BMC Performance Manager version 9.3 for Informix

June 2008

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© Copyright 2006-2008 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

AIX and IBM are trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both.

Linux is the registered trademark of Linus Torvalds.

Solaris and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.

UNIX is the registered trademark of The Open Group in the US and other countries.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legendU.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

http://www.bmc.com

3

Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

■ read overviews about support services and programs that BMC offers■ find the most current information about BMC products■ search a database for issues similar to yours and possible solutions■ order or download product documentation■ download products and maintenance■ report an issue or ask a question■ subscribe to receive proactive e-mail alerts when new product notices are released■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and

telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

■ product information

— product name— product version (release number)— license number and password (trial or permanent)

■ operating system and environment information

— machine type— operating system type, version, and service pack or other maintenance level such as PUT or PTF— system hardware configuration— serial numbers— related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the issue

■ commands and options that you used

■ messages received (and the time and date that you received them)

— product error messages— messages from the operating system, such as file system full— messages from related software

http://www.bmc.com/support_home

mailto:[email protected]

4 BMC Performance Manager Getting Started for Informix

ContentsChapter 1 Product components and capabilities 13

Overview of BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . 14IFMXDS.kml. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14IFMXPO.kml. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16INFORMIX.kml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Features of BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . . 18Informix component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Informix XPO component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Informix ER component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 2 Installing BMC Performance Manager for Informix 41

Verifying installation of BMC Performance Manager for Informix requirements. . . 42Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Check for product patches or fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 45Determining whether to install locally or remotely . . . . . . . . . . . . . . . . . . . . . . . . . 46Determine where to install KMs based on architecture. . . . . . . . . . . . . . . . . . . . . . 46Target computers and their roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Typical and custom installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Determining the PATROL security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing, upgrading and migrating customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Upgrading from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Automatic migration of console and agent customizations . . . . . . . . . . . . . . . . . . 52Migration of KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Location of PATROL variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Upgrade without saving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Upgrade and preserve KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Distribution server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Contents 5

Installing the online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Installing the UNIX version of the help browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Setting environment variables settings for the browser. . . . . . . . . . . . . . . . . . . . . . 71Additional considerations for using online help for UNIX . . . . . . . . . . . . . . . . . . . 73

Uninstalling BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . 74Uninstalling from a UNIX environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Uninstalling from a windows environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 3 Configuring PATROL for Informix 77

Setting up BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Loading Knowledge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Unloading knowledge modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Verifying that BMC Performance Manager for Informix is discovered. . . . . . . . . 81Saving KM changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Adding Informix instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configuring instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Deleting instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Configuring failover monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 4 Using PATROL configuration manager with BMC Performance Manager for Informix 91

Overview of PATROL configuration manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Installation and setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Setting the archive option to save backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring BMC Performance Manager for Informix instances. . . . . . . . . . . . . . 93

Using PATROL Configuration Manager to modify or remove an instance . . . . . . . . 93Configuration variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Application classes with status changes set in code . . . . . . . . . . . . . . . . . . . . . . . . . 95Modifying or deleting a configured instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Modifying the blackout configuration variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Using PATROL Configuration Manager to manage parameters . . . . . . . . . . . . . . . . . 99Deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Changing parameter thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Changing parameter polling cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Modifying parameter properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Parameters that use an event trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 5 Managing and monitoring Informix IDS and XPO servers 105

Managing Informix IDS and XPO servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Configuring and managing server instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Starting and stopping Informix servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Managing the global channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Debugging parameters and menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Changing profile statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111


Changing the response time query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Archiving and logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Loading, unloading, exporting, and importing . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Managing decision support maintenance from PATROL. . . . . . . . . . . . . . . . . . . 114

Monitoring Informix IDS and XPO servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Viewing parameters that monitor servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Viewing InfoBoxes for servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Monitoring databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Excluding or including databases for monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 119Viewing reports on databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Monitoring dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Setting up and managing dbspace monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Viewing parameters that monitor dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Viewing InfoBoxes for dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Viewing reports on dbspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Monitoring dbslices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Viewing reports on dbslices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Monitoring tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Setting up and managing table monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Viewing parameters that monitor tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Viewing InfoBoxes for tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Viewing reports on tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Monitoring logically fragmented tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Setting up and monitoring logically fragmented tables . . . . . . . . . . . . . . . . . . . . 130Viewing parameters that monitor fragmented tables . . . . . . . . . . . . . . . . . . . . . . 131

Monitoring users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Viewing parameters that monitor users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Viewing InfoBoxes for user application instances . . . . . . . . . . . . . . . . . . . . . . . . . 132Viewing reports about users, sessions, and transactions . . . . . . . . . . . . . . . . . . . 134Setting up and managing user monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Chapter 6 Managing and monitoring enterprise replication 139

Managing Informix ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Starting and stopping ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Defining ER servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Disconnecting and reconnecting ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Deleting ER servers from global catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Modifying attributes of an ER server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Suspending and resuming delivery of data to an ER server. . . . . . . . . . . . . . . . . 143Defining an ER replicate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Changing participants for a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Deleting a replicate from the global catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Modifying attributes of a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Suspending and resuming delivery of data to a replicate. . . . . . . . . . . . . . . . . . . 145Starting and stopping replication for a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . 145Defining a replicate group or set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Changing replicates for a replicate group or set . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Deleting a replicate group or set from ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Contents 7

Modifying attributes of a replicate group or set . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Suspending and resuming delivery to a replicate group or set . . . . . . . . . . . . . . 146

Monitoring Informix ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Viewing InfoBoxes for ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Viewing replication reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Monitoring ER servers and server groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing parameters that monitor ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing InfoBoxes for ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing replication reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Viewing reports on ER servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Monitoring ER replicate groups or sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Viewing the InfoBox for replicate groups or sets . . . . . . . . . . . . . . . . . . . . . . . . . . 151Viewing reports on replicate groups or sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Monitoring ER replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Viewing InfoBoxes for replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Viewing a report on replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Monitoring ER participants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Viewing InfoBoxes for participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Viewing a report on participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Monitoring ER queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Viewing InfoBoxes for ER queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Viewing parameters that monitor queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Monitoring ER spool directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Viewing InfoBoxes for ER spool directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Viewing parameters that monitor the spool directories. . . . . . . . . . . . . . . . . . . . . 159

Monitoring ER threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Viewing reports on threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Viewing a list of ER threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Column headings defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Abbreviations defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Parameter dependencies for the Informix component . . . . . . . . . . . . . . . . . . . . . . . . . 208Parameter dependencies for the Informix XPO component . . . . . . . . . . . . . . . . . . . . 213Parameter dependencies for the Informix ER component . . . . . . . . . . . . . . . . . . . . . . 216Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218


FiguresUpgrading overview for BMC Performance Manager for Informix . . . . . . . . . . . . . . 57Overview of migration process using PATROL migration tools . . . . . . . . . . . . . . . . . 60Primary computer console before failover configuration . . . . . . . . . . . . . . . . . . . . . . . 86Secondary computer console before failover configuration . . . . . . . . . . . . . . . . . . . . . 87Failover Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Configuring Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Failover report after failover start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Get command in PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Figures 9


Tables.km files in IFMXDS.kml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.km files in IFMXPO.kml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.km Files in INFORMIX.kml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Applications and icons for the Informix component . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Applications and icons for the Informix XPO component . . . . . . . . . . . . . . . . . . . . . . 31Applications and Icons for the Informix ER component . . . . . . . . . . . . . . . . . . . . . . . . 34Requirements for BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . 42Default values for PATROL location variables in windows . . . . . . . . . . . . . . . . . . . . . 54Default Values for PATROL Location Variables in UNIX . . . . . . . . . . . . . . . . . . . . . . 55.kml files provided by BMC Performance Manager for Informix . . . . . . . . . . . . . . . . 79Variables for BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . 94Places where event_trigger calls are made . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103IFMXDS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117IFMXPO application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118IFMXDS_DBS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122IFMXPO_DBS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123IFMXDS_TBS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127IFMXPO_TBS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128IFMXDS_USER application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132IFMXPO_USER application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133IFMXER application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147IFMXER_SERVER application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148IFMXER_SERVERGRP application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Fields in the IFMXER Servers report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150IFMXER_REPLGRP or SETS application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151IFMXER_REPLICATE application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Fields in the Replicates Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154IFMXER_PARTICIPANT application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Fields in the Participants Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156IFMXER_QUEUE Application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157IFMXER_SPOOL application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158IFMXER_SPOOLDIR application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158IFMXER_SPOOLFILE application InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Fields in the ER Threads Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Enterprise replication threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Accessing KM commands and infoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165BMC Performance Manager for Informix parameters . . . . . . . . . . . . . . . . . . . . . . . . . 171Informix Component Collector and Consumer Dependencies . . . . . . . . . . . . . . . . . 209XPO component collector and consumer dependencies . . . . . . . . . . . . . . . . . . . . . . . 213

Tables 11

ER component collector and consumer dependencies . . . . . . . . . . . . . . . . . . . . . . . . . 216BMC Performance Manager for Informix agent configuration variables . . . . . . . . . 218


C h a p t e r 1
1 Product components and capabilities
This chapter provides information about the components, features, and organization of BMC Performance Manager for Informix product. This chapter presents the following topics:

Overview of BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . 14IFMXDS.kml. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14IFMXPO.kml. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16INFORMIX.kml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Features of BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . . 18Informix component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Informix XPO component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Informix ER component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 1 Product components and capabilities 13

Overview of BMC Performance Manager for Informix

Overview of BMC Performance Manager for Informix

The BMC Performance Manager for Informix product contains knowledge in the form of applications, commands, parameters, and recovery actions that PATROL uses to monitor, analyze, and manage your Informix servers. This knowledge is delivered in the form of .km files. The components of BMC Performance Manager for Informix use .km files to monitor and manage the Informix servers. BMC Performance Manager for Informix contains the following components:

■ Informix■ Informix with Enterprise Replication (Informix ER)■ Informix with Extended Parallel Option (Informix XPO)

Each component provides separate applications, commands, parameters, and recovery actions that help you to monitor, manage, configure, and control specific Informix products. These components are delivered in the following .kml files:

■ IFMXDS.kml contains Informix and Informix ER .km files.■ IFMXPO.kml contains Informix XPO .km files.■ INFORMIX.kml contains Informix, Informix ER, and Informix XPO .km files.

IFMXDS.kml

The IFMXDS.kml file contains .km files that monitor the Informix Online and Informix Dynamic Servers and Informix servers with the Enterprise Replication option. The IFMXDS.kml file monitors the following Informix OnLine and Dynamic Servers:

■ Informix OnLine Server■ Informix Dynamic Server versions

The IFMXDS.kml file also monitors the Informix Enterprise Replication option that is provided in Informix Dynamic Server.

WARNING BMC Performance Manager for Informix does not support Informix Dynamic Server versions 7.3.UC3 through 7.3.UC5, 7.3.FC3 through 7.3.FC5, and 7.3.HC3 through 7.3.HC5 on UNIX®. In some situations, your Informix server may crash or create a blocked checkpoint if you are running these versions of Informix. Because of these problems, BMC Performance Manager for Informix does not discover these versions of Informix.


IFMXDS.kml

Table 1 lists the .km files in IFMXDS.kml that monitor Informix online and Dynamic Servers and the Informix Enterprise Replication option.

Table 1 .km files in IFMXDS.kml

.km files that monitor Informix onLine and dynamic servers .km files that monitor Informix ER servers

INFORMIX.km IFMXER.km

IFMXDS.km IFMXER_COLLECTORS.km

IFMXDS_AVAILABILITY.km IFMXER_PARTICIPANT.km

IFMXDS_CAPACITY.km IFMXER_QUEUE.km (does not apply to Informix version 9.30 and later)

IFMXDS_COLLECTORS.km IFMXER_QUEUELIST.km (does not apply to Informix version 9.30 and later)

IFMXDS_DBS.km IFMXER_REPLGRP.km or IFMXER_REPLSETS.km (Informix version 9.30 and later)

IFMXDS_DBS_CHK.km IFMXER_REPLICATE.km

IFMXDS_DBSTEMP.km IFMXER_REPLLIST.km

IFMXDS_DBSTEMP_CHK.km IFMXER_SERVER.km

IFMXDS_FRAG.km IFMXER_SERVERGRP.km

IFMXDS_FRAG_EXT.km IFMXER_SPOOL.km

IFMXDS_FRAG_SUM.km IFMXER_SPOOLDIR.km

IFMXDS_PDQ.km IFMXER_SPOOLFILE.km

IFMXDS_PERFORMANCE.km IFMXER_THREAD.km

IFMXDS_SPACE.km IFMXER_THREADLIST.km

IFMXDS_TABLES.km

IFMXDS_TBS.km

IFMXDS_USER.km

IFMXDS_USERS.km


IFMXPO.kml

IFMXPO.kml

The IFMXPO.kml file contains the .km files that monitor the following Informix products:

■ Informix Extended Parallel Server (XPS)■ Informix Dynamic Server with Extended Parallel Option (XPO)

Table 2 lists the .km files in IFMXPO.kml.

Table 2 .km files in IFMXPO.kml

.km files that monitor Informix XPS or XPO servers

INFORMIX.km

IFMXPO.km

IFMXPO_COSERVER.km

IFMXPO_CORRELATORS.km

IFMXPO_AVAILABILITY.km

IFMXPO_CAPACITY.km

IFMXPO_COLLECTORS.km

IFMXPO_DBS.km

IFMXPO_DBS_CHK.km

IFMXPO_DBSTEMP.km

IFMXPO_DBSTEMP_CHK.km

IFMXPO_FRAG.km

IFMXPO_FRAG_EXT.km

IFMXPO_FRAG_SUM.km

IFMXPO_PERFORMANCE.km

IFMXPO_SPACE.km

IFMXPO_TABLES.km

IFMXPO_TBS.km

IFMXPO_USER.km

IFMXPO_USERS.km


INFORMIX.kml

INFORMIX.kml

INFORMIX.kml contains all of the .km files in IFMXDS.kml and IFMXPO.kml, and so it contains all of the .km files necessary to monitor all of the Informix servers supported by BMC Performance Manager for Informix.

Table 3 lists the .km files in INFORMIX.kml.

:

Table 3 .km Files in INFORMIX.kml

.km files that monitor Informix online and Dynamic Servers

.km files that monitor Informix XPS or XPO servers

.km files that monitor Informix ER servers

INFORMIX.km IFMXPO.km IFMXER.km

IFMXDS.km IFMXPO_COSERVER.km IFMXER_COLLECTORS.km

IFMXDS_AVAILABILITY.km IFMXPO_CORRELATORS.km IFMXER_PARTICIPANT.km

IFMXDS_CAPACITY.km IFMXPO_AVAILABILITY.km IFMXER_QUEUE.km (does not apply to Informix version 9.30 and later)

IFMXDS_COLLECTORS.km IFMXPO_CAPACITY.km IFMXER_QUEUELIST.km (does not apply to Informix version 9.30 and later)

IFMXDS_DBS.km IFMXPO_COLLECTORS.km IFMXER_REPLGRP.km or IFMXER_REPLSETS.km (Informix version 9.30 and later)

IFMXDS_DBS_CHK.km IFMXPO_DBS.km IFMXER_REPLICATE.km

IFMXDS_DBSTEMP.km IFMXPO_DBS_CHK.km IFMXER_REPLLIST.km

IFMXDS_DBSTEMP_CHK.km IFMXPO_DBSTEMP.km IFMXER_SERVER.km

IFMXDS_FRAG.km IFMXPO_DBSTEMP_CHK.km IFMXER_SERVERGRP.km

IFMXDS_FRAG_EXT.km IFMXPO_FRAG.km IFMXER_SPOOL.km

IFMXDS_FRAG_SUM.km IFMXPO_FRAG_EXT.km IFMXER_SPOOLDIR.km

IFMXDS_PDQ.km IFMXPO_FRAG_SUM.km IFMXER_SPOOLFILE.km

IFMXDS_PERFORMANCE.km IFMXPO_PERFORMANCE.km IFMXER_THREAD.km

IFMXDS_SPACE.km IFMXPO_SPACE.km IFMXER_THREADLIST.km

IFMXDS_TABLES.km IFMXPO_TABLES.km

IFMXDS_TBS.km IFMXPO_TBS.km

IFMXDS_USER.km IFMXPO_USER.km

IFMXDS_USERS.km IFMXPO_USERS.km


Features of BMC Performance Manager for Informix

Features of BMC Performance Manager for Informix

The components of BMC Performance Manager for Informix offer unique features.

Informix component

The Informix component of BMC Performance Manager for Informix helps you manage and monitor your Informix online Servers and Informix Dynamic Servers (for version numbers, see “IFMXDS.kml” on page 14) by providing several features.

Provides commands for the administration of BMC Performance Manager for Informix

The menu commands under KM Admin perform administration and maintenance functions on BMC Performance Manager for Informix.

Blacks out instances for a user-defined period of time

You can stop PATROL from issuing warnings and alarms for selected instances for a user-defined period of time by using the Blackout Instance(s) menu command.

The blackout instance(s) menu command enables you to stop PATROL from issuing warnings and alarms for selected instances for a user-defined period of time.

Maintains channel

PATROL uses one global channel per instance to gather information from the database. The global channel name is SMIChannel.instName. PATROL uses the SMICollector when one is available; otherwise, it uses the Informix DBACCESS utility.

You can restart the global channel for a selected instance by using the KM Admin => Channel Admin or Global Channel Admin => Restart Global Channel menu command.

You can limit the number of local channels PATROL uses by using the KM Admin => Channel Admin or Global Channel Admin => Local Channel Limit menu command.


Informix component

Enable multiple-user access in administration mode

The administration mode replaces the single-user mode to access the database server to perform multiple administrative tasks. The single -user mode allowed only the informix user or a DBSA group user to connect to database server in the administration mode. You can dynamically allow one or more specific users to connect to the database server in the administration mode. The administration mode is enabled by using the onmode or oninit command options from IDS Instance -> KM Commands -> Informix Admin -> Tools -> Onmode, the ADMIN_MODE_USERS from IDS Instance => USERS => KM Commands => KM Admin => User Admin, and the ADMIN_USER_MODE_WITH_DBSA configuration variable.

Monitors error log

The error log (as defined by the Informix MSGPATH configuration parameter) is monitored at a specified interval to determine whether any critical messages were written to the log.

You can define error messages that you want written to the log and remove user-defined error messages, as well as generate lists of other errors by using the KM Admin => Error Log Admin menu commands.

Configures instances

BMC Performance Manager for Informix automatically discovers existing instances for most Informix versions when all the required .km files are loaded. During discovery, these instances are partially configured. You can complete the configuration process using the Configure Instances menu commands.

Excludes databases from monitoring

Using the Exclude or Include => Database Exclude or Include menu command, you can select the databases that you want PATROL to monitor.

Excludes dbspaces from monitoring

Using the Exclude or Include => Dbspace Exclude or Include menu command, you can select the dbspaces that you want the Onstat_dMonitor and TempDBSpaceMonitor collector parameters to monitor. By default, all dbspaces are included.

Includes dbspaces for monitoring by DBSpaceMonitor

Using the Dbspace Monitoring Admin =>Monitor by Dbspace menu command, you can select the dbspaces that you want the DBSpaceMonitor collector parameter to monitor. By default, all dbspaces are excluded.


Informix component

Monitors temp Dbspaces

PATROL monitors the temporary dbspaces only when tempdbs is defined by the DBSPACETEMP onconfig parameter before the server is brought online.

PATROL monitors temp dbspaces to determine whether there is enough space to manage the storage of temporary tables created by sorts, backups, and implicit or non-logging explicit table declarations.

Provides commands for the administration of Informix servers

BMC Performance Manager for Informix provides menu commands that you can use to perform administration of monitored Informix servers from PATROL.

Shuts down servers gracefully

The Start and Stop Server => Stop Server menu command takes the SMICollector offline before shutting down the Informix instance.

Accesses Informix utilities

BMC Performance Manager for Informix provides menu commands that you can use to access the following Informix tools: Dbaccess, Oncheck, Onparams, Onspaces, Onstat, Onstat-g, Onstat-i, Onmode. It also provides menu commands that you can use to enter and execute user-defined SQL commands and SQL scripts.

Monitors the status of monitored instances

The InstanceStatusMonitor collector parameter monitors the status of all monitored instances. This collector parameter resides under the INFORMIX application (but it is not displayed on your screen). It sets the value for the InstanceStatus consumer parameter that resides in the Availability application of each instance.

Monitors ON-Bar activity

The OnBarActivityStatus standard parameter examines the ON-Bar Activity Log for warnings and errors.


Informix component

Monitors Informix decision support resources

PATROL monitors the Informix Dynamic Server decision support resources by using the IFMXDS_PDQ (parallel database query) application. You can enter the values for the Informix parameters that determine the resources that are allocated for PDQ by using the Informix Admin => Decision Support Maint (PDQ) menu command.

The Onconfig DS_NONPDQ_QUERY_MEM parameter allows you to allocate more than 128K memory for a NONPDQ query. To enable the NONPDQ query set the MAX_PDQPRIORITY parameter to 0. Select KM Commands => Informix Admin => Decision Support Maint(PDQ) from the menu command.

Displays BMC Performance Manager for Informix events

Each parameter with an automatic recovery action creates an event. If a PATROL event fails, a message is displayed in the PATROL Event Manager. For example, if a parameter goes into alarm or a collector parameter fails, a message is sent to the PATROL Event Manager.

Monitors page flushes

The page flushes are monitored to count each type of write that flushes pages to disk. Special attention is focused on the number of foreground writes and page cleaners that are down.

Monitors profiles

PATROL monitors all profiles, including the reads and writes from disk and from buffers, the number of pages that are read or written, and the type and number of ISAM calls that are executed. You can also administer the way the profile statistics are gathered and to bring all profile counts back to zero through the Profile Statistics Admin menu command.

Monitors physical and logical logs

The physical log and logical log buffers are monitored for the number of pages and the percentage of pages that are used.

Monitors Dbspaces, including metadata for blob spaces

The IFMXDS_DBS application provides parameters that display data on dbspaces, and data on the fullest metadata for each blob space. The IFMXDS_AVAILABILITY application provides parameters that display information about the space that is used, including metadata that is used for each blob space.


Informix component

Monitors the response time for each server

BMC Performance Manager for Informix monitors the response time of each server by executing a default query that measures the amount of time it takes for the server to respond to each user and by charting the response time over time. You can replace the default query with one that fits your needs.

Automatically increase the number of AIOVPs

You can dynamically enable or disable the automatic increase of Asynchronous Input/Output Virtual Processors (AIOVPs) and page cleaner threads by using Performance => KM Commands => KM Admin => Auto AIOVPs menu command.

Managing server restart by using an RTO policy

You can set the amount of time, in seconds, that the Informix Dynamic Server (IDS) has to recover from a problem after you restart the server by creating a Recovery Time Objective (RTO) policy by using the Performance => KM Commands => KM Admin => Recovery Time Objective Policy menu command, which manages RTO_SERVER_RESTART database parameter.

Automatically configuring instances

The Informix application instance menu automatically configures the Informix instance to monitor all available default application classes. You can use the KM Admin => Auto Configure Instances menu command to automatically configure your Informix instances.

Monitor shared-memory residency

You can specify whether shared memory residency is enforced for the resident portion of the database server shared memory. The IDS Instance -> KM Commands -> Informix Admin -> Tools -> Onmode menu command, which manages RESIDENT database parameter. The resident portion in the database server has the buffer pools which are used to read or write in the database and improve the performance

Monitors the SQL statements processed by Informix

The SQL Snapshot feature of BMC Performance Manager for Informix takes snapshots of the SQL statements that are processed by each Informix server. The snapshots are written to an ASCII file that you specify and that is stored for the number of days that you specify. The SQL statements are saved at the server level.


Informix XPO component

Monitors tables

BMC Performance Manager for Informix analyzes the tables for each server to check for sequential scans, dead locks, and lock waits.

Excludes tables from monitoring

Using the Table Exclude or Include menu command, you can select which tables the TblMonitor collector parameter monitors.

Monitors table extents

The table extents are analyzed to determine whether the number of extents has extended past a defined threshold. Mutually exclusive algorithms monitor regular table extents and logically fragmented table extents so that they are analyzed separately and differently.

Monitors users and sessions

User sessions are monitored so that you can determine problem users and maximize throughput.

Monitors virtual processors

Virtual processors are monitored to ensure that the number of virtual processors is the same from one polling cycle to the next.

Informix XPO component

The Informix XPO component of BMC Performance Manager for Informix helps you manage and monitor your Informix Extended Parallel Servers (XPS) and Informix Dynamic Servers with Extended Parallel Option (XPO) (for version numbers, see “IFMXPO.kml” on page 16). The Informix XPO component offers many of the same features offered by the Informix component, but it specifically monitors and correlates your Informix XPO environment.

Correlation monitoring is performed on any Informix XPS or XPO server in your environment that has multiple nodes. The servers are monitored to determine whether data is distributed evenly across all nodes, including the number of reads and writes, and the amount of data that is stored among all dbspaces.


Informix ER component


The Informix ER component of BMC Performance Manager for Informix helps you manage and monitor your Informix Enterprise Replication servers (for version numbers, see “IFMXDS.kml” on page 14) by providing several features.

Consolidates replication monitoring

The Informix ER component provides one IFMXER application instance under each IFMXDS instance that provides the enterprise replication option to contain and organize all ER component applications, parameters, and commands.

Monitors, defines, and maintains ER Servers

The Informix ER component of BMC Performance Manager for Informix creates an IFMXER_SERVER application instance for each server and an IFMXER_SERVERGRP application instance for each server group that is defined in your enterprise replication environment. Besides providing instant recognition of the existence and status of these servers and server groups, these application instances provide information about each server or server group in the IFMXER_SERVER and IFMXER_ SERVERGRP application InfoBoxes.

The ERConnectState and ERServerState parameters monitor the status of your servers and server groups.

Using the menu commands under the IFMXER application instance in the Informix Admin => Server menu, you can create, define, and maintain the servers and server groups for your enterprise replication environment from the BMC Performance Manager for Informix interface. The Reports => Servers menu command accessed from the IFMXER application instance provides a report about the selected instance.

NOTE Before you can define and monitor ER in PATROL, you must have set up all prerequisites for running ER in Informix. For information about how to initiate and set up your ER environment, see the Informix Enterprise Replication manual.

NOTE You must enter a password for the Informix ER server to use these commands. If you enter a wrong password, an error message PATROL-Message-Unknown: Catalog 1/2 MsgNum 473 error message is displayed in the System Output window.



Monitors, defines, and maintains ER replicates

The ER component of BMC Performance Manager for Informix creates an IFMXER_REPLICATE or an IFMXER_ REPLGRP (or REPLSETS for Informix 9.30 and earlier) application instance for each replicate or replicate group (or replicate set) that is defined in your enterprise replication environment. It also creates an IFMXER_REPLLIST container application to hold all IFMXER_REPLICATE and IFMXER_REPLGRP (or REPLSETS) application instances. Besides providing instant recognition of the existence and status of these replicates and replicate groups, these application instances provide information about each replicate or replicate group in the IFMXER_REPLICATE and IFMXER_ REPLGRP (or REPLSETS) application InfoBoxes.

ERConnectState and ERServerState parameters monitor the status of your servers and server groups.

Using the menu commands under the IFMXER application instance in the Informix Admin => Replicate menu, you can create, define, and maintain the replicates and replicate groups for your enterprise replication environment from the BMC Performance Manager for Informix interface. The Reports => Replicates and Reports=> Replicate Groups menu commands that are accessed from the IFMXER application instance provide reports about the replicates and replicate groups in your ER environment.

Monitors, defines, and maintains ER participants

The ER component of BMC Performance Manager for Informix creates an IFMXER_PARTICIPANT application instance for each ER participant that is defined in your enterprise replication environment. Besides providing instant recognition of the existence and status of the participants, these application instances provide information about participants in the IFMXER_PARTICIPANT InfoBox.

Using the Informix Admin => Server => Define menu command accessed from the IFMXER application instance, you can define the location of ER send and receive queues. Using the Informix Admin => Server => Modify menu command accessed from the IFMXER application instance, you can modify the location of the ER receive queue. The Reports => Participants menu command provides a report about the participants.

Monitors, defines, and maintains ER spool directories

The ER component of BMC Performance Manager for Informix creates an IFMXER_SPOOLDIR application instance for the aborted-transaction spool (ATS) directory and the row-information spool (RIS) directory that is defined in your enterprise replication environment. The ER component also creates an IFMXER_SPOOLFILE application instance for each ATS and RIS file. It also creates an IFMXER_SPOOL container application to hold all IFMXER_SPOOLDIR and



IFMXER_SPOOLFILE application instances. Besides providing instant recognition of the existence and status of these directories and the files that they contain, these application instances provide information about ATS and RIS directories in the application InfoBoxes.

The ERRISSpool, ERRISSpace, ERATSSpool, and ERATSSpace parameters monitor the status of the ATS and RIS directories.

Using the Informix Admin => Server => Define menu command accessed from the IFMXER application instance, you can define the location of the ER send and receive queues. Using the Informix Admin => Server => Modify menu command accessed from the IFMXER application instance, you can modify the location of the ER receive queue.

Monitors, defines, and maintains ER send and receive queues

The ER component of BMC Performance Manager for Informix creates an IFMXER_ QUEUE application instance for the send and receive queues that are defined in your enterprise replication environment. It also creates an IFMXER_QUEUES container application to hold all IFMXER_QUEUE application instances. Besides providing instant recognition of the existence and status of these queues, these application instances provide information about send and receive queues in the IFMXER_QUEUE application InfoBoxes.

The ERSendQueue and ERReceiveQueue parameters monitor the status of the send and receive queues.

Using the Informix Admin => Server => Define accessed from the IFMXER application instance, you can define the location of the ER send and receive queues. Using the Informix Admin => Server => Modify menu command accessed from the IFMXER application instance, you can modify the location of the ER receive queue.

Monitors, defines, and maintains ER threads

The ER component of BMC Performance Manager for Informix creates an IFMXER_ THREAD application instance for each thread that is used by your enterprise replication system. It also creates an IFMXER_THREADLIST container application to hold all IFMXER_THREAD application instances. These application instances provide instant recognition of the existence and status of the threads that are used by ER.

NOTE IFMXER_QUEUES and IFMXER_QUEUE application instances do not apply for instances of Informix version 9.30 and later.


Product architecture

The Reports => Threads menu command accessed from the IFMXER application instance provides a report about the ER threads.

Product architectureBMC Performance Manager for Informix provides parameters, menu commands, and InfoBoxes that are organized and presented under application classes. This section describes these functional components of BMC Performance Manager for Informix and how they are accessed.

Application classes

The application classes are represented by icons. BMC Performance Manager for Informix displays the application icons in a hierarchical structure that groups all Informix instances under the INFORMIX application icon.

BMC Performance Manager for Informix includes application classes that fall into one or more of the following types:

For more information about the applications, see the BMC Performance Manager for Informix online Help. For instructions about how to access the online Help, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Informix component—applications and icons

The Informix component uses application classes to help you monitor and manage Informix On-Line Servers and Informix Dynamic Servers (for specific versions, see “IFMXDS.kml” on page 14).

Table 4 contains a description of each application class and a graphic of the icon that represents each application class that the Informix component of BMC Performance Manager for Informix provides.

Application type Description

discovery discovers the Informix instances in your environment

container enables the organization and display of parameters and menu commands by function

functional uses specific parameters, menu commands, and InfoBox items to provide information about a specific database object


Application classes

Table 4 Applications and icons for the Informix component (part 1 of 3)

Application Name and Icon Definition

INFORMIX The INFORMIX application is the main application class for BMC Performance Manager for Informix. This application discovers and contains all of the Informix instances in your environment and provides menu commands that you can use to begin the setup or configuration of BMC Performance Manager for Informix.

IFMXDS An IFMXDS application discovers and contains all of the applications for an Informix Dynamic Server instance. An IFMXDS application is created for each Informix Dynamic Server version 7.x, 9.x or 10.x that is detected and that is supported by BMC Performance Manager for Informix. You can also manually add Informix version 5.x instances that are supported by BMC Performance Manager for Informix.

Availability An IFMXDS_AVAILABILITY (Availability) application contains the parameters that check on the availability of the selected server and its resources, including space and virtual processes, and the parameters that check on archival and error log activity. An Availability instance is created for each monitored Informix Dynamic Server.

Capacity An IFMXDS_CAPACITY (Capacity) application contains the parameters that pertain to the capacity of the selected server, such as user connections, locks, waits, and physical log size. A Capacity instance is created for an Informix instance if during configuration you selected to have the instance monitored by the Capacity application.

Collectors An IFMXDS_COLLECTORS (Collectors) application contains the collector and the standard collector parameters that set the values for consumer parameters. A Collectors instance is created for each monitored Informix Dynamic Server.

Dbspace An IFMXDS_DBS (Dbspace) application provides specific parameters, menu commands, and InfoBox items pertaining to the dbspaces that the Dbspace application icon represents. DBSpace instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace for monitoring.

Dbspace Chunk An IFMXDS_DBS_CHK (Dbspace Chunk) application provides specific parameters, menu commands, and InfoBox items pertaining to the chunks in the selected dbspace. A Dbspace Chunk application instance is created for each Dbspace instance that has chunks. DBSpace Chunk instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace with chunks for monitoring.

Temp Dbspace An IFMXDS_DBSTEMP (Temp Dbspace) application provides specific parameters, menu commands, and InfoBox items pertaining to the temporary dbspace that the Temporary Dbspace application icon represents. Temp Dbspace instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a temporary dbspace for monitoring.


Application classes

Temp Dbspace Chunk An IFMXDS_DBSTEMP_CHK (Temp Dbspace Chunk) application provides specific parameters, menu commands, and InfoBox items pertaining to the temporary database chunks for a temp dbspace. Temp Dbspace chunk instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a temporary dbspace that has chunks for monitoring.

Frag An IFMXDS_FRAG (Frag) application provides specific parameters, menu commands, and InfoBox items pertaining to the fragmented table that the Frag application icon represents. Frag application instances are not created unless you have used the Fragment Monitoring Admin menu command to set up the monitoring of fragmented tables.

Frag Extent An IFMXDS_FRAG_EXT (Frag Extent) application provides specific parameters, menu commands, and InfoBox items pertaining to the fragmented table extent that the Frag Extent application icon represents. A Frag Extent instance is created for each fragmented extent that is detected for the selected fragmented table instance. Frag Extent instances are not created unless you have used the Frag Monitoring Admin menu command to set up the monitoring of fragmented tables.

Frag Summary An IFMXDS_FRAG_SUM (Frag Summary) application provides specific parameters, menu commands, and InfoBox items that pertain to the fragmented tablespaces that are contained in the server. Frag Summary instances are created when the FragChecker parameter detects more fragmented tables for the instance than the maximum number set by using the Set Logical Fragment Threshold menu command. Frag Summary instances are not created unless you have used the Frag Monitoring Admin menu command to set up the monitoring of fragmented tables.

PDQ An IFMXDS_PDQ (PDQ) application provides specific parameters, menu commands, and InfoBox items that pertain to the Parallel Database Queries (PDQ) or the Decision Support system for the Informix Dynamic Server. A PDQ instance is created for an Informix instance if during configuration you selected to have the instance monitored by the PDQ application.

Performance An IFMXDS_PERFORMANCE (Performance) application contains the parameters that pertain to the performance of the selected server, such as response time in seconds, the number of foreground writes, and the read ahead rate. A Performance instance is created for an Informix instance if during configuration you selected to have the instance monitored by the Performance application.

Space An IFMXDS_SPACE (Space) application provides a container for the Dbspace and Temp Dbspace applications, and commands that help you monitor space. The Space application instances are created by the TBSMonitor and DBSpaceMonitor collector parameters. Space application instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace for monitoring.




Application classes

Informix XPO component—applications and icons

The Informix XPO component uses application classes to help you monitor and manage the Informix Extended Parallel Server or Informix Dynamic Server with Extended Parallel Option (for specific versions, see “IFMXPO.kml” on page 16) in your environment.

Table 5 on page 31 contains a description of each application class and a graphic of the icon that represents each application class that the Informix XPO component of BMC Performance Manager for Informix provides.

Tables An IFMXDS_TABLES (Tables) application provides a container for the TBS instances. Tables application instances are created by the TBSMonitor and FragMonitor collector parameters. A Tables application instance is not created unless you have used the Table Monitoring Admin menu command to set up table monitoring.

Table Spaces (TBS) An IFMXDS_TBS (TBS or Table Spaces) application provides parameters, menu commands, and InfoBox items that pertain to Table Spaces. A TBS instance is not created unless you have used the Table Monitoring Admin menu command to set up table monitoring. TBS instances are created by the TBSMonitor collector parameter.

User An IFMXDS_USER (User) application provides specific parameters, menu commands, and InfoBox items to monitor the user or process that is represented by the User application icon. User instances are created for an Informix instance if during configuration you selected to have the instance monitored by the Users application.

Users An IFMXDS_USERS (Users) application provides specific parameters, menu commands, and InfoBox items to monitor users and processes. The Users application also contains the User application instances. A Users instance is created for an Informix instance if during configuration you selected to have the instance monitored by the Users application.




Application classes

Table 5 Applications and icons for the Informix XPO component (part 1 of 3)


INFORMIX The INFORMIX discovery and container application is the main application class for BMC Performance Manager for Informix. This application discovers the Informix instances in your environment and provides menu commands that allow you to begin the setup or configuration.

IFMXPO An IFMXPO application discovers and contains all of the IFMXPO_COSERVER applications, and the IFMXPO_CORRELATOR application. An IFMXPO application is created for each Informix Dynamic Server with Extended Parallel Option or Informix Extended Parallel Server (Informix XPO) instance that is detected in your environment that is supported by BMC Performance Manager for Informix.

Coserver An IFMXPO_COSERVER application discovers and contains all of the applications for an Informix Dynamic Server with Extended Parallel Option or Informix Extended Parallel Server (Informix XPO) instance. An IFMXPO application is created for each Informix XPO instance that is detected and that is supported by BMC Performance Manager for Informix.

Correlator An IFMXPO_CORRELATORS (Correlator) application class instance is created beneath the Informix XPO instance. The Correlator application determines the state of all of the coservers, and releases control of that information to the correlator and collector parameters.

Availability An IFMXPO_AVAILABILITY (Availability) application contains the parameters that check on the availability of the selected server and its resources, including space and virtual processes, and the parameters that check on archival and error log activity. An Availability instance is created for each monitored Informix XPO coserver instance.

Capacity An IFMXPO_CAPACITY (Capacity) application contains the parameters that pertain to the capacity of the selected server, such as user connections, locks, waits, and physical log size. A Capacity instance is created for a coserver instance if during configuration you selected to have the instance monitored by the Capacity application.

Collectors An IFMXPO_COLLECTORS (Collectors) application contains the collector and the standard collector parameters that set the values for consumer parameters. A Collectors instance is created for each monitored Informix XPO coserver instance.

Database An IFMXPO_DBS (Dbspace) application provides specific parameters, menu commands, and InfoBox items pertaining to the dbspaces that the Dbspace application icon represents. DBSpace instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace for monitoring.


Application classes

Database Chunk An IFMXPO_DBS_CHK (Dbspace Chunk) application provides specific parameters, menu commands, and InfoBox items pertaining to the chunks in the selected dbspace. A Dbspace Chunk application instance is created for each Dbspace instance that has chunks. DBSpace Chunk instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace with chunks for monitoring.

Temporary Database An IFMXPO_DBSTEMP (Temp Dbspace) application provides specific parameters, menu commands, and InfoBox items pertaining to the temporary dbspace that the Temporary Dbspace application icon represents. Temp Dbspace instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a temp dbspace for monitoring.

Temporary Database Chunk An IFMXPO_DBSTEMP_CHK (Temp Dbspace Chunk) application provides specific parameters, menu commands, and InfoBox items pertaining to the temporary database chunks for a temp dbspace. Temp Dbspace chunk instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a temp dbspace that has chunks for monitoring.

Frag An IFMXPO_FRAG (Frag) application provides specific parameters, menu commands, and InfoBox items pertaining to the fragmented table that the Frag application icon represents. Frag application instances are not created unless you have used the Fragment Monitoring Admin menu command to set up the monitoring of fragmented tables.

Frag Extent An IFMXPO_FRAG_EXT (Frag Extent) application provides specific parameters, menu commands, and InfoBox items pertaining to the fragmented table extent that the Frag Extent application icon represents. A Frag Extent instance is created for each fragmented extent that is detected for the selected fragmented table instance. Frag Extent instances are not created unless you have used the Frag Monitoring Admin menu command to set up the monitoring of fragmented tables.

Frag Summary An IFMXPO_FRAG_SUM (Frag Summary) application provides specific parameters, menu commands, and InfoBox items that pertain to the fragmented tablespaces that are contained in the coserver. Frag Summary instances are created when the FragChecker parameter detects more fragmented tables for the coserver instance than the maximum number set by using the Set Logical Fragment Threshold menu command. Frag Summary instances are not created unless you have used the Frag Monitoring Admin menu command to set up the monitoring of fragmented tables.

Performance An IFMXPO_PERFORMANCE (Performance) application contains the parameters that pertain to the performance of the selected coserver, such as response time in seconds, the number of foreground writes, and the read ahead rate. A Performance instance is created for an Informix coserver instance if during configuration you selected to have the instance monitored by the Performance application.




Application classes

Informix ER component—applications and icons

The Informix ER component uses application classes to help you monitor and manage the Informix Dynamic Server with Enterprise Replication Option (for specific versions, see “IFMXDS.kml” on page 14) in your environment.

Table 6 contains a description of each application class and a graphic of the icon that represents each application class that the Informix ER component of BMC Performance Manager for Informix provides.

Space An IFMXPO_SPACE (Space) application provides a container for the Dbspace and Temp Dbspace applications, and commands that help you monitor space. The Space application instances are created by the TBSMonitor and DBSpaceMonitor collector parameters. Space application instances are not created unless you have used the Dbspace Monitoring Admin menu command to select a dbspace for monitoring.

Tables An IFMXPO_TABLES (Tables) application provides a container for the TBS instances. Tables application instances are created by the TBSMonitor and FragMonitor collector parameters. The Tables application instance are not created unless you have used the Table Monitoring Admin menu command to set up table monitoring.

TBS An IFMXPO_TBS (TBS or Table Spaces) application provides parameters, menu commands, and InfoBox items that pertain to Table Spaces. TBS instances are not created unless you have used the Table Monitoring Admin menu command to set up table monitoring. TBS instances are created by the TBSMonitor collector parameter.

User An IFMXPO_USER (User) application provides specific parameters, menu commands, and InfoBox items to monitor the user or process that is represented by the User application icon. User instances are created for an Informix coserver instance if during configuration you selected to have the coserver instance monitored by the Users application.

Users An IFMXPO_USERS (Users) application provides specific parameters, menu commands, and InfoBox items to monitor users and processes. The Users application also contains the User application instances. A Users instance is created for an Informix coserver instance if during configuration you selected to have the coserver instance monitored by the Users application.




Application classes

Table 6 Applications and Icons for the Informix ER component (part 1 of 2)


IFMXER The IFMXER discovery and container application is the main application class for the Informix Enterprise Replication component of BMC Performance Manager for Informix. This application discovers the Informix ER Server instances in your environment and provides menu commands that you can use to begin the set up and configuration of your Informix ER environment.

Collectors The IFMXER_COLLECTORS (ER Collectors) application contains ER collector parameters that gather data and set the values for ER consumer parameters. A Collectors instance is created for each monitored Informix ER Server instance.

Participant The IFMXER_PARTICIPANT (Participant) application class provides information about the participants that you define. A Participant application instance is created for each participant that is defined. Access a Participant application instance by clicking on a Replicate List instance, and then on a Replicate instance.

Queue The IFMXER_QUEUE (Queue) application class instances are created for each queue. The Queue application provides an InfoBox that contains information about the queue s that the instances represent. This application class provides no parameters or menu commands.

Queue List The IFMXER_QUEUELIST (Queue List) application serves as a container for the Queue application instances. A Queue List application instance is created for each IFMXER instance. This application container provides no parameters or menu commands.

Replicate The IFMXER_REPLICATE (Replicate) application class instances provide information in an InfoBox about the replicates that you define. A Replicate application instances is created for each replicate you define. This application class provides no parameters or menu commands.

Replicate Group or Sets The IFMXER_REPLGRP or IFMXER_REPLSETS (Replicate Group or Replicate Sets) application class instance is created for each replicate group or replicate set that you define. These applications provide an InfoBox that contains information about the replicate group or replicate set that it represents.

Note: With the introduction of Informix version 9.30, Informix changed the name of Replicate Groups to Replicate Sets.

Replicate List The IFMXER_REPLLIST (Replicate List) application container is created for each IFMXER application instance to hold all Replicate Group or Replicate Set instances that you define. If you do not define any Replicate Groups or Sets, the Replicate List container holds the Replicate instances that you define. This application class provides no parameters or menu commands.


Parameters

Parameters

A parameter is a command that periodically obtains data on a monitored system resource and then parses and processes that data. Parameter data values are collected, summarized, and stored on the computer where the PATROL Agent resides. The information is available for review by a PATROL console.

BMC Performance Manager for Informix organizes parameters into application classes by function or by the objects that they monitor. PATROL uses several types of parameters and stores parameter history data in a file.

Server The IFMXER_SERVER (Informix ER Server) application class instance provides information in an InfoBox about the ER server instance that it represents. A Server application instance is created for each Informix ER server that is discovered or configured by you. This application class provides no parameters or menu commands.

Server Group IFMXER_SERVERGRP (Server Group) application class instance is created for each ER server group that you define. Each Server Group application instance provides information in an InfoBox about the Server Group that it represents. This application class provides no parameters or menu commands.

Spool An IFMXER_SPOOL (Spool) application class container is created for each IFMXER application instance. The Spool application contains the IFMXER_SPOOLDIR application instances.

Spool Directory An IFMXER_SPOOLDIR (Spool Directory) application instance is created for each of two spool directories, the aborted-transaction spool (ATS) directory and the row-information spool (RIS) directory. The Spool Directory application instances provide information in an InfoBox about the ATS and RIS spool directories.

Spool File An IFMXER_SPOOLFILE (Spool File) application instance is created for each spool file created in an ATS or RIS directory. The Spool File instances provide information in an InfoBox about the spool files that they represent.

Thread An IFMXER_THREAD (Thread) application is created for each thread created during the replication process. The Thread application class instances provide information in an InfoBox about the threads that are created during the replication process.

Thread List An IFMXER_THREADLIST (Thread List) application container is created for each IFMXER application instance. The Thread List application contains all Thread application instances for a replication server.

Table 6 Applications and Icons for the Informix ER component (part 2 of 2)



Parameters

for more information about the BMC Performance Manager for Informix parameters, see Appendix B, “Parameter definitions and defaults,” and the online Help. For more general information about parameters and their functions, see the user guide and online Help for your PATROL console.


Parameters

Parameter types

PATROL provides collector, standard, and consumer parameters. BMC Performance Manager for Informix uses standard parameters, standard parameters with collector properties, and consumer parameters:

■ A collector parameter executes commands at regular intervals (poll times) to gather data that they send to the consumer parameters. Collector parameters do not display the values that they collect, nor do they generate alarms or recovery actions.

■ A standard parameter collects a single value of data as numeric or text and displays that value. Many of the standard parameters that are used by BMC Performance Manager for Informix have collector properties; they execute commands and gather the data that consumer parameters display.

■ A consumer parameter displays a value that was collected by a collector parameter or a standard parameter with collector properties. A consumer parameter does not issue commands and is not scheduled for execution, but it has alarms that are set off by the data it displays, and it may run recovery actions.

The use of standard parameters with collector properties and consumer parameters enables PATROL to set an almost unlimited number of parameters with one data retrieval query to the server, creating an extremely efficient and flexible data retrieval system.

Parameter history file

All parameter history data is stored on the computer where the PATROL Agent resides in a single file named param.hist, which is located in the following directory:

$PATROL_HOME\log\history\computername\portnumber

For more information about the parameter history files, see the user guide for your PATROL console.


Menu commands

Menu commands

Using the BMC Performance Manager for Informix menu commands, you can perform the following tasks:

■ define and manage BMC Performance Manager for Informix■ manage your Informix servers from PATROL■ view reports about your Informix servers

The three components that make up BMC Performance Manager for Informix use separate menu commands:

■ The basic Informix component (IFMXDS.kml) provides menu commands that monitor the Informix Dynamic Server and Informix-Online standard engine products.

■ The Informix XPO component (IFMXPO.kml) provides menu commands that monitor the Informix Dynamic Server with Extended Parallel Option and the Informix Extended Parallel Server products.

■ The Informix ER component (IFMXER.kml) provides menu commands that monitor the Informix Enterprise Replication option that is available with some Informix products.

Many of the same menu commands are in the menus of these three components and are repeated under several of the application classes, but the menu commands can operate differently when executed from different components or from different applications within a component.

For complete descriptions of the menus and menu commands, see the BMC Performance Manager for Informix online Help. For information about how to access menu commands and online Help, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

InfoBoxes

BMC Performance Manager for Informix uses InfoBoxes to provide attributes that are specific to the objects in your Informix servers. InfoBoxes are tables of attributes that are accessed from parameters and application class instance icons. The PATROL Console and Agent populate all attributes that are displayed in the parameter InfoBoxes and some attributes, such as icon type or status, that appear in the application InfoBoxes.


Related documentation

In each application InfoBox, the items that are generated by BMC Performance Manager for Informix are displayed below the items that are generated by the PATROL Console. The InfoBox items that are generated by BMC Performance Manager for Informix are preceded by a check mark (in Windows) or are separated from the items that are generated by the PATROL console by a horizontal rule (in UNIX).

The attributes that populate the InfoBoxes are gathered and updated periodically. Some attributes that are displayed in the application InfoBoxes remain static (for example, KM Version) and some attributes change as your Informix environment changes (for example, Blackout Status). Each InfoBox provides an Update button that you can use to force a refresh of the attributes in that InfoBox.

For more information about the application InfoBoxes, see the BMC Performance Manager for Informix online Help. For information about how to access InfoBoxes and online Help, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Related documentationFor more information about BMC Performance Manager for Informix, see your BMC Performance Manager for Informix online Help. For more information about PATROL, see the following documentation:

■ PATROL Console for Microsoft Windows User Guide, Volume 1■ PATROL Console for Microsoft Windows User Guide, Volume 2■ PATROL Console for Microsoft Windows User Guide, Volume 3■ PATROL Console for UNIX and Linux User Guide■ PATROL Agent Reference Manual■ Help for your PATROL Console

To view the complete PATROL documentation library, visit the support page on the BMC Software website at http://www.bmc.com/support.html. Log on and select a product to access the related documentation. (To log on if you are a first-time user and have purchased a product, you can request a permanent user name and password by registering at the Customer Support page. To log on if you are a first-time user and have not purchased a product, you can request a temporary user name and password from your BMC Software sales representative.)

The complete PATROL documentation library is also available on the PATROL documentation CD that is included with major releases of the PATROL Console and Agent.


http://www.bmc.com

http://www.bmc.com/support.html

Where to go from here

Where to go from hereThe following table lists other topics and where you can find them:

Topic Source of information

installing and migrating BMC Performance Manager for Informix

Chapter 2, “Installing BMC Performance Manager for Informix” on page 41 and BMC Performance Manager for Informix online Help

configuring and setting up BMC Performance Manager for Informix

Chapter 3, “Configuring PATROL for Informix” on page 77 and BMC Performance Manager for Informix online Help

using PATROL Configuration Manager with BMC Performance Manager for Informix to change your configuration variables or parameter properties

Chapter 4, “Using PATROL configuration manager with BMC Performance Manager for Informix” on page 91

using BMC Performance Manager for Informix functionality to manage and monitor Informix and Informix XPO servers

Chapter 5, “Managing and monitoring Informix IDS and XPO servers,” and BMC Performance Manager for Informix online Help

using BMC Performance Manager for Informix functionality to manage and monitor Informix Enterprise Replication

Chapter 6, “Managing and monitoring enterprise replication” on page 139 and BMC Performance Manager for Informix online Help

navigating to menu commands, InfoBoxes, and Help

Appendix A, “Accessing menu commands, infoBoxes, and online Help”

definitions and default values for parameters

Chapter B, “Parameter definitions and defaults” on page 167 and BMC Performance Manager for Informix online Help

consumer and collector parameter dependencies

Chapter C, “Collector-consumer dependencies” on page 207and BMC Performance Manager for Informix online Help

PATROL Agent configuration variables Chapter D, “Agent configuration variables” on page 217

step-by-step procedures and detailed descriptions of the applications, menu commands, parameters, and InfoBoxes

BMC Performance Manager for Informix online Help


C h a p t e r 2
2 Installing BMC Performance Manager for Informix
This chapter provides information about how you need to install and migrate BMC Performance Manager for Informix database. This chapter presents the following topics:

Verifying installation of BMC Performance Manager for Informix requirements. . . 42Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Check for product patches or fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 45Determining whether to install locally or remotely . . . . . . . . . . . . . . . . . . . . . . . . . 46Determine where to install KMs based on architecture. . . . . . . . . . . . . . . . . . . . . . 46Target computers and their roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Typical and custom installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Determining the PATROL security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing, upgrading and migrating customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Upgrading from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Automatic migration of console and agent customizations . . . . . . . . . . . . . . . . . . 52Migration of KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Location of PATROL variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Upgrade without saving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Upgrade and preserve KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Distribution server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Installing the online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Installing the UNIX version of the help browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Setting environment variables settings for the browser . . . . . . . . . . . . . . . . . . . . . 71Additional considerations for using online help for UNIX. . . . . . . . . . . . . . . . . . . 73

Uninstalling BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . 74Uninstalling from a UNIX environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Uninstalling from a windows environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76


Verifying installation of BMC Performance Manager for Informix requirements


Before installing BMC Performance Manager for Informix 9.3.00, verify that your system meets the minimum requirements that are listed in Table 7.

Table 7 Requirements for BMC Performance Manager for Informix

Resource Requirements Comments

operating systems

one of the following operating systems:

■ Microsoft Windows■ IBM® AIX®

■ HP-UX■ Tru64■ Sun ™ Solaris™

■ Red Hat Linux®

■ BMC Performance Manager for Informix 9.3.00 provides console support for Microsoft Windows XP and Windows 2003 server operating systems.

■ BMC Performance Manager for Informix 9.3.00 provides support for Red Hat Enterprise 3.0 AS/ES operating system.

■ You can install a PATROL Console on a Microsoft Windows Server.

■ For a list of the versions of these products that are supported by BMC Performance Manager for Informix, please refer to the release notes for the version of BMC Performance Manager for Informix that you are using.

Informix one or more of the following Informix products:■ Informix-OnLine Server■ Informix Dynamic Server

■ To operate the Informix component of BMC Performance Manager for Informix, you must have one of these Informix products in your environment.

■ For a list of the versions of these products that are supported by BMC Performance Manager for Informix, please refer to the release notes for the version of BMC Performance Manager for Informix that you are using.

Informix XPO one of the following Informix XPO products:■ Informix Extended Parallel Server■ Informix Dynamic Server with Parallel

Option

To operate the Informix Extended Parallel Option (XPO) component of BMC Performance Manager for Informix, you must have one of these Informix products in your environment.



Informix ER Informix Dynamic Server that supports enterprise replication

PATROL products

■ PATROL Installation Utility

■ Distribution Server

■ PATROL Agent■ At least one of the following PATROL

consoles:— PATROL Console for Microsoft Windows— PATROL Console for UNIX— PATROL Central Operator – Web Edition— PATROL Central Operator – Microsoft

Windows Edition

For a list of the versions of these products that are supported by BMC Performance Manager for Informix, please refer to the release notes for the version of BMC Performance Manager for Informix that you are using.

■ Informix-Online 5.x and Informix Dynamic Server with Extended Parallel Option and Informix Extended parallel Server operate only on UNIX.

■ Microsoft Windows requires and checks the registry for the following system variables:

— INFORMIXDIR — INFORMIXSERVER — INFORMIXSQLHOSTS— ONCONFIG

browser for PATROL Help

■ Netscape Navigator if you are running Red Hat Linux and on all other UNIX platforms

PATROL Help does not support Netscape Navigator 6.0.

license You must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.

none

ports If you are installing an agent or console with BMC Performance Manager for Informix, you must specify the port number to connect to all the agent computers.

The default port number is 3181 for agents.





PATROL accounts

For Windows:

■ Use a dedicated user account that is created before PATROL is installed.

■ Stand-alone workgroup servers must use a local user account.

■ Servers that are trusted members of a domain can use a local account or a domain account.

■ A PATROL default accounts cannot exist as a local account and a domain account under the same name.

■ The account on a domain controller must be a member of the domain Administrators group.

■ Each PATROL accounts must be a member of the local Administrators group of the computer where the agent resides.

Warning: Do not use a built-in Windows domain account or local Administrator account as the PATROL default account. If you use such accounts, files that are created by PATROL are owned by the Administrator, which could result in security or file access problems.

For UNIX:

■ The account .login, .profile, .cshrc, and .kshrc files cannot contain any customizations such as aliases, non default prompts, or unmask settings other than 022.

■ Do not use the root account.

■ The account must have permission to create directories and write the installation logs to the $HOME and /tmp directories on the computer where you are installing products.

■ The account must have ftp and telnet enabled.

■ The account must have access to a root account on the computer where PATROL is installed.

Note: BMC Software recommends that you install PATROL on local partitions. If PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.

Note: The PATROL user account must be a member of the Informix group so that it has read access and execute permissions on the binaries under $INFORMIXDIR/bin.

security levels See “Determining the PATROL security levels” on page 49

none




Preparing for installation

Preparing for installationBMC Software recommends that you install BMC Performance Manager for Informix on a limited number of development or test computer, and then configure and test BMC Performance Manager for Informix before installing it onto production computer.

Before installing BMC Performance Manager for Informix, perform the following tasks:

■ check for product patches or fixes (page 45)■ ensure that you are using the correct version of the installation utility (page 45)■ determine how to install products (see page 46)■ determine where to install based on architecture (see page 46)■ understand target computer and their roles (see page 47)■ choose between Typical and Custom installation options (see page 48)■ review the security options (see page 49)

Check for product patches or fixes

Product fixes or patches are often available through the BMC Software website. Patches correct problems that are found after a product is released. BMC Software recommends that you check the product page for your version from the website.

If product fixes or patches are available for BMC Performance Manager for Informix version 9.3.00, install version 9.3.00, and then apply the patch or fix using the installation instructions provided in the technical bulletin or flash for the patch or fix.

Determining the version of the installation utility

You can install products on the computer on which you are running the installation utility (local installation), or you can create an installable image of products so that you can install them at a later time on multiple computers (remote installation functionality). An installable image is a fully configured product image that you can use to install products to multiple computers. With an installable image, you can create one product image with one pass through the installation utility and then use that image to install to remote computers in your environment.

To determine the version of an installation utility, perform the following steps:


Determining whether to install locally or remotely

1 Open a command prompt.

2 Navigate to the directory where the installation utility is located.

3 Enter one of the following commands:

■ setup.exe -v (Windows) ■ setup.sh -v (UNIX)

Determining whether to install locally or remotely

You can install products on the computer on which you are running the installation utility (local installation), or you can create an installable image of products so that you can install them later on multiple computers (remote installation functionality). An installable image is a fully configured product image that you can use to install products to multiple computers. With an installable image, you can create one product image with one pass through the installation utility and then use that image to install to remote computers in your environment.

If you create an installable image, all computers on which the image is installed must use identical configuration information for the following settings:

■ BMC Software products installation directory■ account names■ passwords■ PATROL Agent port number■ security options

If you want to specify different settings for different computers, you must create a separate image for each set of values that you want to implement or edit the variables in the image’s control file by using the ctltool. For details about creating, distributing, and installing installable images, see the PATROL Installation Reference Manual.

Determine where to install KMs based on architecture

PATROL version 3.x and PATROL version 7.x architectures differ as to which target computers store Knowledge Modules (KMs) and how much KM information is required by each type of system. During installation, ensure that you select the appropriate types of systems according to information in this section.


Target computers and their roles

PATROL version 3.x

Install KM packages to computers whose roles are defined as Managed Systems and Console Systems. A PATROL version 3.x environment includes the following components:

■ PATROL Agent versions 3.4.11 and 3.5 run on Managed Systems.■ PATROL Console for Windows or PATROL Console for UNIX versions 3.4.11 and

3.5 run on Console Systems.

PATROL version 7.x

For PATROL Central Operator – Microsoft Windows Edition, install KM packages to Console Systems, Common Services Systems, and Managed Systems.

For PATROL Central Operator – Web Edition, install KM packages to Common Services Systems and Managed Systems.

A PATROL version 7.x environment includes the following components:

■ PATROL Agent version 3.5 runs on Managed Systems.■ RTserver runs on Common Services Systems.■ PATROL Console Server runs on Common Services Systems.■ PATROL Central Operator – Microsoft Windows Edition, PATROL Central

Operator – Web Edition, or both run on Console Systems.

For more information about the PATROL version 7.x architecture, see the PATROL Infrastructure Planning Guide.

Mixed PATROL versions 3.x and 7.x environment

A mixed PATROL versions 3.x and 7.x environment includes the components from a PATROL version 3.x environment and a PATROL version 7.x environment.

Target computers and their roles

The PATROL installation program prompts you to select the roles that are performed by the computer upon which you are installing BMC Software products or by the target computer. Before beginning the installation process, review the following definitions of the roles that are presented in the installation program and decide which definition describes the roles that are performed by each computer in your environment.


Typical and custom installation options

■ Console Systems (also referred to as console computers) host user desktop applications such as consoles, user interfaces, viewers, and browsers. Select this option if the computer to which you are installing performs any of the following roles:

— monitor and manage on Windows by using a PATROL Central Operator – Microsoft Windows Edition console (PATROL 7.x architecture)

— monitor, manage, and develop KMs on UNIX by using a PATROL Classic Console for UNIX (PATROL 3.x architecture)

— monitor, manage, and develop KMs on Windows by using a PATROL Classic Console for Windows (PATROL 3.x architecture)

■ Managed Systems (also referred to as agent computers) host software that manages the resources on the computer, such as a PATROL Agent and the PATROL Knowledge Modules. Select this option if the computer to which you are installing performs any of the following roles:

— host a PATROL Agent that works with PATROL 3.x and PATROL 7.x architecture

— host KMs and components that contain the knowledge PATROL uses to monitor the resources on this computer

■ A Common Services (new with PATROL 7.x architecture) computer hosts services that are shared among managed systems and console systems. You can install each of these common services on any computer in the network. Select this option if the computer to which you are installing will perform any of the following roles:

— host the PATROL Console Servers

— host the RTservers

— host the PATROL Central Operator – Web Edition (PATROL 7.x architecture) Web server

For more information about these products, see PATROL Console Server and RTserver Getting Started, PATROL Central Operator – Web Edition Getting Started, and PATROL Central Operator – Web Edition online Help.

Typical and custom installation options

The PATROL installation program prompts you to select one of the following installation options:


Determining the PATROL security levels

■ The Typical installation option installs BMC Performance Manager for Informix (which includes the BMC Performance Manager for Informix ER component) and BMC Performance Manager for Informix XPO. You may want to use the Typical installation option in the following instances:

— You are new to the product that you want to install. — You are performing a first-time installation (you are not upgrading).

■ The Custom installation option enables you to install BMC Performance Manager for Informix (which includes BMC Performance Manager for Informix ER) or BMC Performance Manager for Informix XPO. Use the Custom installation option in the following instances:

— You are familiar with the product that you want to install.— You are installing into PATROL KMDS or PATROL DS.— You are installing into a PATROL version 3.4.11 environment.— You are upgrading from a previously installed version of BMC Performance

Manager for Informix.

Determining the PATROL security levels

PATROL security is installed as part of the agent, console server, and consoles. KMs inherit the security policy from the agent, console server, and console on which they are installed. BMC Performance Manager for Informix can operate at any of the PATROL security levels. However, the higher security levels require more overhead, which can effect performance. If this is a concern, you might want to check to see which level of security is installed and how it was implemented.

For more information about PATROL security, see the following documents:

■ PATROL Security User Guide■ PATROL Security Release Notes

NOTE If you are installing a KM to a PATROL version 3.4.11 Agent or Console, use the Custom option. Do not use the Typical option. The Typical option installs components that are not compatible with the PATROL version 3.4.11 Agent.


Installing, upgrading and migrating customizations

To check the security level of a previously installed agent, console server, or console, perform the following steps:

1. From the command line, switch to the path on the computer that you want to check:

■ For Windows: %BMC_ROOT\..\common\security\bin\OS

■ For UNIX: $BMC_ROOT/../common/security/bin/OS

2. To display the security policy of the current computer, run the following command:

esstool policy -a

Installing, upgrading and migrating customizations

This section explains the steps to follow if you are installing for the first time, upgrading without saving customizations, or upgrading and manually migrating customizations.

You should install BMC Performance Manager for Informix on a limited number of computers in the development environment first, test the installation thoroughly, and then install BMC Performance Manager for Informix in your production environment.

If you are installing into an environment that does not contain BMC Performance Manager for Informix but does contain PATROL version 3.5, use the following procedure:

1 From the installation CD, run setup.exe (Windows) or setup.sh (UNIX).

2 Read the Welcome window and click Next.

3 Read the License agreement, select Accept, and click Next.

4 In the Select Installation Option window, select Install products on this computer now, and click Next.

5 Select Typical and click Next.

NOTE You must install PATROL agents and consoles before installing BMC Performance Manager for Informix.


Upgrading from an earlier version

6 In the Specify Installation Directory window, specify the base directory path to which you want to append the PATROL 3.x product directory, or accept the default and click Next.

For example, if you want to install BMC Performance Manager for Informix in D:\Program Files\BMC Software\PATROL3-5, you should enter D:\Program Files\BMC Software as the base BMC Software products installation directory in this step. (The PATROL 3.x product directory is appended to the path that you enter.)

7 In the Select System Roles window, select Managed System, Console System, Common Services, or all using the information provided in “Target computers and their roles” on page 47, and click Next.

8 In the Select Products and Components to Install window, select PATROL Solutions for Databases => BMC Performance Manager for Informix and click Next.

9 In the Provide PATROL Default Account Information window, enter the PATROL Default Account Login Name (or accept the default, patrol) and the PATROL Default Account Password information, and click Next.

10 In the Review Selections and Install window, review the selections carefully to ensure that they are correct:

■ If you want to change your selections, click Back and make those changes. ■ If the selections are correct, select Start Install to start installing.

A status window opens that contains current messages, current milestones, and percentage complete.

11 To view the results window, click Next. (Next is not displayed until the installation is 100 percent complete.)

12 In the results window, click View Log to review the details of the installation or click Exit to close the installation utility.

Upgrading from an earlier versionIf you have an earlier version of BMC Performance Manager for Informix installed on the target computer, you have the following options for upgrading to the new version of BMC Performance Manager for Informix:

■ “Upgrade without saving KM customizations” on page 58■ “Upgrade and preserve KM customizations” on page 58


Automatic migration of console and agent customizations

Figure 1 on page 57 illustrates the process of upgrading to a new version of BMC Performance Manager for Informix and migrating any customizations.

Automatic migration of console and agent customizations

Only customizations to Knowledge Modules must be migrated.

Whether you choose to save and migrate your KM customizations or not, the customizations that you have made to the agents and consoles are preserved and incorporated into the new version automatically. Customizations to the agents are stored in the agent configuration file and customizations to your consoles are stored in the console cache files.

Customized Knowledge Modules and PSL files are also stored in the cache, but they are not automatically preserved and incorporated.

Migration of KM customizations

Before migrating customizations, you must determine whether or not your customizations to BMC Performance Manager for Informix can be migrated to the new version of BMC Performance Manager for Informix. You can migrate the following versions of PATROL for Informix:

■ 8.2.00■ 8.3.00■ 8.3.10■ 9.1.00■ 9.1.10

If migration is supported, select one of the following upgrade procedures:


Location of PATROL variables

BMC Performance Manager for Informix does not support installation of a new version of the product over an existing version (over-the-top installation). You must uninstall the product before installing a new version, or use migration tools if you are keeping any customizations.


During the installation process, the PATROL Installation Utility records where it installs PATROL components in environment variables. To function properly, various components of the PATROL product, such as the migration tools, require the information stored in these variables. Two important variables are PATROL_HOME and PATROL_CACHE.

Locating PATROL variables in a windows environment

For a Windows environment, all references to PATROL_HOME represent %PATROL_HOME% and all references to PATROL_CACHE represent %PATROL_CACHE%.

Default values for PATROL location variables

If you do not specify a location for the PATROL installation, the installer uses the default locations that are listed in Table 8 and stores these locations in environment variables.

Use this procedure If you have this situation

“Upgrade without saving KM customizations” on page 58

have not made any customizations to the KM files in your previous version of BMC Performance Manager for Informix

want to overwrite customizations you made to the KM files with the default values of the new version of BMC Performance Manager for Informix

have a currently installed version of BMC Performance Manager for Informix that cannot be migrated

make configuration using PATROL Configuration Manager.

“Upgrade and preserve KM customizations” on page 58

made customizations to the KM files in your previously installed version of BMC Performance Manager for Informix and want to save those customizations and migrate them to the new version of BMC Performance Manager for Informix



Viewing environment variables set by PATROL

To view the value of PATROL_HOME, PATROL_CACHE and other environment variables, perform the appropriate procedure for your operating system.

Table 8 Default values for PATROL location variables in windows

Variable Default value

PATROL_HOME C:\Program Files\BMC Software\patrol_directory

PATROL_CACHE %HOMEDRIVE%\%HOMEPATH%\patrol_directory

Operating system Procedure

Microsoft Windows NT 4.x

Using the Control Panel tools:

1. From the Start Menu, choose Start => Settings => Control Panel.

2. Open the System application.

3. Select the Environment tab.

4. Scroll through the System Variable list box to view the variables.

Note: The System application displays PATROL_CACHE only if it is set to a value other than its default value.

Using the PATROL Environment Probe:

1. From the Start Menu, choose Start => Programs => BMC PATROL => PATROL Environment Probe.

2. Scroll to the variables that you want to view.



Locating PATROL variables in a UNIX environment

For a UNIX environment, all references to PATROL_HOME represent $PATROL_HOME and all references to PATROL_CACHE represent $HOME/patrol.

Default Values for PATROL Location Variables in UNIX

If you do not specify a location for the PATROL installation, the installer uses the default locations that are listed in Table 9 and stores these locations in environment variables.

Viewing environment variables set by PATROL

To view the value of PATROL_HOME, PATROL_CACHE, and other environment variables, perform the appropriate procedure for your shell type.

Microsoft Windows 2000

Using the Control Panel tools:

1. From the Start Menu, choose Start => Settings => Control Panel.

2. Open the System application.

3. Select the Environment tab.

4. Scroll through the System Variable list box to view the variables.

Note: The System application displays PATROL_CACHE only if it is set to a value other than its default value.

Using the PATROL Environment Probe:

1. From the Start Menu, choose Start => Programs => BMC PATROL => PATROL Environment Probe.

2. Scroll to the variables that you want to view.

Table 9 Default Values for PATROL Location Variables in UNIX

Variable Default value

PATROL_HOME /opt/bmc/patrol_directory

PATROL_CACHE $HOME/patrol_directory

Operating system Procedure


Upgrade scenarios

Installing BMC Performance Manager for Informix fails to set the INFORMIXDIR environment variable, which causes unknown macro errors. This problem occurs when PATROL account runs on C shell (csh) instead of Korn shell (ksh). Use ksh and do not use csh.

Upgrade scenarios

Figure 1 on page 57 illustrates several different scenarios for upgrading BMC Performance Manager for Informix. These scenarios include

■ not migrating customizations■ migrating customizations manually■ migrating customizations using the PATROL Migration Tools and then installing

the product by using the following products:— the Common Installation Utility for local installations— the Distribution Server for remote installations

Type of shell Procedure

Bourne and Korn At the shell command prompt, type export and press Enter.

The shell displays a list of environment variables and their values.

Note: If PATROL_HOME is not set, run patrolrc.sh.

C At the shell command prompt, type setenv and press Enter.

The shell displays a list of environment variables and their values.

Note: If PATROL_HOME is not set, run patrolrc.sh.


Upgrade scenarios

Figure 1 Upgrading overview for BMC Performance Manager for Informix

Saving customizations?

Migrating manually or using PATROL Migration

Tools?

Install BMC Performance Manager for Informix by using instructions in “Installing, upgrading and migrating customizations” on page 50.

Shut down agent and console, remove previous version from PATROL_CACHE and PATROL_HOME directories on agent and console computer.

yes

no

PATROL

migrating

Back up PATROL_HOME and PATROL_CACHE directories and note all customizations.

Install BMC Performance Manager for Informix using instructions in “Installing, upgrading and migrating customizations” on page 50.

Shut down agent and console, remove previous version of the product from PATROL_CACHE and PATROL_HOME directories on agent and console computers.

manually

MigrationTools

Manually change settings or PSL files to match your customizations for the previous version.

Installing over an existing BMC Performance Manager for

Informix

yes

no

Run the migration probe to determine differences between the base KM and the customized KM, then run merge tool to merge changes with new KM.


See “Migrating customizations with the PATROL migration tools” on page 60.

See “Migrating customizations manually” on page 2-68.

Installing remotely?

yes

no

Import merged package into the Distribution Server or the PATROL KMDS server and start installer by using instructions.

See Figure 1 on page 57.

yes

noCan you migrate?

See “Migration of KM customizations” on page 52


Upgrade without saving KM customizations

Upgrade without saving KM customizations

If you do not want to save any customizations of .km files, PSL code, alarm thresholds, or events, you can simply install the new version of BMC Performance Manager for Informix over your previous version after moving or deleting BMC Performance Manager for Informix files from the PATROL_CACHE. For instructions, see “Installing, upgrading and migrating customizations” on page 50.

Customizations that are applied by using PATROL Configuration Manager or operator overrides are saved in the agent configuration database automatically. They will take effect automatically unless the parameter name or application name has changed. In either of those cases, you must reapply the customizations.

Upgrade and preserve KM customizations

Use the appropriate task in this section if you want to upgrade to the new version of BMC Performance Manager for Informix and you want to preserve any customizations you have made to the .km files in the previous version of BMC Performance Manager for Informix.

You must first migrate your customizations from the old version of BMC Performance Manager for Informix to the new version and then install the result into your environment. You should complete this process on a limited number of computers in the test environment first, test the merged KMs thoroughly, and then deploy them to your production environment.

To upgrade and preserve customizations, you must migrate your customizations manually or use the PATROL Migration Tools version 3.5 with the Distribution Server. If you are using KMDS or the Distribution Server, ensure that you have the latest version of the product installed and any available patches.

Migrating KM Customizations

Customizations made to BMC Performance Manager for Informix can include changes to the parameter alarm ranges, states, or other parameter properties.

You can migrate customizations manually or use the PATROL migration tools. Migration of .km files with the migration tools is automated, with the following exceptions:

■ modified PSL code, whether it is embedded in .km files or in .psl files■ new Knowledge Modules that you created


Upgrade and preserve KM customizations

The results from the migration tools can be installed using either the PATROL Installation Utility, or the Distribution Server. For more information about the PATROL migration tools, see the PATROL Migration Tools User Guide.

Preparing to upgrade customizations

Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If a .kml file or .km file for the new version of BMC Performance Manager for Informix has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.

Before you begin

Before you upgrade and migrate your customizations, ensure that you have performed the following tasks:

■ If you plan to migrate your customizations, determine whether you can migrate from a previous version of BMC Performance Manager for Informix. (See “Migration of KM customizations” on page 52.)

■ If you use to store and manage KMs, you must check them out from PATROL KMDS. You do not need to back up the current installation.

To back up the current installation

Use the following steps to back up your customizations so that you can restore the current installation if you want to roll back your upgrade:

1 Shut down any PATROL Agents, consoles, and related services that are running.

2 Remove the PATROL for Informix .km files from the list of preloaded KMs on each PATROL Agent. For instructions, see “Unloading knowledge modules” on page 80.

3 Ensure that no one is accessing any PATROL files or directories.

4 Perform a full backup of the directories where PATROL files are typically stored. These directories are located in PATROL_HOME and PATROL_CACHE.



Where to go from hereIf you are migrating customizations automatically, go to “Migrating customizations with the PATROL migration tools” on page 60. If you are migrating customizations manually (not using the migration tools), go to “Migrating customizations manually” on page 68.

Migrating customizations with the PATROL migration tools

Use the following steps to migrate BMC Performance Manager for Informix by using the PATROL migration tools. The PATROL migration tools identify, preserve, and merge customizations from the prior version of BMC Performance Manager for Informix before you install the new version of BMC Performance Manager for Informix. The migration probe identifies and preserves customizations; the merge tool merges your customizations into the new version of BMC Performance Manager for Informix.

Figure 2 Overview of migration process using PATROL migration tools

For a detailed explanation and instructions for using the migration tools, see the PATROL Migration Tools User Guide.

Begin you begin

■ Ensure that you have performed the procedures in “Upgrade and preserve KM customizations” on page 58.

■ Verify that the PATROL migration tools version 3.5 have been installed.

■ Verify that you have the latest version of the KM archive, available from the BMC Software ftp site at ftp://ftp.bmc.com/pub/patrol/patches/p_migration_tools.

If you do not have the latest version of the KM archive, download the updated archive from the cited ftp site and download the latest installer from ftp://ftp.bmc.com/pub/patrol/patches/COMMON_INSTALLv.r.mm/operating_system. Then extract both the KM archive and the installer and run the installer.

■ Verify that you know the version release number of the KM product that you want to probe and merge from. To determine the KM version, check the application InfoBox or view the header in the .km files that compose the product.

Run the migration probe tool to determine differences between the base KM and the customized KM.

Run the merge tool to merge base and customized KM with the new KM.


Create an installation package using instructions in “Creating an installation package of merged BMC Performance Manager for Informix” on page 67.



The migration probe lists the versions of the KM packages in the syntax KM_Package_Name: v.r.mm_mm-yyyy.

■ If you are using an EPD image, ensure that the files for BMC Performance Manager for Informix and the associated installation utility have been extracted into a temporary directory.

■ (UNIX only) Set the environment variables for the migration tools by running the appropriate script from the directory where the migration tools and the KM archives are installed:

To use the PATROL migration probe in a windows environment

The PATROL migration probe compares your customized BMC Performance Manager for Informix and the original version of the BMC Performance Manager for Informix to determine the differences.

1 Start the migration probe by using the Start => Programs => BMC PATROL => New PATROL KM Migration Probe menu command or by executing the wmigprobe.exe file from the PATROL_HOME\bin directory.

2 From the Specify how to find KM files to be migrated dialog box, select one of the following methods to locate the KMs that you want to migrate:

3 Enter the PATROL_CACHE and the PATROL_HOME directories for the modified KMs that you want to migrate and click Next.

Type of shell Command

Bourne or Korn . ./migrc.sh

C source ./migrc.sh

Option Description

Automatically locate KM packages in PATROL_CACHE/PATROL_HOME

generates a list of all the KMs found in PATROL_CACHE or PATROL_HOME.

You can select from the list the KMs that you want to migrate. This search method may take a long time to complete.

Automatically locate KM Packages from a console session definition

generates a list of all KMs loaded in a session by checking a console session file (session-<id>.km)

If you select this option, you are asked to supply the session ID number.

Manually select KM Packages

generates a list of all KM products in the KM archives

This method is the quickest and is recommended if you know which KMs you want to migrate.



4 In the Select KM Packages to Migrate dialog box, in the Available KM Packages list box, highlight the modified KM package that you want to migrate and click Select.

The probe lists all the versions of the selected KM package that are in the KM archives.

5 Select the same version of the KM as the KM that you customized and click Next.

6 Repeat step 4 and step 5 for all KMs that you want to migrate.

7 When you have finished selecting the KMs that you want to migrate, click Next on the Select KM Packages to Migrate dialog box.

The probe prepares the selected KMs for output.

8 In the Output Probe Results dialog box, enter the directory for the image (CD or EPD) for the new version of your KM product in the Location of new CD Image field, and then navigate to the Products directory.

9 If you are using an EPD image, ensure that the files for BMC Performance Manager for Informix and the associated installation utility have been extracted into a temporary directory.

10 In the Output Probe Results dialog box, enter the directory where you want to place the probe results in the Destination of Probe results field.

The following directories are created by the migration probe under the results directory that you entered:

11 Click Copy Files to start the migration process, then exit from the migration probe after the migration probe finishes.

Directory name Description

results_directory_name/packagename/base original BMC Performance Manager for Informix files from the archives

results_directory_name/packagename/modified BMC Performance Manager for Informix files to which you have made customizations

results_directory_name/packagename/new new version of the BMC Performance Manager for Informix files from the EPD or CD image



To use the PATROL merge tool in the windows environment

To use the PATROL migration probe in a Windows environment to compare your customized BMC Performance Manager for Informix and the original version of the BMC Performance Manager for Informix and determine the differences, perform the following steps:

1 Start the PATROL merge tool by using the menu command (Start => Programs => BMC PATROL => New PATROL KM Merge Tool) or by executing the wmigmerge.exe from the PATROL_HOME\bin directory.

2 In the Location of product files window, enter in the Directory Path field the results directory that you specified in step 10 on page 62.

3 Select the Use KM Merge Map file check box, and enter the directory and file for the KM merge map file: informix_9_3_00.map

Ensure that you use the merge map file that is created by the PATROL migration probe. The location is specified in step 10 on page 62. The location is results_directory_name\package_name\new\lib\kmmergemap.

4 Click Merge KM to start the Merge KM process.

5 Click Create Product Image to start creating a product image.

Repeat step 4 and step 5, else migration fails.

6 When the product image is created and the process is complete, exit from the PATROL merge tool.

While doing migration (merge tool) in windows in the last screen there are two operations need to perform one is merging and other is creating image. User has two perform this operations twice in series (first perform merging then image creation and then repeat this sequence once.

The PATROL merge tool creates the following additional directories under the results directory that was created by the migration probe:


results_directory_name/packagename/results merged files



To use the PATROL migration probe in a UNIX environment

To use the PATROL migration probe in a UNIX environment to compare your customized BMC Performance Manager for Informix and the original version of the BMC Performance Manager for Informix and determine the differences, perform the following steps:

1 Start the migration probe by executing the tmigprobe file from the PATROL_HOME directory. The migration probe has a text-based interface.

2 Select a method for locating the KMs that you want to migrate by entering the appropriate option number:

3 Enter the PATROL_CACHE and the PATROL_HOME directories for the modified KMs that you want to migrate.

4 Accept your selection of directories and continue.

The probe searches in the directories that you specified for KM packages.

results_directory_name/packagename/merged_results complete merged BMC Performance Manager for Informix, including changed and unchanged files

results_directory_name/packagename/packaged_results complete merged BMC Performance Manager for Informix in a package that can be used to create an installation package

Option Description

1. Automatically locate KM packages in PATROL_CACHE/PATROL_HOME

generates a list of all the KMs it finds in the PATROL_CACHE or PATROL_HOME.

You can select which of these available KMs that you want to migrate. This search method may take a long time to complete.

2. Automatically locate KM Packages from a console session definition

generates a list of all KMs loaded in a session by checking a console session file (session-<id>.km)

If you select this option, you are asked to supply the session ID number.

(3) Manually select KM Packages

generates a list of all KM products in the KM archives

This is the quickest method and is recommended if you know which KM you want to migrate.




5 At the Select KM Packages to Migrate prompt, select the KM package for which you want to migrate customizations.

The probe lists all versions of the selected KM package that are in the KM archives.

6 At the Select version of Archive KM prompt, select the same version of the KM as the KM that you customized.

7 Review your selections, accept the selected version, and continue.

8 At the Specify Target and CD Path prompt, select option 1: Change TARGET PATH and enter the directory where you want the probe to place its results.

The following directories are created by the migration probe under the results directory that you entered:

9 At the Specify Target and CD Path prompt, select 2) Change CD PATH and enter the directory for the image (CD or EPD) for the new version of your KM product, and then navigate to the Products directory.

10 If you are using an EPD image, ensure that the files for BMC Performance Manager for Informix and the associated installation utility have been extracted into a temporary directory.

11 Press Enter to start the migration process.

The probe reports the location of its output.

12 When the migration probe finishes, exit from the migration probe.

Directory Name Description

results_directory_name/packagename/base original BMC Performance Manager for Informix from the archives

results_directory_name/packagename/modified

BMC Performance Manager for Informix that you have made customizations to

results_directory_name/packagename/new new version of the BMC Performance Manager for Informix from the EPD or CD image



To use the PATROL merge tool in a UNIX environment

1 Start the PATROL merge tool by executing the xmigmerge file from the PATROL_HOME directory. The merge tool has a GUI-based interface and must be run from a machine that supports Windows.

2 Enter the results directory that you specified in step 8 on page 65. This directory contains the subdirectories: /base, /modified, /new.

3 Select Use KM Merge Map file, and enter the directory and file for the KM merge map file: informix_9_3_00.map

Ensure that you use the merge map file that is created by the PATROL migration probe. The location is specified in step 8 on page 65. The location is results_directory_name/package_name/new/lib/kmmergemap.

4 To start the Merge KM process, click Merge KM.

5 To start creating a product image, click Create Product Image.

The PATROL merge tool creates the following additional directories under the results directory that was created by the migration probe:

6 When the product image is created and the process is complete, exit from the PATROL merge tool.

Where to go from hereYou must create an installation package of the merged BMC Performance Manager for Informix, as described in “Creating an installation package of merged BMC Performance Manager for Informix” on page 67.


results_directory_name/packagename/results merged files

results_directory_name/packagename/merged_results

complete merged BMC Performance Manager for Informix, including changed and unchanged files

results_directory_name/packagename/packaged_results

complete merged BMC Performance Manager for Informix in a package that can be used to create an installation package



Creating an installation package of merged BMC Performance Manager for Informix

When you have migrated and merged your customizations, you must create an installation package that you can install locally on one computer by using the installation utility or remotely on multiple computers by using one of the BMC Software distribution products, or Distribution Server.

Use the following steps to create your installation package:

1 Copy the entire contents of the BMC Performance Manager for Informix CD to a temporary directory on a hard drive on a server. You can delete this temporary directory after you have successfully created an installable image.

2 Navigate to the packaged_results directory for the merged package and open the .ppf file with a text editor. Write down the file name in the first line of the .ppf file. This file name is the name of the directory that you will look for in the Products directory of the CD image.

3 Rename the packaged_results directory with the file name that you found in the .ppf file in the previous step.

For example, if pnkckm/9.3.00/030107-233044 is the directory listed in the first line of the .ppf file, use pnkckm as the directory name.

4 Copy the renamed directory to the Products directory of the temporary directory that you used in step 1. You will be replacing the files there with the merged files that contain your customizations.

5 Copy the BMC Performance Manager for Informix CD image to the server that you will use to install BMC Performance Manager for Informix.

Where to go from here■ Remove the files in the PATROL_CACHE directory by following the instructions in

“Moving files from PATROL_CACHE directories” on page 68.

■ Install BMC Performance Manager for Informix from the target server by following the instructions in “Installing, upgrading and migrating customizations” on page 50.



Moving files from PATROL_CACHE directories

Before you install, you must move the current BMC Performance Manager for Informix files from the PATROL_CACHE directory for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the newly installed files from PATROL_HOME.

Copy the BMC Performance Manager for Informix files with the following naming patterns to a directory outside the PATROL installation and delete them from PATROL_CACHE\knowledge and PATROL_CACHE\psl:

■ INFORMIX*■ IFMXDS*■ IFMXPO*■ INF*■ INF8*

Migrating customizations manually

If you have only a few customizations, you might find that migrating your customizations manually is easier than using the PATROL migration tools. If you have made customizations to the PATROL Script Language (PSL) code, you must manually migrate those customizations. This task contains a procedure for manually migrating each kind of customization.

To migrate customizations to KM Files manually

1 Ensure that you have made a record of your customizations and have backed up the customized files in the PATROL_HOME and PATROL_CACHE directories.

2 Uninstall the old version of BMC Performance Manager for Informix.

3 Install the new version of BMC Performance Manager for Informix as described in “Installing, upgrading and migrating customizations” on page 50.

4 Identify and record the coding changes that represent your customizations in BMC Performance Manager for Informix. You can identify those changes by comparing the content of the ASCII files in the newly installed BMC Performance Manager for Informix version with the content of the old, customized ASCII files with the same names. The old, customized ASCII files are in the directory where you moved the old version.



5 Incorporate your customizations to the new BMC Performance Manager for Informix by performing the following steps:

A Restart the PATROL console.

B Load the newly installed BMC Performance Manager for Informix.

C Using a PATROL developer console, enter the customizations that you identified in step 4, one by one.

To migrate customized PSL code

Customizations made to PSL code are not migrated automatically. These customizations can be embedded in .km files or stored in separate .psl files. Migrate these customizations manually by using the following guidelines:

■ If you modified .psl files that were shipped by BMC Software, you must manually re-edit the PSL code in the new KM by using a PATROL developer console to reapply your changes.

■ If you modified PSL code embedded in a .km file, that code will be overwritten when you install a new version of the product. You must manually edit the new .km files by using a PATROL developer console to reapply your changes.

■ If you created a new .psl file (not shipped by BMC Software) outside of a .km file, or if you created new PSL code (not shipped by BMC Software) and embedded it in a .km file that was shipped by BMC Software, use the pslsearch utility to search your .km, .psl, and .ctg files for terms that have since been adopted by BMC Software as PSL keywords. Rename any terms that pslsearch identifies as matching existing PSL keywords. Reapply your changes by using a PATROL developer console. For instructions about using the pslsearch utility, see the PATROL Migration Tools User Guide.

If you have a customized PSL library that was compiled with an earlier version of the PSL compiler than the version that was provided with PATROL 3.2.09i, you must manually recompile the library by using the PATROL 3.4.11 compiler.


Distribution server

Distribution server

The Distribution Server product performs remote installations (or uninstallations) of BMC Software distributed systems products across multiple systems from a central location.

Using the Distribution Server, you can perform the following tasks:

■ install, uninstall, upgrade, and reinstall products on remote systems from one central location

■ create collections of products and system groups to distribute multiple products to multiple systems in one distribution

■ schedule a distribution for a specific date and time

■ maintain multiple product versions for distribution

■ view reports to check distribution status, gather distribution data, and diagnose problems

For more information on how to use Distribution Server, see the latest version of the Distribution Server Getting Started guide.


Installing the online help

Installing the online helpFor the PATROL Classic Consoles, the online Help for BMC Performance Manager for Informix is installed automatically when you install the console KM package to the console. For PATROL Central Operator consoles (either Microsoft Windows Edition or Web Edition), the online Help for BMC Performance Manager for Informix is installed automatically when you install the KM package to the console server.

If you plan to install the UNIX version of BMC Performance Manager for Informix on a PATROL Classic Console for UNIX, you must install the supported version of the Help browser separately (if it is not already installed).

Installing the UNIX version of the help browser

The browser that is required for the UNIX version of PATROL Help on PATROL version 3.x is Netscape Navigator version 3.01 through 4.78. However, if you are running a Red Hat Linux platform, you must run Netscape Navigator version 4.x to display the online Help. Currently, PATROL Help does not support Netscape Navigator 6.0.

Before you begin

You must install Netscape Navigator on the computer where the PATROL Console resides. You can install Netscape anywhere on your UNIX computer as long as the binary is in the path.

Netscape Navigator is supplied by Netscape Communications Corp. You can locate the browser at http://home.netscape.com/download.

Setting environment variables settings for the browser

You must set LANG, PATH, and PATROL_BROWSER environment variables for the Help browser to run properly. This section describes these variables.

LANG variable

If you do not set the UNIX LANG environment variable to C for Netscape Navigator, you might experience product failures. The following table provides the correct export commands:


http://home.netscape.com/download

Setting environment variables settings for the browser

PATH variable

The PATROL user account PATH variable must include the directory where the Netscape files are located. If the directory containing the Netscape files is not in the path, add the directory to the PATROL user account path.

This requirement applies only to the PATROL user account on the PATROL console computer. Use the following table to find the appropriate export command:

PATROL_BROWSER variable

When PATROL starts the Help browser, it uses the command in the PATROL_BROWSER environment variable. As a default, the PATROL_BROWSER environment variable contains the following command:

To use different arguments, set the value of PATROL_BROWSER to the appropriate string. For a Korn shell, use the following:

export PATROL_BROWSER=/usr/local/bin/netscape -raise

Type of shell Export command for LANG variable

Bourne LANG=Cexport LANG

Korn export LANG=C

C setenv LANG=C

Type of shell Export command for PATH variable

Bourne PATH=$PATH:/netscape_locationexport PATH

Korn export PATH=$PATH:/netscape_location

C setenv PATH=$PATH:/netscape_location

Type of shell Export command for PATROL_BROWSER variable

Bourne PATROL_BROWSER=netscape -display $DISPLAY -install -iconicexport LANG

Korn export PATROL_BROWSER=netscape -display $DISPLAY -install -iconic

C setenv PATROL_BROWSER=netscape -display $DISPLAY -install -iconic


Additional considerations for using online help for UNIX

Additional considerations for using online help for UNIX

When you select Help from the PATROL Console for UNIX, it may take a few seconds for the Help browser to launch. Two windows will be displayed. First, the Netscape Navigator window is displayed as an icon, and then a browser window that contains the Help is displayed.

In addition, you must be aware of the following restrictions:

■ Netscape Navigator displays warning messages when it is invoked multiple times within the same user account because of its file-locking mechanism. It will, however, continue functioning.

■ By default, when Netscape Navigator starts, it uses a private color map. As a result, you might experience color flashing on your workstation. If so, you can set the value of PATROL_BROWSER so that the colormap option is not specified. However, some subsequent color requests might fail and the online Help will be displayed improperly.

■ The Exceed for Windows NT X Window Server product by Hummingbird Communication Ltd. may not always display the Help files properly.

Consult your Netscape Navigator documentation for specific platform requirements and restrictions.


Uninstalling BMC Performance Manager for Informix

Uninstalling BMC Performance Manager for Informix

To uninstall PATROL for Informix you must use the same version of the installation utility that you used to install the product. If you use a different version of the installation program to uninstall the product, you might remove files that are required to uninstall other BMC Software products.

For more mo information about how to uninstall, see the PATROL Installation Reference Manual.

Use one of the following procedures to uninstall BMC Performance Manager for Informix:

■ “Uninstalling from a windows environment” on page 75■ “Uninstalling from a UNIX environment” on page 74

Uninstalling from a UNIX environment

This section describes how to uninstall PATROL for Informix from a UNIX environment with or without a browser installed.

To uninstall individual products by using the installation utility

1 Change to the Uninstall directory in your BMC Software product installation directory and enter the following command to launch the installation utility in uninstall mode: ./uninstall.sh

2 When the Welcome window is displayed, click Next.

3 Select the installation directory from which you want to remove a product and click Next.

4 Select the product or products that you want to uninstall and click Next.

5 Review your selections and click Uninstall.

When the uninstallation is complete, a message tells you whether the uninstallation was successful.


Uninstalling from a windows environment

Uninstalling from a windows environment

This section describe how to uninstall products and all related log files from a Windows environment .

To uninstall from a windows environment

1 From the Uninstall directory in your BMC Software product installation directory, double-click uninstall.exe to launch the installation utility in uninstall mode.

2 When the Welcome window is displayed, click Next.

3 Select the installation directory from which you want to remove a product, and click Next.

4 Select the product or products that you want to uninstall, and click Next.

5 Review your selections and click Uninstall.

After the uninstallation is complete, a message tells you whether the uninstallation was successful.

NOTE As an option, you can launch the installation utility in uninstall mode by choosing Start => Settings => Control Panel => Add/Remove Programs and double-clicking BMC Software Tools in the Add/Remove Programs Properties dialog box.




.

Topic Source of Information

overview of BMC Performance Manager for Informix and its features

Chapter 1, “Product components and capabilities” on page 13 and BMC Performance Manager for Informix online Help



Using PATROL Configuration Manager with BMC Performance Manager for Informix to change your configuration variables or parameter properties



Chapter 5, “Managing and monitoring Informix IDS and XPO servers” on page 105 and BMC Performance Manager for Informix online Help




Appendix A, “Accessing menu commands, infoBoxes, and online Help” on page 163


Appendix B, “Parameter definitions and defaults” on page 167and BMC Performance Manager for Informix online Help


Appendix C, “Collector-consumer dependencies” on page 207and BMC Performance Manager for Informix online Help

PATROL Agent configuration variables Appendix D, “Agent configuration variables” on page 217




C h a p t e r 3
3 Configuring PATROL for Informix
This chapter provides information about how to load and configure PATROL for Informix, and information about the default settings for the major components. This chapter presents the following topics

Setting up BMC Performance Manager for Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Loading Knowledge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Unloading knowledge modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Verifying that BMC Performance Manager for Informix is discovered . . . . . . . . 81Saving KM changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Adding Informix instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configuring instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Deleting instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Configuring failover monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92


Setting up BMC Performance Manager for Informix

Setting up BMC Performance Manager for Informix

This section contains instructions for how to perform the following setup tasks:

■ load the BMC Performance Manager for Informix files in the PATROL console■ unload the files from your console■ verify that discovery has taken place■ save the BMC Performance Manager for Informix files on the console■ add Informix instances that are not discoverable by PATROL■ configure the Informix instances■ delete instances

Loading Knowledge Modules

Before you begin to use Knowledge Modules (KMs) that you have installed, you must first load them in a PATROL console. Follow the instructions that apply to your console.

To load KMs in the PATROL Console for Microsoft Windows

1 From the PATROL Console menu bar, choose File => Load KM.

The Load KMs dialog box contains a list of available .kml files.

Table 10 on page 79 describes the .kml files provided by BMC Performance Manager for Informix. For more information, see “IFMXDS.kml” on page 14, “IFMXPO.kml” on page 16, and “INFORMIX.kml” on page 17.


Loading Knowledge Modules

2 Select one or more .kml files and click Open.

PATROL loads the selected KMs on all computers under PATROLMainMap.

To load KMs with the PATROL Console for UNIX

1 From the PATROL console menu bar, choose File => Load KM.

The Load KMs dialog box displays a list of available .kml files.

Table 10 describes the .kml files provided by BMC Performance Manager for Informix. For more information, see “IFMXDS.kml” on page 14, “IFMXPO.kml” on page 16, and “INFORMIX.kml” on page 17.

2 Select one or more .kml file and click Open.

PATROL loads the selected KMs on all computers to which your console is connected.

Table 10 .kml files provided by BMC Performance Manager for Informix

.kml files Description

INFORMIX.kml loads .km files for the Informix, Informix XPO, and Informix ER components of PATROL for Informix into your PATROL console

When INFORMIX.kml is loaded, PATROL automatically discovers all supported Informix server instances. (If you do not have any 8.x servers in your environment, consider loading only the IFMXDS.kml. If you only have version 8.x servers in your environment, consider loading only the IFMXPO.kml.)

IFMXDS.kml loads .km files for the Informix and Informix ER components of PATROL for Informix into your PATROL console

When IFMXDS.kml is loaded, PATROL automatically discovers all supported Informix-OnLine or Informix Dynamic Server instances, including those instances with Enterprise Replication.

IFMXPO.kml loads .km files for Informix XPO .km component of PATROL for Informix into your PATROL console

When IFMXPO.kml is loaded, PATROL discovers all supported Informix XPO instances (versions 8.x).


Unloading knowledge modules

Unloading knowledge modules

If you no longer want to use an application class that you previously loaded, you can unload the .km file so that its application class will no longer appear in your console. In some consoles, unloading is referred to as deleting. When you unload or delete a .km file using the PATROL console, the file is not deleted from the patrol\knowledge directories on the PATROL console or the PATROL Agent computers.

To unload KMs with the PATROL console for Microsoft windows

Unloading a KM is also referred to as deleting a KM in the PATROL Console for Windows.

1 From the KM tab of the tree view, right-click the application class name that you want to delete and choose Delete.

A dialog box prompts you to delete the selected application.

2 Click Yes to delete the application class.

The application class is removed from your cache directory and your console session file.

3 Repeat step 1 and step 2 until you have deleted all application classes that are associated with the KM that you want to delete.

4 To save your changes, choose File => Save KM from the console menu bar.

Your changes are saved.

To unload KMs with the PATROL console for UNIX

Unloading a KM is also referred to as deleting a KM in the PATROL console for UNIX.

1 From the PATROL Main window, choose Attributes => Application Classes.

The List of Application Classes window is displayed.

2 Click the name of the application class that you want to delete.

The application class name is highlighted.

3 From the List of Application Classes menu bar, choose Edit => Delete.


Verifying that BMC Performance Manager for Informix is discovered

The application class is removed from your cache directory and your console session file. The PATROL console removes the application class name from the list of application classes.

4 Repeat steps 2 and 3 until you have deleted all of the application classes associated with the KM that you want to delete.

5 To save the changes, choose File => Save KM from the console menu bar.

Verifying that BMC Performance Manager for Informix is discovered

This section describes how to verify that PATROL for Informix is discovered and that the instance icon is displayed.

1 After loading BMC Performance Manager for Informix, open the PatrolMainMap window and verify that the INFORMIX application icon is displayed.

One INFORMIX application instance icon holds all applications and icons for BMC Performance Manager for Informix. An INFORMIX icon representing an INFORMIX application class is created for each agent computer that has BMC Performance Manager for Informix installed. INFORMIX application locates all configured Informix instances, prepares a list of servers with their respective configurations, and supplies it to the IFMXDS or IFMXPO application.

2 Double-click the INFORMIX icon to verify that the appropriate IFMXDS or IFMXPO application instance icon are displayed. Server name and version number is displayed under each server icon.

■ If you selected to load only IFMXDS.kml, you should see an IFMXDS instance icon for each version 7.2x, 9.x and 10.x Informix-Online or Informix Dynamic Server in your environment.

■ If you selected to load only IFMXPO.kml, you should see an IFMXPO instance icon for each Informix XPO server (version 8.x) instance in your environment.

■ If you selected to load the INFORMIX.kml, you should see an IFMXDS or IFMXPO application instance icon for each Informix server (versions 7.2x, 8.x, 9.x and 10.x) in your environment.

NOTE Informix Online version 5.x instances and 64-bit instances of Informix XPO are not discovered automatically. You must add these instances. See “Adding Informix instances” on page 82.


Saving KM changes

3 Double-click the IFMXDS or IFMXPO application instance icon to verify that the following application instances are displayed.

■ AVAILABILITY■ COLLECTORS

When any of these appear, it indicates that discovery is complete.

Saving KM changes

This section describes how to save changes that you made to PATROL for Informix during setup. The setup process adds a significant amount of knowledge to the libraries for the PATROL Agent and the PATROL console.

To save the current knowledge, choose File => Save KM from the PATROL Console menu bar.

When you restart the PATROL console, PATROL automatically reloads the knowledge that you just saved.

Adding Informix instances

PATROL cannot automatically discover version 5.x and some version 8.x instances of Informix. You must add these instances to BMC Performance Manager for Informix by choosing the KM Admin => Instance Configuration => Add Instances menu command.

NOTE If an instance is in a mode other than Online or Read Only, PATROL considers the instance as offline and the icon for the instance is displayed with a gray base.

NOTE You cannot add an instance that PATROL can or should discover automatically. If PATROL did not discover instances that it should have discovered, ensure that the PATROL Agent default account for undiscovered instance is in the Informix group.


Configuring instances

To add an Informix instance

1 From the menu commands for the INFORMIX application instance, choose KM Admin => Instance Configuration => Add Instance.

2 In the INFORMIX OnLine Configuration File field, enter the complete path name to the ONCONFIG or TBCONFIG file for the server that you want to add and configure.


Using the Configure Instances menu command, you can configure which application classes monitor each Informix instance. You can also select whether or not you want PATROL to notify you when an Informix IDS or Informix XPO instance goes offline.

By default, the following applications are configured to monitor all Informix IDS and Informix XPO instances:

■ AVAILABILITY, which contains parameters that measure the availability of the server instances

■ COLLECTORS, which contains the collector parameters that are used to feed the consumer parameters across all of the other application classes

You can select to have the Informix IDS and XPO instances you are configuring monitored by the following applications (except for PDQ, which is available only for IDS) as well:

■ CAPACITY, which contains the parameters that measure the capacity of the server instances

■ PDQ, which contains the parameters that monitor the parallel data query functions of the server instances (PDQ monitoring is available only for Informix DS instances.)

■ PERFORMANCE, which contains the parameters that measure the performance of the server instances

■ USERS, which contains the parameters that monitor the users and processes for the server instances

NOTE All other Informix component applications are activated only when you select the objects that they can monitor. For more information, see Chapter 5, “Managing and monitoring Informix IDS and XPO servers” and the online Help.



To configure Informix DS and XPO instance

1 From the menu commands under the INFORMIX application instance, choose KM Admin => Configure Instances.

Informix instances that PATROL discovered automatically and instances that you have added are listed in the Configure Instances: Instance Selection list box. Instances that are not configured display an asterisk in the Not Configured column.

2 Select (highlight) the instances that you want to configure.

3 If you want to configure to be applied to all selected instances the same way, click Same configuration for selected instances.

4 Click Accept.

The Configure Instances dialog box displayed. If only one instance is listed, the categories that are listed in the Highlight to include and Highlight to exclude text boxes reflect the current configuration for that instance. If multiple instances are listed, the information does not reflect the current configuration of any instance.

5 In the field Enter Instance Monitored Settings take the appropriate actions:

■ If you want to configure and include the instances for monitoring, click Enable Instance Monitoring.

■ If you want to configure the instances but do not want to include the instances for monitoring, ensure that Enable Instance Monitoring is not selected.

■ If you want the InstanceStatus parameter to go into the alarm state when the instance goes offline without good reason or when the instance is in the quiescent mode, click Instance Always On Line.

6 In the Categories Selected to Monitor list, select the application class categories that you want to include:

■ If you want all application class categories to monitor the instances, click Select all Categories

WARNING If you do not select Instance Always On Line, PATROL for Informix does not notify you or trigger an alarm if the instance goes offline. For more information, see the InstanceStatusMonitor and InstanceStatus parameters in the online Help for BMC Performance Manager for Informix.


Deleting instances

■ If you do not want all application class categories to monitor their instances, ensure that Select all Categories is not selected and select only the application class categories that you should monitor the instance.

7 Click Apply.

The selected categories move to the Categories Selected to Monitor list.

8 Click Done.

Deleting instances

Using the Deleted Instances menu command, you can delete the instance icon and the configuration for a selected instance.

1 From the menu commands under the INFORMIX application instance, choose KM Admin => Delete Instances.

All instances that you have configured are listed in the Configured Informix Instances list box.

2 Select (highlight) the instance or instances that you want to delete.

3 Click Apply.

Configuring failover monitoring

Failover monitoring prevents loss of data monitoring when a BMC Performance Manager for Informix instance experiences a failure. You can ensure continuous monitoring by configuring a secondary instance that can take over the monitoring duties of the primary instance when it fails. You install BMC Performance Manager

NOTE ■ When you delete an instance, you must reconfigure the instance if you want PATROL to

monitor that instance. If the instance that you delete is an instance that you added manually, you must add the instance again, and the reconfigure the instance if you want PATROL to monitor the instance.

■ To exclude instances from monitoring, see Chapter 5, “Managing and monitoring Informix IDS and XPO servers”.



for Informix on both computers and configure failover monitoring on both instances by using the PATROL console. The computer from which you perform the configuration is the primary instance by default, and the other computer is the secondary instance.

As long as no failure of the primary instance occurs, the FailOverMonitor parameter’s settings prevent monitoring the secondary instance. After a failure occurs, the parameter automatically starts monitoring the secondary instance. The switch to the secondary instance is referred to as failover.

Figure 3 Primary computer console before failover configuration



Figure 4 Secondary computer console before failover configuration

The failover can occur due to the following reasons:

■ either of the instance is offline■ the primary host is down■ the PARTROL agent crashed on the primary host

Before you begin

Before you configure failover monitoring, you must

■ Install PATROL Agent and KM on the primary and secondary computer.■ Ensure the Patrol Agent is running on each computer.■ Use the PATROL OS user name and password for both the primary and secondary

computers.

To configure failover monitoring

1 Select the primary instance, choose, KM Admin => Failover Monitoring => Configure.

The Failover Configuration dialog box is displayed.

2 In the Failover dialog box, provide the following information:

■ Host Name: the Host Name of the secondary computer.



■ Port Number: the port on which the secondary computer PATROL Agent is running.

■ Instance name: the name of the secondary instance.

■ Informix Directory Path: $INFORMIXDIR or home directory for Informix on the secondary computer.

■ Backup Instance Version: secondary instance version.

■ Backup Config file Path: the path for the onconfig file for the secondary instance.

■ Backup Sqlhosts file Path: sqlhosts file path for secondary instance.

Figure 5 Failover Configuration

3 Click Accept.



Figure 6 Configuring Failover

NOTE This feature is supported only for informix instances on UNIX.After configuration failover, the primary instance should be online and running. The secondary instance icon appears invisible but is not offline.



Figure 7 Failover report after failover start



To remove failover monitoring

1 Choose KM Admin (from the primary)=> Failover Monitoring => Delete Configuration.

2 Click Apply to delete configuration from the current host.

However, before you modify or delete a configuration, consider the following points:

■ You cannot modify or delete failover configuration from secondary instance.

■ Delete the existing configuration, before you modify any existing host name, port number, and instance name.



To view the failover monitoring report

Choose KM Admin => Reports => Failover Reports => Failover Configuration Report.


NOTE For more information about configuring a failover monitor, see the online Help.


Overview of PATROL for Informix and its features and how to access menu commands, InfoBoxes, and online Help

Chapter 1, “Product components and capabilities” on page 13 and PATROL for Informix online Help

Installing and migrating PATROL for Informix


Using PATROL Configuration Manager with PATROL for Informix to change your configuration variables or parameter properties


Using PATROL for Informix functionality to manage and monitor Informix and Informix XPO servers

Chapter 5, “Managing and monitoring Informix IDS and XPO servers” on page 105 and PATROL for Informix online Help

Using PATROL for Informix functionality to manage and monitor Informix Enterprise Replication

Chapter 6, “Managing and monitoring enterprise replication” on page 139 and PATROL for Informix online Help

Navigating to menu command, InfoBoxes, and Help


Definitions and default values for parameters

Appendix B, “Parameter definitions and defaults” on page 167 and PATROL for Informix online Help

Consumer and collector parameter dependencies

Appendix C, “Collector-consumer dependencies” on page 207 and PATROL for Informix online Help


Step-by-step procedures and detailed descriptions of the applications, menu commands, parameters, and InfoBoxes

PATROL for Informix online Help


C h a p t e r 4
4 Using PATROL configuration manager with BMC Performance Manager for Informix
This chapter provides information about how to use PATROL Configuration Manager to configure and manage BMC Performance Manager for Informix. For additional information about PATROL Configuration Manager, see the PATROL Configuration Manager User Guide version 1.4.01 or later. This chapter presents the following topics:

Overview of PATROL configuration manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Installation and setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Setting the archive option to save backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring BMC Performance Manager for Informix instances. . . . . . . . . . . . . . . . . 93Using PATROL Configuration Manager to modify or remove an instance . . . . . . . . 93

Configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Application classes with status changes set in code. . . . . . . . . . . . . . . . . . . . . . . . . 95Modifying or deleting a configured instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Modifying the blackout configuration variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Using PATROL Configuration Manager to manage parameters . . . . . . . . . . . . . . . . . 99Deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Changing parameter thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Changing parameter polling cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Modifying parameter properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Parameters that use an event trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104


Overview of PATROL configuration manager

Overview of PATROL configuration managerThe PATROL Configuration Manager is used by PATROL administrators, system administrators, and database administrators. To define rules and rule sets that manage configuration variables for PATROL Agents on multiple hosts.

This chapter assumes that you have successfully installed and configured the following products:

■ PATROL Configuration Manager■ PATROL Knowledge Module for Event Management

This chapter also assumes that you know how to set up a host in PATROL and operate PATROL Configuration Manager and PATROL KM for Event Management.

Installation and setup requirementsBMC Performance Manager for Informix requires you to:

■ ensure that the Save Backup Before Apply option is selected in the PATROL Configuration Manager

■ move the rules and rule sets created specifically for BMC Performance Manager for Informix to the appropriate directory

The general requirements for installing PATROL Configuration Manager and the PATROL KM for Event Management are listed in the PATROL Configuration Manager User Guide. For more information on general requirements for BMC Performance Manager for Informix, see “Verifying installation of BMC Performance Manager for Informix requirements” on page 42.

Setting the archive option to save backup

Check the configuration settings in PATROL Configuration Manager to ensure that the Save Backup Before Apply archive option is selected before making any changes to BMC Performance Manager for Informix. This option is set as the default during configuration of PATROL Configuration Manager, and it appears as an option in other PATROL Configuration Manager dialog boxes as well. Ensure that it remains selected as the backup option.

To select this option in PATROL Configuration Manager, use the following procedure:


Configuring BMC Performance Manager for Informix instances

1 To open the Configuration dialog box from the main menu, choose File => Configure.

2 choose the Archives tab to open the Backup Settings.

3 Ensure that Save Backup Before Apply is selected.

4 Click OK to save the settings and close the dialog box.

Configuring BMC Performance Manager for Informix instances

You must configure each BMC Performance Manager for Informix instance separately using either batch configuration or the Instance Configure menu command. You cannot use PATROL Configuration Manager to perform the initial configuration of BMC Performance Manager for Informix instances. You can use PATROL Configuration Manager only to modify instances that were previously configured.

Using PATROL Configuration Manager to modify or remove an instance

You can modify or remove a configured Informix instance from the PATROL console by using either the PATROL Configuration Manager or by changing the variables through menu commands in an instance. However, you cannot change the variables and application classes that are discussed in “Configuration variables” on page 94.

The procedure for “Modifying or deleting a configured instance” on page 96 employs the strengths of the KM and PATROL Configuration Manager.

Also included in this section is a topic about how to modify the Blackout variable:

“Modifying the blackout configuration variable” on page 98

For a complete list of the PATROL configuration variables and the strings that they generate, see Appendix D, “Agent configuration variables”


Configuration variables


Configuration variables are used by BMC Performance Manager for Informix to control and alteration of these variables can harm the operation of BMC Performance Manager for Informix. Table 11 lists the configuration variables, some are supported by PATROL Configuration Manager while others are not supported by PATROL Configuration Manager.

Table 11 Variables for BMC Performance Manager for Informix

Type Variable

supported

■ validation provided /InformixConfig/InstanceName/CurrTblSelLimit/InformixConfig/InstanceName/CurrSesSelLimit/InformixConfig/INFORMIX/ScrollLimit/InformixConfig/InstanceName/LocalChannelLimit/InformixConfig/InstanceName/TableCriteria/InformixConfig/InstanceName/UserCriteria/InformixConfig/InstanceName/UserSessionList/InformixConfig/InstanceName/FragThreshold


Application classes with status changes set in code

Application classes with status changes set in code

The use of the change_state to alter the state of application instances does not drive those events to the Standard Event Catalog that the Event Management KM uses; therefore, the Event Management KM takes no action. BMC Performance Manager for Informix issues the change_state command during its prediscovery and discovery cycles and uses this command during application discovery.

■ validation not provided /InformixConfig/InstanceName/DBExclList/InformixConfig/InstanceName/DBSExclList/InformixConfig/InstanceName/DBSInclList/InformixConfig/InstanceName/FragInfoList/InformixConfig/InstanceName/FragTableList /InformixConfig/InstanceName/TableExclPartList/InformixConfig/InstanceName/TablePartList/InformixConfig/InstanceName/UserExclList/InformixConfig/InstanceName/UserList

not supported /InformixConfig/InstanceName/MonitoredFragDBList/InformixConfig/InstanceName/OrderByStr/InformixConfig/INFORMIX/InstConfiguration

Table 11 Variables for BMC Performance Manager for Informix

Type Variable


Modifying or deleting a configured instance


The procedure for modifying and removing configured instances employs the strengths of the KM and PATROL Configuration Manager:

■ make changes in one instance through the menu commands■ test the changes in that instance to ensure that the changes operate as expected■ export the modified variables to PATROL Configuration Manager■ deploy the modified variables to other instances through the PATROL

Configuration Manager

This method takes advantage of the validations performed by BMC Performance Manager for Informix and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.

No matter which method you use to modify or remove an instance, you must apply the following rules to the rule sets created in PATROL Configuration Manager before they are applied to a BMC Performance Manager for Informix instance.

To modify or delete an instance by using the KM and PCM

Use the following steps to modify or remove an instance:

1 In a PATROL Developer console, modify the configuration of one instance of BMC Performance Manager for Informix in a PATROL Developer console until it meets all of your specifications.

2 Test the instance over a period of time to make sure that the instance you modified performs to your satisfaction.

3 In PATROL Configuration Manager, right-click the Agent host name that contains the modified configuration and choose the Configuration => Get from the menu.

The instance status is displayed in the Job Status Information dialog box. The line that represents the instance turns green and OK is displayed in the Status field for the instance when the job has completed.

The Configuration => Get command copies the pconfig variables from the instance, converts them into rules, and pastes them into the PATROL Configuration Manager in the following folder:

Rule Sets\ChangeSpring\backup\HostName\InstanceName\date-timestamp

Figure 8 shows the Configuration => Get menu command in the left panel of PATROL Configuration Manager and an example of the rules that are displayed in the right panel after the Configuration => Get command finishes importing the variables from the instance.



Figure 8 Get command in PATROL Configuration Manager

4 Select and copy all of the rules from the Rule Sets\Change Spring\backup\HostName\InstanceName\date-timestamp directory (use the one with the most recent timestamp at the bottom of the list).

5 Create a folder in the following directory in PATROL Configuration Manager:

Rule Sets\ChangeSpring

6 Highlight the new folder, and Paste the rules.

The rules are given a timestamp and placed into the new folder:

Rule Sets\Change Spring\NewFolder\timestamp\

7 Drag and drop the new rule set on the Agent host name.

8 Click the Apply Changes icon in the PATROL Configuration Manager menu bar.

To deploy the configuration variables for a modified instance

Perform the following steps to distribute the modifications to other instances:

1 Create a new folder under Rule Sets\Change Spring\ and copy and paste the same rules into this folder.

2 Drag and drop this rule set on the Agent host name named in this Rule Set.

3 In the PATROL Configuration Manager menu bar, click the Apply Changes.


Modifying the blackout configuration variable

4 Repeat step 1 through step 3 for each Agent host name to which you want to apply the modified configuration.

Modifying the blackout configuration variable

Blackout periods that are set in PATROL Configuration Manager are not verified. To validate your changes that are set Blackout for one instance by using the Blackout menu command, and then use the output for that variable in PATROL Configuration Manager to apply that blackout period to other instances.

When you create a blackout period for an instance using the Blackout menu command from any one of the following menus:■ IFMXDS■ INFORMIX■ IFMXPOThe blackout information is stored in the /InformixConfig/blackout variable.

The value created for the variable contains the following information in the following format:

ServerName DayOfTheWeek StartTimeInSecondsAfterMidnight DurationInMinutes

For example, if you set a server called Informix for a blackout period on Monday starting at 1:00 a.m. and lasting for 60 minutes, the following value would display for the InformixConfig.blackout variable:

Informix Monday 3600 60

You can change your blackout periods several ways:

■ In a PATROL Developer Console, you can set your blackout periods by using the BMC Performance Manager for Informix Blackout menu command, test the blackout periods, import the modified variable into PATROL Configuration Manager, and deploy the new variable throughout your environment.


Using PATROL Configuration Manager to manage parameters

Using PATROL Configuration Manager to manage parameters

You can modify BMC Performance Manager for Informix parameters by using either the PATROL Configuration Manager or by changing the parameter properties in an instance. However, there are restrictions to the modifications you can make to some BMC Performance Manager for Informix parameters, as described in the topic “Parameters with their status set in code” on page 100

The following topics provide guidelines and cautions with regard to changing parameters, with our method:

■ “Deactivating parameters” on page 99■ “Changing parameter thresholds” on page 100■ “Changing parameter polling cycles” on page 101

The procedure“Modifying parameter properties” on page 102 employs the strengths of the KM and PATROL Configuration Manager.

For a complete list of the parameters and their default values, see Appendix D, “Agent configuration variables.” For more complete descriptions of the parameters, see the online Help for BMC Performance Manager for Informix.

Deactivating parameters

To reduce the impact on your system resources and enhance performance, you can deactivate parameters that you do not need. A deactivated consumer parameter does not appear in the PATROL console and does not go into an alarm or warning state. However, the collector parameter that sets the deactivated consumer parameter continues to send information to the deactivated consumer parameter. Further, the collector annotates the system output window with an error each time it attempts to send information to a deactivated consumer parameter. Collector parameters might also set off unwanted recovery actions they cannot find a deactivated consumer parameter. Consider the following points before deactivating a parameter:

NOTE If a parameter is not deactivated after following the instructions, use the Reinitialize Agent feature in PATROL Configuration Manager to force deactivation.


Changing parameter thresholds

■ If you disable only the alarms for a consumer parameter, the collector parameter continues to send data to the consumer parameter, and the consumer parameter continues to provide a view and history for that data. However, the consumer parameter no longer triggers any alarms, warnings, or recovery actions.

■ If you deactivate a collector parameter, the collector parameter stops collecting data for the consumer parameters it sets.

■ If you disable an application class, no parameters under that application class are displayed in the console. During configuration, you select which categories or application classes are enabled to monitor the instance.

Parameters with their status set in code

The following Enterprise Replication Server parameters directly set their status, and their status changes when conditions change. These internal status changes overwrite whatever changes are made through PATROL Configuration Manager:

■ RAThreadRetriesCnt■ RAThreadStatus

Changing parameter thresholds

Using the PATROL Configuration Manager, you can change the thresholds for most of the BMC Performance Manager for Informix parameters. You should use caution, however, before changing thresholds. BMC Performance Manager for Informix ships with the parameters set at thresholds that are appropriate for those parameters in the average environment. You should make changes to the thresholds in one instance and then test the results in that instance before exporting those changes throughout your entire enterprise.

Some BMC Performance Manager for Informix consumer parameters have thresholds that are not on a sliding scale, but are fixed at a particular value because that value is used directly by the KM. For example, all parameters that have a Boolean output are created to react only to a setting of 0 or 1.


Changing parameter polling cycles

Changing parameter polling cycles

Collector and standard parameters use queries to obtain data from a monitored server or database. The poll time assigned to a collector or standard parameter sets the interval between executions of the query used by the parameter. The default poll times set for collector and standard parameters in BMC Performance Manager for Informix are calculated to collect sufficient data to appropriately monitor most systems.

If your system requires longer or shorter poll times, you can change poll times, but remember the following cautions:

■ Increasing poll times could cause untimely notification of problems.

■ Decreasing poll times increases the resources used by BMC Performance Manager for Informix, which could lead to performance problems.

■ Poll times must exceed the amount of time it takes to execute the query and allow time for the parameter to parse and distribute the data obtained before it must resend the query.

To find the query execution time

1. Turn Debug on for that parameter.

2. When the parameter completes a polling cycle, look at the debug output and find the Total Execution Time.

Execution times can vary, so make sure that you find the longest possible execution time by running Debug on your busiest system during your busiest time.

WARNING Changing the poll time for a standard or collector parameter to an amount of time that is shorter than the amount of time it takes to complete the execution of the query or collection command used by that parameter can cause the parameter to go into an infinite loop or other serious problems. To avoid problems, use Debug to find the Query Execution Time before decreasing a poll time.


Modifying parameter properties

Modifying parameter properties

The following procedure for modifying parameters employs the strengths of the KM and PATROL Configuration Manager:

■ Make changes in one instance through the parameter property dialog boxes.■ Test the changes in that instance to make sure that the changes operate as expected.■ Export the modified parameter changes to PATROL Configuration Manager.■ Deploy the modified parameter changes to other instances through the PATROL

Configuration Manager.

This method takes advantage of the validations performed by BMC Performance Manager for Informix and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.

To modify parameter properties

1 Using the PATROL console in Developer mode, navigate to the parameter properties for the parameter you want to change:

■ In the PATROL Console for UNIX, click Attributes, and then click Application Classes to open a list of the application classes. Select an application class, then click Attributes, and then click Parameters to open the list of parameters provided by the selected application class.

■ In the PATROL Console for Microsoft Windows, select the KM tree tab and expand the appropriate application class, then click Global, and then click Parameters to open the list of parameters provided by the selected application class.

2 Right-click (Windows) or click (UNIX) the parameter for which you want to access the parameter properties.

3 To activate or deactivate a parameter, perform one of these actions:

■ In Windows, select the General tab and select or clear Active.■ In UNIX, double-click the parameter, and select or clear Active.

4 To change the interval between polling cycles, perform one of these actions:

■ In Windows, select the Scheduling tab, and change the polling time.■ In UNIX, click the parameter and change the polling time.


Parameters that use an event trigger

5 To change the alarm thresholds and disable the alarms, perform one of these actions:

■ In Windows, select the Border, Alarm1, and Alarm2 tabs and make changes.■ In UNIX, click Alarm Ranges, and double-click Border, Alarm1, or Alarm 2, and

make changes.

6 Choose File => Save Configuration.

7 Test the changes on the instance until you are satisfied that they are working.

8 Using the PATROL KM for Event Management, convert the parameters in the instance to a rule set in PATROL Configuration Manager.

The rules that represent each parameter contain the _ANYINST_ for the instance name. The _ANYINST_ designation enables you to apply these changes to any instance without adding specific instance name.

9 Drag and drop the rule set to any other Agent host name where you want the changes applied.

Parameters that use an event trigger

BMC Performance Manager for Informix uses event triggers in many recovery actions with. psl scripts. The Event Management KM does not recognize the triggered events. The KM must eliminate any event_trigger for events monitored by the Event Management KM.

The following table provides the places where event_trigger calls are made:

Table 12 Places where event_trigger calls are made

Application class Parameters

IFMXDS_AVAILABILITY OnBarFailures





overview of BMC Performance Manager for Informix and its features and how to access menu commands, InfoBoxes, and online Help










navigating to menu command, InfoBoxes, and Help



Appendix B, “Parameter definitions and defaults” on page 167 and BMC Performance Manager for Informix online Help


Appendix C, “Collector-consumer dependencies” on page 207 and BMC Performance Manager for Informix online Help





C h a p t e r 5
5 Managing and monitoring Informix IDS and XPO servers
This chapter provides information about how to use BMC Performance Manager for Informix to manage and monitor Informix IDS and XPO servers, databases, dbspaces, dbslices, tables, and users. This chapter presents the following topics:

Managing Informix IDS and XPO servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Configuring and managing server instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Starting and stopping Informix servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Managing the global channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Debugging parameters and menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Changing profile statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Changing the response time query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Archiving and logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Loading, unloading, exporting, and importing . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Managing decision support maintenance from PATROL. . . . . . . . . . . . . . . . . . . 114

Monitoring Informix IDS and XPO servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Viewing parameters that monitor servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Viewing InfoBoxes for servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Monitoring databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Excluding or including databases for monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 119Viewing reports on databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Monitoring dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Setting up and managing dbspace monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Viewing parameters that monitor dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Viewing InfoBoxes for dbspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Monitoring dbslices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Viewing reports on dbslices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Monitoring tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Setting up and managing table monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Viewing parameters that monitor tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Viewing InfoBoxes for tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Viewing reports on tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Monitoring logically fragmented tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Setting up and monitoring logically fragmented tables . . . . . . . . . . . . . . . . . . . . 130


Viewing parameters that monitor fragmented tables. . . . . . . . . . . . . . . . . . . . . . . 131Monitoring users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Viewing parameters that monitor users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Viewing InfoBoxes for user application instances . . . . . . . . . . . . . . . . . . . . . . . . . 132Viewing reports about users, sessions, and transactions . . . . . . . . . . . . . . . . . . . . 134



Managing Informix IDS and XPO servers

Managing Informix IDS and XPO serversThis section contains information about the menu commands provided with PATROL for Informix that you can use to change and update the data that BMC Performance Manager for Informix collects on the Informix IDS and XPO servers and to analyze and correct problems with the collection of that data.

For more information about these menu commands, see the online Help for BMC Performance Manager for Informix. For navigation instructions, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Configuring and managing server instances

Choose the Instance Configuration menu commands, under the INFORMIX application, perform the following tasks:

■ add instances that PATROL did not automatically discover■ configure instances■ delete instances from being monitored■ exclude instances from being monitored■ change the SQLHOSTS file that is associated with an instance (not applicable to

Windows)

For instructions about how to use these menu commands, see “Setting up BMC Performance Manager for Informix” on page 78 and the online Help for PATROL for Informix.

Adding instances

Choose the Add Instances menu command, to add instances that PATROL cannot discover. PATROL cannot discover Informix version 5.x and some version 8.x instances.

NOTE You cannot add an instance that PATROL can or should discover automatically. If PATROL did not discover instances that it should have discovered, ensure that the PATROL Agent default account is in the Informix group. If you add an instance and then delete it, you must add the instance again before you can configure that instance.


Configuring and managing server instances


Choose the Configure Instances menu command, to configure how PATROL should monitor each Informix IDS and XPO instance. By default, all instances are monitored by the following applications:

■ AVAILABILITY■ COLLECTORS

You can select whether the following applications should monitor the Informix IDS and XPO instances:

■ CAPACITY■ PDQ (available only for Informix IDS instances)■ PERFORMANCE■ USERS

All other Informix component applications are activated automatically if PATROL discovers the object that PATROL monitor.

Deleting instances

Choose the KM Admin => Delete Instances menu command, under the INFORMIX application instance, to delete the instance icon and the configuration for a selected instance.

Excluding instances

Choose the KM Admin => Exclude Instances menu command to exclude instances from monitoring. Excluding an instance removes the icon and turns off the SMI collector for that instance. You can also use this menu command to include instances which were previously excluded for monitoring.

Changing the SQLHOSTS file associated with an instance

Choose the KM Admin => Instance Configuration => Modify Instances menu command to change the sqlhosts files that is associated with an instance.

NOTE Once you delete an instance, you must reconfigure the instance if you want PATROL to monitor that instance. If you want PATROL to monitor an instance that was added manually, you must add the instance once again.


Starting and stopping Informix servers

Starting and stopping Informix servers

Choose the Informix Admin => Start Server and Stop Server menu commands, which are available for the Informix IDS and XPO instances, to start and stop the Informix servers. You need an Informix password to use these commands.

When you execute the Stop Server the command, the database sends a disconnect signal to all sessions that are attached to the shared memory. Sessions that do not receive the disconnect signal or that are not compliant within 10 seconds are terminated. The disconnected servers are placed in the offline mode.

Managing the global channel

The global channel is the dedicated connection through which PATROL monitors and manages Informix IDS and XPO servers. The PATROL agent maintains this connection to minimize the consumption of resources. Choose the Global Channel Admin or Channel Admin menu commands, to restart the global channel and to limit the number of local channels.

Restarting the global channel

From the PATROL KM menu on INFORMIX application instance, choose the KM Admin => Global Channel Admin => Restart Global Channel menu command to restart the global channel.

From the PATROL KM menu on an IFMXDS or IFMXPO application instance, use the KM Admin => Channel Admin => Restart Global Channel to restart the global channel.

NOTE There is no SQLHOSTS file in windows, the above statement is not valid for windows.


Debugging parameters and menu commands

Setting a local channel limit

Choose the KM Admin => Global Channel Admin or Channel Admin => Limit Local Channels menu command to limit the number of local channels that BMC Performance Manager for Informix uses. The default is set at 10. Allowing too many processes to run concurrently degrades the performance of the system and lowers the number of connections that are available to the database. However, you should allow at least 4 local channels.

Debugging parameters and menu commands

Choose the Debug On/Off Toggle or (Parameter Debug On/Off Toggle) menu command to toggle debug for the menu commands globally, the parameters individually, and for IFMXDS instances discovery. From IFMXDS instances, you can also send the debug output to a file.

If you want to debug one or more parameters, select (highlight) the parameters that you want to debug. If the application class you are in does not have any parameters, no parameters are displayed.

If you select to debug a consumer parameter to debug, you receive information about its recovery actions only. If the parameter does not provide any recovery actions, no output is generated. To view information about why a consumer parameter failed to provide the correct information, select the collector that provides that consumer parameter with data. To find out which collector supplies data to a consumer, see Appendix C, “Collector-consumer dependencies.”

For collector and standard parameters, PATROL generates debug information each time the selected parameter completes a polling cycle. For consumer parameters, PATROL generates debug information after each polling cycle of the collector parameter that sets that consumer parameter.

NOTE The debug output might not be meaningful without assistance from BMC Software Customer Support.


Changing profile statistics

Changing profile statistics

Choose the profile statistics menu commands to change the way profile statistics are collected or set all of them to zero. By default, profile statistics are cumulative. Changing the way profile statistics are collected affects the values that are provided when you use the onstat -p command and the values that are collected by the OnstatMonitor collector parameter.

The following Capacity application parameters are affected by the profile statistics menu commands:

■ Buffer Overflow■ BufferWaits■ CheckpointWaits■ Deadlocks■ Deadlock_Timeout■ LatchWaits■ LockOverflow■ LockWaits■ TableOverflow■ UserOverflow

The TableScans Performance application parameter is affected by the profile statistics menu commands

Setting profile statistics to cumulative

Choose the KM Admin => Profile Statistics Cumulative menu command to set the profile statistics so that the data that is collected from each polling cycles is added to the current total to provide an accumulated total. The totals reflect the values that were collected since the last time the server was shut down or the last time the profile statistics were set to zero.

Setting profile statistics to delta

Choose the KM Admin => Profile Statistics Delta menu command to set the profile statistics so that the collected and displayed data reflects only the data collected during the last polling cycle.

Resetting profile statistics to zero

Choose the Patrol Admin => Profile Statistics Zero menu command to reset all profile statistics to zero.


Changing the response time query

Changing the response time query

The ResponseTime parameter executes a sample SQL statement and measures the amount of time that the parameter takes to connect to the server, execute the query, and return the response.

Choose the KM Admin => Response Time User Defined menu command to change the query that is used by the ResponseTime parameter, and verify that the query you enter does not contain SQL syntax errors. If PATROL detects any SQL syntax errors in the user-defined query, the ResponseTime parameter uses the default query. If you want to change the query, BMC Software recommends these guidelines:

■ Limit the amount of output generated by the query. PATROL executes the query and reads all rows returned by the query.

■ Use queries with short execution times. The server executes the query, and the query adds to the load on the server.

■ Do not enter queries that require system administrator privileges.

Archiving and logging

The archiving and logging menu commands enable you to archive and log the instance on which the command is executed. These menu commands require an Informix user name and password.

Archiving a server

Choose the Informix Admin => Archiving - Logging => Archive menu command to archive the selected server.

Starting continuous logging

Choose the Informix Admin => Archiving - Logging => Start Continuous Logging menu command to activate continuous logging for the selected server.

NOTE These menu commands are available only in Informix version 5.x, 7.x, 9.x and 10.x instances.


Loading, unloading, exporting, and importing

Running automatic logging

The Informix Admin => Archiving - Logging => Run Automatic Logging activates the automatic backup of logical logs for the selected server.

Loading, unloading, exporting, and importing

The loading and unloading menu commands enable you to loading or unload a database or a table, and to import and export databases using a tape or a directory. All of these menu commands require an Informix user name and password.

Loading and unloading a database

Choose the Informix Admin => Loading - Unloading => Load Database menu command. This menu command uses the Informix onload or tbload utility to load the database.

Choose the Informix Admin => Loading - Unloading => Unload Database menu command. This menu command uses the Informix onunload or tbunload utility to unload the database.

Loading and unloading a table

Choose the Informix Admin => Loading - Unloading => Load a Table menu command. This menu command uses the Informix dbload or tbload utility to load the selected table.

Choose the Admin => Loading - Unloading => Unload a Table menu command. This menu command uses the Informix onunload or tbunload utility to unload the selected table.

Importing a database from a tape or a directory

Choose the Informix Admin => Loading - Unloading => Import a Database => Import Database from Tape menu command. This menu command uses the Informix dbimport utility to import a database from a tape to the instance.

NOTE These menu commands are available only in Informix version 5.x, 7.x, 9.x and 10.x instances.


Managing decision support maintenance from PATROL

Choose the Informix Admin => Loading - Unloading => Import a Database => Import Database from Directory menu command. This menu command uses the Informix dbimport utility to import a database from a directory to the selected instance.

Exporting a database to a tape or a directory

Choose the Informix Admin => Loading - Unloading => Export a Database => To Tape menu command. This menu command uses the Informix dbexport utility to import a database to a tape.

Choose the Informix Admin => Loading - Unloading => Import a Database => From Directory menu command. This menu command uses the Informix dbexport utility to import a database to a directory.

Managing decision support maintenance from PATROL

Choose the Informix Admin => Decision Support Maint (PDQ) menu command in an IFMXDS instance to configure the resources allocated to the parallel database queries (PDQ). You can define the settings for the following parameters:

■ MAX_PDQPRIORITY—this parameter toggles PDQ, sets the query type, and the resources for PDQ:

— 0 means PDQ is turned off (no parallel queries)

— 1 allows only parallel scans

— 2 through 99 represent a percentage of resources allocated to PDQ

■ DS_TOTAL_MEMORY—this parameter limits the total amount of shared memory available for PDQ

NOTE This menu command is available only in the Informix component of BMC Performance Manager for Informix. This menu commands is available under the Informix version 5.x, 7.x, 9.x and 10.x instances.

NOTE An IFMXDS_PDQ application instance is created and the PDQ collector parameter is activated when you set the value of the MAX_PDQPRIORITY parameter to a value greater than 0. You can also set the MAX_PDQPRIORITY parameter in the ONCONFIG file or by using the Onmode utility.


Monitoring Informix IDS and XPO servers

■ DS_MAX_QUERIES—this parameter limits the number of PDQ's that can run concurrently

■ DS_MAX_SCANS—this parameter limits the number of scan threads for PDQ

Values are applied after all database queries that are currently running conclude.

Monitoring Informix IDS and XPO serversThis section provides you information about the parameters, the InfoBoxes, and the menu commands that help you monitor the Informix IDS and XPO servers.

For more information about the parameters, the InfoBoxes, and the menu commands, see the online Help for BMC Performance Manager for Informix. For navigation instructions, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Viewing parameters that monitor servers

The following application classes contain parameters that measure the functions associated with the efficient operation of the Informix XPO servers and their coservers:

■ IFMXPO_CORRELATORS■ IFMXPO_AVAILABILITY■ IFMXPO_CAPACITY■ IFMXPO_PERFORMANCE

The following application classes contain parameters that measure the functions associated with the efficient operation of the Informix IDS servers:

■ IFMXDS_AVAILABILITY■ IFMXDS_CAPACITY■ IFMXDS_PERFORMANCE

For more information about parameters, see “Parameters” on page 35, Appendix B, “Parameter definitions and defaults,”and Appendix C, “Collector-consumer dependencies.”


Viewing parameters that monitor servers

Viewing parameters that monitor coservers

The IFMXPO_CORRELATORS application provides parameters that display information about the coservers and the distribution of data among the coservers that belong to IFMXPO application instance. Click on an IFMXPO_CORRELATORS application icon to access the correlator parameters.

Viewing parameters that monitor availability

The AVAILABILITY application provides parameters that display information about the things that can cause an instance to become unavailable (including a parameter that provides information on the metadata space used for blob spaces). To access the Availability parameters, click on an IFMXDS_AVAILABILITY or IFMXPO_ AVAILABILITY application icon.

Viewing parameters that monitor capacity

The CAPACITY application provides parameters that display information about the configurable settings that allow you to maintain efficient use of the servers. To access the Capacity parameters, click on an IFMXDS_CAPACITY or IFMXPO_CAPACITY application icon.

Viewing the parameters that monitor performance

The PERFORMANCE application provides parameters that display information about the objects that affect or are affected by the performance of the servers. To access the Performance parameters, click on an IFMXDS_ PERFORMANCE or IFMXPO_ PERFORMANCE application icon.


Viewing InfoBoxes for servers


The IFMXDS application instance icon provides an InfoBox with specific information about the Informix server that it represents. Table 13 provides descriptions for the items in the IFMXDS Application InfoBox.

Table 13 IFMXDS application InfoBox

Item Description

KM Version version number of BMC Performance Manager for Informix (and the version number for PATROL Agent)

INFORMIXDIR Informix home directory

INFORMIXSERVER DBSERVERNAME on the onconfig file for the instance

ONCONFIG configuration file for the instance

SQLHOSTS name of the sqlhosts file for the instance

Blackout Status states whether a blackout period is in effect:

■ Inactive: no blackout in effect■ Active: day, date, and time when the blackout period

ends

DBSERVERALIASES aliases for the database server

Host Name name of the computer that contains the node where the instance is connected

Informix Version version number for the server

Online Log online log (MSGPATH) for the instance

Cleaners number of page cleaners per instance

DBSPACETEMP tempdbspace on the ONCONFIG file



The IFMXPO application instance icon provides an InfoBox with information about the Informix XPO server that it represents. Table 14 provides descriptions for items in IFMXPO application InfoBox.

Table 14 IFMXPO application InfoBox

Field Description

KM Version version number for the PATROL KM

Host Name name of the computer that contains the node where the instance is connected

IFMX Version version of INFORMIX-OnLine XPS

DBSERVERNAME name of the database server

DBSERVERALIASES aliases for the database server

INFORMIXDIR location of the home directory for Informix

ONCONFIG location of the configuration file for this instance

NETTYPE connection type for this instance

SQLHOSTS location of the sqlhosts file for this instance

Connection Coserver connection coserver for the PATROL KM


■ Inactive: no blackout in effect■ Active: day, date, and time when the blackout period

ends

Online Log location of the online log

Cleaners number of page cleaners for this instance

DBSPACETEMP configuration file for the DBSPACETEMP parameter


Monitoring databases

Monitoring databasesThis section discusses the menu commands that you can use to monitor or stop monitoring databases and to view reports on databases. In the BMC Performance Manager for Informix menu structure, these menu commands are located under KM Admin and Reports.

For more information, see the online Help for BMC Performance Manager for Informix. For navigation instructions, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Excluding or including databases for monitoring

Choose the KM Admin => Exclude or Include => Database Exclude or Include menu command to exclude a database from monitoring or resume monitoring an excluded database. An excluded database is not included for menu pick selections or parameters. However, excluded databases are included in Informix onstat, menu picks, and non-database parameters.

Viewing reports on databases

The Reports => Database Reports menu command enables you to various reports on databases

Viewing a report on all databases

Choose the Reports => Database Reports => Show All menu command to open a report that lists all databases for the selected server.

Viewing a report on the monitored databases

Choose the Reports => Database Reports => Show Monitored menu command to open a report that lists all databases that are monitored by BMC Performance Manager for Informix.

Viewing a report on the default excluded databases

Choose the Reports => Database Reports => Show Default Excluded menu command to open a report that lists all databases that are by default excluded from monitoring.


Monitoring dbspaces

Monitoring dbspacesThis section discusses the InfoBoxes and parameters that display information about dbspaces, temporary dbspaces, and the menu commands that help you to monitor and view reports on dbspaces and temporary dbspaces.


Setting up and managing dbspace monitoring

Choose the KM Admin => Exclude or Include=> Dbspace Exclude or Include menu command to exclude a dbspace from menu selections and from monitoring or to resume monitoring a previously excluded dbspace. Excluded dbspaces are still included in the dbspace reports. By default, all dbspaces are included for menu pick selections and for monitoring.

Choose the KM Admin =>DBSpace Monitoring Admin menu command to select the dbspaces that the DBSpaceMonitor collector parameter monitors. The DBSpaceMonitor parameter creates a Space application instance if any dbspaces or temp dbspaces are selected for monitoring. A DBS or Temp DBS application instance is created for each dbspace or temp dbspace that is selected for monitoring and a DBS Chunk and Temp DBS Chunk application instance is created for each dbspace chunk or temp dbspace chunk that is selected for monitoring. By default, all dbspaces are excluded from monitoring.

Viewing parameters that monitor dbspaces

BMC Performance Manager for Informix parameters are placed in application classes based on their functions. The following application classes contain parameters that display information about the functions that are associated with the efficient use of dbspaces:

■ IFMXDS_DBS and IFMXPO_DBS■ IFMXDS_DBS_CHK and IFMXPO_DBS_CHK■ IFMXDS_DBSTEMP and IFMXPO_DBSTEMP■ IFMXDS_DBSTEMP_CHK and IFMXPO_DBSTEMP_CHK



Viewing InfoBoxes for dbspaces

Viewing dbspace parameters

The IFMXDS_DBS and IFMXPO_DBS applications provide parameters that display information about allocated dbspace and used dbspace. The IFMXDS_DBS application also provides a parameter that displays information about the percentage of used metadata for each blob space for each instance. Click an IFMXDS_DBS or IFMXPO_DBS application icon to access the dbspace parameters and the dbspace chunk instances.

Viewing dbspace chunk parameters

The IFMXDS_DBS_CHK and IFMXPO_DBS_CHK applications provide parameters that display information about the reads, writes, page reads, and page writes for the chunks. Click on an IFMXDS_DBS_CHK or IFMXPO_DBS_CHK application icon to access the dbspace chunk parameters.

Viewing temp dbspace parameters

The IFMXDS_DBSTEMP and IFMXPO_DBSTEMP applications provide parameters that display information about allocated and used temporary dbspace. Click an IFMXDS_DBSTEMP or IFMXPO_DBSTEMP application icon to access the temporary dbspace parameters and the temp dbspace chunk instances.

Viewing temp dbspace chunk parameters

The IFMXDS_DBSTEMP_CHK and IFMXPO_DBSTEMP_CHK applications provide parameters that display temporary read, temporary write, temporary page read, and temporary page write data on the temporary chunks that the instances represent. Click an IFMXDS_DBSTEMP_CHK or IFMXPO_DBSTEMP_CHK application icon to access the temporary dbspace chunk parameters.


The IFMXDS_DBS application instance icons provide Infoboxes with specific information about the dbspaces that they represent. Table 15 provides descriptions for the items in the IFMXDS_DBS Application InfoBox.



Table 15 IFMXDS_DBS application InfoBox

Item Description


■ Inactive: no blackout in effect■ Active: day, date, and time when blackout ends

KM Version version number of BMC Performance Manager for Informix and, in parenthesis, the version number of the PATROL Agent

Name name of the dbspace

Size size of the dbspace

Free amount of free space in the dbspace

Owner owner of the dbspace

Number number of the dbspace

Address address of the dbspace

Number of Chunks number of chunks in the dbspace

First Chunk number of the first chunk in the dbspace

Logical Log ID log ID for the logical restore

Log Position position in the log for the logical restore

Flags current dbspace flags



The IFMXPO_DBS application instance icons provide Infoboxes with specific data about the dbspaces that they represent. Table 16 provides descriptions of the items in the IFMXPO_DBS Application InfoBox.

Table 16 IFMXPO_DBS application InfoBox

Field Description



KM Version version number of the PATROL KM for Informix XPO (and, in parenthesis, the version number for the PATROL Agent

Name name of the dbspace

Size size of the dbspace in kilobytes

Free amount of free space in kilobytes

Owner name of the owner

Number number of the dbspace

Address address of the dbspace

Number of Chunks number of chunks in the dbspace

First Chunk location of the first chunk

Logical Log ID number of the logical log for the dbspace

Log Position location of the logical log

Flags number of flags for the dbspace


Viewing reports on dbspaces

Viewing reports on dbspaces

The Reports menu command in the PATROL for Informix menu structure enables you to view various reports on chunks and dbspaces.

Viewing a report on all chunks

Choose the Reports => Chunk and Dbspace Reports => Show Chunks menu command to open a report that provides information about all the chunks.

Viewing a report on dbspaces and chunks

Choose the Reports => Chunk and Dbspace Reports => Show Dbspace and Chunks menu command to open a report that provides information about all the dbspaces and their associated chunks.

Viewing a report on dbspaces with read and write details

Choose the Reports => Chunk and Dbspace Reports => Show Dbspace and Detail menu command to open a report that provides information about all the dbspaces, including their page reads and page writes.

Viewing a report on dbspace tables

Choose the Reports => Chunk and Dbspace Reports => Show Dbspace’s Tables menu command to open a report that provides information, by dbspace, about the tables that contain information about the dbspace.

NOTE This report is available only from Informix versions 5.x, 7.x, 9.x and 10.x instances.


Monitoring dbslices

Monitoring dbslicesChoose the Reports => Dbslice menu command under Reports in the BMC Performance Manager for Informix menu structure to display reports on dbslices.


Viewing reports on dbslices

The Reports => Dbslice menu commands provide reports on dbslices.

Viewing the allocated and free dbspace

Choose the Reports => Dbslice Reports => Show Allocated and Free menu command to open a report that lists the allocated and free dbspace per dbslice for the on about which the command was executed

Viewing the allocated and used dbspace

Choose the Reports => Dbslice Reports => Show Allocated and Used menu command to open a report that lists the allocated and used dbspace per dbslice for the server on which the command was executed.

Viewing dbspaces per dbslice

Choose the Reports => Dbslice Reports => Show Detail menu command to open a report that lists all dbspaces per dbslice for the server on which the command was executed.

NOTE These reports are available only from Informix XPO instances.


Monitoring tables

Monitoring tablesBMC Performance Manager for Informix provides parameters that display data about tables, InfoBoxes that display the status of a table, and menu commands that you can use to select tables for monitoring and to view reports on tables.

IFMXPO_TBS application instance icons are not created unless you set up table monitoring through the Table Monitoring Admin menu command by selecting an active table for monitoring or by selecting a criterion that fits an active table.

For more detailed information, see the online Help for BMC Performance Manager for Informix. For navigation instructions, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

Setting up and managing table monitoring

BMC Performance Manager for Informix provides menu commands that you can use to exclude or include tables for monitoring, set up table monitoring by criteria or by table, and show the current table monitoring setup.

Excluding or including tables for monitoring

Using the KM Admin => Table Monitoring Admin => Table Exclude or Include menu command, you can exclude a table from monitoring or resume monitoring an excluded table.

Monitoring tables by criteria

Using the Table Monitoring Admin => Monitoring Choice => Monitor by Criteria menu command, you can monitor tables that meet a criterion. If no active tables meet the criterion selected, no table instances are created.

Monitoring by table

Using the Table Monitoring Admin => Monitoring Choice => Monitor by Table menu command, you can add an active table to the list of available tables that are monitored or delete an active table from the list of tables that are monitored.

Viewing the current setup for monitoring tables

Choose the Table Monitoring Admin => Show Current Setup menu command to open a report that displays the current configuration for monitoring tables.


Viewing parameters that monitor tables

Viewing parameters that monitor tables

The IFMXDS_TBS and IFMXPO_TBS application provides parameters that display information about the locks, deletes, page reads, page writes, and sequential scans for the tablespaces. Click an IFMXDS_TBS or IFMXPO_TBS application icon to access the tablespace parameters.


Viewing InfoBoxes for tablespaces

The IFMXDS_TBS application instance icon provides an Infobox with information about the tablespaces that they represent. Table 17 provides descriptions of the items in the IFMXDS_TBS Application InfoBox.

Table 17 IFMXDS_TBS application InfoBox

Item Description



KM Version the version number of BMC Performance Manager for Informix and, in parenthesis, the version number for the PATROL Agent

Server Name name of the server

Connection Server name of the server

Database Name name of the database

Table Name name of the table

Partition Number number of the partition

Lock Requests number of lock requests

Lock Waits number of lock waits

Deadlocks number of deadlocks

Lock Timeouts number of lock timeouts

Reads number of reads

Writes number of writes

Deletes number of deletes

Buffer Reads number of buffer reads

Buffer Writes number of buffer writes

Sequential Scans number of sequential scans


Viewing InfoBoxes for tablespaces

The IFMXPO_TBS application instance icons provide an Infobox with information about the tablespaces that they represent. Table 18 provides descriptions of the items in the IFMXPO_TBS Application InfoBox.

Page Reads number of page reads

Page Writes number of page writes

Reason reason why the PATROL KM is monitoring this tablespace

Table 18 IFMXPO_TBS application InfoBox

Field Description



KM Version version number of the PATROL KM for Informix XPO (and, in parenthesis, the version number for the PATROL Agent)

Server Name name of the server

Connection Coserver name of the connection coserver

Database Name name of the database

Table Name name of the table

Partition Number number of the partition



Deadlocks number of deadlocks

Lock Timeouts number of lock timeouts









Reason reason for monitoring this tablespace

Table 17 IFMXDS_TBS application InfoBox

Item Description


Viewing reports on tables

Viewing reports on tables

Choose the Reports => Table Reports menu commands access reports on Active Tables, Partition Profile, and Tables in Sysptprof.

Viewing a report on active tables

Choose the Reports => Table Reports => Active Tables menu command opens a report that provides information about all the active tables.

Viewing a report on a partition profile

Choose the Reports => Table Reports => Partition Profile menu command opens a report that provides information about the partition profile for the specified partition number.

Viewing a report on tables in Sysptprof

Choose the Reports => Table Reports => Tables in Sysptprof menu command to open a report that provides information about the tables that currently populate the SMI sysptprof view.

Viewing a report on dbspaces for a Table

Choose the Reports => Table Reports => Show Table's Dbspaces Report menu command to open a report that lists the tables and the dbspaces for each table.

This report is available for Informix IDS instances only.

Viewing a report on logical fragments that are summed

Choose the Reports => Table Reports => Show Summed Logical Fragments menu command to open a report that provides a summary of the information about logically fragmented tables.

This report is available for Informix IDS instances only.


Monitoring logically fragmented tables

Monitoring logically fragmented tablesBMC Performance Manager for Informix provides parameters that enable you to view data on logically fragmented tables, InfoBoxes that display the status of fragmented tables, and menu commands that allow you to select fragmented tables for monitoring and to view reports on fragmented tables.

IFMXDS_FRAG or IFMXPO_FRAG application instance icons are not created unless you set up table monitoring through the Fragment Monitoring Admin menu command.


Setting up and monitoring logically fragmented tables

Choose the Fragment Monitoring Admin menu commands to manage how PATROL should monitors logically fragmented tables:

■ Choose the KM Admin => Fragment Monitoring Admin => Monitor by Fragmented Table menu command to include or exclude databases from the list of databases PATROL monitors for fragmented tables

■ Choose the KM Admin => Fragment Monitoring Admin => Set Fragment Threshold menu command to set a threshold for the number of fragments a fragmented table contains before PATROL summarizes the data that it collects on the fragments, rather than present each fragment as a separate instance.

■ Choose the KM Admin => Fragment Monitoring Admin => Show Current Setup menu command to view the current settings for the monitoring of fragmented tables, as well as information about the fragmented tables currently monitored.

NOTE The scroll limit entered by using the Modify Scroll Limit menu command affects the selections for fragment monitoring.


Viewing parameters that monitor fragmented tables

Viewing parameters that monitor fragmented tables

IFMXDS, IFMXPO_FRAG_EXT, and FRAG_SUM applications provide parameters that display information about the locks, deletes, page reads, page writes, and sequential scans for the fragments. Click any one of the following application icons to access the fragmented table parameters:

■ IFMXDS

■ IFMXPO_FRAG_EXT

■ FRAG_SUM .

For more about parameters, see “Parameters” on page 35, Appendix B, “Parameter definitions and defaults,”and Appendix C, “Collector-consumer dependencies.”

Monitoring usersBMC Performance Manager for Informix provides parameters that display information about users, InfoBoxes that display the status of users, and menu commands that allow you to view user transactions, view user reports, kill a session, and monitor or stop monitoring users by criteria, user, or session ID.

IFMXPO_USER and IFMXDS_USER application instance icons are not created unless you set up user monitoring of an active user through the User Monitoring Admin menu command. Choose the User Monitoring Admin menu command to select an active user or session ID for monitoring or select a criterion that fits an active user. For step-by-step instructions, see “Viewing reports about users, sessions, and transactions” on page 134.


Viewing parameters that monitor users

IFMXDS_USERS and IFMXPO_USERS application instance icons provide parameters that display information about the locks, deletes, resources, transactions, and sequential scans for the users. Click an IFMXDS_USERS or IFMXPO_USERS application icon to view parameters that display information about users.

For more information, see “Parameters” on page 35, Appendix B, “Parameter definitions and defaults,”and Appendix C, “Collector-consumer dependencies.”


Viewing InfoBoxes for user application instances


IFMXDS_USER application instance icons provide InfoBoxes that display information about the users that they represent. Table 19 provides descriptions of the items in IFMXDS_USER application InfoBoxes.

Table 19 IFMXDS_USER application InfoBox (part 1 of 2)

Item Description



KM Version version number of BMC Performance Manager for Informix (and, in parenthesis, the version number for the PATROL Agent)

INFORMIXSERVER name of the Informix server

User Name name of the user

User Session ID number that identifies the session

User Process ID number that identifies the user process

Reason reason for monitoring this user

Connected Since day, date, and time this user connection began

Lock Requests number of lock requests made by this user during this session

Locks Currently Held number of locks currently held by this user for this session


Deadlocks Detected number of deadlocks detected

Deadlock Timeouts number of deadlock timeouts

Logical log Displays Written number of logical log Displays written by this user during this session

Reads number of reads executed by this user during this session

Writes number of writes executed by this user during this session

Rewrites number of rewrites executed by this user during this session

Deletes number of deletes executed by this user during this session

Commits number of commits executed by this user during this session

Rollbacks number of rollbacks executed during this session

Long Transactions number of long transactions that have occurred during this session

Buffer Reads number of buffer reads executed during this session

Buffer Writes number of buffer writes executed during this session

Sequential Scans number of sequential scans executed during this session

Page Reads number of page reads executed during this session

Page Writes number of page writes executed during this session



IFMXPO_USER application instance icons provide InfoBoxes with information about the users that they represent. Table 20 provides descriptions of the items in IFMXPO_USER InfoBoxes.

Total Sorts number of total sorts executed during this session

Sorts not in Memory number of sorts executed but not in memory

Table 20 IFMXPO_USER application InfoBox (part 1 of 2)

Field Description



KM Version version number of the PATROL KM for Informix XPO (and, in parenthesis, the version number for the PATROL Agent)

INFORMIXSERVER name of the Informix server

User Name name of the user

User Session ID session number

User Process ID process number

Reason reason for monitoring this user

Connected Since day, date, and time this user connection began


Locks Currently Held number of locks currently held by this user session


Deadlocks Detected number of deadlocks detected

Deadlock Timeouts number of deadlock timeouts

Logical log Displays Written number of logical log Displays written



Rewrites number of rewrites


Commits number of commits

Rollbacks number of rollbacks

Long Transactions number of long transactions





Table 19 IFMXDS_USER application InfoBox (part 2 of 2)

Item Description


Viewing reports about users, sessions, and transactions

Viewing reports about users, sessions, and transactions

IFMXPO_USER application instances provide several reports about users. Transaction log reports that are available from several application instances display transaction logs by tablespace, transaction ID, and user. All of these reports open in a task output window, and a task icon is created for the report.

Viewing memory fragments allocated

Choose the Reports => Memory Fragments Allocated menu command to open a report that provides information about the allocated memory fragments for the selected session ID.

Viewing memory fragments alloc use

Choose the Reports => Memory Fragments Alloc Use menu command to open a report that provides information about the allocated memory fragments by use for the selected session ID.

Viewing memory fragments free

Choose the Reports => Memory Fragments Free menu command to open a report that provides information about the free memory fragments for the selected session ID.

Viewing memory statistics

Choose the Reports => Memory Statistics menu command to open a report that provides memory statistics for the selected session ID.


Total Sorts number of total sorts

Sorts not in Memory number of sorts that did not fit in memory

Maximum Space Used by Sort maximum amount of space used by sort

Bytes Logical log Space Used number of bytes of logical log space used by the current transaction

Max Bytes Logical log Used maximum number of bytes of logical log space ever used by a session

Table 20 IFMXPO_USER application InfoBox (part 2 of 2)

Field Description


Setting up and managing user monitoring

Viewing memory status network

Choose the Reports => Memory Status Network menu command to open a report that provides the status of the network shared memory for the selected session ID.

Viewing session information

Choose the Reports => Session Information menu command to open a report that provides session information for the selected session ID.

Viewing SQL information

Choose the Reports => SQL Information menu command to open a report that provides the SQL for the selected session ID.

Viewing transaction logs by tablespace

Choose the Reports => Transaction Log Reports => Show by Tblspace menu command to provide the transaction log entries for a specified table space.

Viewing transaction logs by transaction id

Choose the Reports => Transaction Log Reports => Show by Transaction ID menu command to view the transaction logs by transaction ID.

A transaction ID is a unique identification number that is assigned to global transactions. When a roll-forward occurs, Informix sends a message to the message log that includes the ID of the offending transaction.

Viewing transaction logs by user

Choose the Reports => Transaction Log Reports => Show by User menu command to open a report that provides the transaction log entries for a specified user.


BMC Performance Manager for Informix provides menu commands that you can use to kill a session, show the current user monitoring setup, and set up user monitoring by criteria, user, or session.



Killing a session

Choose the KM Admin => User Monitoring Admin => Kill Session menu command to stop or kill a user session.

Monitoring by criteria

Choose the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by Criteria menu command to monitor users according to the specified criteria.

Monitoring by session

Choose the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by Session menu command to monitor individual sessions.

Monitoring by user

Choose the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by User menu command to monitor all sessions for selected users.

Viewing the current setup for monitoring users

Choose the KM Admin => User Monitoring Admin => Monitoring Choices => Show Current Setup menu command to display the current setup for monitoring users.

Stopping the monitoring of a specified user

From the KM Commands menu in an IFMXDS_USER or an INFXPO_USER application instance that represents the user or session that you want to stop monitoring, use the KM Admin => Stop Monitoring menu command to stop monitoring a specified user and remove that user instance icon.

NOTE The Stop Monitoring menu command does not work on instances that were created by using the Monitor by Session or Monitor by Criteria. See “Viewing reports about users, sessions, and transactions” on page 134.















navigating to menu command, InfoBoxes, and Help



Appendix B, “Parameter definitions and defaults” on page 167 and BMC Performance Manager for Informix online Help


Appendix C, “Collector-consumer dependencies” on page 207 and BMC Performance Manager for Informix online Help







C h a p t e r 6
6 Managing and monitoring enterprise replication
This chapter provides information about how to use BMC Performance Manager for Informix to manage and monitor Informix Enterprise Replication (Informix ER). This chapter presents the following topics:

Managing Informix ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Starting and stopping ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Defining ER servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Disconnecting and reconnecting ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Deleting ER servers from global catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Modifying attributes of an ER server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Suspending and resuming delivery of data to an ER server. . . . . . . . . . . . . . . . . 143Defining an ER replicate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Changing participants for a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Deleting a replicate from the global catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Modifying attributes of a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Suspending and resuming delivery of data to a replicate. . . . . . . . . . . . . . . . . . . 145Starting and stopping replication for a replicate . . . . . . . . . . . . . . . . . . . . . . . . . . 145Defining a replicate group or set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Changing replicates for a replicate group or set . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Deleting a replicate group or set from ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Modifying attributes of a replicate group or set . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Suspending and resuming delivery to a replicate group or set . . . . . . . . . . . . . . 146

Monitoring Informix ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Viewing InfoBoxes for ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Viewing replication reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148


Monitoring ER servers and server groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing InfoBoxes for ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing parameters that monitor ER servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Viewing replication reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Viewing reports on ER servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Monitoring ER replicate groups or sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Viewing the InfoBox for replicate groups or sets . . . . . . . . . . . . . . . . . . . . . . . . . . 151Viewing reports on replicate groups or sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Monitoring ER replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Viewing InfoBoxes for replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Viewing a report on replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Monitoring ER participants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Viewing InfoBoxes for participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Viewing a report on participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Monitoring ER queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Viewing InfoBoxes for ER queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Viewing parameters that monitor queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Monitoring ER spool directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Viewing InfoBoxes for ER spool directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Viewing parameters that monitor the spool directories. . . . . . . . . . . . . . . . . . . . . 159

Monitoring ER threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Viewing reports on threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Viewing a list of ER threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161



Managing Informix ER

Managing Informix ERInformix ER server is an Informix database server that participates in replication. A server group is an Informix server and all of its aliases. The Enterprise Replication (ER) component of BMC Performance Manager for Informix provides menu commands that you can use to define and maintain the servers, replicates, replicate groups, and participants in the Informix ER environment. Before you can define these objects for the Informix ER environment, you must identify the type of Informix ER environment that you want to create and identify the servers that you want to use in your Informix ER environment. For details about setting up an Informix ER environment, see the Informix Enterprise Replication documentation.

You must configure and monitor at least one of the Informix instances defined for Enterprise Replication. When you have defined an Informix ER instance, PATROL monitors the Informix ER instance during the next IFMXER discovery cycle. You can use the Informix Admin => ER Admin => Server => Define menu command under an IFMXDS instance to define an ER server. You can use the menu commands under the IFMXER instance to administer and maintain Informix ER. Use the INFORMIX application menu to select and configure the Informix servers in your environment. For more information about selecting and configuring servers for monitoring, see “Configuring instances” on page 83.

For more information about Informix ER, see the online Help for BMC Performance Manager for Informix. For navigation instructions, see Appendix A, “Accessing menu commands, infoBoxes, and online Help.”

NOTE Because the Informix ER server requires a password and these menu commands access this server, you must enter a password to use these commands.

NOTE If you enter a wrong password, an error message “PATROL-Message-Unknown: Catalog 1/2 MsgNum 473” displays in the System Output window.


Starting and stopping ER

Starting and stopping ER

Use the Stop menu command from the IFMXER application menu to stop enterprise replication for a global catalog and all servers or server groups that are connected to the specified global catalog.

Use the Start menu command from the IFMXER application menu to restart enterprise replication for a global catalog and all servers or server groups that are connected to that global catalog.

Defining ER servers

From the IFMXER application menu, choose Informix Admin => Server => Define to define an Informix ER server.

Disconnecting and reconnecting ER servers

Use the Informix Admin => Server => Disconnect menu command from the IFMXER application menu to remove a server or server group from participating with other servers in the global catalog.

WARNING Use the Stop command cautiously. You must manually enter transactions that occurred while replication was stopped.

WARNING Synchronize the servers before restarting replication.

NOTE A root server is a database server at the uppermost level in the ER hierarchy. The root server is the server from which other database servers branch. Ensure that all root servers are fully connected. A leaf server is any ER server that is not a root server. For Informix versions 7.30 and 7.31 ER servers, you must select Root Server as the server type when defining an ER server.


Deleting ER servers from global catalog

Use the Informix Admin => Server => Connect menu command, from the IFMXER application menu to reconnect a server or server group to participate with other services in the global catalog.

Deleting ER servers from global catalog

Use the Informix Admin => Server => Delete menu command from the IFMXER application menu to delete a server from the global catalog. This command removes the selected server group from participation in ER and deletes the instance icon for the selected server group.

Modifying attributes of an ER server

Use the Informix Admin => Server => Modify menu command from the IFMXER application menu to change the enterprise replication attributes of a server.

Suspending and resuming delivery of data to an ER server

Use the Informix Admin =>Server => Suspend menu command from the IFMXER application menu to temporarily stop a server from receiving replication data. Use the Server => Resume menu command from the IFMXER application menu to restart the delivery of replication data to a server that was suspended.

NOTE This action does not delete the server from the global catalog. To delete the server from the global catalog, see “Deleting ER servers from global catalog” on page 143.

NOTE To disconnect a server from the global catalog without deleting it from the global catalog, see “Disconnecting and reconnecting ER servers” on page 142.

NOTE To modify the Send queue, you must delete and then redefine the server group.


Defining an ER replicate

Defining an ER replicate

Each replicate that you define in the Informix ER environment represents a segment of data (the database, table, and columns) and the database servers that receive that data. After you have defined all of the replicates, you can place replicates that use identical participant database servers into replicate groups. If you intend to group into replicate groups, the individual replicates that you define, use the following guidelines for defining them:

■ Select the same options for the replicates that you will group together.■ Synchronize the system clocks in the database servers.■ Create unique select statements for all the participants.

Use the Informix Admin => Replicate => Define menu command from the IFMXER application menu to select the server or server group, define conflict resolution, define the frequency of replication, define flags, define the replicates, and define participants.

Changing participants for a replicate

Use the Replicate => Change menu command from the IFMXER application menu to add or delete the participants for a selected replicate.

Deleting a replicate from the global catalog

Use the Informix Admin => Replicate => Delete command to delete a replicate from the global catalog.

Modifying attributes of a replicate

Use the Replicate => Modify menu command from the IFMXER application menu to modify:

■ conflict resolution■ frequency and timing of data replication■ use of spool directories■ activity of triggers■ mode of the participants for a replicate.


Suspending and resuming delivery of data to a replicate

Suspending and resuming delivery of data to a replicate

Use the Informix Admin => Replicate => Suspend menu command from the IFMXER application menu to temporarily stop a replicate from receiving replication data. Use the Server => Resume command to restart the delivery of replication data to a replicate that was suspended.

Starting and stopping replication for a replicate

Use the Replicate => Start menu command from the IFMXER application menu to start the capture and transmittal of transactions for a replicate. Use the Replicate => Stop command to stop the capture and transmittal of transactions for replication.

Defining a replicate group or set

Replicate groups or sets (Informix versions 9.30 and later use the term replicate sets) organize replicates into groups. Using replicate groups or sets saves time and increases the efficiency of your Informix ER environment. Use the following guidelines when defining replicate groups:

Replicate groups organize replicates

■ Define all the replicates that you intend to add to a replicate group before defining the replicate group.

■ Each replicate can belong to only one replicate group.

■ Replicates that are assigned to a replicate group must share the same state, the same frequencies, and the same participants that are attending the same set of replication servers.

■ If the replicate group uses parallel processing, the replicates that are assigned to the group must have disjoint data domains.

Use the Informix Admin => Group => Define menu command from the IFMXER application menu to define replicate groups.

WARNING Synchronize all tables that you have defined for this replicate before using the Replicate => Start command for this replicate. Replicates are created inactive and remain inactive until you use the Replicate => Start command or, if the replicate is in a group, the Group => Start command.


Changing replicates for a replicate group or set

Changing replicates for a replicate group or set

Use the Informix Admin => Group => Change menu command from the IFMXER application menu to add or delete replicates to or from a replicate group or set.

Deleting a replicate group or set from ER

Use the Informix Admin => Group => Delete menu command from the IFMXER application menu to delete a specified replicate group or set.

Modifying attributes of a replicate group or set

Using the Group => Modify menu command from the IFMXER application menu to modify the attributes of a replicate group or set. When you select a replicate group or set to modify, the Modify Replicate Group dialog box opens. You can modify the process and frequency options for the selected replicate group or set in the dialog box.

Suspending and resuming delivery to a replicate group or set

Use the Informix Admin => Group => Suspend menu command from the IFMXER application menu to stop the delivery of replication data to a replicate group or set. Use the Group => Resume menu command to restart the delivery of replication data to a replicate group or set.

WARNING Before deleting a replicate group or set, remove individual replicates from the replicate group or set. See “Deleting a replicate from the global catalog” on page 144.


Monitoring Informix ER

Monitoring Informix ERInformation about Informix ER is available in the InfoBoxes under the IFMXER application instance and in Data Replication reports.


Viewing InfoBoxes for ER

IFMXER application instances display information about the ER environment in the InfoBoxes as described in Table 21:

Table 21 IFMXER application InfoBox

Item Description

CDR_LOGBUFFERS amount of buffer space that is reserved by ER for the evaluation of transactions from logical logs

CDR_EVALTHREADS number of evaluator threads that are created by ER

CDR_DSLOCKWAIT number of seconds the data synchronization component waits for a dslockwait time-out

If this value is too high, check for locking problems.

CDR_QUEUEMEM maximum amount of memory that is used for send and receive queues


Viewing replication reports


The Data Replication Information menu command opens a report that provides information about the ER process for the selected server, including whether data replication is activated, the name of the database server, and the name of the replication server.

The Data Replication Information menu command is located under Reports => Data Replication Reports in the Informix component of BMC Performance Manager for Informix menu structure. In the Informix XPO component of BMC Performance Manager for Informix, this report is located under Data Replication => Data Replication Info.

Monitoring ER servers and server groupsInformation about the servers that participate in ER is available in the InfoBoxes under the IFMXER_SERVER and IFMXER_SERVERGRP application instances, in a Report => Server menu command under the IFMXER application instances, and in the parameters available under the IFMXER application.


Viewing parameters that monitor ER servers

Access the parameters that monitor the ER servers under the IFMXER application instance icon. To access the consumer parameters, double-click the IFMXER application instance icon.

Viewing InfoBoxes for ER servers

Each IFMXER_SERVER application instance provides an InfoBox that contains specific data about the ER server that it represents as described in Table 22.

Table 22 IFMXER_SERVER application InfoBox

Item Description

ID not currently available



Each IFMXER_SERVERGRP application instance provides an InfoBox with specific data about the ER server that it represents as described in Table 23.


The Data Replication Information menu command opens a report about the ER process for the selected server, including whether data replication is activated, the name of the database server, and the name of the replication server.

The Data Replication Information menu command is located under Reports => Data Replication Reports in the Informix component of the BMC Performance Manager for Informix menu structure. In the Informix XPO component of BMC Performance Manager for Informix, this report is located under Data Replication => Data Replication Info.

Table 23 IFMXER_SERVERGRP application InfoBox

Item Description

ID database server ID

Name database server name

Connection Status status of the connection to the server:

■ C = connected■ D = connection disconnected (will be retried)■ L = local■ T = idle time-out caused connection to terminate■ X = connection closed by user command (connection

unavailable until reset by user)

Last Conn. State Change time that the connection state was last changed

Server State state of the server:

■ A = active■ S = suspended■ H = holding■ Q = quiescent (initial sync state only)

Server Type whether the server is a hub, a leaf, or uses a sparse catalog

Root Server Identifier root server ID

Parent Server Identifier parent server ID

Time Out amount of time that you want the database server to remain idle before the connection to that server times out

Send Queue location of send queue

Receive Queue location of receive queue

ATS Directory directory for the aborted-transaction spool (ATS)

RIS Directory directory for the row-information spool (RIS)


Viewing reports on ER servers

Viewing reports on ER servers

From the IFMXER application menu, the Reports => Servers menu command accesses a report about ER servers. Table 24 describes the fields in the report.

Table 24 Fields in the IFMXER Servers report

Field Description

SERVER ID ID for the server

NAME name of the server

CNST connection state:

■ C = connected■ D = disconnected, will be retried■ L = local■ T = idle time-out, connection terminated■ X = closed by user, unavailable until reset by user

LAST CONN STATE CHANGE time when the connection state was last changed

SVST state of the server:

■ A = active■ S = suspend■ H = holding■ Q = quiescent (initial sync state only)

HUB whether server is a hub:

■ Y = yes■ N = no

LEAF whether server connection is a leaf node:

■ Y = yes■ N = no

ROOT SERVER ID ID for root server

PRNT SRVR ID ID for parent server

TIME OUT amount of idle time in seconds

SEND QUEUE dbspace where the send queue is located

RECEIVE QUEUE dbspace where the receive queue is located

ABORTED-TRANSACTION SPOOLING DIRECTORY

path name for the ATS directory (truncated at 40 characters)

ROW-INFORMATION SPOOLING DIRECTORY

path name for the RIS directory (truncated at 40 characters)


Monitoring ER replicate groups or sets

Monitoring ER replicate groups or setsBMC Performance Manager for Informix provides information about the replicate groups (which are called replicate sets in Informix version 9.30) that participate in ER in the IFMXER_REPLGRP or IFMXER_REPLSETS InfoBox, and in the Replicate Groups Report. This section describes how to access and use the InfoBox and the report.


Viewing the InfoBox for replicate groups or sets

Each IFMXER_REPLGRP or IFMXER_REPLSETS application instance provides an InfoBox with specific data about the replicate group or set that it represents as described in Table 25.

Viewing reports on replicate groups or sets

From the IFMXER application menu, the Reports => Replicate Groups menu command accesses a report about replicate groups or sets. describes the fields in the Replicate Groups Report.

Table 25 IFMXER_REPLGRP or SETS application InfoBox

Item Description



Replicate Group Name name of replicate group

Replicate Group DB Server Name name of database server for the replicate group

Replicate Group State state of the replicate group

Sequential Flag whether replication is sequential or parallel


Monitoring ER replicates

Monitoring ER replicatesBMC Performance Manager for Informix provides information about replicates in the IFMXER_REPLICATE InfoBox, and in the report about replicates available under the IFMXER application menu.


Viewing InfoBoxes for replicates

Each IFMXER_REPLICATE application instance provides an InfoBox that contains specific data about the replicate group or set that it represents as described in Table 26 on page 152.

Field Description



Replicate Group name of the replicate group

IS SEQ whether the replicate group processes replication data sequentially (or in parallel):

■ Y = yes (sequentially)■ N = no (not sequentially, but in parallel)

REPLICATES names of the replicates in this replicate group

Table 26 IFMXER_REPLICATE application InfoBox

Item Description



Replicate Name name of the replicate

Replicate Group ID replicate group ID


Viewing a report on replicates


From the IFMXER application instance menu, the Reports => Replicates menu command accesses a report about replicates. Table 27 describes the fields in the Replicates Report.

Replicate State state of the replicate:

■ A= active■ I= inactive■ S= suspended■ Q= quiescent

Frequency Type type of frequency used for replication:

■ C = continuous■ I = interval■ T = time-based■ M = day of month■ W = day of week

Frequency: Minute minute that a refresh should occur

Frequency: Hour hour that a refresh should occur

Frequency: Day day of the week or of the month (1–30) that a refresh should occur (L = last day of the month)

Scope whether replication is determined by transaction or row-by-row:

■ T = transaction■ R = row-by-row

Row Spooling whether row-information spooling is invoked

Transaction Spooling whether aborted-transaction spooling is invoked

Primary Resolution first method used to resolve conflicts for data replication:

■ I = ignore■ T = time stamp■ S = stored procedure

Secondary Resolution whether a stored procedure is used to determine a data replication conflict when time-stamps are identical

Stored Procedure Name the name of the stored procedure used

Do Fire Trigger whether triggers are invoked

Is Canonical whether conversion to canonical form is required

Table 26 IFMXER_REPLICATE application InfoBox

Item Description



Table 27 Fields in the Replicates Report

Field Description



REPLICATE name of the replicate

REPLICATE GROUP name of the replicate group (or set) for the replicate

REPL. STATE whether replicate is ACTIVE or INACTIVE

FREQUENCY when replication occurs:

■ T = C for continuous or T for time-based■ DY = day of the week ■ HR = hour ■ MN = minute

CONFLICT RESOLUTION how replication conflicts are resolved:

■ P = procedure (T = time stamp; I = Ignore)■ S = stored procedure■ PROCEDURE = name of stored procedure■ SCP = scope of replication (T = transaction; R = row-by-

row)

FLAGS which flags are invoked:

■ ATS = aborted-transaction spooling■ RIS = row-information spooling■ CAN = conversion of data to canonical form■ TGR = triggers are invoked


Monitoring ER participants

Monitoring ER participantsPATROL KM for Informix ER provides InfoBoxes and reports to help you monitor the participants in ER.


Viewing InfoBoxes for participants

Each IFMXER_PARTICIPANT application instance provides an InfoBox that contains specific data about the replicate group or set that it represents as described in Table 28.

Table 28 IFMXER_PARTICIPANT application InfoBox

Item Description



Replicate Name name of the replicate

Server Group Name name of the server group

Participant State state of the participant database (active or inactive)

Participant Mode mode of the participant database (read only or read and write)

Database Name name of database (dbsname) where the replicated table resides

Owner name of owner of the table replicated

Table Name name of table replicated

Select Statement statement that determines which columns in the table are replicated


Viewing a report on participants

Viewing a report on participants

From the IFMXER application menu, the Reports => Participants menu command accesses a report about the participants involved in ER. Table 29 describes the fields in the Participants Report.

Monitoring ER queuesBMC Performance Manager for Informix provides information about the send and receive queues in the IFMXER_QUEUE application InfoBox and in the ERSendQueue and ERReceiveQueue parameters.


Table 29 Fields in the Participants Report

Field Description



REPLICATE name of the replicate

SERVER name of the server or server group

STATE state of the participant:

■ ACTIVE■ INACTIVE

M mode of participation for this participant:

■ P for primary or read and write■ S for secondary or read only

DATABASE name of the database

OWNER name of the owner of the database

TABLE name of the table in the database

SELECT STATEMENT statement that determines the data replicated

NOTE ER Queues are not monitored for Informix ER version 9.3.


Viewing InfoBoxes for ER queues

Viewing InfoBoxes for ER queues

Each IFMXER_QUEUE application instance provides an InfoBox that contains specific data about the queue that it represents as described in Table 30.

Viewing parameters that monitor queues

Access the parameters that monitor the ER send and receive queues using the IFMXER application instance. To access the consumer parameters, double-click on the IFMXER application instance icon.

Monitoring ER spool directoriesBMC Performance Manager for Informix provides information about aborted-transaction spooling (ATS) and row-information spooling (RIS) directories in the:

■ IFMXER_SPOOL application InfoBox■ IFMXER_SPOOLDIR application InfoBox■ IFMXER_SPOOLFILE application InfoBox■ ERATSSpace■ ERATSSpool■ ERRISSpace■ ERRISSpool consumer parameters


Table 30 IFMXER_QUEUE Application InfoBox

Item Description



DB Space dbspace name (send queue, receive queue, or root)

DBS Size amount of dbspace available expressed in megabytes

DBS Used amount of dbspace used expressed in megabytes

Percent Used percentage of the available dbspace that is used


Viewing InfoBoxes for ER spool directories

Viewing InfoBoxes for ER spool directories

Each IFMXER_SPOOL application instance provides an InfoBox that contains specific data about the spool that it represents described in Table 31.

Each IFMXER_SPOOLDIR application instance provides an InfoBox that contains specific data about the spool directory that it represents described in Table 32.

Each IFMXER_SPOOLFILE application instance provides an InfoBox that contains specific data about the spool file that it represents described in Table 33.

Table 31 IFMXER_SPOOL application InfoBox

Item Description



ATS Directory Path path for the ATS spooling directory

RIS Directory Path path for the RIS spooling directory

Num. RIS Files number of row-information files

Num. ATS Files number of aborted-transaction files

Table 32 IFMXER_SPOOLDIR application InfoBox

Item Description

Blackout Status states whether or not a blackout period is in effect:


File System Name name of the file system where the spool directory resides

File System Free Blocks number of free blocks in the file system in which the spool directory resides

File System Size Blocks size of the file system in which the spool directory resides

Table 33 IFMXER_SPOOLFILE application InfoBox

Item Description



File Name spool file name

File Size size of the spool file


Viewing parameters that monitor the spool directories

Viewing parameters that monitor the spool directories

Use the IFMXER application instance to access the parameters that monitor the spool directories. To access the consumer parameters, double-click on the IFMXER application instance icon.

Monitoring ER threadsThe ER component of BMC Performance Manager for Informix provides information about the threads involved in enterprise replication in a report located under the IFMXER application menu. This section describes the report and includes a list of the threads used by ER.


Viewing reports on threads

From the IFMXER application menu, the Reports => Threads menu command accesses a report about the threads involved in enterprise replication. Table 34 describes the fields in the ER Threads Report.

File Creation Timestamp date and time when the spool file was created

File Owner name of the owner of the spool file

Table 34 Fields in the ER Threads Report

Field Description



ID ID for the thread

NAME name of the thread

Table 33 IFMXER_SPOOLFILE application InfoBox

Item Description


Viewing reports on threads

STATUS status of the thread:

■ sleeping forever = set to sleep forever■ sleeping secs: n = set to sleep for n seconds■ cond wait = waiting for a condition

VP CLASS virtual process class for the thread

Table 34 Fields in the ER Threads Report

Field Description


Viewing a list of ER threads

Viewing a list of ER threads

Table 35 lists the threads that are involved in ER.

Table 35 Enterprise replication threads

Thread Description

ddr_log_io performs physical I/O from logical log

ddr_snoopy verifies potential replication and sends applicable log record entries to ER fan-out thread

CDRGfan receives log entries and passes entries to evaluator thread

CDR Geval ServerGroupId evaluates log entry to determine wether it should be replicated, performs transaction compression on the receipt of COMMIT WORK, and sends completed replication messages to the queue

CDRCparse parses all WHERE clauses for replicate definitions

CDRSchedMgr schedules ER events

CDRN_CM takes replication messages from the queue and passes them to the appropriate sending threads

unknown keeps track of current buffers in use

CDRNrA ServerGroupId CDRNrT ServerGroupId

sending thread for site

CDRNrA ServerGroupId CDRNrT ServerGroupId

receiving thread for site

ackTh ServerGroupId accepts acknowledgment from site

cntlTh ServerGroupId accepts control messages (updates to the global catalog) from other sites and replicates those to the local global catalog

replTh ServerGroupId determines which replication messages are processed in parallel and passes threads

syncTh ServerGroupId receives global catalog information during initialization of server

CDRD_0 (created for parallel processing) synchronizes data, receives the replication message, and applies it to local instance, and performs conflict resolution and inserts information into shadow tables if required

unknown schedules internal ER events


















Appendix B, “Parameter definitions and defaults” on page 167and BMC Performance Manager for Informix online Help


Appendix C, “Collector-consumer dependencies” on page 207and BMC Performance Manager for Informix online Help





A p p e n d i x A
A Accessing menu commands, infoBoxes, and online Help
BMC Software offers several PATROL consoles from which you can view a PATROL Knowledge Module (KM). Because of the different environments in which these consoles run, each one uses a different method to display and access information in the KM. The following topics provide instructions for accessing the KM menu commands, InfoBoxes, and online Help on each of the PATROL consoles.

For more information about navigation in the PATROL consoles, see the PATROL for Informix online Help.

Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Appendix A Accessing menu commands, infoBoxes, and online Help 163

Accessing KM commands and InfoBoxes

Accessing KM commands and InfoBoxesTable 36 provides information about how to access KM commands and InfoBoxes from the various PATROL consoles.

Table 36 Accessing KM commands and infoBoxes

Console Menu commands InfoBoxes

PATROL Console for Microsoft Windows Servers

In either the Desktop tree tab or work area, right-click a computer or application icon and choose KM Commands from the pop-up menu.

In either the Desktop tree tab or the work area, right-click an application class or parameter icon and choose InfoBox from the pop-up menu.

PATROL Console for UNIX In the work area, right-click a computer or application icon to display a pop-up menu that contains KM-specific commands.

With the middle mouse button, click an application class or parameter icon.

PATROL Central Operator – Windows Edition

In the navigation pane, right-click a managed system or application icon and choose Knowledge Module Commands from the pop-up menu.

In the navigation pane, right-click a PATROL object and choose InfoBox from the pop-up menu.

PATROL Central Operator – Web Edition

In the tree view area, right-click an application icon and choose Knowledge Module Commands from the pop-up menu.

In the tree view area, right-click a PATROL object and choose Infobox from the pop-up menu.


Accessing online Help

Accessing online HelpTable 37 provides information about how to access Help from each console.

NOTE If you are trying to access Help from a UNIX console, see “Installing the online help” on page 71 for specific instructions about installing and setting up a browser in a UNIX environment.

Table 37 Accessing Online Help

Console Product help Application class help Parameter help

PATROL Console for Microsoft Windows Servers

From the console menu bar, choose Help => Help Topics => PATROL Knowledge Modules.

Double-click an application class in the KM tab of the console. From the Application Properties dialog box, click the Help tab. Then click Show Help.

■ Right-click a parameter icon and choose Help On from the pop-up menu.

■ Double-click a parameter icon; click the ? icon or Help button in the parameter display window.

■ Double-click a parameter in the KM tab of the console; from the properties dialog box, click the Help tab, then click Show Help.

PATROL Console for UNIX

From the console menu bar, choose Help On => Knowledge Modules.

Choose Attributes => Application Classes and double-click the application name. Click Show Help in the Application Definition dialog box.

Right-click a parameter icon and click Help On.

PATROL Central Operator – Windows Edition

From the console menu bar, choose Help => Help Topics. In the Contents tab, click the name of your product.

In the Operator tab of the navigation pane, select an application icon and press F1.

In the Operator tab of the navigation pane, select a parameter icon and press F1.

PATROL Central Operator – Web Edition

In the upper right corner of PATROL Central, click Help and choose PATROL KM Help.

In the tree view, right-click an application class and choose Help.

In the tree view, right-click a parameter and choose Help.

Appendix A Accessing menu commands, infoBoxes, and online Help 165

Accessing online Help


A p p e n d i x B
B Parameter definitions and defaults
The following topics provide a definition and the default values for each parameter that is used in BMC Performance Manager for Informix.

For more information about individual parameters, see the BMC Performance Manager for Informix online Help. For information about the dependencies between standard collector and consumer parameters, see Appendix C, “Collector-consumer dependencies.”

Column headings defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Abbreviations defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170INFORMIX application (contains Informix, Informix XPO, and Informix ER

components) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Informix Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

IFMXDS_AVAILABILITY application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171IFMXDS_CAPACITY Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174IFMXDS_COLLECTORS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176IFMXDS_DBS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179IFMXDS_DBS_CHK application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179IFMXDS_DBSTEMP application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180IFMXDS_DBSTEMP_CHK application class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180IFMXDS_FRAG_EXT application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180IFMXDS_FRAG_SUM application class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181IFMXDS_PDQ application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182IFMXDS_PERFORMANCE application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183IFMXDS_TBS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185IFMXDS_USERS Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Extended Parallel Option (XPO) Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189IFMXPO_AVAILABILITY Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189IFMXPO_CAPACITY application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190IFMXPO_COLLECTORS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191IFMXPO_CORRELATORS application class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194IFMXPO_DBS Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195IFMXPO_DBS_CHK application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195IFMXPO_DBSTEMP application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196IFMXPO_DBSTEMP_CHK application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Appendix B Parameter definitions and defaults 167

IFMXPO_FRAG_EXT application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196IFMXPO_PERFORMANCE application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199IFMXPO_TBS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201IFMXPO_USERS application class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Enterprise Replication (ER) Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203


Column headings defined

Column headings definedThe column headings in Table 38 on page 171 are defined as follows:

Column Description

Description states the parameter name and describes the parameter’s function; for consumer parameters, lists the collector parameters that gather the data displayed by this parameter

Active atInstallation

indicates whether the parameter is active or inactive by default

ParameterType

indicates the parameter type:

■ standard (std) gathers and displays a single data value;■ collector (coll) gathers multiple data values but has no display

capabilities■ consumer (con) displays values gathered by collector or standard

parameters.

Some standard parameters have collector properties.

BorderRangea

a Border ranges that are inactive by default might contain values that are not necessarily the values that are recommended for the parameter.

defines the default range for the parameter; can be set so that values that fall outside this range trigger warnings, alarms, or recovery actions

Alarm1Rangeb

b Alarm1 ranges that are inactive by default might contain values that are not necessarily the values that are recommended for the parameter.

specifies the thresholds for the first-level alarm; not applicable to collector parameters

Alarm2Range c

c Alarm2 ranges that are inactive by default might contain values that are not necessarily the values that are recommended for the parameter.

specifies the thresholds for the second-level alarm; not applicable to collector parameters

Scheduling(poll time)

specifies how frequently the parameter will run and collect data (polling cycle); not applicable to consumer parameters

Icon Style specifies whether the parameter is represented as a graph, gauge, text box, stoplight (signal), or Boolean state

Unit specifies the unit of measure in which the parameter output is expressed, such as a percentage, a number, or bytes


Abbreviations defined

Abbreviations definedThe abbreviations in Table 38 on page 171 are defined as follows:

Abbreviation Definition

bool Boolean; shows a state, such as on or off, OK or not OK

coll collector parameter

con consumer parameter

disc discovery; refers to the PATROL discovery process

GB gigabyte or gigabytes

hr hour or hours

KB kilobyte or kilobytes

MB megabyte or megabytes

MHz megahertz

min minute or minutes

msec millisecond or milliseconds

N no; parameter is inactive after KM is installed

NA not applicable; a value cannot be assigned

nsec nanosecond or nanoseconds

sec second or seconds

std standard parameter

TB terabyte or terabytes

undef undefined; a value can be set, but no default is provided

warn warning; type of alert

yes yes; parameter is active after KM is installed


Parameter table

Parameter tableTable 38 contains the parameters for the Informix, Informix XPO, and Informix ER components of BMC Performance Manager for Informix. Table 38 groups the parameters alphabetically by application class under each component.

Table 38 BMC Performance Manager for Informix parameters (part 1 of 35)

Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t

INFORMIX application (contains Informix, Informix XPO, and Informix ER components)

InstanceStatusMonitorGathers information about the status changes for the Informix IDS and XPO servers by using the results from Onstat. This parameter does not appear as an icon.

yes coll undef undef undef 60 sec none none

Informix Component

IFMXDS_AVAILABILITY application class

ArchiveLevel0Appears only when your environment uses Ontape to back up the server.Displays the number of days since the last level 0 archive.Collector: ArchiveMonitor

yes con undef 7–100warn

undef set by coll

graph number of days

ArchiveLevel1Appears only when your environment uses Ontape to back up the server.Displays the number of days since the last level 1 archive. Collector: ArchiveMonitor


undef set by coll



Parameter table

ArchiveLevel2Appears only when your environment uses Ontape to back up the server.Displays the number of days since the last level 2 archive. Collector: ArchiveMonitor


undef set by coll


CheckpointDurationDisplays the checkpoint interval for “Checkpoint Completed” messages. These messages are written to the Informix Dynamic Server error log that is defined by the MSGPATH configuration parameter. This instance must exceed thresholds 5 times before the alarms or warnings are activated.Collector: ErrorLogMonitor

yes con undef 3–4 warn

5–100 alarm

set by coll

graph number of sec

CheckpointFrequencyDisplays the number of minutes between checkpoints using the timestamp for “Checkpoint Completed” messages. These messages are written to the error log that is defined by the MSGPATH configuration parameter. Collector: ErrorLogMonitor


6–100alarm

set by coll

graph number of min

ChunkDownDisplays the number of chunks that are down for the server. Collector: Onstat_dMonitor

yes con 0–100alarm

undef 1–100alarm

set by coll

gauge number of chunks

DbsLevel0Appears only when your environment uses ON-Bar to back up the server.Displays the number of days since the last level 0 archive.Collector: OnbarMonitor

yes con 0–30 alarm

7–30 warn undef set by coll







Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table





EventSeverityCaptures and displays the severity rating for each event reported to the message log, and annotates the events of a severity level of 3, 4, or 5 with the error message. Collector: ErrorLogMonitor

yes con 3–5OK

3–3warn

4–5alarm

set by coll

graph severity level (1–5)

FailOverMonitorMonitors the secondary instance automatically once the failover occurs.

yes std undef 1-1warn

1-2alarm

1 min graph number

FullestChunkDisplays the percent full for the fullest chunk on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

gauge percentage full for the fullest chunk

FullestDbsDisplays the percent full for the fullest dbspace on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

gauge percentage full for fullest dbspace

FullestMetadataDisplays the percent full for the fullest metadata for the blob spaces on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

gauge percentage full for fullest metadata

InstanceStatusDisplays status changes for the server instance.Collector: InstanceStatusMonitor

yes con undef 1warn

2alarm

set by coll

bool none

LogSpaceDisplays the percentage of the total logical log space that is used for the server. Collector: Onstat_IMonitor


80–100alarm

set by coll

gauge percentage of total logical space used


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

OnBarActivityStatusChecks for warnings and errors found in the Informix ON-Bar Activity Log for each server.

yes std undef 1–1warn

2–50alarm

2 min bool none

OnBarFailuresAppears only when your environment uses On Bar to backup the server.Displays the number of failures found in the backup and recovery error log.

yes std 0-10 alarm

1–10 warn undef 12 hrs graph number of failures

UsedSpaceDisplays the percentage of total space used for each dbspace on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

graph percentage of total space used per dbspace

VPListDisplays a list of virtual processors for the server.Collector: VPMonitor

yes con undef undef undef set by coll

text none

VPTotalDisplays the total number of virtual processors on the server. Collector: VPMonitor


graph number of processors

IFMXDS_CAPACITY Application Class

ActiveLocksDisplays the percentage of total locks that are active for the server. Collector: OnstatMonitor


95–100alarm

set by coll

gauge percentage of total locks

BufferOverflowDisplays the number of attempts made to exceed the shared memory buffer limit (buffer overflows) for the server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


undef set by coll

graph number of attempts

BufferWaitsDisplays the number of buffer waits for the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


61–100alarm

set by coll

graph number of buffer waits


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

CheckpointWaitsDisplays the number of checkpoint waits for the selected server.Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


undef set by coll

graph number of checkpoint waits

Deadlock_TimeoutDisplays the number of times that a deadlock time out value was exceeded for the selected server.Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


51–100alarm

set by coll

graph number of deadlock timeouts

DeadlocksDisplays the number of potential deadlocks that were detected and prevented for the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


51–100alarm

set by coll

graph number of potential deadlocks

LatchWaitsDisplays the number of times a thread waits to access shared memory for the selected server.Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor

yes con undef undef 51–100alarm

set by coll

graph number of thread waits

LockOverflowDisplays the number of times an attempt was made to exceed the locks limit for the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


26–100alarm

set by coll


LockWaitsDisplays the number of times a thread waits for a lock for the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


21–100alarm

set by coll

gauge number of thread waits

PhysicalLogSizeDisplays the size of the physical log buffers for the selected server. Collector: Onstat_IMonitor


undef set by coll

gauge number of pages


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

TableOverflowDisplays the number of attempts to exceed the table space (tblspace) limits for the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


5–100alarm

set by coll


UserOverflowDisplays the total number of attempts to exceed the user limit on the selected server. Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


6–100alarm

set by coll


IFMXDS_COLLECTORS application class

ArchiveMonitorAppears only when Ontape is used to backup the server.Gathers the archive information by using the results from the oncheck -pr and by checking the sysutils database.


undef 12 hrs bool none

DBSpaceMonitorMonitors the dbspaces selected for monitoring using the Monitor by Dbspace menu command. For the selected dbspaces, it reports the space used versus the space allocated for each dbspace and the reads, the writes, the page reads, and the page writes for each chunk.


undef 25 min bool none

ERMonitorDiscovers and creates the Informix Enterprise Replication instances. The ER database must exist.



ErrorLogMonitorMonitors the Informix Dynamic Server error log, as defined by the MSGPATH configuration parameter, and displays the diagnostic and status messages written during operation by the selected server.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

FragCheckerMonitors the number of fragments for each monitored table and determines whether the number of fragments for a table exceeds the user-defined threshold. If the number of fragments for a table exceeds the threshold, then the IFMXDS_FRAG instances created for those fragments are deleted and replaced by IFMXDS_FRAG_SUM instances.


undef 12 hrs bool none

FragMonitorMonitors the logically fragmented tables listed by the FragChecker parameter for the selected server. Creates and destroys the Frag and Frag_Ext application instances.



OnbarMonitorAppears only when OnBar is used to back up the server.Uses the Informix OnBar utility to monitor the status of the level0, level1, and level2 backups for each instance.

yes std undef undef undef 12 hrs bool none

Onstat_dMonitorUses the onstat -d utility to monitor the chunks and dbspaces for the selected server. This collector also monitors the smart blob or metadata spaces.



Onstat_IMonitorUses the onstat -F utility to monitor the page cleaners and foreground writes for the selected server.



Onstat_IMonitorUses the onstat -l utility to monitor the information on the physical and logical logs on the selected server.



OnstatMonitorUses the onstat -p utility to monitor the profile counts for the selected server. Note: See “Changing profile statistics” on page 111.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

PDQMonitorMonitors the resources used by the Decision Support feature when it is activated.



SesMonitorMonitors the active user sessions on the selected server.



SQLViewerMonitorCaptures the SQL statements that are processed by the Informix Dynamic Server database engines for the selected server and writes them to a flat file defined by the user. This parameter does not display the sql statements directly; you can view the sql statements through the SQL Viewer menu selections.



TblMonitorMonitors the active tables in sysptprof for the selected server.



TBSMonitorMonitors the active tables by specified table or criteria for the selected server.



TempDBSMonitorMonitors the dbspaces and chunks, as defined by the DBSPACETEMP parameter in the ONCONFIG file, for the selected server when there are Temp DBSpaces in the ONCONFIG file. This parameter reports the space used versus the space allocated for each dbspace, and reports the reads, writes, page reads, and page writes for each chunk. It does not report on temp dbspaces if the value for DBSPACETEMP is set to ALL or NOTCRITICAL. This parameter is inactive if there are no temp dbspaces to monitor.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

UserMonitorMonitors the active user sessions by specified user, criteria, or session ID for the selected server. This standard parameter with collector properties creates the instances found under the IFMXDS_USER application.


undef 16 min

bool none

VPMonitorMonitors the virtual processors on the selected server. This collector sets the values for the VPList and VPTotal consumer parameters.



IFMXDS_DBS application class

DBSpaceAllocatedDisplays the percentage of total space in each dbspace that is allocated for the selected server.Collector: DBSpaceMonitor


80–90warn

90–100alarm

set by coll

gauge percentage of space allocated in each dbspace

DBSpaceUsedDisplays the percentage of total space on each dbspace that was used as of the last high water mark for the selected server. Collector: DBSpaceMonitor


80–90warn

90–100alarm

set by coll

gauge percentage of total space used on each dbspace

MetadataUsedDisplays the percentage of used metadata for each blob space for each instance.Collector: Onstat_dMonitor


80–90warn

90–100alarm

set by coll

gauge percentage of used metadata

IFMXDS_DBS_CHK application class

PageReadDisplays the number of page reads for each chunk for the selected server. Collector: DBSpaceMonitor


graph reads per chunk

PageWriteDisplays the number of page writes for each chunk for the selected server. Collector: DBSpaceMonitor


graph writes per chunk

ReadDisplays the number of reads for each chunk for the selected server.Collector: DBSpaceMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

WriteDisplays the number of writes for each chunk for the selected server. Collector: DBSpaceMonitor



IFMXDS_DBSTEMP application class

TempDBSpaceAllocatedDisplays the percentage of total space in each temporary dbspace that is allocated for the selected server. Collector: TempDBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of space that is allocated

TempDBSpaceUsedDisplays the percentage of total space on each temporary dbspace that was used as of the last high water mark for the selected server. Collector: TempDBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of space that is used

IFMXDS_DBSTEMP_CHK application class

TempPageReadDisplays the number of page reads for each chunk for the selected server. Collector: TempDBSpaceMonitor



TempPageWriteDisplays the number of page writes for each chunk for the selected server. Collector: TempDBSpaceMonitor


graph writers per chunk

TempReadDisplays the number of reads for each chunk for the selected server. Collector: TempDBSpaceMonitor



TempWriteDisplays the number of writes for each chunk for the selected server. Collector: TempDBSpaceMonitor



IFMXDS_FRAG_EXT application class

FragDeadLocksDisplays the number of deadlocks for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph deadlocks per partition


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

FragDeletesDisplays the number of deletes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph deletes per partition

FragLockRequestsDisplays the number of lock requests for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph lock requests per partition

FragLockWaitsDisplays the number of lock waits for each of the logically fragmented tblspaces (partitions) for the selected server.Collector: FragMonitor


graph lock waits per partition

FragPageReadsDisplays the number of page reads for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph reads per partition

FragPageWritesDisplays the number of page writes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph writes per partition

FragSeqScansDisplays the number of sequential scans for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor


graph sequential scans per partition

IFMXDS_FRAG_SUM application class

FragSDeadLocksDisplays a summary of the number of deadlocks for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of deadlocks per fragmented table


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

FragSDeletesDisplays a summary of the number of deletes for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of deletes per fragmented table

FragSLockRequestsDisplays a summary of the number of lock requests for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of lock requests per fragmented table

FragSLockWaitsDisplays a summary of the number of lock waits for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of lock waits per fragmented table

FragSPageReadsDisplays a summary of the number of page reads for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of page reads per fragmented table

FragSPageWritesDisplays a summary of the number of page writes for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of page writes per fragmented table

FragSSeqScansDisplays a summary of the number of sequential scans for the logically fragmented tablespaces (partitions) for each instance.Collector: FragMonitor


graph number of sequential scans per fragmented table

IFMXDS_PDQ application class

CpuVpUsageDisplays the percentage used of the CPU allocated to virtual processes (VPs). Collector: PDQMonitor


95–100 after 10 timesalarm

set by coll

graph percentage of CPU used


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

MemoryUsageDisplays the percentage used of the memory allocated to Decision Support. Collector: PDQMonitor


95–100alarm

set by coll

graph percentage of memory used

ScanThreadUsageDisplays the percentage used of the scan threads allocated to Decision Support. Collector: PDQMonitor


95–100alarm

set by coll

graph percentage of scan threads used

ScanThreadsAvailableDisplays the number of times the maximum number of scan threads is less than the maximum number of fragments found in any table in the instance. Collector: PDQMonitor


undef set by coll

bool none

IFMXDS_PERFORMANCE application class

CleanersDownDisplays the percentage of page cleaners that are down for the selected server. Collector: Onstat_FMonitor


65–100alarm

set by coll

gauge percentage of page cleaners down

DataDistributionDisplays the percentage of difference between the least accessed chunk and the most accessed chunk for the selected server.


55–100alarm

3 min gauge percentage difference between most and least accessed chunk

FgWritesDisplays the number of foreground writes for the selected server. Collector: Onstat_FMonitor


set by coll

graph number of foreground writes

IOQueueDisplays the maximum length of the I/O queue for the selected server.

yes std undef 31–100alarm

undef 14 min gauge maximum length of I/O queue

LogicalLogBufSizeDisplays the percentage of the total logical log buffer size pages used by each I/O for the selected server. Collector: Onstat_IMonitor


undef set by coll

gauge percentage of total logical log buffer size pages used per I/O


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

PhysicalLogBufSizeDisplays the percentage of the total physical log buffer size pages used for each I/O for the selected server. Collector: Onstat_IMonitor

yes con undef 40–60warn after 5 times

60-60alarm after 5 times

set by coll

gauge percentage of total physical log buffer size pages used per I/O

PhysicalLogUsedDisplays the number of pages in the physical log that are used for the selected server. Collector: Onstat_IMonitor


graph number of pages

ReadAheadDisplays the ratio of page reads to pages used for the selected server. Collector: OnstatMonitor


undef set by coll

graph ratio of page reads to pages used

ReadCacheDisplays the percentage of read requests that were satisfied from the memory buffers for the selected server. Collector: OnstatMonitor


undef set by coll

graph percentage of read requests that were satisfied

ReadyQueueDisplays the maximum length of the ready queue for the selected server.


undef 8 min graph maximum length for ready queue

ResponseTimeDisplays the response time in seconds for the selected server.

yes std 0–100alarm

31–60warn

61–100alarm

10 min graph number of sec

SysCpuDisplays the total CPU time used by all user threads on the selected server. Collector: OnstatMonitor


gauge percentage of CPU time used by threads

TabExtentsDisplays the number of table extents for each active table on the selected server.


16–100alarm

5 min graph number of table extents

TableScansDisplays the total number of table sequential scans on the selected server.Note: See “Changing profile statistics” on page 111.Collector: OnstatMonitor


graph number of table sequential scans


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

TblDeadLocksDisplays the total number of table deadlocks for the selected server. Collector: TblMonitor


21–100alarm

set by coll

graph number of table deadlocks

TblLockWaitsDisplays the total number of table lock waits for the selected server. Collector: TblMonitor


31–100alarm

set by coll

graph number of table lock waits

TblSeqScansDisplays the number of sequential scans for each active table on the selected server.Collector: TblMonitor


51–100alarm

set by coll

graph sequential scans per active table

UserCpuDisplays the percentage of total CPU usage by all user threads for the selected server. Collector: OnstatMonitor


gauge percentage of total CPU usage by all user threads

WriteCacheDisplays the percentage of write requests that were satisfied from memory buffers for the selected server. Collector: OnstatMonitor


undef set by coll

graph percentage of write requests that were satisfied

IFMXDS_TBS application class

TBSDeadLksDisplays the number of deadlocks for each of the monitored tblspaces (partitions) for the selected server.Collector: TBSMonitor



TBSDeletesDisplays the number of deletes for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



TBSLockReqsDisplays the number of lock requests for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

TBSLockWtsDisplays the number of lock waits for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



TBSPageReadsDisplays the number of page reads for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor


graph page reads per partition

TBSPageWritesDisplays the number of page writes for each of the monitored tblspaces (partitions) for the selected server.Collector: TBSMonitor


graph page writes per partition

TBSSeqScansDisplays the number of sequential scans for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



IFMXDS_USER application class

UserCurrLogSpaceDisplays the amount of log space used by the transaction in this user session since the last polling cycle.Collector: UserMonitor


graph percent of used log space

UserDeadLksDisplays the number of times that a deadlock was detected in this user session since the last polling cycle.Collector: UserMonitor


graph number of deadlocks

UserDiskSortsDisplays the number of sorts performed on disk instead of in memory by this user sessions since the last polling cycle.Collector: UserMonitor


graph number of sorts

UserLocksHeldDisplays the number of locks held by this user session since the last polling cycle.Collector: UserMonitor


graph number of locks held


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

UserLockTimeoutsDisplays the number of deadlock timeouts that occurred in this user session since the last polling cycle.Collector: UserMonitor


graph number of dead lock timeouts

UserLogRecordsDisplays the number of log records written in this user session since the last polling cycle.Collector: UserMonitor


graph number of log Displays written

UserLongTransDisplays the number of long transactions that occurred in this user session since the last polling cycle.Collector: UserMonitor


graph number of long transactions

UserMaxLogSpaceDisplays the percentage of the total log space that was used by any one transaction in this user session since the last polling cycle.Collector: UserMonitor


graph percent of log space used

UserMaxResourceWaitDisplays the maximum amount of time in seconds that this user session had to wait for resources since the last polling cycle.Collector: UserMonitor


graph number of seconds

UserPageReadsDisplays the number of page reads that occurred in this user session since the last polling cycle.Collector: UserMonitor


graph number of page reads

UserPageWritesDisplays the number of page writes that occurred in this user session since the last polling cycle.Collector: UserMonitor


graph number of page writes

UserSeqScansDisplays the number of sequential scans that occurred in this user session since the last polling cycle.Collector: UserMonitor


graph number of sequential scans


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

IFMXDS_USERS Application Class

LicensesUsedDisplays the percentage of the total number of licenses available that are currently in use for user sessions, according to onstat –u.Collector: SesMonitor


90–100alarm

set by coll

graph percentage of licenses in use

ProblemSessionsDisplays the percentage of the total active sessions that belong to users.Collector: SesMonitor


90–100alarm

set by coll

graph percentage of active sessions for users

ProblemUsersDisplays the percentage of the total I/O that is attributable to users.Collector: SesMonitor


90–100alarm

set by coll

graph percentage of I/O for users

SesDeadlocksDisplays the number of user session deadlocks for the selected server. Collector: SesMonitor


1–14warn

15–100alarm

set by coll


SesDeletesDisplays the number of user sessions deletes for the selected server. Collector: SesMonitor


50–99warn

undef set by coll

graph number of deletes

SesHeldResourcesDisplays the longest amount of time a user session waited for a resource for the selected server. Collector: SesMonitor


10–100alarm

set by coll

graph number of sec

SesLocksHeldDisplays the number of locks held for user sessions for the selected server. Collector: SesMonitor

yes con 0–100 50–99warn

undef set by coll


SesLongTxsDisplays the number of long transactions caused by user sessions for the selected server.Collector: SesMonitor


5–100alarm

set by coll


SesSeqScansDisplays the number of sequential scans for user sessions for the selected server. Collector: SesMonitor


31–100alarm

set by coll

graph number or sequential scans


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

Extended Parallel Option (XPO) Component

IFMXPO_AVAILABILITY Application Class

CheckpointTimeDisplays the average checkpoint interval for “Checkpoint completed” messages written to the Informix error log, as defined by the MSGPATH configuration path.Collector: ErrorLogMonitor


graph check point interval in seconds

ChunkDownDisplays information on the chunks that are down.Collector: Onstat_dMonitor


text none

EventSeverityCaptures and displays the severity rating for each event reported to the message log, and annotates the events of a severity level of 3, 4, or 5 with the error message. Collector: ErrorLogMonitor

yes con undef 3warn

4–5alarm

set by coll

graph severity level (3, 4, or 5)

FullestChunkDisplays the percent full for the fullest chunk on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

gauge percentage full for the fullest chunk

FullestDbsDisplays the percent full for the fullest dbspace on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

gauge percentage full for fullest dbspace

InstanceStatusIf Instance Always On Line was selected when the instance was configured and the instance goes down without good cause or it is placed in Quiescent Mode, then this parameter goes into the alarm state.If Instance Always On Line was NOT selected, then this parameter does not go into the alarm state when the server goes off line, no matter the cause. Collector: InstanceStatusMonitor


2–2alarm

set by coll

bool none


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

LogSpaceDisplays the percentage of the total logical log space that is used for the server. Collector: Onstat_IMonitor


80–100alarm

5 min gauge percentage of total logical space used

UsedSpaceDisplays the percentage of total space used for each dbspace on the server. Collector: Onstat_dMonitor


90–100alarm

set by coll

graph percentage of total space used per dbspace

VPListDisplays a list of virtual processors for the server.Collector: VPMonitor


text none

VPTotalDisplays the total number of virtual processors on the server. Collector: VPMonitor


graph number of processors

IFMXPO_CAPACITY application class

ActiveLocksDisplays the number of total locks that are active.Collector: OnstatMonitor


95–100alarm

set by coll

gauge number of active locks

BufferOverflowDisplays the number of attempts made to exceed the shared memory buffer limit (buffer overflows) for the server. Collector: OnstatMonitor


undef set by coll


BufferWaitsDisplays the number of buffer waits for the selected server.Collector: OnstatMonitor


61–100alarm

set by coll

graph number of buffer waits

CheckpointWaitsDisplays the number of checkpoint waits for the selected server. Collector: OnstatMonitor


undef set by coll

graph number of check point waits

Deadlock_TimeoutDisplays the number of times that a deadlock timeout value was exceeded for the selected server. Collector: OnstatMonitor


51–100alarm

set by coll

graph number of dead lock time outs


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

DeadlocksDisplays the number of potential deadlocks that were detected and prevented for the selected server. Collector: OnstatMonitor


51–100alarm

set by coll

graph number of potential dead locks

LatchWaitsDisplays the number of times a thread waits to access shared memory for the selected server.Collector: OnstatMonitor


set by coll

graph number of thread waits

LockOverflowDisplays the number of times an attempt was made to exceed the locks limit for the selected server. Collector: OnstatMonitor


26–100alarm

set by coll


LockWaitsDisplays the number of times a thread waits for a lock for the selected server. Collector: OnstatMonitor


21–100alarm

set by coll

gauge number of thread waits

PhysicalLogSizeDisplays the size of the physical log buffers for the selected server. Collector: Onstat_IMonitor


undef set by coll

gauge number of pages

TableOverflowDisplays the number of attempts to exceed the table space (tblspace) limits for the selected server. Collector: OnstatMonitor


5–100alarm

set by coll


UserOverflowDisplays the total number of attempts to exceed the user limit on the selected server. Collector: OnstatMonitor


6–100alarm

set by coll


IFMXPO_COLLECTORS application class

CollectorStatusDisplays error messages produced by any of the collector or standard parameters that issue collection commands. BMC Performance Manager for Informix


text none


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

DBSpaceMonitorMonitors the Informix dbspaces and chunks for each coserver and then reports the space used versus the space allocated for each dbspace and the reads, the writes, the page reads, and the page writes for each chunk.



ErrorLogMonitorMonitors the Informix XPO or XPS error log, as defined by the MSGPATH configuration parameter, and displays the diagnostic and status messages.



FragCheckerMonitors the number of fragments for each monitored table and determines whether the number of fragments for a table exceeds the user-defined threshold set using the Set Fragment Threshold menu command. If the number exceeds the threshold, the IFMXPO_FRAG instances created for those fragments are deleted and replaced by IFMXPO_FRAG_SUM instances.

yes std undef 1–50 undef 12 hrs bool none

FragMonitorThis parameter is not available for Informix-OnLine XPS 8.11.Monitors for each coserver the logically fragmented tables listed by the FragChecker parameter.Creates and destroys the INFXPO_ FRAG and IFMXPO_FRAG_EXT instances.



Onstat_dMonitorUses the onstat -d utility to monitor the chunks and dbspaces for each coserver.



Onstat_FMonitorUses the onstat -F utility to monitor the Informix-Online XPS 8.11 or 8.21 page cleaners and foreground writes for each coserver.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

Onstat_IMonitorUses the onstat -l utility to monitor the Informix-Online XPS 8.11 or XPS 8.21 for information on the physical and logical logs.



OnstatMonitorUses the onstat -p utility to monitor the Informix-Online XPS 8.11 or 8.21 profile counts.



SesMonitorMonitors the Informix-Online XPS 8.11 or 8.21 active user sessions on each coserver.



SQLViewerMonitorCaptures the SQL statements that are processed by the Informix database engines and writes them to a flat file of the user’s choosing. The SQLViewerMonitor parameter does not display the sql statements directly; you can view the sql statements through the SQL Viewer menu selections.



TblMonitorThis parameter is not available for Informix-OnLine XPS 8.11.Monitors the Informix-Online XPS 8.11 or 8.21 active tables in sysptprof for each coserver.



TBSMonitorThis parameter is not available for Informix-OnLine XPS 8.11.Monitors the Informix-Online XPS 8.11 or 8.21 active tables by specified table or criteria.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

TempDBSMonitorMonitors the Informix-Online XPS 8.11 or 8.21 dbspaces and chunks as defined in the ONCONFIG file parameter DBSPACETEMP, reports the space used versus the space allocated for each dbspace, and reports the reads, writes, page reads, and page writes for each chunk.It does not report on temp dbspaces if the value for DBSPACETEMP in the ONCONFIG file is set to ALL or NOTCRITICAL.



UserMonitorMonitors the Informix XPS or XPO active user sessions by specified user, criteria, or session ID for each coserver and creates the instances found under the IFMXPO_USER application.



VPMonitorMonitors the Informix-Online XPS 8.11 or 8.21 virtual processors on each coserver.



IFMXPO_CORRELATORS application class

CoserverCorrelatorCompares the coserver instances with the coserver definitions in the ONCONFIG file and if they do not match, the value in the graph is set to 1, which triggers a warning alarm.


undef 1 min graph 0 or 1 (matches or does not match the number of coserver definitions)

DbsAllocCorrelatorMonitors the distribution of allocated dbspaces in dbslices across coservers. This parameter calculates and displays the percentage of difference between the lowest amount of dbspace allocated by a coserver and the highest amount of dbspace allocated by a coserver.


undef 5 min graph percentage of difference


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

DbsUsedCorrelatorMonitors the distribution of used dbspaces in dbslices across the coservers. This parameter calculates and displays the percentage of difference between the three lowest amounts of dbspace used by a coserver and the highest amount of dbspace used by a coserver.


undef 5 min graph percentage of difference

VPCorrelatorCompares the number of virtual processors (vps) on the root node (coserver.1) with the number of vps on each coserver node. If any node has more or fewer vps than the root node, the value in the graph is set to 1, which triggers a warning.


undef 1 min graph 0 or 1

IFMXPO_DBS Application Class

DBSpaceAllocatedDisplays the percentage of total space in each dbspace that is allocated for each coserver.Collector: DBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of space allocated in each dbspace

DBSpaceUsedDisplays the percentage of total space on each dbspace that was used for each coserver. Collector: DBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of total space used on each dbspace

IFMXPO_DBS_CHK application class

PageReadDisplays the number of page reads for each chunk for the selected server. Collector: DBSpaceMonitor


graph number of page reads per chunk

PageWriteDisplays the number of page writes for each chunk for the selected server. Collector: DBSpaceMonitor


graph number of page writes per chunk

ReadDisplays the number of reads for each chunk for the selected server.Collector: DBSpaceMonitor


graph number of reads per chunk


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

WriteDisplays the number of writes for each chunk for the selected server. Collector: DBSpaceMonitor


graph number of writes per chunk

IFMXPO_DBSTEMP application class

TempDBSpaceAllocatedDisplays the percentage of total space in each temporary dbspace that is allocated for the selected server. Collector: TempDBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of space that is allocated

TempDBSpaceUsedDisplays the percentage of total space on each temporary dbspace that was used. Collector: TempDBSpaceMonitor


80–89warn

90–100alarm

set by coll

gauge percentage of space that is used

IFMXPO_DBSTEMP_CHK application class

TempPageReadDisplays the number of page reads for each chunk for the selected server. Collector: TempDBSpaceMonitor


graph number of page reads per chunk

TempPageWriteDisplays the number of page writes for each chunk for the selected server. Collector: TempDBSpaceMonitor


graph number of page writes per chunk

TempReadDisplays the number of reads for each chunk for the selected server. Collector: TempDBSpaceMonitor


graph number of reads per chunk

TempWriteDisplays the number of writes for each chunk for the selected server. Collector: TempDBSpaceMonitor


graph number of writes per chunk

IFMXPO_FRAG_EXT application class

FragDeadLksDisplays the number of deadlocks for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

FragDeletesDisplays the number of deletes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragLockReqsDisplays the number of lock requests for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragLockWtsDisplays the number of lock waits for each of the logically fragmented tblspaces (partitions) for the selected server.Collector: FragMonitor



FragPageReadsDisplays the number of page reads for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragPageWritesDisplays the number of page writes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSeqScansDisplays the number of sequential scans for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

IFMXPO_FRAG_SUM application class

FragSDeadLocksDisplays the number of deadlocks for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSDeletesDisplays the number of deletes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSLockRequestsDisplays the number of lock requests for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSLockWaitsDisplays the number of lock waits for each of the logically fragmented tblspaces (partitions) for the selected server.Collector: FragMonitor



FragSPageReadsDisplays the number of page reads for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSPageWritesDisplays the number of page writes for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor



FragSSeqScansDisplays the number of sequential scans for each of the logically fragmented tblspaces (partitions) for the selected server. Collector: FragMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

IFMXPO_PERFORMANCE application class

CleanersDownDisplays the percentage of page cleaners that are down for the selected server. Collector: Onstat_FMonitor


66–100alarm

set by coll

gauge percentage of page cleaners down

DataDistributionDisplays the percentage of difference between the least accessed chunk and the most accessed chunk for the selected server.


56–100alarm

3 min gauge percentage difference between most and least accessed chunk

FgWritesDisplays the number of foreground writes for the selected server. Collector: Onstat_FMonitor


6–100alarm

set by coll

graph number of foreground writes

IOQueueDisplays the maximum length of the Informix XPO or XPS I/O queue.


undef 14 min gauge maximum length of I/O queue

LogicalLogBufSizeDisplays the percentage of the total logical log buffer size pages used by each I/O for the selected server. Collector: Onstat_IMonitor


undef set by coll

gauge percentage of total logical log buffer size pages used per I/O

PhysicalLogBufSizeDisplays the percentage of the total physical log buffer size pages used for each I/O for the selected server. Collector: Onstat_IMonitor


1–39alarm

set by coll

gauge percentage of total physical log buffer size pages used per I/O

PhysicalLogUsedDisplays the number of pages in the physical log that are used for the selected server. Collector: Onstat_IMonitor


graph number of pages

ReadAheadDisplays the ratio of page reads to pages used for the selected server. Collector: OnstatMonitor


undef set by coll

graph ratio of page reads to pages used


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

ReadCacheDisplays the percentage of read requests that were satisfied from the memory buffers for the selected server. Collector: OnstatMonitor


undef set by coll

graph percentage of read requests that were satisfied

ReadyQueueDisplays the maximum length of the ready queue for the selected server.


undef 8 min graph maximum length for ready queue

ResponseTimeDisplays the response time in seconds for the selected server.

yes std 0–100 31–60 61–100 10 min graph number of sec

SysCpuDisplays the total CPU time used by all user threads on the selected server. Collector: OnstatMonitor


gauge percentage of CPU time used by threads

TabExtentsDisplays the number of table extents for each active table on the selected server.


16–100alarm

5 min graph number of table extents

TableScansDisplays the total number of table sequential scans on the selected server. Collector: OnstatMonitor


graph number of table sequential scans

TblDeadLocksDisplays the total number of table deadlocks for the selected server. Collector: TblMonitor


21–100alarm

set by coll

graph number of table deadlocks

TblLockWaitsDisplays the total number of table lock waits.Collector: TblMonitor


31–100alarm

set by coll

graph number of waits

TblSeqScansDisplays the number of sequential scans for each active table on the selected server.Collector: TblMonitor


51–100alarm

set by coll

graph sequential scans per active table

UserCpuDisplays the percentage of total CPU usage by all user threads for the selected server. Collector: OnstatMonitor


gauge percentage of total CPU usage by all user threads


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

WriteCacheDisplays the percentage of write requests that were satisfied from memory buffers for the selected server. Collector: OnstatMonitor


undef set by coll

graph percentage of write requests that were satisfied

IFMXPO_TBS application class

TBSDeadLksDisplays the number of deadlocks for each of the monitored tblspaces (partitions) for the selected server.Collector: TBSMonitor



TBSDeletesDisplays the number of deletes for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



TBSLockReqsDisplays the number of lock requests for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



TBSLockWtsDisplays the number of lock waits for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor



TBSPageReadsDisplays the number of page reads for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor


graph page reads per partition

TBSSeqScansDisplays the number of sequential scans for each of the monitored tblspaces (partitions) for the selected server. Collector: TBSMonitor




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

IFMXPO_USERS application class

SesDeadlocksDisplays the number of user session deadlocks for the selected server. Collector: SesMonitor


1–14warn

15–100alarm

set by coll


SesDeletesDisplays the number of user sessions deletes for the selected server. Collector: SesMonitor


50–99warn

undef set by coll

graph number of deletes

SesHeldResourcesDisplays the longest amount of time a user session waited for a resource for the selected server. Collector: SesMonitor


10–100alarm

set by coll

graph number of sec

SesLocksHeldDisplays the number of locks held for user sessions for the selected server. Collector: SesMonitor

yes con 0–100 50–99warn

undef set by coll


SesLongTxsDisplays the number of long transactions caused by user sessions for the selected server.Collector: SesMonitor


5–100alarm

set by coll


SesSeqScansDisplays the number of sequential scans for user sessions for the selected server. Collector: SesMonitor


31–100alarm

set by coll

graph number or sequential scans


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

Enterprise Replication (ER) Component

IFMXER Application Class

ERATSSpaceMonitors the space in the file system where the aborted transaction spooling (ATS) files are located. Collector: ERSpoolMonitor


95–100alarm

set by coll

graph percentage used

ERATSSpoolMonitors the aborted transaction spooling (ATS) directory and issues an alarm if one or more aborted transaction files are created.Collector: ERSpoolMonitor

yes con undef 1–100alarm

undef set by coll

graph number of files

ERConnectStateMonitors the state of the connection for the server. Collector: ERServerMonitor

yes con undef 1warn

2–50alarm

set by coll

bool none

ERErrorMonitors the number of errors that have occurred since the last polling cycle. Collector: ERErrorMonitor


undef set by coll

graph number of errors

ERReceiveQueueMonitors the percentage of dbspace used by the receive queue. Collector: ERQueueMonitor


95–100 alarm

set by coll

graph percentage of used dbspace

ERRISSpaceMonitors the space in the file system where the row information spooling (RIS) files are located. Collector: ERSpoolMonitor


95–100alarm

set by coll

graph percentage full

ERRISSpoolMonitors the row information spooling (RIS) directory and goes into an alarm state if one or more files are sent to the directory. Collector: ERSpoolMonitor


undef set by coll

graph number of files

ERSendQueueMonitors the percentage of dbspace used by the send queue.Collector: ERQueueMonitor


95–100alarm

set by coll

graph percentage used


Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

ERServerStateMonitors the state of the replicate server. Collector: ERServerMonitor


undef set by coll

bool none

IFMXER_COLLECTORS application class

ERErrorMonitorCollects data from the error log and sends the data on new errors to the ERError consumer parameter.



ERQueueMonitorMonitors the status of the receive queue and the send queue. Collects data about the send and receive queues are using dbspace and sends the data to the ERSendQueue and ERReceiveQueue consumer parameters. Also creates the IFMXER_QUEUE application instances.



ERReplicateMonitorCollects data about all of the replicates that you have defined and creates the IFMXER_Replicate, the IFMXER_Participant, and the IFMXER_REPLGRP/SETS application instances; populates the IFMXER_Replicate, the IFMXER_Participant, and the IFMXER_REPLGRP/SETS application InfoBoxes; and provides the data for the Replicates report.



ERServerMonitorCollects data that the servers defined in the PATROL KM for Informix ER and sends the data to the ERConnectState and ERServerState consumer parameters. Also creates the IFMXER_SERVERGRP/SETS instances.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table

ERSpoolMonitorMonitors the aborted-transaction spooling (ATS) and the row-information spooling (RIS) processes and the ATS and RIS spooling file directories.



ERThreadMonitorMonitors the status of all of the threads related to the enterprise replication process.




Parameter Act

ive

atin

stal

lati

on

Para

met

erty

pe

Bord

erra

nge

Ala

rm1

rang

e

Ala

rm2

rang

e

Sche

dulin

g(p

oll t

ime)

Icon

sty

le

Uni

t


Parameter table


A p p e n d i x C
C Collector-consumer dependencies
This appendix contains the following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Parameter dependencies for the Informix component . . . . . . . . . . . . . . . . . . . . . . . . . 208Parameter dependencies for the Informix XPO component . . . . . . . . . . . . . . . . . . . . 213Parameter dependencies for the Informix ER component. . . . . . . . . . . . . . . . . . . . . . 216

Appendix C Collector-consumer dependencies 207

Overview

OverviewA consumer parameter depends on a collector parameter, or a standard parameter that is used as a collector, to set its value or to feed it information. If you disable a collector parameter, you also disable its corresponding consumer parameters.

The tables in this appendix reveal at a glance which collector parameters set which consumer parameters for the Informix, Informix Extended Parallel Option (XPO), and Informix Enterprise Replication (ER) components of PATROL for Informix. Collector parameters are listed alphabetically across the top, and consumer parameters are listed alphabetically in the left column. Standard parameters also appear in the left column, but they are not referenced to a collector since they collect their own information.

Collector, consumer, and standard parameters can have other dependencies to other parameters, menu commands, or application classes. See the BMC Performance Manager for Informix online Help for complete descriptions of individual parameters.

For descriptions and default values for the parameters, see Appendix B, “Parameter definitions and defaults.”

Parameter dependencies for the Informix component

Table 39 on page 209 provides the collector-consumer dependencies for the parameters in the Informix component of PATROL for Informix.

The SQLViewerMonitor, ERMonitor, and FragChecker collectors are not listed in Table 39 on page 209 because they do not set any consumer parameter values.

Standard parameters that collect and display their own data, do not depend on a collector, and do not set any consumers are listed in Table 39 on page 209 and are shaded.



Table 39 Informix Component Collector and Consumer Dependencies (part 1 of 4)

Consumersand standards Co

llect

ors

Arc

hive

Mon

itor

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Mon

itor

Inst

ance

Stat

usM

onit

or

Onb

arM

onit

or

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or

ActiveLocks X

ArchiveLevel0 X

ArchiveLevel1 X

ArchiveLevel2 X

BufferOverflow X

BufferWaits X

CheckpointDuration X

CheckpointFrequency X

CheckpointWaits X

ChunkDown X

CleanersDown X

CpuVpUsage

DataDistribution

DbsLevel0 X

DbsLevel1 X

DbsLevel2 X

DBSpaceAllocated X X

DBSpaceUsed X X

Deadlock_Timeout X

Deadlocks X

EventSeverity X

FgWrites X

FragDeadLocks X

FragDeletes X

FragLockRequests X

FragLockWaits X

FragPageReads X

FragPageWrites X

FragSDeadLocks X

FragSDeletes X

FragSeqScans X

FragSLockRequests X



FragSLockWaits X

FragSPageReads X

FragSPageWrites X

FragSSeqScans X

FullestChunk X

FullestDbs X

FullestMetadata X

InstanceStatus X

IOQueue

LatchWaits X

LicensesUsed X

LockOverflow X

LockWaits X

LogicalLogBufSize X

LogSpace X

MemoryUsage

MetadataUsed X

OnBarActivityStatus

OnbarFailures

PageRead X X

PageWrite X X

PDQMonitor

PhysicalLogBufSize X

PhysicalLogSize X

PhysicalLogUsed X

ProblemSessions X

ProblemUsers X

Read X X

ReadAhead X

ReadCache X

ReadyQueue

ResponseTime



llect

ors

Arc

hive

Mon

itor

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Mon

itor

Inst

ance

Stat

usM

onit

or

Onb

arM

onit

or

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or



ScanThreadsAvailable

ScanThreadUsage

SesDeadlocks X

SesDeletes X

SesHeldResources X

SesLocksHeld X

SesLongTxs X

SesSeqScans X

SysCpu X

TabExtents

TableOverflow X

TableScans X

TblDeadLocks X

TblLockWaits X

TblSeqScans X

TBSDeadLks X

TBSDeletes X

TBSLockReqs X

TBSLockWts X

TBSPageReads X

TBSPageWrites X

TBSSeqScans X

TempDBSpaceAllocated X

TempDBSpaceUsed X

TempPageRead X

TempPageWrite X

TempRead X

TempWrite X

UsedSpace X

UserCpu X

UserCurrLogSpace X

UserDeadLks X



llect

ors

Arc

hive

Mon

itor

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Mon

itor

Inst

ance

Stat

usM

onit

or

Onb

arM

onit

or

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or



UserDiskSorts X

UserLocksHeld X

UserLockTimeouts X

UserLogRecords X

UserLongTrans X

UserMaxLogSpace X

UserMaxResourceWait X

UserOverflow X

UserPageReads X

UserPageWrites X

UserSeqScans X

VPList X

VPTotal X

Write X X

WriteCache X



llect

ors

Arc

hive

Mon

itor

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Mon

itor

Inst

ance

Stat

usM

onit

or

Onb

arM

onit

or

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or


Parameter dependencies for the Informix XPO component


Table 40 provides the collector-consumer dependencies for the parameters in the Informix XPO component of PATROL for Informix.

Standard parameters that collect and display their own data, do not depend on a collector, and do not set any consumers are listed in Table 40 and are shaded.

Table 40 XPO component collector and consumer dependencies (part 1 of 3)


llect

ors

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Chec

ker

Frag

Mon

itor

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

SQLV

iew

erM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or

ActiveLocks X

BufferOverflow X

BufferWaits X

CheckpointTime X

CheckpointWaits X

ChunkDown X

CleanersDown X

CollectorStatus (All collectors send status to this consumer)

X X X X X X X X X X X X X X X

CoserverCorrelator

DataDistribution

DbsAllocCorrelator

DBSpaceAllocated X

DBSpaceUsed X

DbsUsedCorrelator

Deadlock_Timeout X

Deadlocks X

EventSeverity X

FgWrites X

FragDeadLks X

FragDeletes X

FragLockReqs X

FragLockWts X

FragPageReads X



FragPageWrites X

FragSeqScans X

FullestChunk X

FullestDbs X

IOQueue

LatchWaits X

LockOverflow X

LockWaits X

LogSpace

LogicalLogBufSize X

PageRead X

PageWrite X

PhysicalLogBufSize X

PhysicalLogSize X

PhysicalLogUsed X

Read X

ReadAhead X

ReadCache X

ReadyQueue

ResponseTime

SesDeadlocks X

SesDeletes X

SesHeldResources X

SesLocksHeld X

SesLongTxs X

SesSeqScans X

SysCpu X

TabExtents

TableOverflow X

TableScans X

TblDeadLocks X

TblLockWaits X

TblSeqScans X



llect

ors

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Chec

ker

Frag

Mon

itor

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

SQLV

iew

erM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or



TBSDeadLks X

TBSDeletes X

TBSLockReqs X

TBSLockWts X

TBSPageReads X

TBSPageWrites X

TBSSeqScans X

TempDBSpaceAllocated X

TempDBSpaceUsed X

TempPageRead X

TempPageWrite X

TempRead X

TempWrite X

UsedSpace X

UserCpu X

UserOverflow X

VPCorrelator

VPList X

VPTotal X

Write X

WriteCache X



llect

ors

DBS

pace

Mon

itor

Erro

rLog

Mon

itor

Frag

Chec

ker

Frag

Mon

itor

Ons

tat_

dMon

itor

Ons

tat_

FMon

itor

Ons

tat_

IMon

itor

Ons

tatM

onit

or

SesM

onit

or

SQLV

iew

erM

onit

or

TblM

onit

or

TBSM

onit

or

Tem

pDBS

Mon

itor

Use

rMon

itor

VPM

onit

or


Parameter dependencies for the Informix ER component

Parameter dependencies for the Informix ER component

Table 41 provides the collector-consumer dependencies for the parameters in the Informix ER component of PATROL for Informix.

The ERReplicateMonitor and ERThreadMonitor collectors are not listed in Table 41 because they do not set any consumer parameter values.

Table 41 ER component collector and consumer dependencies

Consumers Colle

ctor

s

ERErrorMonitor ERQueueMonitor ERServerMonitor ERSpoolMonitor

ERATSSpace X

ERATSSpool X

ERConnectState X

ERError X

ERReceiveQueue X

ERRISSpace X

ERRISSpool X

ERSendQueue X

ERServerState X


A p p e n d i x D
D Agent configuration variables
This appendix covers the following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Configuration variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Appendix D Agent configuration variables 217

Overview

OverviewThe variables described in this section are BMC Performance Manager for Informix variables that are set in the PATROL Agent. You can use the PATROL Configuration Manager or the wpconfig utility to view variable settings or to deploy them to other computer. See the PATROL Configuration Manager User Guide or the PATROL Agent Reference Manual for more information.

The variables in BMC Performance Manager for Informix are read only when the PATROL agent initializes. If any of the variables are modified by means other than through the menu commands in BMC Performance Manager for Informix, no changes appear until the PATROL Agent is restarted.

Configuration variablesTable 42 contains descriptions of the Agent Configuration Variables generated by BMC Performance Manager for Informix.

WARNING Do not use the wpconfig utility or PATROL Configuration Manager to remove variables, modify variables, or add new variables. Doing so may prevent some functions from working properly and can affect your entire installation. Many BMC Performance Manager for Informix variables are set by menu commands or functions. BMC Software recommends that you use the menu commands to change these variables.

Table 42 BMC Performance Manager for Informix agent configuration variables (part 1 of 6)

Variable Description

/InformixConfig/blackout contains blackout information for all instances of BMC Performance Manager for Informix

You must use the KM Admin => Blackout menu command from the INFORMIX application instance to change this variable.

/InformixConfig/InstanceName/blackout contains blackout information for a single instance of BMC Performance Manager for Informix

You must use the KM Admin => Blackout menu command from the IFMXDS application instance to change this variable.

/AgentSetup/defaultAccount contains PATROL account information

/InformixConfig/INFORMIX/AppCategories indicates the applications that are selected to monitor the instance



/InformixConfig/INFORMIX/AppCategoryDefaults

indicates the applications that monitor the instance by default

/InformixConfig/INFORMIX/ConfiguredInstList lists the instances that are configured for monitoring

You must use the KM Admin => Instance Configuration menu commands to change this variable.

/InformixConfig/InstanceName/Cumulative

indicates whether profile count parameter values for the engine are delta or cumulative per polling cycle

You must use the KM Admin => Profile Statistic => Profile Statistics Cumulative menu command to change this variable.

/InformixConfig/InstanceName/CurrSesSelLimit

indicates the maximum number of sessions that you can select for monitoring

You must use the KM Admin => User Monitoring Admin => Configure Session Monitor menu command to change this variable.

/InformixConfig/InstanceName/CurrTblSelLimit

indicates the maximum number of tables that you can select for monitoring

You must use the KM Admin => Table Monitoring Admin => Configure Table Monitor to change this variable.

/InformixConfig/InstanceName/DBExclList

lists the databases that were excluded from monitoring

You must use the KM Admin => Exclude or Include => Dbspace Exclude or Include => Database Exclude or Include menu command to change this variable.

/InformixConfig/InstanceName/DBSExclList

lists the DBSpaces that are excluded from general DBSpace monitoring

You must use the KM Admin => Exclude or Include => Dbspace Exclude or Include menu command to change this variable.

/InformixConfig/InstanceName/DBSInclList

lists the DBSpaces that are included for detailed DBSpace monitoring

You must use the KM Admin => DBSpace Monitoring Admin => Monitor by DBSpace menu command to change this variable.

/InformixConfig/InstanceName/FragInfoList

contains the information for each monitored fragmented table

This Informix account information is entered the first time the KM Admin => Fragment Monitoring Admin => Monitor by Fragmented Table menu command is accessed.





/InformixConfig.InstaceName.FailoverMonitoring.Active

Indicates FailoverMonitoring is active or not.

/InformixConfig.InstaceName.FailoverMonitoring. AlternateConfigPath

Indicates the onconfig file path on the secondary machine

/InformixConfig.InstaceName.FailoverMonitoring. AlternateHost

Indicates the secondary host name

/InformixConfig.InstaceName.FailoverMonitoring. AlternateINFHome

Indicates INFORMIXDIR on secondary host

/InformixConfig.InstaceName.FailoverMonitoring. AlternateINFSid

Indicates IDS instance name of the secondary machine

/InformixConfig.InstaceName.FailoverMonitoring. AlternateInfVersion

Indicates IDS version on the secondary machine.

/InformixConfig.InstaceName.FailoverMonitoring. AlternatePort

Indicates the PATROL Agent port number on the secondary machine.

/InformixConfig.InstaceName.FailoverMonitoring. LocalFailoverSqlhostsPath

Indicates SQLHOSTS file path of the secondary machine.

/InformixConfig.InstaceName.FailoverMonitoring. Primary

Indicates the IDS instance name on the primary machine.

/InformixConfig.InstaceName.FailoverMonitoring. Secondary

Indicates the IDS instance name on the secondary machine.

/InformixConfig/InstanceName/FragMonitor/.defaultAccount

contains the Informix account information that PATROL uses to connect to the various databases that contain fragmented tables

This Informix account information is entered the first time the KM Admin => Fragment Monitoring Admin => Monitor by Fragmented Table menu command is accessed.

/InformixConfig/InstanceName/FragTableList

lists the fragmented tables that are selected for monitoring

You must use the KM Admin => Fragment Monitoring Admin => Monitor by Fragmented Table menu command to change this variable.

/InformixConfig/InstanceName/FragThreshold

contains the number of fragments, as defined by the user, that causes BMC Performance Manager for Informix to monitor the fragmented tables in summary instead of providing details on each fragment

You must use the KM Admin => Fragment Monitoring Admin => Set Frag Threshold menu command to change this variable.





/InformixConfig/INFORMIX/InstConfiguration

contains the discovery configuration information for the instance


/InformixConfig/INFORMIX/InstExclList lists the instances that are excluded from monitoring

You must use the KM Admin => Instance Configuration => Exclude Instances menu command to change this variable.

/InformixConfig/InstanceName/LocalChannelLimit

contains the number of concurrent query sessions that are allowed, not including the global channel

You must use the KM Admin => Channel Admin => Limit Local Channels menu command to change this variable.

/InformixConfig/InstanceName/MonitoredFragDBList

lists the databases that contain the monitored fragmented tables

You must use the KM Admin => Fragment Monitoring Admin => Monitor by Fragmented Table menu command to change this variable.

/InformixConfig/INFORMIX/MonitoredInstList lists the Informix instances that are configured for monitoring


/InformixConfig/InstanceName/OnbarDBSExclList

lists the DBSpaces that are excluded from being monitored by the OnbarMonitor

You must use the KM Admin => Exclude or Include => Dbspace Exclude for OnBar menu command to change this variable.

/InformixConfig/InstanceName/OnbarFailureTimestamp

contains the timestamp of the last check for OnBar failures

/InformixConfig/InstanceName/OrderByStr

contains the query clause that specifies the order of results from TblMonitor

You must use the KM Admin => Table Monitoring Admin => Configure Table Monitor menu command to change this variable.

/InformixConfig/InstanceName/ResponseTime/.defaultAccount

contains the account information that is necessary to connect to the user specified database of the query that is used for response time monitoring

You must use the KM Admin => Response Time User Defined menu command from the INFORMIX application instance to change this variable.





/InformixConfig/InstanceName/RespTimeInfo

contains the query that is used to check response time

You must use the KM Admin => Response Time User Defined menu command from the INFORMIX application instance to change this variable.

/InformixConfig/INFORMIX/ScrollLimit displays the number that sets the limit for how many records PATROL can place in the scrollable region of some selection screens for all instances

You must use the KM Admin => Modify Scroll Limit menu command from the INFORMIX application instance to change this variable.

/InformixConfig/InstanceName/ScrollLimit

displays the number that sets the limit for how many records PATROL can place in the scrollable region of some selection screens for the instance

You must use the KM Admin => Modify Scroll Limit menu command from the IFMXDS or IFMXPO application to change this variable.

/InformixConfig/InstanceName/SQLViewConf

contains the directory where selected queries are placed and states the number of days that those queries are saved

You must use the KM Admin => SQL Viewer menu commands to change this variable.

/InformixConfig/InstanceName/TableCriteria

indicates the top number of entries to process and the column used as the key for the selection of tables for detailed monitoring

You must use the KM Admin => Table Monitoring Admin => Monitoring Choices => Monitor by Criteria menu commands to change this variable.

/InformixConfig/InstanceName/TableExclPartList

lists the tables that are excluded from general monitoring

You must use the KM Admin => Table Monitoring Admin => Table Exclude or Include menu command to change this variable.

/InformixConfig/InstanceName/TablePartList

lists the tables that are included for detailed monitoring

You must use the KM Admin => Table Monitoring Admin => Monitoring Choices => Monitor by Table menu command to change this variable.





/InformixConfig/InstanceName/UserCriteria

indicates the top number of entries to process and the column to use as the key for the selection of user instances for detailed monitoring

You must use the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by Criteria menu command to change this variable.

/InformixConfig/InstanceName/UserExclList

lists the users that are excluded from general user monitoring

You must use the KM Admin => User Monitoring Admin => User Exclude or Include menu command to change this variable.

/InformixConfig/InstanceName/UserList

lists the users that are included for detailed user monitoring.

You must use the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by User menu command to change this variable.

/InformixConfig/InstanceName/UserSessionList

lists the sessions that are included for detailed user monitoring

You must use the KM Admin => User Monitoring Admin => Monitoring Choices => Monitor by Session menu command to change this variable.

/InformixConfig/IfmxInstance OBSOLETE.

/InformixConfig/InformixInstance OBSOLETE.






A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

Symbols$PATROL_HOME 55%PATROL_CACHE% 53, 55%PATROL_HOME% 53

Aaborted-transaction spooling

directory 25directory location 149monitoring 157number of files 158path name 150

accessing Informix utilities 20ackTh thread 161Active Tables menu command 129ActiveLocks parameter 174, 190Add Instances menu command 107agent configuration variables 218alarms 37aliases for database server 118allocated dbspace per dbslice 125applications

administrative 27container 27descriptions 27, 30, 33discovery 27functional 27icons 27, 30, 33list of 27

ArchiveLevel0 parameter 171ArchiveLevel1 parameter 171ArchiveLevel2 parameter 172ArchiveMonitor parameter 176, 209Archiving - Logging menu command 112archiving configuration settings 92archiving servers 112automatic logging 113availability monitoring 108availability parameters 116

Bbacking up current installation before migration 59blackout

string 98validating 98variable 98

Blackout Instances menu command 18Blackout menu command 98blob spaces 21, 116, 121BMC Software, contacting 2Bourne shell 72browser requirements 43buffer reads, number of 127, 128buffer space 147buffer writes, number of 127, 128BufferOverflow parameter 174, 190BufferWaits parameter 174, 190Bytes Logical log Space Used 134

CC shell 72capacity parameters 116CDR Geval thread 161CDR_DSLOCKWAIT configuration parameter 147CDR_EVALTHREADS configuration parameter 147CDR_LOGBUFFERS configuration parameter 147CDR_QUEUEMEM configuration parameters 147CDRCparse thread 161CDRD_0 thread 161CDRGfan thread 161CDRN_CM thread 161CDRNrA thread 161CDRNrT thread 161CDRSchedMgr thread 161Change menu command 144, 146CheckpointDuration parameter 172CheckpointFrequency parameter 172CheckpointTime parameter 189CheckpointWaits parameter 175, 190ChunkDown parameter 172, 189chunks

reports 124temp dbspace parameters 121

cleaners 117, 118CleanersDown parameter 183, 199cntlTh thread 161collection commands 101

Index 225


collector and consumer relationships 208collector parameters 37CollectorStatus parameter 191colormap option 73command 113commits executed by user 132components

Informix 14Informix ER 14Informix XPO 14

configurationIDS and XPO instances 108modifying 96PATROL Configuration Manager 93

configuration file 118configuration file location 118configuration parameters, Informix ER 147configuration variables 218Configure Instances menu command 19, 108configuring failover monitoring

steps 87Connect menu command 143connecting ER servers 143connecting server 143connection coserver 118connection coserver name 128connection server 127connection state 149, 150connection state, servers 150connection status 149console system, overview 48consumer parameters 37correlation monitoring

IFMXPO_CORRELATORS application 23parameters 116

coserver connected to PATROL KM 118coserver monitoring

availability 116capacity 116performance 116

CoserverCorrelator parameter 194CpuVpUsage parameter 182customer support 3customizations, migrating 58

Ddata history 37data replication monitoring 148, 149data retrieval

parameters 37summary 35

Database Exclude or Include menu command 19database monitoring menu commands 119database name 127, 128database reports 119

226 BMC Performance Manager Getting Started for In

database server ID 149database server name 118, 149, 151databases

excluding from monitoring 19exporting from tape 114importing from a directory 114importing from tape 114loading 113unloading 113

DataDistribution parameter 183, 199DBACCESS 18dbexport utility 114dbimport utility 114DbsAllocCorrelator parameter 194DBSERVERALIASES 117, 118DBSERVERNAME 117, 118dbslice, dbspaces per 125dbspace address 122Dbspace Exclude or Include menu command 19, 120dbspace flags 122, 123dbspace free space 122, 123dbspace monitoring

excluding dbspaces 19how to 120InfoBox 121, 123parameters 120temp dbspaces 20

Dbspace monitoring Admin menu command 120dbspace name 122, 123dbspace owner 122, 123dbspace size 122, 123dbspace, chunks in 123dbspace, first chunk 123dbspace, first chunk in 122dbspace, logical log 123dbspace, number of 123dbspace, number of chunks in 122DBSpaceAllocated parameter 179, 195DBSpaceMonitor parameter 176, 192, 209, 213dbspaces per dbslice 125dbspaces, number of 122DBSPACETEMP 117, 118DBSPACETEMP onconfig parameter 20DBSpaceUsed parameter 179, 195DbsUsedCorrelator parameter 195ddr_log_io thread 161ddr_snoopy thread 161dead locks 23deadlock timeouts, number of 132Deadlock_Timeout parameter 175, 190Deadlocks parameter 175, 191deadlocks, number of 127, 128, 132debug

query execution time 101debug output file 110debugging

menu commands 110

formix


parameters 110Decision Support Maint menu command 21, 114decision support maintenance

see parallel database queriesdecision support maintenance, See parallel database

queriesdefault values for parameters 167Define menu command 142defining

ER servers 142replicate groups 145servers for ER 142

Delete menu command 143delete server from global catalog 143Deleted Instances menu command 85, 108deletes executed by user 132deletes, number of 127, 128deleting

failover monitoring 91instances 108menu command 143, 144, 146old version 68replicate group 146

directoryaborted-transaction spooling 149row-information spooling 149

Disconnect menu command 142disconnect signal 109discovering instances 107displaying events 21DS_MAX_QUERIES parameter 115DS_MAX_SCANS parameter 115DS_TOTAL_MEMORY parameter 114dslockwait time-out 147

Eenterprise replication

administration of 141attributes 143configuring servers 141monitoring 147starting 142stopping 142threads 161

Enterprise Replication (ER) parameters 203environment variables

LANG 71PATH 71, 72PATROL_BROWSER 72PATROL_CACHE 53PATROL_HOME 53, 55setting for Help browser 71setting for the browser 71

ER component, See Informix ER componentER servers

defining 141, 142disconnecting 142

ERATSSpace parameter 203ERATSSpool parameter 203ERConnectState parameter 24, 203ERError parameter 203ERErrorMonitor parameter 204ERMonitor parameter 176ERQueueMonitor parameter 204ERReplicateMonitor parameter 204ERRISSpace parameter 203ERRISSpool parameter 203Error Log Admin menu commands 19ErrorLogMonitor parameter 176, 192, 209, 213ERSendQueue parameter 203ERServerMonitor parameter 204ERServerState parameter 24, 204ERSpoolMonitor parameter 205ERThreadMonitor parameter 205evaluator threads 147EventSeverity parameter 173, 189eXceed 73Exclude or Include menu command 119, 120excluding

databases from monitoring 19, 119dbspaces from monitoring 19, 120tables from monitoring 126

excluding instances 108Export Database from Directory menu command 114Export Database from Tape menu command 114Extended Parallel Option (XPO) parameters 189

Ffailover monitoring

configuring 87deleting a configuration 91overview 85veiwing report 92

featuresInformix component 18Informix ER component 24

FgWrites parameter 183, 199flags invoked for replicate 154flags invoked for replication 154foreground writes 21FragBuilder parameter 213FragChecker parameter 177FragDeadLks parameter 180, 196, 198FragDeletes parameter 181, 197, 198FragLockReqs parameter 181, 197, 198FragLockWts parameter 181, 197, 198Fragment Monitoring Admin menu command 29, 32, 130fragmented table monitoring 130FragMonitor parameter 177, 192, 209, 213FragPageReads parameter 181, 197, 198

Index 227


FragPageWrites parameter 181, 197, 198FragSDeadLocks parameter 181FragSDeletes parameter 182FragSeqScans parameter 181, 197, 198FragSLockRequests parameter 182FragSLockWaits parameter 182FragSPageReads parameter 182FragSPageWrites parameter 182FragSSeqScans parameter 182free dbspace per dbslice 125frequency

hour, minute, and day 153of replication 154type 153

FullestChunk parameter 173, 189FullestDbs parameter 173, 189FullestMetadata parameter 173

Gglobal catalog, delete server 143global channel 18, 109Global Channel Admin menu command 18, 109graceful shutdown 20Group menu command 146

Hhierarchy, ER server 142history files 37home directory for Informix 118host computer 117, 118host name 117, 118

Iicons, types of 27, 30, 33ID for server 150idle time 150IFMXDS application 28, 117IFMXDS.kml file

Informix component 14Informix ER component 14

IFMXDS_AVAILABILITY applicationdescription 28monitoring servers 115parameters 171

IFMXDS_CAPACITY applicationdescription 28monitoring servers 115parameters 116, 174

IFMXDS_COLLECTORS applicationdescription 28parameters 176

IFMXDS_DBS application


description 28InfoBox 121monitoring dbspaces 120parameters 121, 179

IFMXDS_DBS_CHK applicationdescription 28monitoring dbspaces 120parameters 179

IFMXDS_DBSTEMP applicationdescription 28monitoring dbspaces 120parameters 121, 180

IFMXDS_DBSTEMP_CHK applicationdescription 29monitoring dbspaces 120parameters 180

IFMXDS_FRAG applicationdescription 29

IFMXDS_FRAG application monitoring 130IFMXDS_FRAG_EXT application

description 29monitoring 131parameters 180

IFMXDS_FRAG_SUM applicationdescription 29monitoring 131parameters 181

IFMXDS_PDQ applicationcreating an instance of 114description 29overview 21parameters 182

IFMXDS_PERFORMANCE applicationdescription 29monitoring servers 115parameters 116, 183

IFMXDS_SPACE applicationdescription 29

IFMXDS_TABLES applicationdescription 30

IFMXDS_TBS applicationdescription 30monitoring 127parameters 127, 185

IFMXDS_USER applicationdescription 30

IFMXDS_USERS applicationdescription 30monitoring users 131parameters 131, 188

IFMXER applicationInfoBox 147monitoring replicates 152monitoring servers 148overview of menu commands 24, 25

IFMXER_ QUEUE application instance 26IFMXER_COLLECTORS application

formix


description 34IFMXER_PARTICIPANT application

description 34InfoBox 155instance 25

IFMXER_QUEUE applicationdescription 34

IFMXER_QUEUE application InfoBox 157, 158IFMXER_QUEUELIST application

description 34IFMXER_REPLGRP application

description 34IFMXER_REPLGRP application InfoBox 151IFMXER_REPLICATE application

description 34InfoBox 152monitoring replicates 152

IFMXER_REPLLIST applicationdescription 34

IFMXER_REPLSETS applicationdescription 34

IFMXER_SERVER applicationdescription 35instance 24monitoring ER servers 148

IFMXER_SERVERGRP applicationdescription 35instance 24monitoring ER servers 148

IFMXER_SPOOL applicationdescription 35

IFMXER_SPOOLDIR applicationdescription 35instance 25

IFMXER_SPOOLFILE application 25description 35

IFMXER_SPOOLFILE application InfoBox 158IFMXER_THREAD application 26

description 35IFMXER_THREADLIST application 25, 26

description 35IFMXPO 115IFMXPO application 31IFMXPO application InfoBox 118IFMXPO.kml file

Informix XPO component 16IFMXPO_AVAILABILITY application

description 31monitoring servers 115parameters 116, 189

IFMXPO_CAPACITY applicationdescription 31monitoring servers 115parameters 116, 190

IFMXPO_COLLECTORS applicationdescription 31

IFMXPO_COLLECTORS application parameters 191

IFMXPO_CORRELATORS applicationdescription 31monitoring servers 115parameters 116, 194

IFMXPO_COSERVER applicationdescription 31

IFMXPO_DBS applicationdescription 31InfoBox 121, 123monitoring dbspaces 120parameters 195

IFMXPO_DBS_CHK applicationdescription 32monitoring dbspaces 120parameters 195

IFMXPO_DBSTEMP applicationdescription 32monitoring dbspaces 120parameters 196

IFMXPO_DBSTEMP_CHK applicationdescription 32monitoring dbspaces 120parameters 121, 196

IFMXPO_FRAG applicationdescription 32

IFMXPO_FRAG application monitoring 130IFMXPO_FRAG_EXT application

monitoring 131parameters 196

IFMXPO_FRAG_SUM applicationdescription 32

IFMXPO_FRAG_SUM application monitoring 131IFMXPO_PERFORMANCE application

description 32monitoring servers 115parameters 116, 198, 199

IFMXPO_SPACE applicationdescription 33

IFMXPO_TABLES applicationdescription 33

IFMXPO_TBS applicationdescription 33InfoBox 127, 128parameters 127, 201

IFMXPO_USER applicationdescription 33InfoBox 132, 133monitoring users 131

IFMXPO_USERS applicationdescription 33monitoring users 131parameters 131, 202

Import Database from Directory menu command 114Import Database from Tape menu command 113importing a database 113include

tables for monitoring 126

Index 229


includingdatabases for monitoring 119dbspaces for monitoring 120

InfoBoxesdbspace monitoring 121, 123ER monitoring 147IFMXDS application, InfoBox 117IFMXDS_DBS application 121IFMXDS_TBS application 127IFMXDS_USER application 132IFMXER application 147IFMXER_PARTICIPANT application 155IFMXER_QUEUE application 157, 158IFMXER_REPLGRP application 151IFMXER_REPLICATE application 152IFMXER_SPOOLFILE application 158IFMXPO application 118IFMXPO_DBS application 123IFMXPO_TBS 127IFMXPO_TBS application 128IFMXPO_USER 132IFMXPO_USER application 133participant monitoring 155queue monitoring 157, 158replicate group monitoring 151replicate monitoring 152server monitoring 117spool file monitoring 158table monitoring 127, 128user monitoring 132, 133

INFORMIX 31Informix Admin menu commands 141INFORMIX application 28Informix component

.km files 14features 18Informix products monitored by 14KM Admin menu 18overview 14parameters 171

Informix configuration parameters 147Informix Dynamic Server decision support resources 21Informix Enterprise Replication component, See Informix

ER componentInformix Enterprise Replication monitoring 24Informix ER component

.km files 14definition of ER server 141Informix Admin menu commands 141Informix products monitored by 14

Informix ER configuration parameters 147Informix Extended Parallel Option component, See

Informix XPO componentInformix server, name of 132Informix utilities 20Informix version 117Informix XPO component


Informix products monitored by 16Informix XPO monitoring 23Informix XPO version 118INFORMIX.kml file 17INFORMIXDIR 43, 117, 118INFORMIXSERVER 43, 117, 132INFORMIXSQLHOSTS 43installation

backing up before migration 59clearing cache 68online Help 71preparing for 45upgrading from an earlier version 51

Instance Configuration menu command 107instance, previously excluded 108instances

adding manually 85archiving an 112deleting 85, 108logging an 112reconfiguring deleted 85, 108

InstanceStatus parameter 20, 173InstanceStatusMonitor parameter 209IOQueue parameter 183, 199ISAM calls executed 21

KKill Session menu command 136km files, saving 82KM version 117, 118, 122, 123, 127, 128, 132KMs

determining if migratable 52upgrading from an earlier version 51

Korn shell 72

LLANG environment variable 71LatchWaits parameter 175, 191leaf node 150leaf server 150LicensesUsed parameter 188Load a Database menu command 113Load a Table menu command 113Loading - Unloading menu command 113loading product components

PATROL Console for Unix 79PATROL Console for Windows 2000 78

Local Channel Limit menu command 18, 110lock requests by user 132lock requests, number of 127, 128lock timeouts, number of 127, 128lock waits 23lock waits, number of 127, 128, 132

formix


LockOverflow parameter 175, 191locks held by user 132LockWaits parameter 175, 191logging of server 112logging server automatically 113logging servers 112logical log buffers 21logical log records written by user 132logical log, location of 123logical restore 122LogicalLogBufSize parameter 183, 199logically fragmented table extents 23LogSpace parameter 173, 190long transactions per session 132

Mmanually enter transactions 142Max Bytes Logical log Used 134MAX_PDQPRIORITY parameter 114MAX_QUERIES configuration value 115MAX_SCANS configuration value 115MAX_SCANS parameter 115Maximum Space Used by Sort 134Memory Fragments Alloc Use menu command 134Memory Fragments Allocated menu command 134Memory Fragments Free menu command 134Memory Statistics menu command 134Memory Status Network menu command 135MemoryUsage parameter 183menu commands

debugging 110Group 146monitoring databases 119

merge map file 63, 66metadata 21, 116, 121MetadataUsed parameter 179migrating

backing up current installation before 59customizations 58determining if KM is migratable 52from an earlier version of the KM 51

mode of participant 156mode of participant database 155Modify Instances menu command 108Modify menu command 143, 144, 146Modify Scroll Limit menu command 130modifying instances 93modifying replicate 144Monitor by Criteria menu command 126, 136Monitor by Dbspace menu command 19Monitor by Fragmented Table menu command 130Monitor by Session menu command 136Monitor by Table menu command 126Monitor by User menu command 136monitoring

data replication 148, 149databases 119dbspaces 120enterprise replication 147ER servers 148fragmented tables 130participants 156queues 157replicate groups 151servers 115spools 157threads 159

Monitoring Choices menu command 136monitoring data replication 148, 149monitoring databases 119monitoring dbspaces

how to 120InfoBox 121, 123parameters 120

monitoring servers 115availability 116capacity 116correlation 116InfoBox 117, 118performance 116

monitoring tablesInfoBox 127, 128parameters 127reports 129

monitoring usersInfoBox 132, 133reports 134Show Transaction Log by Transaction ID 135

MSGPATH 117

NNETTYPE 118

OON-Bar Activity Log 20OnBarActivityStatus parameter 20, 174ONCONFIG 43, 114, 117, 118onconfig file for instance 117online Help, installing 48, 71online log 117onload 113Onmode utility 114onstat -p command 111Onstat_dMonitor parameter 177, 192, 209, 213Onstat_FMonitor parameter 177, 192, 209, 213Onstat_IMonitor parameter 177, 193Onstat_lMonitor parameter 209, 213OnstatMonitor parameter 177, 193, 209, 213

Index 231


onunload utility 113

Ppage cleaners, number of 117, 118page flushes 21page reads by session 132page reads, number of 128page writes by session 132page writes, number of 128PageRead parameter 179, 195pages read and written 21PageWrite parameter 179, 195parallel database queries

configuring 114limiting number 115limiting shared memory 115resources allocated 114settings 114

parallel processing 151parallel scans 114param.hist file 37Parameter 171Parameter Debug On Off Toggle menu command 110parameter properties, changing 102parameters

alarms 37changing poll times 101changing thresholds 100collector 37collector and consumer relationships 208collector-consumer dependencies 207consumer 37correlation monitoring 116data retrieval 35, 37deactivating 99debugging 110default values 167defaults 207definitions 167fragmented table 131history data 37history file 37modifying 99, 102monitoring dbspaces 121overview of 35standard 37with status set 100

parent server ID 150participant mode

description 155types of 156

participantsmode of 155monitoring 156overview 25


report 156state of 155

Participants menu command 156partition number 127, 128Partition Profile menu command 129Partition Profile report 129PATH environment variable 72PATROL Agent 35PATROL Agent default account 107PATROL Central Operator - Web Edition, installing 48PATROL Configuration Manager 218

archiving 92modifying instances 93overview 92removing instances 93requirements 92

PATROL Consoleviewing parameters 35

PATROL Console version 117PATROL Event Manager (PEM) 21PATROL KM for Event Management 92, 103PATROL_BROWSER environment variable 72PATROL_CACHE 53, 55, 68PATROL_HOME 53, 55PDQ, See parallel database queries or IFMXDS_PDQPdqMonitor parameter 178performance parameters 116physical log buffers 21PhysicalLogBufSize parameter 184, 199PhysicalLogSize parameter 175, 191PhysicalLogUsed parameter 184, 199poll times 101polling cycles 101preparing for installation 45ProblemSessions parameter 188ProblemUsers parameter 188processing replication 151processing replication data 152product support 3products, uninstalling in Unix environments 74profile counts 21profile statistics

administration of 111changing 111Cumulative menu command 111delta 111Delta menu command 111feature description 21how to set to cumulative 111how to set to delta 111monitoring 21overview 111parameters effected 111setting to zero 111Zero menu command 111

formix


Qquery execution time 101

RRead parameter 179, 195ReadAhead parameter 184, 199ReadCache parameter 184, 200reads and writes 21reads executed by session 132reads executed by user 132reads, number of 127ReadyQueue parameter 184, 200receive queue

dbspace for 150location 149memory 147monitoring 157

remove 91replicate group ID 152replicate group replicates 152replicate group state 151replicate group, name of 151, 152, 154replicate groups

defining 145definition of 145deleting 146guidelines for 145monitoring 151reports 151

Replicate Groups menu command 151Replicate menu command 144, 145replicate name 152replicate set, see replicate groupreplicate tables, synchronize 145replicate, name of 154, 155, 156replicate, state of 153replicated table 155replicates

defining 144definition of 144guidelines for 144, 145modifying 144monitoring 25

replicates in replicate group 152Replicates menu command 153replication conflicts 154replication conflicts, stored procedure 153replication data process 152replication data, resume delivery 143replication, reports on 148, 149replication, scope of 153replTh thread 161Reports

participant 156

replicate groups 151server 150user reports 134

response time 22Response Time User Defined menu command 112ResponseTime parameter 184, 200restart enterprise replication 142Restart Global Channel menu command 18, 109Resume menu command 143, 146rewrites executed by user 132rollbacks executed, number of 132root server ID 150root server, description of 142row-information spooling

directory 25directory location 149monitoring 157number of files 158path name 150

Run Automatic Logging menu command 113

Ssaving changes 82saving km files 82scan threads, limiting 115ScanThreadsAvailable parameter 183ScanThreadUsage parameter 183scope type 153select statement for replication 156select statements for participants 144send queue

dbspace for 150location 149memory 147modifying location 143monitoring 157

sequential processing 151sequential scans 23sequential scans by session 132sequential scans, number of 127, 128server aliases 118server group, definition 141server group, name of 155, 156Server menu command 142, 143server monitoring

availability 116capacity 116correlation 116InfoBoxes 117, 118performance 116

server name 128server type 149servers

connecting 143, 149connection state 150

Index 233


data replication 148, 149disconnecting ER 142hub 150ID 150Informix ER 141leaf 150logging automatically 113monitoring 115monitoring ER 148parent 150parent ID 149receive queue location 149reports 150root ID 149, 150send queue location 149state of 149, 150suspending 143time out 149type 149type of 150

Servers menu command 150SesDeadlocks parameter 188, 202SesDeletes parameter 188, 202SesHeldResources parameter 188, 202SesLocksHeld parameter 188, 202SesLongTxs parameter 188, 202SesMonitor parameter 178, 193, 209, 213SesSeqScans parameter 188, 202Session Information menu command 135session number 132session reports 134Set Fragment Threshold menu command 130setting environment variables for Help browser 71shared memory for parallel database queries, limiting 114shells

Bourne 72C 72Korn 72

Show All menu command 119Show Allocated and Free menu command 125Show Allocated and Used menu command 125Show by Tblspace menu command 135Show by Transaction ID menu command 135Show by User menu command 135Show Chunks menu command 124Show Current Setup menu command 126, 130, 136Show Dbspace and Chunks menu command 124Show Dbspace and Detail menu command 124Show Dbspace’s Tables menu command 124Show Default Excluded (databases) 119Show Detail menu command 125Show Monitored menu command 119Show Table’s Dbspaces Report menu command 129Show Transaction Log by Transaction ID 135shutting down Informix instance 20smart blob spaces 21, 116, 121, 177SMI collector, turning off 108


SMI sysptprof 129SMICollector 20Sorts not in Memory 134spool directory 158spool file name 158spool file owner 159spool file size 158SQL commands 20SQL Information menu command 135SQL scripts 20SQL statements 22SQL syntax errors, detecting 112SQLHOSTS 117, 118sqlhosts file 108sqlhosts file for instance 117sqlhosts file location 118SQLViewerMonitor parameter 178, 193, 213standard collectors 37standard parameters 37Start Continuous Logging menu command 112Start menu command 145State 24state of replicate 153state of server 149, 150stop enterprise replication 142Stop menu command 142Stop Monitoring (users) menu command 136Stop Server menu command 20stopping replication 142stored procedure used 153support, customer 3Suspend menu command 143, 145, 146suspending a server 143synchronize replicate tables 145syncTh thread 161SysCpu parameter 184, 200system clocks in ER servers 144system clocks, synchronizing 144system roles

console systems 48

TTabExtents parameter 184, 200table

loading 113unloading 113

Table Exclude or Include menu command 23, 126table extents 23table monitoring

InfoBox 128parameters 127reports 129

Table Monitoring Admin menu command 126table name 127, 128Table Reports menu command 129

formix


TableOverflow parameter 176, 191tables

including 126synchronize for replication 145

Tables in Sysptprof menu command 129tables, excluding 126tables, fragmented 130TableScans parameter 184, 200tablespace, reason for monitoring 128TblDeadLocks parameter 185, 200TblLockWaits parameter 185TblMonitor parameter 178, 193, 209, 213tbload utility 113TblSeqScans parameter 185, 200TBSDeadLks parameter 185, 201TBSDeletes parameter 185, 201TBSLockReqs parameter 185, 201TBSLockWts parameter 186, 201TBSMonitor parameter 178, 193, 209, 213TBSPageReads parameter 186, 201TBSPageWrites parameter 186TBSSeqScans parameter 186, 201tbunload utility 113technical support 3tempdbs 20TempDBSMonitor parameter 178, 194, 209, 213TempDBSpaceAllocated parameter 180, 196TempDbspaces, monitoring 20TempDBSpaceUsed parameter 180, 196TempPageRead parameter 180, 196TempPageWrite parameter 180, 196TempRead parameter 180, 196TempWrite parameter 180, 196threads

ackTh 161CDR Geval 161CDRCparse 161CDRD_0 161CDRN_CM 161CDRNrA 161CDRNrT 161CDRSchedMgr 161cntlTh 161ddr_log_io 161ddr_snoopy 161ID 159list of for ER 161monitoring 159name of 159replTh 161status of 159virtual process class 159

threads CDRGfan 161Threads menu command 159thresholds, changing for parameters 100time out, server groups 149total sorts by session 133

TOTAL_MEMORY parameter 114Transaction Log Reports menu command 135transaction reports 134triggers for replicate 153

Uuninstalling products 74Unload a Database menu command 113Unload a Table menu command 113upgrading

backing up current installation before 59from an earlier version of the KM 51overview 51

used dbspace per dbslice 125UsedSpace parameter 174, 190user account 72user connection 132user monitoring

InfoBox 132, 133reports 134Show Transaction Log by Transaction ID 135

User Monitoring Admin menu command 136user process ID 132user, name of 132UserCpu parameter 185, 200UserMonitor parameter 179, 194, 209, 213UserOverflow parameter 176, 191users, monitoring 23, 131

Vvariable, PATROL_BROWSER 72Variables

deploying 97variables 218version number of KM 117, 118, 123, 127, 132version of Informix 117viewing

failover monitoring report 92virtual process class 159virtual processors 23VPCorrelator parameter 195VPList parameter 174, 190VPMonitor parameter 179, 194, 209, 213VPTotal parameter 174, 190

Wwpconfig utility 218Write parameter 180, 196WriteCache parameter 185, 201writes executed by session 132writes executed by user 132writes, number of 127, 128

Index 235


formix

Notes

*92510**92510**92510**92510*

92510