OracleTrace InstallationGuide - s-and-b.ru · PDF fileIf you ﬁnd any errors or have any ......

Oracle Trace™

Installation Guide

Version 2.2

Part No. A38158-1

®

Oracle Trace Installation Guide

Version 2.2

Part No. A38158-1

Copyright © Oracle Corporation, 1990, 1995

All rights reserved. Printed in the U.S.A.

This software/documentation contains proprietary information of Oracle Corporation; it isprovided under a license agreement containing restrictions on use and disclosure and is alsoprotected by copyright law. Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Departmentof Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights LegendUse, duplication, or disclosure by the Government is subject to restrictions as setforth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data andComputer Software (October 1988).

Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065.

If this software/documentation is delivered to a U.S. Government Agency not within theDepartment of Defense, then it is delivered with ‘‘Restricted Rights,’’ as defined in FAR52.227-14, Rights in Data – General, including Alternate III (June 1987).

The information in this document is subject to change without notice. If you find anyproblems in the documentation, please report them to us in writing. Oracle Corporationdoes not warrant that this document is error-free.

Oracle is a registered trademark of Oracle Corporation.

Oracle CDD/Administrator, Oracle CDD/Repository, Oracle CODASYL DBMS, OracleDBA Workcenter, Oracle Expert, Oracle Graphical Schema Editor, Oracle InstantSQL,Oracle Module Language, Oracle RALLY, Oracle Rdb, Oracle RMU, Oracle RMUwin,Oracle SQL/Services, Oracle Trace, and Oracle Trace Collector are trademarks of OracleCorporation.

All other product or company names mentioned are used for identification purposes only,and may be trademarks of their respective owners.

Contents

Send Us Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1 Preparing for Oracle Trace Installation

1.1 Required Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11.2 Required Operating System Components and Software . . . . . . . . . . . . . . 1–11.3 Special Checks and Requirements for Installing Oracle Trace . . . . . . . . . 1–21.4 Cluster Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–31.5 Installation Procedure Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–31.5.1 Process Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–31.5.2 Process Account Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–41.5.3 System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–51.5.4 Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–51.5.5 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–61.5.6 Additional System Maintenance Procedures . . . . . . . . . . . . . . . . . . . 1–61.5.6.1 Checking System Parameter Values . . . . . . . . . . . . . . . . . . . . . . . 1–71.5.6.2 Calculating the Values for Global Pagelets and Global

Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–71.5.6.3 Changing System Parameter Values with AUTOGEN . . . . . . . . . 1–81.5.6.4 Setting Dynamic System Parameter Values . . . . . . . . . . . . . . . . . 1–9

2 Installing Oracle Trace

2.1 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.2 Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8

iii

3 After Installing Oracle Trace

3.1 Running the Installation Verification Procedure Separately . . . . . . . . . . 3–23.2 Inserting Registered Facility Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3–23.3 Editing the System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33.4 Modifying System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33.5 Cluster Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43.5.1 Dividing a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43.6 User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–53.6.1 User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–53.6.2 User Account Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–53.7 Enhancing Oracle Trace Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63.8 Determining and Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6

A Sample Installation Log

B Files and Logical Names Installed on Your System

B.1 File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1B.2 Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4

Figures

2–1 The Process Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7

Tables

1 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii1–1 Hardware Requirements for Installing Oracle Trace . . . . . . . . . . . . . 1–11–2 Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–21–3 Minimum Required Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–31–4 Process Quotas for the Installing Account . . . . . . . . . . . . . . . . . . . . . 1–41–5 Minimum Required System Parameter Values . . . . . . . . . . . . . . . . . . 1–51–6 Disk Space Requirements for Oracle Trace . . . . . . . . . . . . . . . . . . . . 1–63–1 User Account Quotas for Using Oracle Trace . . . . . . . . . . . . . . . . . . . 3–5

iv

Send Us Your Comments

Oracle Corporation welcomes your comments and suggestions on thequality and usefulness of this publication. Your input is an important partof the information used for revision.

You can send comments to us in the following ways:

• electronic mail — [email protected]

• FAX — 603-881-1639 Attn: Oracle Trace Documentation

• postal service

Oracle CorporationOracle Trace Documentation110 Spit Brook Road, ZKO2-2/R88Nashua, NH 03062-2698USA

If you like, you can use the following questionnaire to give us feedback.

Name Title

Company Department

Mailing Address Telephone Number

Book Title Version Number

• Did you find any errors?

• Is the information clearly presented?

• Do you need more information? If so, where?

• Are the examples correct? Do you need more examples?

v

• What features did you like most about this manual?

If you find any errors or have any other suggestions for improvement,please indicate the chapter, section, and page number (if available).

vi

Preface

This guide describes how to install Oracle Trace for OpenVMS. TheOpenVMS VAX and OpenVMS Alpha hardware systems discussed in thisguide are products of Digital Equipment Corporation. The OpenVMSoperating system is also a product of Digital Equipment Corporation.Throughout this guide the hardware will be more simply referred to asVAX and Alpha and the operating system will be referred to as OpenVMS.

Intended AudienceThis document is intended for system managers. Keep this document withyour distribution kit. You will need it to install maintenance updates or toreinstall Oracle Trace for any other reason.

Document StructureThis guide contains the following chapters and appendixes:

• Chapter 1 describes how to prepare for Oracle Trace installation.

• Chapter 2 describes how to install Oracle Trace.

• Chapter 3 describes postinstallation procedures.

• Appendix A shows a log from a sample installation.

• Appendix B lists the files and logical names installed on your systemwhen Oracle Trace is installed.

Associated DocumentationThe other components of the Oracle Trace documentation set are:

• Oracle Trace Collector User’s Guide — Provides a detailed descriptionof how to use the Oracle Trace Collector software.

• Oracle Trace Reporter User’s Guide — Provides a detailed description ofhow to use the Oracle Trace Reporter software.

vii

• Oracle Trace Monitor User’s Guide — Provides a detailed description ofhow to use the Oracle Trace Monitor software.

• Oracle Trace Getting Started — Provides a detailed description of howto get started using the Oracle Trace software.

For information on the Oracle Trace online release notes, see Chapter 1.

For information on OpenVMS system management, see the OpenVMSoperating system documentation set provided by Digital EquipmentCorporation.

ConventionsTable 1 lists the conventions used in this guide.

Table 1 Conventions

Convention Meaning

UPPERCASE TEXT Uppercase text indicates the name of acommand, file, parameter, procedure, orutility.

$ @SYS$UPDATE:VMSINSTAL In interactive examples, prompts or displayedtext appears in a monospace font. User inputappears in bold monospace font.

Ctrl/x A sequence such as Ctrl/x indicates that youmust hold down the key labeled Ctrl whileyou press another key or a pointing devicebutton; for example, Ctrl/C or Ctrl/Z.

[YES] Square brackets indicate that the encloseditem is a default value in a VMSINSTALprompt. Also, square brackets serve asdelimiters for a directory name in a filespecification.

. . . Horizontal ellipsis in an example indicatesthat you can enter additional parameters,values, or information.

.

.

.

Indented vertical ellipsis in an exampleindicates that information not directly relatedto the example has been omitted.

(continued on next page)

viii

Table 1 (Cont.) Conventions

Convention Meaning

$ The dollar sign is used to indicate the DCLprompt. This prompt may be different onyour system.

ix

1Preparing for Oracle Trace Installation

If your kit is damaged or if you find that parts of it are missing, contact yourOracle Corporation representative.

Oracle Trace provides online release notes, which are copied to the followingfile during installation:

SYS$HELP:EPC022.RELEASE_NOTES

Oracle Corporation strongly recommends that you read the release notes beforeproceeding with the installation. For information about how to access theonline release notes, see Section 2.1.

1.1 Required HardwareTable 1–1 describes the hardware items needed to install Oracle Trace.

Table 1–1 Hardware Requirements for Installing Oracle Trace

Item Purpose

VAX system To run OpenVMS VAX

Alpha system To run OpenVMS Alpha

1.2 Required Operating System Components and SoftwareOracle Trace for OpenVMS Version 2.2 requires OpenVMS VAX Version 5.4-3or higher or OpenVMS Alpha Version 1.5 or higher. Future Oracle Tracereleases may require higher versions of the operating system, as described inthe online release notes or the Before You Install Oracle Trace for OpenVMSVersion 2.2 letter.

