dba/m Database Manager 7.1 Installation and Operations Manual

dba/m Database Manager V7.1 Installation and Operations Manual

Release 7.1 May 2005

dba/m Database Manager V7.1 Installation and Operations Manual – 540155-001

Copyright Information Copyright © 1996 – 2005 Genus Software, Incorporated. All rights reserved. Trademark Acknowledgements

• Microsoft is a registered trademark of the Microsoft Corporation. • Windows is a trademark of Microsoft Corporation. Other products referred to in

this document are the trademarks of the respective manufacturers. Copying and Use Restrictions No part of this manual can be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Genus Software Inc.


PREFACE Welcome to dba/m Database Manager, a client-server product to manage NonStop SQL/MP databases on Hewlett-Packard Devlopment Company L. P. NonStop Systems. This manual provides procedures for installing and managing dba/m Database Manager on the server and client workstations. For Technical assistance, contact GCSC by calling 1-800-255-5010 Or by going to HP Support Web site http://www.support.HP.com.

Manual Part No. 540155-001.


CONTENTS

INTRODUCTION dba/m Database Manager is a tool for managing NonStop SQL/MP databases on HP NonStop Systems from client workstations. dba/m Database Manager can be used to perform the following: • Managing SQL objects such as tables, views, indexes, partitions, programs, and

catalogs at single or multiple nodes • Creating, analyzing, and modifying query plans • Controlling workloads by scheduling jobs • Monitoring disk space used by SQL objects Dba/m Database Manager uses the client-server architecture. User has to use TCP/IP to implement the communication between the client and the server.

How This Manual Is Organized The HP NonStop system administrator should use this manual to install and manage dba/m Database Manager on the NonStop System. The dba/m Database Manager administrator should use this manual to install or uninstall dba/m Database Manager, upgrade the dba/m Database Manager license, and add users or nodes on the client workstation. This manual is organized as follows: Chapter 1, Introduction. Defines conventions and abbreviations used in this manual. Chapter 2, Installation on the Server. Provides preinstallation and installation steps for installing dba/m Database Manager on the HP NonStop host. Chapter 3, Installation on the Client. Provides preinstallation and installation steps for installing dba/m Database Manager on the client.


Chapter 4, Client Operations. Contains procedures for the following client tasks: upgrading the dba/m Database Manager license, adding nodes and users, installing dba/m Database Manager on additional workstations, and removing dba/m Database Manager from a client. Chapter 5, Sever Operations. Contains the procedures for stopping and starting dba/m Database Manager on the server. Describes the subvolumes and files used by dba/m.

Conventions used in This Manual The following conventions are used in this manual: • Names of objects or menu items displayed in a screen are capitalized, for example,

the Cancel button. • Variable names are italicized and enclosed in brackets, for example, <volume>.

Substitute the appropriate name for your installation. • The command line prompt seen on the NonStop System is represented by the

character >. • Variables that are parts of names and addresses are italicized, for example, DBXPxx,

where xx is the variable. • Commands that must be typed are printed in boldface, for example, type a: setup. • Names of volumes, subvolumes, and files are in all capital letter, for example,

subvolume GENDB.

dba/m Database Manager V7.1 Installation and Operations Manual – 540155-001 2

GLOSSARY Abbreviations used in this manual are defined as follows: FTP - file transfer protocol FUP- file utility processor LAN- local area network MLAD – multi-LAN attachment device RSC – remote server call RSCCOM – an RSC utility QBE - query by example SQL – structured query language SVGA – super video graphics adapter TACL – Tandem advanced command language TCP/IP – transmission-control protocol/internet protocol TLAM – Tandem LAN access method TMF – transaction-monitoring facility


INSTALLATION ON THE SERVER dba/m Database Manager must be installed on the server before it is installed on any client. This chapter describes installation requirements, the installation procedure, and a validation procedure. You will need the following materials to install dba/m Database Manager on the server: • dba/m Database Manager server-installation software (provided on CD). The

installation CD contains the following: - dba/m Database Manager server software components: GCMDLOG command logging program GDBASQL SQL command-processing program GDBAT batch scheduling program GDBCH SQLCI control program GDBDR SQL command processing program GDBROWS query by example (QBE) interface program GDBSV client interface program GDBWK client connection program GDCOLL results-collecting program GDERR error-handling program GDMON disk-space monitoring program SMPLPRG sample dba/m Database Manager program USERP user profile creation program - Installation macro GENINSTL, a Tandem advanced command language(TACL)

