Ibm tivoli storage manager for databases data protection for oracle for windows installation and user's guide version 5.4.1

Tivoli Storage Manager
®

for Databases

Version 5 Release 4

Data Protection for Oracle for Windows
Installation and User’s Guide

SC32-9065-02

Note
Before using this information and the product it supports, read the general information under “Notices” on page 61.

This edition applies to Version 5, Release 4, Modification 1.0, of IBM Tivoli Storage Manager for Databases Data
Protection for Oracle for Windows XP or Windows Server 2003 (product number 5608-APD) and to all subsequent
releases until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 1998, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Summary of changes . . . . . . . . . v 3. Define Tivoli Storage Manager options in the
| Technical changes for Version 5.4.1 . . . . . . . v dsm.opt file . . . . . . . . . . . . . . 14
Required options . . . . . . . . . . . 15
About this guide . . . . . . . . . . vii Other options to consider . . . . . . . . . 15
4. Define Tivoli Storage Manager policy
Who should read this guide . . . . . . . . . vii
requirements . . . . . . . . . . . . . . 17
Publications . . . . . . . . . . . . . . vii
5. Initialize the password with a Tivoli Storage
IBM Tivoli Storage Manager library . . . . . vii
Manager server . . . . . . . . . . . . . 19
Accessing terminology online . . . . . . . ix
Accessing publications online . . . . . . . ix
Ordering publications . . . . . . . . . . ix Chapter 4. Using RMAN and Data
Tivoli Technical Training . . . . . . . . . x Protection for Oracle. . . . . . . . . 21
Accessibility . . . . . . . . . . . . . . x Invoking RMAN. . . . . . . . . . . . . 21
Support information . . . . . . . . . . . . x Scripts . . . . . . . . . . . . . . . . 21
IBM Tivoli Storage Manager Web site . . . . . x Example . . . . . . . . . . . . . . 22
IBM Tivoli Storage Manager for Databases Web Using the Duplex Copy function . . . . . . . 22
site . . . . . . . . . . . . . . . . x Removing old backups . . . . . . . . . . 24
Conventions used in this book . . . . . . . . x Example . . . . . . . . . . . . . . 24
Typeface conventions . . . . . . . . . . xi Management class options affecting object
Reading syntax diagrams . . . . . . . . . . xi removal . . . . . . . . . . . . . . 24

Chapter 1. Introducing Data Protection Chapter 5. Using the utilities . . . . . 25
for Oracle . . . . . . . . . . . . . . 1 Command line syntax and characteristics . . . . 25
Understanding Tivoli Storage Manager . . . . . 1 TDPOCONF . . . . . . . . . . . . . . 26
Overview of Data Protection for Oracle . . . . . 2 Password command . . . . . . . . . . 26
RMAN and Data Protection for Oracle . . . . . 2 Showenvironment command . . . . . . . 27
LAN-free data transfer . . . . . . . . . . 3 TDPOSYNC . . . . . . . . . . . . . . 28
Migration and coexistence . . . . . . . . . 3 Considerations . . . . . . . . . . . . 29
Syncdb Command . . . . . . . . . . . 30
Chapter 2. Installing Data Protection for
Oracle . . . . . . . . . . . . . . . 5 Appendix A. Quick configuration guide 33
Windows x86 environment . . . . . . . . . 6
Operating system requirements . . . . . . . 6 Appendix B. Using the Tivoli Storage
Hardware requirements . . . . . . . . . . 6 Manager scheduler . . . . . . . . . 35
Software requirements . . . . . . . . . . 6 Setting up a schedule . . . . . . . . . . . 35
Communication methods . . . . . . . . . 6 Part I: On the Tivoli Storage Manager server . . 36
Windows x86_64 environment . . . . . . . . 7 Part II: On the workstation with the Oracle
Operating system requirements . . . . . . . 7 Server: . . . . . . . . . . . . . . . 36
Hardware requirements . . . . . . . . . . 7
Software requirements . . . . . . . . . . 7 Appendix C. Support information . . . 41
Communication methods . . . . . . . . . 7 What to do when you encounter a problem . . . 41
Windows Itanium 2 environment (64-bit) . . . . . 8 Searching knowledge bases . . . . . . . . . 42
Operating system requirements . . . . . . . 8 Searching the information center . . . . . . 42
Hardware requirements . . . . . . . . . . 8 Searching the Internet . . . . . . . . . . 42
Software requirements . . . . . . . . . . 8 Obtaining fixes . . . . . . . . . . . . . 43
Communication methods . . . . . . . . . 8 Receiving weekly support updates . . . . . . 43
Installing Data Protection for Oracle . . . . . . 9 Contacting IBM Software Support . . . . . . . 44
Determining the business impact . . . . . . 45
Chapter 3. Configuring Data Protection Describing problems and gathering information 45
for Oracle . . . . . . . . . . . . . 11 Submitting problems . . . . . . . . . . 46
1. Define Data Protection for Oracle options in the
tdpo.opt file . . . . . . . . . . . . . . 11 Appendix D. Accessibility . . . . . . 47
Available options . . . . . . . . . . . 12 Navigating the interface using the keyboard . . . 47
2. Register the Data Protection for Oracle node to a Magnifying what is displayed on the screen . . . 47
Tivoli Storage Manager server . . . . . . . . 13

© Copyright IBM Corp. 1998, 2007 iii

Appendix E. Messages . . . . . . . . 49 Trademarks . . . . . . . . . . . . . . 63

Notices . . . . . . . . . . . . . . 61 Index . . . . . . . . . . . . . . . 65

iv IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

Summary of changes
This section summarizes changes made to the Data Protection for Oracle product
and this publication. Changes to the text since the SC32-9065-01 version are
indicated by vertical lines (|) in the margin to the left of the change.

| Technical changes for Version 5.4.1
| The following changes have been made to this publication:
| Scheduler procedure
| The batch file (orcsched.cmd) example and settings have changed. See
| Appendix B, “Using the Tivoli Storage Manager scheduler,” on page 35 for
| detailed information.

© Copyright IBM Corp. 1998, 2007 v

vi IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

About this guide
The subject of this publication is Data Protection for Oracle, a component of the IBM
Tivoli Storage Manager for Databases product.

Data Protection for Oracle performs online or offline backups of Oracle 9i and
Oracle 10g databases to Tivoli Storage Manager storage. This integration with the
RMAN Media Management API maximizes the protection of data, thus providing
a comprehensive storage management solution.

Tivoli Storage Manager is a client-server licensed product that provides storage
management services in a multi-platform computer environment.

Throughout this document, the term Windows® (unless otherwise specified) refers
to the following operating systems:
v Windows XP Server
v Windows Server 2003

Who should read this guide
The target audience for this publication are system installers, system users, Oracle
database administrators, Tivoli Storage Manager administrators, and system
administrators.

In this book, it is assumed that you have an understanding of the following
applications:
v Oracle Server
v Tivoli Storage Manager server
v Tivoli Storage Manager backup-archive client
v Tivoli Storage Manager Application Program Interface
It is also assumed that you have an understanding of one of the following
operating systems:
v Windows XP Server
v Windows Server 2003

Publications
This section lists related IBM Tivoli Storage Manager publications. It also describes
how to access Tivoli® publications online and how to order Tivoli publications.

IBM Tivoli Storage Manager library
The following documents are available in the IBM Tivoli Storage Manager library:
v IBM Tivoli Storage Manager for Windows Backup-Archive Client Installation and
User’s Guide
Provides information for an end-user to install, configure, and use the Tivoli
Storage Manager client on Windows operating systems.
v IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation
and User’s Guide
Provides information for an end-user to install, configure, and use the Tivoli
Storage Manager client on UNIX and Linux operating systems.

© Copyright IBM Corp. 1998, 2007 vii

v IBM Tivoli Storage Manager for Windows Administrator’s Guide
Provides concepts and procedures for configuring and customizing the Tivoli
Storage Manager server on Windows operating systems.
v IBM Tivoli Storage Manager for Windows Administrator’s Reference
Provides details about administrative commands, server options, and server
utilities for Tivoli Storage Manager server on Windows operating systems.
v IBM Tivoli Storage Manager for AIX Administrator’s Guide
Storage Manager server on AIX operating systems.
v IBM Tivoli Storage Manager for AIX Administrator’s Reference
utilities for Tivoli Storage Manager server on AIX operating systems.
v IBM Tivoli Storage Manager for Sun Solaris Administrator’s Guide
Storage Manager server on Sun Solaris operating systems.
v IBM Tivoli Storage Manager for Sun Solaris Administrator’s Reference
utilities for Tivoli Storage Manager server on Sun Solaris operating systems.
v IBM Tivoli Storage Manager Messages
Provides explanations and suggested actions for messages issued by the Tivoli
Storage Manager server program for storage management services, the
administrative client graphical user interface, administrative command line
client, data protection clients, and backup-archive client.
v IBM Tivoli Storage Manager: Problem Determination Guide
This guide describes how to diagnose problems with Tivoli Storage Manager.
v IBM Tivoli Storage Manager Using the Application Program Interface
Provides information to help you add Tivoli Storage Manager application
program interface calls to an existing application and to write programs with
general-use program interfaces that obtain the services of Tivoli Storage
Manager.
v IBM Tivoli Storage Manager for SAN for AIX Storage Agent User’s Guide
Provides an overview of LAN-free data transfer and detailed explanations about
configuring and using the Tivoli Storage Manager client, storage agent, and
server.
v IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent User’s Guide
server.
v IBM Tivoli Storage Manager for SAN for Linux Storage Agent User’s Guide
server.
v IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent User’s Guide
server.
v IBM Tivoli Storage Manager for SAN for Windows Storage Agent User’s Guide

viii IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

server.

Accessing terminology online
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online
The product CD contains the publications that are in the product library. The
format of the publications is PDF, HTML, or both. To access the publications using
a Web browser, open the infocenter.html file. The file is in the appropriate
publications directory on the product CD.

IBM® posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click the <Tivoli Storage Manager> link
to access the product library at the Tivoli software information center.

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

Ordering publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:
v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli
publications.

About this guide ix

Tivoli Technical Training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.

For additional information, see the appendix, Appendix D, “Accessibility,” on page
47.

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v Contacting IBM Software Support: If you still cannot solve your problem, and
you need to work with someone from IBM, you can use a variety of ways to
contact IBM Software Support.

For more information about these three ways of resolving problems, see
Appendix C, “Support information,” on page 41.

IBM Tivoli Storage Manager Web site
Technical support information and publications are available at the following
address: http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html

By accessing the Tivoli Storage Manager home page, you can access subjects that
interest you. You can also keep up-to-date with the newest Tivoli Storage Manager
product information.

IBM Tivoli Storage Manager for Databases Web site
The IBM Tivoli Storage Manager for Databases Web site contains a knowledge base
of articles and information related to backup and restore issues. Access this
information at:
www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManagerforDatabases.html

Conventions used in this book
This guide uses several conventions for special terms and actions, operating
system-dependent commands and paths.

x IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Commands, keywords, authorization roles, or other information that you
must use.
v Example: Log on to the server as root user.
italics
v Values or variables that you must provide.
v Emphasized words and phrases.
v Example: The node name of the production node and backup node must not
be the same.
bold italics
v Options and parameters.
v Example: Specify the value for the compression option.
monospace
v Directories, parameters, URLs, and output examples.
v Example: The product is installed in the C:program
filestivolitsmclientba directory.
UPPER CASE
v Environment variables associated with Tivoli Storage Manager, operating
systems, or Oracle Server.
v Example: Make sure the DSM_DIR environment variable is set correctly.

Reading syntax diagrams
This section describes how to read the syntax diagrams used in this book. To read
a syntax diagram, follow the path of the line. Read from left to right, and top to
bottom.
v The ─── symbol indicates the beginning of a syntax diagram.
v The ─── symbol at the end of a line indicates the syntax diagram continues on
the next line.
v The ─── symbol at the beginning of a line indicates a syntax diagram continues
from the previous line.
v The ─── symbol indicates the end of a syntax diagram.

Syntax items, such as a keyword or variable, can be:
v On the line (required element)
v Above the line (default element)
v Below the line (optional element).

About this guide xi

Syntax Diagram Description Example
Abbreviations:
KEYWOrd
Uppercase letters denote the shortest
acceptable truncation. If an item appears
entirely in uppercase letters, it cannot be
truncated.

You can type the item in any combination of
uppercase or lowercase letters.

In this example, you can enter KEYWO,
KEYWORD, or KEYWOrd.
Symbols: * Asterisk
{} Braces
Enter these symbols exactly as they appear in : Colon
the syntax diagram. , Comma
= Equal Sign
- Hyphen
() Parentheses
. Period
Space
Variables:
KEYWOrd var_name
Italicized lowercase items (var_name) denote
variables.

In this example, you can specify a var_name
when you enter the KEYWORD command.
Repetition:

An arrow returning to the left means you can
repeat the item. repeat
A character or space within the arrow means
,
you must separate repeated items with that
character or space.
repeat
A footnote by the arrow references the
number of times you can repeat the item.
(1)
repeat
Notes:
1 Specify repeat as many as 5 times.

Required Choices:
A
When two or more items are in a stack and B
one of them is on the line, you must specify C
one item.

In this example, you must choose A, B, or C.

xii IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

Syntax Diagram Description Example
Optional Choice:

When an item is below the line, that item is A
optional. In the first example, you can choose
A or nothing at all.
A
When two or more items are in a stack below
B
the line, all of them are optional. In the
C
second example, you can choose A, B, C, or
nothing at all.
Defaults:
A
Defaults are above the line. The default is
selected unless you override it. You can B
override the default by including an option C
from the stack below the line.

In this example, A is the default. You can
override A by choosing B or C. You can also
specify the default explicitly.
Repeatable Choices:

A stack of items followed by an arrow
returning to the left means you can select A
more than one item or, in some cases, repeat B
a single item. C
In this example, you can choose any
combination of A, B, or C.
Syntax Fragments:
The fragment name
Some diagrams, because of their length, must
fragment the syntax. The fragment name The fragment name:
appears between vertical bars in the diagram.
The expanded fragment appears between A
vertical bars in the diagram after a heading
with the same fragment name. B
C

About this guide xiii

xiv IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

Chapter 1. Introducing Data Protection for Oracle
This section provides a brief overview of Tivoli Storage Manager and Data
Protection for Oracle.

Understanding Tivoli Storage Manager
Tivoli Storage Manager is a client/server program that provides storage
management services in a multi-vendor, multi-platform computer environment.