The OpenVMS operating system comes with a variety of support options, orcomponents. Components include such features as networking and VAX RMSjournaling. To use Oracle Trace, your system should be running a version of

Preparing for Oracle Trace Installation 1–1

OpenVMS that includes the base component and the utilities (UTIL) tailoringclass.

Table 1–2 provides information on the software you must have installed onyour system before installing Oracle Trace.

Table 1–2 Prerequisite Software

Prerequisite Products Purpose

Oracle Rdb Version 4.0-2 orhigher

Provides access to the Administration database.

Motif Version 1.1 or higher Required in order to run the Oracle Trace Monitor.

1.3 Special Checks and Requirements for Installing Oracle TraceDuring the installation procedure, the Oracle Trace software verifies thefollowing:

• Oracle Rdb Version 4.0-2 or higher is installed, and the Oracle Rdb monitorprocess is active on the system. To start the Oracle Rdb monitor, issue thefollowing command:

$ @SYS$STARTUP:RMONSTART

• The Oracle Trace Registrar process is already running. If it is, then thisis a reinstallation and you must stop the existing Oracle Trace Registrarprocess by issuing the following command on all nodes in the cluster:

$ COLLECT STOP SYSTEM/ABORT

In addition, all users should exit from the Oracle Trace commandenvironment. If any user is bound to the History or Administrationdatabases, the installation procedure will not be able to convert those filesto the new Version 2.2 format.

• ACMS/EPC is installed on the system. For systems currently runningACMS/EPC, stop the Registrar process by issuing the following command:

$ EVENT COLLECT SHUTDOWN

In addition, Oracle Corporation recommends that before starting an upgrade,you first cancel all active collections, then shut down the Registrar process.After the installation, all registered images should be restarted.

1–2 Preparing for Oracle Trace Installation

If you do not cancel all collections before an upgrade, any processes that aregathering data will continue to do so until the collection interval ends, orthe image terminates, whichever comes first. Note that changes to facilitydefinitions might make it impossible to format or merge the data collectionfiles produced by previous versions of Oracle Trace.

After an upgrade, any processes which had been registered should be restartedso that they will re-register and be available for collection.

1.4 Cluster ConsiderationsTo use Oracle Trace in a cluster environment, specify EPC$ROOT (whenprompted during the installation) to be on a common shared disk for all nodesthat will run Oracle Trace.

If you are installing Oracle Trace in a mixed-interconnect cluster environment,you must perform the installation procedure on each of the system disks inthe cluster. The Oracle Trace software distinguishes the group of nodes bootedfrom each system disk as a separate cluster for cluster operations using OracleTrace commands. Alternatively, you can specify EPC$ROOT to point to amixed-interconnect clusterwide-accessible directory for all nodes comprisingthe cluster. Oracle Trace would then treat all nodes in the mixed-interconnectcluster as members of a single cluster.

1.5 Installation Procedure RequirementsThis section discusses settings that should be checked to be sure that yoursystem is ready for the installation of Oracle Trace to proceed.

1.5.1 Process PrivilegesTo install Oracle Trace, you must be logged into an account that has SETPRVor at least the privileges listed in Table 1–3.

Table 1–3 Minimum Required Privileges

ALTPRI DETACH SYSGBL SYSPRV

BYPASS NETMBX SYSLCK TMPMBX

CMKRNL PRMGBL SYSNAM WORLD

VMSINSTAL turns off BYPASS privileges at the start of the installation.


1.5.2 Process Account QuotasOracle Trace requires that the installation account has the minimum quotasshown in Table 1–4.

Table 1–4 Process Quotas for the Installing Account

AccountQuota Value

ASTLM 24

BIOLM 20

BYTLM 20,480

DIOLM 20

ENQLM 1,800

FILLM 50

PGFLQUO1 20,000

WSEXTENT1 2,048 or greater

WSQUOTA1 1,024 or greater

1These parameters need to be set high to facilitate the formatting of large data collection files.

Use the OpenVMS Authorize Utility to verify and change process quotasfor the installation account in the user authorization file (UAF). (Some sitesmay restrict the use of the OpenVMS Authorize Utility to certain accountsor people.) For instance, to change the BYTLM quota for the account-nameinstallation account, you might enter the following command sequence:

$ RUN SYS$SYSTEM:AUTHORIZEUAF> MODIFY account-name /BYTLM = 18000UAF> SHOWaccount-nameUAF> EXIT$ LOGOUT

After the quotas for the installation account have been changed, log out of theinstallation account and log in again for the new quotas to take effect. You canthen proceed with the installation.

User account quotas are stored in the file SYSUAF.DAT. For more informationon modifying account quotas, see the OpenVMS documentation set.


1.5.3 System ParametersTable 1–5 lists the minimum required system parameter values for theinstallation. Depending on the kinds of programs and applications running atyour site, you might need higher values for some settings.

Table 1–5 Minimum Required System Parameter Values

System Parameter Minimum Value

CLISYMTBL1 250

GBLPAGES 105 available pages

GBLSECTIONS 8 available sections

LOCKIDTBL_MAX2 2,048 entities

MAXBUF2 1,200 bytes

PROCSECTCNT 32 sections

RESHASHTBL 512 entries

SRPCOUNTV 2,048 packets

VIRTUALPAGECNT3 20,000

1The CLISYMTBL dynamic system parameter must be set to a minimum value of 250 during theinstallation procedure. You can change the setting to its original value once the installation isfinished.2These dynamic system parameters must be set permanently to values equal to or greater than thevalues listed. Do not lower these values after the installation.3This parameter value should be set high to facilitate formatting of large data collection files andreporting on large formatted databases. You might need to raise this parameter to 50,000.

1.5.4 Disk SpaceThe installation procedure checks your system during installation anddetermines whether you are in a cluster or standalone environment. Ona standalone system, the installation creates a smaller Administrationdatabase. Note that if you later add this standalone machine to a cluster,or build a cluster around the standalone node, you must reinstall the OracleTrace software so that the installation procedure creates the larger, clusterAdministration database. See the EXTRACT DEFINITION command in theOracle Trace Collector User’s Guide for information on how to move existingfacility definitions from one Administration database to another.

Table 1–6 summarizes the storage requirements during and after installationfor the various Oracle Trace options.


During the installation, you can specify that the Oracle Trace root directory(EPC$ROOT) be placed on any device that is accessible from all nodes in yourcluster. Table 1–6 shows the disk space requirements for each device. Youshould plan for additional space on the EPC$ROOT device to accommodatethe History database (EPC$HISTORY_DB) and any dump files created byOracle Trace during a bugcheck. Note that if disk quotas are enabled on theEPC$ROOT device, the EPC$SERVER account is given a quota of 100,000blocks.

Table 1–6 Disk Space Requirements for Oracle Trace

ConfigurationBlocks DuringInstallation

Blocks AfterInstallation System Disk

EPC$ROOTDisk

Full StandaloneVAX

26,900 18,400 10,400 8,000

Full VAXcluster 31,000 19,100 10,400 8,700

Full StandaloneAlpha

32,000 25,700 17,700 8,000

Full Alpha cluster 36,100 26,400 17,700 8,700

Note that the requirements for an upgrade may be higher because theinstallation procedure attempts to convert existing History and Administrationdatabases to the new Version 2.2 format.

To determine the number of free disk blocks on the current system disk, enterthe following command at the DCL prompt:

$ SHOW DEVICE SYS$SYSDEVICE

1.5.5 Backing Up Your System DiskAt the beginning of the installation, VMSINSTAL asks if you have backedup your system disk. Oracle Corporation recommends that you back up yoursystem disk before installing any software.

Use the backup procedures that are established at your site. For details onperforming a system disk backup, see the section on the Backup Utility in theOpenVMS documentation set.

1.5.6 Additional System Maintenance ProceduresThis section explains how to use the System Generation Utility (SYSGEN) andthe AUTOGEN Utility to prepare your system for an installation of OracleTrace. AUTOGEN uses system configuration data to automatically set systemparameters.


