Home

DB/Cockpit User Manual, Version 7.3

1. Comparison Condition p 2 21 erie 2 20 DB Cockpit User Manual Comparison Condition Expression Expression Expression Relational Operator DB Cockpit Criteria Syntax a Constant a Using Alarms 2 21 Field IDs 2 22 DB Cockpit User Manual Field IDs You can use the following three types of field IDs Any parameter included in the sysprofile table of the sysmaster database For more information refer to your Administrator s Guide Some of the sysprofile parameters have aliases whose names resemble the column titles in the onstat p output For a full list of aliases refer to the following tables Any Dynamic Server configuration parameter Take care to enter these field IDs in uppercase characters For more information refer to your Administrator s Guide The values of most configuration parameters are retrieved from Dynamic Server reserved pages in order to reflect any changes entered since the last Dynamic Server boot Several parameters which are not available in the reserved pages are retrieved from the onconfig configuration file For more information about reserved pages refer to your Administrator s Guide Unique DB Cockpit field IDs The following table lists all the DB Cockpit field IDs and their aliases where applicable Recommended Alias DB Cockpit DB Cockpit Field ID Field ID Description boot_time Dynamic Server boot time cached_reads Numb
2. __ Super user root is connected Every n2 B pi and Field IDs Reschedule o o SMI Active z mate BE O Cockpit C JEA CO Never SQL text Deliver to __________ select from syssessions E Popup alarm where username root E Mail brian mary H Pipe beeper_program H Log File my_cockpit_al log Cane m If you selected Cockpit define the criteria in the Criteria area as exemplified in Figure 2 2 on page 2 9 The criteria are field ID based conditions evaluated by onprobe When they prove true the alarm is triggered The criteria resemble the WHERE clause of a SQL SELECT statement For more information about syntax refer to DB Cockpit Criteria Syntax on page 2 20 Usually any field ID that appears in the select list in the Type and Field IDs area also appears in the criteria To specify a field ID either type it in or select it with the center mouse button from the field ID scrolled list accessed with the ellipsis button in the Type and Field IDs area Using Alarms 2 13 Defining a New Alarm 2 14 DB Cockpit User Manual Examples loglogs_used gt 0 5 The criterion defines a condition for logical log overflow To receive data about logical log usage in percent define oglogs_used 100 in the Type and Field IDs area cached_reads lt 0 95 OR cached_writes lt 0 85 The criteria h
3. Icons comment Intro 7 feature Intro 8 platform Intro 8 product Intro 8 Industry standards compliance with Intro 14 INFORMIXDIR bin directory Intro 5 ISAM view 3 53 ISO 8859 1 code set Intro 4 I O VP Queues view 3 44 L Launching oncockpit 1 9 1 11 Launching onprobe 1 7 Loading a severity file 4 6 Loading alarm files 2 26 Locale Intro 4 Logical Logs view 3 33 M Machine notes Intro 13 Main window oncockpit 1 11 2 6 3 5 CPU 1 11 Disks 1 11 ISAM calls 1 11 logical logs 1 11 shared memory buffers 1 11 Major features Intro 5 Message file error messages Intro 12 Modifying alarms 2 17 O oncockpit 1 3 1 4 1 9 2 4 to 2 5 2 26 2 29 2 30 launching 1 6 terminating 1 10 On line manuals Intro 12 onprobe 1 3 1 4 1 7 2 4 to 2 5 2 26 2 29 4 3 4 6 launching 1 6 terminating 1 10 Opening an alarm file 2 25 Overflow view 3 54 P Permanent alarm file 2 4 to 2 5 2 7 2 17 2 26 to 2 29 Physical Log view 3 35 Platform icons Intro 8 Printed manuals Intro 12 Product icons Intro 8 Program group Documentation notes Intro 14 Release notes Intro 14 R Refreshing views 3 4 Release notes Intro 13 Release notes program item Intro 14 Replacing active session alarm file 2 26 Requests 2 3 types of 1 4 S Saving alarm files 2 25 Service TCP 1 6 Session alarm file 2 4 to 2 5 2 7 2 17 2 26 to 2 29 Session Profile view 3 27 Sessions view 3 26 Severities 4 3 to 4 6 and
4. The Chunk Spaces view includes the following fields Label Field ID Remarks no chunklist number device name chunklist name Basename 3 10 DB Cockpit User Manual 0 50 100 chunklist used Graphic display gauging values between 0 and 1 total M chunklist total In MB rounded free M chunklist free In MB rounded correct chunklist correct Accepts Y N values disk read chunklist read_ops Number of disk reads disk write chunklist write_ops Number of disk writes The Chunk Space Information View The Chunk Space Information View You can select a chunk from the list in the Chunk Spaces view and drill down with the Chunk Info button to see the following detailed information about the selected chunk m General information m Blobspace information if the chunk belongs to a blobspace m Mirror chunk information if the chunk is mirrored Figure 3 5 DB Cockpit Chunk Space Information pern_shm The Chunk Space Chunk General Information Information View dbspace sblobmir Chunk number 28 Device name menlo s2blobmir_1 Device Type cooked file Offset M 0 Total Space M 0 98 Free Space M 0 97 Used Space 1 00 Disk read 32 Disk write 2 Is blobspace y Is mirrored Status flags chunk is on line Blobspace Information Page size K 10 Total pages 100 Free pages 99 Mirror Chunk Information jj Device name menlo s2blobmir_miri dwn Offset M 0 Disk read
5. Performance Reliability availability and serviceability Manageability Windows NT specific features Application migration Several additional features affect connectivity replication and the optical subsystem For a comprehensive list of new features see the release notes for your database server Documentation Conventions This section describes the conventions that this manual uses These conven tions make it easier to gather information from this and other Informix manuals Introduction 5 Typographical Conventions Convention KEYWORD The following conventions are covered Typographical conventions Icon conventions Command line conventions Terminology conventions Screen illustration conventions Typographical Conventions This manual uses the following standard set of conventions to introduce new terms illustrate screen displays describe command syntax and so forth Meaning All keywords appear in uppercase letters in a serif font italics Within text new terms and emphasized words appear in italics Within syntax diagrams values that you are to specify appear in italics boldface Identifiers names of classes objects constants events functions program variables forms labels and reports environment variables database names filenames table names column names icons menu items command names and other similar terms appear in boldface monospace Information t
6. m Each field ID is followed by three expressions that represent the three severity levels beginning with Fatal then Error and ending with Warning m Field IDS and expressions are separated by commas m Each of the three expressions is optional and can be omitted If you omit an expression from the trio make sure to keep the separating comma so that the correct sequence can be followed m Anything written after the sign and up to the end of the line is a comment and therefore ignored Examples physlogs used 4 gt 0 9 or 4 lt 0 5 4 gt 0 8 lt 0 7 loglogs_used gt LTXEHWM 5 100 gt LTXHWM 100 gt 0 5 LTXEHWM and LTXHWM are examples of field IDs that represent Dynamic Server configuration parameters You can use any Dynamic Server configuration parameter For more information about configuration parameters refer to the your Administrator s Guide The Severity Analyst 4 5 Assigning Colors to Severity Levels Assigning Colors to Severity Levels The colors are user defined X resources As such they can be overridden by your own Xdefaults file located in the home directory or by a file named Cockpit located in usr lib x11 app defaults The resource names are FatalColor ErrorColor and WarningColor The default settings are Cockpit FatalColor red Cockpit ErrorColor orange Cockpit WarningColor yellow Loading a Severity File You can load any existing severity file By default onprobe loads INFORMIX
7. DB Cockpit User Manual Informix Dynamic Server Informix Dynamic Server Developer Edition Informix Dynamic Server Workgroup Edition Version 7 3 February 1998 Part No 000 4378 Published by INFORMIX Press Informix Software Inc 4100 Bohannon Drive Menlo Park CA 94025 1032 Copyright 1981 1998 by Informix Software Inc or its subsidiaries provided that portions may be copyrighted by third parties as set forth in documentation All rights reserved The following are worldwide trademarks of Informix Software Inc or its subsidiaries registered in the United States of America as indicated by and in numerous other countries worldwide Answers OnLine INFORMIX Informix Ilustra C ISAM DataBlade Dynamic Server Gateway NewEra All other names or marks may be registered trademarks or trademarks of their respective owners Documentation Team Twila Booth Geeta Karmarkar Jennifer Leland RESTRICTED RIGHTS SPECIAL LICENSE RIGHTS Software and documentation acquired with US Government funds are provided with rights as follows 1 if for civilian agency use with Restricted Rights as defined in FAR 52 227 19 2 if for Dept of Defense use with rights as restricted by vendor s standard license unless superseded by negotiated vendor license as prescribed in DFAR 227 7202 Any whole or partial reproduction of software or documentation marked with this legend must reproduce the legend ii DB Co
8. The Physical Log View The Physical Log view provides information about m the physical log on disk m buffer activity and utilization m caching Figure 3 17 The Prosi Log View 0 50 100 total K free K O 4000 354 PHYSICAL LOG ON DISK Log size in pages 500 Log pages used 323 Position in log 87 dbspace rootdbs Device name menlo dbspaces BUFFER INFORM ATION Buffer size in pages 16 Buffer pages in use 3 CACHING INFORM ATION No pages written 2290 No disk writes 152 Pages i o 15 07 Buffer utilization 94 16 oy Important The Physical Log view refreshes automatically The DB Cockpit Viewer 3 35 The Physical Log View The Physical Log view includes the following fields Label Field ID Remarks 0 50 100 physlog used Graphic display gauging values between 0 and 1 total K physlog totspace In KB free K physlog free In KB Log size in pages physlog logsize Log pages used physlog lpgused Position in log physlog logpos dbspace physlog dbspace Device name physlog device Full pathname of the chunk where the physical log resides Buffer size in pages physlog bufsize Buffer pages in use physlog bpgused No pages written physlog pgwrite No disk writes physlog diskwrite Pages i o physlog pg_io Number of pages per I O operation Buffer utilization physlog bufutil Pages per I O divided by buffer size 3 36 DB Cockp
9. total K free K E Z 4 General Information Caching Information Number of logs 8 No records written 802 No pages written 268 No disk writes Buffer Information 268 o Pages i o 1 00 Buffer size in pages 16 O Buffer pages in use 0 Buffer utilization 6 25 Logical Logs List log flags unique id size K 0 50 100 free K dbspace rootdbs rootdbs rootdbs rootdbs rootdbs rootdbs Important The Logical Logs view refreshes automatically The DB Cockpit Viewer 3 33 The Logical Logs View The Logical Logs view includes the following fields Label Field ID Remarks 0 50 100 loglogs used Graphic display gauging values between 0 and 1 total K loglogs totalloc In KB free K loglogs totleft In KB Number of logs loglogs logs_no Buffer size in pages loglogs bufsize Buffer pages in use loglogs bpgused No records written loglogs recwrite No pages written loglogs pgwrite No disk writes loglogs diskwrite Pages i o loglogs pg_io Number of pages per I O operation Buffer utilization loglogs bufutil Pages per I O divided by buffer size log loglist number flags loglist flags Text field unique id loglist uniqid size K loglist size In KB 0 50 100 loglist used Graphic display gauging values between 0 and 1 free K loglist free In KB dbspace loglist dbspace 3 34 DB Cockpit User Manual The Physical Log View
10. 0 Disk write 32 Status flags chunk is on line The DB Cockpit Viewer 3 11 The Chunk Space Information View The Chunk Space Information view includes the following fields Label Field ID Remarks dbspace chunkinfo dbspace Chunk number chunkinfo number Device name chunkinfo device Full path Device type chunkinfo dev_type Values accepted raw device cooked file Offset M chunkinfo offset In MB Total space M chunkinfo total In MB Free space M chunkinfo free In MB Used space chunkinfo used In percent Disk read chunkinfo read_ops Number of disk reads Disk write chunkinfo write_ops Number of disk writes Is blobspace chunkinfo blob Accepts Y N values Is mirrored chunkinfo mirror Accepts Y N values Status flags chunkinfo status Text field Page size K chunkinfo blobpg_size In KB Total pages chunkinfo totpgs Free pages chunkinfo freepgs Device name chunkinfo mdevice Full path Offset M chunkinfo moffset In MB Disk read chunkinfo mread_ops Number of disk reads Disk write chunkinfo mwrite_ops Number of disk writes Status flags 3 12 DB Cockpit User Manual chunkinfo mstatus Text field The Chunk Disk Fragmentation View The Chunk Disk Fragmentation View You can select a dbspace from the main Spaces view and drill down with the Disk Frag button to see a graphic presentation of dbspace fragmentation The Chunk Disk Fragmentation view al
11. 3 55 3 57 4 3 4 4 4 4 4 6 4 6 Table of Contents v Introduction About This Manual Types of Users Software Dependencies Assumptions About Your Locale Demonstration Databases New Features Documentation Conventions Typographical Conventions Icon Conventions l Comment Icons Feature Product and Platform Icons Command Line Conventions How to Read a Command Line Diagram Screen Illustration Conventions Additional Documentation On Line Manuals Printed Manuals On Line Help Error Message Files Documentation Notes Release Notes Machine Notes Compliance with Industry Standards Informix Welcomes Your Comments RPROAPMNNAYGT A Bee BR WW 2 DB Cockpit User Manual ead this introduction for an overview of the information provided in this manual and for an understanding of the documentation conventions used About This Manual This manual summarizes the features that make up the DB Cockpit utility a graphical tool designed especially for the following Informix Dynamic Server administrative tasks managing Informix Dynamic Server maintaining its integrity and ensuring a smooth running database for other users Types of Users This manual is for database server administrators This manual assumes that you have the following background m A working knowledge of your computer your operating system and the utilities that your operating system provides m Some experience w
12. Auto refresh mechanism 2 3 C Chunk Disk Fragmentation view 3 13 Chunk Space Information view 3 12 Chunk Spaces view 3 10 Cockpit alarm 2 10 COCKPITSERVICE environment variable 1 7 Colors of severity levels 4 3 4 6 Command line conventions elements of Intro 9 example diagram Intro 10 how to read Intro 10 Comment icons Intro 7 Compliance with industry standards Intro 14 D Data Replication view 3 37 Database Information view 3 17 Databases view 3 15 Default locale Intro 4 Defaults permanent alarm file 2 4 2 25 2 26 to 2 29 session alarm file 2 4 2 25 2 26 to 2 29 severity file 4 6 Defining alarms 2 9 to 2 16 Defining severity expressions 4 4 Deleting alarms 2 17 Demonstration database Intro 4 Disk view 3 57 Documentation on line manuals Intro 12 Documentation conventions command line Intro 8 icon Intro 7 typographical Intro 6 Documentation notes Intro 13 Documentation notes program item Intro 14 Documentation types of documentation notes Intro 13 error message files Intro 12 machine notes Intro 13 printed manuals Intro 12 release notes Intro 13 Drill down method 3 3 E Editing alarms 2 8 Environment variable COCKPITSERVICE 1 7 en_us 8859 1 locale Intro 4 Error message files Intro 12 F Feature icons Intro 8 Features product Intro 5 Field IDs 2 10 2 18 4 4 types of 2 22 to 2 24 finderr utility Intro 13 G Global Language Support GLS Intro 4 2 DB Cockpit User Manual
13. From the list in the Tables view you can access the Table Disk Fragmentation view by clicking the Disk Frag button This view includes two parts m A graphic presentation of fragmentation per chunk m A list of table extents Important When you select a table whose type is synonym view or pseudo in the Tables view the Disk Frag button is grayed because these tables have no extents on the disk Figure 3 12 The Table Disk Fragmentation View DB Cockpit Table Disk Fragmentation pern_shm Fragmentation per Chunk chunk device name size M table fragmentation 26 et1_dbspace_c1 12 a 27 et 1_dbspace_c2 3 kL List of Extents for et1 account dbspace chunk device offset K size K detached index et1_dbspace 26 et1_dbspace_c1 738 5370 et1_dbspace 26 et1_dbspace_c1 6456 5500 3 et1_dbspace 27 et1_dbspace_c2 6 1500 1 Goss 3 24 DB Cockpit User Manual The Table Disk Fragmentation View The Table Disk Fragmentation view includes the following fields Label Field ID Remarks chunk extentslist chunk_no device name extentslist device Chunk basename size M extentslist chunk_size Chunk size in MB table fragmentation no field ID Graphic display that presents the distribution of table extents per chunk dbspace extentslist dbspace chunk extentslist chunk_no device extentslist device Chunk basename offset K extentslist offset Table extent offset
14. Page reads V pagreads Buffer reads V bufreads cache reads V cached_reads Disk writes V dskwrites Page writes y pagwrites Buffer writes V bufwrites cache writes V cached_writes 3 58 DB Cockpit User Manual Index data RA V ixda_RA Data RA V dp_RA Index RA V idx_RA RA pages used V RA_pgsused The Severity Analyst How Does the Severity Mechanism Operate Managing Severities Defining Severity Expressions Assigning Colors to Severity Levels Loading a Severity File 4 3 4 4 4 4 4 6 4 2 DB Cockpit User Manual y using three colors that represent three severity levels DB Cockpit enables you to mark values returned by onprobe when they reach or pass a certain threshold This color coded mechanism known as the severity mechanism allows you to draw attention to suspected or out of range values Rather than having to read data you can take a quick glance and immediately detect any trouble spots How Does the Severity Mechanism Operate Any data that onprobe returns whether intended for views or when replying to alarms passes a severity evaluator The severity evaluator uses expressions that the Dynamic Server administrator defines to compare the returned value to the threshold value set by the expression If the value returned meets the condition defined by the expression it is marked by the color set for that severity level The fol
15. column in the following table are in one of the following categories m Parameters included in the sysprofile table of the sysmaster database m Parameters that appear in the onconfig configuration file m Unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The DB Cockpit Viewer 3 5 The DB Cockpit Main Window The Remarks column shows the formulas that DB Cockpit uses to calculate values Slope is a unique DB Cockpit function that measures changes in the sampled value over a period of time The fields in the lower section of the DB Cockpit main window are depicted as graphic displays In the following table 1 and 2 represent the upper and lower graphs respectively The DB Cockpit main window includes the following fields Label Field ID Remarks User username User that launched onprobe Sessions num_sessions Number of sessions currently connected Server INFORMIXSERVER The INFORMIXSERVER environment variable used to launch onprobe Status Vonline_mode Up period V online_uptime Last ckpt V ckpt_interval Time of last checkpoint Disks 1 no field ID slope totdiskio 2 no field ID slope dskwrites SHM buffers no field ID dirty_buffs_per CPU 1 no field ID slope totcpu 2 no field ID slope systemcpu ISAM calls no field ID slope isamtot Logical Logs loglogs used Graphic display gauging values between 0 and 1 3 6 DB Cockpit U
16. symbols that you must enter exactly as shown Single quotes are literal symbols that you must enter as shown Privileges p 5 17 A reference in a box represents a subdiagram Imagine that the subdiagram is spliced into the main diagram at this point When a page number is not specified the subdiagram appears on the same page 1 of 2 Introduction 9 Command Line Conventions setenv Element Description _ m A shaded option is the default action gt gt Syntax within a pair of arrows indicates a subdiagram The vertical line terminates the command A branch below the main path indicates an optional a OFF path Any term on the main path is required unless ON a branch can circumvent it A loop indicates a path that you can repeat Punctuation 3 along the top of the loop indicates the separator symbol variable for list items A gate ona path indicates that you can only use that path the indicated number of times even if it is part 3 size of a larger loop Here you can specify size no more than three times within this statement segment 2 of 2 How to Read a Command Line Diagram Figure 1 shows a command line diagram that uses some of the elements that are listed in the previous table Figure 1 Example of a Command Line Diagram INFORMIXC aes compiler St pathname To construct a command correctly start at the top left with the co
17. Class Unix pid User cpu System cpu Ready threads Semops Busy waits Spins wait 1 0 VP Information i 1O sec State Total operations Disk read Disk write Disk copy Wakeups 10 ops wakeups I O VP Big Buffer Usage Hil READS Pages 1978 Operations 1943 Pages op 1 02 Holes 21 Hole ops 3 Holes op 7 00 WRITES Pages 927 Operations 810 Pages op 1 14 Important The VP Information view refreshes automatically 3 42 DB Cockpit User Manual The VP Information View The VP Information view includes the following fields Label Field ID Remarks VP id VP gen_vp_id Class VP gen_class Text field Unix pid VP gen_pid User cpu VP gen_user_cpu User CPU time in seconds System cpu VP gen_sys_cpu System CPU time in seconds Ready threads VP gen_ready Semops VP gen_semops Number of semaphore opera tions Busy waits VP gen_busy_waits i Spins wait VP gen_spins_wait Spins per busy waits IO sec VP io_io_sec I O operations per second State VP io_state Text field Total operations VP io_total_ops 1 Disk read VP io_read Number of disk reads Disk write VP io_write Number of disk writes Disk copy VP io_copy Number of disk copies Wakeups VP io_wakeups d IO ops wakeups VP io_ops_wakeup I O operations per wakeup Pages VP iob_r_pages 1 Operations VP iob_r_ops 1 Pages op VP iob_r_page_op Pages per operati
18. Manual Launching onprobe Make sure to assign a unique service number Example cockpit 1555 tcp DB Cockpit During launching onprobe and oncockpit search for the service name according to the following precedence 1 The service command line option 2 The COCKPITSERVICE environment variable The following example illustrates settings for the COCKPITSERVICE environment variable in the C shell and the Bourne or Korn shell C shell setenv COCKPITSERVICE cockpit2 Bourne shell COCKPITSERVICE cockpit2 export COCKPITSERVICE For more information about setting environment variables refer to your UNIX documentation 3 The default which is set to cockpit is assumed if you do not specify the service name either in the command line or as an environment variable Important If you have multiple Dynamic Server instances on the same computer define one service per Dynamic Server instance because each onprobe instance monitors a different Dynamic Server instance Launching onprobe To launch onprobe you enter various command line options at the operating system prompt To launch onprobe 1 Login as user informix or root 2 Make sure your INFORMIXDIR and INFORMIXSERVER environ ment variables are set exactly like those of the monitored Dynamic Server system Important For performance reasons Informix recommends using onipcshm as the connection type in the INFORMIXDIR etc sqlhosts file for the INFORMIXSER
19. New Alarm Figure 2 4 The Alarm Request Dialog Box That Shows a Cockpit Alarm DB Cockpit Alarm Request pern_shm Message Sampling frequency _ Cached writes percentage is too low Every B s Type and Field IDs Reschedule O sm E Active m Ate 5 FF W Cockpit E O Never Criteria Deliver to cached_writes lt 0 85 HE Popup alarm W Mail E Pipe E Log File cockpit_al log CO e Sampling Frequency In the Sampling frequency text box set the onprobe sampling rate for the alarm in seconds minutes hours or days Type the desired sampling frequency in the text box and then select a desired time unit from the option menu box Reschedule Reschedule sets behavior strategy after an alarm is triggered Once triggered an alarm is automatically deactivated by onprobe so as not to bother you with information about the same event If you want onprobe to resume alarm evaluation with exactly the same conditions and sampling frequency specify the time interval after which the alarm should be re activated Using Alarms 2 15 Defining a New Alarm Type the desired time interval in the text box and then select a desired time unit from the option menu box To reschedule the alarm request immediately type 0 To trigger the alarm only once that is without resuming its evaluation click Never Deliver to In the Deliver to text box
20. Next extent size The Table Information View cockpit 08 06 1997 100000 11 100 regular 2 12370 3 1 Page 2 5264 5370 500 3 22 DB Cockpit User Manual Important The Table Information view refreshes automatically In addition to profiling information abouta certain table you can also receive general information about it Select the desired table in the Tables view and click the Table Info button to receive the Table Information view Figure 3 11 The Table Information View The Table Information View The Table Information view includes the following fields Label Field ID Remarks Owner tabinfo owner Date created tabinfo created Number of rows tabinfo rows_no Number of columns tabinfo cols_no Row size tabinfo rowsize In bytes Table type tabinfo tabtype For information on table types see explanations in The Tables View on page 3 17 Number of partitions _ tabinfo part_no In KB Total extents size tabinfo totext In KB Total extent number tabinfo ext_no Number of indexes tabinfo idx_no Lock level tabinfo locklevel Total no of pages used _ tabinfo totpgsused Number of extents Values accepted Row Page No of data pages used tabinfo datapgsused First extent size K tabinfo fextsize Next extent size K tabinfo nextsize In KB In KB The DB Cockpit Viewer 3 23 The Table Disk Fragmentation View The Table Disk Fragmentation View
21. Sessions conn dbinfo sess_no Number of sessions currently connected to the database Owner dbinfo owner Date created dbinfo created Total extents K dbinfo totext In KB NLS dbinfo isnls Accepts Y N values The Tables View Another view that you can open is the Tables view To see a list of tables created in a certain database select the desired database in the main Databases view and click the Tables button Tables in this view are sorted alphabetically The upper part of the view named Display Criteria enables you to define criteria for retrieving tables DB Cockpit recognizes several table types m system system catalog table m temporary m view The DB Cockpit Viewer 3 17 The Tables View m regular m synonym m pseudo pseudo table that Dynamic Server maintains in the sysmaster SMI database only The Temporary button in the Display Criteria area represents temporary tables The Regular button represents regular and pseudo tables By default Regular is selected Figure 3 9 The Tables View DB Cockpit Tables pern_shm r Display Criteria HB regular L view Hi system L temporary L synonym _ pseudo Apply List of tables for databases stores7 table name rows no size K ref count ISAM calls table type cust_calls 16 0 regular 0 customer 28 16 1 regular 0 items 67 16 0 regular 0 log_record 0 regular 0 manufact 0 regular 0 orders 23 16 0 regula
22. alarms 1 6 2 14 2 19 4 4 and views 1 6 4 4 colors of levels 4 3 4 6 defining expressions 4 4 to 4 5 level thresholds 1 5 4 3 4 4 levels of 1 6 4 4 mechanism of 1 6 2 14 4 3 Severity file 4 4 4 5 default 4 4 X loading 4 6 Severity mechanism 1 6 2 14 4 3 Severity function 2 19 Shared memory 1 4 Shared Memory view 3 47 SHM Buffers view 3 49 SHM Segments view 3 51 Slope function 2 14 2 19 SMI alarm 2 10 SMI sysmaster database 1 4 Software dependencies Intro 4 Space Information view 3 9 Spaces view 3 7 SQL Statement view 3 31 stores7 database Intro 4 X Open compliance level Intro 14 T Table Disk Fragmentation view 3 24 Table Information view 3 22 Table Profile view 3 20 Tables view 3 17 TCP service 1 6 Terminating oncockpit 1 10 Terminating onprobe 1 10 Threshold of severity levels 1 5 4 3 4 4 V Views 1 5 2 3 3 3 to 3 58 4 4 drill down method 3 3 refreshing data in 3 4 Virtual Processors View 3 38 VP Classes view 3 38 VP Information view 3 41 W Waits view 3 55 Index 3
23. at a given interval and warn when that condition is met You can use alarms for almost anything for example to warn against dbspaces or logs that fill up as well as deadlocks when they occur Tip The request is the basic communication tool between onprobe and its oncockpit clients The onprobe program executes requests and replies with data collected from the monitored Dynamic Server system The alarm is a special request because it has an auto refresh mechanism that you can customize by setting how often to sample data and under what conditions Although the Viewer is also based on the auto refresh mechanism the end user cannot alter its request parameters An alarm file is a set of alarms that can function at the same time An alarm file can contain no alarms at all one alarm or as many alarms as you want Once created you can change the alarm file by adding new alarms to it deleting alarms from it and modifying a certain alarm without affecting other alarms in the file You can create numerous alarm files An alarm file can be dormant file on the disk or active loaded in onprobe You can switch between active alarm files as the need arises Using Alarms 2 3 Permanent and Session Alarm Files Permanent and Session Alarm Files DB Cockpit supports permanent alarm files and session alarm files m The permanent alarm file is an integral part of onprobe and is therefore loaded at onprobe start up By default onprobe looks fo
24. before you begin working in the Alarm Editor As already mentioned some features are mode dependent If you have entered changes in the current alarm file and request to open a new file you are warned that the current file has not been saved Saving an Alarm File The Alarm Editor provides the following three menu items that allow you to save the changes entered in the current alarm file m To save the current alarm file under its original name choose File Save m To save the current file directly to the default permalrm or sessalrm file in the oncockpit INFORMIXDIR etc directory choose File Save As permalrm or File gt Save As sessalrm The name of this menu item changes to reflect the current file mode If you copied permalrm file from a remote computer for editing do not forget to copy it back Using Alarms 2 25 Replacing the Active Session Alarm File m To save the current alarm file under another name choose File gt Save As The Save As menu item opens a standard file selection dialog box where you can assign a new name for the alarm file and specify its location Important Saving alarms does not update the active alarm file neither permanent nor session loaded in onprobe To override the active session alarm file you must use the Options gt Replace menu item as explained in the next section To override the active permanent alarm file you must restart onprobe Replacing the Active Session Alarm File Y
25. databaselst log Values accepted no logging unbuffered buffered ansi 1 of 2 The DB Cockpit Viewer 3 15 The Database Information View General Information The Database Information View Label Field ID Remarks dbspace databaselst dbspace The dbspace where the data base was created tbl no databaselst tables_no Number of tables Counts only tables that have extents on the disk for example regular sys tem and temporary tables sess con databaselst sess_no Number of sessions currently connected to the database 2 of 2 From the main Databases view you can select a database and drill down with the DB Info button to receive general information about a specific database Figure 3 8 DB Cockpit Database Information pern_shm The Database Information View Add Database Logging status dbspace No of tables Sessions conn Owner Date created Total extents K NLS stores7 no logging rootdbs 39 0 cockpit 07 24 1997 688 N Important The Database Information view refreshes automatically 3 16 DB Cockpit User Manual The Tables View The Database Information view includes the following fields Label Field ID Remarks Database dbinfo database Logging status dbinfo log Values accepted no logging unbuffered buffered ansi dbspace dbinfo dbspace dbspace where the database was created No of tables dbinfo tables_no
26. error 0 Isolation level No Logging No of tables 1 Lock mode Not Wait Est cost 3 Est no rows 28 _ Current SQL Statement select from customer Last Parsed SQL Statement select from customer Close The DB Cockpit Viewer 3 31 The SQL Statement View The SQL Statement view includes the following fields Label Field ID Remarks Sid sqlstmt sid Dynamic Server session ID Database sqlstmt database Database accessed Isolation level sqlstmt iso_level Accepted values Not Wait Wait Wait where represents number of seconds Lock mode sqlstmt lockmode Accepted values Dirty Read Committed Read Cursor Stability Repeatable Read No Logging SQL error sqlstmt sqlerr SQL error number ISAM error sqlstmt isamerr ISAM error number No of tables sqlistmt ntables Number of tables in query Est cost sqlstmt estcost Estimated cost Est no rows Current SQLStmt Last Parsed SQL Stmt 3 32 DB Cockpit User Manual sqlstmt estsize sqistmt currstmt sqlstmt lastparsed Estimated size of query result SQL statement Text field SQL statement Text field The Logical Logs View The Logical Logs View The Logical Logs view lists all logical logs and provides general information about logs as well as buffer activity and utilization Figure 3 16 The Logical Logs View DB Cockpit Logical Logs pern_shm 0 50 100
27. expressions for the field IDs whose severities you want to evaluate m set the preferred color for each severity level m load a desired severity file Defining Severity Expressions Each field ID in a severity file can have three severity expressions associated with it corresponding to the three severity levels In effect there are the following five severity levels Undefined Normal Warning Error Fatal 4 4 DB Cockpit User Manual Defining Severity Expressions Because Normal is the standard for presenting data it is left uncolored so as not to clutter the views with too much color The Undefined level is assigned to any field ID that is not referred to in the severity file it is also left uncolored If an expression evaluates to TRUE the field ID is presented in color If more than one expression evaluates to true the gravest level determines the color of the field ID If none of the expressions evaluates to true the data is considered normal and remains uncolored The syntax of a line in the severity file is as follows field id fatal expression error expression warning expression Note the following information m The syntax of each expression is identical to the syntax of DB Cockpit criteria For detailed information refer to DB Cockpit Criteria Syntax on page 2 20 m The sign in the expression stands for the field ID It is used as a placeholder to ease readability and avoid spelling mistakes
28. file named permalrm from INFORMIXDIR etc The number of alarms in the file is flexible depending on your needs Replies to alarms can be piped logged in a file or mailed Can be edited from oncockpit To load a new alarm file you have to restart onprobe Serve as a watchdog for the Dynamic Server system Requires oncockpit as well as onprobe to function By default oncockpit loads the file named sessalrm from INFORMIXDIR etc The number of alarms in the file is flexible depending on your needs Replies to alarms can be piped logged ina file mailed or projected in real time on a graphic screen Can be edited from oncockpit Loading a new alarm file is immediate and can be executed during run time from oncockpit Serve as on the spot troubleshooters Using Alarms 2 5 The Alarm Editor The Alarm Editor The Alarm Editor is an oncockpit tool that allows you to manage and modify session alarm files as well as permanent alarm files Important Do not mix the current alarm file displayed in the Alarm Editor with the active alarm files permanent and session loaded in onprobe The Alarm Editor allows you to open and display an existing alarm file enter the Alarm Request dialog box where you can create a new alarm or modify an existing alarm within the current alarm file m delete an existing alarm from the file m save anew or modified alarm file m replace the active session alarm file w
29. reside on any host computer in the network as well as on the database server itself m The onprobe program can function independently without oncockpit and serve sites that do not have a resident Dynamic Server administrator The onprobe program watches over the system issuing alarms when needed and recording user defined events 1 4 DB Cockpit User Manual DB Cockpit Tools DB Cockpit Tools DB Cockpit provides you with the following three tools Alarms You can customize DB Cockpit to warn against exceptional system behavior and other anomalies when they occur and directly on the screen You select the parameters that you want to monitor and DB Cockpit triggers an alarm when one of them reaches a certain threshold Performance related events and peak hour anomalies can all be detected and analyzed Viewer The Viewer is an information collector and a data evaluator It presents real time information about system configuration system operation disk and data layout current activities and user and resource management Each subject is displayed in a separate View Each View is a window and like all true windows you can open as many views as you need on your screen Important One major difference exists between alarms and views Information retrieved for alarms is user dependent Views are predefined to show specific information DB Cockpit Overview 1 5 Starting and Terminating DB Cockpit m Severity Analyst
30. specify the output method for a triggered alarm To select an output method click the desired button and where necessary type the required text m Select Popup Alarm to project the alarm and attached message on the screen Popup Alarm is enabled in session mode only m Select Mail and then type one or more electronic mail addresses or aliases m Select Pipe to send alarm output through the UNIX pipe for instance to a program that sends text to a beeper Type the desired UNIX command m Select Log File and then type the name of the file If triggered alarm output is appended to the end of the file If you select Popup Alarm the reply is displayed in graphic format in the Alarm Display window In all other cases the reply is sent in ASCII format and includes a time stamp indicating time of receipt Examples The first example shows the reply received after an SMI alarm was triggered Sun Jul 30 12 54 15 1997 Alarm On SQL Statement select count from syssessions having count gt 2 More than one user is currently connected Ceount AJ 3 The second example shows the reply received after a Cockpit alarm was triggered Sun Jul 30 12 54 15 1997 Alarm On cached_writes With Criteria cached_writed lt 0 85 Cached writes percentage is too low cached_writes 0 2 ERROR 2 16 DB Cockpit User Manual Modifying an Existing Alarm Modifying an Existing Alarm To change the definition of an existing alar
31. the field ID with the center mouse button and dragging it to the desired place The following example represents an alarm that reports logical log usage as a percentage loglogs_used 100 The next example examines cache usage cached_reads cached_writes The last example reports the total size of Dynamic Server resident virtual and message shared memory segments in bytes totshmem 1024 shared_memory_size_in_bytes Active By default every new alarm that you define is active that is onprobe executes it To deactivate an alarm so that it will not be executed with other alarms in the alarm file click the Active button in the Type and Field IDS area This feature may come in handy when you want to tune a specific alarm on line without being harassed by the triggering of other alarms You can also use this feature when you want to temporarily deactivate an alarm based on a heavy SQL statement Important Note the difference between an active alarm file and an active alarm An active alarm file is the file loaded in onprobe an active alarm is an enabled alarm Both an active alarm file and a dormant alarm file can include active and non active alarms Using Alarms 2 11 Defining a New Alarm 2 12 DB Cockpit User Manual SQL Text Criteria In this area you define the condition on which the alarm is based If you select SMI specify the SQL text here as Figure 2 3 on page 2 13 shows You can only use SELECT st
32. variable to the suitable service name 2 Run oncockpit using the following syntax oncockpit host host_name service service_name alarms alarm_file log log_file Xtoolkitoptions host Connect to the onprobe server running on the host host_name The default is the local host service Connect to the onprobe server using the service service_name The default service is named cockpit alarms Load the session alarm file alarm_file INFOR MIXDIR etc is added to any filename that does not begin with a dot or a slash The default file is INFORMIXDIR etc sessalrm DB Cockpit Overview 1 9 Terminating oncockpit log Append log messages to the file log_file If you use a hyphen to designate log_file the log messages will be printed to the standard output Xtoolkitoptions Any standard Xt options Print this usage message V Print the current product version Important Whether you set the service name as an environment variable or specify it in the command line make sure you use the service name that is assigned to the onprobe server to which you want to connect Terminating oncockpit To terminate oncockpit choose File gt Exit from the Main window Terminating onprobe The onprobe program is a UNIX daemon process If you want to terminate onprobe use the Kill command However when you change the Dynamic Server mode to quiescent or off line you do not have to termina
33. view presented in this chapter includes a screen example and a table that details the field IDs included in the view where necessary additional remarks are added The field IDs listed in these tables are used in severity expressions Using the Drill Down Method Most views make use of the drill down method You begin at the top view where general information about a certain subject is displayed and from this view you drill down to specific information presented in subviews This method relies on buttons that enable you to navigate between several related views and access additional information from the main top most view Usually the main view presents the most important or general information while the drill down views hold detailed and specific information The DB Cockpit Viewer 3 3 Refreshing Information in Views 3 4 DB Cockpit User Manual Several views such as Spaces or Databases present a scrollable list of items Initially the first item in the list is selected by default To select another item list click it To explore other views for further information select the item list that interests you and click the relevant drill down button All buttons are located at the bottom of the views Refreshing Information in Views DB Cockpit views provide the following manual and automatic refresh methods Manual refresh You must click the suitable refresh button in the view to initiate a new display of the information D
34. 420 informix pern sysmaster 6184 0 01 19 51 0 444 root pern db1 6200 0 01 02 40 0 460 alex pern db1 6393 0 00 03 02 0 458 gabi pern stores7 6377 0 00 03 29 0 Close Profile SQL Stmt 3 26 DB Cockpit User Manual The Session Profile View The Sessions view includes the following fields Label Field ID Remarks sid seslist sid Dynamic Server session ID user seslist user host seslist host database seslist db Database accessed pid seslist pid UNIX process ID of the client process connect time seslist conntime Connection duration flexible sort field seslist sortfield Variable field can display any field The Session Profile View in the Session Profile marked by You can select a session from the list in the main Sessions view and drill down to the Session Profile view with the Profile button The DB Cockpit Viewer 3 27 The Session Profile View Figure 3 14 DB Cockpit Session Profile pern_shm The Session Profile Profile Information View Sid 456 User light Host pern Database stores7 Pid 6361 tty devittyp7 Connect time 0 00 09 48 Total memory byte 40960 Used memory byte 31400 Locks requested 69 Locks wait 0 Locks held 1 Locks timeout 0 Deadlocks detected 0 CPU time sec No of long tx 0 Reads 3 Writes 0 Rewrites 0 Deletes 0 Commits 0 Rollbacks 0 Buffer reads 7 Buffer writes 0 0 0 6 0 0 0 0 N R No of seq scans No of log r
35. B rounded free M spaceslist free In MB rounded mirror spaceslist mirror Accepts V blank values 2 of 2 You can select a dbspace from the main Spaces view and drill down with the Space Info button to see additional information about a dbspace Figure 3 3 The Space Information View The Space Information View The Space Information view includes the following fields Label dbspace number Field ID Remarks spaceinfo dbspace_no dbspace name spaceinfo name dbspace owner spaceinfo owner Total space M spaceinfo total In MB Free M spaceinfo free In MB Used spaceinfo used In percent Date created spaceinfo created Date and time Is correct spaceinfo correct Accepts Y N values Is temporary spaceinfo temporary Accepts Y N values Mirroring flags spaceinfo mirror Text field blobspace flags spaceinfo blob Text field Recovery flags spaceinfo recovery Text field The DB Cockpit Viewer 3 9 The Chunk Spaces View The Chunk Spaces View You can select a dbspace from the main Spaces view and drill down with the Chunks button to see a list of existing chunks of that dbspace Figure 3 4 The Chunk Spaces View space name DB Cockpit Chunk Spaces pern_shm s2mir no device name 0 50 mirror E 100 total M free M correct disk read disk write 4 5 s2mir_1 s2mir_2dwn 0 0 Chunk Info Refresh
36. B Cockpit offers two refresh buttons a The Refresh button a The Apply button The main purpose of this button is to retrieve information according to new display criteria To refresh a view click Apply without first changing the current criteria The Chunk Fragmentation view is the one exception Although this view belongs to the manual refresh method to refresh the data display for the current selected chunk you have to re select it by clicking Automatic refresh Any view that does not provide one of the above refresh methods refreshes automatically The DB Cockpit Main Window The DB Cockpit Main Window When you launch oncockpit the DB Cockpit main window is displayed monitoring the main Dynamic Server system activities As opposed to other views that this chapter describes the DB Cockpit main window includes a menu bar that allows you to access other views and perform various DB Cockpit functions Most of the field IDs in the DB Cockpit main window are retrieved directly from shared memory to reduce CPU overhead Figure 3 1 The DB Cockpit Main Window DB Cockpit pern_shm File View Edit User informix Server pern_shm Up period 1 23 40 35 Sessions 4 Status On line Since ckpt 0 00 00 16 0 0 acon eer 0 Disks SHM buffers ISAM ain ied Important The DB Cockpit main window refreshes automatically Any field ID checked in the Field ID column and all field IDs in the Remarks
37. DIR etc severity Important If you modified expressions in the severity file you must restart onprobe for changes to take effect To load another severity file that is not the default specify its pathname at onprobe start up with the severity parameter in the command line Note the difference between a relative pathname and an absolute pathname If you specify a relative pathname INFORMIXDIR etc is appended to the pathname Example To load a severity file named severity gen type onprobe severity severity gen 4 6 DB Cockpit User Manual Index A Active alarm 2 11 alarm file 2 3 2 11 Active VPs view 3 40 Alarm Display window 2 30 to 2 31 Alarm Editor 2 6 to 2 7 Edit menu 2 8 File menu 2 25 opening the 2 6 Options menu 2 25 working modes in 2 7 2 17 Alarm file 2 3 activating 2 26 to 2 29 defaults 2 4 2 25 2 27 2 29 opening 2 25 replacing the active session 2 26 saving 2 25 switching modes 2 7 2 17 Alarm Request dialog box 2 9 2 31 Alarms 1 4 1 5 2 3 to 2 31 Cockpit type 2 10 to 2 11 criteria 2 13 to 2 14 2 20 to defining 2 9 deleting 2 17 message attached to 2 9 modifying 2 17 output method 2 16 2 17 popup display 2 16 2 25 2 27 2 28 rescheduling 2 15 sampling frequency 2 15 select list 2 10 2 18 to 2 20 severity expressions in 2 14 2 19 SMI type 2 10 SQL text 2 12 syntax 2 17 to 2 24 types of to 2 11 ANSI compliance level Intro 14 Architecture of DB Cockpit 1 3 to 1 4
38. ECT list of an SQL SELECT statement Cockpit Select List Expression display label Expression field id Constant Expression p 2 19 Function Expression p 2 19 Expression 2 18 DB Cockpit User Manual Constant Expression DB Cockpit Select List Syntax gt Quoted String see SQLS Literal Number see SQLS Severity Constant p 2 20 A Quoted String is marked at both ends by double quotation marks Literal Number can be an integer or a decimal number Function Expression gt slope tield id p gt a severity field id f SLOPE and SEVERITY are unique DB Cockpit functions SLOPE measures changes in the sampled value between two samples The value returned is expressed in units per second SEVERITY returns a severity constant that expresses the current severity value of the sampled field ID This function can return one of the following values UNDEFINED NORMAL WARNING ERROR and FATAL For details about these values refer to Chapter 4 The Severity Analyst Using Alarms 2 19 DB Cockpit Criteria Syntax Severity Constant UNDEFINED NORMAL WARNING ERROR FATAL DB Cockpit Criteria Syntax Cockpit criteria are field ID based conditions that onprobe evaluates When they prove true the alarm is triggered The syntax of Cockpit criteria resembles the syntax of the WHERE clause of an SQL SELECT statement
39. ID btradata btraidx dpra iscommits isdeletes isreads isopen isrewrites isrollbacks isstarts iswrites latchreqs rapgs_used 2 24 DB Cockpit User Manual Alias DB Cockpit Field ID ixda_RA idx_RA dp_RA iscommit isdelete isread isopens iswrite isrollbk isstart iswrite Ichregs RA_pgsused The following table lists the sysprofile field IDs that have alias DB Cockpit Description Data pages read aheads through leaf Leaf read aheads through parent Data pages read aheads iscommit calls isdelete calls isread calls isopen calls iswrite calls isrollback calls isstart calls iswrite calls Number of latch requests Read ahead pages used a Since Dynamic Server boot time or last onstat z command Managing Alarm Files Managing Alarm Files The File and Options menus in the Alarm Editor contain commands that allow you to manage an alarm file Opening an Alarm File To edit an existing alarm file or modify specific alarms within the file you must first open the alarm file in the Alarm Editor Tip If the permanent alarm file resides on a remote computer and you have no NFS access to the file remote copy it before opening the file To open an alarm file choose File Open When you choose this menu item a standard file selection dialog box opens from which you can select the desired alarm file Important If necessary do not forget to change modes session versus permanent
40. M dbs_fraglst chunk_size In MB rounded fragmentation display no field ID Graphic display that presents dbspace distribution of extents per chunk database chk_fraglst database size chk_fraglst persize Extent size percentage from the total chunk size size K chk_fraglst size Extent size in KB Chunk chunkinfo number Device chunkinfo device Full path Offset M chunkinfo offset In MB Total M chunkinfo total Chunk size in MB Free M chunkinfo free In MB 3 14 DB Cockpit User Manual The Databases View The Databases View The six Databases views enable you to investigate the logical structures within the Dynamic Server system The main top most view lists all the databases in the Dynamic Server system sorted by the number of sessions that are currently connected Figure 3 7 The Databases View DB Cockpit Databases pern_shm Databases List database log status dbspace tbl no sess con db1 unbuffered staddmir 30 2 sysmaster unbuffered rootdbs 56 2 sports unbuffered rootdbs 40 1 stores7 no logging rootdbs 39 0 eti no logging et1_dbspace 35 0 ecotoolsdb no logging rootdbs 32 0 syspg4gl no logging rootdbs 32 0 elitest buffered rootdbs 31 0 restock no logging rootdbs 30 0 sarit unbuffered dummy12 30 0 DB Info Tables Refresh The Databases view includes the following fields Label Field ID Remarks database databaselst database log status
41. VER intended for use by onprobe DB Cockpit Overview 1 7 Launching onprobe 3 Optionally set the COCKPITSERVICE environment variable as explained in the previous section 4 Run onprobe using the following syntax onprobe s severity severity _file service service_name alarms alarm_file log log_file V severity Load the severity file severity_file INFOR MIXDIR etc is added to any filename that does not begin with a dot or a slash The default file is INFORMIXDIR etc severity service Accept oncockpit clients using the service service_name The default service is named cockpit alarms Load the permanent alarm file alarm_file INFORMIXDIR etc is added to any filename that does not begin with a dot or a slash The default file is INFORMIXDIR etc permalrm log Append log messages to the file log_file If you use a hyphen to designate log_file the log messages will be printed to the standard output Print this usage message V Print the current product version Tip You can add the sequence that launches onprobe to the suitable rc file after the oninit command that starts the monitored Dynamic Server system 1 8 DB Cockpit User Manual Launching oncockpit Launching oncockpit To launch oncockpit you enter various command line options at the operating system prompt To launch oncockpit 1 Optionally set the COCKPITSERVICE environment
42. You can receive out of range alerts about the values you are browsing should one of them deviate from the range you defined If you set normal ranges for system parameters that interest you DB Cockpit passes their data through an evaluator that uses a color coded mechanism to emphasize anything out of range DB Cockpit supports the following five severity levels a Warning a Error a Fatal a Undefined a Normal which plays a chief role Color coded data is not only easily interpreted it also assists in on the spot analysis and system tuning Severities have one other on line advantage You can color code the data that the Viewer presents or simply put you can see most devia tions on time and act on time You can also base alarm definition on severity levels making sure that important values initiate alarms when they cross the severity threshold defined for them Starting and Terminating DB Cockpit This section details how to launch and terminate DB Cockpit Before You Launch DB Cockpit The onprobe and oncockpit programs communicate with each other through a TCP service Therefore before you can launch either onprobe or oncockpit you should define the service To define a suitable service m Ifyou use NIS add a new TCP service to the NIS server services map m If you do not use NIS add an identical TCP service to your etc services files on both the onprobe and oncockpit computers 1 6 DB Cockpit User
43. aits requests Lock waits requests Latch waits requests Read ahead utilization Phys log capacity at CKPT 100 1 0 oe ae total IO _ total cpu 4 SS g writes a ne sys cpu 1 0 1K AN 0 0 dirty buffs PO 0 locks requested Buffers Segments ISAM Overflow Waits Disk Important The Shared Memory view refreshes automatically All the fields in the Shared Memory view are depicted as graphic displays In the following table 1 and 2 represent the upper and lower graphs respectively The DB Cockpit Viewer 3 47 The Shared Memory View The Shared Memory view includes the following fields Label Field ID Remarks cached reads y cached_reads cached writes V cached_writes Buffer waits requests buff_waits buffwts bufwrites bufreads Lock waits requests lock_waits lockwts lockreqs Latch waits requests latch_waits latchwts latchreqs Read ahead utilization ra_utilization RA_pgsused ixda_RA idx_RA dp_RA Phys log capacity at physlog_cap physlog pgwrite numckpts 3 48 DB Cockpit User Manual CKPT physlog logsize 1 total IO no field ID slope totdiskio 2 writes no field ID slope dskwrites 1 total cpu no field ID slope totcpu 2 system cpu no field ID slope systemcpu dirty buffs no field ID dirty_buf
44. al Please examine these files before you begin using your database server They contain vital information about application and performance issues On UNIX platforms the following on line files appear in the INFORMIXDIR release en_us 0333 directory On Line File Purpose COCKPITDOC_7 3 The documentation notes file describes features that are not covered in this manual or that have been modified since publication SERVERS_7 3 The release notes file describes feature differences from earlier versions of Informix products and how these differences might affect current products This file also contains infor mation about any known problems and their workarounds IDS_7 3 The machine notes file describes any special actions that are required to configure and use Informix products on your computer Machine notes are named for the product described Introduction 13 Compliance with Industry Standards The following items appear in the Informix folder To display this folder choose Start gt Programs Informix from the Task Bar Program Group Item Description Documentation Notes This item includes additions or corrections to manuals along with information about features that may not be covered in the manuals or that have been modified since publication Release Notes This item describes feature differences from earlier versions of Informix products and how these differ ences might affect current products This file also conta
45. am displays the sequences of required and optional elements that are valid in a command A diagram begins at the upper left corner with a command It ends at the upper right corner with a vertical line Between these points you can trace any path that does not stop or back up Each path describes a valid form of the command You must supply a value for words that are in italics You might encounter one or more of the following elements on a command line path Element Description command This required element is usually the product name or other short word that invokes the product or calls the compiler or preprocessor script for a compiled Informix product It might appear alone or precede one or more options You must spell a command exactly as shown and use lowercase letters variable A word in italics represents a value that you must supply such as a database file or program name A table following the diagram explains the value flag A flag is usually an abbreviation for a function menu or option name or for a compiler or preprocessor argument You must enter a flag exactly as shown including the preceding hyphen ext A filename extension such as sql or cob might follow a variable that represents a filename Type this extension exactly as shown immediately after the name of the file The extension might be optional in certain products Punctuation and mathematical notations are literal
46. amic Server system The broken line shows system CPU consumed by all user threads in the Dynamic Server system The distance between the two lines represents user CPU The ISAM calls graph shows the total number of ISAM calls This graph is a good indicator of the requirement for Dynamic Server services The Logical logs graph gauges the percentage of logical logs currently used DB Cockpit Overview 1 11 Using Alarms Permanent and Session Alarm Files The Alarm Editor Opening the Alarm Editor Switching Between Alarm File Modes Editing Specific Alarms Defining a New Alarm Message Type and Field IDs Active SQL Text Criteria Sampling Frequency Reschedule Deliver to Modifying an Existing Alarm Deleting an Existing Alarm DB Cockpit Alarm Syntax DB Cockpit Select List Syntax DB Cockpit Criteria ges Field IDs Managing Alarm Files Opening an Alarm File Saving an Alarm File Replacing the Active Session Alarm File i 2 4 2 6 2 6 2 7 2 9 2 9 2 10 2 11 2 12 2 15 2 15 2 16 2 17 2 17 2 17 2 18 2 20 2 22 2 25 2 25 2 25 2 26 Activating Alarm Files Preparing the Template Alarm Files for Activation Activating the Default Alarm Files Activating Other Alarm Files The Alarm Display Window 2 2 DB Cockpit User Manual 2 26 2 27 2 29 2 29 2 30 n alarm is a request that enables you to check for a specific condition
47. and Platform Icons Feature product and platform icons identify paragraphs that contain feature specific product specific or platform specific information Icon Description E C Identifies information that is specific to the INFORMIX ESQL C product GLS Identifies information that relates to the Informix Global Language Support GLS feature MOTIF Identifies information that is specific to the Motif environment Identifies information that is specific to UNIX platforms Identifies information that is specific to Informix Dynamic w D ek Server Workgroup and Developer Editions WIN NT Identifies information that is specific to the Windows NT environment These icons can apply to a row ina table one or more paragraphs or an entire section If an icon appears next to a section heading the information that applies to the indicated feature option or platform ends at the next heading at the same or higher level A symbol indicates the end of the feature product or platform specific information that appears within a table or a set of paragraphs within a section Command Line Conventions This section defines and illustrates the format of commands that are available in Informix products These commands have their own conventions which might include alternative forms of a command required and optional parts of the command and so forth 8 DB Cockpit User Manual Command Line Conventions Each diagr
48. atements and query only the sysmaster database The current database for SELECT statements is sysmaster Type the SELECT statement in the SQL text area For more infor mation about SELECT statements refer to the Informix Guide to SQL Syntax The following statement triggers an alarm when onprobe detects one or more sessions that super user root runs Session IDs are returned together with other alarm data select sid from syssessions where username root The statement in the second example triggers an alarm when more than one user is connected the onprobe session is taken into account The number of users is returned together with other alarm data select count from syssessions having count gt 2 The alarm in the last example notifies you about dbspaces that are more than 90 percent full select sysdbspaces dbsnum sysdbspaces name sum chksize sum nfree sum chksize used sum chksize total_pages sum nfree free_pages from syschunks sysdbspaces where syschunks dbsnum sysdbspaces dbsnum and sysdbspaces is_blobspace 0 and syschunks dbsnum in select dbsnum from sysdbspaces group by sysdbspaces dbsnum sysdbspaces name having sum nfree sum chksize lt 0 1 order by sysdbspaces dbsnum Defining a New Alarm Figure 2 3 The Alarm Request Dialog Box That Shows an SMI Alarm DB Cockpit Alarm Request pern_shm Message __ SSS r Sampling frequency
49. ckpit User Manual Chapter 1 Table of Contents Introduction About This Manual Types of Users i Software Dependencies Assumptions About Your Locale Demonstration Databases New Features fo ah as Documentation Conventions Typographical Conventions Icon Conventions A Command Line Conventions Screen Illustration Conventions Additional Documentation On Line Manuals Printed Manuals On Line Help Error Message Files Documentation Notes Release Notes Machine Notes Compliance with Industry Standards Informix Welcomes Your Comments DB Cockpit Overview DB Cockpit Architecture DB Cockpit Components DB Cockpit Tools Starting and Terminating DB Cockpit Before You Launch DB pe Launching onprobe Launching oncockpit Terminating oncockpit Terminating onprobe The DB Cockpit Main Window FPONODAT OF FRB WW ra 1 3 1 5 1 6 1 6 1 7 1 10 1 10 1 11 Chapter 2 Chapter 3 iv DB Cockpit User Manual Using Alarms Permanent and Session Alarm Files The Alarm Editor Opening the Alarm Editor Switching Between Alarm File Modes Editing Specific Alarms Defining a New Alarm Modifying an Existing Alarm Deleting an Existing Alarm DB Cockpit Alarm Syntax DB Cockpit Select List Syntax DB Cockpit Criteria ie F Field IDs f Managing Alarm Files Opening an Alarm File Saving an Alarm File Replacing the Active Session Alarm File Activating Alarm Files P
50. ct the desired output method in the Deliver To area and modify its contents if necessary If necessary customize other values in the alarm definition according to the parameters of your Dynamic Server system After you modify the desired alarms choose File gt Save As permalrm to save the current file under INFORMIXDIR etc If you copied the permalrm file from a remote computer remember to copy it back To prepare the sessalrm file Choose File Open to open INFORMIXDIR etc sessalrm in the Alarm Editor Click the desired alarm in the Alarm Editor and choose Edit Modify to open the alarm that you want to activate or custom ize To redirect alarm results to another destination or to more than one destination select the desired output method in the Deliver To area and modify its contents if necessary By default Popup Alarm is selected If necessary customize other values in the alarm definition according to the parameters of your Dynamic Server system After you modify the desired alarms choose File gt Save As sessalrm to save the current file Activating the Default Alarm Files Activating the Default Alarm Files If you modified alarms in the permalrm file you must restart onprobe for changes to take effect Unlike permalrm you can activate the modified sessalrm file directly from the Alarm Editor in oncockpit by choosing Options gt Replace Activating Other Alarm Files You can create as many permanent an
51. d session alarm files as you want and switch between the currently active files and other files The easiest way to activate another alarm file if it is not the default is to specify its name at start up with the alarms command line option The alarms parameter is relevant for both onprobe and oncockpit The following example shows how to activate a permanent alarm file named permalrm gen onprobe alarms permalrm gen The following example shows how to activate a session alarm file named sessalrm tom oncockpit alarms sessalrm tom Tip Alternatively if you do not want to use the alarms parameter you can save the current permalrm or sessalrm file under another name if you want to use the file in the future and rename the alarm file you want to activate to the suitable default name Using Alarms 2 29 The Alarm Display Window The Alarm Display Window Because oncockpit operates in a graphic environment you can request to display results from triggered session alarms on the screen When a session alarm is triggered the Alarm Display window opens and shows alarm output To enable this option click the Popup Alarm button in the Alarm Request dialog box Figure 2 5 shows the Alarm Display window for an SMI alarm Figure 2 5 The Alarm Display Window That Shows SMI Alarm Output DB Cockpit Alarm Display pern_shm Type and Field IDs D _ Message Super us
52. e For instructions on how to specify a nondefault locale additional syntax and other considerations related to GLS locales see the Informix Guide to GLS Functionality Demonstration Databases The DB Access utility which is provided with your Informix database server products includes a demonstration database called stores7 that contains information about a fictitious wholesale sporting goods distributor You can use SQL scripts provided with DB Access to derive a second database called sales_demo This database illustrates a dimensional schema for data warehousing applications Sample command files are also included for creating and populating these databases 4 DB Cockpit User Manual New Features Many examples in Informix manuals are based on the stores7 demonstration database The stores7 database is described in detail and its contents are listed in this manual The scripts that you use to install the demonstration databases reside in the INFORMIXDIR bin directory on UNIX platforms and the INFORMIXDIR bin directory on Windows NT platforms For a complete explanation of how to create and populate the stores7 demonstration database refer to the DB Access User Manual For an explanation of how to create and populate the sales_demo database refer to the Informix Guide to Database Design and Implementation New Features Most of the new features for Version 7 3 of Informix Dynamic Server fall into five major areas
53. e VPs button Figure 3 20 The Active VPs View DB Cockpit Active VPs pern_shm Active VPs List class i user cpu syScpu average cpu usage io sec ready 1 2 3 4 5 6 0 01 0 04 7 aio 740 0 41 2 45 CO 9 75 8 shm 741 0 81 0 32 Co The Active VPs view includes the following fields Label Field ID Remarks vp id VPlist vp_id class VPlist class Text field pid VPlist pid UNIX process ID user cpu VPlist user_cpu User CPU time in seconds sys cpu VPlist sys_cpu System CPU time in seconds average cpu usage 3 40 DB Cockpit User Manual VPlist cpu_usage user cpu sys cpu elapsed time Graphic display gaugin values between 0 and 1 1 of 2 The VP Information View Label Field ID Remarks ready VPlist ready Number of ready threads io sec VPlist io_sec I O operations per second Relevant for I O classes only 2 of 2 a Since Dynamic Server boot time or last onstat z command The VP Information View Select the VP that you want to study and then click the VP Info button in the Active VPs view to access the VP Information view You can see general information about any VP but I O information and I O big buffer usage are displayed only for I O VP classes The DB Cockpit Viewer 3 41 The VP Information View Figure 3 21 DB Cockpit VP Information pern_shm The VP Information View VP General Information VP id
54. ecords Page reads Page writes Total no of sorts No sorts with disk io Max disk used by sort pg Front end directory auto home vitaly Session Flags flag condition primary thread Close Important The Session Profile view refreshes automatically 3 28 DB Cockpit User Manual The Session Profile View The Session Profile view includes the following fields Label Field ID Remarks Sort Sid sessprof sid Dynamic Server session ID User sessprof username Host sessprof hostname Database sessprof database Database accessed Pid sessprof pid UNIX process ID of the client process tty sessprof tty tty of the client process Connect time sessprof connduration Connection duration Total memory byte sessprof totmem Total memory that the session consumed in bytes Used memory byte sessprof usedmem Actual memory that the session used in bytes Locks requested sessprof lockreqs Locks wait sessprof lockwts Locks held sessprof locksheld Locks timeout sessprof lktouts Deadlocks detected sessprof deadlks CPU time sec sessprof cpu_time CPU time that the session consumed in seconds No of long tx sessprof longtxs Number of long transactions Reads sessprof isreads Writes sessprof iswrites Rewrites sessprof isrewrites 1 of 2 The DB Cockpit Viewer 3 29 The Session Prof
55. ents DB Cockpit Tools Starting and Terminating DB Cockpit Before You Launch DB Cockpit Launching onprobe ee Launching oncockpit Terminating oncockpit Terminating onprobe The DB Cockpit Main Window 1 5 1 2 DB Cockpit User Manual his chapter introduces DB Cockpit a graphical tool designed especially for the following Informix Dynamic Server administrative tasks monitoring Informix Dynamic Server maintaining its integrity and ensuring a smooth running database for other users DB Cockpit allows you to monitor many Dynamic Server system parameters that other utilities report It has the following advantages m Itis a graphic environment and not just a graphics displayer m Itshows actual numeric values m Data presentation is intuitive and straightforward DB Cockpit provides you with the right decision making tools for gathering information about Dynamic Server You can use this information to solve problems and improve Dynamic Server performance DB Cockpit Architecture This section describes components and tools which are the two aspects of DB Cockpit architecture DB Cockpit Components DB Cockpit implements a client server architecture It combines two major components the onprobe server and the oncockpit client The onprobe program is the data collector the oncockpit program is responsible for user interaction DB Cockpit Overview 1 3 DB Cockpit Components The onprobe program rece
56. er root is connected __ Alarm Data sid 444 Pq username root lt a SQL text select from syssessions where username root 2 30 DB Cockpit User Manual The Alarm Display Window Figure 2 6 shows the Alarm Display window for a Cockpit alarm Figure 2 6 The Alarm Display Window That Shows Cockpit Alarm Output DB Cockpit Alarm Display pern_shm Type and Field IDs te cached_writes CO Message Cached writes percentage is too low _ Alarm Data cached_writes 10 84 N Criteria cached_writes lt 0 85 a To close the Alarm Display window click the Dismiss button Once the alarm is triggered it is rescheduled according to the value specified in the Alarm Request dialog box irrespective of whether its popup display was dismissed or not Using Alarms 2 31 The DB Cockpit Viewer Using the Drill Down Method Refreshing Information in Views The DB Cockpit Main Window The Spaces View ae The Space Information View The Chunk Spaces View The Chunk Space Information View The Chunk Disk Fragmentation View The Databases View The Database Information View i The Tables View The Table Profile View The Table Information View The Table Disk Fragmentation View The Sessions View The Session Profile View The SQL Statement View The Logical Logs View The Physical Log View The Data Replicatio
57. er of reads from shared memory buffers Number of actual reads from disk Number of reads from shared memory buffers cached_writes Number of writes to shared memory buffers Number of actual writes to disk Number of writes to shared memory buffers dirty_buffs dirty_buffs_per Number of dirty buffers in shared memory Total number of buffers 1 of 2 Recommended Alias DB Cockpit DB Cockpit Field ID Field ID last_ckpt loglogs_used online_mode online_uptime page_size_in_K systemcpu time_since_ckpt ckpt_interval totcpu totdiskio totshmem usercpu Field IDs Description Time of last checkpoint Total used space in logical logs Total allocated space in logical logs Current Dynamic Server operating mode followed by optional data replication type of the database server optional checkpoint status and optional long transaction indi cator Time passed since Dynamic Server boot Page size in kilobytes Total system CPU time in seconds that all user threads use Time passed since last checkpoint Sum of systemcpu and usercpu Total number of actual reads from and writes to disk Total size of Dynamic Server resident vir tual and message shared memory seg ments in KB Total user CPU time in seconds that all user threads use 2 of 2 a Since Dynamic Server boot time or last onstat z command Using Alarms 2 23 Field IDs field IDs sysprofile Field
58. ere examine cache usage triggering an alarm when the percentage of cached reads falls below 0 95 or the percentage of cached writes falls below 0 85 To receive values for cached reads and writes their field IDs should appear in the Type and Field IDs area slope fgwrites gt 0 In this example an alarm is triggered when a foreground write occurs Slope is a special DB Cockpit function that measures changes in the sampled value over a period of time To receive values for foreground writes fgwrites should appear in the Type and Field IDs area slope deadlks The condition in this example triggers an alarm when deadlocks occur To receive the actual number of deadlocks define dead1ks in the Type and Field IDs area online_mode On line The condition in this example instructs onprobe to warn when the Dynamic Server system is not in on line mode Here too onl ine_mode should appear in the Type and Field IDs area to receive the current Dynamic Server mode severity loglogs_used FATAL The condition in this example is based on the severity mechanism The alarm will be triggered when the severity defined for logical log usage reaches fatal level For more information about severity expressions refer to Chapter 4 The Severity Analyst Tip To define an alarm whose sole purpose is data retrieval do not specify criteria An alarm with no criteria is triggered as if its conditions proved true Defining a
59. fs_per locks requested no field ID slope lockreqs The SHM Buffers View The SHM Buffers View From the Shared Memory view you can drill down to see information about SHM buffers with the Buffers button The lower part of the view contains a list of LRU queues Figure 3 24 DB Cockpit SHM Buffers pern_shm The SHM Buffers View Buffers related values Buffer table overflow 0 No foreground writes 0 No LRU writes 0 No chunk writes 0 Buffers related parameters LRUS 8 LRU_MAX_DIRTY 60 LRU_MIN_DIRTY 50 BUFFERS 500 CLEANERS 1 List of LRUS LRU tot size 0 50 100 cleaner 1 62 _ XY 2 63 _ _ YS amp etstsS S 3 59 E V 4 63 o 5 62 __ _Z_ 6 63 _ __ 7 62 __ _ 8 63 _ _ 1 Important The SHM Buffers view refreshes automatically The DB Cockpit Viewer 3 49 The SHM Buffers View In the following table any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The SHM Buffers view includes the following fields Label Field ID Remarks Buffer table overflow V ovbuff No foreground writes V f
60. gwrites No LRU writes V lruwrites No chunk writes LRUS V chunkwrites V LRUS LRU_MAX_DIRTY V LRU_MAX_DIRTY LRU_MIN_DIRTY V LRU_MIN_DIRTY BUFFERS BUFFERS CLEANERS V CLEANERS LRU Iru_list queue LRU queue number tot size lru_list totsize LRU queue size 0 50 100 lru_list dirty_buff Graphic display gauging percentage of dirty buffers ina LRU cleaner Iru_list pgcleaner Accepts blank values 3 50 DB Cockpit User Manual vV means that a page cleaner is working on the queue The SHM Segments View The SHM Segments View Another aspect of SHM are the shared memory segments To access the SHM Segments view click the Segments button Figure 3 25 DB Cockpit SHM Segments pern_shm The SHM Segments View Segments related values SHM VIRTSIZE K 8000 SHM ADD K 8192 SHM TOTAL K 0 SHM segments usage LAT Ea ED 0 1 0 1 0 1 Resident Message Virtual Shared Memory Segments List id size K class 0 50 100 1203 1928 resident LT 1004 8000 virtual L_L_ 9 560 message ET Close Important The SHM Segments view refreshes automatically In the following table any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that ap
61. hat the product displays and information that you enter appear ina monospace typeface KEYSTROKE Keys that you are to press appear in uppercase letters in a sans serif font This symbol indicates the end of feature product platform or compliance specific information within a table or section 6 DB Cockpit User Manual This symbol indicates a menu item For example Choose ToolsOptions means choose the Options item from the Tools menu Icon Conventions Tip When you are instructed to enter characters or to execute a command immediately press RETURN after you type the indicated information on your keyboard When you are instructed to type the text or to press other keys you do not need to press RETURN Icon Conventions Throughout the documentation you will find text that is identified by several different types of icons This section describes these icons Comment Icons Comment icons identify warnings important notes or tips This information is always displayed in italics Icon Description The warning icon identifies vital instructions cautions or critical information The important icon identifies significant information about the feature or operation that is being described The tip icon identifies additional details or shortcuts for the functionality that is being described Ou gt Introduction 7 Command Line Conventions Feature Product
62. iew The Overflow view includes the following fields Label Field ID Remarks Transactions table no field ID slope ovtrans overflow Locks table overflow no field ID slope ovlock User threads table no field ID slope ovuser overflow Buffers table overflow no field ID slope ovbuff The Waits View Waits information is presented when you click the Waits button in the main Shared Memory view Figure 3 28 DB Cockpit Waits pern_shm The Waits View Waits Information Latch waits 2 Latch requested 0 latch waits 0 00 Latch requested per sec 0 00 Lock waits 1 Locks requested 28776 lock waits 0 00 Buffer waits 1 Buffer reads 45400 Buffer writes 4233 buffer waits 0 00 Buffer I O per second 236 17 The DB Cockpit Viewer 3 55 The Waits View Important The Waits view refreshes automatically In the following table any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The Waits view includes the following fields Label Field ID Remarks Latch waits y latchwts Latch requested V latchreqs latch waits latch_waits_per latchwts latchreqs Latch requested per latchre
63. ile View 3 30 DB Cockpit User Manual Label Field ID Remarks Sort Deletes sessprof isdeletes ss Commits sessprof iscommits 3 Rollbacks sessprof isrollbacks t Buffer reads sessprof bufreads s Buffer writes sessprof bufwrites No of seq scans sessprof seqscans Number of sequential scans No of log records sessprof logrecs Page reads sessprof pagreads 7 Page writes sessprof pagwrites Total no of sorts sessprof totsorts J No of sorts with disk sessprof dsksorts J io Max disk used by sort sessprof srtspmax Maximum disk space pg used by sort in pages Front end directory sessprof fe_dir Front end program starting directory flag sessflags flag Flag description 2 of 2 a To receive CPU time values add the WSTATS configuration parameter to the onconfig file with the following syntax WSTATS 1 The SQL Statement View The SQL Statement View From the main Sessions view you can select a session and click the SOL Stmt button to see its current SQL statement The upper part of the view shows general information about the statement The lower part of the view includes two scrollable windows that show the current and last SQL statements When the only statement is the last parsed SQL statement no current statement exists Figure 3 15 DB Cockpit SQL Statement pern_shm The SQL Statement Statement Information View Sid 456 SQL error 0 Database stores7 ISAM
64. in chunk measured in KB size K extentslist extsize Extent size in KB detached index extentslist det_index No of detached indexes The DB Cockpit Viewer 3 25 The Sessions View The Sessions View The Sessions view enables you to monitor user activity in the Dynamic Server system Because the session list can reach unmanageable size Display Criteria are provided in the upper part of the view enabling you to retrieve and display a desired set of sessions in sorted order To set the type of sessions in the list specify one or more criteria in the user host and database text boxes Wildcards are not supported so take care to enter full names only To sort the list of sessions retrieved choose a sort key by clicking the sort by option box Available sort keys are assigned an asterisk in the table on page 3 29 After defining the criteria click the Apply button Important To refresh the session list using the same criteria click the Apply button once more Figure 3 13 The Sessions View DB Cockpit Sessions pern_shm Display Criteria user database host pern sort by number of long tx Apply Sessions List According to Criteria sid user host database pid connect time long tx 456 light pern stores7 6361 0 00 03 59 0 448 svitaly pern db1 6278 0 00 22 33 0 454 roy pern syspg4gl 6360 0 00 04 22 0 452 mcollins pern sports 6359 0 00 04 42 0
65. ins information about any known problems and their workarounds Machine notes do not apply to Windows NT platforms Compliance with Industry Standards The American National Standards Institute ANSI has established a set of industry standards for SQL Informix SQL based products are fully compliant with SQL 92 Entry Level published as ANSI X3 135 1992 which is identical to ISO 9075 1992 In addition many features of Informix database servers comply with the SQL 92 Intermediate and Full Level and X Open SQL CAE common applications environment standards 14 DB Cockpit User Manual Informix Welcomes Your Comments Informix Welcomes Your Comments Please tell us what you like or dislike about our manuals To help us with future versions of our manuals we want to know about corrections or clari fications that you would find useful Include the following information m The name and version of the manual that you are using m Any comments that you have about the manual m Your name address and phone number Write to us at the following address Informix Software Inc SCT Technical Publications Department 4100 Bohannon Drive Menlo Park CA 94025 If you prefer to send email our address is doc informix com Or send a facsimile to the Informix Technical Publications Department at 650 926 6571 We appreciate your feedback Introduction 15 DB Cockpit Overview DB Cockpit Architecture DB Cockpit Compon
66. it User Manual The Data Replication View The Data Replication View The Data Replication view supplies relevant information for Dynamic Server administrators who make use of the data replication feature DB Cockpit Data Replication pern_shm Data Replication Information This server type standard Paired server name DRINTERVAL 30 DRTIMEOUT DRLOSTFOUND DR server state Last ping time DR session thread id DR ping thread id DR secondary apply tid Switchover DRAUTO manual cockpit logs dr log Figure 3 18 The Data Replication View Important The Data Replication view refreshes automatically The Data Replication view includes the following fields Label Field ID This server type drinfo server_type Remarks Accepted values primary secondary standard Paired server name drinfo paired_name DRINTERVAL drinfo interval onconfig parameter DRTIMEOUT drinfo timeout onconfig parameter DRLOSTFOUND drinfo lost onconfig parameter DR server state drinfo server_state 1 of 2 The DB Cockpit Viewer 3 37 The Virtual Processors View Label Last ping time Field ID drinfo pingtime Remarks DR session thread id drinfo sessid DR ping thread id drinfo pingid DR secondary apply drinfo applyid tid Switchover DRAUTO drinfo switch The Virtual Processors View onconfig parameter Accepted values manual auto DB Cockpit VP Clas
67. ith the alarm file currently displayed Opening the Alarm Editor To open the Alarm Editor choose Edit gt Alarms from the main window of oncockpit When you open the Alarm Editor for the first time a list of the alarms defined in the active session alarm file is displayed as Figure 2 1 on page 2 7 shows 2 6 DB Cockpit User Manual Switching Between Alarm File Modes Figure 2 1 The Alarm Editor DB Cockpit Alarm Editor pern_shm File Edit Options Alarm file sessalrm e Session o Permanent on SQL text Field IDs frequency message y cached_reads 10 seconds Cached reads percentage is too low y select sum used sum size used 2 minutes Logical Logs need to be backed up y select dbsname tabname ti_nextns 1 days Tables with more than 8 extents cached_writes 5 minutes Cached writes percentage is too low y ovbuff 10 seconds Buffers table overflow y ovtbls 10 seconds Tablespace overflow y oviock 10 seconds Locks table overflow y ovuser 12 seconds Users table overflow y select from syssessions whereus 6 seconds Super user root is connected The menu bar offers commands for managing specific alarms and the alarm file as a whole The name of the current alarm file is displayed above the alarm list on the left hand side The working mode for the current alarm file session or permanent is displayed on the right hand side The list includes an on off check alarm name sampling frequency and the me
68. ives requests for information about Dynamic Server status and activity The onprobe program handles two types of requests m Regular requests forwarded from oncockpit clients m Conditional requests called alarms which both onprobe and oncockpit can issue The onprobe program samples the required data according to the requests received and at pre defined rates It always replies to regular requests by returning the corresponding data If onprobe receives an alarm it only returns data when the condition of the alarm proves true The onprobe program evaluates the severity of all the data it returns according to predefined severity expressions The onprobe program extracts the requested data from two sources the System Monitoring Interface SMI database and directly from Dynamic Server shared memory SHM The oncockpit program is a two way highway You use it to send requests for information about current database activity and configuration You also use it to receive the data returned by your requests and display any alarms directed to it by onprobe A dual process architecture has two major advantages m You can monitor any database server directly from your workstation without overtaxing database server resources and at the same time benefit from a graphics environment Many database servers do not have an X display Only onprobe resides on the same database server as the monitored Dynamic Server system The oncockpit program can
69. lowing three examples show how the severity mechanism can benefit both numeric and graphic data survey m Dbspace capacity can be yellow Warning when it passes the 80 percent mark and orange Error when it passes the 90 percent mark m Logical logs can be red Fatal when they pass the defined level for LTXHWM long transaction exclusive high water mark percentage m User root sessions superuser can be yellow whenever they appear to warn against this event The Severity Analyst 4 3 Managing Severities Managing Severities You can set severity thresholds for any field ID presented in DB Cockpit views and alarms To set a severity threshold you need to define the conditions for what should be presented as Fatal Error or Warning These conditions are referred to as severity expressions You define expressions in an ASCII severity file DB Cockpit offers a default severity file named severity located in the INFORMIXDIR etc directory of onprobe You can also create your own file or files and load a desired file at onprobe start up with the severity command line option Tip The default severity file lists all field IDS Suitable expressions are defined for Q some of the field IDs To enable severity evaluation for other field IDs define expres sions according to your needs DB Cockpit also offers a copy of the severity file named severity std for reference The following sections describe how to m define the severity
70. lows you to evaluate the amount of free space occupied space and fragmented areas at a glance Note that the Disk Frag button is disabled when blobspaces are selected The upper part of the view shows a list of chunks and a graphic presentation of their fragmentation Initially information about the first chunk is shown because it is selected by default To see detailed information about a specific chunk select it from the list The detailed information about extents in the current chunk as well as general information about the chunk are displayed in the two lower areas of the view Figure 3 6 The Chunk Disk Fragmentation View DB Cockpit Chunk Disk Fragmentation pern_shm List of chunks for dbspace rootdbs chunk device name size M fragmentation display root_chunk 2 rootdbs_2 Extents List Chunk General Information database size size K Chunk 1 LOGICAL LOG 7 2 50 500 Py Device menlo dbspaces root_chunk LOGICAL LOG 8 2 50 500 Offset M 0 Database TBLSpace 0 04 8 Total M 19 53 sysmaster 4 00 800 Free M 8 97 Tables TBLSpace 0 50 100 sysmaster 1 84 368 v Close The DB Cockpit Viewer 3 13 The Chunk Disk Fragmentation View Important To refresh the view for the current chunk click the chunk again The Chunk Fragmentation view includes the following fields Label Field ID Remarks chunk dbs_fraglst number device name dbs_fraglst device Basename size
71. m click the desired alarm in the Alarm Editor and choose Edit gt Modify Enter the desired changes in the Alarm Request dialog box For information about the various alarm components refer to Defining a New Alarm on page 2 9 Important If you change a session alarm file to a permanent alarm file take care to specify an output method other than Alarm Popup for each alarm in the file Popup display is enabled in session mode only and is automatically disabled when you switch modes from session to permanent Any alarm whose only output is popup display has as a consequence no output method because there is no way of transmitting the information Switching back to session mode enables the popup option For more information refer to Switching Between Alarm File Modes on page 2 7 Deleting an Existing Alarm To delete an alarm click the desired alarm in the Alarm Editor and choose Edit Delete DB Cockpit Alarm Syntax This chapter describes the syntax used to define Cockpit type alarms m DB Cockpit select list syntax m DB Cockpit criteria syntax m Field IDs Using Alarms 2 17 DB Cockpit Select List Syntax DB Cockpit Select List Syntax The select list defines the data to be returned when an alarm is triggered The select list contains one or more field ID based expressions If the alarm is triggered the value of each expression listed is returned The syntax of a Cockpit select list resembles the syntax of a SEL
72. mmand Then follow the diagram to the right including the elements that you want The elements in the diagram are case sensitive 10 DB Cockpit User Manual Screen Illustration Conventions Figure 1 diagrams the following steps Type the word setenv Type the word INFORMIXC Supply either a compiler name or pathname After you choose compiler or pathname you come to the terminator Your command is complete Press RETURN to execute the command Screen Illustration Conventions The illustrations in this manual represent a generic rendition of various windowing environments The details of dialog boxes controls and windows were deleted or redesigned to provide this generic look Therefore the illustrations in this manual depict the windowing environment a little differently than the way it appears on your screen Additional Documentation For additional information you might want to refer to the following types of documentation On line manuals Printed manuals On line help Error message files Documentation notes release notes and machine notes Introduction 11 On Line Manuals On Line Manuals An Answers OnLine CD that contains Informix manuals in electronic format is provided with your Informix products You can install the documentation or access it directly from the CD For information about how to install read and print on line manuals see the installation insert that accompanies Answers OnLine P
73. n View The Virtual Processors View The Active VPs View The VP Information View The I O VP Queues View 3 3 3 4 3 5 3 7 3 10 3 11 3 13 3 15 3 16 3 17 3 20 3 22 3 24 3 26 3 27 3 31 3 33 3 35 3 37 3 38 3 40 3 41 3 44 The Shared Memory View The SHM Buffers View The SHM Segments View The ISAM View The Overflow View The Waits View The Disk View 3 2 DB Cockpit User Manual 3 46 3 49 3 51 3 53 3 54 3 55 3 57 he DB Cockpit utility provides a variety of views or windows that open into the Dynamic Server system to allow you to focus on its values according to the subject that you want to monitor Some of the views handle static information while others are dynamic in nature The Spaces view which shows the physical structure of data or the Databases view which shows the logical structure of data are static views The Sessions view which monitors user access to database tables or the Shared Memory view are dynamic views and the data they display changes more frequently Depending on the subject views can present the data in text and graphic format Some views present the data in both formats allowing you to decide whether a quick glance and a general idea of matters are enough or whether you need accurate values DB Cockpit supports views about dbspaces databases sessions logical and physical logs data replication virtual processors and shared memory Tip Each
74. on Holes VP iob_r_holes 1 Hole ops VP iob_r_h_ops Hole operations 1 of 2 The DB Cockpit Viewer 3 43 The I O VP Queues View Label Field ID Remarks Holes op VP iob_r_hole_op Holes per operation pages VP iob_w_pages operations VP iob_w_ops l pages op VP iob_w_page_op Pages per operation 2 of 2 a Since Dynamic Server boot time or last onstat z command The I O VP Queues View Additional statistics about I O VP activity can be monitored as well Click the IO Queues button in the main VP Classes view to access the I O VP Queues view Figure 3 22 The I O VP Queues View DB Cockpit 1 0 VP Queues pern_shm 1 0 VP Queues List class iovpid len maxlen len maxlen totalops reads writes disk copy adt 0 0 0 0 0 0 opt 0 0 0 0 0 0 msc 0 1 54 0 0 0 aio 0 0 0 0 0 0 pio 0 1 17 0 17 0 lio 0 1 9 0 9 0 Close Important The I O VP Queues view refreshes automatically 3 44 DB Cockpit User Manual The I O VP Queues View The I O VP Queues view includes the following fields Label Field ID Remarks class iovpq class Text field iovp id iovpq iovp_id Displays only if there is more than one instance in the I O VP class len iovpq len Actual length of queue maxlen iovpq maxlen Maximum length of queue len maxlen iovpq usage Graphic display gauging val ues between 0 and 1 total ops iovpq total_ops Total number of opera
75. orking with relational databases or exposure to database concepts m Some experience with database server administration operating system administration or network administration m Working knowledge of Structured Query Language SQL If you have limited experience with relational databases SQL or your operating system refer to Getting Started with Informix Dynamic Server for a list of supplementary titles Introduction 3 Software Deoendencies Software Dependencies This manual assumes that your database server is one of the following products m Informix Dynamic Server Version 7 3 m Informix Dynamic Server Developer Edition Version 7 3 m Informix Dynamic Server Workgroup Edition Version 7 3 Assumptions About Your Locale Informix products can support many languages cultures and code sets All culture specific information is brought together in a single environment called a GLS Global Language Support locale This manual assumes that you are using the default locale en_us 8859 1 This locale supports U S English format conventions for dates times and currency In addition this locale supports the ISO 8859 1 code set which includes the ASCII code set plus many 8 bit characters such as and If you plan to use nondefault characters in your data or your SQL identifiers or if you want to conform to the nondefault collation rules of character data you need to specify the appropriate nondefault local
76. ormulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The ISAM view includes the following fields Label Field ID Remarks istotal vV isamtot isopens V isopen isstarts isstart isreads vV isread 1 of 2 The DB Cockpit Viewer 3 53 The Overflow View Label Field ID Remarks iswrites V iswrite isrewrites v isrewrite isdeletes V isdelete iscommits V iscommit isrollbacks y isrollbk 2 of 2 The Overflow View Overflow information is presented when you click the Overflow button in the main Shared Memory view Figure 3 27 DB Cockpit Overflow pern_shm The Overflow View Overflow Information Transactions table overflow Locks table overflow User threads table overflow Buffers table overflow Close ooooe Important The Overflow view refreshes automatically In the following table any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 3 54 DB Cockpit User Manual The Waits V
77. ou can replace the active session alarm file immediately during run time To do so open the session alarm file that you want to activate in the Alarm Editor and choose Options Replace Replacing the active permanent alarm file requires another approach Although you can edit permanent alarms from the Alarm Editor you cannot replace the active permanent alarm file with your updates For more information refer to Activating Alarm Files on page 2 26 Activating Alarm Files By default onprobe loads that is activates the permanent alarm file named permalrm in INFORMIXDIR etc By default oncockpit loads the session alarm file named sessalrm in INFORMIXDIR etc The onprobe and oncockpit programs can also load any other alarm file provided that it is specified at start up with the alarms parameter in the command line Important If you use the default alarm files permalrm and sessalrm and onprobe and oncockpit run on different computers their corresponding INFORMIXDIR directories can reside in different file systems 2 26 DB Cockpit User Manual Preparing the Template Alarm Files for Activation DB Cockpit comes ready made with the following four template alarm files m Two identical permanent alarm files named permalrm and permalrm std reside in the onprobe INFORMIXDIR etc directory and contain a suggested set of permanent alarms m Two identical session alarm files named sessalrm and sessalrm std
78. pear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The DB Cockpit Viewer 3 51 The SHM Segments View The SHM Segments view includes the following fields Label Field ID Remarks SHMVIRTSIZE V SHMVIRTSIZE SHMADD V SHMADD SHMTOTAL V SHMTOTAL Resident seg_val resident Memory usage in resident segments Graphic display gauging values between 0 and 1 Message seg_val message Memory usage in message segments Graphic display gauging values between 0 and 1 Virtual seg_val virtual Memory usage in virtual segments Graphic display gauging values between 0 and 1 id seg_list id UNIX shared memory segment ID size seg_list size SHM segment size in KB class seg_list class Accepted values resident message virtual 0 50 100 seg_list used Graphic display gauging 3 52 DB Cockpit User Manual values between 0 and 1 The ISAM View The ISAM View To see information about ISAM operations click the ISAM button in the main Shared Memory view Figure 3 26 DB Cockpit ISAM pern_shm The ISAM View ISAM Operations istotal isopens isstarts isreads iswrites isrewrites isdeletes iscommits isrollbacks 77138 5495 13305 26928 1575 4725 Important The ISAM view refreshes automatically In the following table any field ID checked in the Field ID column and all field IDs used in f
79. qs_per_sec slope latchreqs sec Lock waits y lockwts Locks requested V lockreqs lock waits lock_waits_per lockwts lockreqs Buffer waits V buffwts Buffer reads V bufreads Buffer writes vV bufwrites buffer waits buff_waits_per buffwts bufwrites bufreads Buffer I O per second 3 56 DB Cockpit User Manual buff_IO_per_sec slope bufreads slope bufwrites The Disk View The Disk View Disk information is presented when you click the Disk button in the main Shared Memory view Figure 3 29 DB Cockpit Disk pern_shm The Disk View Disk Operations 1 0 OPERATIONS Disk reads 1531 Page reads 1531 Buffer reads 34698 cache reads 95 59 Disk writes 1226 Page writes 2157 Buffer writes 3447 cache writes 64 43 READ AHEAD OPERATIONS Index data RA Data RA Index RA RA pages used Close Important The Disk view refreshes automatically In the following table any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 The DB Cockpit Viewer 3 57 The Disk View The Disk view includes the following fields Label Field ID Remarks Disk reads V dskreads
80. r a permanent alarm file named permalrm under INFORMIXDIR etc You can only have one active permanent alarm file at a given time but you can have more than one dormant file You are free to change the number of alarms ina file as well as their syntax and parameters To change the permanent alarm file you need to work from the oncockpit Alarm Editor If you want to activate another alarm file or re activate the active file after modifying it you must restart onprobe for changes to take effect You can direct replies resulting from permanent alarms to a UNIX pipe append them to an alarm log file or send them to a desired address by way of electronic mail m The session alarm file originates in oncockpit By default oncockpit looks for a session alarm file named sessalrm under INFORMIXDIR etc You can customize a session alarm file and immediately activate it without restarting either onprobe or oncockpit by choosing a simple menu item In addition you can also create as many dormant session alarm files as your system dictates and activate the desired file as the need arises As with permanent alarms replies from session alarms can be sent to a UNIX pipe appended to an alarm log file or sent by way of electronic mail to a certain address In addition because of their graphic origin replies from session alarms can also be projected on the screen in real time How do different characteristics affect alarm functionality Permanen
81. r 0 state 52 16 0 regular 0 stock 74 16 0 regular 0 sysblobs 5 16 0 system 0 syschecks 6 16 0 system 0 Close Profile Tbl Info Disk Frag 3 18 DB Cockpit User Manual The Tables View The Tables view includes the following fields Label Field ID Remarks Display Criteria tablelist tabtype See explanations at the beginning of this section table name tableslist tabname rows no tableslist rowsno size tableslist totext Total size of table extents in KB user cnt tableslist usercnt Number of users currently accessing the table table type tableslist tabtype See explanations at the beginning of this section ISAM calls tableslist isamtot Note that for some table types part of the table parameters may not be displayed For example tables of type pseudo view synonym and tables named VERSION have no extends on the disk therefore all the disk related parameters size Total extents size First extent size and so forth are empty The DB Cockpit Viewer 3 19 The Table Profile View The Table Profile View You can select a table name from the list in the Tables view and drill down with the Profile button to see profiling information about the selected table Important Profiling information is not available for tables of type synonym view S and pseudo because they have no extents on the disk When you select a table of one of these types in the Tables view the Profile button is gra
82. reparing the Template Alarm Files for Activation Activating the Default Alarm Files Activating Other Alarm Files The Alarm Display Window The DB Cockpit Viewer Using the Drill Down Method Refreshing Information in Views The DB Cockpit Main Window The Spaces View The Space Information Views The Chunk Spaces View The Chunk Space Information View The Chunk Disk Fragmentation View The Databases View The Database Information View The Tables View The Table Profile View The Table Information View The Table Disk Fragmentation View The Sessions View The Session Profile View The SQL Statement View The Logical Logs View 2 4 2 6 2 6 2 8 2 9 2 17 2 17 2 17 2 18 2 20 2 22 2 25 2 25 2 25 2 26 2 26 2 27 2 29 2 29 2 30 3 3 3 5 3 7 3 8 3 10 3 11 3 13 3 15 3 16 3 17 3 20 3 22 3 24 3 26 3 27 3 31 3 33 Chapter 4 The Physical Log View The Data Replication View The Virtual Processors View The Active VPs View The VP Information View The I O VP Queues View The Shared Memory View The SHM Buffers View The SHM Segments View The ISAM View The Overflow View The Waits View The Disk View The Severity Analyst How Does the Severity Mechanism Operate Managing Severities oy Defining Severity Expressions Assigning Colors to Severity Levels Loading a Severity File Index 3 35 3 37 3 38 3 40 3 41 3 44 3 46 3 49 3 51 3 53 3 54
83. reside in the oncockpit INFORMIXDIR etc directory and contain a suggested set of session alarms Tip DB Cockpit offers the permalrm std and sessalrm std files as copies for reference Preparing the Template Alarm Files for Activation The permalrm file and the sessalrm file contain an identical set of alarms The Mail Pipe and Log File options in the Deliver To area are disabled for all alarms because they are site dependent Although the two files contain an identical set of alarms the following two major differences exist between the files m The alarms in permalrm are inactive while those in sessalrm are active m The Popup Alarm output method is enabled for all alarms in the sessalrm file As already mentioned Popup Alarm is irrelevant for permanent alarms You can easily edit both these alarm files as well as any other alarm file from the oncockpit Alarm Editor To prepare the permalrm file 1 Choose File Open to open INFORMIXDIR etc permalrm in the Alarm Editor If the permalrm file resides on a remote computer and you have no NFS access to the file remote copy it before you open the file 2 Click the desired alarm in the Alarm Editor and choose Edit gt Modify to open the alarm that you want to activate in the Alarm Request dialog box 3 Click the Active button in the Type and Field IDs area Using Alarms 2 27 Preparing the Template Alarm Files for Activation 1 2 28 DB Cockpit User Manual Sele
84. rinted Manuals To order printed manuals call 1 800 331 1763 or send email to moreinfo informix com Please provide the following information when you place your order m The documentation that you need m The quantity that you need m Your name address and telephone number On Line Help Informix provides Help screens with each graphical user interface GUI that display information about the those interfaces and the functions that they perform You can display these Help screens using the Help facilities provided with each GUI Error Message Files Informix software products provide ASCII files that contain all of the Informix error messages and their corrective actions For a detailed description of these error messages refer to Informix Error Messages in Answers OnLine 12 DB Cockpit User Manual UNIX WIN NT UNIX Documentation Notes Release Notes Machine Notes To read the error messages under UNIX you can use the following commands Command Description finderr Displays error messages on line rofferr Formats error messages for printing To read error messages and corrective actions under Windows NT use the Informix Find Error utility To display this utility choose Start gt Programs Informix from the Task Bar Documentation Notes Release Notes Machine Notes In addition to printed documentation the following sections describe the on line files that supplement the information in this manu
85. ser Manual The Spaces View and use of Dynamic Server spaces The Spaces View The Spaces views deal with data storage focusing on the physical structure The main Spaces view provides general information about dbspaces Figure 3 2 The Spaces View DB Cockpit Spaces pern_shm dbspaces list sOdown n E s6_1chunks y E s18sym2mb_temporar y E j s2blobmir y V dummy10 y dummy11 y 4 dummy12 y Es space name correct blob 0 50 100 total M free M mirror rootdbs y Zl 10 staddmir y I 0 V anna A o NN A v Space io The main Spaces view includes the following fields Label Field ID Remarks space name spaceslist name correct spaceslist correct Accepts Y N values blob spaceslist blob Accepts V blank values 1 of 2 The DB Cockpit Viewer 3 7 The Space Information View The Space Information View DB Cockpit Space Information pern_shm Space General Information dbspace number 7 dbspace name s2blobmir dbspace owner informix Total space M 1 95 Free M 1 93 Used 1 00 Date created 1997 07 24 16 07 00 Is correct y Is temporary n Mirroring flags dbspace uses mirroring blobspace flags dbspace is a BlobSpace Recovery flags 3 8 DB Cockpit User Manual Label Field ID Remarks 0 50 100 spaceslist used Graphic display gauging values between 0 and 1 total M spaceslist total In M
86. ses pern_shm VP Classes List 2 of 2 The VP Classes view displays a list of all Dynamic Server VP classes Figure 3 19 The VP Classes View VPs user cpu sys cpu average cpu usage ready io sec 1 2 0 1 1 1 1 0 0 1 0 34 54 0 56 0 00 0 52 0 02 0 04 0 01 0 00 0 00 0 01 0 00 4 75 3 07 0 00 0 20 0 05 0 53 0 03 0 00 0 00 0 01 0 00 kz z_ L 0 oooooo ceooe 12 99 0 03 0 76 0 00 0 04 0 00 3 38 DB Cockpit User Manual Active VPs 10 Queues The Virtual Processors View Important The VP Classes view refreshes automatically The VP Classes view includes the following fields Label Field ID Remarks class VPclass class Text field VPs VPclass vps Number of instances in this class user cpu VPclass user_cpu User CPU time in seconds sys cpu VPclass sys_cpu System CPU time in seconds average cpu usage VPclass cpu_usage user cpu sys cpu elapsed time Graphic display gaugin values between 0 and 1 ready VPclass ready Number of ready threads io sec VPclass io_sec I O operations per second Relevant for I O classes only a Since Dynamic Server boot time or last onstat z command The DB Cockpit Viewer 3 39 The Active VPs View The Active VPs View From the list of VP classes you can access the list of active VPs with the Activ
87. ssage issued if the alarm is triggered Switching Between Alarm File Modes The Alarm Editor supports two working modes one for permanent alarm files and the other for session alarm files Modes are displayed as radio buttons Session and Permanent above the message list on the right side Using Alarms 2 7 Editing Specific Alarms 2 8 DB Cockpit User Manual Most options are supported in both modes There are however two practical differences between the modes In permanent mode the Options gt Replace menu item is grayed because you cannot activate a permanent alarm file from oncockpit and output to a graphic popup window is disabled When you enter the Alarm Editor for the first time Session mode is turned on On subsequent entries to the Alarm Editor the last mode activated is restored To change modes click the desired radio button Remember to check whether the desired mode is turned on before you save an alarm file Editing Specific Alarms An alarm includes the following components that you can edit Message issued with alarm data if the alarm is triggered Alarm type SMI or Cockpit Active check box used to turn a certain alarm on or off without affecting the rest of the alarm file Conditions by which to filter Dynamic Server data An alarm is triggered only when the conditions are met Sampling frequency that specifies how often to evaluate the alarm Rescheduling time specifying when onprobe should res
88. t alarms are suited for global Dynamic Server system subjects and tend to remain fixed Permanent alarms serve as the system watchdog on the lookout for major problems For example permanent alarms are ideal for monitoring logical logs their absence points to a smooth running system 2 4 DB Cockpit User Manual Permanent and Session Alarm Files Session alarms on the other hand are easy to customize and replace They can be directed to handle specific issues answer everyday dynamic type needs and serve as local troubleshooters For example you can create a special alarm file to check caching Permanent and session alarm files can be active simultaneously one and only one permanent alarm file from onprobe and one session alarm file from each oncockpit client The permanent alarm file is not dependent on a graphical interface and because it is executed directly from onprobe you can use it at sites that do not have a full time Dynamic Server administrator Activating a session alarm file on the other hand requires a running oncockpit client Important DB Cockpit comes ready made with templates of a permanent alarm file and a session alarm file For more information on how to customize and activate these files refer to Activating Alarm Files on page 2 26 The following table summarizes the two alarm file types Permanent Alarm File Session Alarm File Requires onprobe to function By default onprobe loads the
89. ta from the sysmaster database by using SQL SELECT statements To create an SMI alarm click the SMI RADIO BUTTON Note that the title of the lower left area of the dialog box changes from Criteria to SQL Text If the alarm is triggered SELECT statement output is returned Cockpit is an alarm that uses data retrieval procedures especially defined for DB Cockpit To create a Cockpit alarm click the Cockpit radio button The Cockpit alarm includes a select list that defines the data to be retuned and criteria that define the condition that triggers the alarm The select list contains one or more field ID based expressions whose values you want retrieved for examination if the alarm is triggered Specify the desired select list in the right hand text box The select list resembles the SELECT list of a SELECT statement For more infor mation about select list syntax refer to DB Cockpit Select List Syntax on page 2 18 Defining a New Alarm To specify a field ID either type it in or select it from the list box To access the list box click the ellipsis button on the right side of the text box To select a field ID from the list use one of the following methods a Double click the desired field ID in the list to insert it at the position of the cursor a Click the field ID and then click the Apply button The field ID is inserted at the position of the cursor a Use the Motif built in Drag amp Drop feature by clicking
90. te onprobe because it detects the Dynamic Server mode automatically Although onprobe monitors a Dynamic Server instance it continues functioning by itself even when Dynamic Server is off line waiting until it is restarted While Dynamic Server is in off line mode onprobe cannot extract data When requested for data it sends an error message instead However while Dynamic Server is in quiescent mode onprobe can extract data from shared memory but not from SMI 1 10 DB Cockpit User Manual File View The DB Cockpit Main Window The DB Cockpit Main Window When you launch oncockpit the DB Cockpit main window is displayed as Figure 1 1 shows Edit Figure 1 1 The DB Cockpit Main Window DB Cockpit pern_shm User informix Sessions 4 Server pern_shm Up period 1 23 40 35 Status On line Since ckpt 0 00 00 16 Disks SHM buffers CPU ISAM calls Logical logs 1 The lower part of the DB Cockpit main window presents graphical displays of the resources that the Dynamic Server system uses The solid line on the Disks graph shows total disk operations reads and writes that the Dynamic Server system performs per second The broken line shows disk writes The distance between the two lines represents disk reads The SHM buffers graph shows the percentage of dirty shared memory buffers The solid line on the CPU graph shows total CPU time consumed by all user threads in the Dyn
91. tions reads iovpq read Number of disk reads writes iovpq write Number of disk writes disk copy iovpq copy Number of disk copies a Since Dynamic Server boot time or last onstat z command The DB Cockpit Viewer 3 45 The Shared Memory View The Shared Memory View The Shared Memory view monitors information about buffers LRU queues locks and SHM segments as well as SHM profile The main view shows an overall view of SHM operations From this top most view you can drill down to six other views each handling one aspect of shared memory Most of the field IDs in the Shared Memory views are either parameters included in the sysprofile table of the sysmaster database parameters that appear in the onconfig configuration file or unique DB Cockpit field IDs For more information refer to Field IDs on page 2 22 Any field ID checked in the Field ID column and all field IDs used in formulas in the Remarks column in the tables that describe Shared Memory views are in one of the above categories The Remarks column in the Shared Memory tables shows the formulas that DB Cockpit uses to calculate values Slope is a unique DB Cockpit function that measures changes in the sampled value over a period of time 3 46 DB Cockpit User Manual The Shared Memory View Figure 3 23 DB Cockpit Shared Memory pern_shm The Shared Memory View 0 50 100 cached reads ee cached writes ee es as Buffer w
92. ume alarm evaluation after the alarm was last triggered Output destination for alarm data and message if the alarm is triggered The Edit menu offers three items for editing the current file Defining a new alarm Modifying the components of a specific alarm Deleting an alarm Defining a New Alarm Defining a New Alarm To define a new alarm choose Edit gt New in the Alarm Editor The Alarm Request dialog box opens as Figure 2 2 shows Figure 2 2 Alarm Request Dialog Box with Initial Settings DB Cockpit Alarm Request pern_shm Message Cd Type and Field IDs O smi HE Active M Cockpit A Criteria 4 ox cance Sampling frequency Every 6 E Seconds Reschedule E After flo j LI Never Minutes x Deliver to HE Popup alarm O Mail O Pipe O Log File Message caused the alarm Example Time to back up logical logs Specify the following items in the Alarm Request dialog box You can add any free text in this area Text that you write is attached to the output when the alarm is triggered to help you understand the event that Using Alarms 2 9 Defining a New Alarm logs 2 10 DB Cockpit User Manual This example shows text attached to an alarm that checks the usage of logical Type and Field IDs You can define an alarm as either an SMI alarm or a Cockpit alarm SMI is an alarm that extracts da
93. yed DB Cockpit Table Profile pern_shm et1 account Reference count 0 Lock requests 2649 Lock waits 0 Deadlocks 0 Lock timeouts 0 isreads 883 iswrites 0 isrewrites 883 isdeletes 0 Buffer reads 6181 Buffer writes 883 Page reads 1546 Page writes 853 Sequential scans 0 cA Important The Table Profile view refreshes automatically 3 20 DB Cockpit User Manual Figure 3 10 The Table Profile View The Table Profile View The Table Profile view includes the following fields Label Field ID Remarks Reference count tabprof usercnt Number of current references to the table Lock requests tabprof lockreqs Lock waits tabprof lockwts Deadlocks tabprof deadlks Lock timeouts tabprof Iktouts isreads tabprof isreads iswrites tabprof iswrites isrewrites tabprof isrewrites isdeletes tabprof isdeletes Buffer reads tabprof bufreads Buffer writes tabprof bufwrites Page reads tabprof pagreads Page writes tabprof pagwrites Sequential scans tabprof seqscans The DB Cockpit Viewer 3 21 The Table Information View DB Cockpit Table Information pern_shm et1 account Owner Date created Number of rows Number of columns Row size Table type Number of partitions Total extents size K Total extent number Number of indexes Lock level Total no of pages used No of data pages used First extent size K

DB/Cockpit User Manual, Version 7.3

Contents

Download Pdf Manuals

Related Search

Related Contents