Tivoli Storage Manager provides these functions:
v Reduces network complexity
Tivoli Storage Manager reduces network complexity with interfaces and
functions that span network environments. This provides consistency across
different operating systems and hardware.
v Increases administrator productivity
Tivoli Storage Manager can reduce the cost of network administration by
allowing administrators to perform these actions:
– Automate repetitive processes
– Schedule unattended processes
– Administer Tivoli Storage Manager from anywhere in the network
v Reduces the risk of data loss
Many users do not back up their data. Other users apply stand-alone backup
techniques with diskettes and tapes as the only protection for business data.
These backup systems often produce disappointing results during recovery
operations. Tivoli Storage Manager schedules routine backups that enable users
to recover from accidental data deletion without administrator involvement.
v Optimizes existing storage resources
Tivoli Storage Manager allows users to move files from client file systems to
Tivoli Storage Manager storage. This saves space on client file systems and can
eliminate the expense of upgrading client storage hardware.
Tivoli Storage Manager monitors client storage space and moves files from client
file systems to Tivoli Storage Manager storage if an out-of-space condition
threatens. This function can also eliminate the expense of client hardware
upgrades.

Tivoli Storage Manager provides these services:
v Backup and restore services
These services generate backup copies of data at specified intervals and restores
the data from these copies when required. These services protect against
workstation or file server media failure, accidental file deletion, data corruption,
data vandalism, or site disasters.
v Archive and retrieve services
These services provide backup-archive clients with point-in-time copies of data
for long-term storage.

© Copyright IBM Corp. 1998, 2007 1

v Server hierarchical storage management services
These services migrate client files from expensive storage media to less
expensive storage media (from disk to tape, for example). Administrator-defined
thresholds determine file migration for each storage pool. Migration applies to
all backup and archive client files.
v Automation services
Tivoli Storage Manager administrators can increase productivity by automating
common storage administration tasks.
v Administration services
Tivoli Storage Manager administration services provide support for routine
monitoring, administration, and accounting. Administrators can manage the
server from another system or the same system. The Tivoli Storage Manager
utilities allow the administrator to perform these functions:
– Set client and server options
– Define devices
– Format storage volumes
– Add additional clients
– Label tape volumes
Tivoli Storage Manager monitors scheduled operations and maintains status
information in the database. An administrator can export data to removable
media. This data can be imported by another server, making the export and
import features a convenient utility for moving server data. The administrator
can specify the accounting option generated at the end of each client session.
v Security services
Security services control user access to Tivoli Storage Manager data, storage,
policy definitions, and administrative commands.
v Disaster recovery management
Disaster recovery management helps the administrator implement a
comprehensive backup and recovery procedure for important business
applications, data, and records.

Overview of Data Protection for Oracle
Data Protection for Oracle currently supports Oracle 9i and Oracle 10g databases
with the Oracle Recovery Manager (RMAN). See Chapter 2, “Installing Data
Protection for Oracle,” on page 5 for specific levels of supported Oracle databases.

RMAN and Data Protection for Oracle
RMAN provides consistent and secure backup, restore, and recovery performance
for Oracle databases. While the Oracle RMAN initiates a backup or restore, Data
Protection for Oracle acts as the interface to the Tivoli Storage Manager server
Version 5.3.x (or later). The Tivoli Storage Manager server then applies
administrator-defined storage management policies to the data. Data Protection for
Oracle implements the Oracle defined Media Management application program
interface (SBTAPI) 2.0. This SBTAPI interfaces with RMAN and translates Oracle
commands into Tivoli Storage Manager API calls to the Tivoli Storage Manager
server.

With the use of RMAN, Data Protection for Oracle allows you to perform the
following functions:
v Full and incremental backup function for the following while online or offline:
– Databases

2 IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and User’s Guide

– Tablespaces
– Datafiles
– Archive log files
– Control files
v Full database restores while offline
v Tablespace and datafile restore while online or offline

LAN-free data transfer
Data Protection for Oracle supports backup and restore operations in a LAN-free
environment. This environment shifts the movement of data from the
communications network to a storage area network (SAN). Data moves over the
SAN to a SAN-attached storage device by the Tivoli Storage Manager Storage
Agent. Running Data Protection for Oracle in a LAN-free environment avoids
constraints of the network and decreases the load on the Tivoli Storage Manager
server, allowing the server to support a greater number of simultaneous
connections.

Before enabling LAN-free support, you must install the Tivoli Storage Manager
Managed System for SAN Storage Agent on the same system as Data Protection
for Oracle. See the IBM Tivoli Storage Manager for SAN for your operating
environment for more information about LAN-free requirements.

Migration and coexistence
| v Data Protection for Oracle Version 5.4 does not support Oracle8 (8.0.x) databases.
| v Existing backups created using Data Protection for Oracle Version 2.2.0 and 2.2.1
| are restorable using Data Protection for Oracle 5.4.
v Data Protection for Oracle relies heavily on the tdpo.opt file for accuracy in
setup and maintenance. The contents of the tdpo.opt file are different than the
environment variables used with Data Protection for Oracle Version 2.1.
Therefore, Version 2.1 RMAN scripts for environment variables are ignored. For
more information, see Chapter 3, “Configuring Data Protection for Oracle,” on
page 11 or “Scripts” on page 21.
| v Tivoli Storage Manager server Version 5.3.x (or later) and the Tivoli Storage
| Manager API Version 5.4.0 (or later) are required.

Chapter 1. Introducing Data Protection for Oracle 3

Chapter 2. Installing Data Protection for Oracle
This chapter provides information on the required client environment for Data
Protection for Oracle and instructions on installing Data Protection for Oracle.

Make sure these conditions exist before installing Data Protection for Oracle:
v Tivoli Storage Manager server Version 5.3.x (or later) is configured.
| v Tivoli Storage Manager API Version 5.4.0 (or later) is installed. The required
| version of the Tivoli Storage Manager API is included in the Data Protection for
| Oracle product media.
v Determine the appropriate Data Protection for Oracle bit size to use by
identifying the bit size of your Oracle target database. For example, if you are
using a 32-bit Oracle target database, you must use a 32-bit version of Data
Protection for Oracle. If you are using a 64-bit Oracle target database, you must
use a 64-bit version of Data Protection for Oracle. The Data Protection for Oracle
bit size is not determined by the bit size of your operating system.
v Any previous version of Data Protection for Oracle or the Tivoli Storage
Manager API must be uninstalled before installing a new or updated version. If
you are installing a PTF version of Data Protection for Oracle, do not remove the
license file from the previous version. The PTF driver does not contain a license.

Attention: A user with administrative authority must install Data Protection for
Oracle on a Windows server where the target database resides.

After Data Protection for Oracle is installed, see Chapter 3, “Configuring Data
Protection for Oracle,” on page 11 for detailed task instructions you must perform
before attempting to back up data..

Note: If you would like to configure Data Protection for Oracle using default
settings, see Appendix A, “Quick configuration guide,” on page 33 for
instructions.

Important
| See the readmedporc_enu.htm file that is shipped on the product installation
| media for the most current information.


Windows x86 environment
This section contains the hardware and software requirements for installing Data
Protection for Oracle in a Windows x86 environment.

Operating system requirements
One of the following Windows operating systems:
| v Windows XP (32-bit)
| v Windows Server 2003 (32-bit)

Hardware requirements
v A Pentium® 166 (or faster) processor or equivalent
v 96 MB of RAM minimum (128 MB recommended)
v 14 MB of disk space

Software requirements
v Tivoli Storage Manager server Version 5.3.x (or later)
| v Tivoli Storage Manager API Version 5.4.0 (or later)

| Note: The Tivoli Storage Manager API is included on the product media. If you
| have already installed a later level API, the latest version is retained
| during installation.
v One of the following levels of Oracle Server:
– Oracle9i Version 9.2 (32-bit)
– Oracle 10g Release 1 (32-bit)

Communication methods
Data Protection for Oracle supports the communication methods supported by the
Tivoli Storage Manager API and the Tivoli Storage Manager server.


Windows x86_64 environment
Protection for Oracle in a Windows x86_64 environment.

The following Windows operating system:
v Windows Server 2003 (64-bit)

v An AMD Opteron, AMD Athlon 64, Intel® 64-Bit Xeon™, or Intel Pentium with
EM64T (or compatible) processor


v Oracle 10g Release 2 (64-bit)


Chapter 2. Installing Data Protection for Oracle 7

Windows Itanium 2 environment (64-bit)
Protection for Oracle in a Windows Itanium® 2 64-bit environment.

One of the following Windows operating systems:
v Windows XP (64-bit)
v Windows Server 2003 (64-bit)

v An Intel Itanium 2 (or compatible) processor


v One of the following levels of Oracle Server:
– Oracle9i Version 9.2 (64-bit)
Table 1. Supported Oracle Server and operating system combinations on Windows Itanium 2
Oracle 9i Version Oracle 10g Release Oracle 10g Release 2
9.2 (64-bit) 1 (64-bit) (64-bit)
Windows XP U U
Windows Server 2003 U U U



Installing Data Protection for Oracle
The following instructions assume that a Windows XP or Windows Server 2003
program is running on the client workstation.

Note: Data Protection for Oracle must be installed from an account having
administrator privileges to the local system.

Installing all Tivoli Storage Manager products and components into the same
base directory is highly recommended. The installation process does not overwrite
the existing dsm.opt (options file), tdpo.opt (configuration file), or log files.
v If Data Protection for Oracle was not previously installed on your system, you
can install Data Protection for Oracle into the Tivoli Storage Manager base
directory of your choice. Data Protection for Oracle 32-bit installs to the
AgentOBA directory and Data Protection for Oracle 64-bit installs to the
AgentOBA64 directory under this base default directory:
c:Program FilesTivoliTSM
| v If Version 2.2 of Data Protection for Oracle exists on your system, Data
| Protection for Oracle 5.4.1 will replace it in the same directory.
| v If Data Protection for Oracle 5.4.1 was previously installed, the Program
| Maintenance dialog prompts you to Repair the program if files are missing or
| corrupt, or to Remove the existing version from your computer.

These instructions guide you through the installation of Data Protection for Oracle:
1. Insert the Data Protection for Oracle CD into the CD drive.
Windows automatically starts the InstallShield wizard for you. If the wizard is
not enabled, perform the following steps:
a. Select Run from the Start menu.
b. Enter x:setup where x is your CD drive letter.
c. Click OK to start the installation program.
Alternatively, you can double-click setup.exe using the Windows file manager.
2. Follow the instructions displayed on your screen.
You are prompted to choose a setup language. You can choose:
v Chinese (Simplified)
v Chinese (Traditional)
v Czech
v English (United States) This is the default.
v French (France)
v German (Germany)
v Hungarian
v Italian (Italy)
v Japanese
v Korean
v Polish
v Portuguese (Brazil)
v Russian
v Spanish (Traditional Sort)
Note that you must download the Language Pack of your desired language
after installing Data Protection for Oracle. The Language Pack enables the

Chapter 2. Installing Data Protection for Oracle 9

command output, error log text, and messages to display in your desired
language. You can download the Language Pack from the product CD or
online. See the readmedporc_enu.htm file that is shipped on the product
installation media for the exact location of these Language Packs.
3. Data Protection for Oracle prompts you to accept the License Agreement. If you
do not accept the License Agreement, Data Protection for Oracle will not install.
4. Click Finish to complete the installation.


Chapter 3. Configuring Data Protection for Oracle
After Data Protection for Oracle is successfully installed, you must complete the
following configuration tasks:
1. Define Data Protection for Oracle options in the tdpo.opt file.
2. Register the Data Protection for Oracle node to a Tivoli Storage Manager server.
3. Define Tivoli Storage Manager options in the dsm.opt file.
4. Define Tivoli Storage Manager policy requirements.
5. Initialize the password with a Tivoli Storage Manager server.

Note: If you would like to configure Data Protection for Oracle using default
settings, see Appendix A, “Quick configuration guide,” on page 33 for
instructions.

1. Define Data Protection for Oracle options in the tdpo.opt file
The Data Protection for Oracle options file, tdpo.opt, contains options that
determine the behavior and performance of Data Protection for Oracle. The only
environment variable Data Protection for Oracle Version 5.4.1 recognizes within an
RMAN script is the fully qualified path name to the tdpo.opt file. Therefore, some
RMAN scripts may need to be edited to use TDPO_OPTFILE=fully qualified path
and file name of options file variable in place of other environment variables. For
example:
allocate channel t1 type ’sbt_tape’ parms
’ENV=(TDPO_OPTFILE=C:RMANscriptstdpo.opt)’

See “Scripts” on page 21 for further information. Note that the allocate channel
entry is divided on two lines after the parms option to accommodate page
formatting.

If a fully qualified path name is not provided, Data Protection for Oracle uses the
tdpo.opt file located in the Data Protection for Oracle default installation directory.
If this file does not exist, Data Protection for Oracle fails.

Note: Though it is possible to change values in the options file, you cannot effect
changes to the dsmi options until you restart Data Protection for Oracle.
Data Protection for Oracle loads these values from the default tdpo.opt file
into the default installation directory when the Oracle service is started.

Considerations
v It is strongly recommended that you use the tdpo.opt file exclusively instead of
default parameters.
v RMAN and the tdpoconf and tdposync utilities use the options defined in the
tdpo.opt file.
v By default, the tdpo.opt file is located in the directory where Data Protection for
Oracle is installed.
v Data Protection for Oracle supports options (specified in the tdpo.opt file) in
both upper case or lower case type.


Available options
The following options can be set in the tdpo.opt file:
dsmi_log
Specify the directory that contains the Data Protection for Oracle error log
file (tdpoerror.log).
dsmi_orc_config
Specify the complete path to the Tivoli Storage Manager client user options
file (dsm.opt) used during the Data Protection for Oracle session. If you do
not specify this option, Data Protection for Oracle looks for this options file
in the Data Protection for Oracle installation directory. You must specify
this option if your Tivoli Storage Manager client user options file is located
in a directory other than the Data Protection for Oracle installation
directory.
| tdpo_fs
| Specify a file space name on the Tivoli Storage Manager server for Data
| Protection for Oracle backup, delete, and restore operations. The file space
| name can contain a string of 1 to 1024 characters.
| v The default file space name is adsmorc.
| v When you have more than one Oracle database, use this option to back
| up each Oracle target database to its own file space on the Tivoli Storage
| Manager server.
| v The file space name in the include/exclude statement must match the
| file space name specified in the tdpo_fs option for include/exclude
| processing to function correctly.
tdpo_date_fmt
This option specifies the format you want to use to display dates. You can
specify a number between 1 and 5 inclusively. The default value is 1.
1 MM/DD/YYYY (Default)
2 DD-MM-YYYY
3 YYYY-MM-DD
4 DD.MM.YYYY
5 YYYY.MM.DD
tdpo_num_fmt
This option specifies the format you want to use to display numbers. You
can specify a number between 1 and 6 inclusively. The default value is 1.
1 1,000.00 (Default)
2 1,000,00
3 1 000,00
4 1 000.00
5 1.000,00
6 1’000,00
tdpo_time_fmt
This option specifies the format you want to use to display time. You can
specify a number between 1 and 4 inclusively. The default value is 1.
1 23:00:00 (Default)
2 23,00,00
3 23.00.00
4 12:00:00 A/P