1.5.6.1 Checking System Parameter ValuesTo check the values of your system parameters, enter the following commandat the DCL prompt to invoke SYSGEN:

$ RUN SYS$SYSTEM:SYSGENSYSGEN>

At the SYSGEN> prompt, enter the SHOW command to display the value of asystem parameter. The following example displays the value for the WSMAXsystem parameter:

SYSGEN>SHOW WSMAX

After checking the parameters with the SHOW command, enter the EXITcommand at the SYSGEN> prompt to return to DCL level. For information onsetting dynamic system parameter values, see Section 1.5.6.4.

1.5.6.2 Calculating the Values for Global Pagelets and Global SectionsTo install and run Oracle Trace, you must have sufficient free global pageletsand global sections. You must first find out how many free global pagelets andsections you have on your system. Then use AUTOGEN if you need to increasethe global pagelets and global sections system parameters.

Enter the following DCL command to determine the number of global pageletsrequired by SYS$LIBRARY:DCLTABLES.EXE:

$ DIR/SIZE SYS$LIBRARY:DCLTABLES.EXE

This command returns the size of SYS$LIBRARY:DCLTABLES.EXE (in blocks).As an approximation, use this figure as the number of global pagelets for thefile.

You can use the WRITE command with the F$GETSYI lexical function tofind the number of free global pagelets and global sections. The followingexample shows how to get this information at your terminal (the default forSYS$OUTPUT):

$ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")15848$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")24

If the values displayed by the system are greater than the values in Table 1–5,you do not need to increase the values for these parameters. If the value offree global pagelets or global sections is less than the value in Table 1–5, youmust increase the system parameter setting.

Section 1.5.6.3 describes the procedures for increasing these values usingAUTOGEN.


1.5.6.3 Changing System Parameter Values with AUTOGENUse the AUTOGEN utility to change system parameters. AUTOGENautomatically adjusts values for parameters that are associated with thevalues you reset manually. To change system parameters with AUTOGEN, editthe following file:

SYS$SYSTEM:MODPARAMS.DAT

Use an editor to access the file. To change a parameter value listed in thisfile, delete the current value associated with that parameter and enter the newvalue.

To add a new parameter, add a line to the file that includes both the name ofthe parameter and its value. For example:

WSMAX = 8096

To modify incremental parameters such as free global pagelets and globalsections, use ADD_. The following example increases the global page settingby 2000:

ADD_GBLPAGES = 2000

Note that when you set the page file quota, do not use a value that exceeds theamount of page file space available on the system.

After you make all your changes, exit from the editor and execute theAUTOGEN procedure to recalculate your system parameters. The followingcommand recalculates your system parameters and reboots the system:

$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

When you specify REBOOT, AUTOGEN performs an automatic systemshutdown and then reboots the system. Any users logged onto the systemare immediately disconnected during the shutdown. The automatic reboot putsthe new parameter values into effect.

AUTOGEN automatically adjusts some of the SYSGEN parameters based onthe consumption of resources since the last reboot. If you do not want to takeadvantage of this automatic adjustment, include the /NOFEEDBACK qualifieron the AUTOGEN command line.

For more information about using AUTOGEN, see the OpenVMS systemdocumentation.


1.5.6.4 Setting Dynamic System Parameter ValuesUse SYSGEN to set dynamic parameters. Dynamic parameters changed withthe SYSGEN command WRITE ACTIVE become active immediately withoutany need to reboot your system. In fact, rebooting returns dynamic systemparameter values to their previous settings.

Once you change dynamic parameter values, you should complete theinstallation before rebooting the system. After you finish the installation,you can reset the dynamic parameters to their previous values or let them bereset automatically when you reboot your system the next time.

If the dynamic parameter values on your system are less than the valuespreviously listed, use the following series of commands to change the values.This example changes the CLISYMTBL value to 250.

$ RUN SYS$SYSTEM:SYSGENSYSGEN>USE ACTIVESYSGEN>SET CLISYMTBL 250SYSGEN>WRITE ACTIVESYSGEN>EXIT


2Installing Oracle Trace

The Oracle Trace installation takes approximately 10 to 20 minutes, dependingon your system configuration. A sample installation log is provided inAppendix A.

2.1 Installation ProcedureOn OpenVMS Alpha Systems: If it is not already inserted,place the compact disc (CD) media into the CD drive.

To abort the installation procedure at any time, press Ctrl/Y. When you pressCtrl/Y, the installation procedure deletes all files it has created up to that pointand exits. You can then start the installation again.

When the system prompts you with a question during the installationprocedure, the default answer is often listed in brackets ([ ]).

1. Log into a privileged account and set your default device anddirectory to SYS$UPDATE.

Username: SYSTEMPassword:

$ SET DEFAULT SYS$UPDATE

2. Invoke VMSINSTAL.

@SYS$UPDATE:VMSINSTAL saveset-name device-name option-list

To start the installation, invoke the VMSINSTAL command procedure froma privileged account, such as the SYSTEM account. VMSINSTAL is in theSYS$UPDATE directory.

If you do not supply either the saveset name or the device name,VMSINSTAL prompts you for this information later in the installationprocedure. VMSINSTAL does not prompt you for any options, so be sureto include OPTIONS N on the VMSINSTAL command line to access therelease notes during the installation.

Installing Oracle Trace 2–1

Descriptions of these elements are as follows:

saveset-nameThe installation name for the component. For Oracle Trace, use thefollowing installation name:

EPC022

On OpenVMS Alpha Systems: To obtain the directorylocation of the Oracle Trace saveset on the CD, refer tothe OpenVMS Alpha Layered Products Compact Discdocumentation that accompanies the CD distributionkit, or before starting installation, complete thesesteps:

a. To determine whether the CD drive is alreadymounted (MOUNT command), enter the followingcommand:

$ SHOW DEVICE EPC$KIT:

b. If it is not mounted, enter the appropriate MOUNTcommand to mount to CD (omit the /FOREIGNqualifier).

c. To obtain the saveset name, use a DIRECTORYcommand specifying the directory file from theprevious command:

$ DIRECTORY EPC$KIT:EPC022

device-nameThe name of the device on which you plan to mount the media and thedirectory containing the Oracle Trace saveset. For example, in this guideEPC$KIT: is the sample device name used. The directory is EPC022.

2–2 Installing Oracle Trace

option-listThe word OPTIONS followed by one or more of the following optiondesignators: A, G, L, N, R:

• Auto_answer option (A)

Initially creates a file that contains your answers to VMSINSTALquestions and prompts. You can then use the option (and the answerfile) to save time during a reinstallation (typically after upgrading yoursystem).

• Get save-set option (G)

Lets you store product savesets temporarily on a magnetic tape or in adisk directory.

• File log option (L)

Logs all activity to the terminal during installation.

• Display or print the release notes (N)

Indicates that you want to see the installation question on releasenotes. If you do not include the N option, VMSINSTAL does not askyou about the release notes. You should review the release notesbefore proceeding with the installation in case they contain additionalinformation about the installation.

If you are restarting the installation and have already reviewed therelease notes, you do not need to specify the N option. (Even if youomit the N option when you invoke VMSINSTAL, the Oracle Tracerelease notes are copied automatically to the SYS$HELP directory.)

• Alternate root option (R)

Lets you install the product to a system root other than that of therunning system.

For detailed information on these software installation options, see theOpenVMS operating system documentation. If you specify more than oneoption, separate the options with commas, such as:

OPTIONS A,N

When you invoke VMSINSTAL, it checks the following:

• Whether you are logged into a privileged account. Oracle Corporationrecommends that you install software from the system manager’saccount with your default device and directory set to SYS$UPDATE.

• Whether you have adequate quotas for installation. VMSINSTALchecks for the quota values shown in Table 1–4.


VMSINSTAL then checks to determine whether any users are logged intothe system. If users are logged in, VMSINSTAL asks whether you want tocontinue the installation:

* Do you want to continue anyway [NO]? YES

If you want to continue, enter YES. If you want to stop the installation,press Return.

3. Confirm system backup.

* Are you satisfied with the backup of your system disk [YES]?

If you are satisfied with the backup of your system disk, press Return.Otherwise, enter NO to discontinue the installation. After you back upyour system disk, you can restart the installation.