macro - Utility files: DBGEN, GDBSTOP, FUPINSTL, GENINSTL, PROGCMPL,

README, SOFTDOC, REMGDB, UPGINSTL, USERP, LICP - Configuration-file templates: PWYCFG, COLDSTRT


Prepare the Server This section provides the prerequisites for dba/m Database Manager to be installed successfully on the server.

General requirements: • Group Id and UserID: Install the dba/m Database Manager software as

SUPER.<user>. This user must have the security string as “NNNO”. DO NOT USE SUPER.SUPER for the installation.

• Volume for dba/m Database Manager files: Assign a volume of dba/m Database

Manager files. Verify that there are no subvolumes with the following names: GENBAT, GENCAT, GENCOLL, GENTACL, GENDB, GENINSTL, GENOBY, GENOUT, GENPROG, GENPWY, and GENEDT.

• NonStop Kernel Operating System Software: Verify that the following software is

installed and running: ♦ Guardian operating system, Release G06.13 or higher

♦ NonStop SQL/MP database, release 2 or higher

♦ Pathway release ACJ or higher

♦ Transaction monitoring facility (TMF)

♦ TCP/IP Subsystem

Install dba/m Database Manager on the Server (NPV Version) Use IP Setup to install dba/m Database Manager Server components to the installation Volume on Nonstop System. Then follow the on-screen instructions. For more details regarding the IPSetup, please refer to “IPSetup User’s Guide”. If you already have dba/m installed on your server and if you would only like to upgrade the dba/m to latest version then go to UPGRADE dba/m section. This section describes the complete installation for NPV based versions. If you attempt to install dba/m when you already have, all previous dba/m data may be deleted.

Log on as Super.<user> onto the NonStop System.

Setup Installation Environment


1. Set the volume to <dba/m Database Manager installation vol.ZDBAM>: VOLUME $<vol>.ZDBAM

2. Load the GENINSTL macro:

LOAD/ KEEP 1/ GENINSTL

Execute the dba/m Database Manager Installation Macro The installation procedure uses sample values that might not be the same as the values you will use. The installation macro assumes that the node on which you are installing dba/m Database Manager is the default node. • Asks for confirmation that your user ID should be used for the installation. If the user

ID is not appropriate or it is not SUPER.<user>, exit the installation, log on with the correct user ID, and restart the installation macro.

• Verifies that the Guardian version is correct and that SQLCI2, TMF, and RSC are

running. If any of these checks fail, the macro displays the appropriate error message and exits the session.

• Displays prompt or requests confirmation of displayed information. If the default

value displayed by the macro is valid, you can press the Return key to accept the default value.

• Checks for the existence of all dba/m-related files, such as program files and pathway

configuration files, in the current subvolume. If the files are not found, the macro will prompt you to enter the <volume>.<subvolume> name where the dba/m Database Manager files are stored.

Perform the installation as follows. You can cancel the installation at any time by pressing any function key.

1. Execute the dba/m Database Manager installation macro:

INSTALL

2. The installation macro plays the prompts shown in Table 2-1. Explanations of the prompts and sample responses are provided.


Type a response or press carriage return <cr> to accept the default value shown in the prompt. To cancel the installation at any time, press any function key.

3. After you have answered all of the prompts listed in Table 2-1, the installation macro displays the parameters and asks you to confirm that the displayed values are correct.

• If any of the parameters are incorrect, select No. The installation macro displays

the prompts shown in Table 2-1 again. • If all of the parameters are correct, select Yes. The installation macro displays the

prompts shown in Table 2-2.


Table 2-1 Initial Installation-Macro Prompts.

PROMPT SAMPLE RESPONSE

> Enter SQL System Catalog Location (Default $system.SQL):

If the system catalog is not $SYSTEM.SQL, you must provide the system-catalog location

<cr>

>Enter Volume Name for SQLCI(Default <$system.system>):

<cr>

>Enter Volume Name for SQLCOMP(Default $system.system>):

<cr>

>Enter Volume Name for dba/m Database Manager (Default $<volume>):

All dba/m Database Manager related files will be stored in this volume Make Sure that the Volume you select is the Audited Volume.