tdpo_language
This option specifies the national language in which to display Data
Protection for Oracle messages in the error log file. You can specify the
following:
enu American English (Default)
deu Standard German
esp Standard Spanish
fra Standard French
ita Standard Italian
jpn Standard Japanese
kor Standard Korean
ptb Brazilian Portuguese
sch Chinese, Simplified
tch Chinese, Traditional
tdpo_mgmt_class_2
This option specifies the second management class used for copy 2 in the
RMAN duplex copy command.
tdpo_mgmt_class_3
This option specifies the third management class used for copy 3 in the
RMAN duplex copy command.
tdpo_mgmt_class_4
This option specifies the fourth management class used for copy 4 in the
RMAN duplex copy command. Four copies is the maximum allowed by
RMAN.

Note: It is recommended that you review “Using the Duplex Copy function” on
page 22 for specific details on using management class options.

2. Register the Data Protection for Oracle node to a Tivoli Storage
Manager server
The Data Protection for Oracle node name and password (if required) must be
registered to the Tivoli Storage Manager server before you can begin requesting
backup and restore services. The process of setting up a node name and password
with the Tivoli Storage Manager server is called registration.

The following information is needed to register Data Protection for Oracle with the
Tivoli Storage Manager server:
v The Data Protection for Oracle node name
This is the node name that identifies the instance on which Data Protection for
Oracle is installed. It is recommended that you use a separate and unique node
name for Data Protection for Oracle. This prevents any confusion with an
existing Tivoli Storage Manager backup-archive client on the same workstation.
v The initial password
This is the password you want to use, if a password is required.

The following information is defined by the Tivoli Storage Manager administrator:
v The policy domain to which your client node belongs.
A policy domain contains policy sets and management classes that control how
Tivoli Storage Manager manages the objects you back up. Rather than binding

Chapter 3. Configuring Data Protection for Oracle 13

Data Protection for Oracle backups to a different management class, it is
recommended that a unique policy domain be defined for Data Protection for
Oracle node names. These backups can be bound to the default management
class within this unique policy domain. Rather than binding a different
management class for Oracle backups, it is also recommended that you specify a
different domain for Oracle backups with a separate management class.
v The authority to enable compression.
| The Tivoli Storage Manager administrator can specify the server to compress
| files. If the Tivoli Storage Manager administrator specifies that the compression
| decision belongs to the client (compression client), you must specify compression
| yes in the client user options file (dsm.opt) in order for the Data Protection for
| Oracle node to be able to compress objects before sending them to the Tivoli
| Storage Manager server.
v The authority to delete backup data from Tivoli Storage Manager storage.
| The Data Protection for Oracle node can only delete backed up data from Tivoli
| Storage Manager storage if the Tivoli Storage Manager administrator registers
| the node with backdelete authority. Specify the following option to allow
| backdelete authority:
| backdelete yes
| Note that when backdelete no is specified, the backed up object is marked as
| inactive and is removed from the Tivoli Storage Manager server based on the
| backretention setting associated with the copy group. Data Protection for Oracle
| cannot restore objects that are marked as inactive. Therefore, by specifying
| backdelete yes, the object is immediately removed from the Tivoli Storage
| Manager server when the next inventory expiration occurs. This expiration also
| makes the previously used storage space available for new use.

3. Define Tivoli Storage Manager options in the dsm.opt file
You must define some Tivoli Storage Manager options after the Data Protection for
Oracle node is registered to the Tivoli Storage Manager server:
v These options are defined in the Tivoli Storage Manager client user options file
(dsm.opt by default).
v Note that the Tivoli Storage Manager client user options file (dsm.opt by default)
you must edit for Data Protection for Oracle is located in the directory specified
by the dsmi_orc_config option. If this option is not specified, Data Protection for
Oracle looks for this options file in the Data Protection for Oracle installation
directory.
v Data Protection for Oracle provides sample Tivoli Storage Manager options files
that you can modify for this purpose. These sample files are located in the Data
Protection for Oracle installation directory.
v The Tivoli Storage Manager administrator can provide you with the TCP server
address (tcpserveraddress) and communication method (commmethod) for
connecting Data Protection for Oracle to the Tivoli Storage Manager server.


Required options
Specify these options in the Tivoli Storage Manager client user options file
(dsm.opt by default) located in the directory specified by the dsmi_orc_config
option:
nodename
Specify the Data Protection for Oracle node name used during operations
with the Tivoli Storage Manager server. The node name can contain a
string of 1 to 64 characters.
To restore data from one Oracle server to another Oracle server using Data
Protection for Oracle, make sure the value of the nodename option in the
dsm.opt file on the target Oracle server equals the value of the nodename
option in the dsm.opt file on the source Oracle server. Data Protection for
Oracle, the Tivoli Storage Manager backup-archive client, and the Tivoli
Storage Manager API must be at the same levels on both the source Oracle
server and the target Oracle server. If there is a password associated with
the nodename option in the dsm.opt file on the target Oracle server, use the
tdpoconf utility to generate the local password file once the value of the
nodename option changes.
| passwordaccess
| Specify passwordaccess generate. This allows the Tivoli Storage Manager
| API to manage all password actions after the password is created using the
| tdpoconf password command. The Tivoli Storage Manager API saves the
| current password (encrypted) in the Windows registry and automatically
| generates a new password when the current password expires. This method
| of password management is useful when running unattended scheduled
| backups because it ensures that the backup never fails due to an expired
| password.
tcpserveraddress
Specify the TCP/IP address for the Tivoli Storage Manager server to be
used for Oracle backups.
commmethod
Specify the communication method for Data Protection for Oracle to
communicate with the Tivoli Storage Manager server. Note that this option
requires other Tivoli Storage Manager options, depending on the
communication method you specify.

Other options to consider
It is recommended that you specify these options in the Tivoli Storage Manager
client user options file, dsm.opt:
compression
Specify whether the Tivoli Storage Manager API compresses data before
sending it to the Tivoli Storage Manager server. You can specify on or off.
The default value is on. The value of the compression option for Data
Protection for Oracle is honored only if the Tivoli Storage Manager
administrator leaves the compression decision to the node. Enabling
compression affects performance in three ways:
v CPU utilization is higher on the machine on which Data Protection for
Oracle is running.
v Network bandwidth utilization is lower because fewer bytes are
transmitted.
v Storage usage on the Tivoli Storage Manager server is reduced.


Considerations: It is recommended that you specify on when any of the
following conditions exist:
v The network adapter has a data overload.
v Communications between Data Protection for Oracle and the Tivoli
Storage Manager server are over a low bandwidth connection.
v There is heavy network traffic.
It is recommended that you specify off when any of the following
conditions exist:
v The machine running Data Protection for Oracle has a CPU overload.
The added CPU usage (as a result of enabling compression) can impact
other applications, including the Oracle server. You can monitor CPU
and network resource utilization using the Performance Monitor
program shipped with Windows.
v You are not constrained by network bandwidth. In this case, you can
achieve the best performance by specifying compression off and enabling
hardware compaction on the tape drive, which also reduces storage
requirements.
| v Hardware compression is in use for the media where Data Protection for
| Oracle data resides.

Note: The compression option also accepts these values to signify ON: true
or yes. These values are also accepted to signify OFF: false or no.
enablelanfree
Specify whether you run backup operations in a LAN-free environment if
you are equipped to do so. You can specify yes or no. The default value is
no. You can avoid network constraints by shifting the movement of data to
a storage area network (SAN). For more information, see the appropriate
Storage Agent User’s Guide.
include
Add an include statement to the dsm.opt file (used by the Oracle node)
when a management class (other than the default management class) is
defined within an existing policy domain. This include statement binds the
Oracle backup objects to the management class that is defined for
managing these objects. The include statement uses the following naming
convention:
FilespaceNameorcntObjectName

The FORMAT parameter in the RMAN script can also be used to assist
with object naming. For example, if the FORMAT parameters (in the
RMAN script) specified the following values for databases and logs:
format ’DB_%u_%p_%c’
format ’LOG_%u_%p_%c’

The include statement in the dsm.opt file (used by the Oracle node) would
be as follows:
INCLUDE FilespaceNameorcntDB* mgmtclassname
INCLUDE FilespaceNameorcntLOG* mgmtclassname
enableclientencryptkey
When enableclientencryptkey is set to yes, Data Protection for Oracle
provides 128-bit transparent encryption of Oracle databases during backup
and restore processing. One random encryption key is generated per
session and is stored on the Tivoli Storage Manager server with the object


in the server database. Although Tivoli Storage Manager manages the key,
a valid database must be available in order to restore an encrypted object.
You can specify the databases you want encrypted by adding an include
statement with the include.encrypt option in the client user options file
(dsm.opt).
| For example, to enable transparent encryption, set the following options in
| the client user options file, dsm.opt:
| 1. Specify enableclientencryptkey yes.
| 2. Specify encryptiontype AES128 (recommended) or DES56.
| 3. Specify the objects to encrypt. This example encrypts all data:
| include.encrypt adsmorc...*
| Thus, the encryption options in this client user options file, dsm.opt would
| be as follows:
| enableclientencryptkey yes
| encryptiontype aes128
| include.encrypt adsmorc...*

See IBM Tivoli Storage Manager Using the Application Program Interface for
more details regarding the enableclientencryptkey option.

4. Define Tivoli Storage Manager policy requirements
RMAN uses the format parameter (in the RMAN script) to generate unique
backup file names. Because all backup objects inserted into the Tivoli Storage
Manager backup storage pool have unique file names, they never expire on the
Tivoli Storage Manager server. As a result, Data Protection for Oracle requires
these special Tivoli Storage Manager policy domain settings:
Backup copy group values
Data Protection for Oracle provides the tdposync utility to remove
unwanted backup objects from the Tivoli Storage Manager server. It is
recommended that the following Tivoli Storage Manager backup copy
group options be set:
v verdeleted 0
v retonly 0
Then, when Data Protection for Oracle marks a backup object inactive, that
object is deleted from the Tivoli Storage Manager server the next time
expiration processing occurs. A backup object is marked for immediate
expiration when you delete it through RMAN using the Data Protection for
Oracle interface or with the tdposync utility. Note that an inactive backup
object cannot be restored through RMAN using the Data Protection for
Oracle interface.
Notes:
| 1. The Tivoli Storage Manager administrator must also register your node
| by specifying backdelete yes in order for backup objects to be deleted.
| However, be aware that a backup object is marked for immediate
| expiration when backdelete yes and you delete it through RMAN using
| the Data Protection for Oracle interface or with the tdposync utility.
| Also note that even when backdelete no is specified, the object is
| marked inactive. The verdeleted 0 and retonly 0 settings will remove
| these inactive objects from the Tivoli Storage Manager server when the
| next inventory expiration occurs.


2. The following backup copy group options are not applicable to Data
Protection for Oracle:
v frequency
v verexists
v retextra
v mode
v serialization
Data Protection for Oracle accepts default values for these options.
3. An archive copy group is not required (although it can exist) because
Data Protection for Oracle stores all objects as backup objects on Tivoli
Storage Manager.
Management class
Tivoli Storage Manager uses management classes to manage backups on
the Tivoli Storage Manager server. When you back up a database, the
default management class for your node is used. Because the policy
requirements for Data Protection for Oracle may be different from the
desired settings for the regular Tivoli Storage Manager backup-archive
clients, you must have a different management class defined for Data
Protection for Oracle. It is recommended that you define a separate policy
domain where the default management class has the required settings and
then register all Data Protection for Oracle nodes to that domain.
If you choose to define a new management class within an existing policy
domain (not the default management class for that domain), then you must
add an include statement to the Data Protection for Oracle options file to
bind all objects to that management class.
The following steps assign a management class name orcbackup to all
Oracle backups with a default file space name adsmorc:
1. Add this inclexcl entry under the server stanza you use in the dsm.opt
file:
inclexcl C:myfileinclude.def
2. Add this include entry to the C:myfileinclude.def file:
include adsmorc...* orcbackup

Note: The file space name in the include/exclude statement must
match the file space name defined with the tdpo_fs option. If a
file space name other than the default value (adsmorc) is used:
a. You must specify the file space name with the tdpo_fs option.
b. You must specify the file space name defined in the tdpo_fs
option in the include/exclude statement.

All the files backed up with a default file space name of adsmorc are
assigned to management class orcbackup.

Note: Data Protection for Oracle stores all objects as backup objects on Tivoli
Storage Manager storage, so an archive copy group is not required, although
it can exist.

See your Tivoli Storage Manager administrator or see the Tivoli Storage Manager
Administrator’s Guide for more information on defining or updating Tivoli Storage
Manager policy domains and copy groups.


5. Initialize the password with a Tivoli Storage Manager server
The administrator must run the tdpoconf utility program to set the password
before using Data Protection for Oracle. See “TDPOCONF” on page 26 for more
information.


Chapter 4. Using RMAN and Data Protection for Oracle
You can perform full or partial, offline or online backups with Oracle. Once you
identify which database to back up, Oracle locates all necessary files and sends
them to the Tivoli Storage Manager server through Data Protection for Oracle. As a
result, Data Protection for Oracle provides an interface between Oracle Media
Management API calls and Tivoli Storage Manager API routines.

Invoking RMAN
Invoke RMAN to back up and restore an Oracle database. In this example, the
catalog database contains a registered target database. Invoke RMAN with this
command:
$> rman target xxx/yyy@target rcvcat aaa/bbb@catalog
cmdfile bkdb.scr msglog bkdb.log

This starts RMAN in the sequence shown.
target xxx/yyy@target: connect to target database
using user xxx and password yyy with connect string target
rcvcat aaa/bbb@catalog: connect to catalog database
using user aaa and password bbb with connect string catalog
cmdfile bkdb.scr: run bkdb.scr script
msglog bkdb.log: log the output messages in bkdb.log

Note: In the above example, RMAN creates a log file (bkdb.log) in the current
working directory. If an error occurs, you will see the error stack in the log
file.

Scripts
Data Protection for Oracle does not recognize environment variables specified in
an RMAN script. The only environment variable Data Protection for Oracle Version
5.4.1 recognizes within an RMAN script is the fully qualified path name to the
tdpo.opt file. Therefore, existing RMAN scripts may need to be edited to use
TDPO_OPTFILE=fully qualified path and file name of options file variable in place of
other environment variables.


Example
This backup script allocates two parallel connections to the Tivoli Storage Manager
server. The Tivoli Storage Manager server views these connections as two separate
sessions:
run
{
’ENV=(TDPO_OPTFILE=C:oracleora91scriptstdpo.opt)’;

backup
filesperset 5
format ’df_%t_%s_%p’
(database);

}