If you omitted the device name on the VMSINSTAL command line, thefollowing prompt appears:

* Where will the distribution volumes be mounted: EPC$KIT:[EPC022]

On OpenVMS Alpha Systems: If this prompt appears,enter the name of the distribution (media) device anddirectory that contains the Oracle Trace kit (saveset).In this example, the media is contained on a devicenamed EPC$KIT:, in a directory named [EPC022].

On OpenVMS VAX Systems: You should now mountthe first distribution volume on the device you specifiedwhen you invoked VMSINSTAL.

Depending on the type of device and whether the deviceis already mounted, the following prompt may or maynot appear:

Please mount the first volume of the set onEPC$KIT:.

* Are you ready? YES%MOUNT-I-MOUNTED, EPC$KIT: mounted

If you have not already done so, you should now insertthe distribution volume on the device you specified whenyou invoked VMSINSTAL. The device name appears inthe line preceding the question. VMSINSTAL then asksif you are ready to continue with the installation.

If you respond YES to indicate that you are ready, VMSINSTAL displays amessage that the media containing Oracle Trace has been mounted on thespecified device and that the installation has begun.


If you entered the wrong device name when you invoked VMSINSTALand need to restart the installation, enter NO in response to the ‘‘Are youready?’’ question. To abort the installation for other reasons, press Ctrl/Y.

4. Verify the product being installed.

The following products will be processed:

EPC022

Beginning installation of EPC022 at hh:mm

%VMSINSTAL-I-RESTORE, Restoring product saveset A...

The product name and version are displayed. The first saveset ( A ) isrestored to a subdirectory of SYS$UPDATE:.

5. Specify Oracle Rdb version.

*Do you want to use this version of Rdb [NO]?

The installation procedure notifies you of the default version of Oracle Rdbto be used in the installation. If you answer NO to this question, you areprompted for the version you want to use and asked whether you also wantthat version to be set system-wide.

6. Specify device specification.

*Specify device specification for EPC$ROOT [SYS$DEVICE:]:

7. Specify write access.

*Do you want to add public write access to the ADMINISTRATIONdatabase [YES]?*Do you want to add public write access to the HISTORY database [YES]?

These questions allow you to determine who has access to Oracle Trace. Ifyou answer NO, you can add the users directly by using the Oracle TraceSET ACCESS command after the installation is complete.

8. Specify a UIC and password.

*Enter UIC to be used for EPC$SERVER account:*Please enter PASSWORD to be used for EPC$SERVER account:

Installation of Oracle Trace requires the creation of an EPC$SERVERaccount. If this is a new installation, you must supply a password and aUIC for the EPC$SERVER account.

If this is a reinstallation, you will be prompted for a password, but not fora UIC.

The entire installation will fail if you do not enter a valid password (andUIC, if applicable).


9. Choose the Installation Verification Procedure (IVP) option.

* Do you want to run the IVP after the installation [YES]?

The installation procedure now asks if you want to run the IVP. The IVPfor Oracle Trace checks to be sure that the installation is successful. OracleCorporation recommends that you run the IVP.

After Oracle Trace is installed, you can run the IVP independently to verifythat the software is available on your system. You might need to run theIVP after a system failure to make sure that users can access Oracle Trace.

10. Purge files.

* Do you want to purge files replaced by this installation [YES]?

The directories SYS$HELP, SYS$LIBRARY, SYS$MESSAGE,SYS$SYSTEM, and SYS$TEST may contain previous versions of OracleTrace files. These files are replaced during the installation with new files,but the old files are not automatically purged. Purging is recommended,unless you need to keep files from previous versions.

11. Read informational messages.

At this point, the installation procedure displays informational messagesthat report on the progress of the installation. If the installation procedurehas been successful up to this point, VMSINSTAL moves the new ormodified files to their target directories, updates help files, and updatesDCL tables, if necessary. Refer to Appendix B for a list of these files.

Also, if you answered YES in response to the prompt that requests a filepurge, previous versions of the Oracle Trace files are now purged.

The end of the installation is indicated by the following message:

%VMSINSTAL-I-MOVEFILES, files will now be moved to their targetdirectories...

12. Observe the Installation Verification Procedure (IVP).

If you chose to run the IVP, VMSINSTAL now invokes the IVP to verifythat Oracle Trace was installed successfully.

The IVP displays the Monitor Process window as shown in Figure 2–1.


Figure 2–1 The Process Window

NU−3124A−RA

The IVP takes about 15 minutes to run through the Monitor demonstration.You can exit the replay earlier by selecting the Exit option from the Filemenu in the Process window.

If you let the Monitor demonstration continue to completion, a dialog boxpop ups informing you when it is over. Click on the OK button to exit andfinish the IVP.

If Oracle Trace was installed successfully, the IVP displays the following:

IVP Completed Successfully

13. End the installation procedure.

Installation of EPC V2.2 completed at 09:37

VMSINSTAL procedure done at 09:41:54.02

Depending on whether you specified parameters on the VMSINSTALcommand line, the * Products: prompt or the DCL prompt ( $ ) mayappear. If the * Products: prompt appears, you can return to the DCLprompt ( $ ) by pressing Ctrl/Z.

If you removed any media from the console drive before beginning theinstallation, you should replace it now.


VMSINSTAL deletes or changes entries in the process symbol tablesduring the installation. Therefore, if you are going to continue using theinstallation account (such as SYSTEM) and you want to restore thesesymbols, you should log out and log in again.

2.2 Error RecoveryIf VMSINSTAL detects any problems during the installation, it notifies youand asks if you want to continue the installation. In some instances, youcan enter YES to continue. To stop the installation process and correct thesituation, enter NO or press Return. Then correct the problem and restart theinstallation.

If errors occur during the installation itself or when the InstallationVerification Procedure (IVP) is running, VMSINSTAL displays failuremessages. If the installation fails, you see the following message:

%VMSINSTAL-E-INSFAIL, The installation of Oracle Trace for OpenVMSVersion 2.2 has failed.

If the IVP fails, you see the following message:

**************************************************************** ** The EPC V2.2 IVP has failed. ** The reason for the failure is listed above. ** ** You should: 1. Correct the problem indicated ** 2. Execute $@SYS$TEST:EPC$IVP.COM ** ** ****************************************************************

Errors can occur during the installation if any of the following conditionsexists:

• The operating system version is incorrect.

• A prerequisite software version is incorrect.

• Quotas necessary for successful installation are insufficient.

• System parameter values for successful installation are insufficient.

• The OpenVMS Help library is currently in use.

• Multiple versions of Oracle Rdb exist on the system.


For descriptions of the error messages generated by these conditions, seethe OpenVMS documentation on system messages and recovery procedures.If you are notified that any of these conditions exists, you should take theappropriate action as described in the message. For information on installationrequirements, see Chapter 1.


3After Installing Oracle Trace

Oracle Trace is now installed and can be invoked by all users with theCOLLECT command.

The installation procedure modifies the DCL command table so that theCOLLECT command is recognized and processed. However, the previouscommand table is still in effect for those users who are currently logged in. Alllogged-in users who want to use the COLLECT command must log out and login again, or use the following DCL command:

$ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES

The following tasks can be performed after Oracle Trace is installed:

• Running the Installation Verification Procedure (IVP) separately

• Inserting registered facility definitions into the Oracle TraceAdministration database

• Editing the system startup and shutdown files

• Modifying system parameter settings

• Making the product usable on a cluster

Reinstall (using the VMSINSTAL utility) the imageSYS$SHARE:DCLTABLES.EXE on each node that will be runningOracle Trace Version 2.2.

Execute the SYS$STARTUP:EPC$STARTUP.COM startup file on eachnode that will be running Oracle Trace. This is executed automaticallyas part of the IVP on the node you used for the installation.

• Enhancing performance

• Reporting problems

The following sections describe these tasks in detail.

After Installing Oracle Trace 3–1

3.1 Running the Installation Verification Procedure SeparatelyYou usually run the Installation Verification Procedure (IVP) during theinstallation. However, if you want to run the IVP separately to ensure theintegrity of installed files should system problems occur, enter the followingcommand procedure:

$ @SYS$TEST:EPC$IVP.COM

If the IVP fails for any reason, the following message is displayed:

Oracle Trace Version 2.2 TEST FAILED

Oracle recommends that you run the IVP on every node where you intend touse Oracle Trace.

3.2 Inserting Registered Facility DefinitionsIf you are installing Oracle Trace for the first time, you must enter facilitydefinitions into the Oracle Trace Administration database using a commandprocedure called EPC$INSERT.COM.

To insert the facility definitions, execute the command procedure, as follows:

$ @EPC$EXAMPLES:EPC$INSERT.COM

The command procedure prompts you to verify each facility definition before itinserts it into the Administration database.

If you want to add all of the facility definitions from the Oracle Trace facilitylibrary, SYS$LIBRARY:EPC$FACILITY.TLB, into the Administration databaseand submit the command procedure as a batch job, use the following command:

$ @EPC$EXAMPLES:EPC$INSERT.COM ALL

In both cases, the EPC$INSERT procedure checks for the existence of theOracle Trace facility library, located in SYS$LIBRARY:EPC$FACILITY.TLB.

In Oracle Trace Version 2.2, this command procedure does not move anyfacility definitions that have events defined as both point and duration into theVersion 2.2 Administration database.

Note

After you run EPC$INSERT.COM, you could have facility definitionsfor more than one version of a facility in the facility library. If thishappens, you must explicitly specify the correct facility version whenyou create a selection for a facility. If you do not supply a facilityversion on the CREATE SELECTION command, Oracle Trace uses the

3–2 After Installing Oracle Trace

the facility definition with the most recent creation date as the defaultversion.

Subsequent versions of the layered products automatically insert theirfacility definitions into the Oracle Trace Administration database as partof their installation procedures. That is why you only have to run theEPC$INSERT.COM command procedure when you are installing Oracle Tracefor the first time.

3.3 Editing the System FilesYou must edit the system startup and shutdown files to provide for automaticstartup and shutdown of Oracle Trace when your system is rebooted.

Add the command line that starts Oracle Trace to the system startup fileSYS$MANAGER:SYSTARTUP_V5.COM. You must position this new commandline after the line that activates the Oracle Rdb monitor process.

$! Start the Oracle Rdb monitor process$ @SYS$STARTUP:RMONSTART.COM$! Start Oracle Trace$ @SYS$STARTUP:EPC$STARTUP.COM

Add the Oracle Trace shutdown procedure to the system shutdown fileSYS$MANAGER:SYSHUTDWN.COM. You must position this new commandline before the line that stops the Oracle Rdb monitor process.

$! Shutdown Oracle Trace and abort all active data collection$ COLLECT STOP SYSTEM /ABORT$! Wait for Registrar processing to complete$ WAIT 00:00:30$! Shutdown the Oracle Rdb monitor process$ @SYS$MANAGER:RMONSTOP.COM

3.4 Modifying System ParametersThe installation for Oracle Trace requires that you raise the values of theCLISYMTBL and CTLPAGES system parameters. Once the installation iscomplete, lower these values to ensure efficient system performance. Table 1–5contains the values for the parameters under normal operations.

If you typically format very large data collection files, you may need to increasethe enqueue limit quota (ENQLM) on your process. If you do this, you mustalso raise the corresponding system parameters. If you increase your ENQLM,the lock ID table (LOCKIDTBL_MAX) must be set to a value at least as high


as the ENQLM. Also, the resource hash table (RESHASHTBL) should be set toat least one-quarter the value of the lock ID table.

3.5 Cluster ConsiderationsStart the Oracle Trace Registrar process on each node for which you want datacollection enabled. Issue the following command on each node:

$ @SYS$STARTUP:EPC$STARTUP.COM

You may need to use the VMSINSTAL utility to replace the DCLTABLES.EXEimage on each node:

$ INSTALLINSTALL> REPLACE SYS$SHARE:DCLTABLES.EXE/OPEN/HEADER/SHARE

Note that you must log out and back in again for the new DCL tables to takeeffect. If you do not, your process will not recognize the COLLECT command.

3.5.1 Dividing a ClusterIf you have Oracle Trace installed on a cluster and then decide to reorganizethe cluster into two or more clusters, you can preserve the facility definitionsand selections stored in your Administration database. Perform the followingsteps:

1. Extract EPC$EXT_ADMIN_DB.DB_EXE and EPC$INS_ADMIN_DB.DB_EXE from the EPC022.A saveset.

2. Shut down the Registrar processes on each node in the cluster by enteringthe COLLECT STOP SYSTEM /ABORT command on each system.

3. Run the EPC$EXT_ADMIN_DB.DB_EXE image on the original cluster.One EPC$DEF binary file and seven TXT flat files will be placed in theEPC$DATABASE_DIR directory.

4. Divide the cluster.

5. Reinstall Oracle Trace on the original and new clusters.

6. Shut down the Registrars on the nodes used to install Oracle Trace.

7. Run the EPC$INS_ADMIN_DB.DB_EXE image on the original cluster.

8. Copy the EPC$DEF and TXT files to the EPC$DATABASE_DIR directoryon the new clusters.

9. Run the EPC$INS_ADMIN_DB.DB_EXE image on the new clusters.

10. Delete the EPC$DEF and TXT files.


11. Restart the Registrars on all nodes (@SYS$UPDATE:EPC$STARTUP).

Note

You cannot simply back up the original database and then restore iton the new cluster. The Registrar would attempt to start collections onnodes that are no longer part of the original cluster.

3.6 User Account RequirementsSome products cannot be used unless certain privilege and quota requirementsare met by user accounts. The following sections describe the privilege andquota requirements needed to work with Oracle Trace.

3.6.1 User PrivilegesTo use Oracle Trace, each account must have at least the TMPMBX andNETMBX privileges. Use the OpenVMS Authorize Utility to determinewhether users have the privileges they require.

3.6.2 User Account QuotasYou must make sure that the appropriate user accounts have sufficient quotasto be able to use Oracle Trace. If you typically format very large collection files(over 50,000 blocks) and generate reports based on large formatted databases,you can improve performance by increasing several of your account quotas.Table 3–1 summarizes the required and optional user account quotas.

Table 3–1 User Account Quotas for Using Oracle Trace

Account Quota Normal Use Formatting and Reporting on Large Files

ASTLM 24

BIOLM 20

BYTLM 20,480 34,810

DIOLM 20

ENQLM 1,800 10,000

FILLM 50

PGFLQUO 20,000 75,000

(continued on next page)


Table 3–1 (Cont.) User Account Quotas for Using Oracle Trace

Account Quota Normal Use Formatting and Reporting on Large Files

PRCLM 1

WSEXTENT 2048

WSQUOTA 1024

See Section 1.5.2 for a description of how to verify and change account quotas.

3.7 Enhancing Oracle Trace PerformanceThis section includes information on system tuning and explains how to installOracle Trace as a shared image.

After you install Oracle Trace, you might want to adjust your system toenhance performance or lower the use of some system resources. Onerecommendation is to increase process working set parameters which willspeed up Oracle Trace formatting operations and report generations.

After you perform a number of collections on your system, you may wish tocreate a new version of the History database and purge (or offload) the oldone. If you want this to happen automatically, place the Oracle Trace SETHISTORY/NEW_FILE command into your site-specific startup procedure. Thiscommand closes the old database and creates a new one. If you choose to dothis, you should put the command before the execution of EPC$STARTUP sothat no history data is lost. For example:

$ COLLECT SET HISTORY/NEW_FILE$ PURGE/NOLOG/NOCONFIRM/KEEP=2 EPC$HISTORY_DB$ @SYS$STARTUP:EPC$STARTUP

3.8 Determining and Reporting ProblemsIf you encounter a problem while using Oracle Trace, report it to your OracleCorporation representative.


ASample Installation Log

This appendix contains a sample log from an installation of Oracle Tracefor OpenVMS Alpha. The log from your own installation may look slightlydifferent.

OpenVMS ALPHA Software Product Installation Procedure V1.5

It is 23-AUG-1995 at 13:04.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.%VMSINSTAL-W-ACTIVE, The following processes are still active:

Jonathan_3Jonathan_2NOTES$00E1_0*Jonathan_1DECW$TE_025BDECW$TE_015CGROYAL_FTA5:MEGADECW$TE_0284ToddTodd_2DECW$TE_0292HIGGSUCX$REXEC_BG242DECW$TE_01BCGOR_FTA30:GodzillaDECW$TE_01EEDECW Notes

* Do you want to continue anyway [NO]? y* Are you satisfied with the backup of your system disk [YES]?

The following products will be processed:

EPC V2.2

Sample Installation Log A–1

Beginning installation of EPC V2.2 at 13:04

%VMSINSTAL-I-RESTORE, Restoring product save set A ...%VMSINSTAL-I-RELMOVED, Product’s release notes have been moved to SYS$HELP.

Installation procedures for: "Oracle Trace V2.2"

Be sure you have read the section entitled

"Installation Procedure Requirements"

in the Oracle Trace installation guide before continuing withthe installation.

Checking system requirements ...

Your current process level version of Oracle Rdb is as follows

Current PROCESS Oracle Rdb environment is version V5.1-03 (MULTIVERSION)

The following versions of Oracle Rdb are installed on your system

"RDBVMS$INSTALLED_VERSIONS" = "V5.1-0" (LNM$PROCESS_TABLE)= "*V5.1-03"= "*V6.0-0"

**************************************************************

You have multiple of Oracle Rdb on your system. An asteriskbeside the version indicates a multiversion variant ofOracle Rdb and is not part of the actual version name. Thedifferent versions are:V5.1-0*V5.1-03*V6.0-0

**************************************************************

**************************************************************

The default version of Oracle Rdb to be used for thisinstallation is: 6.0The corresponding Oracle Rdb monitor must be running.

**************************************************************

* Do you want to use this version of Rdb [YES]? no

*******************************************************************

A–2 Sample Installation Log

Oracle Rdb V4.0-2 or greater is required.If the Oracle Rdb monitor (RDMS_MONITORxx) is not runningthe install will fail accessing the databases. If you wantto use a specific version and the corresponding Oracle Rdb monitoris not running, you may abort the installation, start themonitor (@SYS$STARTUP:RMONSTARTxx.COM) and restart theinstallation.

*******************************************************************

* Do you want to continue with the installation [YES]?

* Which version of Oracle Rdb installed on your system do you want to use: 5.1Current PROCESS Oracle Rdb environment is version V5.1-03 (MULTIVERSION)Current PROCESS SQL environment is version V5.1-03 (MULTIVERSION)Current PROCESS Rdb/Dispatch environment is version V5.1-13 (MULTIVERSION)

* Do you want to continue with the installation [YES]?

****************************************************************

The detached process EPC$REGISTRAR will be started with5.1, as its default version.If you wish to at this time you may change this to be the defaultsystem version of Oracle Rdb as well.

****************************************************************

* Do you want to set the Rdb version systemwide to the above version [YES]? no

* Specify device specification for EPC$ROOT [SYS$SYSDEVICE:]:%EPC-I-LIBRARY, The logical name EPC$ROOT is defined as SYS$SYSDEVICE:[EPC.]

******************************************************************

SYSTEM MANAGER:

By adding PUBLIC access to the Oracle Trace databases you areallowing all users on your system access to Oracle Trace. If youwant to allow only certain users access to Oracle Trace, enter Noat the prompts and add the users directly via the Oracle TraceSET ACCESS command after the installation.

******************************************************************

* Do you want to add public write access to the ADMINISTRATION database [YES]?* Do you want to add public write access to the HISTORY database [YES]?

*************************************************************

An EPC$SERVER account has been found. This account willcontinue to be used. You will be asked to give a newpassword for the account.

**************************************************************


* Please enter carriage return to continue:

*************************************************************

The entire installation will FAIL if you do not enter a validpassword for the EPC$SERVER account. This installationprocedure requires at least 15 characters for theEPC$SERVER password. Valid characters for a password are:

A through Za through z0 through 9$ (dollar sign)_ (underscore)

As with the DCL SET PASSWORD command, your input will notappear on the terminal.

*************************************************************

Please enter a password of at least 15 characters.

=

* Password:==

* Verification:=%VMSINSTAL-I-SYSDIR, This product creates system disk directoryVMI$ROOT:[SYSTEST.EPC].%CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.EPC] already exists%VMSINSTAL-I-SYSDIR, This product creates system disk directorySYS$SYSDEVICE:[EPC.][HOMEDIR].%CREATE-I-EXISTS, SYS$SYSDEVICE:[EPC.][HOMEDIR] already exists%VMSINSTAL-I-SYSDIR, This product creates system disk directorySYS$SYSDEVICE:[EPC.][DATABASES].%CREATE-I-EXISTS, SYS$SYSDEVICE:[EPC.][DATABASES] already exists%VMSINSTAL-I-SYSDIR, This product creates system disk directoryVMI$ROOT:[SYSHLP.EXAMPLES.EPC].%CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.EPC] already exists

The sample data file used in the Oracle Trace Monitor User Guide willbe copied to EPC$EXAMPLES:DEMO_DATA.DAT. This file is needed torun the Monitor portion of the IVP.

You may delete this file (1290 blocks) after the installation hascompleted

* Do you want to run the IVP after the installation [YES]?* Do you want to purge files replaced by this installation [YES]?

Beginning installation ...


If this is an upgrade an attempt will be made to convert the existingTrace databases. If the existing databases are compatible withthis version, no conversion will be needed. If no errors are encountered,

there will be no more questions.Installing under VMS V1.5 -

%VMSINSTAL-I-RESTORE, Restoring product save set B ...%DCPS-I-JOBSTART, Job ECONCAL (queue SSG_LPS17, entry 242) started on

SSG_LPS17_DTRACY

Creating the Administration database...

Job ECONCAL (queue SSG_LPS17, entry 242) completed

Creating the History database...

There are no more questions. The remainder of the installationtakes approximately 15 minutes on a standalone VAX-11/780.

****************************************************************

SYSTEM MANAGER:

The following command line MUST be added to the system startupcommand file SYS$MANAGER:SYSTARTUP_V5.COM for all nodes that willbe running Oracle Trace.NOTE: Add this command line after starting Oracle Rdb

$ @SYS$STARTUP:EPC$STARTUP.COM

The following command line MUST be added to the system shutdowncommand file SYS$MANAGER:SYSHUTDWN.COM for all nodes that willbe running Oracle Trace.NOTE: Add this command line before shutting down the Rdbmonitor.

$ COLLECT STOP SYSTEM/ABORT

****************************************************************

*************************************************************

All applications instrumented with Oracle Trace must berestarted in order to be able to be part of an activecollection.

*************************************************************

*************************************************************

The Oracle Trace Installation Verification Procedure (IVP) hasbeen provided in SYS$TEST

It is invoked using the command:


$ @SYS$TEST:EPC$IVP.COM

*************************************************************

*************************************************************

An Oracle Trace postinstallation procedure has been providedin EPC$EXAMPLES. The purpose of this procedure is toinsert ACMS, ALL-IN-1, DBMS, DECforms, RALLY, and Rdbfacility definitions into the Oracle Trace Administrationdatabase on your system.

It is invoked using the command:

$ @EPC$EXAMPLES:EPC$INSERT.COM

*************************************************************

*************************************************************

The Oracle Trace sample ATM application has been providedin EPC$EXAMPLES.

*************************************************************

*************************************************************

The release notes for Oracle Trace are available in the fileSYS$HELP:EPC022.RELEASE_NOTES

*************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their targetdirectories...

"RDBVMS$INSTALLED_VERSIONS" = "V5.1-0" (LNM$PROCESS_TABLE)= "*V5.1-03"= "*V6.0-0"

%RUN-S-PROC_ID, identification of created process is 20600315$$******************************************************************** ** Executing the IVP ********************************************************************Displaying Oracle Trace HELP from DCL...

Oracle_TRACE

Notice of Product Name Changes: The product DECtrace and a number ofother related products were recently purchased from Digital EquipmentCorporation by Oracle Corporation. DECtrace is now known as OracleTrace. Because the sale of these products was concluded recently,the software/documentation does not necessarily reflect the new namesfor all the products in all cases.


