Database Management Technology

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

DBAnalyzer Server Install (Unix)

  1. Log in as ingres.

  2. If you are installing a new version of DBAnalyzer over an existing installation stop all running DBAnalyzer processes before proceeding.  Use the dba_procs command to find the list of running DBAnalyzer processes.

    $DBA_SYSTEM/bin/dba_procs

    if any DBAnalyzer processes are running issue the following command:

    dba_stop all


    If you are upgrading from one of the 3.0/xx beta releases or DBAnalyzer 2.5 you will need to remove all of the following files

    $DBA_SYSTEM/alarms
    $DBA_SYSTEM/bin  
    $DBA_SYSTEM/log

    The format and/or location of several key files has changed therefore the old files MUST be removed prior to starting the installation.

    Proceed to step 4.

  3. If you are installing DBAnalyzer for the first time or building a new installation, create the DBAnalyzer installation directory.  The examples below assume DBAnalyzer is installed in /dba_tools/dbanalyzer.

    (C shell)

    mkdir  /dba_tools
    mkdir /dba_tools/dbanalyzer
    setenv DBA_SYSTEM  /dba_tools/dbanalyzer
    cd  $DBA_SYSTEM


    (Bourne shell)

    mkdir  /dba_tools/dbanalyzer
    DBA_SYSTEM=/dba_tools/dbanalyzer
    export DBA_SYSTEM
    cd $DBA_SYSTEM

  4. Create the DBAnalyzer definition database if it does not already exist, the recommended name for this database is dbanalyzer (this database MUST be owned by $ingres).

    createdb  -u\$ingres  dbanalyzer

  5. If your distribution media is CD-ROM mount the DBAnalyzer CD.  Unload the DBAnalyzer tar archive, this example assumes the tar archive is located in /cdrom/dba3/solaris/dba3.tar

    cd  $DBA_SYSTEM
    tar  xvf   /cdrom/dba3/solaris/dba3.tar

  6. Run the dba_build program to build the DBAnalyzer installation.


     bin/dba_build

    If you are installing DBAnalyzer for the first time you will be prompted to enter a license string, the string is shipped as a part of the DBAnalyzer package.

    Enter license string for node 'geneva'

     

    If you are installing over an existing DBAnalyzer installation you will have the opportunity to change the current license string.

    *********************************************************************
    Below is your current license information:
    String: 12345678 12345678 12345678
    Products: All
    Node Name: geneva
    CPU Model: 0
    Expiration: December 31, 2001
    *********************************************************************

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

     

    The build procedure verifies the that the installation has all the required files, sets the appropriate file protections and ownerships and creates the default set of DBAnalyzer configuration files.

    Verifying directory structure...

    Setting image ownership and protection...

    Creating symbolic links...

    Creating default startup files from templates...

     

    The next step is to define the name of DBAnalyzer definition database, this is the database created in step 2 above.

    *********************************************************************
    The DBAnalyzer definition database is used to register the IMA
    primitive tables and to materialize the DBAnalyzer PDB tables.
    The definition database must exist on the local node.
    *********************************************************************

    Enter the DBAnalyzer definition database name <dbanalyzer> :

     

    The build procedure will load the required DBAnalyzer catalogs, register the appropriate IMA tables, and update the internal table cache in the definition database.

    Loading dba_tables and dba_columns...
    Registering IMA tables...
    Updating database table cache...

     

    To monitor the current installation DBAnalyzer client consoles must supply an ACCESS password at connect time.  The build procedure allows you to define or change the ACCESS password for the installation.  If the ACCESS password is not defined any client will have the ability to monitor this installation.

    *********************************************************************
    In order to monitor the current installation each client must provide
    the ACCESS password. If the ACCESS password is not defined all 
    clients will have the ability to monitor the current installation.
    *********************************************************************

    The ACCESS password is not defined, define ACCESS password<N> :

    Enter ACCESS password: 
    Re-enter ACCESS password: 

    ACCESS password defined

    Some clients need the ability to start and stop DBAnalyzer servers and remove Ingres database server sessions.  To perform these operations the client must supply the CONTROL password.  The build procedure allows you to define or change the installation CONTROL password.  If the CONTROL password is not defined any client will be allowed to perform these operations.

    *********************************************************************
    To perform control functions, such as starting/stopping DBAnalyzer 
    components and removing Ingres sessions, the client must provide the 
    CONTROL password. If the CONTROL password is not defined all clients
    will be allowed to perform these functions.
    *********************************************************************

    The CONTROL password is not defined, define CONTROL password<N> :

    Enter CONTROL password: 
    Re-enter CONTROL password: 

    CONTROL password defined




    The DBanalyzer Console Server allows the current node to be monitored from remote consoles.  Starting the server allows remote consoles to monitor and control the DBAnalyzer environment on the current node.

    *********************************************************************
    The DBAnalyzer Console Server 'dba_cs' allows the local node and
    Ingres installation to be monitored by remote DBAnalyzer consoles.
    *********************************************************************

    Start the DBAnalyzer Console Server and default Sentinel now? <Y>

     

    To start the default configuration automatically at system startup perform the following steps.

    *********************************************************************
    To start a default DBAnalyzer configuration at system startup time add a
    script file to the /etc/rc3.d directory with the following command

    su ingres -c "/dba_tools/dbanalyzer/bin/dba_startup"

    The script file name should have the following form

    S<integer>dbanalyzer

    where <integer> is a number that is greater than the script used to
    start ingres.

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

     

    Customize Sentinel alarm notification by adding entries to $DBA_SYSTEM/alarms/recipients.dis (one email address per line).  Each e-mail address in the file will receive notification whenever an alarm is raised.
     


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