Note: To back up to Tivoli Storage Manager using Data Protection for Oracle, you
must specify type ’sbt_tape’ in the RMAN script or within the global
RMAN configuration settings.
This restore script allocates one parallel connection to the Tivoli Storage Manager
server:
run
{
’ENV=(TDPO_OPTFILE=C:homeoracletdpo.opt)’;
restore database;
recover database;
alter database open;
}
Notes:
1. The allocate channel entry is divided on two lines after the parms option to
accommodate page formatting.
2. The Oracle database must be in mount mode for the restore to succeed.

Using the Duplex Copy function
Data Protection for Oracle supports the Oracle Server Duplex backup feature. This
feature allows you to make up to four exact duplicate copies of a backup that can
be stored on different backup media. A different management class is required for
each backup copy. By default, the primary management class is the default
management class on the policy domain defined for the Data Protection for Oracle
node.

Note: It may be necessary to define the Oracle parameter value
(BACKUP_TAPE_IO_SLAVES=TRUE) in the init.ora file of the target
database for Data Protection for Oracle to use the duplex copy feature. Refer
to your Oracle documentation regarding the use of this Oracle parameter.

For example, to create four backup copies:
1. Specify the following option in the RMAN backup script:
set duplex 4
2. Define the following options in the tdpo.opt file:
v tdpo_mgmt_class_2
v tdpo_mgmt_class_3
v tdpo_mgmt_class_4

3. Run the RMAN backup script.
The following backup behavior occurs:
v The first backup copy is bound to the default management class to which the
node is registered.
v The second backup copy is bound to the management class defined by the
tdpo_mgmt_class_2 option.
v The third backup copy is bound to the management class defined by the
v The fourth backup copy is bound to the management class defined by the

Considerations
The duplex copy feature does not use include statements. It only uses the
management classes specified in the tdpo.opt file.
You will receive an error message if you specify set duplex 4 in the RMAN
backup script and do not define a sufficient number of tdpo_mgmt_class
options in the tdpo.opt file.
In order to place duplicate copies on different media:
– Make sure the storage pool information for each backup copy group within
the management classes is not the same.
– Make sure backups from these different storage pools are not migrated to the
same storage pool at a later time.
Be aware that duplicate data will be sent across the network.
Be aware that if you specify set duplex 4 and allocate one channel in the RMAN
backup script, RMAN will start four sessions to the Tivoli Storage Manager
server. Likewise, if you specify set duplex 4 and allocate two channels in the
RMAN backup script, RMAN will start eight sessions to the Tivoli Storage
Manager server.
The duplex copy feature sends the backup copies simultaneously. If the backup
destination is tape, the number of sessions will be multiples of the duplex
value. As a result, make sure RMAN does not start more sessions than the
maximum mount points allowed by the Tivoli Storage Manager server. The
node definition option on the Tivoli Storage Manager server (maxnummp)
determines the maximum number of mount points a client node is allowed to
use on the Tivoli Storage Manager server during a backup operation. You can
view the maximum mount points allowed by the Tivoli Storage Manager server
for a particular node by entering the query node command from a Tivoli
Storage Manager Administrative Client prompt:
q node f=d

See the appropriate Tivoli Storage Manager Administrator’s Reference for more
information regarding this option.

It is highly recommended that you review your current Oracle documentation
regarding the duplex backup function.

Chapter 4. Using RMAN and Data Protection for Oracle 23

Removing old backups
Data Protection for Oracle uses the Tivoli Storage Manager backup repository. Each
database backup creates a new object with a unique name. Since these objects have
unique names, they always remain active and never expire. This allows the
Database Administrator (DBA) to control and coordinate copies removed from the
Tivoli Storage Manager server with RMAN.

Note: Make sure to use the same tdpo.opt file that was used for the original
backup. This enables the backup objects to be found on the Tivoli Storage
Manager server.

Example
To remove an old backup, issue this command from the RMAN prompt:
run
{
allocate channel for delete type ’sbt_tape’ parms

change backupset backupset number delete;

}

See the Oracle RMAN manual for more information on the change command and
its options.

Management class options affecting object removal
| The Tivoli Storage Manager administrator must specify backdelete=yes when
| registering your node in order for you to be able to delete backup objects. You can
| use parameters in the management class definition to control when the inactive
| object expires on the Tivoli Storage Manager server. For the backup copy group,
| use:
| v verdeleted=0
| v retonly=0
| These settings erase the inactive objects from the server after the next inventory
| expiration. However, be aware that a backup object is marked for immediate
| expiration when backdelete=yes and you delete it through RMAN using the Data
| Protection for Oracle interface or with the tdposync utility. Also note that even
| when backdelete=no is specified, the object is marked inactive. The verdeleted=0
| and retonly=0 settings will remove these inactive objects from the Tivoli Storage
| Manager server when the next inventory expiration occurs.


Chapter 5. Using the utilities
This chapter describes how to use the Data Protection for Oracle utilities (tdpoconf
and tdposync) from the command line interface. These utilities are located in the
directory where Data Protection for Oracle is installed.
v The tdpoconf utility is used for password maintenance and general Data
Protection for Oracle setup and maintenance.
v The tdposync utility is used to delete the Oracle backups on the Tivoli Storage
Manager server which are not in the RMAN catalog. This occurs when backups
have inadvertently not been deleted from the Tivoli Storage Manager server.

Command line syntax and characteristics
The Data Protection for Oracle utilities use the following command line syntax:
tdpoconf <command> <0 or more optional parameters>
tdposync <command> <0 or more optional parameters>

The command line parameters have the following characteristics:
v Minimum abbreviations for keywords are indicated in upper case.
v Optional parameters begin with a dash (-).
v Optional parameters can appear in any order.
v Some keyword parameters require a value separated by the equal sign (=).
v If a parameter requires more than one value, the values are separated with
commas.
v A space separates the invocation from the command and the command from any
optional parameters.
v Each parameter is separated from others by a space.
v If a parameter value includes spaces, the entire parameter must be enclosed in
double quotes.


TDPOCONF
This utility provides setup tasks to ease the configuration of Data Protection for
Oracle. The utility uses the tdpo.opt file in the installation directory to centralize
information for setup purposes.

Two commands are available using the tdpoconf utility:
v PASSWord
v SHOWENVironment
A description of these two commands and their parameters follows.

Password command
Use the password command to create a new password or change an existing
password on the Tivoli Storage Manager server. You are prompted to enter both
the old and new passwords when you invoke this utility.

Syntax
TDPOCONF PASSWord
installed tdpo.opt
-TDPO_OPTFILE=
pathname

Optional parameters
-TDPO_OPTFILE=pathname
This parameter specifies the fully qualified path name to the tdpo.opt file.
If you choose not to specify this option, the default path is used.

Example
This is an output example of the tdpoconf password command:
IBM Tivoli Storage Manager for Databases:
Data Protection for Oracle
Version 5, Release 4, Level 1.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.

***************************************************************
* IBM Tivoli Storage Manager for Databases Utility *
* Password file initialization/update program *
***************************************************************

Please enter current password:

******
Please enter new password:

******
Please reenter new password for verification:

**********
ANU0260I Password successfully changed.


Showenvironment command
Use the showenvironment command to query the Tivoli Storage Manager server
using the options set in –TDPO_OPTFILE, the tdpo.opt file in the default
installation directory, or the default values set by Data Protection for Oracle. The
screen output displays information about the Tivoli Storage Manager API and
Tivoli Storage Manager server. This command is useful when troubleshooting Data
Protection for Oracle setup. If, for example, the password file is not initialized
properly, tdpoconf showenvironment reports this error immediately and prevents
complications that can arise if this error were to go undetected.

Note: For initial setup, it is recommended that you direct the output to a file with
the –outfile option to ensure that the desired environment is set correctly
before using RMAN.

Syntax
TDPOCONF SHOWENVironment
installed tdpo.opt
-TDPO_OPTFILE=
pathname

-OUTfile= pathname

Optional parameters
This is the options file that is used by the utilities and the Data Protection
for Oracle library.
-OUTfile=pathname
This parameter specifies the fully qualified path name to the output file.
The formatted text of this file is the same content that appears as output to
the screen.

Example
Below is an output example of the tdpoconf showenvironment command:
| IBM Tivoli Storage Manager for Databases:
| Data Protection for Oracle
| Version 5, Release 4, Level 1.0
| (C) Copyright IBM Corporation 1997, 2007. All rights reserved.
|
| Data Protection for Oracle Information
| Version: 5
| Release: 4
| Level: 1
| Sublevel: 0
| Platform: 32bit DP Oracle Win32
|
| Tivoli Storage Manager Server Information
| Server Name: DSMSERV
| Server Address: 9.33.255.127
| Server Type: AIX-RS/6000
| Server Port: 1500
| Communication Method: TCP/IP
|
| Session Information
| License Information: License file exists and contains valid license data
| Node Name: AGAPE

Chapter 5. Using the utilities 27

| Node Type: DP Oracle Win32
| DSMI_DIR: C:Program FilesTivoliTSMapi
| DSMI_ORC_CONFIG: c:Program Filestivolitsmagentobadsm.opt
| TDPO_OPTFILE: C:Program FilesTivoliTSMAgentOBAtdpo.opt
| Compression: FALSE
| License Information: License file exists and contains valid license data.

Note: The Server Name: value above identifies the Tivoli Storage Manager server
stanza in the dsm.sys file, not the actual name of the Tivoli Storage Manager
server.

TDPOSYNC
Attention: Deleted files and inactive files cannot be restored! When using this
utility to delete files, ensure that you do not log on under the wrong node name,
query a different database than intended, and delete files in error. Double-check
the node name listed at the top of the PICK window. See “Optional parameters”
on page 30 and “PICK Window” on page 31 for further details.

The tdposync utility checks for items on the Tivoli Storage Manager server that are
not in the RMAN catalog. This utility allows you to repair such discrepancies
between the Tivoli Storage Manager server and the RMAN catalog. By thus
removing unwanted objects in Tivoli Storage Manager storage, you can reclaim
space on the server.

When an RMAN deletion script is run, RMAN deletes entries in the recovery
catalog before confirmation from the Tivoli Storage Manager server. In cases where
objects are not found on the Tivoli Storage Manager server, RMAN tries to delete
backup sets from the Tivoli Storage Manager server and fails. However, the entries
in the RMAN catalog for these objects are still removed. When this happens,
RMAN can no longer identify these backups through the catalog even though the
file still exists on the Tivoli Storage Manager server. This utility therefore
synchronizes the contents of the servers.

| Be aware that when the RMAN catalog contains backups marked as expired,
| RMAN still considers these objects as existing. If tdposync is invoked against these
| objects, it will recognize these objects in the RMAN catalog and on the Tivoli
| Storage Manager server and consider them to be in sync. Therefore, it is necssary
| to delete these objects from the RMAN catalog in order for them to be deleted
| from the Tivoli Storage Manager server. Use the Oracle crosscheck command to
| verify whether the backups exist. Then, use the Oracle delete expired command to
| remove their record from the RMAN catalog.

When you invoke tdposync, the utility does the following:
1. Prompts you for information
2. Gathers information for the Oracle server(s)
3. Queries the Oracle backup catalog and the Tivoli Storage Manager server
4. Displays formatted output to the screen (files that exist on Tivoli Storage
Manager but not in the RMAN catalog)
5. Prompts you to do one of the following:
v Delete any files found causing the discrepancy.
v Delete all files.
v Exit the program without deleting files from the Tivoli Storage Manager
server.


Considerations
The following information must be considered before using the tdposync
command:
v Resynchronize Oracle catalogs with the target databases before running the
tdposync syncdb command. First, connect to the target database and the catalog
database. The following is an example:
$ rman target xxx/yyy@targetdb rcvcat xxx/yyy@catalogdb

When you are connected to both databases, type resync catalog at the RMAN
prompt.
v If the information for sqlplus that you provide to tdposync is incorrect (such as
logon, password, or connect string information), sqlplus stops at its logon
screen. You will need to log on again at the prompt using the following:
login/password@connectstring

where connectstring represents the Oracle database in which to connect. When
you enter the correct input, tdposync proceeds correctly.
v By default, Data Protection for Oracle prompts you to synchronize with one
Oracle catalog at a time. However, if you use multiple Oracle catalogs to back
up multiple target databases to the same file space, the same node name, and
the same owner name on the same Tivoli Storage Manager server, you must use
–numcatalogs=number. This is necessary so that tdposync has all the information
to correctly query both Oracle and Tivoli Storage Manager.
If, for example, you back up only one target database using two catalogs, you do
not need to specify this option. However, if you back up two target databases
using two catalogs (one catalog for each) to the same Tivoli Storage Manager
server under the same file space, node name, and owner name, you must specify
numcatalogs. If you fail to provide information for the second target database
(by not specifying two catalogs), that database will be displayed as eligible for
deletion.For more information , see “Optional parameters” on page 30.
Attention: Failure to provide all pertinent and correct information can result in
erroneous output. To prevent this, see the next consideration.
v If you have more than one Oracle database, back up each Oracle target database
to its own file space on the Tivoli Storage Manager server. To do this, use the
tdpo_fs option in the tdpo.opt file. In addition, it is highly recommended that
you use a separate Data Protection for Oracle options file for each database that
you back up to Tivoli Storage Manager. In this way, it is only necessary to
synchronize one catalog at a time (once for each target database), thus
minimizing the display of wrong information in the PICK window.
v Make sure to use the same tdpo.opt file that was used for the original backup.


Syncdb Command
This is the only command available to tdposync utility.

Syntax
TDPOSYNC syncdb
installed tdpo.opt
-TDPO_OPTFILE=
pathname

1
-NUMCATalogs=
number

Optional parameters
This is the options file that is used by the utilities and the Data Protection
for Oracle library. This file contains the information for the Tivoli Storage
Manager server name and address that tdposync needs for synchronizing.

Note: For syncdb TDPO_OPTFILE, you must specify the same options file
values that were used to perform the original backup operations.
-NUMCATalogs=number
This parameter specifies the number of Oracle catalog databases that you
want to synchronize and prompts you for information for each catalog. .
Specify this option only when you use multiple Oracle catalogs to back up
multiple target databases to the same Tivoli Storage Manager server under
the same file space, node name, and owner name.
According to the number you specify for -numcatalogs, you are prompted
for the user name, password, and connect string for each. If you do not
specify -numcatalogs, the default is 1, and you are prompted only once.

For each catalog, you are prompted for the following information:
v Catalog # User Name:
v Catalog # Password:
v Catalog # Connect String:
You are also prompted for the following date information to narrow your search:
v From Date: (MM/DD/YYYY)
v To Date: (MM/DD/YYYY)
If no dates are specified, Data Protection for Oracle displays all objects that are not
in sync.