Oracle Trace is a layered product that collects and reports onevent-based data gathered from layered products and applications thatcontain Oracle Trace service routine calls. Oracle Trace operates withminimal performance impact on the system and thus can be used in bothproduction and development environments.

Additional HELP is provided within the Oracle Trace command environmentand can be viewed with the command:

Press RETURN to continue ...

$ COLLECT HELP

Additional information available:

Interface Release_notes Error_messages Sample_applicationLogical_names IVP Deinstallation

Oracle_TRACE Subtopic?Topic?

Displaying HELP using the Oracle Trace HELP command...

Information available:

@(Execute_Procedure) CANCEL_COLLECTION Command_Syntax CREATEDELETE Error_Messages_and_Recovery EXIT EXTRACT_DEFINITIONFORMAT HELP INSERT_DEFINITION MONITOR Name_Change_NoticeREPORT SCHEDULE_COLLECTION Service_Routines SET SHOWSPAWN STOP_SYSTEM

Creating a facility definition...%EPC-S-FACCRE, Facility definition EPC$IVP_FAC V1.0 was created

Showing the facility definition...23-AUG-1995 14:02 Facility Definition Information Page 1Full Report Oracle Trace V2.2

Facility: EPC$IVP_FACNumber: 750Version: V1.0 DEFAULTCreation Date: 23-AUG-1995 14:02Created By: ROYAL

Events:

Event Name Event ID Report Header--------------- -------- ----------------FIRST_EVENT 1 FIRST_EVENTSECOND_EVENT 2 SECOND_EVENT

Items:


Item Name Item Datatype Max. Usage Item Report Report Char RadID Size Type Header Width

------------ ---- -------- ---- ------- ------------ ------ ---- ---BIO 101 LONGWORD 4 COUNTER Buffered I/O 11 PRT DECDIO 102 LONGWORD 4 COUNTER Direct I/O 11 PRT DECPAGEFAULTS 103 LONGWORD 4 COUNTER Pagefaults 11 PRT DECPAGEFAULT_IO 104 LONGWORD 4 COUNTER Pagefault 11 PRT DEC

I/OsCPU 105 LONGWORD 4 COUNTER CPU Time 11 PRT DEC

.01secCURRENT_PRIO 106 WORD 2 LEVEL Current Prio 6 PRT DECVIRTUAL_SIZE 107 LONGWORD 4 LEVEL Virtual Size 11 PRT DECWS_SIZE 108 LONGWORD 4 LEVEL Working Set 11 PRT DEC

SizWS_PRIVATE 109 LONGWORD 4 LEVEL Private WS 11 PRT DECWS_GLOBAL 110 LONGWORD 4 LEVEL Global WS 11 PRT DEC

Item Groups:

Item Group Name: RESOURCE_ITEMS

Item Name-----------------BIODIOPAGEFAULTSPAGEFAULT_IOCPUCURRENT_PRIOVIRTUAL_SIZEWS_SIZEWS_PRIVATEWS_GLOBAL

Class: ALL DEFAULT

Event Name: FIRST_EVENT

Record Type Item Name Position---------------- --------------- --------START EVENT BIO x

DIO x

23-AUG-1995 14:02 Facility Definition Information Page 2Full Report Oracle Trace V2.2


Record Type Item Name Position---------------- --------------- --------

PAGEFAULTS xPAGEFAULT_IO xCPU xCURRENT_PRIO xVIRTUAL_SIZE xWS_SIZE xWS_PRIVATE xWS_GLOBAL x

END EVENT BIO xDIO xPAGEFAULTS xPAGEFAULT_IO xCPU xCURRENT_PRIO xVIRTUAL_SIZE xWS_SIZE xWS_PRIVATE xWS_GLOBAL x

Event Name: SECOND_EVENT

Record Type Item Name Position---------------- --------------- --------START EVENT BIO x

DIO xPAGEFAULTS xPAGEFAULT_IO xCPU xCURRENT_PRIO xVIRTUAL_SIZE xWS_SIZE xWS_PRIVATE xWS_GLOBAL x

END EVENT BIO xDIO xPAGEFAULTS xPAGEFAULT_IO xCPU xCURRENT_PRIO xVIRTUAL_SIZE xWS_SIZE xWS_PRIVATE xWS_GLOBAL x

Creating the facility selection...%EPC-S-SELCRE, Selection EPC$IVP_SELECTION was created

Schedule a collection...%EPC-S-SCHED, Data collection EPC$IVP_COLLECTION is scheduled


Showing the EPC$IVP_COLLECTION collection was scheduled...23-AUG-1995 14:03 Scheduled Collections Page 1Brief Report Oracle Trace V2.2

Collections scheduled for node DATABS

Collection Name Selection Name Start End---------------- --------------- ----------------- -----------------

-> EPC$IVP EPC$IVP 23-AUG-1995 14:02 23-AUG-1995 14:12_COLLECTION _SELECTION

Running the IVP test program...

Canceling data collection...%EPC-S-SCHED_ABTNG, Data collection EPC$IVP_COLLECTION has been set toaborting

Showing the EPC$IVP_COLLECTION collection was canceled...23-AUG-1995 14:04 Scheduled Collections Page 1Brief Report Oracle Trace V2.2

%EPC-I-SCHED_NOMSGFND, No Collections Found

Showing any errors that may have occurred during collection...23-AUG-1995 14:04 Data Collection History Page 1Oracle Trace error history for cluster Oracle Trace V2.2

For database: EPC$HISTORY_DB

%EPC-I-HST_NOMSGFND, No History Messages Found

Delete the facility selection...%EPC-S-SELDEL_DELETED, Selection EPC$IVP_SELECTION was deleted

Delete the facility definition...%EPC-S-FACDEL_DELETED, Facility definition EPC$IVP_FAC V1.0 was deleted

Showing that the data collection file was created...

Directory SYS$COMMON:[SYSTEST.EPC]

EPC$DCF.DAT;2 320 23-AUG-1995 14:02:50.89EPC$DCF.DAT;1 320 1-JUL-1992 13:20:05.00

Total of 2 files, 640 blocks.

Formatting the data collection file...%EPC-I-FMT_RDB_CREATE, Creating database EPC$IVP_DIR:EPC$IVP_DB%EPC-S-FMT_RDB_SUCCESS, Successfully created database%EPC-I-FMT_DCF_BEGIN, Formatting data file EPC$IVP_DIR:EPC$DCF.DAT%EPC-S-FMT_DCF_SUCCESS, Successfully formatted data fileEPC$IVP_DIR:EPC$DCF.DAT%EPC-S-FMT_SUCCESS, Formatting successfully completed

Generating a Detail Report to epc$ivp_dir:epc$ivp_detail.txt...%EPC-S-RPCL_SUCCESS, Report successfully completed


Generating a Frequency Report...23-AUG-1995 14:05 IVP Frequency Report Page 1Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Event: FIRST_EVENT In Facility: EPC$IVP_FAC Version: V1.0

Time Period Occurrences

23-AUG-1995 14:03:00 4123-AUG-1995 14:04:00 9

23-AUG-1995 14:05 IVP Frequency Report Page 2Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Event: SECOND_EVENT In Facility: EPC$IVP_FAC Version: V1.0

Time Period Occurrences

23-AUG-1995 14:03:00 4023-AUG-1995 14:04:00 10

23-AUG-1995 14:05 Index Page 3Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Report Index

Facility Name Event Name Join item Page

EPC$IVP_FAC FIRST_EVENT 1EPC$IVP_FAC SECOND_EVENT 2%EPC-S-RPCL_SUCCESS, Report successfully completed

******** End of Frequency Report ********

Generating a Summary Report...23-AUG-1995 14:05 IVP Summary Report Page 1Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Event: FIRST_EVENT In Facility: EPC$IVP_FAC Version: V1.0

Elapsed Buffered CPU Time Curren Direct I/O PagefaultsI/O .01sec t Prio

Minimum 0.50 0 0 4 0 0Maximum 0.50 0 0 4 0 1Mean 0.500 0.00 0.000 4.00 0.00 0.02Std Dev 0.000 0.00 0.000 0.00 0.00 0.1495 Prct 0.501 0.00 0.000 4.00 0.00 0.29Total 25.04 0 0 200 0 1Count 50