<cr>

>Enter dba/m Database Manager Process Name for Gateway Server.(Maximum 4 characters including $.Default $DBM.)

<cr>

>Enter Maximum SQL Operation Cost (Default 500):

This value limits query execution. Dba/m Database Manager will warn the client user of this threshold value. If exceeded, the client user has the option to terminate or continue execution of the query.

200

>Enter dba/m License Key Serial no. : 30 days trial version can be known from HP support center by calling 1-800-322-8636 or [email protected]. If it is purchased copy then permanent license key is given by HP Order desk at the time of purchase.

4. The installation macro displays additional prompts, shown in Table 2-2. Explanations of the prompts and sample responses are provided.

Press carriage return to accept the default value shown in bold type. To cancel the installation at any time, press any function key.


mailto:[email protected]

Table 2-2. Final Installation-Macro Prompts.

PROMPT SAMPLE RESPONSE

>Enter IP address for NonStop System (Default:0.0.0.0) This entry is required only for native TCP/IP option and NOT for RSC option.

Enter IP address of your NSK server.

>Enter Base Socket Port Address(Default:3000) This entry is required only for native TCP/IP option and NOT for RSC option.

<cr>

>Enter Base Socket Port Address (Default: 3100) for Monitor Utility. This entry is required only for native TCP/IP option and NOT for RSC option

<cr>

>Enter dba/m Database Manager Pathway Name(Default $GDB): The pathway name must match PATHMON_NAME defined on the client.

<cr>

>Enter Home Terminal Name for dba/m Database Manager Pathway Server(Default $ZHOME): dba/m Database Manager requires that the home terminal must exist as an active terminal in a paused state. For ‘S’ Series Systems, specify Home Terminal as $ZHOME.

<cr>

>Enter dba/m Database Manager Pathmon’s Primary CPU(Default 1):

<cr>

>Enter dba/m Database Manager Pathmon’s Backup CPU(Default 0):

<cr>

>Enter CPU A for dba/m Database Manager Servers (Default 1): The CPU A number must be different from the CPU B number and the CPU C number must be different from the CPU D number. CPU C and D pairing can be the same as CPU A and B pairing.

<cr>

>Enter CPU B for dba/m Database Manager Servers(Default 0): <cr> >Enter CPU C for dba/m Database Manager Servers(Default 2): <cr> >Enter CPU D for dba/m Database Manager Servers(Default 3): <cr> >Enter Server Priority for dba/m Database Manager

Servers(Default 149) <cr>

>Enter Pathmon Process Priority for dba/m Database Manager Servers(Default 149)

<cr>


5. After you have responded to all of the prompts in Table 2-2, the installation macro displays all configuration parameters and asks you to confirm that the values displayed are correct.

• If any of the parameters are incorrect, select No. The macro displays all of the

prompts again, beginning with the prompts shown in Table 2-1. • If all of the parameters are correct, select Yes.

After you confirm that the parameters are correct (step 5), the installation macro • Copies the files from $volume. GENINSTL to the appropriate subvolumes. • Update the files with the values you entered during the installation. • Generates the dba/m Database Manager database (GENCAT). • Creates the dba/m Database Manager Enscribe files:

- Inserts a system-configuration record. ($SYSTEM.GENUS.CONFIG)

- Inserts a user-profile record. ($dbam^vol.GENDB.USERPROF) • Compiles the object code. • Starts the dba/m Database Manager pathway environment.


Verification of dba/m Database Manager Installation Macro The installation procedure writes the output from installation macros to the terminal and a set of output files stored in the GENOUT subvolume of the volume on which dba/m Database Manager is installed. Check these outputs for errors and warnings. If there are any errors or warnings, call Dba/m Database Manager Support before using dba/m. Output File Contents Expected Errors ODBGEN SQLCI output for creation of dba/m Database

Manager tables and index Drop table error

OGCMDLOG SQLCOMP output for compilation of GCMDLOG None OGDBSQL SQLCOMP output for compilation of GDBSQL None OGDBAT SQLCOMP output for compilation of GDBAT None OGDBDR SQLCOMP output for compilation of GDBDR None OGDBROWS SQLCOMP output for compilation of GDBROWS None OGDCOLL SQLCOMP output for compilation of GDCOLL None OPWYCFG PATHMON cold start output None OSMPLPRG SQLCOMP output for compilation of GSMPLPRG None