Example
When you specify the syncdb -numcatalogs parameter, you are prompted for
input for each catalog on the node. This example assumes two separate RMAN
catalogs (rman, rman2):

C:TivoliTsmAgentOba>tdposync syncdb -numcatalogs=2 -TDPO_OPTFILE=c:RMAN
scriptstdpo.opt

Catalog 1 User Name: rman

Catalog 1 Password: rman

Catalog 1 Connect String: rman

From Date (MM/DD/YYYY): 01/01/2007

To Date (MM/DD/YYYY): 01/11/2007

Catalog 2 User Name: rman2

Catalog 2 Password: rman2

Catalog 2 Connect String: rman2

From Date (MM/DD/YYYY): 01/01/2007

To Date (MM/DD/YYYY): 01/11/2007

Note: From Date implicitly searches from time=00:00:01 and To Date implicitly
searches to time=23:59:59 of the same day.

PICK Window
The PICK window provides the following useful information to help you decide if
the files displayed are indeed out of synchronization with the Oracle catalog:
v The node with which you are querying the Tivoli Storage Manager server
v The date of the file backup
v The size of the backup
v The backup name (hlorcntll)

Attention: Use caution when selecting files for deletion. If you are unsure that
the files in question are really out of synchronization, do further research before
deleting them. Once you delete files, they cannot be restored.


Example: This is an example output of the PICK window:

Tivoli Data Protection for Oracle
Synchronize utility PICK Window
Node Name: AGENT_NODE

Backup Date Size Backup Name
------------------------------------------------------------------------
1. | 01/09/2007 09:19:59 50.35MB adsmorcorcnt1kc2cnfv_1_1
2. | 01/02/2007 11:36:20 427.08MB adsmorcorcnt4kc3cnfv_1_1
3. | 01/02/2007 07:14:30 508.00MB adsmorcorcnt4qcgdhfr_1_1
4. | 01/02/2007 07:21:38 763.94MB adsmorcorcnt4ocf8999_1_1
7. | 01/09/2007 11:00:13 656.69MB adsmorcorcnt4rch25jk_1_1
|
|
|
0---------10--------20--------30--------40--------50--------60--------70
<U>=Up <D>=Down <T>=Top <B>=Bottom <R#>=Right <L#>=Left
<G#>=Goto Line # <#>=Toggle Entry <+>=Select Al<->=Deselect All
<#:#+>=Select A Range <#:#->=Deselect A Range <O>=Ok <C>=Cancel
pick>

Files selected for deletion are marked by a plus (+). To delete selected files:
1. Enter OK at the PICK prompt.
A warning message appears to confirm deletion of the selected files.
2. Enter Yes to delete the selected files from the Tivoli Storage Manager server.

Attention: The deletion process is irreversible. Use caution when selecting files
for deletion.


Appendix A. Quick configuration guide
This section provides instructions on how to perform a quick configuration of Data
Protection for Oracle on a Windows XP machine. This procedure uses default
settings and requires minimal configuration tasks. It minimizes set up time and
allows you to proceed quickly to a state where you can begin backing up your
Oracle databases. See page 11 for detailed instructions on how to customize Data
Protection for Oracle for your environment and processing needs.
1. Install Data Protection for Oracle. Detailed installation instructions are available
on page 5.
2. Change to the C:Program FilesTivoliTSMAgentOBA directory and copy the
tdpo.opt.smp file to tdpo.opt. Edit the tdpo.opt file to include these options:
dsmi_orc_config C:Program FilesTivoliTSMAgentOBAdsm.opt
dsmi_log C:Program FilesTivoliTSMAgentOBA

v More information about these options is available on page 12.
3. In this same directory, copy the dsm.smp file to dsm.opt. Edit the dsm.opt file to
include these options:
COMMMethod TCPip
TCPServeraddress x.x.x.x
PASSWORDAccess generate
NODename hostname_oracle

Replace x.x.x.x with the IP address of the Tivoli Storage Manager server to
which Data Protection for Oracle will back up data.
v More information about these options and the dsm.opt file is available on
page 14.
4. Register the node (specified in Step 3) to the Tivoli Storage Manager server
with the following command:
REG NODE hostname_oracle password maxnummp=2 passexp=0

Where hostname is the name of the machine where Data Protection for Oracle is
installed and password is the password for this node.
5. Make sure the Oracle user has the following permissions:
v Read and Write permission to the C:Program FilesTivoliTSMAgentOBA
directory.
| 6. Change to the C:Program FilesTivoliTSMAgentOBA directory and run the
| tdpoconf password command (as Oracle user) to generate the password file.
| You will be prompted to enter the password from Step 4 three times.
| v More information about this command is available on page 26.
7. Run the tdpoconf showenvironment command to confirm proper
configuration.
v More information about this command is available on page 27.
8. As Oracle user, run your RMAN backup script with the
ENV=(TDPO_OPTFILE="C:Program FilesTivoliTSMAgentOBAtdpo.opt")
parameter specified.
For example:


run
{
’ENV=(TDPO_OPTFILE="C:Program FilesTivoliTSMAgentOBAtdpo.opt")’;

backup
filesperset 5
format ’df_%t_%s_%p’
(database);

}

Note that the allocate channel entry is divided on two lines after the parms
option to accommodate page formatting.
v More information about RMAN backup scripts is available on page 21.


Appendix B. Using the Tivoli Storage Manager scheduler
This section describes how to use the Tivoli Storage Manager scheduler with Data
Protection for Oracle to automate online backups of Oracle server databases. The
example illustrates the use of the Tivoli Storage Manager Version 5.4
backup-archive client scheduler.

Considerations
The Tivoli Storage Manager backup–archive client must reside on the same
machine as Data Protection for Oracle for the Tivoli Storage Manager scheduler
to function.

After Data Protection for Oracle has been registered to a Tivoli Storage Manager
server and installed on the Oracle server, perform these steps:
1. On the Tivoli Storage Manager server:
| a. Define a schedule to run a Windows command file in the policy domain to
| which Data Protection for Oracle is registered.
b. Associate the Data Protection for Oracle node to the defined schedule.
2. On the Oracle Server where Data Protection for Oracle is installed:
a. Install the Tivoli Storage Manager backup-archive client scheduler as a
Windows service for Data Protection for Oracle. If a scheduler service
already exists for the regular Tivoli Storage Manager backup-archive client,
install another one for Data Protection for Oracle.
b. Configure the scheduler service to run under the Oracle Site Services
account or an account that has Oracle authorization.
c. Define a command file that contains Data Protection for Oracle commands
to do the desired backup.

Note: Refer to Windows documentation for details on creating a Windows
command file.
d. Start the scheduler service installed in step 2a (this is step 2.1 in some
HTML browsers).

Setting up a schedule
For consistency, this procedure uses specific information. However, you can define
a command file with any set of commands you choose. This allows you to use the
same command file to define schedules on other Tivoli Storage Manager servers.
All command information is presented as command-line interface entries.

This schedule in this procedure contains the following settings:
v The Data Protection for Oracle node name is NodeA1.
v The password for node name NodeA1 is PasswordA1.
v The policy domain to which node name NodeA1 is registered is PolicyA1.
v The schedule is a daily backup of an online Oracle database.
v The scheduled backup begins between 9:00 and 9:15 PM.


Part I: On the Tivoli Storage Manager server
1. Define the following schedule on the Tivoli Storage Manager server. You can
enter the command on the Tivoli Storage Manager server console or on an
Administrative Client. The Administrative Client does not have to be running
on the same system as the Tivoli Storage Manager server.
define schedule PolicyA1 daily_orcbkup description="07Daily Online DB Backup"
action=command objects="C:Program FilesTivoliTSMAgentOBAschedorcsched.cmd"
starttime=21:00 duration=15 durunits=minutes period=1 perunits=day
dayofweek=any
The following message must display before proceeding to Step 2:
ANR2500I Schedule daily_orcbkup defined in policy domain PolicyA1.

2. Issue the following command to associate the Data Protection for Oracle node
to the backup schedule defined in Step 1:
define association PolicyA1 daily_orcbkup NodeA1
The following message must display before proceeding to Part II:
ANR2510I Node NodeA1 associated with schedule orc_dailybkup
in policy domain PolicyA1.

Summary:
v A backup schedule is now defined on the Tivoli Storage Manager server.
v The backup schedule runs a command file (orcsched.cmd) located in the
C:Program FilesTivoliTSMAgentOBAsched directory.
v The backup is performed once a day around 9:00 PM.
v The backup schedule can start on any day of the week.
v You can run the Tivoli Storage Manager query schedule and query
association commands to confirm that the schedule and node association are
set correctly.

Part II: On the workstation with the Oracle Server:
This example assumes:
v The Tivoli Storage Manager backup-archive client is installed on the Oracle
Server in the directory:
C:Program FilesTivoliTSMbaclient
v The Data Protection for Oracle for the Oracle server is installed in the directory:
C:Program FilesTivoliTSMAgentOBA
v The options files in each of these directories has been updated so that the
communication parameters point to the Tivoli Storage Manager server.
1. Login using a Windows account that has administrative privileges.
2. Open a Windows command prompt window.
3. Change to the backup-archive client installation directory with this command:
C:>cd Program FilesTivoliTSMbaclient

4. Use the Tivoli Storage Manager Client Service Configuration Utility (dsmcutil)
to install the Tivoli Storage Manager Scheduler Service. Issue the command
from your current location in the backup-archive client installation directory.


For example:
dsmcutil inst /name:"TSM Oracle Bkup Scheduler"
/node:nodea1 /password:passworda1 /autostart:yes
/clientdir:"C:Program FilesTivoliTSMbaclient"
/optfile:"C:Program FilesTivoliTSMAgentOBAdsm.opt"
/validate:yes

You can modify the command to contain options specific to your schedule.
This is an example of the output:
TSM Windows Client Service Configuration Utility
Command Line Interface - Version 5, Release 4, Level 0.0
(C) Copyright IBM Corporation, 1990, 2007, All Rights Reserved.
Last Updated Dec 31 2006
TSM Api Verison 5.4.0

Command: Install TSM Client Service
Machine: ABC-ARTXNC(Local Machine)

Installing TSM Client Service:

Machine : ABC-ARTXNC
Service Name : TSM Oracle Bkup Scheduler
Client Directory : C:Program FilesTivoliTSMbaclient
Automatic Start : yes
Logon Account : LocalSystem

The service was successfully installed.

Creating Registry Keys ...

Updated registry value ’ImagePath’ .
Updated registry value ’EventMessageFile’ .
Updated registry value ’TypesSupported’ .
Updated registry value ’TSM Oracle Bkup Scheduler’ .
Updated registry value ’ADSMClientKey’ .
Updated registry value ’OptionsFile’ .
Updated registry value ’EventLogging’ .
Updated registry value ’ClientNodeName’ .

Generating registry password ...
Authenticating TSM password for node NODEA1 ...

Connecting to TSM Server via client options file
’C:Program FilesTivoliTSMAgentOBAdsm.opt’ ...

Password authentication successful.

The registry password for TSM node NODEA1 has been updated.

Starting the ’TSM Oracle Bkup Scheduler’ service .......

The service was successfully started.
Note that the options file that is defined for Data Protection for Oracle is used
by the scheduler when validating the node and password. The options files are
also used when contacting the Tivoli Storage Manager server for schedule
information. This example assumes that the dsm.opt file is updated so that the
communication parameters point to the Tivoli Storage Manager server to which
the Oracle databases are to be backed up.

Appendix B. Using the Tivoli Storage Manager scheduler 37

If this message appears:
A communications error occurred connecting to the TSM server

Ensure that the dsm.opt file contains entries that point to the correct Tivoli
Storage Manager server. Also ensure that the Tivoli Storage Manager server is
running. If you have to correct one of these, enter the following command:
dsmcutil remove /name:"TSM Oracle Bkup Scheduler"

Then enter the command given in Step 4.
5. Data Protection for Oracle must be running under the Oracle Site Services
account in order to be able to access the Oracle backup API. The Data
Protection for Oracle scheduler service must logon using that account. The
scheduler service account information can be specified using the services applet
in the control panel.
| 6. Create a batch file called orcsched.cmd and place it in the following location:
| C:Program FilesTivoliTSMAgentOBAschedorcsched.cmd

| The orcsched.cmd file must contain these variables with the following values:
| oracle_sid
| Specify the Oracle system identifier for the instance to be used in the
| scheduled backup. A value of ilr is used in the example.
| ora_exe
| Specify the complete path and file name of the Oracle RMAN
| executable file. A value of c:oracleora91binrman.exe is used in the
| example.
| cmdfile
| Specify the complete path and file name of the Oracle command file. A
| value of C:rmanbkdb.rmn is used in the example.

| Note: Note that since the scheduler service runs from the Windows system
| directory, it is important that complete paths be specified for all file names
| and non-system commands. That is because the scheduler service checks
| the Windows system directory for input and produces its output by
| default.
| The following is an example of the orcsched.cmd file:
| rem orcsched.cmd
| rem =======================
|
| rem =======================
| rem setting oracle sid
| rem =======================
| set oracle_sid=ilr
|
| rem =======================
| rem set orc executable binary
| rem =======================
| set ora_exe=c:oracleora91binrman.exe
|
| %ora_exe% cmdfile ‘C:rmanbkdb.rmn’
| The following is an example of the bkdb.rmn file:
| connect target agnttest/agttest
| run
| {
| allocate channel ch1 type ’SBT_TAPE’ parms
| ’ENV=(TDPO_OPTFILE=C:oracletdpo.opt)’;


| backup (database);
| release channel ch1;
| }

| Note: Note that the allocate channel entry for each channel is divided on two
| lines after the parms option to accommodate page formatting. The actual
| bkdb.rmn file must have the allocate channel entry for each channel
| specified on one line.
7. The scheduler service is now installed, but has not been started. To start the
service, issue this command in the Windows command prompt:
net start "TSM Oracle Bkup Scheduler"
The following message is displayed:
The TSM Oracle Bkup Scheduler service is starting.
The TSM Oracle Bkup Scheduler service was started successfully.
Note that because autostart=yes is specified, the Tivoli Storage Manager
scheduling service is automatically started each time the Windows system is
rebooted.
Your system is now ready to run automatic daily online database backups.
Notes:
1. If you want to use the Tivoli Storage Manager server-prompted scheduling
mode, you must ensure that the Data Protection for Oracle options file has the
tcpclientaddress and tcpclientport options specified. If you want to run more
than one scheduler service, use the same tcpclientaddress. However, you must
use different values for tcpclientport in addition to the different node names.
Scheduling Data Protection for Oracle as well as the regular Windows
backup-archive client is an example of running more than one scheduler
service.
Server-prompted scheduling is supported only when TCP/IP communication is
being used. By default, Data Protection for Oracle uses the polling schedule
mode.
2. If any changes that affect the scheduler service are made to the Data Protection
for Oracle options file, the scheduler service has to be restarted in order to pick
up the changes. An example of this is the Tivoli Storage Manager server
address, the schedule mode, or the machine TCP/IP address or port. This can
be done by entering these commands:
net stop "TSM Oracle Bkup Scheduler"
net start "TSM Oracle Bkup Scheduler"
3. The file named dsmsched.log contains status information for the Tivoli Storage
Manager scheduler service. Though the default directory is
TivoliTSMbaclientscheddsmsched.log, you can specify a different
directory, such as TivoliTSMAgentOBAscheddsmsched.log using the
schedlogname option in the Data Protection for Oracle options file.
4. If a Tivoli Storage Manager scheduler service is already installed on your
workstation (for the regular backups of the Windows system), you need to
install another one (with a unique name) to run the schedules defined for Data
Protection for Oracle. The Tivoli Storage Manager scheduler service needs a
different node name than the regular Tivoli Storage Manager backup-archive