Pagefault Virtual Global WS Private WS WorkingI/Os Size Set Siz


Minimum 0 12095 0 0 256Maximum 0 12095 0 0 256Mean 0.00 12095.00 0.00 0.00 256.00Std Dev 0.00 0.00 0.00 0.00 0.0095 Prct 0.00 12095.00 0.00 0.00 256.00Total 0 604750 0 0 12800Count 50

%EPC-I-RPQU_BAD_95, 95 Prct for events with counts under 1000 are less precise

23-AUG-1995 14:05 IVP Summary Report Page 2Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Event: SECOND_EVENT In Facility: EPC$IVP_FAC Version: V1.0

Elapsed Buffered CPU Time Curren Direct I/O PagefaultsI/O .01sec t Prio

Minimum 0.50 0 0 4 0 0Maximum 0.50 0 0 4 0 0Mean 0.500 0.00 0.000 4.00 0.00 0.00Std Dev 0.000 0.00 0.000 0.00 0.00 0.0095 Prct 0.501 0.00 0.000 4.00 0.00 0.00Total 25.04 0 0 200 0 0Count 50

Pagefault Virtual Global WS Private WS WorkingI/Os Size Set Siz

Minimum 0 12095 0 0 256Maximum 0 12095 0 0 256Mean 0.00 12095.00 0.00 0.00 256.00Std Dev 0.00 0.00 0.00 0.00 0.0095 Prct 0.00 12095.00 0.00 0.00 256.00Total 0 604750 0 0 12800Count 50

%EPC-I-RPQU_BAD_95, 95 Prct for events with counts under 1000 are less precise

23-AUG-1995 14:05 Index Page 3Selection: EPC$IVP_SELECTION Oracle Trace V2.2

Report Index

Facility Name Event Name Join item Page

EPC$IVP_FAC FIRST_EVENT 1EPC$IVP_FAC SECOND_EVENT 2%EPC-S-RPCL_SUCCESS, Report successfully completed

******** End of Summary Report ********


Deleting the formatted database...%DELETE-I-FILDEL, SYS$COMMON:[SYSTEST.EPC]EPC$IVP_DB.RDB;1 deleted(5092 blocks)%DELETE-I-FILDEL, SYS$COMMON:[SYSTEST.EPC]EPC$IVP_DB.SNP;1 deleted(4 blocks)%DELETE-I-TOTAL, 2 files deleted (5096 blocks)%DELETE-I-FILDEL, SYS$COMMON:[SYSTEST.EPC]EPC$DCF.DAT;2 deleted (320 blocks)%DELETE-I-FILDEL, SYS$COMMON:[SYSTEST.EPC]EPC$DCF.DAT;1 deleted (324 blocks)%DELETE-W-SEARCHFAIL, error searching forSYS$COMMON:[SYSTEST.EPC]EPC$IVP_DB.*;*-RMS-E-FNF, file not found%DELETE-I-TOTAL, 2 files deleted (644 blocks)

Executing Monitor IVP

%EPC-S-MONITOR, Monitor spawned successfully*****************************************

Oracle Trace Monitor completed successfully

*****************************************

*************************************************************************** IVP Completed Successfully ***************************************************************************

Installation of EPC V2.2 completed at 14:06

Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

Creating installation data file: VMI$ROOT:[SYSUPD]EPC022.VMI_DATA

VMSINSTAL procedure done at 14:06

ROYAL logged out at 23-AUG-1995 14:07:01.75


BFiles and Logical Names Installed on Your

System

The Oracle Trace installation procedure installs a number of files on yoursystem and defines some logical names. Section B.1 lists the files installed.Section B.2 lists the logical names that are added to the system logical nametable.

B.1 File NamesThe following list contains the names of all files created on your system whenOracle Trace is installed:

SYS$SYSROOT:[SYS$STARTUP]

EPC$STARTUP.COM

SYS$SYSROOT:[SYSHLP]

EPC012.RELEASE_NOTESEPC$CLI_HELP.HLBEPC$MSG.DOC

SYS$SYSROOT:[SYSLIB]

EPC$DEFINITIONS.ADAEPC$DEFINITIONS.BASEPC$DEFINITIONS.FOREPC$DEFINITIONS.HEPC$DEFINITIONS.LIBEPC$DEFINITIONS.MAREPC$DEFINITIONS.PASEPC$DEFINITIONS.PLIEPC$DEFINITIONS.R32EPC$FUNCSHR.EXEEPC$FUNCSHRP.EXE

Files and Logical Names Installed on Your System B–1

EPC$LSE_ENVIRONMENT.ENV

SYS$SYSROOT:[SYSMSG]

EPC$MSG.EXE

SYS$SYSROOT:[SYSEXE]

EPC$MAIN.EXEEPC$REGISTRAR.EXEEPC_MONITOR.EXEEPC_MON_EXECUTOR.EXEEPC_DATA_CHANNEL.EXE

SYS$SYSROOT:[SYSUPD]

EPC$DEINSTAL.COMEPC$VMSINSTAL_CALLBACK.COM

SYS$SYSROOT:[DECW$DEFAULTS.USER]

EPC_MONITOR.UIDEPC_MONITOR.DAT

EPC$EXAMPLES:

EPC$INSERT.COMACMSV31_FAC_DEF.EPC$DEFDBMSV41_FAC_DEF.EPC$DEFRDBV31_FAC_DEF.EPC$DEFRDBV31A_FAC_DEF.EPC$DEFALLIN1V24_FAC_DEF.EPC$DEFEPC$ATM-SAMPLE.EXEEPC$ATM-SAMPLE.CEPC$ATM-SAMPLE.COBEPC$ATM-SAMPLE.FOREPC$ATM-SAMPLE.PASEPC$ATM-SAMPLE.DATEPC$ATM-PASCAL.DATEPC$ATM-FAC-DEF.COMEPC$ATM-SAMPLE-EXTENDED.CEPC$ATM-FAC-DEF-EXTENDED.COMEPC_MON_THRESH.COMDEMO_DATA.DAT

B–2 Files and Logical Names Installed on Your System

SYS$SYSROOT:[SYSTEST]

EPC$IVP.COMEPC.DIR

SYS$SYSROOT:[SYSTEST.EPC]

EPC$IVP.EXEEPC$DCF.DATEPC$IVP_DB.RDBEPC$IVP_DB.SNPEPC$IVP_DETAIL.TXT

EPC$DATABASE_DIR:

EPC$ADMIN_DB.RDBEPC$ADMIN_DB_AREA_01.RDAEPC$ADMIN_DB_AREA_01.SNPEPC$ADMIN_DB_AREA_02.RDAEPC$ADMIN_DB_AREA_02.SNPEPC$ADMIN_DB_AREA_05.RDAEPC$ADMIN_DB_AREA_05.SNPEPC$ADMIN_DB_AREA_06.RDAEPC$ADMIN_DB_AREA_06.SNPEPC$ADMIN_DB_AREA_SYS.RDAEPC$ADMIN_DB_AREA_SYS.SNPEPC$HISTORY_DB.RDBEPC$HISTORY_DB.SNP

EPC$HOME_DIR:

EPC$REGISTRAR*.LOG (EPC$REGISTRAR log)*_EPC$REGISTRAR*.LOG (Old EPC$REGISTRAR logs)

Files and Logical Names Installed on Your System B–3

B.2 Logical NamesThe following logical names are entered into the system logical name tablewhen Oracle Trace is installed. These names are stored in the product’sstartup file. They are automatically entered into the system logical name tablewhenever the system reboots or whenever the software is invoked.

• EPC$ADMIN_DB

• EPC$DATABASE_DIR

• EPC$EXAMPLES

• EPC$HISTORY_DB

• EPC$HOME_DIR

• EPC$ROOT

B–4 Files and Logical Names Installed on Your System

Date post:	10-Mar-2018
Category:	Documents
Upload:	hacong
View:	214 times
Download:	2 times

OracleTrace InstallationGuide - s-and-b.ru · PDF fileIf you ﬁnd any errors or have any ......

Documents