Install dba/m Database Manager on the Server (SUT Version) This section describes the complete installation for SUT based versions. If you attempt to install dba/m when you already have, all previous dba/m data may be deleted.

Log on as Super.<user> onto the NonStop System.

Setup Installation Environment 3. Set the volume to <dba/m Database Manager installation vol.ZDBAM>:

VOLUME $<vol>.ZDBAM 4. Load the GENINSTL macro:

LOAD/ KEEP 1/ GENINSTL For details regarding Execution and Verification of Installation Macro, please refer to Execute the dba/m Database Manager Installation Macro and Verification of dba/m Database Manager Installation Macro Sections of Install dba/m Database Manager (NPV Version).


Install dba/m Database Manager on the Server (IPM Version) To Install NonStop dba/m Database Manager IPM on server, follow the following steps

• Use IP setup to install dba/m Database Manager IPM server components to the installation volume on NonStop system. For details regarding IP setup please refer to IPSET UP User’s Guide.

• Logon to the NonStop system as a super group user.

• Setup IPM Installation environment a> Change current volume and sub volume to $<vol>.ZDBAM

> VOLUME $<vol>. ZDBAM b> Load the IPM_INSTALL macro:

> LOAD/ KEEP 1/GENINSTL

• Execute the IPM__INSTALL macro: IPM_INSTALL

The IPM_INSTALL macro finds out existing installed node name, and dba/m volume name from $SYSTEM.GENUS.CONFIG . It does the various checks before IPM_INSTALL starts. If the user ID is not appropriate or does not belong to the super group the installation exists. An Error message is displayed, instructing the user to log on using correct Super Group user ID. Verifies that the Guardian Version is correct and that SQLCI2, TMF, and RSC are running. If any of these checks fail, then the installation macro displays the appropriate error message and exits. Checks for the existence of all dba/m IPM related files, such as program files and IPM installation macro, in the current sub volume. If the files are not found, the macro will prompt you to enter the sub volume name where the NonStop dba/m IPM files are stored.

• If the above checks pass then macro: Copies the program files from $<volume>.ZDBAM to the appropriate subvolume. SQL Compiles the Object code Starts the dba/m Database Manager Pathway Environment.

• Verification of the dba/m Database Manager Macro:

The upgrade procedure writes the output from installation macros to the terminal and a set of output files stored $<vol>.GENOUT Where <vol> is the volume on which NonStop dba/m IPM is installed.


Check the outputs mentioned above for errors and warnings. If there are any errors or warnings, call NonStop Dba/m Database Manager Support before using dba/m.

Start of DBA/M At the end of installation, dba/m Database Manager will be started automatically. Verify correct installation and startup using the procedures described in this section.


Verify Pathmon To verify that dba/m Database Manager Pathmon was correctly started, type the following command at the TACL prompt: To verify that dba/m Database Manager Pathmon was correctly started, type the following command at the TACL prompt:

PATHCOM $GDB; STATUS SERVER * The status of the dba/m Database Manager processes will be displayed, for example

SERVER #RUNNING ERROR INFO ALARMSV 1 CMNDS 1 DBAM 0 GDBAT 1 GDBPR 1 GDBWK 1 GDCOLL 0 GDERR 1 GDMON 1


Verify All Tables Use SQLCI to verify that the following tables have been created in $DBAM^VOL.gendb:

FILENAME DESCRIPTIONS BATCH Batch data CMDHIST Command data from batch EXPDETL Explain-operation detail EXPSTEP Explain-operation steps data EXPSTM1 Index on the EXPSTMT table EXPSTMT Explain SQL statement data EXPVERS Explain-version information LOGON Logon information table MONOBJ Monitored Object data MONREC Statistics data of Monitored Object PROGCAT Program-catalog data PROGDEF Program-define data USERBAT User batch-number data QUEJOB Queued Jobs data

Reinstall dba/m If the installation fails for any reason, you must do the following steps prior to re-installing dba/m.

• On TACL prompt:

• VOLUME $vol.GENOBY ($vol is the volume on which dba/m Database Manager was installed)

• OBEY GDBSTOP

• Wait for all the processes to terminate.

• VOLUME $vol1.ZHOME ($vol1 is the volume on which dba/m Database

Manager Server components files have been copied by IP Setup)


