Oracle7 Enterprise Backup Utility Administrator's Guide Go to Product Documentation Library
Go to books for this product
Go to Contents for this book
Go to Index

Go to previous file in sequence Go to next file in sequence

Installing and Setting Up EBU

This chapter describes how to set up the Enterprise Backup Utility

Topics covered in this chapter are:

Installing and Setting Up EBU in a Target Database

Perform the following steps to install EBU and set up a EBU Catalog:

  1. Verify that the database names of the target databases (and catalog database if it already exists) are not "DEFAULT". The database name is specified in the initsid.ora file or one of its include files, or you can query the V$DATABASE view from each database.

Additional Information: Oracle7 Server Administrator's Guide for instructions on how to change the name of a target database, if necessary.

  1. Create a database in which to install the EBU Catalog user and schema (if one does not already exist).
  2. Verify that you can connect to the catalog database from the target database machine with a SQL*Net connect string. For example:


EBU 2.2 supports SQL*Net Version 2 only.

  1. As the oracle software owner, install EBU using the Oracle Installer. (See the CD-ROM insert that accompanies the product distribution for instructions on starting the Installer.)
  2. Set the EBU_HOME environment variable to the directory where EBU is installed, and update the PATH of all EBU users to include EBU_HOME/bin.
  3. Verify that the DMO from the media management vendor (libobk) is installed according to the media management vendor's instructions, and its location is included in the environment variable that sets the search path for shared libraries.


Proper installation of the DMO and specifying its location in the search path for shared libraries is essential for using EBU.

  1. Create a release 2.2 EBU Catalog. The method for doing this depends on whether you have a release 2.0 or 2.1 catalog, and whether you will continue to have target database running EBU release 2.0 or 2.1, after installing EBU 2.2 on some target databases.

    The different scenarios and procedures for creating the EBU Catalog are described beginning in the section "Setting Up the EBU Catalog".

  2. Optional: Create a user in the target database for performing EBU operations (See "Authorizing Target Database Backups". ).
  3. Create and run a register script to register the target database. (See Chapter 3, "Invoking EBU and Registering Target Databases".)

    Registration does the following:


If you enter incorrect information when EBU prompts for a connection string, EBU prompts you again for correct information, up to three times. You can abort connect operations with [Ctrl]-C (or SIGINT) on Unix systems.


Database Module for Oracle

EBU includes a version of the DMO that bypasses the media management software and writes directly to disk. This DMO is in the file EBU_HOME/lib/libobk.{a,so}.DISK (the exact filename varies slightly from platform to platform). On NT, the file is named ORASBT.DSK. It should only be used for testing purposes, such as trying to determine whether a problem originates from EBU or the media management software.

The libobk.DISK DMO is indicated in the log file by the following message:

BACKUP_DIR is not set!!

The following banner may also be written to the log file, indicating the use of the libobk.DISK file:

Tape Management Software: Release
Vendor API: Disk API (Oracle Internal Only) 

Additional Information:

"See also "Troubleshooting for EBU".


Authorizing Target Database Backups

Unless you intend to perform all EBU operations as INTERNAL, each target database must have a backup user. This is the Oracle user under which all Enterprise Backup Utility operations are performed. Creating the backup user and performing all backup operations with it ensures that the Enterprise Backup Utility has sufficient privileges to execute the necessary SQL commands on the target database.

If not using INTERNAL, you must create the target database backup user with the ebutool utility before registering a database in the EBU Catalog.

$ ebutool -cretrgtusr

The utility prompts you for the SYS user password and other necessary information for creating the backup user. If you want to change any information about the target database or backup user, you can run ebutool -cretrgtusr again.


After running -cretrgusr, you do not forget to run the register comand.



When you invoke ebu to register a database or update its configuration information, the Enterprise Backup Utility prompts you for the backup user/password and the connect alias to the target database. You can pre-empt these prompts by defining the environment variable EBU_DB_LOGIN in the startup files of EBU users.

The syntax for EBU_DB_LOGIN is:


If you define a user/password in EBU_DB_LOGIN, but no connect alias, the Enterprise Backup Utility defaults to the SQL*Net V2 Pipe driver.


If you enter incorrect information on EBU_DB_LOGIN, ebu aborts.



