dba/m Database Manager V7.1 Installation and Operations Manual Release 7.1 May 2005 dba/m Database Manager V7.
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.
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. dba/m Database Manager V7.
CONTENTS INTRODUCTION dba/m Database Manager is a tool for managing NonStop SQL/MP databases on HP NonStop Systems from client workstations.
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.
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 dba/m Database Manage
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).
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.. 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.
1. Set the volume to : ¾ VOLUME $.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.
Type a response or press carriage return 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.
Table 2-1 Initial Installation-Macro Prompts. PROMPT > Enter SQL System Catalog Location (Default $system.SQL): SAMPLE RESPONSE If the system catalog is not $SYSTEM.SQL, you must provide the system-catalog location >Enter Volume Name for SQLCI(Default <$system.system>): >Enter Volume Name for SQLCOMP(Default $system.
Table 2-2. Final Installation-Macro Prompts. PROMPT >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 Base Socket Port Address(Default:3000) This entry is required only for native TCP/IP option and NOT for RSC option. >Enter Base Socket Port Address (Default: 3100) for Monitor Utility.
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.
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.
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 $.ZDBAM > VOLUME $.
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. dba/m Database Manager V7.
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 ALARMSV CMNDS DBAM GDBAT GDBPR GDBWK GDCOLL GDERR GDMON #RUNNING ERROR INFO 1 1 0 1 1 1 0 1 1 dba/m Database Manager V7.
Verify All Tables Use SQLCI to verify that the following tables have been created in $DBAM^VOL.
• 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.
• 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 $.GENOUT Where 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. dba/m Database Manager V7.
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. dba/m Database Manager V7.
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.
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.
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.
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. dba/m Database Manager V7.
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.
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. dba/m Database Manager V7.
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. dba/m Database Manager V7.
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.. (Do not use any other logon id) 3. Enter the following commands at the TACL prompt: ¾ volume GENOBY ¾ obey GDBSTOP 4.
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.
• 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.
Table 5-1. GENDB Files.
Table 5-2 GENOBY Files. FILE NAME COLDSTRT DESCRIPTION Pathway cold start DBGEN GENCAT catalog and database generation FUPINSTL GDBSTOP PROGCMPL PWYCFG FUP in file to create Enscribe files Dba/m Database Manager stop Obey file used to SQLCOMP the programs Pathway configuration file Table 5-3 GENOUT Files.
Table 5-4 GENPROG Object Files.