• RUN REMGDB $vol ($vol is the volume on which dba/m Database Manager was installed)

Upgrade dba/m Upgrading NonStop dba/m Database Manager will only update the server objects and dba/m database without deleting the current data. To Upgrade NonStop dba/m Database Manager on server, follow the following steps

• Use IP setup to install dba/m Database Manager IPM server components to the installation volume on NonStop system. For details regarding IP setup please refer to IPSET UP User’s Guide.

• Logon to the NonStop system as a super group user.

• Setup IPM Installation environment c> Change current volume and sub volume to $<vol>.ZDBAM

> VOLUME $<vol>. ZDBAM d> Load the UPGINSTL macro:

> LOAD/ KEEP 1/UPGINSTL

• Execute the UPGINSTL macro: UPGRADE

The UPGRADE macro finds out existing installed node name, and dba/m volume name from $SYSTEM.GENUS.CONFIG . It does the various checks before UPGRADE starts. If the user ID is not appropriate or does not belong to the super group the installation exists. An Error message is displayed, instructing the user to log on using correct Super Group user ID. Verifies that the Guardian Version is correct and that SQLCI2, TMF, and RSC are running. If any of these checks fail, then the installation macro displays the appropriate error message and exits. Checks for the existence of all dba/m IPM related files, such as program files and IPM installation macro, in the current sub volume. If the files are not found, the macro will prompt you to enter the sub volume name where the NonStop dba/m IPM files are stored. Verifies that the NonStop SQL/MP Version is 350 or later.

• If the above checks pass then macro: Copies the program files from $<volume>.ZDBAM to the appropriate subvolume. SQL Compiles the Object code Starts the dba/m Database Manager Pathway Environment.


• Verification of the dba/m Database Manager Macro:

The upgrade procedure writes the output from installation macros to the terminal and a set of output files stored $<vol>.GENOUT Where <vol> is the volume on which NonStop dba/m IPM is installed.

Check the outputs mentioned above for errors and warnings. If there are any errors or warnings, call NonStop Dba/m Database Manager Support before using dba/m.


INSTALLATION ON THE CLIENT If the client does not have networking capability, you must install the networking hardware, drivers, and networking software before you can install dba/m. After you have installed the networking hardware and software, return to this chapter to install dba/m Database Manager on the client. Installing dba/m Database Manager consists of preparing the client, installing dba/m Database Manager software, then verifying that the installation was successful.


Prepare the Client

General Requirements • Installation License Number: This number is located on all of the dba/m

Database Manager diskettes. • Native (non-RSC) TCP/IP Option: If native TCP/IP option is used for

communication between the workstation and NonStop System, get the TCP/IP address and port number for NonStop System. This address must be the same address and port number used in the installation of the server.

• Super video-graphics adapter (SVGA) card: This card is installed and meets

the following requirements: ♦ 1024 x 768 display mode ♦ 256 colors ♦ Small-font support

• MS-DOS Version: Version 5.0 or higher • Windows Version: Windows 98 or higher • Random-access memory (RAM): 8 MB or more • Disk Space: 50 MB or more for dba/m


Install dba/m Database Manager (SPR & New Product Version) Perform the following steps to install dba/m. 1) Use IP Setup to start the installation on the client this will invoke DBAM Database

Manager client installation process. Then follow the on-screen instructions. For more details regarding the IPSetup, please refer to “IPSetup User’s Guide”. You will be asked the following information during the installation process. • Dba/m Database Manager license number • Your name • Company name • Destination path for dba/m Database Manager software and files • For native TCP/IP option, the TCP/IP address of NonStop System and the

base port number and alarm port number.

2) When a pop-up window appears notifying you that the installation is complete, click

the OK button to exit to Program Manager. The installation has created a new program group for dba/m.

3) Remove the dba/m Database Manager CD from the CD drive.

Install dba/m Database Manager (SUT Version) 1) FTP 'DBAMWS' self extracting zip file from <$vol>. ZDBAM to PC in binary mode. 2) Extract (Unzip) DBAMWS file into temporary folder. 3) Execute Setup.exe to start installation. 4) You will be asked the following information during the installation process.

