Obt5010 Install Guide

SmartDBA Recovery Management: SQL-BackTrack for Oracle
Installation Guide
Supporting
SmartDBA Recovery Management for Oracle 5.0.10 SQL-BackTrack for Oracle 5.0.10
October 15, 2004
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC Software, Inc. 2101 CityWest Blvd. Houston TX 77042-2827 713 918 8800 or 800 841 2031 713 918 8000
Outside United States and Canada

Telephone Fax (01) 713 918 8800 (01) 713 918 8000
Telephone Fax
Copyright 2004 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM is a registered trademark of International Business Machines Corporation. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can
s s s s s s s
read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at http://www.bmc.com/support_home.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:
s
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
s s s
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide
Contents
About This Book 11 Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Chapter 1 Preparing to Install 13 14 14 14 14 15 16 18 19 19 21 23 24 24 25 26 27 27 27 28 31 32 32 33 35 35 36 42 44 45 45 48 50
5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SmartDBA Recovery Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Task Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing on a Single Unix Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing in a RAC Environment (Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing in a Failover Environment (Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing on a Windows Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems and Oracle Software . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Module Software Requirements. . . . . . . . . . . . . . . . . . Supported Backup Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an Earlier Version of SQL-BackTrack for Oracle . . . . . . . . . . . . Installing Multiple Versions of SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Licensing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Installing SQL-BackTrack for Oracle
Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SQL-BackTrack for Oracle on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the Patch Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Installation of SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Unix . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Windows . . . . . . . . . . . . . . . . . . . . Procedures for Uninstalling SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Uninstalling SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Uninstalling SQL-BackTrack for Oracle on Windows . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 3 Performing Post-Installation Tasks 57
SQL-BackTrack for Oracle Post-Installation Tasks on Unix. . . . . . . . . . . . . . . . . . . . . . 57 Setting Environment Variables for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Updating License Information for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Setting Up Licensing Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Setting Port Numbers for dtlicense and dtoarchmon . . . . . . . . . . . . . . . . . . . . . . . . 65 Running the SQL-BackTrack for Oracle Configuration Script . . . . . . . . . . . . . . . . 66 SQL-BackTrack for Oracle Post-Installation Tasks on Windows . . . . . . . . . . . . . . . . . 67 Setting Environment Variables for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Adding or Updating a License Key on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Setting Up Operating System Authentication for Windows . . . . . . . . . . . . . . . . . . 69 Chapter 4 Configuring RAC Environments for SQL-BackTrack for Oracle 71
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 SQL-BackTrack for Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Oracle Database Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Setting the Time Zone for RAC Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Storage Manager Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 5 Configuring Failover Environments for SQL-BackTrack 75
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 SQL-BackTrack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Specifying Node Information for Failover Environments . . . . . . . . . . . . . . . . . . . . 77 Starting Services during a Node Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Oracle Database Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Storage Manager Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Index Glossary 81 85
Figures
SQL-BackTrack for Oracle Installation Task Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle on a Single Unix Computer . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle in a RAC Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle in a Failover Environment . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Unix . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Windows . . . . . . . . . . . . . . . . . . . . 17 19 21 22 23 46 48
Figures
Tables
SmartDBA Recovery Management components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Authorization Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Catalog Space Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . Procedures for Determining Computer IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Unix ($DTBASE) . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Unix ($DT_OBACKTRACK_HOME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Windows (%DTBASE%) . . . . . . . SQL-BackTrack for Oracle Directory Structure on Windows (%DT_OBACKTRACK_HOME%) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Environment Variables for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Environment Variables for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Environment Variables for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 24 26 33 46 47 49 49 59 59 68
Tables
10
About This Book

This book contains detailed information about installing the SQL-BackTrack for Oracle product. It describes how to install and license your SQL-BackTrack product on the supported Unix and Windows platforms. It also describes post-installation and configuration tasks that you need to complete before running SQL-BackTrack. The book is intended for system administrators and database administrators (DBAs) who are responsible for Oracle databases.
NOTE
This book assumes that you are familiar with Oracle system administration and your operating system commands and privileges.
All SQL-BackTrack books are provided as online books. Your shipment also includes a printed installation book. Visit the BMC Software Customer Support page at http://www.bmc.com/support_home to request additional printed books or to view online books and notices (such as release notes and technical bulletins).
NOTE
Online books are formatted as Portable Document Format (PDF) or HTML files. To view, print, or copy PDF books, use the free Acrobat Reader from Adobe Systems. If your product installation does not install the reader, you can obtain the reader at http://www.adobe.com.
The product software also offers online Help for

s s
commands that you enter at the command line prompts that the obacktrack program displays
You can display the command-line Help by entering the -help option after a command. You can display the obacktrack Help by entering ? at any prompt.
About This Book
11
Related Publications
Related Publications
The following related publications supplement this book and the online Help:
Document SQL-BackTrack for Oracle Messages Manual SQL-BackTrack for Oracle Reference Manual Description describes informational, warning, and error messages that SQL-BackTrack issues describes the syntax and usage of SQL-BackTrack commands, the usage of SQL-BackTrack parameter files and parameters, and the structure of the SQL-BackTrack catalog directory describes the features and limitations of this version of the SQL-BackTrack product and last-minute changes to product information provides instructions for using SQL-BackTrack to perform database backups and recoveries describes how to integrate SQL-BackTrack with several leading storage-manager products
SQL-BackTrack for Oracle Release Notes
SQL-BackTrack for Oracle User Guide SQL-BackTrack Module user guides
Conventions
This book uses the following special conventions:
s
All syntax, operating system terms, and literal examples are presented in this typeface.
Variable text in path names, system messages, or syntax is displayed in angle brackets (<>):
testsys/<instance>/<fileName>
The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu.
12
Chapter
1
14 14 14 14 15 16 18 19 19 21 23 24 24 25 26 27 27 27 28 31 32 32 33
Preparing to Install
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SmartDBA Recovery Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Task Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing on a Single Unix Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing in a RAC Environment (Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing in a Failover Environment (Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing on a Windows Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems and Oracle Software . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Module Software Requirements. . . . . . . . . . . . . . . . . . Supported Backup Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an Earlier Version of SQL-BackTrack for Oracle . . . . . . . . . . . . Installing Multiple Versions of SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Licensing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1
13
Overview
Overview
This chapter provides general information to review before installing the SQL-BackTrack for Oracle product. The following topics are described:
s s s s s s
Products and Components on page 14 Installation Task Map on page 16 Configurations on page 18 Installation Requirements on page 24 Installation Considerations on page 27 Licensing on page 32
Products and Components

The following sections describe the SQL-BackTrack for Oracle products and their components:
Products and Components SQL-BackTrack for Oracle SQL-BackTrack Modules SmartDBA Recovery Management Components Reference page 14 page 14 page 15
SQL-BackTrack for Oracle

The SQL-BackTrack for Oracle product is a complete backup and recovery management solution that simplifies database backup and recovery tasks. To perform backup and recovery jobs using SQL-BackTrack for Oracle, you must install SQL-BackTrack for Oracle on each computer that contains an Oracle database.
SQL-BackTrack Modules
The SQL-BackTrack modules extend the capabilities of SQL-BackTrack for Oracle by allowing physical backups and exports directly to tape, disk, or specific enterprise storage-management systems. In earlier versions of SQL-BackTrack for Oracle, these components were known as open backup stream interface (OBSI) modules.
14
SmartDBA Recovery Management Components
The standard tape and disk module software is installed with SQL-BackTrack for Oracle. If you want to perform a backup or recovery by using a supported enterprise storage-management system, you must first install the SQL-BackTrack for Oracle module for the storage management system. After installation, you must link the module software to your version of SQL-BackTrack for Oracle. For details about installing and linking SQL-BackTrack modules for enterprise storage-management systems, see your SQL-BackTrack module documentation.
NOTE
SQL-BackTrack modules for enterprise storage-management systems are sold separately. If you purchase such a module, the module documentation includes installation information.
SmartDBA Recovery Management Components

The following SmartDBA Recovery Management components are installed automatically when you install SQL-BackTrack for Oracle: Table 1
Component SmartDBA Recovery Management services
SmartDBA Recovery Management components

Reference EPM Integration Package on page 16
SmartDBA Console agents and services SmartDBA Integration Package on page 15
SmartDBA Integration Package

The SmartDBA Integration Package processes queries and commands for SQL-BackTrack for Oracle from the optional SmartDBA Console. The SmartDBA Console is an optional Java-based interface through which you can perform the majority of the SQL-BackTrack for Oracle backup and recovery tasks that are available through the obacktrack program menus. It is automatically installed on each computer where you install SQL-BackTrack for Oracle. For more information about where the SmartDBA Integration Package is installed, see SQL-BackTrack for Oracle Directory Structure on Unix on page 45 and SQL-BackTrack for Oracle Directory Structure on Windows on page 48. For more information about getting started with the SmartDBA Console, see the SQL-BackTrack for Oracle User Guide.
Chapter 1
15
Installation Task Map
EPM Integration Package

The EPM Integration Package provides services that collect status and performance metrics from SQL-BackTrack and display them in the Enterprise Policy Monitor (EPM). The optional EPM is a special interface that runs in the SmartDBA Console. The EPM allows you to view and monitor enterprise-wide backup and recovery activities for SQL-BackTrack for Oracle data sources. The EPM Integration Package is required to run the EPM. The EPM Integration Package is automatically installed and started on the database server host when you install SQL-BackTrack for Oracle. For more information about where the EPM Integration Package is installed, see SQL-BackTrack for Oracle Directory Structure on Unix on page 45 and SQL-BackTrack for Oracle Directory Structure on Windows on page 48. For more information about the EPM, including the components that are required to run it, see SmartDBA Recovery Management Getting Started.

Figure 1 on page 17 provides an overview of the installation process and the tasks that you must perform to complete the installation of SQL-BackTrack for Oracle. This task map also lists the sections of the book where you can find more information about each task.
16
Figure 1
Install SQL-BackTrack for Oracle.
SQL-BackTrack for Oracle Installation Task Map
Installation begins.
Install SQL-BackTrack for Oracle on each Unix or Windows computer. Chapter 2, Installing SQL-BackTrack for Oracle
Install the SmartDBA client.
Install the BMC Application Server and SmartDBA client files on a Windows computer.
Do you want to use SQL-BackTrack from the SmartDBA Console?
yes SmartDBA Recovery Management: Getting Started
no
Perform the post-installation steps.
Complete post-installation tasks.
Chapter 3, Performing Post-Installation Tasks
Chapter 1
17
Configurations
Figure 1
SQL-BackTrack for Oracle Installation Task Map (continued)
Configure RAC environment for SQL-BackTrack for Oracle.
4
Are you installing in a RAC environment?
yes
Configure environment for use with SQL-BackTrack for Oracle. Chapter 4, Configuring RAC Environments for SQL-BackTrack for Oracle
no
Configure failover environment for SQL-BackTrack for Oracle.
5
Are you installing in a failover environment? yes
Configure environment for use with SQL-BackTrack for Oracle. Chapter 5, Configuring Failover Environments for SQL-BackTrack
no
Installation ends.
Configurations
The following sections describe the configurations that are possible with SQL-BackTrack for Oracle:
s s s s
Installing on a Single Unix Computer on page 19 Installing in a RAC Environment (Unix) on page 19 Installing in a Failover Environment (Unix) on page 21 Installing on a Windows Computer on page 23
18
Installing on a Single Unix Computer
Installing on a Single Unix Computer

To use the SQL-BackTrack for Oracle product on a single Unix computer that is not part of a RAC or failover environment, install the SQL-BackTrack for Oracle product software. Figure 2 illustrates where the SQL-BackTrack for Oracle components reside on a single Unix computer. This configuration also shows optional SmartDBA Console client computers, which allow you to run your SQL-BackTrack utility from the SmartDBA Console. (This configuration does not include the data repository.) For more information about getting started with the SmartDBA Console, see the SQL-BackTrack for Oracle User Guide. Figure 2 SQL-BackTrack for Oracle on a Single Unix Computer
Installing in a RAC Environment (Unix)

SQL-BackTrack for Oracle supports backup and recovery of a Real Application Clusters (RAC) database on supported Unix platforms (see the SQL-BackTrack for Oracle Release Notes for your version). In a RAC environment, you can set up several computers, or nodes, that can access the same database. Each node has its own memory, but each node can use storage-management products such as VERITAS NetBackup, LEGATO NetWorker, or IBM Tivoli Storage Manager (TSM).
Chapter 1
19
Installing in a RAC Environment (Unix)
The primary node is the Unix computer on which SQL-BackTrack for Oracle initiates the backup or recovery job. A secondary node is any node other than the primary node in a RAC environment.
NOTE
You must follow specific licensing guidelines when installing SQL-BackTrack for Oracle in a RAC environment. For more information, see Licensing Guidelines on page 32.
Configuring the Primary Node

Perform the following tasks on the primary node in your RAC environment:
s s
install the SQL-BackTrack for Oracle software install the SQL-BackTrack third-party enterprise storage-management modules
Configuring Secondary Nodes

Perform the following tasks on the secondary node in your RAC environment:
s s
NOTE
If you want to use SQL-BackTrack for Oracle from a secondary node, you must configure the secondary node exactly as you configured the primary node. This process includes obtaining a SQL-BackTrack for Oracle license authorization key that was generated using the computer name and computer ID of the secondary node.
Figure 3 on page 21 illustrates where the SQL-BackTrack for Oracle components reside in a RAC environment. This configuration also shows optional SmartDBA Console client computers, which allow you to run your SQL-BackTrack utility from the SmartDBA Console. (This configuration does not include the data repository.) For more information about getting started with the SmartDBA Console, see the SQL-BackTrack for Oracle User Guide and SmartDBA Recovery Management Getting Started.
20
Installing in a Failover Environment (Unix)
Figure 3
SQL-BackTrack for Oracle in a RAC Environment
For more information about configuring SQL-BackTrack for Oracle in a RAC environment, see Chapter 4, Configuring RAC Environments for SQL-BackTrack for Oracle.

SQL-BackTrack for Oracle functions in an operating system cluster environment that is set up to support a failover strategy for Oracle, but it does not support failover of the backup or recovery process. In the event of a failover, the backup or recovery process fails gracefully, and after you restart the process it runs on the failover node without manual intervention.
Chapter 1 Preparing to Install 21
To use SQL-BackTrack for Oracle in a failover environment, install the SQL-BackTrack for Oracle product on a shared disk. Installing the product files on the shared disk enables the primary node and a failover node to access the same product files. You should also create the SQL-BackTrack for Oracle catalog on the shared disk so that both nodes can access the same catalog information. Figure 4 illustrates where the SQL-BackTrack for Oracle components reside on a shared disk in a failover environment. This configuration also shows optional SmartDBA Console client computers, which allow you to run your SQL-BackTrack utility from the SmartDBA Console. (This configuration does not include the data repository.) For more information about getting started with the SmartDBA Console, see the SQL-BackTrack for Oracle User Guide. Figure 4 SQL-BackTrack for Oracle in a Failover Environment
22
Installing on a Windows Computer
For more information about configuring SQL-BackTrack for Oracle in a failover environment, see Chapter 5, Configuring Failover Environments for SQL-BackTrack.
Installing on a Windows Computer

If you are installing SQL-BackTrack for Oracle on a Windows computer, you must perform the following tasks:
s s
Figure 5 illustrates where the SQL-BackTrack for Oracle components reside on a Windows computer. This configuration also shows optional SmartDBA Console client computers, which allow you to run your SQL-BackTrack utility from the SmartDBA Console. (This configuration does not include the data repository.) For more information about getting started with the SmartDBA Console, see the SQL-BackTrack for Oracle User Guide. Figure 5 SQL-BackTrack for Oracle on Windows
Chapter 1
23
Installation Requirements
Installation Requirements
The following sections describe the requirements necessary for installing SQL-BackTrack for Oracle:
s s s s s
Authorization Requirements on page 24 Hardware Requirements on page 25 Supported Operating Systems and Oracle Software on page 26 SQL-BackTrack for Oracle Module Software Requirements on page 27 Supported Backup Media on page 27
Authorization Requirements
Table 2 lists the operating system authorizations that are required to install SQL-BackTrack for Oracle. Table 2
Unix
Operating System Authorization Requirements

To install SQL-BackTrack for Oracle on a Unix computer, you must meet the following requirements:
s
Operating System Type Authorization Required
Install SQL-BackTrack for Oracle by using the same user ID that was used to install Oracle. Otherwise, you might not be able to perform backup and recovery jobs by using SQL-BackTrack for Oracle. Log on to the Unix computer as a user with root authority.
Note: If you need to run the SmartDBA Recovery Management services as different user than root (for example, oracle), you can set the EPM_USER_ID environment variable to that user before starting the installation program. For example: export EPM_USER_ID=oracle Windows To install SQL-BackTrack for Oracle on Windows, you must be a member of the local Administrators group.
24
Hardware Requirements
Hardware Requirements
To install SQL-BackTrack for Oracle product, the computer must meet the following hardware requirements.
CD Drive
You must be able to access a CD drive from the computer on which you are installing the product.
Memory
Verify that the computer on which you want to install SQL-BackTrack for Oracle meets the following memory requirements:
s
If you are installing SQL-BackTrack for Oracle on a Windows computer, verify that the computer has a minimum of 128 MB of RAM. If you want to use the dtwatch (or dtwwatch on Windows) program to monitor the status of SQL-BackTrack for Oracle operations, the Unix or Windows computer must meet the following requirements: 4 KB of shared memory (a 4 KB memory-mapped file on Windows) 1 semaphore set and 25 semaphores For instructions on meeting these requirements, see your operating system documentation and your Oracle installation and configuration documentation.
Disk Drive
Verify that the disk drive where you want to install SQL-BackTrack for Oracle meets the following requirements:
s
The disk drive is not an NFS-mounted drive.
Chapter 1
25
Supported Operating Systems and Oracle Software
The disk drive has sufficient disk space to install SQL-BackTrack for Oracle. To ensure sufficient disk space, consider the following factors: size of the SQL-BackTrack for Oracle product files SQL-BackTrack for Oracle requires approximately 550 MB of available disk space on Unix and 150 MB on Windows. size of the .stat files created during an incremental backup You must allocate a minimum of 50 MB of disk space for the .stat files that are created. The size of the .stat files depends on the size of the corresponding data files. SQL-BackTrack for Oracle catalog size The space allocation for the SQL-BackTrack for Oracle catalog is based on the number of data files and the number of backups that you want to keep for the data files. Table 3 lists examples of approximate sizes for a SQL-BackTrack for Oracle catalog used with a single Oracle database. If you plan to use SQL-BackTrack for Oracle with multiple databases, calculate the space required for each database to determine the total disk space to allocate for the catalog. Table 3 SQL-BackTrack for Oracle Catalog Space Allocation
Number of Data Files 512 1024 1024 Data File Size 500 MB 1 GB 1 GB Number of Backups Disk Space 1 1 2 18 MB 75 MB 150 MB
Supported Operating Systems and Oracle Software

For complete information about the operating systems and Oracle software that are supported for SQL-BackTrack for Oracle, see the SQL-BackTrack for Oracle Release Notes for your version.
26
SQL-BackTrack for Oracle Module Software Requirements
SQL-BackTrack for Oracle Module Software Requirements

For complete information about the module software supported for SQL-BackTrack for Oracle, see the SQL-BackTrack for Oracle Release Notes for your version. For more information about specific requirements for installing and using the module software, see your SQL-BackTrack for Oracle module documentation.
Supported Backup Media

The following sections describe the backup media supported for tape and disk.
Tape Media
The following tape media is supported:
s s s
4 mm digital audio tape (DAT) 8 mm (Exabyte) digital linear tape (DLT)
NOTE
For information about the supported DLT tapes, see the appendix titled Managing Tapes in the SQL-BackTrack for Oracle User Guide.
Disk Media
The following disk media is supported:
s s
magnetic disks optical disks
Installation Considerations
The following sections describe the installation considerations for SQL-BackTrack for Oracle:
s s
Upgrading from an Earlier Version of SQL-BackTrack for Oracle on page 28 Installing Multiple Versions of SQL-BackTrack for Oracle on page 31
Chapter 1
27
Upgrading from an Earlier Version of SQL-BackTrack for Oracle

If you are upgrading to a newer version of SQL-BackTrack for Oracle, review the information in the following sections.
NOTE
Always create a backup of the existing catalog directory before upgrading to a new version of SQL-BackTrack for Oracle.
Upgrading on Unix
Before upgrading to a new version of SQL-BackTrack for Oracle on a Unix computer, consider the following information:
s
If you are using SQL-BackTrack for Oracle version 4.0.00 or earlier on Linux, you cannot use the existing license authorization key with version 5.0 or later releases. You must run the dthostid command to obtain your ethernet address, and then submit the information to BMC Software to request a new license key. See Obtaining a License Key on page 33 and Updating License Information for Unix on page 62. Before installing the new version of SQL-BackTrack for Oracle, stop any dtoarchmon or dtlicense processes that are running on the Unix computer. After you have completed installing the new version of SQL-BackTrack for Oracle, restart the dtlicense and dtoarchmon processes on the computers where they were running. Change the value of the DTBASE, DT_OBACKTRACK_HOME, and PATH environment variables so that they point to the current directories. Do not include the SQL-BackTrack version number in any environment variable values; the obacktrack symbolic link always points to the most recently installed directory. See Setting Environment Variables for Unix on page 58 for more information. The installation program does not overwrite the installation of an earlier version of SQL-BackTrack for Oracle on Unix. The default installation directory for SQL-BackTrack for Oracle on Unix is as follows:
/opt/bmc/SQL-BackTrack for Oracle/obacktrack
The obacktrack symbolic link always points to the most recently installed directory.
s
You can use an existing SQL-BackTrack for Oracle catalog with the new version of SQL-BackTrack for Oracle. However, using an existing catalog is not recommended because you will not have access to the latest features of SQL-BackTrack. To use an existing catalog, ensure that you set the
28
DT_ORACATALOG environment variable to point to the existing catalog directory. If you create a new SQL-BackTrack for Oracle catalog in a different directory, you must set the DT_ORACATALOG environment variable to point to the new catalog directory location.
WARNING
BMC Software recommends that you do not create the catalog directory (oracatalog) in the default $DTBASE, $DTBASE/obacktrack, or $DTBASE/obacktrack-<version> directory. If you create the catalog in one of these directories, you might accidentally delete the catalog directory if you remove or upgrade the SQL-BackTrack product.
NOTE
If you want to use an earlier version of SQL-BackTrack for Oracle after upgrading to a newer version, you cannot use the same catalog with the earlier version of the product. Using an upgraded version of the catalog with an earlier version of the product can cause problems with your backups and dump history.
You must modify any existing backup and recovery scripts so that they reference the new version of SQL-BackTrack for Oracle and the different catalog directory (if you are not reusing an existing catalog). To reuse an existing SQL-BackTrack for Oracle parameters file, you must copy this file from the following directory for your earlier version of SQL-BackTrack for Oracle to the same directory for your later version of SQL-BackTrack for Oracle:
$DTBASE/obacktrack/ctl
You can reuse a license key from an earlier version of a SQL-BackTrack for Oracle product for the later version of the software if the earlier version is still supported by BMC Software. The license key is located in the license file that is located in the following directory:
You must modify the existing physical profiles and export profiles to use any of the new features available with the latest release of SQL-BackTrack for Oracle. See the SQL-BackTrack for Oracle User Guide for more information. To determine which version of the obacktrack program you are using, run obacktrack with the -version option as follows:
obacktrack -version
This program produces output similar to the following output:
Chapter 1
29
> obacktrack -version obacktrack: version 5.0.10, serial number OB-12345678-1234, licensed to BMC This version of SQL-BackTrack supports large files(>2GB).
Upgrading on Windows
Before upgrading to a new version of SQL-BackTrack for Oracle on a Windows computer, consider the following information:
s
In earlier versions of SQL-BackTrack for Oracle, the ML_ROOT environment variable was set for the Windows operating system. To use the latest version of SQL-BackTrack for Oracle, you must remove the ML_ROOT environment variable. Before installing the new version of SQL-BackTrack for Oracle, stop any dtoarchmon processes running on the Windows computer. After you install SQL-BackTrack for Oracle, restart dtoarchmon. You can use an existing SQL-BackTrack for Oracle catalog with the new version of SQL-BackTrack for Oracle. Ensure that you set the DT_ORACATALOG environment variable to point to the existing catalog directory. If you create a new SQL-BackTrack for Oracle catalog in a different directory, you must set the DT_ORACATALOG environment variable to point to the new catalog directory location.
WARNING
BMC Software recommends that you do not create the catalog directory (oracatalog) in the default %DTBASE%, %DTBASE%\obacktrack, or %DTBASE%\obacktrack-<version> directory. If you create the catalog in one of theses directories, you might accidentally delete the catalog directory if you remove or upgrade the SQL-BackTrack product.
NOTE
If you want to use an earlier version of SQL-BackTrack for Oracle after upgrading to a newer version, you cannot use the same catalog with the earlier version of the product. Using an upgraded version of the catalog with an earlier version of the product can cause problems with your backups and dump history.
If you want to reuse an existing SQL-BackTrack for Oracle parameters file, you must copy this file from the following directory in the earlier version of SQL-BackTrack for Oracle to the same directory in the later version of SQL-BackTrack for Oracle:
%DTBASE%\obacktrack\ctl
30
Installing Multiple Versions of SQL-BackTrack for Oracle
You can reuse a license key from an earlier version of the SQL-BackTrack for Oracle product when installing the latest version of the software. However, you can reuse the license key only if the earlier version is still supported by BMC Software. You can find the license key in the license file in the following directory:
%DTBASE%\obacktrack\ctl
To use any new features that are available with the latest release of SQL-BackTrack for Oracle, you must modify the existing physical or export profiles. For more information, see the SQL-BackTrack for Oracle User Guide. You must modify the existing backup and recovery scripts so that they reference the new version of SQL-BackTrack for Oracle and the different catalog directory (if you are not reusing an existing catalog).
Installing Multiple Versions of SQL-BackTrack for Oracle

If you are installing the 32-bit and 64-bit versions of SQL-BackTrack for Oracle on a single Unix computer, observe the following restrictions and guidelines:
s
You cannot install the 32-bit and 64-bit versions of SQL-BackTrack for Oracle in the same base installation directory (DTBASE). For example, if you installed the 32-bit version of SQL-BackTrack for Oracle in the default directory (opt/bmc/SQL-BackTrack for Oracle), you must install the 64-bit version in a different directory. After you install SQL-BackTrack for Oracle, set the PATH environment variable to include the path for the version of SQL-BackTrack for Oracle that you want to use. To perform this task, see Setting Environment Variables for Unix on page 58. Reset the PATH variable if you want to use a different installed version of the product. After you install SQL-BackTrack for Oracle, set the DTBASE and DT_OBACKTRACK_HOME environment variables to point to the symbolic link for the installation directory for SQL-BackTrack for Oracle, which is obacktrack. The symbolic link obacktrack always points to the latest installed version of SQL-BackTrack for Oracle. To perform this task, see Setting Environment Variables for Unix on page 58. Reset these variables if you want to use a different installed version of the product.
Chapter 1
31
Licensing
Licensing
You can install SQL-BackTrack for Oracle by using an evaluation license or by obtaining a license authorization key (also called a license key). To obtain a license key for SQL-BackTrack for Oracle, you must gather specific information about each computer on which you will install the products and then complete the SQL-BackTrack License Authorization Key Request Form that is included in the SQL-BackTrack for Oracle product kit.
NOTE
If you cannot locate the required form, contact your BMC Software sales representative.
The following sections describe the licensing guidelines and how to obtain a license key:
s s
Licensing Guidelines on page 32 Obtaining a License Key on page 33
Licensing Guidelines
To license the SQL-BackTrack for Oracle product, follow these guidelines:
s
If you do not have a license key for the SQL-BackTrack for Oracle product, you can install it with a 15-day evaluation license. If you are installing the SQL-BackTrack for Oracle product in a failover environment, a different license key is required for the primary node and the failover node. Both license keys must be added to the SQL-BackTrack for Oracle license file. To add the license information for each node, see Updating License Information for Unix on page 62. To install the SQL-BackTrack for Oracle product in a RAC environment, you must have a RAC license key. This license key allows you to install the product on each licensed node in a RAC environment. If the computer name or computer ID for a computer on which SQL-BackTrack for Oracle is installed changes, you must obtain a new license key for the computer. After you have obtained the new license key, update the license information by using one of the following procedures: Updating License Information for Unix on page 62 Adding or Updating a License Key on Windows on page 69
32
Obtaining a License Key
If you have installed an earlier version of SQL-BackTrack for Oracle on Linux, you cannot use the existing license authorization key with version 5.0 or later releases. Follow the procedure in Obtaining a License Key on page 33 and apply for a new license.

Use the following procedure to obtain a license authorization key for SQL-BackTrack for Oracle.
Before You Begin

Obtain a copy of the SQL-BackTrack License Authorization Key Request Form. A copy of this form should be included in the product kit. If you do not have a copy of this form, contact your sales representative.
To Obtain a License Key 1 Use the procedures listed in Table 4 to determine the computer IDs of the
computers on which you will install the SQL-BackTrack for Oracle product. Table 4
Platform Hewlett-Packard HP-UX
Procedures for Determining Computer IDs

Procedure At the command prompt, enter the following command: uname -i
IBM AIX
At the command prompt, enter the following command: uname -m
Microsoft Windows
From a command prompt, enter the following command: ipconfig /all In the information that is displayed, note the Physical Address.
Chapter 1
33
Table 4
Platform
Procedures for Determining Computer IDs

Procedure For these platforms, obtain the ethernet address (instead of the computer ID) by using the following procedures: If SQL-BackTrack Is Not Installed 1. Mount the SQL-BackTrack for Oracle CD. 2. At the prompt, enter the following command: <CDMountDir>/<osDir>/dthostid The <osDir> variable represents the directory on the product CD where the dthostid utility is located (either /DEC or /Linux, depending on the operating system). If SQL-BackTrack Is Installed At the command prompt, enter the following command: $DTBASE/obacktrack/install/dthostid
Red Hat Linux SLES LINUX Hewlett-Packard Tru64 UNIX
Sun Solaris
At the command prompt, enter the following command: /usr/ucb/hostid
2 Complete the remaining entries on the SQL-BackTrack License Authorization Key

Request Form.
3 Fax the form to the number listed on the form.

After receiving the information, BMC Software generates license authorization keys and sends them to you in an e-mail message.
34
Chapter
2
35 36 42 44 45 45 48 50 50 53
Installing SQL-BackTrack for Oracle

This chapter presents the following topics: Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SQL-BackTrack for Oracle on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the Patch Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Installation of SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Unix . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Directory Structure on Windows . . . . . . . . . . . . . . . . . . . . Procedures for Uninstalling SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling SQL-BackTrack for Oracle on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling SQL-BackTrack for Oracle on Windows . . . . . . . . . . . . . . . . . . . . . . .
Installation Procedures
Use the following procedures to install the SQL-BackTrack for Oracle product on a Unix or Windows computer:
Platform Unix Reference
s s
Installing SQL-BackTrack for Oracle on Unix on page 36 Verifying Installation of SQL-BackTrack for Oracle on Unix on page 45
Windows
Installing SQL-BackTrack for Oracle on Windows on page 42
Chapter 2
35
Installing SQL-BackTrack for Oracle on Unix

Use this procedure to install SQL-BackTrack for Oracle on a Unix computer.
Before You Begin

Before you begin the installation process, perform the following actions:
s
Review the information in Chapter 1, Preparing to Install. Ensure that your system meets all the requirements listed in Installation Requirements starting on page 24. Verify that you have the correct SQL-BackTrack for Oracle product CD for your operating system. Verify that the disk drive where you want to install SQL-BackTrack for Oracle is accessible and meets the requirements specified in Hardware Requirements on page 25.
To Install SQL-BackTrack for Oracle on Unix 1 Log on to the Unix computer as root.
If you prefer to run the database server host as a different user than root, you can set the EPM_USER_ID environment variable to that user. For example:
export EPM_USER_ID=oracle
2 Mount the SQL-BackTrack for Oracle product CD by using one of the following
commands:
Operating System Hewlett-Packard HP-UX Hewlett-Packard Tru64 UNIX IBM AIX Red Hat Linux Sun Solaris SLES LINUX Command mount -F cdfs -r <device> <mountPoint> mount -r <device> <mountPoint> mount -v cdrfs -r <device> <mountPoint> mount <device> <mountPoint> mount -F hsfs -o ro <device> <mountPoint> mount <device> <mountPoint>
3 Log on to the computer as the user who installed Oracle on this computer.
36
4 Create an installation base directory for SQL-BackTrack for Oracle.

The default directory is /opt/bmc/SQL-BackTrack for Oracle.
5 From the CD mount point, run the installation script by typing the following
command at the command prompt:
./obtinstall.sh
The installation program launches.
6 At the prompt, press Enter to continue. 7 Press the Space key as needed to review the license information. 8 At the following prompt, enter Yes to accept the license agreement. Otherwise,
enter No to cancel the installation.
Do you accept the above license agreement ? (Yes/No)
If you enter No, the installation is cancelled and the following message displays:
*** The user did not accept the license agreement. The installation process was cancelled. ***
9 If the following prompt appears, the installation program detected components

from a previous installation at the location where you are installing SQL-BackTrack for Oracle. Perform one of the following actions:
s s
Enter y to remove the existing components before installing the product. Enter n to cancel the installation.
The installation program detected that the following files or directories already reside in the installation directory: <component1> <component2> <component3> ... If you continue, the installation program and directories, including the catalog if the listed directories. Additionally, the updates the links to OBSI modules and the point to the new installation. Do you want to continue? (Y/N) removes the listed files it is located in one of installation program obacktrack program to
Chapter 2
37
If you entered n, perform one of the following actions at the following prompt:
s s
Enter y to remove the existing components before installing the product. Enter n to cancel the installation.
Do you want to try to move CD distribution to production directory again? [No]
10 At the following prompt, press Enter if you can log on as the user who installed the
Oracle binaries. Otherwise, enter n to cancel the installation process.
Can you log on to this computer as the user who installed the Oracle binaries? (Y/N) [Y]
11 At the following prompt, press Enter to install with the user ID that is displayed in
the prompt, or enter a different user ID. Ensure that the user has read, write, and execute permissions on the directory created in step 4.
The user ID that will be used for installation is: [<userID>]
12 At the following menu, enter the number that corresponds to the product that you
want to install. Otherwise, enter q to cancel the installation process.
The products available for installation are: 1) SQL-BackTrack for Oracle(32 bit) 2) SQL-BackTrack for Oracle(64 bit) q) Quit Installation Enter menu number of product to be installed [1-2 | q]:
NOTE
The second menu option appears only if SQL-BackTrack for Oracle detects a 64-bit operating system and a 64-bit version of SQL-BackTrack for Oracle is available for that operating system.
13 At the following prompt, enter the full path name for an existing directory where
you want to install the files, or press Enter to accept the default path shown in brackets.
Where do you want to install the product [<$DTBASE>]?:
NOTE
If you are installing both the 32-bit and 64-bit versions of SQL-BackTrack for Oracle on the same Unix computer, install each version under a separate installation directory.
38
14 At the following prompt, enter y if you are using the product in an RAC
environment. Otherwise, press Enter.
Will you be using this product in an OPS/RAC environment? [Y/N] [N]
NOTE
SQL-BackTrack for Oracle version 5.0.10 supports clustering through Real Application Clusters (RAC), the new generation of Oracle Parallel Server (OPS). SQL-BackTrack for Oracle no longer supports clustering through OPS.
15 At the following prompt, enter the name of your organization.

Enter your organization name (up to 40 characters):
16 At the following prompt, proceed with one of the following actions:

s s
If you have a license key, press Enter. If you do not have a license key, enter n to install with a 15-day evaluation license. Then, skip to step 19.
Do you have your authorization key now? [Yes]
17 At the following prompt, enter the license key that was generated for this
computer:
Enter the authorization key:
18 When the installation program displays your license information, verify that the
information is correct and press Enter. Otherwise, enter n and then re-enter your license information.
Ready to write an entry: Serial number: <serialNumber> Host name: <computerName> Host id: <computerID> Authorization: <licenseKey> OK to proceed? [Yes]
19 At the following prompt, press Enter to specify an e-mail address that will receive
licensing notification messages. Otherwise, enter n and skip to step 22 on page 40.
Do you want to specify an e-mail address to receive notification messages? [Yes]
Chapter 2
39
NOTE
You can set up licensing notification after installation, if you prefer. For more information, see Setting Up Licensing Notification on page 64.
20 At the following prompt, enter the e-mail address that will receive the licensing
notification messages.
Enter the e-mail address to which you want licensing notification messages sent []:
21 At the following prompt, press Enter to confirm the e-mail address. Otherwise,
enter n and repeat step 20.
Is this correct ? [Yes]
22 At the following prompt, choose from the following actions:

s s
Press Enter to run the configuration script. Enter n if you want to skip this process and run the configuration script later.
Do you want to run the script Now? (Y/N) (Y)
NOTE
To enable the complete functionality of SmartDBA Recovery Management and the Enterprise Policy Monitor, run the configuration script. If you are not able to log on as a root user at this time, you must run the configuration script after the installation is complete. For more information, see Running the SQL-BackTrack for Oracle Configuration Script on page 66. In a RAC environment, you must run the configuration script on all nodes to support distributed backups, and also in the event that the primary node is no longer available and a new node is designated as the primary one.
23 At the following prompt, press Enter to accept the root user as the user who will be
used to install the EPM Integration Package. Otherwise, enter a different user with root authority.
The user ID that will be used for installation is: [root]
24 At the following prompt, enter the password for the user with root authority on the
computer where you are installing SQL-BackTrack for Oracle:
Please enter the password for user <user> Password:
40
After the configuration script completes, the installation program displays a message indicating that the installation completed successfully.
Chapter 2
41
Installing SQL-BackTrack for Oracle on Windows
Where to Go from Here

Before you can use the SQL-BackTrack for Oracle product, you might need to complete some of the following tasks:
Task Verify the patch level. Verify your installation of SQL-BackTrack for Oracle. Reference Verifying the Patch Level on page 44
s
Verifying Installation of SQL-BackTrack for Oracle on Unix on page 45 SQL-BackTrack for Oracle Directory Structure on Unix on page 45
Set the environment variables required for using SQL-BackTrack for Oracle. Update your license information. Set up licensing notification. Set port numbers for the dtlicense and dtoarchmon processes. Run the SQL-BackTrack for Oracle configuration script. Configure a RAC environment for use with SQL-BackTrack for Oracle. Configure a failover environment for use with SQL-BackTrack for Oracle.
Setting Environment Variables for Unix on page 58 Updating License Information for Unix on page 62 Setting Up Licensing Notification on page 64 Setting Port Numbers for dtlicense and dtoarchmon on page 65 Running the SQL-BackTrack for Oracle Configuration Script on page 66 Chapter 4, Configuring RAC Environments for SQL-BackTrack for Oracle Chapter 5, Configuring Failover Environments for SQL-BackTrack

Use this procedure to install SQL-BackTrack for Oracle on Windows.
Before You Begin

Before you begin your installation, verify that the computer meets the requirements listed in Installation Requirements on page 24.
42
WARNING
The installer cannot verify if you have already installed this version of the software, and the installer overwrites the earlier installation if you attempt to install the product in the same directory. To reinstall the latest version of the product, you must first uninstall SQL-BackTrack for Oracle. To perform this task, see Uninstalling SQL-BackTrack for Oracle on Windows on page 53.
To Install SQL-BackTrack for Oracle on Windows 1 Insert the product CD into the CD drive. 2 If the installer does not launch automatically, perform the following steps: A From the Start menu, choose Run. B In the Open box, enter the following command:
<CDDriveID>:\setup.exe
3 On the Introduction page, click Next to continue. 4 On the License Agreement page, review the license agreement information, and
select the option to accept the license agreement. Click Next to continue.
5 On the Specify Installation Directory page, accept the default installation directory,
or click Choose to specify a different location. After you have specified your installation directory, click Next.
6 On the Provide License Information page, enter the following information, and
then click Next.
s s s
your name your companys name license key If you have a license authorization key, enter it in the License Key box. If you do not have a license authorization key, leave the box blank to install with a 15-day evaluation license.
7 On the Pre-Installation Summary page, review the displayed information, and

then click Install to install the product.
8 When the Install Complete page is displayed, click Done to exit the installer.
Chapter 2
43
Verifying the Patch Level
Where to Go from Here

Before you can use SQL-BackTrack for Oracle on Windows, you might need to complete some of the following tasks:
Task Verify the patch level. Verify the installation directories. Set the required environment variables. Update your licensing information. Reference Verifying the Patch Level on page 44 SQL-BackTrack for Oracle Directory Structure on Windows on page 48 Setting Environment Variables for Windows on page 67 Adding or Updating a License Key on Windows on page 69
Verifying the Patch Level

The SmartDBA Integration package uses a private copy of the Java Runtime Environment (JRE), version 1.3.1, that requires your operating system to be at a certain patch level. Verify that the operating system on this computer is at the requisite patch level before using SQL-BackTrack for Oracle through the optional SmartDBA Console. To determine the correct patch level for your operating system, view the README file file, Readme-JRE.html or Readme-JRE.txt, which are located in the following directories:
Platform Unix Windows File $DTBASE/obacktrack/btsdba/ %DTBASE%\obacktrack\btsdba\
44
Verifying Installation of SQL-BackTrack for Oracle on Unix
Verifying Installation of SQL-BackTrack for Oracle on Unix

Use the dtoverifyinstall script to verify that the SQL-BackTrack for Oracle product is installed and configured properly on a Unix computer. The dtoverifyinstall script checks that
s s s s
the license information is correct all SQL-BackTrack for Oracle programs are installed SQL-BackTrack for Oracle is customized with the license information the SQL-BackTrack modules are linked correctly
Before You Begin

Set the DTBASE environment variable to your installation directory before verifying your installation. See Setting Environment Variables for Unix on page 58 for more information. Also, ensure that other environment variables, such as DT_OBACKTRACK_HOME, are not set.
To Verify the Installation of SQL-BackTrack for Oracle on Unix 1 Change to the following directory:
cd $DTBASE/obacktrack/install
2 Enter the following command at the command prompt:

./dtoverifyinstall
3 When prompted, press Enter to continue.
SQL-BackTrack for Oracle Directory Structure on Unix

Figure 6 shows the structure of the product directory for both the $DTBASE and $DT_OBACKTRACK_HOME directories after installation on a Unix computer is complete.
Chapter 2
45
Figure 6
$DTBASE

$DT_OBACKTRACK_HOME
.grx_dirname
bin
common
btsdba cdump
dtlicense grx
ctl
grx_<yymmddhhmiss>
deinstall
log
ebr
mls
install
obacktrack
links
obsi.disk
log
obsi.tape
man
utilities
mls
msgs
support
Table 5 shows the contents of the directories within the $DTBASE directory on a Unix computer. Table 5 SQL-BackTrack for Oracle Directory Structure on Unix ($DTBASE) (Part 1 of 2)
Contents contains the name of the directory that contains the updated contents for the services and agents needed to run the obacktrack program from the SmartDBA Console part of the EPM Integration Package, which is installed during the first installation of the EPM Integration Package on this computer This directory is shared across installations. Note: The obtuninstall program removes the common directory only if this is the last $DTBASE installation being uninstalled on this computer. /dtlicense dtlicense command
Directory or file .grx_dirname
/common
46
Table 5
/grx
SQL-BackTrack for Oracle Directory Structure on Unix ($DTBASE) (Part 2 of 2)

Contents part of the SmartDBA Integration Package, which provides the services and agents needed to run the obacktrack program from the SmartDBA Console the directory that contains the updated contents for the services and agents needed to run the obacktrack program from the SmartDBA Console datatools.log file localization files SQL-BackTrack for Oracle; see Table 6 SQL-BackTrack for Oracle module for disk files SQL-BackTrack for Oracle module for tape files diagnostic utilities
Directory or file
/grx_<yymmddhhmiss> /log /mls /obacktrack /obsi.disk /obsi.tape /utilities
Table 6 shows the contents of the directories within the $DT_OBACKTRACK_HOME directory ($DTBASE/obacktrack) on a Unix computer. Table 6
Directory /bin /btsdba /cdump /ctl /deinstall /ebr
SQL-BackTrack for Oracle Directory Structure on Unix ($DT_OBACKTRACK_HOME)

Contents SQL-BackTrack for Oracle binaries such as obacktrack, dtobackup, dtorestore, and so on part of the SmartDBA Integration Package, which provides services needed to run the obacktrack program from the SmartDBA Console core dumps serial and license information internal files for removal of SQL-BackTrack for Oracle components part of the EPM Integration Package, which provides the SmartDBA Recovery Management services that enable monitoring and management from the Enterprise Policy Monitor (EPM) scripts for installing individual SQL-BackTrack for Oracle components and customizing the product links to the SQL-BackTrack modules SQL-BackTrack for Oracle log files, including datatools.log Unix man pages localization files for support of foreign languages product messages utilities to help analyze performance and diagnose problems
/install /links /log /man /mls /msgs /support
Chapter 2
47
SQL-BackTrack for Oracle Directory Structure on Windows

Figure 7 on page 48 shows the structure of the product directory for both the %DTBASE% and %DT_OBACKTRACK_HOME% directories after installation on a Windows computer is complete. Figure 7 SQL-BackTrack for Oracle Directory Structure on Windows
%DT_OBACKTRACK_HOME%
%DTBASE%
common jre obacktrack-<version>
bin
btsdba ctl
obsi.disk
ebr
obsi.tape
lib
links
log
mls
msgs
support
UninstallerData
Table 7 shows the contents of the directories within the %DTBASE% directory on a Windows computer.
48
Table 7
Directory /common
SQL-BackTrack for Oracle Directory Structure on Windows (%DTBASE%)

Contents part of the EPM Integration Package, which is installed during the first installation of the EPM Integration Package on this computer This directory is shared across installations. Note: The obtuninstall program removes the common directory only if this is the last $DTBASE installation being uninstalled on this computer.
/jre /obacktrack-<version> /obsi.disk /obsi.tape
JRE package SQL-BackTrack for Oracle; see Table 8 on page 49 SQL-BackTrack for Oracle module for disk files SQL-BackTrack for Oracle module for tape files
Table 8 on page 49 shows the contents of the directories within the %DT_OBACKTRACK_HOME% directory (%DTBASE%\obacktrack) on a Windows computer. Table 8
Directory \bin \btsdba \ctl \ebr
SQL-BackTrack for Oracle Directory Structure on Windows (%DT_OBACKTRACK_HOME%)

Contents SQL-BackTrack for Oracle binaries such as obacktrack, dtobackup, dtorestore, and so on part of the SmartDBA Integration Package, which provides services needed to run the obacktrack program from the SmartDBA Console serial and license information part of the EPM Integration Package, which provides the SmartDBA Recovery Management services that enable monitoring and management from the Enterprise Policy Monitor (EPM) library files links to the SQL-BackTrack modules SQL-BackTrack for Oracle log files, including datatools.log localization files for support of foreign languages product messages utilities to help analyze performance and diagnose problems internal files for removal of SQL-BackTrack for Oracle components
\lib \links \log \mls \msgs \support \UninstallerData
Chapter 2
49
Procedures for Uninstalling SQL-BackTrack for Oracle
Procedures for Uninstalling SQL-BackTrack for Oracle

Use the following procedures to uninstall SQL-BackTrack for Oracle on a Unix or Windows computer:
Platform Unix Windows Reference Uninstalling SQL-BackTrack for Oracle on Unix on page 50 Uninstalling SQL-BackTrack for Oracle on Windows on page 53
Uninstalling SQL-BackTrack for Oracle on Unix

To remove the SQL-BackTrack for Oracle product from a Unix computer, you must uninstall SQL-BackTrack for Oracle by using the instructions provided on page 50. Then, uninstall the BMC Remote Execution (GRX) Agent by using the instructions provided on page 52.
Before You Begin

Before uninstalling SQL-BackTrack for Oracle, perform the following actions:
s
Verify that no SQL-BackTrack for Oracle programs are running. Create a copy of the SQL-BackTrack for Oracle catalog in a directory that is not part of the SQL-BackTrack for Oracle directory structure.
WARNING
You cannot recover from a SQL-BackTrack backup without the associated catalog.
To Uninstall SQL-BackTrack for Oracle Components on Unix 1 Change to the directory that contains the SQL-BackTrack for Oracle obtuninstall
script by using the following command:
50
2 Run the obtuninstall script by entering the following command at the command
prompt:
./obtuninstall
NOTE
The obtuninstall script removes all components of SQL-BackTrack, including the Enterprise Snapshot component (if it is installed) and the EPM Integration Package. However, the obtuninstall program removes the common directory only if this is the last $DTBASE installation being uninstalled on this computer. If you want to uninstall only the EPM Integration Package, enter the command as follows: ./obtuninstall -epm
3 If you are sure that you want to uninstall SQL-BackTrack for Oracle, press Enter at
the following prompt. Otherwise, enter No to exit the uninstallation process.
Are you sure you want to run the uninstall utility? Yes/No (Yes)
4 At the following prompt, press Enter to accept the root user as the user that will be
used to uninstall the EPM Integration Package. Otherwise, enter a different user name with root authority.
The root user ID is: [root]
5 At the following prompt, enter the password for the user with root authority:
Please enter the password for user <user> Password:
The script finishes uninstalling SQL-BackTrack for Oracle components.
Chapter 2
51
NOTE
If the uninstallation script detects any of the following files or directories, the script does not remove them:
s s s s s s s s s s s s s s
$DTBASE/.grx_dirname $DTBASE/commona $DTBASE/dtlicense $DTBASE/dumpdata $DTBASE/grx $DTBASE/grx_<yymmddhhmiss> $DTBASE/log $DTBASE/mls $DTBASE/obsi.disk -> obsi.disk-6.1.00 $DTBASE/obsi.disk-6.1.00 $DTBASE/obsi.tape -> obsi.tape-6.1.00 $DTBASE/obsi.tape-6.1.00 $DTBASE/oracatalog $DTBASE/utilities
The uninstallation script does remove the common directory if this is the last installation of the product for the current release version. However, if you have two SQL-BackTrack for Oracle installations ($DTBASE1 and $DTBASE2), and you use the uninstallation script to remove the first installation ($DTBASE1), the uninstallation script does not remove the $DTBASE1/common directory because the $DTBASE2 installation uses it.
To Uninstall the BMC Remote Execution Agent on Unix WARNING

Do not uninstall the BMC Remote Execution Agent if you want to use the SmartDBA Console to perform any tasks on this computer.
1 Log in as root. 2 Using a text editor, remove the specified entries from the following files:
File /etc/bmc_pdm Entries to Remove #BMC-PDM-DELIMITER BKO_5.0.10_mapiversion=2.0.10 BKO_5.0.10_bttag=BKO-<dateTime> jre_1.4.2.01_<bits>_installDir=<directory> jboss_3.2.4_installDir=<directory> EBRDC_2.0.10_<bits>_installDir=<directory> jbdcl_2.0.00_installDir=<directory> BKO_5.0.10_dtbase=<directory> BKO_5.0.10_installdir=<directory> XBT_1.5.00_installdir=<directory> grx_1.1.08_local_repository=<directory> grxagent <port>/tcp # BMC GRX Agent
/etc/services
52
Uninstalling SQL-BackTrack for Oracle on Windows
File /etc/inetd.conf
a
Entries to Remove grxagent stream tcp nowait root <directory> grxagent port=0 home=<directory> logfile=<directory>/grxagent.log j1:a:once=<directory>/run_bmc2.sh
/etc/inittab
a
For Red Hat Linux and SLES LINUX, the xinetd.conf file is used.
3 Reinitialize the inetd or xinetd process by performing the following steps: A To determine the process ID (PID) for the inetd or xinetd process, execute the
following command:
ps -ef | grep <processName>
The program displays the PID, as in the following example:

root 369 1 0 May 24 ? 0:00 /usr/sbin/inetd -s
B At the command prompt, execute the following command specifying the PID:
kill -HUP <PID>
4 Remove the $DTBASE/grx directory.

To remove the SQL-BackTrack for Oracle product from a Windows computer, uninstall SQL-BackTrack for Oracle and the SQL-BackTrack for Oracle Modules for Tape and Disk by using the instructions provided on page 54. Then, uninstall the BMC Remote Execution Agent (GRX) Agent by using the instructions provided on page 54.
Before You Begin

Before uninstalling SQL-BackTrack for Oracle, perform the following actions:
s
Verify that no SQL-BackTrack for Oracle programs are running. Create a copy of the SQL-BackTrack for Oracle catalog in a directory that is not part of the SQL-BackTrack for Oracle directory structure.
Chapter 2
53
WARNING
You cannot recover from a SQL-BackTrack for Oracle backup without the associated catalog.
To Uninstall SQL-BackTrack for Oracle and the SQL-BackTrack for Oracle Modules on Windows 1 From the Windows desktop, choose Start => Control Panel => Add/Remove
Programs.
2 From the Add/Remove Programs dialog, click Change/Remove for any one of the
following components:
s s s
SQL-BackTrack for Oracle SQL-BackTrack for Oracle Module for Disk SQL-BackTrack for Oracle Module for Tape
3 When the Uninstall Wizard launches, click Uninstall. 4 After the component is uninstalled, click Done to exit the Uninstall Wizard. 5 Repeat step 2 through step 4 until all of the SQL-BackTrack for Oracle components
have been removed from your computer.
To Uninstall the BMC Remote Execution Agent on Windows WARNING

Do not uninstall the BMC Remote Execution Agent if you want to use the SmartDBA Console to perform any tasks on this computer.
1 Stop the BMC Remote Execution Agent service, as follows: A Choose Start => Settings => Control Panel => Administrative Tools => Services or
Start => Settings => Control Panel => Windows Services Manager.
B Select the BMC Remote Execution Agent and stop the service. 2 Open a command prompt and change to the grx directory. The default installation
path for this directory is as follows:
cd C:\Program Files\Common Files\BMC Shared\grx
54
NOTE
You can find the location of the grx directory in the following entry of your Windows registry: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\GRX\ CurrentInstallDir
3 Run the following command to uninstall the BMC Remote Execution Agent:
grxagent install=N
NOTE
Because the command syntax is case sensitive, you must enter an uppercase N.
4 Delete the grx directory.
Chapter 2
55
56
Chapter
3
57 58 62 64 65 66 67 67 69 69
Performing Post-Installation Tasks

This chapter presents the following topics: SQL-BackTrack for Oracle Post-Installation Tasks on Unix . . . . . . . . . . . . . . . . . . . . . Setting Environment Variables for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating License Information for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Licensing Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Port Numbers for dtlicense and dtoarchmon . . . . . . . . . . . . . . . . . . . . . . . Running the SQL-BackTrack for Oracle Configuration Script . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Post-Installation Tasks on Windows . . . . . . . . . . . . . . . . . Setting Environment Variables for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding or Updating a License Key on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Operating System Authentication for Windows. . . . . . . . . . . . . . . . . .
SQL-BackTrack for Oracle Post-Installation Tasks on Unix

Depending on the actions that you took when you installed the SQL-BackTrack for Oracle product, you might need to perform some or all of the following tasks before you can use SQL-BackTrack for Oracle on Unix:
Task Set the environment variables for Unix. Add an entry to the license file. Customize SQL-BackTrack for Oracle for licensing. Set up licensing notification. Set port numbers for the dtlicense and dtoarchmon processes. Reference page 58 page 62 page 64 page 64 page 65
Chapter 3 Performing Post-Installation Tasks
57
Setting Environment Variables for Unix

Before you can use SQL-BackTrack for Oracle, you must set specific environment variables. Some variables are always required, while the use of others depends on your operating system and other factors. Use the following procedures to set environment variables for the product.
Before You Begin

Before setting any environment variables, review the information in Table 9 on page 59 and Table 10 on page 59.
To Set Unix Environment Variables for the Current Session 1 At the command prompt, set the environment variables. Depending on your Unix
shell, use the correct command syntax to set variables as follows:
Unix Shell C shell Bourne or Korn shells Command Syntax setenv <environmentVariable> <value> <environmentVariable>=<value> export <environmentVariable>
2 If the dtoarchmon process is running, stop the process and then restart it. For more
information, see the SQL-BackTrack for Oracle Reference Manual.
To Set Environment Variables Automatically 1 Use a text editor to open your Unix shell startup or initialization file (for example,
.login or .profile).
2 In the file, define the environment variables required for your system
environment.
3 Save the file. 4 From the command prompt, run the startup file.
For example, if you made the changes in your .profile file, use the following command:
. .profile
5 If the dtoarchmon process is running, stop the process and then restart it. For more
information, see the SQL-BackTrack for Oracle Reference Manual.
58
Table 9
Variable
Required Environment Variables for Unix

Description If you want to use the version of SQL-BackTrack for Oracle that was most recently installed, set the environment variable as follows: DT_OBACKTRACK_HOME=$DTBASE/obacktrack export DT_OBACKTRACK_HOME Note: If you have more than one version of SQL-BackTrack for Oracle installed, set this variable to this same symbolic link, obacktrack. The obacktrack symbolic link always points to the most current version of SQL-BackTrack for Oracle that is installed.
DT_OBACKTRACK_HOME
DTBASE LANG
Set this variable to the base installation directory. Set this variable only if you are using SQL-BackTrack for Oracle on Linux. Set the value of this variable to C to ensure that the correct date and time format is configured for SQL-BackTrack for Oracle. Set this variable to the directory containing the Oracle run-time libraries ($ORACLE_HOME/lib). Set this variable only if you are using SQL-BackTrack for Oracle on an AIX platform. Set this variable to the directory containing the Oracle run-time libraries ($ORACLE_HOME/lib). Set this variable only if you are using SQL-BackTrack for Oracle on HP-UX platforms. Set this variable to the directory containing the Oracle run-time libraries ($ORACLE_HOME/lib).
LD_LIBRARY_PATH LIBPATH
SHLIB_PATH
Table 10
Variable
Optional Environment Variables for Unix (Part 1 of 3)

Definition Set this variable if you are backing up to disk and the Unix file system that contains the disk destination directory is not mounted as a large file system. This variable must be set to less than 2 GB.
DT_DISK_FILESIZE
59
Table 10
Variable

Definition Set this variable to specify the directory where the stat files for incremental backups are created. If this variable is not set, SQL-BackTrack for Oracle creates the stat files in the following directory, by default: $DTBASE/obacktrack/obacktrack_stat Note: To allow SQL-BackTrack for Oracle to perform incremental backups after a failover event, set DT_OBACKTRACK_STAT to a directory that is accessible from both the primary node and the failover node.
DT_OBACKTRACK_STAT
DT_ORACATALOG
Set this variable to the location of the SQL-BackTrack for Oracle catalog directory. If you do not set the DT_ORACATALOG variable, the obacktrack program verifies whether the catalog variable is set in the $DTBASE/obacktrack/ctl/parameters file. If the variable is defined there, obacktrack uses the specified directory. If the catalog variable is not set, obacktrack checks the default catalog directory ($DTBASE/oracatalog). If the default directory exists, obacktrack prompts you to use this directory. If the default directory does not exist, obacktrack prompts you to enter the path name for the directory that you want to use. Note: The catalog directory should not be located on an NFS-mounted drive.
60
Table 10
Variable

Definition By default, SQL-BackTrack for Oracle assigns an arbitrary alphanumeric key to identify a shared memory segment. All SQL-BackTrack for Oracle processes write status information in this shared memory segment. If a process cannot identify a shared memory segment or the operating system does not have a minimum of 4 KB of shared memory available, the following message is displayed: BMCDSR4401161: ShMemInitialize: shmat error [<error>]. If you receive this message, set the DTSHMEM environment variable to an arbitrary alphanumeric key. For example, you might set this variable as follows: setenv DTSHMEM=5678 If you are running 32-bit and 64-bit versions of SQL-BackTrack for Oracle on the same computer, you must create a different key for each version of the product. If the error occurs again, try increasing the minimum amount of available shared memory. Note: If DTSHMEM=none, SQL-BackTrack for Oracle processes do not create a key to identify a shared memory segment. If no shared memory segment has been identified, the status monitoring utility (dtwatch) does not receive any status information to display.
DTSHMEM
DTTEMPDIR
Set this environment variable to point to the directory where SQL-BackTrack for Oracle stores temporary files. The default directory that SQL-BackTrack for Oracle uses is /tmp/datatools
s
If you plan to use SQL-BackTrack for Oracle in a RAC or failover environment, it is recommended that you specify a directory located on an NFS-mounted drive. If you are using SQL-BackTrack for Oracle in a single-instance environment, do not create the directory on an NFS-mounted drive or tmpfs file system.
Warning: If you have already started the product without setting DTTEMPDIR, do not specify the /tmp directory for your temporary directory. MANPATH Set this environment variable to enable access to the SQL-BackTrack online manual pages. Set this variable to $DTBASE/obacktrack/man. Then, use the man command from any command prompt, as follows: man <SQL-BackTrackCommand>
61
Updating License Information for Unix

Use the following procedure to update the information in your SQL-BackTrack for Oracle license file. You should use this procedure if you did not enter a license authorization key during installation, if your license information has changed, or if you need to add the license information for one of the nodes in your failover environment.
Before You Begin

Before you can update your license information, you must perform the following tasks:
s
Set the DTBASE environment variable. See Setting Environment Variables for Unix on page 58. If you have purchased a license for this product, you must obtain a license authorization key for each computer on which you are installing the product. See Licensing on page 32. If you have changed the name of the server where SQL-BackTrack for Oracle is installed in a failover environment, you must modify the corresponding hostname entry in the opsconfig.rdf file. See Specifying Node Information for Failover Environments on page 77.
NOTE
If you are already using SQL-BackTrack for Oracle version 4.0.00 or earlier on Linux, you cannot use your existing license authorization key with version 5.0 or later releases. You must run the dthostid command to obtain your ethernet address, and then submit the information to BMC Software to request a new license key. See Obtaining a License Key on page 33.
To Add an Entry to the License File 1 Change to the following directory:

$DTBASE/obacktrack/install/
2 Stop all processes related to SQL-BackTrack for Oracle including the dtlicense,
dtoarchmon, and dtobackup processes.
3 Run the dtoinstall command as follows:

dtoinstall license customize
62
4 At the following prompt, enter y if you are using the product in a RAC
environment. Otherwise, press Enter.
Will you be using this product in an OPS/RAC environment? [Y/N] [N]
NOTE
SQL-BackTrack for Oracle version 5.0.10 supports clustering through Real Application Clusters (RAC), the new generation of Oracle Parallel Server (OPS). SQL-BackTrack for Oracle no longer supports clustering through OPS.
5 At the following prompt, enter the name of your organization or press Enter to
accept the default value:
Enter your organization name (up to 40 characters): [<orgName>]
The dtoinstall command writes the internal serial number and organization name to the serial file located in the $DTBASE/obacktrack/ctl directory.
6 At the following prompt, proceed with one of the following actions:

s s
If you have a license key, press Enter. If you do not have a license key, enter n to install with a 15-day evaluation license. Then, skip to step 11 on page 64.
Do you have your authorization key now? [Yes]
7 At the following prompt, press Enter if this computer is one of your licensed
computers. Otherwise, enter n.
Will this machine be one of your licensed servers? [Yes]
The dtoinstall command displays the computer name and the computer ID as follows:
Machine name: <computerName> Host id: <computerId>
8 At the following prompt, enter the license key that was generated for this
computer:
Enter the authorization key:
63
Setting Up Licensing Notification
The dtoinstall command displays your license information as follows:

Ready to write an entry: Serial number: <serialNumber> Host name: <computerName> Host id: <computerId> Authorization: <licenseKey>
9 At the following prompt, press Enter to verify your information. Otherwise, enter n
and then re-enter your license information.
OK to proceed? [Yes]
10 At the following prompt, enter y to enter license information for an additional

computer. Then repeat step 8 and step 9 on page 64. Otherwise, press Enter.
Are there more servers? [No]
11 At the following prompt, press Enter to write the license information to the license
file. Otherwise, enter n.
Ready to write data to <licenseFile>. OK to proceed? [Yes]
The dtoinstall command updates the license file with the new license entry and then customizes SQL-BackTrack for Oracle with the new license information.
Setting Up Licensing Notification

Use the dtoinstall command to specify the Unix user ID to receive licensing notification messages. These messages are generated when the size of the Oracle database exceeds the size authorized by your SQL-BackTrack for Oracle product license.
Before You Begin

Set the DTBASE environment variable. See Setting Environment Variables for Unix on page 58 for more information.
To Set Up Licensing Notification Messages 1 Change to the directory where the dtoinstall command is located by entering the
following command:
64
Setting Port Numbers for dtlicense and dtoarchmon
2 At the prompt, enter the following command:

dtoinstall notify
3 At the following prompt, enter the e-mail address that will receive the licensing
notification messages.
Enter the e-mail address to which you want licensing notification messages sent []:
4 At the following prompt, press Enter to confirm the e-mail address. Otherwise,
enter n and repeat step 3.
Is this correct ? [Yes]
Setting Port Numbers for dtlicense and dtoarchmon

If the default TCP/IP port settings for the dtlicense and dtoarchmon processes on your Unix computer conflict with the port settings for another process, use the following procedure to create the dthosts file and specify new port numbers.
Before You Begin

Be aware that SQL-BackTrack for Oracle uses the following default port assignments:
s s
4444 for dtlicense 5555 for dtoarchmon
To Specify the Port Numbers for dtlicense and dtoarchmon 1 Use a text editor to create the dthosts file in the following directory:
$DTBASE/obacktrack/ctl/dthosts
2 Assign the ports for the dtlicense and dtoarchmon processes in the dthosts file. The
format of the file is as follows:
begin dtlicense=4444 end dtlicense begin dtoarchmon=5555 end dtoarchmon
3 If you want some computers to use different port assignments, add the computer
name and port number between the begin and end sections for dtlicense and dtoarchmon, as follows:
Chapter 3 Performing Post-Installation Tasks 65
Running the SQL-BackTrack for Oracle Configuration Script
begin dtlicense=<defaultPortNumber> <computerName>=<port> <computerName>=<port> end dtlicense begin dtoarchmon=<defaultPortNumber> <computerName>=<port> <computerName>=<port> end dtoarchmon
4 Save the dthosts file. NOTE

If you are configuring SQL-BackTrack for Oracle for a RAC or failover environment, the dthosts file must contain information about all the nodes in your system environment. The dthosts file must also reside in the same directory on each node.
Running the SQL-BackTrack for Oracle Configuration Script

If you did not run the SQL-BackTrack configuration script postinstall.sh during installation, use this procedure to run the script. This script adds specific entries to files in the /etc directory.
NOTE
If you will be using your SQL-BackTrack for Oracle product in a failover environment, run the configuration script on both the primary node and the failover node.
Before You Begin

Complete the following tasks before configuring your SQL-BackTrack for Oracle product:
s
Install the SQL-BackTrack for Oracle product on the Unix computer.
NOTE
Do not install SQL-BackTrack for Oracle on an NFS-mounted drive.
Log on to the Unix computer as root.
66
SQL-BackTrack for Oracle Post-Installation Tasks on Windows
To Run the SQL-BackTrack for Oracle Configuration Script on Unix 1 Log on as the root user. 2 Change to the directory where the postinstall.sh script is located by entering the
following command:
3 At the command prompt, type the following command:

./postinstall.sh
The configuration script runs and then displays a message indicating that the post-configuration utility completed successfully.
SQL-BackTrack for Oracle Post-Installation Tasks on Windows

Before you can use the SQL-BackTrack for Oracle product on Windows, you might need to perform some or all of the following tasks:
Task Set environment variables on Windows. Add a license key on Windows. Set up operating system authentication for Oracle. Reference page 67 page 69 page 69
Setting Environment Variables for Windows

Use the following procedures to set the environment variables for the location of the SQL-BackTrack for Oracle catalog or the location of the SQL-BackTrack for Oracle temporary directory.
NOTE
If you set an environment variable after the dtoarchmon process is already running, you must restart dtoarchmon. Otherwise, SQL-BackTrack for Oracle might not be able to monitor or back up your archived redo logs.
67
Setting Environment Variables for Windows
To Set the Windows Environment Variables from the Command Prompt

At the command prompt, set each environment variable by using the following syntax. For a list of environment variables, see Table 11 on page 68.
SET <variableName>=<value>
NOTE
If you use this method to set an environment variable, the value of the variable persists only for as long as the current session.
To Set the Windows Environment Variables from the Windows Control Panel 1 From the Windows desktop, choose Start => Settings => Control Panel => System. 2 Click on the Advanced tab and choose Environment Variables. 3 Enter the environment variables and their values by using the information
provided in Table 11. Table 11
Variable DT_ORACATALOG
Optional Environment Variables for Windows

Description Set this environment variable to the location of the SQL-BackTrack for Oracle catalog directory. See the SQL-BackTrack for Oracle User Guide for more information about the catalog. Set this environment variable to the location of the directory that SQL-BackTrack for Oracle uses to store temporary files. On Windows, the default directory location is C:\Documents and Settings\<userProfile>\Local Settings\Temp The <userProfile> variable represents the Windows user profile that you used when installing SQL-BackTrack for Oracle on this computer. Note: Do not specify a directory on an NFS-mounted drive.
DTTEMPDIR
PATH
Set this environment variable if you are running multiple versions of Oracle on a Windows computer. If you are running multiple versions of Oracle, the path information for the version of Oracle that you want to use with SQL-BackTrack for Oracle must come first in your PATH statement.
68
Adding or Updating a License Key on Windows
Adding or Updating a License Key on Windows

Use the following procedure to add a license authorization key or update license information for SQL-BackTrack for Oracle on a Windows computer.
NOTE
If you change the name of the Windows computer on which you are running SQL-BackTrack for Oracle, you must also change the name in the %DT_ORACATALOG%\<dbName>.db\config\opsconfig.rdf file.
Before You Begin

You must obtain a license authorization key for each computer on which you plan to install the product. See Licensing on page 32 for more information.
To Add or Update a License Key on Windows 1 From the Windows desktop, choose Start => Programs => SQL-BackTrack for
Oracle-<version> => Configure.
2 In the SQL-BackTrack Config Utility dialog box, click Add License. 3 In the Add License Information dialog box, type your license authorization key in
the License Key box.
4 In the Add License Information dialog box, click Add.

The information from the top of the dialog box appears in a string in the box at the bottom of the dialog box.
5 Click Save Now, and then click Close. 6 On the SQL-BackTrack Config Utility dialog box, click Done.
Setting Up Operating System Authentication for Windows

To operate properly on Windows, SQL-BackTrack for Oracle requires a connection to the Oracle server as a user with SYSDBA privileges. This connection is also known as operating system authentication.
69
Setting Up Operating System Authentication for Windows
To Set Up Operating System Authentication for Oracle 1 In the init<SID>.ora file, set the REMOTE_LOGIN_PASSWORDFILE parameter to
NONE.
2 In the %ORACLE_HOME%\Network\Admin\sqlnet.ora file, set the

SQLNET.AUTHENTICATION_SERVICES parameter as follows: sqlnet.authentication_services = (nts)
3 Log on to your Windows computer by using a user ID that belongs to the local
Administrators group.
4 In your Windows operating system, create a new local group named ORA_DBA or
ORA_<sid>_DBA, and add the users to the group who will use SQL-BackTrack for
Oracle. The <sid> variable identifies the Oracle database for which you are creating the local group.
5 Log off your computer, and then log on again.

All members of the local group can now connect as a user with SYSDBA privileges by using / without a password. For detailed information about the user authentications required to use SQL-BackTrack for Oracle, see the SQL-BackTrack for Oracle User Guide.
70
Chapter
4
71 71 73 73 74
Configuring RAC Environments for SQL-BackTrack for Oracle

4
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack for Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Database Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Time Zone for RAC Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Manager Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview
The following sections describe the configuration requirements for using the SQL-BackTrack for Oracle product in a Real Application Clusters (RAC) environment:
s s s
SQL-BackTrack for Oracle Configuration on page 71 Oracle Database Software Configuration on page 73 Storage Manager Software Configuration on page 74
SQL-BackTrack for Oracle Configuration

Configure your SQL-BackTrack for Oracle software for use in your RAC environment as follows:
s
Install the SQL-BackTrack for Oracle software on each node in your RAC environment. See Chapter 2, Installing SQL-BackTrack for Oracle, for more information.
Chapter 4
71
SQL-BackTrack for Oracle Configuration
Create the SQL-BackTrack for Oracle catalog on the computer that is the primary node in your RAC environment.
NOTE
BMC Software does not recommend that you create the SQL-BackTrack for Oracle catalog on an NFS-mounted drive.
If you plan to use port numbers other than the default settings for the dtoarchmon and dtlicense processes, create a dthosts file on each node. See Setting Port Numbers for dtlicense and dtoarchmon on page 65. The dthosts file must include all of the port numbers for all of the nodes in your RAC environment. Copy the dthosts file to the following directory on each node:
At the command prompt, start the license validation program (dtlicense) on all nodes of your RAC environment by typing the following command:
$DTBASE/obacktrack/bin/dtlicense -start
For SQL-BackTrack for Oracle to be able to communicate with each node in your RAC database, the dtlicense process must be running on each node. If the dtlicense process is not running on a node, SQL-BackTrack for Oracle assumes that the node is inactive. If dtlicense is not running during a backup, SQL-BackTrack for Oracle attempts to complete the backup, but some of the SQL-BackTrack for Oracle processes required to complete the backup process might not be able to execute. For example, SQL-BackTrack for Oracle might not be able to start the dtoarchmon process on the affected node. If this occurs, SQL-BackTrack for Oracle continues to back up the database, but any archived redo logs that are generated on this node are not backed up. Because the backup does not include a complete set of archived redo logs, you might not be able to perform a complete recovery. For more information about the dtlicense command, see the SQL-BackTrack for Oracle Reference Manual.
s
If you plan to use the SQL-BackTrack for Oracle parameters files to configure the initialization of the product, you must copy this file to the following directory on each node in your RAC environment:
72
Oracle Database Software Configuration
NOTE
The parameters file must contain the same content on each node.
To perform an incremental backup from a secondary node, you must copy the obacktrack_stat directory and the SQL-BackTrack for Oracle catalog from the primary node to the secondary node. SQL-BackTrack for Oracle must be able to access the stat files to perform an incremental backup. SQL-BackTrack for Oracle creates these files in the following directory by default:
$DTBASE/obacktrack/obacktrack_stat

Configure your Oracle database software for use in your RAC environment as follows:
s
Set the following Oracle environment variables on each node in your RAC environment: ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH LIBPATH ORACLE_PSRV
Setting the Time Zone for RAC Environments

To perform a point-in-time (PIT) recovery on a RAC database running on an AIX 5.1 64-bit operating system or an HP-UX 11.00 64-bit operating system, you must set the time zone that Oracle uses to start instances in the specified RAC database. Otherwise, the recovery fails.
To Set the Time Zone for RAC Environments 1 If the Global Services Daemon (GSD) is not already running, start it by using
following command:
gsdctl start
Chapter 4
73
Storage Manager Software Configuration
NOTE
The daemon must be running before you can set the time zone.
2 Set the correct time zone by using the appropriate command for your Oracle
version.
3 Stop the GSD by using the following command:

gsdctl stop
4 Restart the GSD.

Configure your enterprise storage-manager software for use in your RAC environment as follows:
s
If you want to back up your data to a supported enterprise storage-manager product, install the storage-manager client software on each node in your RAC environment. For example, if you are using IBM Tivoli Storage Manager for backups, the IBM TSM client must be installed on the primary node and on all of the secondary nodes.
If you want to back up your data to a LEGATO NetWorker server, add all of the nodes in your RAC environment and the remote user name and password used to initiate the backup to the remote access list on the LEGATO NetWorker server. If you want to back up your data to a VERITAS NetBackup server, you must add all of the RAC nodes to the NetBackup server class/policy client list.
For more information about configuring and using your SQL-BackTrack for Oracle module software, refer to the appropriate SQL-BackTrack for Oracle module documentation.
74
Chapter
5
75 75 77 79 79 80
Configuring Failover Environments for SQL-BackTrack

5
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL-BackTrack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Node Information for Failover Environments. . . . . . . . . . . . . . . . . . . . Starting Services during a Node Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Database Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Manager Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview
The following sections describe the configuration requirements for using the SQL-BackTrack product in an operating system cluster environment that is set up to support a failover strategy for Oracle:
s s s
SQL-BackTrack Configuration on page 75 Oracle Database Software Configuration on page 79 Storage Manager Software Configuration on page 80
SQL-BackTrack Configuration
Configure the SQL-BackTrack product for use in a failover environment as follows:
s
Install the SQL-BackTrack for Oracle software on a shared disk that is accessible to both the primary node and the failover node. See Chapter 2, Installing SQL-BackTrack for Oracle, for more information.
Chapter 5 Configuring Failover Environments for SQL-BackTrack
75
SQL-BackTrack Configuration
Create the SQL-BackTrack catalog on a shared disk that both the primary node and the failover node can access.
TIP
Back up the SQL-BackTrack catalog on a regularly scheduled basis (for example, after every database backup). Also, make an extra backup of the catalog whenever a change is made to the catalog configuration.
Verify that the license file has an entry for both the primary node and the failover node. The license file is located in the following directory:
The entries in the license file should appear as follows:

begin license=<serialNumber> name=<primaryMachineName> machine-id=<PLATFORM>-<computerId> key=<licenseKey> end license begin license=<serialNumber> name=<failoverMachineName> machine-id=<PLATFORM>-<computerId> key=<licenseKey> end license
To add license information for a node to the license file, see Updating License Information for Unix on page 62.
s
If you want to use archive log monitoring, verify that the dtoarchmon process is running on the primary node. If the primary node fails, you must manually start the dtoarchmon process on the failover node. See the SQL-BackTrack for Oracle Reference Manual for more information about starting dtoarchmon.
NOTE
To force the dtoarchmon process to start automatically on the failover node, include the dtoarchmon command in your failover startup scripts.
Edit the SQL-BackTrack catalog configuration file (opsconfig.rdf) to include information about each failover node in your failover environment. For more information, see Specifying Node Information for Failover Environments on page 77.
76
Specifying Node Information for Failover Environments
To perform an incremental backup after a failover event, SQL-BackTrack must be able to access the stat files. If you did not install SQL-BackTrack on a shared disk, you must set the DT_OBACKTRACK_STAT environment variable to point to a directory that both the primary node and the failover node can access. SQL-BackTrack creates these files in the following directory by default:
$DTBASE/obacktrack/obacktrack_stat

Use the following procedure to specify the primary and failover node for your failover environment in the SQL-BackTrack catalog configuration file (opsconfig.rdf).
Before You Begin

Consider the following information before editing your opsconfig.rdf file:
s
You can edit the opsconfig.rdf configuration file only after creating the SQL-BackTrack catalog. Your backup will fail if you do not use the correct syntax in the opsconfig.rdf file.
To Specify the Node Information for a Failover Environment 1 Change to the following directory:
$DT_ORACATALOG/<dbName>.db/config
The $DT_ORACATALOG environment variable represents the SQL-BackTrack catalog directory and <dbName> represents the name of the Oracle database. For example, for the SONOMA database, type the following command:
cd $DT_ORACATALOG/SONOMA.db/config
2 Use a text editor to open the opsconfig.rdf file.

The file contains a block for the current node, as shown in the following example:
begin node=<computerName> oraclehome=<directory> oraclesid=<instanceName> initora=<path/fileName> thread=<threadNumber> end node
77
3 Create a copy of this block for each node, and edit each block to reflect the
appropriate values for each node:
Parameter begin node=<computerName> oraclehome=<directory> oraclesid=<instanceName> initora=<path/filename> thread=<threadNumber> Description begins a node definition and identifies the name of the node the location of the ORACLE_HOME directory (where the Oracle software is located) the name of the Oracle database instance running on this node the path and file name of the Oracle init.ora file the thread number for the Oracle instance on this node You can usually find the thread number in the Oracle init.ora file. Note: The thread number for the primary node and the failover node should be the same. end node ends a node definition
The following example shows an opsconfig.rdf file that is configured for a failover environment with two nodes: a primary node (pnode) and a failover node (fnode).
; This is a required BackTrack file; DO NOT DELETE! ; begin node=pnode.bmc.com oraclehome=/oracle/product/9.2.0 oraclesid=HACMP920 initora=/oracle/product/9.2.0/dbs/HACMP920 thread=1 end node begin node=fnode.bmc.com oraclehome=/oracle/product/9.2.0 oraclesid=HACMP920 initora=/oracle/product/9.2.0/dbs/HACMP920 thread=1 end node ;; RDFEOF ;;
4 Save the opsconfig.rdf file. NOTE

BMC Software recommends that you make a backup copy of the SQL-BackTrack catalog after making these changes.
78
Starting Services during a Node Failure
Starting Services during a Node Failure

In certain cases, it is necessary to start services on the secondary node to ensure that the services continue to run during a node failure. In the event of a node failure, you must start the following services:
s
JBoss service, which is required for the Enterprise Policy Monitor (EPM) BMC Remote Execution (GRX) Agent, which is needed to run the obacktrack program from the SmartDBA Console
To Start the JBoss Service 1 Copy all entries following the #BMC-PDM-DELIMITER line from the /etc/bmc_pdm
file on the source computer to target computer.
2 Start the JBoss service by running the following script:

$DTBASE/obacktrack/ebr/bin/startup.sh
NOTE
If you want to start the JBoss service automatically after every reboot, copy the entry for the JBoss service from the /etc/inittab file on the source computer to the target computer. This entry begins with the string j<n>: where <n> is a number.
To Start the BMC Remote Execution (GRX) Agent 1 From the primary node, copy the entries in the /etc/services and /etc/inetd.conf files
to the secondary node.
2 Run the obtconfig.sh script from the secondary node.

Configure your Oracle database software for use in a failover environment as follows:
NOTE
If you want to perform a cold backup or any type of recovery of an Oracle database in a Hewlett-Packard or Sun cluster environment, the HP or Sun cluster-management software must not be monitoring any of the Oracle instances. Otherwise, during the backup or recovery the shared disk switches from the primary node to the failover node.
79
Verify that your Oracle database software is installed and configured for use in a failover environment. The shared disk should contain all of the database files, including the control file, redo logs, archive logs, and data files. Set the following Oracle environment variables on the primary node in your failover environment: ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH LIBPATH
NOTE
If the failover node is enabled because the primary node has failed, you must set these variables on the failover node.
For more information about setting these environment variables, see Setting Environment Variables for Unix on page 58.

Configure your enterprise storage-manager software for use in a failover environment as follows:
s
If you want to back up your data to a supported enterprise storage-manager product, install the storage-manager client software on each node in your failover environment. For example, if you are using IBM Tivoli Storage Manager for backups, the IBM TSM client must be installed on the primary node and all of the secondary nodes.
If you want to back up your data to a LEGATO NetWorker server, add all of the nodes in your failover environment and the remote user name and password used to initiate the backup to the remote access list on the LEGATO NetWorker server. If you want to back up your data to a VERITAS NetBackup server, you must add the primary node and the failover node to the NetBackup server class/policy client list. Also, if you are using a logical node in your failover environment, you must add the logical node to the class/policy client list.
For more information about configuring and using your SQL-BackTrack module software, refer to the appropriate SQL-BackTrack module documentation.
80
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
archive log monitoring failover environments 76 RAC environments 72 upgrading SQL-BackTrack 28, 30
D
deleting the catalog directory 29, 30 directories, catalog 12 directory structure, SQL-BackTrack 45 disk drive requirements 25 disk media, supported 27 documentation conventions 12 online Help 11 related 11 DT_DISK_FILESIZE environment variable 59 DT_OBACKTRACK_HOME environment variable 59 DT_OBACKTRACK_STAT environment variable 60 DT_ORACATALOG environment variable Unix 60 Windows 68 DTBASE environment variable 59 dthostid command 28, 34, 62 dthosts file editing 65 example 65 location 65 RAC, configuring for 72 dtlicense command 46, 72 dtlicense process port number, setting 65 RAC requirements 72 dtoarchmon command 76 dtoarchmon process port number, setting 65 RAC configuration 72 starting in failover environments 76 dtoinstall command 62, 63, 64, 65 dtoverifyinstall command 45 DTSHMEM environment variable 61 DTTEMPDIR environment variable Unix 61 Windows 68
B
backup media 27 BMC Remote Execution (GRX) Agent, uninstalling on Unix 50, 52, 79 BMC Software, contacting 2
C
catalog, SQL-BackTrack allocating space for 26 backing up 50, 53 directory 12 in a failover environment 76 reusing an existing 28, 30 Unix, setting location for 60 Windows, setting location for 68 CD drive mount commands for Unix 36 requirements 25 cluster environments 71, 79 commands dthostid 28, 34, 62 dtlicense 46, 72 dtoarchmon 76 dtoinstall 62, 63, 64, 65 dtoverifyinstall 45 gsdctl 73 hostid 34 ipconfig 33 mount 36 uname 33 configuration script 66 conventions, documentation 12 customer support 3
Index
81
E
electronic documentation online Help 11 Enterprise Policy Monitor 16 Integration Package 16 Integration Package, uninstalling 51 environment variables (Unix) DT_DISK_FILESIZE 59 DT_OBACKTRACK_HOME 59 DT_OBACKTRACK_STAT 60 DT_ORACATALOG 60 DTBASE 59 DTSHMEM 61 DTTEMPDIR 61 EPM_USER_ID 24, 36 LANG 59 LD_LIBRARY_PATH 59 LIBPATH 59 SHLIB_PATH 59 environment variables (Windows) DT_ORACATALOG 68 DTTEMPDIR 68 EPM. See Enterprise Policy Monitor EPM_USER_ID environment variable 24, 36
H
hardware requirements, SQL-BackTrack 25
I
IBM Tivoli Storage Manager 19 installation requirements authorization 24 disk drive 25 memory 25 operating system 26 Oracle 26 installing SQL-BackTrack considerations 27 in a failover environment 21 in a RAC environment 19 on multiple versions 31 on Unix 19, 3642 on Windows 23, 4244 upgrading 28
L
LANG environment variable 59 LD_LIBRARY_PATH environment variable 59 LEGATO NetWorker 19 LIBPATH environment variable 59 licenses, updating for Unix 6264 for Windows 69 licensing evaluation 32 guidelines 32 obtaining license keys 33 RAC 32 reusing license keys (Unix) 29 reusing license keys (Windows) 31 updating server names 32
F
failover environments cluster restrictions 79 configuration guidelines 75 dtoarchmon, starting in 76 environment variables, setting for 80 installation 21 LEGATO NetWorker configuration 80 LEGATO NetWorker server 80 node information, specifying 77, 79 opsconfig.rdf 76 Oracle database configuration 79 overview 22, 75 SQL-BackTrack configuration 75 storage-manager software configuration 80 VERITAS NetBackup configuration 80 VERITAS NetBackup server 80 files dthosts 65 parameters 29, 30 Readme-JRE.html 44 Readme-JRE.txt 44 SmartDBA services 52
M
memory requirements 25 mounting a CD on Unix 36
O
OBSI modules. See SQL-BackTrack modules obtinstall.sh script 37 obtuninstall script 51 online Help 11 operating system authentication, Windows 69 opsconfig.rdf file for failover environments 77, 79 oracatalog directory 29, 30
G
gsdctl command 73
82
P
parameters files for configuring SQL-BackTrack 72 reusing on Unix 29 reusing on Windows 30 port numbers, setting for SQL-BackTrack 72 postinstall.sh script 67 post-installation tasks Unix 5767 Windows 6770 primary node 20 in failover environments 22 in RAC environments 20 product support 3
support, customer 3
T
tape media, supported 27 technical support 3 TSM. See IBM Tivoli Storage Manager
U
uninstalling BMC Remote Execution (GRX) Agent 52 Enterprise Policy Monitor Integration Package 51 SQL-BackTrack on Unix 50 on Windows 53 Unix installation considerations 31 installing SQL-BackTrack 3642 reusing license keys 29 uninstalling BMC Remote Execution (GRX) Agent 52 Enterprise Policy Monitor Integration Package 51 SQL-BackTrack 50 updating SQL-BackTrack license information 6264 upgrading SQL-BackTrack 28 upgrading SQL-BackTrack on Unix 28 on Windows 30
R
RAC. See Real Application Clusters Readme-JRE.html file 44 Readme-JRE.txt file 44 Real Application Clusters dthosts file 72 dtlicense process 72 dtoarchmon, starting 72 installation, SQL-BackTrack 19 license key for SQL-BackTrack 32 Oracle database configuration 73 overview 19, 71 parameters file location 72 primary node 20 secondary node 20 SQL-BackTrack configuration 71 storage-manager software configuration 74 VERITAS NetBackup configuration 74 related documentation 11
V
verifying installation on Unix 45 VERITAS NetBackup 19
S
scripts obtinstall.sh 37 obtuninstall 51 postinstall.sh 67 secondary node 20 SHLIB_PATH environment variable 59 SmartDBA files 52 SmartDBA Integration Package 15 SmartDBA Recovery Management components 15 SQL-BackTrack modules LEGATO NetWorker 74 RAC configuration 74 software requirements 27 supported backup media 27 VERITAS NetBackup 74 stat files 26
W
Windows installing SQL-BackTrack 42, 43, 44 reusing license keys 31 setting up operating system authentication 69 uninstalling SQL-BackTrack 53 updating license information 69 upgrading SQL-BackTrack 30
Index
83
84
Glossary
A
application server See BMC Application Server.
B
backup A copy of the information in a database that is required to rebuild the database if the database becomes unusable. With SQL-BackTrack, you can perform either a physical backup or a logical backup. BMC Application Server Processes incoming requests and returns responses to each client. Any client may access a BMC Application Server, which runs on port 8082 by default. See also client.
C
catalog A set of files that contains the SQL-BackTrack for Oracle backup and recovery information, such as backup and recovery preferences, backup history, and backup device definitions. client The SmartDBA graphical user interface (GUI) or console. A user downloads the client as a locally installed application and accesses a BMC Application Server through an Internet browser. See also BMC Application Server. console See client. customize The process in which the SQL-BackTrack for Oracle license information is applied to the product binaries. You cannot use the SQL-BackTrack for Oracle product if this process has not been completed.
Glossary
85
F
failover environment An environment consisting of two hosts: a primary node and a secondary node. These nodes and other resources act like a single system and operate nearly continuously. See primary node and failover node. failover node The node in a failover environment that takes the workload from the primary node, if the primary node becomes unavailable.
L
license authorization key The 25-digit key, which is generated from the machine name and machine ID that authorizes the use of the SQL-BackTrack product.
O
OBSI module See SQL-BackTrack for Oracle Module.
P
primary node For RAC, the first RAC node that SQL-BackTrack for Oracle tries to use for a backup or recovery operation. In a failover environment, this term refers to the node that processes the workload until the node becomes unavailable. See failover node.
R
RAC See Real Application Clusters. Real Application Clusters (RAC) This term refers to the feature in Oracle 9i that allows users on multiple nodes to access the same database simultaneously. recovery The process of restoring one or more databases or database objects from backup files.
S
script A set of commands and options that perform a backup or recovery operation when executed. A script can be saved in a file for future execution.
86
secondary node Any node other than the primary node in a RAC environment. SmartDBA Console A graphical user interface (GUI) in which you can perform SQL-BackTrack for Oracle tasks formerly available only through the obacktrack program menus. SQL-BackTrack Module Provides the software interface through which SQL-BackTrack communicates with physical backup devices and enterprise storage-management systems. SQL-BackTrack parameters file Includes parameters related to multiple functions such as SQL-BackTrack reports, the SQL-BackTrack catalog, Oracle, and so on. It applies to multiple databases if multiple databases are defined in your SQL-BackTrack catalog. The parameters file is also referred to as the ctl/parameters file because it must be located in the ctl directory.
Glossary
87
88
END USER LICENSE AGREEMENT

NOTICE
BY OPENING THE PACKAGE, INSTALLING, PRESSING AGREE OR YES OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT. This Agreement (Agreement) is between the entity or individual entering into this Agreement (You) and BMC Software Distribution, Inc., a Delaware corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity (BMC). You includes you and your Affiliates. Affiliate is defined as an entity which controls, is controlled by or shares common control with a party. IF MORE THAN ONE LICENSE AGREEMENT COULD APPLY TO THE PRODUCT, THE FOLLOWING ORDER OF LICENSE AGREEMENT PRECEDENCE APPLIES: (1) WEB BASED LICENSE AGREEMENT WITH BMC, (2) WRITTEN LICENSE AGREEMENT WITH BMC, (3) SHRINK-WRAP LICENSE AGREEMENT WITH BMC PROVIDED WITH THE PRODUCT, AND (4) THIS ELECTRONIC LICENSE AGREEMENT WITH BMC. In addition to the restrictions imposed under this Agreement, any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product. PRODUCT AND CAPACITY. Software means the object code version of the computer programs provided, via delivery or electronic transmission, to You. Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and error corrections. Documentation means all written or graphical material provided by BMC in any medium, including any technical specifications, relating to the functionality or operation of the Software. Product means the Software and Documentation. License Capacity means the licensed capacity for the Software with the pricing and other license defining terms, including capacity restrictions, such as tier limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the Software. For licenses based on the power of a computer, You agree to use BMC's current computer classification scheme, which is available at http://www.bmc.com or can be provided to You upon request. ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC. LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive, non-transferable, perpetual (unless a term license is provided on an order) license for each copy of the Software, up to the License Capacity, to do the following: A. install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license; B. operate the Software solely for processing Your own data in Your business operations; and C. make one copy of the Software for backup and archival purposes only (collectively a License). If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new software programs for Your internal purposes or otherwise consistent with the License. BMC grants You a license to use the Documentation solely for Your internal use in Your operations. LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and Your payment of applicable fees. There is no additional warranty period or free support period for license upgrades. RESTRICTIONS: You agree to NOT: A. disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code; B. distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment, or processing the data of third parties, or for rental, lease, or sublicense); or C. provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMC's prior written approval, unless prohibited by local law. TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license consists solely of a nonexclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC or, if not specified, a 30 day time period (Trial Period) only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee; and (ii) Your use of the Product is on an AS IS basis without any warranty, and BMC, ITS AFFILIATES AND RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE (Trial License). BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this Product automatically expires. If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a capacity-based license to the Product for a fee. TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must uninstall the Software, and either certify the destruction of the Product or return it to BMC. OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all intellectual property, informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to You. Products are protected by applicable copyright, trade secret, and industrial and intellectual property laws. BMC reserves any rights not expressly granted to You herein. CONFIDENTIAL AND PROPRIETARY INFORMATION. The Products are and contain valuable confidential information of BMC (Confidential Information). Confidential Information means non-public technical and non-technical information relating to the Products and Support, including, without limitation, trade secret and proprietary information, and the structure and organization of the Software. You may not disclose the Confidential Information to third parties. You agree to use all reasonable efforts to prevent the unauthorized use, copying, publication or dissemination of the Product. WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the Software. EXCLUSIVE REMEDY. BMCs entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective
Software within a reasonable period of time, or if BMC cannot remedy or replace such defective copy of the Software, then BMC shall refund the amount paid by You for the License for that Software. BMC's obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED AS IS. BMC, ITS AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE CORRECTED. DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT, AND/OR THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE OR LOSS OF USE OF DATA), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW. LIMITS ON LIABILITY. BMCS AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO THE PRODUCT. SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week) (Support). You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. There is a free support period during the one year warranty period. A. Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its thencurrent operating specifications; and (ii) BMC provides new releases or versions, so long as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software made available by BMC. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement fee of 1.5 times what You would have paid if You were enrolled in Support during that time period. B. Fees. The annual fee for Support is 20% of the Softwares list price less the applicable discount or a flat capacity based annual fee. BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date. VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or electronically, detailing Your use of the Software in accordance with this Agreement, including, without limitation, the License Capacity. BMC may, at its expense, perform an audit, at your facilities, of Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You have underpaid fees, You agree to pay such underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also pay BMCs reasonable costs of conducting the audit. EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any underlying information or technology except in full compliance with all United States, foreign and other applicable laws and regulations. GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in the State of New York, if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in the Province of Ontario, if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the Americas Region); (c) in Singapore, if you acquired the License in Japan, South Korea, Peoples Republic of China, Special Administrative Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India, Australia, New Zealand, or Thailand (collectively, Asia Pacific Region); or (d) in the Netherlands, if you acquired the License in any other country not described above. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety. ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH, SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY PENDING THE ARBITRATORS AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTYS CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY. U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is commercial computer software as that term is described in 48 C.F.R. 252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulations (FAR) and its successors. If acquired by or on behalf of any agency within the Department of Defense (DOD), the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors. MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice, unless otherwise provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including sales, use, duty, tariffs, customs, withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than taxes based on BMCs net income) imposed in connection with the Product and/or the Support. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements, whether oral, written or displayed electronically, concerning the Product and related subject matter. No modification or waiver of any provision hereof will be effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a third party without BMCs prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the provisions will remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Les parties exigent que la prsente convention ainsi que les documents qui sy rattachent soient rdigs en anglais.
SW Click EULA 071102
Third Party Legal Notices and Disclaimers

This section contains third-party legal notices and disclaimers for all products that are bundled with the SmartDBA Console.
Cryptix
Copyright 1995, 1996, 1997, 1998, 1999, 2000 The Cryptix Foundation Limited. All rights reserved. 1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Apache Software Foundation

The Apache Software License, Version 1.1 Copyright 2000 The Apache Software Foundation. All rights reserved. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>. Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
Hypersonic SQL
This product includes Hypersonic SQL. Copyright 2001, Regents of the University of California All rights reserved. s s s Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the University of California, Berkeley nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Sun Microsystems, Inc.

Copyright 2003 Sun Microsystems, Inc. All Rights Reserved. Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived from this software without specific prior written permission. This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You acknowledge that this software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility.
Tanuki Software
This product includes the Tanuki Software product found at http://www.wrapper.tanukisoftware.org and this product is distributed to us pursuant to the following terms and conditions: Copyright (c) 1999, 2004 Tanuki Software Permission is hereby granted, free of charge, to any person obtaining a copy of the Java Service Wrapper and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sub-license, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Portions of the Software have been derived from source code developed by Silver Egg Technology under the following license: Copyright (c) 2001 Silver Egg Technology Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sub-license, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
JBoss Inc. Software (GNU Lesser General Public License)

Certain software used by this program is: Provided by JBoss Inc. and is subject to its copyrights and those of its licensors; Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA The above component is licensed under the terms of the GNU Lesser General Public License version 2.1 which is included on the distribution media. NO WARRANTY BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Notes
*49487* *49487* *49487* *49487*

*49487*

Obt5010 Install Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Obt5010 Install Guide

Uploaded by

Copyright:

Available Formats

SmartDBA Recovery Management: SQL-BackTrack for Oracle

October 15, 2004

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted Rights Legend

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

About This Book

The product software also offers online Help for

About This Book

SQL-BackTrack for Oracle Release Notes

SQL-BackTrack for Oracle User Guide SQL-BackTrack Module user guides

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

Products and Components

SQL-BackTrack for Oracle

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

SmartDBA Recovery Management Components

SmartDBA Recovery Management Components

SmartDBA Recovery Management components

SmartDBA Console agents and services SmartDBA Integration Package on page 15

SmartDBA Integration Package

Installation Task Map

EPM Integration Package

Installation Task Map

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

Installation Task Map

SQL-BackTrack for Oracle Installation Task Map

Install the SmartDBA client.

Do you want to use SQL-BackTrack from the SmartDBA Console?

yes SmartDBA Recovery Management: Getting Started

Perform the post-installation steps.

Complete post-installation tasks.

Chapter 3, Performing Post-Installation Tasks

SQL-BackTrack for Oracle Installation Task Map (continued)

Configure RAC environment for SQL-BackTrack for Oracle.

Configure failover environment for SQL-BackTrack for Oracle.

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

Installing on a Single Unix Computer

Installing on a Single Unix Computer

Installing in a RAC Environment (Unix)

Installing in a RAC Environment (Unix)

Configuring the Primary Node

Configuring Secondary Nodes

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

Installing in a Failover Environment (Unix)

SQL-BackTrack for Oracle in a RAC Environment

Installing in a Failover Environment (Unix)

Installing in a Failover Environment (Unix)

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

Installing on a Windows Computer

Installing on a Windows Computer

Operating System Authorization Requirements

Operating System Type Authorization Required

SmartDBA Recovery Management: SQL-BackTrack for Oracle Installation Guide

The disk drive is not an NFS-mounted drive.

Supported Operating Systems and Oracle Software

Supported Operating Systems and Oracle Software