EBU requires INTERNAL, with the OS user being in the OSDBA group, or by a user with SYSDBA privileges. EBU attempts to connect to the database AS SYSDBA, unless the user is INTERNAL. You must grant the SYSDBA role to that user, or be in the OSDBA group. ebutool -cretrgtusr will perform the grant. When connecting, the backup user must then connect to the Server as SYSDBA or INTERNAL. For example:

SQL> CONNECT backup_user/password AS SYSDBA

Additional Information:

Chapter 1, "The Oracle7 Database Administrator", in the Oracle7 Server Administrator's Guide for more information on SYSDBA administrative privileges and how to grant them.


Setting Up the EBU Catalog

Figure 2-1, "EBU Catalog Installation Scenarios" illustrates the possible scenarios for creating a EBU Catalog, and outlines the appropriate procedure for each one. Each procedure is described in detail, beginning.

Figure 2-1 EBU Catalog Installation Scenarios

First-Time EBU Installation

EBU creates the EBU Catalog schema automatically, the first time it is invoked. Prior to invoking the utility, you must perform the following steps:

  1. Install EBU in the ORACLE_HOME of the target database.


(UNIX only) EBU must be installed on a one-per-oracle software owner, per machine basis. This means that if you have multiple Oracle7 Servers owned by the same UNIX account on a single machine, you only need to install EBU in one ORACLE_HOME. On NT there can only be one installation of EBU per machine.


  1. Install an Oracle7 instance and create a database to house the EBU Catalog.
  2. Configure a network connection and SQL*Net V2 alias for the catalog database that should be accessible from the target database.


The default database you can create with the Oracle Installer is adequate for the catalog database. The database name cannot be longer than eight characters on UNIX, four charactes on NT (Oracle Corporation recommends four characters or less).


All EBU Installations are Upgraded Together

If all EBU installations can be upgraded within a single time frame, use the following procedure:

  1. Install EBU release 2.2 on all target database machines.
  2. Verify that the existing, 2.0 or 2.1 EBU Catalog is running and accessible to all target databases.
  3. Execute the following command once to upgrade the catalog:
    $ ebu -upgrade  

Target Databases are Upgraded at Different Times

If you intend to operate EBU release 2.0 or 2.1 and release 2.2 at the same time, use the following procedure:

  1. Install EBU release 2.2 on the desired target database machines.
  2. Create a new Oracle7 database as the catalog database for the 2.2 EBU Catalog.
  3. Verify that the old and new catalog databases are accessible from the host where EBU release 2.2 is installed.
  4. Execute the following command once for each target database where you have installed EBU release 2.2:
    $ ebutool -migrate 

    The utility prompts for the following connect strings:

    The ebutool utility then creates the structures for the new catalog, copies job entries from the 2.0/2.1 catalog to the 2.2 catalog, and finally overwrites the catalog.ebu file in the EBU_HOME/admin directory to point to the new catalog database.


    If you enter incorrect information when EBU prompts for a connection string, EBU prompts you again for correct information, up to three times. You can abort connect operations with [Ctrl]-c.


Remaining target databases running EBU 2.0/2.1 can be upgraded by installing EBU 2.2 on the target database and running the ebutool -migrate command.


You must migrate the information from the 2.0/2.1 EBU Catalog before performing any backup jobs with EBU 2.2. If you perform a backup before migrating the catalog, EBU registers the target database as a new target and you lose the ability to use backups from release 2.0/2.1.


Enterprise Backup Utility Privileges

Backing up, restoring, and recovering a database requires a high level of Oracle server privileges. The privileges required by EBU and the reasons for those privileges are summarized in the following sections.

UNIX Execution Permission

The ebu executable assumes the privileges of the oracle software owner (setuid oracle) for the following reasons:

NT Execution Permissions

There are no special execution permission for EBU on the NT platform.

The Instance Manager

EBU starts the Instance Manager (the brd process) once (in Unix, once per oracle software owner) per host machine for the following reasons:

Target Database Privileges

The Oracle user used to connect to the target database must be granted SYSDBA privileges for the following reasons:

Go to previous file in sequence Go to next file in sequence
Prev Next
Copyright © 1997 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Go to books for this product
Go to Contents for this book
Go to Index