• Dba/m Database Manager license number (Temporary license Key # 192010100945)

• Your name • Company name • Destination path for dba/m Database Manager software and files • For native TCP/IP option, the TCP/IP address of NonStop System and the

base port number and alarm port number.


5) When a pop-up window appears notifying you that the installation is complete, click the OK button to exit to Program Manager. The installation has created a new program group for dba/m.

Validate the Installation Verify that dba/m Database Manager was installed successfully. Perform the following steps: 1. In the dba/m Database Manager program group, double click on the dba/m Database

Manager icon. The Logon screen appears:

2. In the User ID field, type the user ID (SUPER.<user>) that was used during the server installation. Then press the tab key to move to the Password field.

3. Enter the user password. The password is not displayed.


4. Click on the OK button to establish a dba/m Database Manager session. The first time you establish a session, dba/m Database Manager downloads information about the database you are connecting to. A dialog box is displayed indicating the progress of the download, for example

The amount of time required to download the information depends on how many database objects must be downloaded. When the download is complete, the dialog box disappears and you can begin using dba/m.


CLIENT OPERATIONS Client management includes the following tasks:

• Upgrading the dba/m Database Manager license • Adding nodes in a multinode environment • Adding dba/m Database Manager users • Installing dba/m Database Manager on additional clients • Removing dba/m Database Manager from clients

This chapter provides the procedures to perform these functions.

Upgrading the License Refer to the HP Computer license agreement for a definition of the types of licenses available: trial, single, node, and corporate. You can upgrade the dba/m Database Manager license as follows:

If your license is currently…. Then you can upgrade to… Trial Permanent license for 1 Node to n

Node.

Permanent License for n Node Permanent License for n + 1 Node to m Node. (where m is the physical limit on no. of nodes on Expand network.)

To upgrade the dba/m Database Manager license, contact HP at 1-800- 322-8636 or send E-mail to [email protected].


mailto:[email protected]

Adding Nodes Refer to “dba/m Database Manager V7.1 User’s Guide” Chapter 4 on Managing dba/m Database Manager Profile to add and delete nodes.

Adding or Upgrading User Profiles Refer to “dba/m Database Manager User’s Guide” Chapter 4 on Managing User Profile to add and delete nodes.

Installing dba/m Database Manager on Other Clients Install dba/m Database Manager on other clients using the procedures in Chapter 3.


Removing dba/m Database Manager From a Client Remove dba/m Database Manager from a client if you need to move the software to another client or if the address or class name of the client is changed on the server. In the second case, you must reinstall dba/m Database Manager using the new address information provided by the NonStop System administrator. To remove dba/m Database Manager from a client, go to Programs. Then to DBAM Database Manager and click on Uninstall.


SERVER OPERATIONS This chapter provides the following:

• Procedures to start and stop dba/m Database Manager on the server • Descriptions of the sub volumes and files used by dba/m.

Stopping dba/m Perform the following steps to stop execution of dba/m: 1. Logoff from all dba/m Database Manager workstations. 2. Log onto the server as SUPER.<user>. (Do not use any other logon id) 3. Enter the following commands at the TACL prompt:

volume GENOBY obey GDBSTOP

4. Verify that all servers and child processes are stopped. (In some cases some servers or processes might still be running.) Use the STOP command to stop any remaining dba/m Database Manager servers.

Starting dba/m When dba/m Database Manager is installed, it is started by the installation macro. If dba/m Database Manager is stopped for any reason, it must be restarted using the procedure in this section. HP Computer recommends that the startup procedure provided in this section be included in the NonStop System startup script so that dba/m Database Manager will start automatically if the NonStop System is shut down and then restarted. Perform the following steps to start dba/m Database Manager on the server: 1. Log onto the server as SUPER.<user>. (Do not use any other logon id) 2. At the TACL prompt, type the following:

Volume GENOBY Obey COLDSTRT

Upon completion of the cold start, all dba/m Database Manager servers will begin running.


Licensing dba/m Database Manager to Manually Update Statistics If you must update table statistics manually to simulate production statistics in development nodes, you must license the GDBASQL process. You can FUP-license and FUP revoke the process using the following commands:

FUP LICENSE GENPROG.GDBASQL FUP REVOKE GENPROG.GABASQL

You must log onto the NonStop System as SUPER.SUPER in order to license and revoke the process.