Appendix B. Using the Tivoli Storage Manager scheduler 39

client. If the path you want to use has a space in it, for example C:Program
FilesTivoliTSMbaclient, you can place quotation marks around the section
of the path name that contains a space (C:"Program Files") You can also use
the short form of the path name. The short form of a path name is made up of
the first six characters in the path and is followed by a tilde (~) and unique
identifier. The following is an example of the short form of the path name:
C:Progr~1TivoliTSMbaclient


Appendix C. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This
section describes the following options for obtaining support for IBM software
products:
v “What to do when you encounter a problem”
v “Searching knowledge bases” on page 42
v “Obtaining fixes” on page 43
v “Receiving weekly support updates” on page 43
v “Contacting IBM Software Support” on page 44

What to do when you encounter a problem
If you encounter a problem while using Data Protection for Oracle or if you cannot
start Data Protection for Oracle, do the following:
1. Run the tdpoconf utility showenvironment command to collect information on
your options file (–TDPO_OPTFILE=) and specified output files (–outfile=).
2. If the above command ran successfully, check its output to see if the setup
worked as expected.
3. If the above command failed, check the tdpoerror.log and dsierror.log files. The
tdpoerror.log is a log file created in the installation directory by default. The
dsierror.log is generated by the Tivoli Storage Manager API when a problem
occurs with the Tivoli Storage Manager API setup.
4. Fix the problem and run the tdpoconf utility again.
5. If the problem persists, gather the following information:
v A problem description file that includes the command you used and the
session output you received when the problem occurred.
v The tdpo.opt file specified by TDPO_OPTFILE variable in the RMAN script
v The dsm.opt file specified by dsmi_orc_config in the tdpo.opt file
v The Data Protection for Oracle error log file (tdpoerror.log) in the following
location (listed from highest to lowest precedence):
– The value of the Tivoli Storage Manager API errorlogname option
specified in the dsm.opt file.
– The value of the dsmi_log environment variable.
– If a failure occurs during option processing for the initialization, the
tdpoerror.log file may be located in $ORACLE_HOME/bin.
v The Tivoli Storage Manager API error log file (dsierror.log) in the following
location (listed from highest to lowest precedence):
– The value of the Tivoli Storage Manager API errorlogname option
specified in the dsm.opt file.
– The value of the dsmi_log environment variable.
v The RMAN log file
v The Tivoli Storage Manager API trace file
To generate the Tivoli Storage Manager API trace file, add the following lines
in your dsm.opt file:
tracefile C:oracleadminrmantsmapi.out
traceflag service


v The node information on the Tivoli Storage Manager server. To obtain this
information, enter:
query node <nodename> format=detail
v The Tivoli Storage Manager server activity log. To obtain this information,
enter this Tivoli Storage Manager administrator command:
query actlog

Note that this command provides one previous hour of activity. Since the
activity log should be obtained for the time period immediately prior to the
failed operation until a few moments after the failed operation, you can
specify the following settings to obtain activity for the exact time of failure:
query actlog begindate=MM/DD/YYYY begintime=HH:MM:SS
v The Data Protection for Oracle trace file
To generate the Data Protection for Oracle trace file, add the following lines
in your tdpo.opt file:
tdpo_trace_flags orclevel0 orclevel1 orclevel2
tdpo_trace_file C:oracleadminrmantdpo.out

where:
orclevel0
Traces out function exit points when errors occur.
orclevel1
Traces out normal function entry and exit points.
orclevel2
Traces out more detailed information.

Note: Any path and file name can be specified for the tdpo_trace_file and
tracefile options. However, the directory must exist and have writable
rights.

Searching knowledge bases
You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center
IBM provides extensive documentation that can be installed on your local
computer or on an intranet server. You can use the search function of this
information center to query conceptual information, instructions for completing
tasks, and reference information.

Searching the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

To search multiple Internet resources for your product, go to this product support
web site: http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html and look for the section to search the support
knowledge base. From this section, you can search a variety of resources including:
v IBM technotes
v IBM downloads


v IBM Redbooks™
v Forums and newsgroups

You can also search the IBM Tivoli Storage Manager: Problem Determination Guide for
helpful diagnostic information at this Web site: http://publib.boulder.ibm.com/
infocenter/tivihelp/v1r1
/topic/com.ibm.itsmm.doc/update/main.html

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support.
2. Click Downloads and drivers in the Support topics section.
3. Select the Software category.
4. Select a product in the Sub-category list.
5. In the Find downloads and drivers by product section, select one software
category from the Category list.
6. Select one product from the Sub-category list.
7. Type more search terms in the Search within results if you want to refine your
search.
8. Click Search.
9. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at http://techsupport.services.ibm.com/guides/
handbook.html.

Receiving weekly support updates
To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support.
2. Click My support in the upper right corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select the product segment, Storage Management. A third
list is displayed.
7. In the third list, select the product sub-segment, Data Protection. A list of
applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
Tivoli Storage Manager for Databases.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email
on the Edit profile tab.

Appendix C. Support information 43

11. Select Please send these documents by weekly email.
12. Update your e-mail address as needed.
13. In the Documents list, select Software.
14. Select the types of documents that you want to receive information about.
15. Click Update.

If you experience problems with the My support feature, you can obtain help in
one of the following ways:
Online
Send an e-mail message to erchelp@ca.ibm.com, describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software Support
IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2® and WebSphere® products that
run on Windows or UNIX® operating systems), enroll in Passport Advantage® in
one of the following ways:
Online
Go to the Passport Advantage Web site at http://www.lotus.com/
services/passport.nsf/WebDocs/
Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at http://techsupport.services.ibm.com/guides/
contacts.html and click the name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at https://techsupport.services.ibm.com/
ssr/login.
v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries, zSeries,
and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name
of your geographic region for phone numbers of people who provide support for
your location.


To contact IBM Software support, follow these steps:
1. “Determining the business impact”
2. “Describing problems and gathering information”
3. “Submitting problems” on page 46

Determining the business impact
When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information
When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What is the operating system platform, version, and release level of the machine
on which your Tivoli Storage Manager server product is installed?
v What is the version and release level of your Tivoli Storage Manager server
product? Enter the query status command to determine this information. For
example:
query status
v The version and release level of your Data Protection for Oracle product and the
Tivoli Storage Manager API. You can locate this in the readmedporc_enu.htm file
or by performing the following:
– In the Control Panel of the Start Menu, go to Add/Remove Programs, select
IBM Tivoli Storage Manager for Databases - Oracle and click support information.
– Right-click on the tsmapi.dll file (located in the *SystemRoot*system32
directory), select Properties, then select Version.
v What software versions were you running when the problem occurred?
v What are the bit levels of the Oracle instance, Data Protection for Oracle, and
Tivoli Storage Manager API? These bit levels should be the same among these
three products.
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you create the problem again? If so, what steps were performed to create
the problem?

Appendix C. Support information 45

v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site at
http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at http://
techsupport.services.ibm.com/guides/contacts.html and click the name
of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround for you to implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
IBM product support Web pages daily, so that other users who experience the
same problem can benefit from the same resolutions.

For more information about problem resolution, see Searching knowledge bases
and Obtaining fixes.


Appendix D. Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in this product enable users to do the following:
v Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include features to aid
accessibility:
v All documentation is available in both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.

Navigating the interface using the keyboard
Standard shortcut and accelerator keys are used by the product and are
documented by the operating system. Refer to the documentation provided by
your operating system for more information.

Magnifying what is displayed on the screen
You can enlarge information on the product windows using facilities provided by
the operating systems on which the product is run. For example, in a Microsoft
Windows environment, you can lower the resolution of the screen to enlarge the
font sizes of the text on the screen. Refer to the documentation provided by your
operating system for more information.


Appendix E. Messages
ANU0003S An internal processing error has ANU0057E The checksum in the license file
occurred. (licensefile) does not match the license
Explanation: An internal processing error has string text.
occurred. Explanation: An attempt was made to read
System action: Processing ends. information from the license file. The checksum was
User response: Retry the operation. If this error not valid so it appears that the license file is not at the
persists, contact your service representative. correct level.
System action: Processing ends.
User response: Reinstall the product.
ANU0004E An unknown error has been detected.
Explanation: An internal processing error has
occurred that prevents the generation of a message for ANU0058E The ’Try and Buy’ license has expired.
a return code. Explanation: This ’Try and Buy’ license that was
System action: Processing continues. detected has expired.
User response: Retry the operation. If this error System action: Processing ends.
persists, contact your service representative. User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
ANU0005E Out of memory. Stop other processes
and try the operation again.
Explanation: The machine has run out of memory. ANU0100E Incomplete command:
System action: Processing continues. Explanation: This message displays the incomplete
User response: Close unnecessary processes and try command that was entered.
the operation again. System action: Processing ends.
User response: Re-enter the complete command.
ANU0053E License file (licensefile) could not be
opened. ANU0101E Invalid argument:
Explanation: An attempt to read from the license file Explanation: This message displays the command that
failed. was entered, up to and including the invalid command
System action: Processing ends. or option argument that was detected.
User response: Install the product again. This ensures System action: Processing ends.
that the correct license file is installed. User response: Re-enter the command specifying a
valid argument for the command or option.
ANU0054E Read failure on license file (licensefile).
Explanation: An attempt was made to read from the ANU0102E Invalid command:
license file. This attempt failed. Explanation: This message displays the invalid
System action: Processing ends. command that was entered.
User response: Reinstall the product. This will ensure System action: Processing ends.
that the correct license file is installed. User response: Re-enter a valid command.

ANU0055E Write failure on license file (licensefile). ANU0103E Invalid option for the specified
Explanation: An attempt to write to the license file command:
failed. Explanation: This message displays the command that
System action: Processing ends. was entered, up to and including the option that was
User response: Make sure enough space exists on the detected as invalid for the command.
workstation to write to the license file. If enough space System action: Processing ends.
exists, run the command again. User response: Re-enter the command specifying valid
command options.
ANU0056E Data in the license file (licensefile) is not
in a valid format. ANU0104E Invalid option:
Explanation: An attempt to read information from the Explanation: This message displays the command that
license file failed. was entered, up to and including the invalid option
System action: Processing ends. that was detected.
User response: Install the product again. System action: Processing ends.


User response: Re-enter the command specifying valid
ANU0151E Errors occurred while processing the
command options.
request.
Explanation: Attempting to process the request
ANU0105E Missing argument: entered, an error occurred.
Explanation: This message displays the command that System action: Processing ends.
was entered, up to and including the command or User response: Attempt to determine the source of the
option whose required argument is missing. errors from viewing the log file. Correct the problems
System action: Processing ends. and try running the command again.
User response: Re-enter the command specifying a
valid argument for the command or option.
ANU0152I Performance stats: seconds seconds spent
in apicall API calls
ANU0132W Tracing could not be started. Processing Explanation: The indicated number of seconds were
will continue. spent making API calls for the indicated system.
Explanation: A problem prevented tracing from System action: Processing continues.
beginning. User response: None
System action: Processing will continue with the
command entered.
ANU0153I Performance stats: seconds seconds spent
User response: Refer to the other messages that
in function
display with this message to determine the problem.
Explanation: The indicated number of seconds were
spent the named function.
ANU0133W Could not locate installation directory. System action: Processing continues.
Attempting to continue... User response: None
Explanation: An attempt was made to read the
registry to determine where the Tivoli Data Protection
ANU0154E The Data Protection for Oracle
application client was installed. This attempt failed.
application client cannot work with the
version of the Tivoli Storage Manager
command entered.
API you have installed. Please install
User response: There should be other messages along
version version.release.level or greater.
with this one. Refer to the other messages to determine
Explanation: The version of the Tivoli Storage
the problem. If the problem can not be determined, it
Manager API currently installed on the system is older
may be necessary to reinstall the application client
than the version used to build the Data Protection for
code. This will ensure that the registry entries are set
Oracle application client.
up correctly.
User response: Install a version of the Tivoli Storage
ANU0134W Could not locate log directory. Manager API at or later than the indicated level. A
Processing will continue... copy is distributed with the Data Protection for Oracle
Explanation: An attempt was made to read the application client.
registry to determine where the Tivoli Data Protection
application client log is located. This attempt failed.
ANU0155E The Data Protection for Oracle
application client cannot work with the
command entered.
release of Tivoli Storage Manager API
User response: There should be other messages along
you have installed. Please install release
with this one. Refer to the other messages to determine
version.release.l evel or greater.
the problem. If the problem can not be determined, it
Explanation: The release of the Tivoli Storage
may be necessary to reinstall the application client
Manager API currently installed on the system is older
code. This will ensure that the registry entries are set
than the release used to build the Data Protection for
up correctly.
Oracle application client.
ANU0150I Operation canceled by user. User response: Install a release of the Tivoli Storage
Explanation: The user has requested that the Data Manager API at or later than the indicated level. A
Protection for Oracle application client end by entering copy is distributed with the Data Protection for Oracle
ctrl-C. application client.
User response: None


ANU0156E Could not load the Tivoli Storage ANU0200E File (filename) could not be opened for
Manager API. reading.
Explanation: The Tivoli Storage Manager API could Explanation: An attempt was made to open a file for
not be loaded. reading. This attempt failed.
System action: Processing ends. System action: Processing ends.
User response: Ensure the Tivoli Storage Manager API User response: None
is correctly installed. Run the Data Protection for Oracle
application client with the /TRACEFLAGS=API
ANU0201E File (filename) could not be opened for
/TRACEFILE=filename options and view the tracefile
writing.
to determine why it could not be loaded. Another
Explanation: An attempt was made to open a file for
possible cause is that the TSMAPI.DLL does not exist in
writing. This attempt failed.
the system directory. Re-install the Tivoli Storage
Manager API, if this is the case.
User response: None

