Database Management Technology

Architecture | Monitor | Sentinel | Query | Testimonials | Documentation | Downloads
Courses | On-Site Courses | Course Schedule | Testimonials |
DBAnalyzer | JVM
Contact Info

DBAnalyzer2 Server Install (Unix)

Single-node Installation

If you are installing DBAnalyzer on a single network node, then you may use the following installation procedure. To install DBAnalyzer on multiple network nodes, follow the installation procedure described in the Multi-node Installation section.

DBAnalyzer need not be installed in any particular directory. DMT recommends that you not install DBAnalyzer in any of the INGRES system directories, as DBAnalyzer files may be deleted when new versions of INGRES are installed.

DISK SPACE

DBAnalyzer system files require approximately 50 MB of disk space to install, this does not include the space required for the definition and performance databases, log files, and raw collected data.

The DBAnalyzer distribution is shipped as a single tar archive which must be unloaded into the DBAnalyzer system directory, DBA_SYSTEM.

  1. Log in as root.

    su - root

  2. Make sure II_SYSTEM is defined and points to the correct Ingres installation

    echo $II_SYSTEM
    $II_SYSTEM/ingres/bin/ingprenv |grep II_INSTALLATION

  3. Create the DBAnalyzer distribution directory. The following example assumes there is a directory dba_tools and DBAnalyzer will be installed in that director tree.

    cd /dba_tools
    mkdir dbanalyzer
    cd dbanalyzer

  4. Unload the distribution archive.

    umask 0
    tar -xvf dba2_4_02.tar

  5. Change the file ownership of the distribution tree. DMT recommends that the DBAanlyzer installation be owned by ingres.

    chown -R ingres ../dbanalyzer/*

  6. Define environment variables and place the DBAnalyzer root directory in your search path. The following steps must be performed prior to running DBAnalyzer and should be added to the shell startup file of all DBAnalyzer users. The following example assumes that you installed DBAnalyzer in the /dba_tools/dbanalyzer directory, substitute the appropriate directory name for your environment.

    C shell:
    setenv DBA_SYSTEM /dba_tools/dbanalyzer
    set path=($DBA_SYSTEM/bin $path)
    rehash

    Bourne shell:
    DBA_SYSTEM=/dba_tools/dbanalyzer
    export DBA_SYSTEM
    PATH=$DBA_SYSTEM/bin:$PATH
    export PATH

  7. Run the DBAnalyzer installation program dba_build. This will prompt you for the license string, verify that all required files have been installed, and set the appropriate file protections. DBAnalyzer tools Monitor, Sentinel, Collector, and Query are used to monitor the state of Ingres, the operating system, and running processes. To collect these statistics each tool must be owned by root and have the set UID bit set in the protection mask, dba_build will set the correct protection bits. All DBAnalyzer tools passively monitor, they will not alter Ingres, the operating system, or running processes in any way.

    dba_build

    Installing DBAnalyzer 2.4/02 (Solaris)

    Enter license string for node ‘geneva’ or press RETURN for ‘client only’ :

    Enter the supplied license string and verify that the license information is correct.

    ***************************************************************
    Below is your current license information:
         String: 01234567 89101112 13141516
         Products: All
         Node Name: geneva
         CPU Model: 0
         Expiration: March 01, 1999
    ***************************************************************

    Would you like to change your license string? <N>:

    Since you have selected to perform a single node installation answer single to the following question.


    *******************************************************************
    DBAnalyzer can be configured in one of two modes, single node
    standalone of multi-node.

    SINGLE NODE STANDALONE:
            The current node will not monitor or be monitored by other
            nodes in the installation.

            MULTI_NODE:
            The current node can monitor and be monitored by other nodes
            in the installation.
    *******************************************************************
    DBAnalyzer installation mode [single|multi]? <single>


    dba_build will verify that all of the required directories and files are in place, set the appropriate file protections, and create the required symbolic links.

    Verifying directory structure...

    Setting image ownership and protection...

    Creating symbolic links...


    System startup, shutdown and user login scripts need to be modified to use DBAnalyzer.


    *******************************************************************
    To shut down dbanalyzer execute

         $DBA_SYSTEM/bin/dba_stop all

    This should also be added to you shutdown script and should execute
    prior to shutting down INGRES.

    Each DBAnalyzer user must define the DBA_SYSTEM environment variable
    and place $DBA_SYSTEM/bin in their search path:

    C shell: setenv DBA_SYSTEM /dba_tools/dbanalyzer
             set path=($DBA_SYSTEM/bin $path)

    Bourne shell: DBA_SYSTEM=/dba_tools/dbanalyzer
                  export DBA_SYSTEM
                  PATH=$DBA_SYSTEM/bin:$PATH
                  export PATH
    ********************************************************************


    Note
    The following steps only need to be performed if you will be using DBACollector and DBASentinel. If you will not be using these tools, then the installation is complete.

  8. Create the definition database. The definition database contains information that is used to create and monitor Collector and Sentinel processes. Create this database with the following operating system commands.

    $ createdb [options] dbanalyzer
    $ dbasetup

    options may be any valid flags for the INGRES createdb utility. dbasetup is a utility for defining information about the DBAnalyzer environment. Choose the "Create DBA Tables" option and follow the prompts. Because the definition database is vital to the proper operation of DBAnalyzer, it is recommended that this database be checkpointed regularly.

  9. Create the performance database(s). If you will load collected data into an INGRES database for analysis, then create the tables into which the collected data will be loaded. You may create as many performance databases as you like (e.g., one for each INGRES installation, database, application, etc.). A performance database may reside on the local node or on a remote node which is accessible via INGRES/Net. Select a node which has sufficient CPU and disk capacity for storing and analyzing large amounts of data. Use the following commands to create the performance database(s).

    $ createdb [options] pdb_name
    $ dbasetup

    pdb_name is the name of the database (if you are only creating one, "dbapdb" is a good choice). Choose the "Create DBA Tables" option in dbasetup and enter the name of the database. After the tables are created, you may enter another database name. Performance databases do not need to be checkpointed or journalled because they can be recreated at any time by reloading collected performance data.

  10. Define the output devices for Collector reports and graphs. If you will use DBAnalyzer reports and graphs to analyze collected data, then define the devices on which their output may be displayed or printed. Choose the "Define Devices" option of the dbasetup utility and follow the directions given in the Define Output Devices section.


About DMT | Contact Us | ©2004 Database Management Technology, Inc. All rights reserved.