Updating dba/m Database Manager Table Statistics HP Computer recommends that you periodically run an update statistics operation on all dba/m Database Manager tables. Table 5-1 in the next section provides the names of the dba/m Database Manager tables.

Managing dba/m Database Manager Subvolumes and Files dba/m Database Manager uses the following subvolumes in the installation volume and GENUS subvolumes in $SYSTEM: • $SYSTEM.GENUS. Contains dba/m Database Manager configuration information

shown in one file named CONFIG. • GENBAT. Contains the edit files for every batch. The edit files contain the

SQLCI/IN <SQLEDT file> or SQLCOMP/IN commands generated by the GSQLBAT process, depending on the type of batch. The edit-file name is the same as the batch number assigned on the client when the batch is created.


• GENCOLL. Contains edit-type files, which have the output from SQLCI or SQLCOMP, depending on the type of batch. The contents of the files are displayed on the Results screen. The edit-file name is the same as the batch number.

• GENCAT. Contains the SQL catalog tables for the GENCAT catalog. • GENDB. Contains the files listed in Table 5-1. • GENEDT. Contains the edit file for SQLCI-type batches. The edit files contain

SQLDDL commands generated by the GSQLBAT process. The edit-file name is the same as the batch number.

• GENOBY. Contains the files listed in Table 5-2. The files are generated by the

TACL macro after successful installation. • GENOUT. Contains the files listed in Table 5-3. The files are generated by the

TACL macro during installation. • GENPROG. Contains the files listed in Table 5-4. The object files are generated by

the TACL macro after successful installation. • GENPWY. Contains the file PATHCTL, which is generated the first time the

pathway environment is started.


Table 5-1. GENDB Files.

FILE NAME DESCRIPTION TYPE BATCH Batch data SQL table BATCH1 Index on the Batch table SQL index CMDHIS1 Index on CMDHIST table SQL index CMDHIST Command data from batch SQL table DEPBAT Dependent batch data(not currently used) SQL table ENVDEF Environment default data(not currently used) SQL table ERRLOG Error log file Enscribe file ERRLOG0 Alternate index on ERRLOG file Enscribe index ERRMSG Error message data Enscribe file EXPDETL Explain-operation detail data SQL table EXPSTEP Explain-operation steps data SQL table EXPSTM1 Index on the EXPSTMT SQL index EXPSTMT Explain-SQL statement data SQL table EXPVER1 Index on the EXPVERS table SQL index EXPVERS Explain-version information SQL table HISTSEQ Sequence number file Enscribe file LICENSE License Info file Enscribe File LOGON Logon information table SQL table LOGON1 Index on the LOGON table SQL index LOGTBL Log for every statement in batch SQL table MONREC Disk-space monitor data SQL table PROGCAT Program-catalog data SQL table PROGDEF Program-define data SQL table USERPROF User-profile file Enscribe file USERBAT User & batch-number data SQL table


Table 5-2 GENOBY Files.

FILE NAME DESCRIPTION COLDSTRT Pathway cold start DBGEN GENCAT catalog and database generation

FUPINSTL FUP in file to create Enscribe files GDBSTOP Dba/m Database Manager stop PROGCMPL Obey file used to SQLCOMP the programs PWYCFG Pathway configuration file

Table 5-3 GENOUT Files.

FILE NAME DESCRIPTION ODBGEN SQLCI output during installation OGDBASQL SQLCOMP output during installation

OCMDLOG SQLCOMP output during installation OGDBAT SQLCOMP output during installation OGDBDR SQLCOMP output during installation OGDCOLL SQLCOMP output during installation OPWYCFG PATHCOM output during startup OSMPLPRG SQLCOMP output during installation


Table 5-4 GENPROG Object Files.

FILE NAME DESCRIPTION

ALARMSV Object file for Alarm Notifier process GDBASQL Object file for SQL command process GDBAT Object file for batch monitor process

GDBCH SQLCI interface process GDBDR Object file for SQL command process GDBPR Object file for Auto Partitioning process GDBROWS Object file for browse process GDBSV Object file for gateway-server process GDBWK Object file for client logon process GDCOLL Object file for collector process GDERR Object file for error process GDMON Object file for disk space monitor process USERP Object file for creating the installer’s user profile.


dba/m Database Manager 7.1 Installation and Operations Manual

Documents

Transcript of dba/m Database Manager 7.1 Installation and Operations Manual