ANU0160E An authentication error occurred with
ANU0202E Read failure on file (filename).
your stored Tivoli Storage Manager
Explanation: An attempt was made to read from a
password.
file. This attempt failed.
Explanation: You were unable to log on to the Tivoli
Storage Manager server due an authentication error.
User response: None
System action: Processing stops.
User response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your ANU0203E Write failure on file (filename).
Tivoli Storage Manager server administrator. Explanation: An attempt was made to write to a file.
This attempt failed.
ANU0161E Authentication error. The password
User response: None
entered is not valid. You are not logged
on to the Tivoli Storage Manager server.
Explanation: An incorrect password was entered. ANU0204E File (filename) could not be closed.
System action: Processing stops. Explanation: An attempt was made to close a file.
User response: Enter the correct Tivoli Storage This attempt failed.
Manager password and try again. System action: Processing ends.
User response: None
ANU0162E The passwords entered do not match.
Please enter them again. ANU0205E File (filename) statistics could not be
Explanation: An incorrect password was entered. obtained.
System action: Processing stops. Explanation: An attempt was made to obtain file
User response: Enter the passwords again. statistics. This attempt failed.
User response: None
ANU0163E The directory path needs to be
fully-qualified.
Explanation: The /intopath option was specified ANU0206E Directory (directory) could not be created.
without a fully-qualified path. Explanation: An attempt was made to create a
System action: Processing stops. directory. This attempt failed.
User response: Enter the command again and specify System action: Processing ends.
a fully-qualified path in the /intopath option. User response: None

ANU0167E The fully-qualified file name is too ANU0207E Directory path (directorypath) is too long.
long. Explanation: An attempt was made to use a directory
Explanation: An attempt was made to use a path that was too long. This attempt failed.
fully-qualified file name that was too long. This System action: Processing ends.
attempt failed. User response: None
User response: None
ANU0208E There is not enough disk space for the
operation attempted.
Explanation: An attempted operation required more
disk space than was available. The attempt failed.

Appendix E. Messages 51

User response: None
ANU0215E All backup objects do not have the same
management class backup copy
ANU0209E The rename of file (filename1) to destination.
(filename2) failed. Explanation: In order to maintain backup data
Explanation: An attempt was made to rename a file. integrity, multiple backup objects are sent to the Tivoli
This attempt failed. Storage Manager server within a single transaction. All
System action: Processing ends. backup objects within a single transaction are required
User response: None to have the same management class backup copy
destinations.
ANU0210E The Tivoli Storage Manager high level User response: Contact your Tivoli Storage Manager
qualifier is too long. server administrator.
Explanation: An attempt was made to use a Tivoli
Storage Manager high level qualifier that was too long.
This attempt failed. ANU0216E Unable to obtain space information for
System action: Processing ends. volume (volumename).
User response: None Explanation: An attempt was made to obtain space
information for a volume. This attempt failed.
ANU0211E The Tivoli Storage Manager low level User response: None
qualifier is too long.
Storage Manager low level qualifier that was too long. ANU0217E The Tivoli Storage Manager filespace
This attempt failed. name is invalid.
System action: Processing ends. Explanation: The filespace name or directory
User response: None delimeter is invalid.
User response: Check that the filespace name length,
ANU0212E The Tivoli Storage Manager filespace characters, and directory delimeters are valid.
name is too long.
Storage Manager filespace name that was too long. This ANU0218E The Tivoli Storage Manager high level
attempt failed. qualifier is invalid.
System action: Processing ends. Explanation: The high level qualifier name or
User response: None directory delimeter is invalid.
User response: Check that the high level qualifier
ANU0213E The maximum number of objects name length, characters, and directory delimeters are
allowed per Tivoli Storage Manager valid.
transaction is t oo small.
Explanation: In order to maintain backup data
integrity, multiple backup objects are sent to the Tivoli ANU0219E The Tivoli Storage Manager low level
Storage Manager server in a single transaction. The qualifier is invalid.
Tivoli Storage Manager server has indicated that the Explanation: The low level qualifier name or directory
maximum number of objects allowed per transaction is delimeter is invalid.
less than the minimum required by the Data Protection System action: Processing ends.
for Oracle application client. User response: Check that the low level qualifier
System action: Processing ends. name length, characters, and directory delimeters are
User response: Increase the maximum number of valid.
objects allowed per transaction on the Tivoli Storage
Manager server and retry the operation.
ANU0256E The password in your Tivoli Storage
Manager options file has expired. Please
ANU0214E The backup object’s management class change your password on the Tivoli
backup copy group does not exist. Storage Manager server using the
Explanation: The Tivoli Storage Manager server has ’change password’ command and then
indicated that the backup object’s management class either change or remove the password
backup copy group does not exist. value in your options file.
System action: Processing ends. Explanation: Your Tivoli Storage Manager password
User response: Contact your Tivoli Storage Manager has expired. You need to change your password.
server administrator. System action: Processing ends.
User response: Obtain a new password for your Tivoli
Storage Manager server; node using the change


password command or by asking your Tivoli Storage
ANU0264I Could not find the default browser
Manager Administrator to change your password.
defined. An attempt will be made to use
Microsoft Internet Explorer.
ANU0257E Your password has expired. Explanation: An attempt was made to read the
Explanation: Your Tivoli Storage Manager password registry to determine the default browser. However, a
has expired. A new password needs to be obtained. default browser is not defined. A determination will be
System action: Processing ends. made where Microsoft Internet Explorer is installed.
User response: Obtain a new password for your Tivoli System action: Processing continues.
Storage Manager node using the change password User response: It is possible that a default browser is
command or by asking your Tivoli Storage Manager not defined for the system. This is okay. An attempt
Administrator to change your password. will be made to use Microsoft Internet Explorer.

ANU0258E You did not enter a valid password. ANU0265E Could not find Internet Explorer.
Processing ends. Explanation: An attempt was made to read the
Explanation: The password that was entered was not registry to determine where Microsoft’s Internet
a valid password. Explorer was installed. This attempt failed.
System action: Processing ends. System action: Processing ends.
User response: Re-enter the command specifying a User response: Make sure that the registry is set up
valid password. correctly for Internet Explorer.

ANU0259E The password you entered for ANU0266E Could not find the Tivoli Storage
verification does not match the Manager HTML books.
password you entered for your new Explanation: An attempt was made to read the
password. Your password will not be registry to determine where the Tivoli Storage Manager
changed. books were installed. This attempt failed.
Explanation: The password you entered for System action: Processing ends.
verification of your new password does not match the User response: It may be necessary to reinstall the
new password that was entered. application client code. This will ensure that the
System action: Processing ends. registry entries are set up correctly.
User response: Try again to change your password
being sure to enter the same password for the new
ANU0267E The verify password entered does not
password and for the verification password.
match the new password entered.
Explanation: The verify password does not match the
ANU0260I Password successfully changed. new password.
Explanation: The change password command System action: Processing ends.
completed successfully User response: Retry the command with a matching
System action: Processing ends. verify password.
User response: None
ANU0300E Invalid restore type.
ANU0261I There are no backups for the server Explanation: The type of restore requested is invalid.
named servername. System action: Processing ends.
Explanation: There are no backups on the Tivoli User response: Re-enter the command specifying a
Storage Manager server for the specified server name. valid restore type.
User response: None
ANU0301E Invalid backup type.
Explanation: The type of backup requested is invalid.
ANU0263E Failed to start Web browser with a System action: Processing ends.
return code of returncode. User response: Re-enter the command specifying a
Explanation: An attempt was made to start the web valid backup type.
browser to view the TSM HTML b ook. This attempt
failed.
ANU351E Invalid trace keyword - ’keyword’
Explanation: A TRACEFLAG option in the user
User response: Start your web browser manually and
configuration file or on the command line is incorrect.
point it to bookfrm.htm in the agent htm directory.
System action: Client program did not initialize or
tracing was not enabled in the applet.
User response: Correct the value.


ANU357E Unable to open trace output file ANU385E Unable to delete symbolic link ’link’.
file-name. Explanation: Log ’linkname’ cannot be a symbolic link.
Explanation: A TRACEFILE option in the user System action: Processing stops.
configuration file or on the command line used a User response: Delete the symbolic link ’linkname’.
directory path and file-name combination to which you
do not have write access.
ANU476E program-name: cannot open file file-spec:
System action: Client program did not initialize.
error.
User response: Change the TRACEFILE value so that
Explanation: TDP cannot open the file.
it is a location to which you have write access.
System action: TDP cannot complete the requested
operation.
ANU366E Unable to close trace output file User response: Retry the operation. If the problem
file-name. continues, check with your system administrator.
Explanation: An error occurred during the closing of a
trace output file-name (for example, not enough disk
ANU487E Specifying the error log ’link’ as a
space).
symbolic link is not allowed.
System action: Processing continues.
Explanation: Error log ’linkname’ cannot be a symbolic
User response: Check the options.doc file for a
link.
description of possible causes of the error, or see your
System action: The symbolic link ’linkname’ is deleted,
system administrator.
the error log is recreated, and processing stops.
User response: Check the location of the new error
ANU367E Unable to write to trace file tracefile. log. To specify the location of the error logs, refer to the
Tracing disabled. user’s manual for the ’errorlogname’ option and
Explanation: An error occurred when writing to the ’DSM_LOG’ environmental variable.
specified tracefile.
System action: Tracing is disabled. Processing
ANU488E Initialization functions cannot open the
continues.
error log: log-name. errno = errno-value,
User response: Ensure the device that the tracefile
Explanation: The file log-name could not be opened
access is available and has sufficient space for the
during initialization. The system set the error code
tracefile. Retry the command.
errno-value. If the reason given is ″access denied,″ the
current user does not have permission to write to the
ANU368E Invalid trace file name (name too long). log in the directory specified. It is also possible that no
Explanation: A TRACEFILE option in the preferences space is available at the given log location.
files used a file name that is too long. System action: Processing terminates.
System action: Client program did not initialize. User response: Set the DSM_LOG (or DSMI_LOG)
User response: Change the file name used as the environment variable to a directory into which the
TRACEFILE so that it is equal to or less than 255 current user can write. You may also use the
characters in length. ERRORLOGNAME option to specify a file to which the
current has write permission.
ANU383E Specifying the trace file ’link’ as a
symbolic link is not allowed. ANU495E Failure writing to a Tivoli Storage
Explanation: Trace file ’linkname’ cannot be a symbolic Manager log or log-related file: file-name,
link. errno = errno-value, reason
System action: The symbolic link ’linkname’ is deleted, Explanation: A failure was encountered when writing
the trace file is recreated, and processing stops. to one of the log files or a related file named file-name.
User response: Specify the trace file location with the The system set the error code errno-value. reason is the
’tracefile’ option. system explanation of that error code. Among other
things, it is possible that no space is available at the
given log location.
ANU384E Symbolic link ’linkname’ to ’target’ was
System action: Processing terminates.
successfully deleted.
User response: Set the DSM_LOG (or DSMI_LOG)
Explanation: Log ’linkname’ cannot be a symbolic link.
environment variable to a directory with adequate
System action: The symbolic link ’linkname’ is deleted,
space to write the log data.
the log is recreated, and processing stops.
User response: Check the location of the new file. To
specify the location of log files, refer to the user’s
manual for the ’errorlogname’ option, the
’schedlogname’ option, and the ’DSM_LOG’
environmental variable.


ANU496I TDP is converting the log-file from ANU2501E Oracle passed a null file name
continuous (pruning) mode to wrapping Explanation: Null file name passed by Oracle.
mode. This process may take several System action: The system returns to the calling
minutes. procedure.
Explanation: The log-file was previously in continouos User response: Contact your system administrator.
mode where the only size control was through the use
of ERRORLOGRETENTION or
ANU2502E Wrong data block size
SCHEDLOGRETENTION option. This is the first
Explanation: Wrong data block size.
occasion where ERRORLOGMAX or SCHEDLOGMAX
System action: The system returns to the calling
is specified for this log, so its format must be changed
procedure.
and old data saved.
User response: Contact your system administrator.
System action: Transition processing continues.
User response: None.
ANU2503E Backup object ’filespacehlll’ already exists
on TSM Server.
ANU497I TDP is converting the log-file from
Explanation: The object has previously been backed
wrapping mode to continuous (pruning)
up to the TSM Server.
mode. This process may take several
System action: Data Protection for Oracle returns to
minutes.
the calling procedure.
Explanation: The log-file was previously in wrapping
User response: If backing up an object, make sure
mode where the size control was through the use of the
Oracle is generating a unique backup object name.
ERRORLOGMAX or SCHEDLOGMAX option. This is
the first occasion where ERRORLOGMAX or
SCHEDLOGMAX is not specified for this log, so its ANU2504E Dissimilar Oracle handle
format must be changed and old data saved. Explanation: The handle passed from Oracle is not the
System action: Transition processing continues. same handle that TSM passed back.
User response: None. System action: The system returns to the calling
procedure.
ANU498I count log records processed.
Explanation: This is just a progress report to let you
know the process is still ongoing. ANU2505I End of file reached
System action: Transition processing continues. Explanation: End of file reached.
User response: None. System action: The system returns to the calling
procedure.
User response: None.
ANU501T Invalid Proxy Configuration Detected:
Target Node ’targetnode’ is not listed as a
valid node to proxy to for Node Name ANU2506E Wrong Read State
’nodename’. Explanation: The operation must be in READ state.
Explanation: The proxy node configuration on the System action: The system returns to the calling
TSM Server is not correct to support this VSS procedure.
operation. User response: Contact TSM support.
System action: The VSS operation stops.
User response: Contact the TSM Server administrator
to have the correct TSM Server GRANT PROXY ANU2507E Runtime API version is outdated
commands issued to enable proxy authority for the Explanation: Runtime API is lower than compile time
nodes. If the error persists, contact your service API.
representative. System action: The system returns to the calling
procedure.
User response: Check compile time API level, obtain
ANU2500E Oracle passed an invalid mode same or higher level of API library.
Explanation: Invalid mode passed by Oracle.
procedure. ANU2508E Wrong write state
User response: Contact your system administrator. Explanation: The operation must be in WRITE state.
procedure.
User response: Contact TSM support.


ANU2509E Invalid flag passed ANU2517E Try and Buy Evaluation period is over
Explanation: Oracle passed an invalid flag. for license file: license file
System action: The system returns to the calling Explanation: The Try and Buy Evaluation period is
procedure. over.
User response: Contact your system administrator. System action: The system returns to the calling
procedure.
User response: Purchase the product or discontinue
ANU2510E The Caller must be a root user
use.
Explanation: Only a UNIX root user can execute
password
System action: The system returns to the calling ANU2518E License file: license file not valid for this
procedure. application
User response: Contact your system administrator. Explanation: The license file is not intended for this
application.
ANU2511E Reduce the number of copies to that
procedure.
specified in RMAN
User response: Reinstall the license that came with
Explanation: The duplex copy feature has reached
Data Protection for Oracle.
maximum allowed copies.
procedure. ANU2519E Could not read password
User response: Reduce the number of backup copies Explanation: There is an invalid password or the
to that allowed by RMAN. password file cannot be not found.
procedure.
ANU2512E Could not open license file: license file
User response: Check that password file exists and is
Explanation: The license file could not be opened.
valid.
procedure.
User response: Check that the license file exists with ANU2521E Error opening file name. Check
the correct permissions. permissions.
Explanation: A directory could not be created.
ANU2513E Could not read license file: license file
procedure.
Explanation: The license file could not be read.
User response: Check that permissions allow the
creation of directories.
procedure.
User response: Check that the license file permissions
are correct. ANU2522E No memory available
Explanation: There is not enough system memory to
complete the action.
ANU2514E Could not write license file: license file
Explanation: The license file could not be written.
procedure.
User response: Make more system resources available
procedure.
by closing other applications, then try the action again.
User response: Check that the license file permissions
are correct.
ANU2523E The Management Class does not match
Explanation: The management class for the query
ANU2515E Invalid data format in license file: license
object could not be found.
file
Explanation: The license file data format is invalid.
procedure.
procedure.
Data Protection for Oracle. ANU2525E Input date does not match expected date
format or range.
Explanation: The input date does not match the
ANU2516E Bad checksum of license file: license file
expected date format or range.
Explanation: The license file has a bad checksum.
procedure.
procedure.
User response: Check that the format and length of
the date entry matches TDP_DATE_FORMAT type and
Data Protection for Oracle.


the range of the date values are valid.Valid days are: User response: Check the TSM Server activity log.
1-31Valid months are: 1-12Valid years are:1990-2089
ANU2536I File /fs/hl/ll = number bytes recieved
ANU2529E To Date cannot occur before From Date Explanation: This is the total bytes received from the
Explanation: The specified To Date occurs before From server for that backup file name.
Date. System action: The system returns to the calling
System action: The system returns this error. procedure.
User response: Enter a valid To Date that occurs after User response: Check the TSM Server activity log.
the From Date.
ANU2537E Error found while parsing options in
ANU2530E Screen size is too small to accurately Data Protection for Oracle options file.
display the PICK window. Explanation: There was an error found while parsing
Explanation: You cannot use the PICK option on a the Data Protection for Oracle options file.
workstation that has a screen smaller than 20 characters System action: The system returns to the calling
across and 10 lines down. procedure.
System action: The operation was not completed. User response: Check that the options and the options
User response: Retry the operation using a file are valid.
workstation that has a screen with the minimum size.
ANU2538E Error found while initializing tracing for
ANU2531E Could not create a temporary file name Data Protection for Oracle.
for Data Protection for Oracle utility Explanation: Error found while initializing the Data
Explanation: A temporary file name could not be Protection for Oracle trace facility.
created by the Operating System call to tempnam(). System action: The system returns to the calling
System action: The system returns to the calling procedure.
procedure. User response: Contact your system administrator.
User response: Check with the Operating System
Vendor for specific reasons why the function call to
ANU2539E Function Name: Error - string pointer is
tempnam() could fail. Take the necessary corrective
NULL.
action and try operation again.
Explanation: A NULL pointer was passed to Data
Protection for Oracle.
ANU2532E Unknown Error - View the Data System action: The system returns to the calling
Protection for Oracle error log procedure.
Explanation: There was an unknown error. View the User response: Contact your system administrator.
tdpoerror.log.
System action: None
ANU2571E Could not load the library: library Data
User response: None
Protection for Oracle
Explanation: Library cannot be loaded.
ANU2533E SQLPLUS error System action: The system returns to the calling
Explanation: The utility could not find SQLPLUS or procedure.
there was a scripting error. User response: Check that the library exists.
procedure.
ANU2575E An error was detected while attempting
User response: Check that SQLPLUS is installed and
to open the file ’filename’ for writing.
located in your search path. Verify the password.
Explanation: The Data Protection for Oracle utility
failed to open the file named in the error message.
ANU2534E Option file error. System action: The system returns to the calling
Explanation: The option or option file name is invalid. procedure.
System action: The system returns to the calling User response: Check to ensure that the directory
procedure. exists or that the directory has write permission, and
User response: Check the tdpoerror.log file for an that the disk is not full. Take the necessary corrective
explanation of the error. action and try operation again.

ANU2535I File /fs/hl/ll = number bytes sent ANU2576E An error was detected while attempting
Explanation: This is the total bytes sent to the server to open the file ’filename’ for reading.
for that file name Explanation: The Data Protection for Oracle utility
System action: The system returns to the calling failed to open the temporary file named in the error
procedure. message.


ANU2615E Options file ’filename’ not found.
procedure.
Explanation: The option file name specified could not
User response: Check to ensure that the file named in
be located.
the error exists in the path specified and that the file
named has read permissions. Take the necessary
procedure.
corrective action and try operation again.
User response: Ensure that an option file exists in the
default path or that the user specified option file is
ANU2600E There is no Registry entry for the TSM valid.
API.
Explanation: The Windows Registry entry was not
ANU2616E Empty parameter specified for option
found.
’option’ in options file ’filename’.
Explanation: The option specified must have a
procedure.
parameter supplied.
User response: Check that the TSM API is installed
correctly.
procedure.
User response: Ensure that a valid parameter for the
ANU2601E There is no Registry entry for the Data given option is entered and valid.
Protection for Oracle install path.
Explanation: The Registry Entry for the Data
ANU2620E Attempting to create or modify Data
Protection for Oracle install path was not found.
Protection for Oracle prompted
password as non-root user.
procedure.
Explanation: According to the settings in your Data
User response: Check that Data Protection for Oracle
Protection for Oracle options file you are attempting to
was installed correctly.
authenticate using passwordaccess=prompt as a
non-root user. Root access is needed to modify the Data
ANU2602E The object Filespace NameHigh Level Protection for Oracle password file.
NameLow Level Name was not found on System action: The system returns to the calling
the TSM Server procedure.
Explanation: The object name was not found on the User response: To create or modify the Data
TSM Server. Protection for Oracle password file, switch to the root
System action: The system returns to the calling user and re-run the Data Protection for Oracle
procedure. password configuration utility.
User response: Check that the object name is correct
and that it exists on the TSM Server.
ANU2621E Attempting to create or modify Data
Protection for Oracle generated
ANU2603E The option Option Name in file Filename password as root user.
is invalid. Explanation: According to the settings in your Data
Explanation: An incorrect option was passed into the Protection for Oracle options file the TDPO_NODE is
Data Protection for Oracle options file. not defined which indicates that you are attempting to
System action: The system returns to the calling authenticate using passwordaccess=generate. As a root
procedure. user this is not allowed.
User response: Verify that your options are correct in System action: The system returns to the calling
the Data Protection for Oracle options file. procedure.
User response: If you intend to use
passwordaccess=prompt method of authentication
ANU2614E Invalid sequence of function calls to please modify the Data Protection for Oracle and set
Data Protection for Oracle TDPO_NODE to a valid registered TSM node and
Explanation: Data Protection for Oracle received a re-run the password configuration utility as root user.
function call from Oracle that is out of sequence.
System action: Data Protection for Oracle returns to
the calling procedure. ANU2622E One or more option parameters contain
User response: Contact Oracle or Data Protection for invalid values.
Oracle support. Explanation: An invalid parameter value was
specified at the command-line.
procedure.
User response: Check the User’s Guide for correct
usage of option parameters and the possible values for


this command. Retry the command with valid option
values.

ANU2623I No user input detected.
Explanation: Valid user input is required to fullfill the
parameter request.
System action: The operation gives the user 3
attempts before returning to the calling procedure.
User response: Check the User’s Guide for correct
usage of the command and the possible values for this
command. Retry the command with valid values.


Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Information Enabling Requests


Dept. M13
5600 Cottle Road
San Jose CA 95193-0001
U.S.A.

Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.


Trademarks
IBM, the IBM logo and the following terms are trademarks of the International
Business Machines Corporation in the United States, other countries, or both:

AIX OpenEdition
AS/400 OS/2
DB2 OS/390
DFS OS/400
DFSMS/MVS Passport Advantage
DFSMShsm pSeries
DFSMSrmm RACF
DPI Rational
Enterprise Storage Server Redbooks
ESCON RS/6000
eServer S/390
FICON SANergy
FlashCopy SecureWay
HACMP StorageSmart
Informix SystemView
iSeries Tivoli
Lotus Tivoli Enterprise Console
Lotus 1-2-3 Tivoli Management Enterprise
Lotus Approach TotalStorage
Lotus Domino TME
Lotus Notes VTAM
Magstar WebSphere
MVS z/OS
NetView zSeries

Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation
in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.

Other company, product or service names may be trademarks or service marks of
others.

Notices 63

Index
A Data Protection for Oracle (continued)
overview 2
I
accessibility x prior versions 9 inclexcl
archive copy group 18 recommendations 29 and Tivoli Storage Manager
autostart 39 Recovery Manager (RMAN) 2 policy 18
reporting problems 41 include
supported Oracle versions 2 and duplex copy 23
B Tivoli Storage Manager policy and Tivoli Storage Manager
policy 18
backdelete requirements 17
version migration 3 description 16
and backup removal 24
Windows Itanium 2 information centers, searching for
and Data Protection for Oracle
supported Oracle versions 8 problem resolution 42
node 14
Windows Itanium 2 environment 8 installation
and Tivoli Storage Manager
Windows x86 instructions
policy 17
supported Oracle versions 6 node name registration 13
backup copy group values 17
Windows x86 environment 6 installing Data Protection for Oracle
backups
Windows x86_64 Windows Itanium 2 environment 8
automating 35
supported Oracle versions 7 Windows x86 environment 6
removing 24
Windows x86_64 environment 7 Windows x86_64 environment 7
bkdb.log 21
dsierror.log Internet
bkdb.scr
problem determination 41 searching for problem resolution 42
and the Tivoli Storage Manager
scheduler 36 dsm.opt
books description 14
see publications ix problem determination 41 K
recommended options 15 knowledge bases, searching for problem
required options 15 resolution 42
C dsmi_log 12
dsmi_orc_config 12
command line syntax
characteristics 25
dsmsched.log 39
duplex copy
L
commands considerations 23 LAN-free data transfer
Oracle overview 22 description 3
change 24 options 16
tdpoconf password 26
tdpoconf showenvironment 27
tdposync E M
syncdb 30 education
see Tivoli technical training x management class
Tivoli Storage Manager server
enablelanfree 16 for automatic expiration 17
query actlog 42
examples using 24
query association 36
duplex copy 22 manuals
query node 23, 42
include/exclude 18 see publications ix
query schedule 36
invoking RMAN 21 maxnummp 23
commmethod
removing backups 24 migration considerations 3
description 15
communication methods RMAN scripts 22
Windows Itanium 2 8 tdpoconf password command 26
Windows x86 6 tdpoconf showenvironment N
Windows x86_64 7 command 27 node name
compression 15 tdposync syncdb command 31 registration 13
conventions pick window 32 nodename 15
typeface xi Tivoli Storage Manager scheduler 35 numcatalogs
customer support expiration of objects 17 and tdposync syncdb command 30
See Software Support

F O
D fixes, obtaining 43 online publications
Data Protection for Oracle accessing ix
and Oracle databases 21 options 12
configuring 14 Oracle
generating trace file 42 Windows Itanium 2
installing 5, 9 supported versions 8


Oracle (continued)
Windows x86
TDPO_OPTFILE
and tdpoconf password command 26
V
supported versions 6 and tdpoconf showenvironment verdeleted
Windows x86_64 command 27 and backup removal 24
supported versions 7 and tdposync syncdb command 30 and Tivoli Storage Manager
orcsched.cmd file 38 example 11 policy 17
ordering publications ix tdpo_time_fmt 12
outfile tdpo_trace_file 42
and tdpoconf showenvironment tdpo.opt W
command 27 and version migration 3 Windows Itanium 2
description 11 communication methods 8
problem determination 41 disk space 8
P tdpoconf
and password initialization 19
environment 8
passwordaccess 15 hardware 8
and tdpo.opt 11 memory 8
pick window 32
description 26 operating system 8
policy domain 17
for problem determination 41 software requirements 8
problem determination
password command 26 Windows x86
describing problems 45
example 26 communication methods 6
determining business impact 45
syntax diagram 26 disk space 6
guidelines 41
TDPO_OPTFILE 26 environment 6
submitting problems 46
showenvironment command 27 hardware 6
publications
example 27 memory 6
accessing online ix
outfile 27 operating system 6
ordering ix
syntax diagram 27 software requirements 6
TDPO_OPTFILE 27 Windows x86_64
tdpoerror.log communication methods 7
R how to specify 12 disk space 7
readmedporc_enu.htm 5 problem determination 41 environment 7
retonly tdposync hardware 7
and backup removal 24 and tdpo.opt 11 memory 7
and Tivoli Storage Manager considerations 29 operating system 7
policy 17 description 28 software requirements 7
RMAN syncdb command 30
description 2 numcatalogs 30
invoking 21 pick window 32
scripts 21 syntax diagram 30
TDPO_OPTFILE 30
Tivoli software information center ix
S Tivoli Storage Manager
functions 1
schedlogname 39
management class 18
scripts 21
policy requirements 17
set duplex 23
scheduler 35
software requirements
services 1
Windows Itanium 2 8
Windows Itanium 2
Windows x86 6
supported API 8
Windows x86_64 7
Windows x86
Software Support
supported API 6
contacting 44
Windows x86_64
describing problems 45
supported API 7
determining business impact 45
Tivoli Storage Manager API trace file 41
receiving weekly updates 43
Tivoli Storage Manager server
submitting problems 46
Windows Itanium 2
supported version 8
Windows x86
T supported version 6
tcpclientaddress 39 Windows x86_64
tcpclientport 39 supported version 7
tcpserveraddress 15 Tivoli technical training x
tdpo_date_fmt 12 trace file, generating 42
tdpo_fs 12 tracefile 42
tdpo_language 13 training, Tivoli technical x
tdpo_mgmt_class_2 13 typeface conventions xi
tdpo_mgmt_class_3 13
tdpo_mgmt_class_4 13
tdpo_num_fmt 12


Program Number: 5608-APD

Printed in USA

SC32-9065-02

Ibm tivoli storage manager for databases data protection for oracle for windows installation and user's guide version 5.4.1

More Related Content

What's hot (18)

Similar to Ibm tivoli storage manager for databases data protection for oracle for windows installation and user's guide version 5.4.1 (20)

More from Banking at Ho Chi Minh city (20)

Recently uploaded (20)

Ibm tivoli storage manager for databases data protection for oracle for windows installation and user's guide version 5.4.1