IBM Tivoli Storage Manager For Databases Data Protection For Oracle For UNIX and Linux Installation and User's Guide Version 5.4.1

Tivoli Storage Manager
for Databases
Data Protection for Oracle for UNIX and Linux
Installation and Users Guide
Version 5 Release 4
SC32-9064-03

for Databases
Data Protection for Oracle for UNIX and Linux
Installation and Users Guide
Version 5 Release 4
SC32-9064-03

Note
Before using this information and the product it supports, read the general information under Notices on page 91.
This edition applies to Version 5, Release 4, Modification 1.0, of IBM Tivoli Storage Manager for Databases Data
Protection for Oracle for AIX, Linux, HP-UX, or Solaris (product number 5608-APD) and to all subsequent releases
until otherwise indicated in new editions.
Copyright International Business Machines Corporation 1997, 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
Technical changes for Version 5.4.1 . . . . . . . v
About this guide . . . . . . . . . . vii
Who should read this guide . . . . . . . . . vii
Publications . . . . . . . . . . . . . . vii
IBM Tivoli Storage Manager library . . . . . vii
Accessing terminology online . . . . . . . ix
Accessing publications online . . . . . . . ix
Ordering publications . . . . . . . . . . ix
Tivoli Technical Training . . . . . . . . . ix
Accessibility . . . . . . . . . . . . . . x
Support information . . . . . . . . . . . . x
IBM Tivoli Storage Manager Web site . . . . . x
IBM Tivoli Storage Manager for Databases Web
site . . . . . . . . . . . . . . . . x
Conventions used in this book . . . . . . . . x
Typeface conventions . . . . . . . . . . x
Reading syntax diagrams . . . . . . . . . . xi
Chapter 1. Introducing Data Protection
for Oracle . . . . . . . . . . . . . . 1
Understanding Tivoli Storage Manager . . . . . 1
Overview of Data Protection for Oracle . . . . . 2
RMAN and Data Protection for Oracle . . . . . 2
LAN-free data transfer . . . . . . . . . . 3
Migration and coexistence . . . . . . . . . 3
Chapter 2. Installing Data Protection for
Oracle . . . . . . . . . . . . . . . 5
AIX . . . . . . . . . . . . . . . . . 6
AIX 5L environment (64-bit) . . . . . . . . 6
HP-UX . . . . . . . . . . . . . . . . 9
HP-UX PA-RISC environment (64-bit) . . . . . 9
HP-UX Itanium 2 environment (64-bit) . . . . 12
Linux . . . . . . . . . . . . . . . . 15
Linux x86 environment (32-bit) . . . . . . . 15
Linux x86_64 environment . . . . . . . . 17
Linux on POWER environment . . . . . . . 20
Linux zSeries environment (64-bit) . . . . . . 23
Solaris . . . . . . . . . . . . . . . . 26
Solaris SPARC environment (32-bit) . . . . . 26
Solaris SPARC environment (64-bit) . . . . . 29
Solaris x86 environment (32-bit) . . . . . . 32
Solaris x86_64 environment . . . . . . . . 35
Chapter 3. Configuring Data Protection
for Oracle . . . . . . . . . . . . . 39
1. Define Data Protection for Oracle options in the
tdpo.opt file . . . . . . . . . . . . . . 39
Available options . . . . . . . . . . . 40
2. Register the Data Protection for Oracle node to a
Tivoli Storage Manager server . . . . . . . . 43
3. Define Tivoli Storage Manager options in the
dsm.opt and dsm.sys files . . . . . . . . . 44
Required options . . . . . . . . . . . 44
Other options to consider . . . . . . . . . 45
4. Define Tivoli Storage Manager policy
requirements . . . . . . . . . . . . . . 47
5. Initialize the password with a Tivoli Storage
Manager server . . . . . . . . . . . . . 49
Chapter 4. Using RMAN and Data
Protection for Oracle. . . . . . . . . 51
Invoking RMAN . . . . . . . . . . . . . 51
Scripts . . . . . . . . . . . . . . . . 51
Example . . . . . . . . . . . . . . 52
Using the Duplex Copy function . . . . . . . 52
Removing old backups . . . . . . . . . . 54
Example . . . . . . . . . . . . . . 54
Management class options affecting object
removal . . . . . . . . . . . . . . 54
Chapter 5. Using the utilities . . . . . 55
Command line syntax and characteristics . . . . 55
TDPOCONF . . . . . . . . . . . . . . 56
Password command . . . . . . . . . . 56
Showenvironment command . . . . . . . 57
TDPOSYNC . . . . . . . . . . . . . . 58
Considerations . . . . . . . . . . . . 59
Syncdb Command . . . . . . . . . . . 60
Appendix A. Quick configuration guide 63
Appendix B. Using the Tivoli Storage
Manager scheduler . . . . . . . . . 65
Setting up a schedule . . . . . . . . . . . 65
Part I: On the Tivoli Storage Manager server . . 66
Part II: On the client machine (NodeA1) . . . . 66
Appendix C. Support information . . . 69
What to do when you encounter a problem . . . 69
Searching knowledge bases . . . . . . . . . 71
Searching the information center . . . . . . 71
Searching the Internet . . . . . . . . . . 71
Obtaining fixes . . . . . . . . . . . . . 71
Receiving weekly support updates . . . . . . 72
Contacting IBM Software Support . . . . . . . 72
Determining the business impact . . . . . . 73
Describing problems and gathering information 74
Submitting problems . . . . . . . . . . 74
Appendix D. Accessibility . . . . . . 77
Navigating the interface using the keyboard . . . 77
Magnifying what is displayed on the screen . . . 77

Copyright IBM Corp. 1997, 2007 iii
||
Appendix E. Messages . . . . . . . . 79
Notices . . . . . . . . . . . . . . 91
Trademarks . . . . . . . . . . . . . . 93
Index . . . . . . . . . . . . . . . 95

iv IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users Guide
Summary of changes
This section summarizes changes made to the Data Protection for Oracle product
and this publication. Technical changes to the text 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:
Tivoli Storage Manager API password management
Password expiration can now be managed by Data Protection for Oracle
through the Tivoli Storage Manager API. This allows a new password to be
automatically generated by the Tivoli Storage Manager server, thus
preventing a backup failure due to an expired password.
See the description of the passwordaccess option in the Required options
on page 44 section for detailed information.
SuSE Linux
Enterprise Server 10
Support for Data Protection for Oracle on SuSE Linux Enterprise Server 10
is provided in this release.
See Linux x86 environment (32-bit) on page 15 and Linux x86_64
environment on page 17 for detailed information.
Changes since the SC32-9064-02 version are marked with a vertical bar (|) in the
left margin.

Copyright IBM Corp. 1997, 2007 v
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vi IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users 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.
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 AIX

v HP-UX
v Linux
v Solaris Operating Environment (hereinafter referred to as Solaris)
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
Users 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 Users Guide
Provides information for an end-user to install, configure, and use the Tivoli
Storage Manager client on UNIX and Linux operating systems.
v IBM Tivoli Storage Manager for Windows Administrators Guide

Copyright IBM Corp. 1997, 2007 vii
Provides concepts and procedures for configuring and customizing the Tivoli
Storage Manager server on Windows operating systems.
v IBM Tivoli Storage Manager for Windows Administrators 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 Administrators Guide
Storage Manager server on AIX operating systems.
v IBM Tivoli Storage Manager for AIX Administrators Reference
utilities for Tivoli Storage Manager server on AIX operating systems.
v IBM Tivoli Storage Manager for Sun Solaris Administrators Guide
Storage Manager server on Sun Solaris operating systems.
v IBM Tivoli Storage Manager for Sun Solaris Administrators 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 Users 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 Users Guide
server.
v IBM Tivoli Storage Manager for SAN for Linux Storage Agent Users Guide
server.
v IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent Users Guide
server.
v IBM Tivoli Storage Manager for SAN for Windows Storage Agent Users Guide
server.

viii IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users Guide
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.
Tivoli Technical Training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education

About this guide ix
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
77.
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 69.
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.
Typeface conventions
This guide uses the following typeface conventions:
Bold
v Commands, keywords, authorization roles, or other information that you
must use.

x IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users Guide
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 /usr/tivoli/tsm/client/ba/bin
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).

Syntax Diagram Description Example
Abbreviations:
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.
KEYWOrd

About this guide xi
Symbols:
Enter these symbols exactly as they appear in
the syntax diagram.
* Asterisk
{ } Braces
: Colon
, Comma
= Equal Sign
- Hyphen
() Parentheses
. Period
Space
Variables:
Italicized lowercase items (var_name) denote
variables.
In this example, you can specify a var_name
when you enter the KEYWORD command.
KEYWOrd var_name
Repetition:
An arrow returning to the left means you can
repeat the item.
A character or space within the arrow means
you must separate repeated items with that
character or space.
A footnote by the arrow references the
number of times you can repeat the item.

repeat

,
repeat

(1)

repeat

Notes:
1 Specify repeat as many as 5 times.
Required Choices:
When two or more items are in a stack and
one of them is on the line, you must specify
one item.
In this example, you must choose A, B, or C.
A
B

C

Optional Choice:
When an item is below the line, that item is
optional. In the first example, you can choose
A or nothing at all.
When two or more items are in a stack below
the line, all of them are optional. In the
second example, you can choose A, B, C, or
nothing at all.
A

B

C

xii IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users Guide
Defaults:
Defaults are above the line. The default is
selected unless you override it. You can
override the default by including an option
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.
A
B

C

Repeatable Choices:
A stack of items followed by an arrow
returning to the left means you can select
more than one item or, in some cases, repeat
a single item.
In this example, you can choose any
combination of A, B, or C.

A

B

C

Syntax Fragments:
Some diagrams, because of their length, must
fragment the syntax. The fragment name
appears between vertical bars in the diagram.
The expanded fragment appears between
vertical bars in the diagram after a heading
with the same fragment name.
The fragment name
The fragment name:
A
B

C

About this guide xiii
xiv IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users 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. 1997, 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 UNIX and Linux Installation and Users 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 39 or Scripts on page 51.
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. Note that Tivoli Storage
Manager API Version 5.3.4 is required for a Solaris SPARC 32-bit environment.

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. Note that Tivoli
Storage Manager API Version 5.3.4 is required for a Solaris SPARC 32-bit
environment. 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 root user must install the Tivoli Storage Manager API before
installing Data Protection for Oracle on the workstation where the target database
resides.
After Data Protection for Oracle is installed, see Chapter 3, Configuring Data
Protection for Oracle, on page 39 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 63 for
instructions.

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

|
|
|
|
|
|
AIX
AIX 5L environment (64-bit)
This section contains operating system, hardware, software, and communication
requirements for installing Data Protection for Oracle in an AIX 5L
environment.
Operating system requirements
One of the following AIX 5L operating systems:
v AIX 5.2 (64-bit)
v AIX 5.3 (64-bit)
Hardware requirements
v Any RS/6000
or pSeries

workstation
v Disk space: 8 MB
v Memory: 64 MB (128 MB or more recommended)
Software requirements
v Tivoli Storage Manager server Version 5.3.x (or later)
v Tivoli Storage Manager API Version 5.4.0 (or later)
v One of the following levels of Oracle Server:
Oracle9i Version 9.2 (64-bit)
Oracle 10g Release 1 (64-bit)
Communication methods
v TCP/IP

|
Installing Data Protection for Oracle on AIX 5L 64-bit
All installables on the CD reside under the /cdrom/usr/sys/inst.images directory.
Table 1. AIX 5L 64-bit Default Installation Directories
AIX Default Installation Directories
Data Protection for Oracle 64-bit /usr/tivoli/tsm/client/oracle/bin64
Data Protection for Oracle
Utilities
/usr/tivoli/tsm/client/oracle/bin64
Tivoli Storage Manager API
64-bit
/usr/tivoli/tsm/client/api/bin64

Table 2. Data Protection for Oracle AIX 5L 64-bit, Utilities, Languages, and Tivoli Storage
Manager API Package Names
Package Package Name
Data Protection for Oracle 64-bit tivoli.tsm.client.oracle.aix.64bit
Utilities
tivoli.tsm.client.oracle.tools.aix.64bit
Electronic License Agreement tivoli.tsm.loc.client.oracle.aix.64bit.ela
Languages
tivoli.tsm.client.oracle.msg.aix.64bit.xx_XX
64-bit
tivoli.tsm.client.api.aix.64bit
Languages
tivoli.tsm.msg.xx_XX.client.api.64bit

Follow these instructions to install Data Protection for Oracle. This example
assumes that your CD drive is /dev/cd0.
1. Insert the CD containing the client package into the CD drive.
2. Log in as the root user.
3. Enter smitty install at the command prompt.
4. Select Install and Update Software. Press Enter.
5. Select Install and Update from ALL Available Software. Press Enter.
6. Enter /dev/cd0 in the Entry Field for INPUT device / directory for software.
Press Enter.
7. Highlight the SOFTWARE to install option. Press F4 to list available software.
8. Select the installable packages by performing the following:
a. Highlight the Data Protection for Oracle package
(tivoli.tsm.client.oracle.aix.64bit) and press F7.
b. Highlight the Data Protection for Oracle utilities package
(tivoli.tsm.client.oracle.tools.aix.64bit) and press F7.
c. Highlight the Tivoli Storage Manager API package
(tivoli.tsm.client.api.aix.64bit) and press F7.
d. If you want to install Data Protection for Oracle in a language other than
English, highlight the desired language package
(tivoli.tsm.client.oracle.msg.aix.64bit.xx_XX) and press F7. Make sure
the Tivoli Storage Manager API language package for the desired language
(tivoli.tsm.msg.xx_XX.client.api.64bit) is also installed.

Chapter 2. Installing Data Protection for Oracle 7
e. Highlight the Electronic License Agreement
(tivoli.tsm.loc.client.oracle.aix.64bit.ela) and press F7.
1) Make sure you set ACCEPT new license agreements? to Yes. (The
default is No). You can also specify the -Y option with the installp
command.
2) Set Preview new license agreements? to No (the default value) for the
installation to proceed.
3) If Preview new license agreements? is set to Yes, the installation will
enter preview mode but Data Protection for Oracle does not install.
Preview new license agreements? must be set to No for Data
Protection for Oracle to install.
After all five packages are selected, press Enter.
9. When the Install and Update from LATEST Available Software window
displays, press Enter.
10. A window displays and prompts you with this message:
ARE YOU SURE?

Press Enter to continue the installation procedure.
11. After successfully installing Data Protection for Oracle, press F10 to exit the
smitty install environment. You can view the Summary for more information
regarding the installation.
12. Link the Oracle target database instance with Data Protection for Oracle by
performing the following steps:
a. Set the Oracle LD_LIBRARY_PATH option to specify $ORACLE_HOME/lib as
the first entry:
LD_LIBRARY_PATH=$ORACLE_HOME/lib

b. Shut down all Oracle instances that use $ORACLE_HOME.
c. Go to the $ORACLE_HOME/lib directory.
d. Symbolically link the library file to libobk.a:
$ ln -s /usr/lib/libobk64.a $ORACLE_HOME/lib/libobk.a

e. Start the Oracle instances.

HP-UX
HP-UX PA-RISC environment (64-bit)
requirements for installing Data Protection for Oracle in an HP-UX PA-RISC 64-bit
environment.
One of the following levels of HP-UX 64-bit operating system:
v HP-UX 11i v2 (64-bit)
v Any HP 9000 Series 700 or 800 workstation
v Disk space: 8 MB
v Memory: 96 MB
v TCP/IP

|
|
|
Installing Data Protection for Oracle on HP-UX PA-RISC 64-bit
All installable files reside under the /cdrom/oracle/hpux11/ directory.
Table 3. HP-UX PA-RISC 64-bit Default Installation Directories
HP-UX Default Installation Directories
Data Protection for Oracle 64-bit /opt/tivoli/tsm/client/oracle/bin64
Utilities
/opt/tivoli/tsm/client/oracle/bin64
Messages
Tivoli Storage Manager API /opt/tivoli/tsm/client/api/bin64

Table 4. Data Protection for Oracle 64-bit and Tivoli Storage Manager installable files and
packages
Component Installable file or package
Data Protection for Oracle 64-bit base code,
license, utilities
TDPOracle64.bin
Data Protection for Oracle Languages TDPOracle.msg.xx_XX.bin
Tivoli Storage Manager API TIVsmCapi64
Tivoli Storage Manager API Languages TIVsmC.msg.xx_XX

To install:
1. Log in as the root user:
# su
Password:

Enter your password.
2. Create a directory for mounting the CD. Set the appropriate permission to the
directory:
# mkdir /cdrom
# chmod 755 /cdrom

3. Insert the CD into the drive and mount the CD:
# mount -r -F hsfs <device_name> /cdrom

Enter your device_name for the CD in this command. An example of
device_name is /dev/dsk/c1t2d0.
4. Issue this command to install the Tivoli Storage Manager API:
$ swinstall -v -s /cdrom/oracle/hpux11/TIVsmCapi64

5. Enter the name of the installable file (TDPOracle64.bin) on the command line
and press Enter to install the Data Protection for Oracle product, utilities, and
license:
$ TDPOracle64.bin

6. If you want to install Data Protection for Oracle in a language other than
English, enter the name of the installable file for the desired language
(TDPOracle.msg.xx_XX.bin) on the command line and press Enter:
$ TDPOracle.msg.xx_XX.bin

Make sure the Tivoli Storage Manager API language package for the desired
language (TIVsmC.msg.xx_XX) is also installed.
the first entry:

d. Symbolically link the library file to libobk.sl:
$ ln -s /usr/lib/pa20_64/libobk.sl $ORACLE_HOME/lib/libobk.sl


|
HP-UX Itanium 2 environment (64-bit)
requirements for installing Data Protection for Oracle in an HP-UX Itanium

2
64-bit environment.
The following level of HP-UX operating system:
v HP-UX 11i v2 (11.23) 64-bit
v An HP Integrity server with an Itanium 2 processor
v Disk space: 8 MB
v Memory: 96 MB
v TCP/IP

|
Installing Data Protection for Oracle on HP-UX Itanium 2 64-bit
All installable files reside under the /cdrom/oracle/hpuxia/ directory.
Table 5. HP-UX Itanium 2 64-bit Default Installation Directories
HP-UX Default Installation Directories
Utilities
Messages

packages
license, utilities
TDPOracle64.bin
Data Protection for Oracle Languages TDPOracle64.msg.xx_XX.bin
Tivoli Storage Manager API TIVsmCapi64
Tivoli Storage Manager API Languages TIVsmC.msg.xx_XX

To install:
1. Log in as the root user:
# su
Password:

Enter your password.
2. Create a directory for mounting the CD. Set the appropriate permission to the
directory:
# mkdir /cdrom
# chmod 755 /cdrom

3. Insert the CD into the drive and mount the CD:
# mount -r -F hsfs <device_name> /cdrom

Enter your device_name for the CD in this command. An example of
device_name is /dev/dsk/c1t2d0.
$ swinstall -v -s /cdrom/oracle/hpuxia/TIVsmCapi64

5. Enter the name of the installable file (TDPOracle64.bin) on the command line
and press Enter to install the Data Protection for Oracle product, utilities, and
license:
$ TDPOracle64.bin

English, enter the name of the Data Protection for Oracle installable file for the
desired language (TDPOracle.msg.xx_XX.bin) on the command line and press
Enter:

language (TIVsmC.msg.xx_XX) is also installed.
the first entry:

d. Symbolically link the library file to libobk.so:
$ ln -s /usr/lib/hpux64/libobk.so $ORACLE_HOME/lib/libobk.so


|
|
|
|
Linux
Linux x86 environment (32-bit)
requirements for installing Data Protection for Oracle in a Linux on Intel
x86
32-bit environment.
One of the following levels of Linux 32-bit operating system:
v Red Hat Enterprise Linux 4 (32-bit)
v SuSE Linux Enterprise Server 9 (32-bit)
v Asianux 2.0 (32-bit)
v Any Intel x86 (or compatible) 32-bit workstation
v Disk space: 8 MB
Table 7. Supported Oracle Server and operating system combinations for Linux x86 32-bit
Oracle 9i Version 9.2
(32-bit)
Oracle 10g Release 1
(32-bit)
(32-bit)
Asianux 2.0 (32-bit) U U U
SuSE Linux Enterprise
Server 9 (32-bit)
U U U
Server 10 (32-bit)
U
Linux Red Flag Advanced
Server 4.1 (32-bit)
U U

v TCP/IP

|
|
|
|
|
|
||||
|
|
|||
Installing Data Protection for Oracle on Linux x86
All installable files reside under the /cdrom/oracle/linux86/ directory.
Table 8. Linux x86 Default Installation Directories
Linux Default Installation Directories
Data Protection for Oracle 32-bit /opt/tivoli/tsm/client/oracle/bin
Utilities
/opt/tivoli/tsm/client/oracle/bin
Messages
32-bit
/opt/tivoli/tsm/client/api/bin

Table 9. Data Protection for Oracle Linux x86 and Tivoli Storage Manager installable files
and packages
license, and utilities
TDP-Oracle.i386.bin
Data Protection for Oracle Languages TDPOracle.msg.xx_XX.bin
Tivoli Storage Manager API 32-bit TIVsm-API.i386.rpm
Tivoli Storage Manager API Languages TIVsm-.msg.xx_XX.i386.rpm

This installation procedure is designed to install directly from the Data Protection
for Oracle CD:
2. Mount the Data Protection for Oracle CD to /cdrom:
$ mount <device name> /cdrom

3. Change to the /cdrom/oracle/linux86 directory where the installation packages
reside on the CD:
$ cd /cdrom/oracle/linux86

4. Issue the following command to install the Tivoli Storage Manager API:
$ rpm -i TIVsm-API.i386.rpm

5. Enter the name of the installable file (TDP-Oracle.i386.bin) on the command
line and press Enter to install Data Protection for Oracle:
$ TDP-Oracle.i386.bin

Enter:

language (TIVsm-.msg.xx_XX.i386.rpm) is also installed. Note that the libobk.so
library file is located automatically based on the link that the installation
program places in the /usr/lib directory.

Linux x86_64 environment
requirements for installing Data Protection for Oracle in a Linux x86_64
environment.
One of the following levels of Linux operating system:
v Red Hat Enterprise Linux 4 (64-bit)
v Any Intel EM64T or Opteron AMD64 (or compatible) processor
v Disk space: 8 MB
Table 10. Supported Oracle Server and operating system combinations for Linux x86_64
Oracle 9i Version 9.2
(64-bit)
(64-bit)
(64-bit)
Asianux 2.0 (64-bit) U U U
Server 9 (64-bit)
U U U
Server 10 (64-bit)
U

v TCP/IP

|
|
|
|
|
|
|
|||
Installing Data Protection for Oracle on Linux x86_64
All installable files reside under the /cdrom/oracle/linux86_64 directory.
Table 11. Linux x86_64 Default Installation Directories
Linux x86_64
Utilities
Messages

Table 12. Data Protection for Oracle Linux x86_64 and Tivoli Storage Manager installable
files and packages
Data Protection for Oracle Linux x86_64 base
code, license, utilities
TDP-Oracle.x86_64.bin
Data Protection for Oracle Languages TDPOracle.msg.xx_XX.x86_64.bin
Tivoli Storage Manager API Linux x86_64 TIVsm-API64.i386.rpm
Tivoli Storage Manager API Languages TIVsm-msg.xx_XX.i386.rpm

for Oracle CD:
1. Log in as the root user on the machine with the accessible CD device.

3. Mount /cdrom to the /cdrom directory on the Linux zSeries
machine. The
/cdrom directory must already exist on the Linux zSeries machine:
$ mount -o soft hostname:/cdrom /cdrom

Note: hostname is the machine with the accessible CD device identified in Step
1.
4. Change to the /cdrom/oracle/linux86_64 directory where the installation
packages reside on the CD:
$ cd /cdrom/oracle/linux86_64

$ rpm -i TIVsm-API64.x86_64.rpm

6. Enter the name of the installable file (TDP-Oracle.x86_64.bin) on the command
$ TDP-Oracle.x86_64.bin

|
|
|
|
||
||
Enter:
$ TDPOracle.msg.xx_XX.x86_64.bin

language (TIVsm-msg.xx_XX.x86_64.rpm) is also installed.
Note: The libobk.so library file is located automatically based on the link that the
installation program places in the /usr/lib64 directory.

Linux on POWER environment
requirements for installing Data Protection for Oracle in a Linux on POWER
environment.
v Red Hat Enterprise Linux 4
v SuSE Linux Enterprise Server 9
v Any iSeries
, pSeries, or Power 5 (or compatible) processor

v Disk space: 8 MB
v Memory: 96 MB
v Oracle 10g Release 2 (64-bit)
v TCP/IP

|
Installing Data Protection for Oracle on Linux on POWER
All installable files reside under the /cdrom/oracle/linuxppc64 directory.
Table 13. Linux on POWER Default Installation Directories
Linux on POWER
Utilities
Messages

Table 14. Data Protection for Oracle Linux on POWER and Tivoli Storage Manager
installable files and packages
Data Protection for Oracle Linux on POWER
base code, license, utilities
TDP-Oracle64.ppc64.bin
Data Protection for Oracle Languages TDP-Oracle64.msg.xx_XX.ppc64.bin
Tivoli Storage Manager API Linux on
POWER
TIVsm-API.ppc64.rpm
Tivoli Storage Manager Languages TIVsm-msg.xx_XX.ppc64.rpm

for Oracle CD:

3. Mount /cdrom to the /cdrom directory on the Linux machine. The /cdrom
directory must already exist on the Linux machine:

1.
4. Change to the /cdrom/oracle/linuxppc64 directory where the installation
$ cd /cdrom/oracle/linuxppc64

$ rpm -i TIVsm-API.ppc64.rpm

6. Enter the name of the installable file (TDP-Oracle64.ppc64.bin) on the command
$ TDP-Oracle64.ppc64.bin

|
|
|
|
|
|
|
|
|
|
||
desired language (TDP-Oracle64.msg.xx_XX.ppc64.bin) on the command line
and press Enter:
$ TDP-Oracle64.msg.xx_XX.ppc64.bin

language (TIVsm-msg.xx_XX.ppc64.rpm) is also installed.
installation program places in the /usr/lib64 directory.

Linux zSeries environment (64-bit)
requirements for installing Data Protection for Oracle in a Linux zSeries 64-bit
environment.
v SuSE Linux Enterprise Server 9
v A zSeries 900 or 800 server (64-bit)
v Disk space: 8 MB
Note: To view Data Protection for Oracle in a language other than English, you
must install the Tivoli Storage Manager Language package of the desired
language.
v TCP/IP

|
|
|
|
|
|
|
Installing Data Protection for Oracle on Linux zSeries 64-bit
All installable files reside under the /cdrom/oracle/linuxz64 directory.
Table 15. Linux zSeries (64-bit environment) Default Installation Directories
Linux zSeries
Utilities
Messages

Table 16. Data Protection for Oracle Linux zSeries (64-bit environment) and Tivoli Storage
Manager installable files and packages
Data Protection for Oracle Linux zSeries base
code, license, utilities
TDP-Oracle.s390x.bin
Data Protection for Oracle Languages TDP-Oracle.msg.xx_XX.s390x.bin
Tivoli Storage Manager API Linux zSeries TIVsm-API64.s390.rpm
Tivoli Storage Manager Languages TIVsm-msg.xx_XX.s390.rpm

for Oracle CD:

3. Mount /cdrom to the /cdrom directory on the Linux machine. The /cdrom
directory must already exist on the Linux machine:

1.
4. Change to the /cdrom/oracle/linuxz64 directory where the installation
$ cd /cdrom/oracle/linuxz64

$ rpm -i TIVsm-API.s390.rpm

6. Enter the name of the installable file (TDP-Oracle.s390x.bin) on the command
$ TDP-Oracle.s390x.bin

desired language (TDP-Oracle.msg.xx_XX.s390x.bin) on the command line and
press Enter:
$ TDP-Oracle.msg.xx_XX.s390x.bin

language (TIVsm-msg.xx_XX.s390.rpm) is also installed.
installation program places in the /usr/lib64 directory. This is the default
link:
/usr/lib64/libobk.so /opt/tivoli/tsm/client/oracle/bin64/libobk.so

|
|
|
|
Solaris
Solaris SPARC environment (32-bit)
requirements for installing Data Protection for Oracle in a Solaris SPARC 32-bit
environment.
One of the following levels of Solaris operating system:
v Solaris 9
v Solaris 10
v A SPARC 32-bit (or compatible) workstation.
v Disk space: 8 MB
v Memory: 96 MB
v Tivoli Storage Manager API Version 5.3.4
v Oracle9i Version 9.2 (32-bit)
Communication method
v TCP/IP

|
|
|
|
Installing Data Protection for Oracle on Solaris SPARC 32-bit
All installable files reside under the /cdrom/oracle/solaris directory.
Table 17. Solaris SPARC 32-bit Default Installation Directories
Solaris Default Installation Directories
Data Protection for Oracle 32-bit /opt/tivoli/tsm/client/oracle/bin
Utilities
Messages
32-bit
/opt/tivoli/tsm/client/api/bin

packages
license, utilities
TDPoracle32.bin
Data Protection for Oracle Languages TDPoracle32xx_XX.bin
Tivoli Storage Manager API 32-bit TIVsmCapi.pkg
Tivoli Storage Manager API Languages TIVsmClXx.pkg

Perform these instructions to install the Tivoli Storage Manager API, Data
Protection for Oracle, and the Data Protection for Oracle license package. This
example assumes that your CD drive is /cdrom and that you are installing the
Data Protection for Oracle 32-bit product.
1. Insert the CD containing the package into the CD drive.
$ pkgadd -d /cdrom/oracle/solaris/TIVsmCapi.pkg

4. Enter the name of the installable file (TDPoracle32.bin) on the command line
and press Enter to install Data Protection for Oracle:
$ TDPoracle32.bin

desired language (TDPoracle32xx_XX.bin) on the command line and press
Enter:
$ TDPoracle32xx_XX.bin

language (TIVsmClXx.pkg) is also installed.

a. Set the Oracle LD_LIBRARY_PATH option to specify $ORACLE_HOME/lib32 as
the first entry:
LD_LIBRARY_PATH=$ORACLE_HOME/lib32

c. Go to the $ORACLE_HOME/lib32 directory.
$ ln -s /usr/lib/libobk.so $ORACLE_HOME/lib32/libobk.so


Solaris SPARC environment (64-bit)
requirements for installing Data Protection for Oracle in a Solaris SPARC 64-bit
environment.
One of the following levels of Solaris operating system:
v Solaris 9 (64-bit)
v A SPARC 64-bit (or compatible) workstation
v Disk space: 8 MB
v Memory: 96 MB
v TCP/IP

|
|
|
|
Installing Data Protection for Oracle on Solaris SPARC 64-bit
All installable files reside under the /cdrom/oracle/solaris directory.
Table 19. Solaris SPARC 64-bit Default Installation Directories
Utilities
Messages
64-bit
/opt/tivoli/tsm/client/api/bin64

packages
license, utilities
TDPoracle64.bin
Data Protection for Oracle Languages TDPoracle64xx_XX.bin

Data Protection for Oracle 64-bit product.
$ pkgadd -d /cdrom/oracle/solaris/TIVsmCapi.pkg

4. Enter the name of the installable file (TDPoracle64.bin) on the command line
$ TDPoracle64.bin

desired language (TDPoracle64xx_XX.bin) on the command line and press
Enter:
$ TDPoracle64xx_XX.bin


the first entry:

$ ln -s /usr/lib/sparcv9/libobk.so $ORACLE_HOME/lib/libobk.so


Solaris x86 environment (32-bit)
requirements for installing Data Protection for Oracle in a Solaris x86 32-bit
environment.
The following level of Solaris operating system:
v Any Intel x86 (or compatible) 32-bit workstation.
v Disk space: 8 MB
v Memory: 96 MB
v TCP/IP

|
Installing Data Protection for Oracle on Solaris x86 32-bit
All installable files reside under the /cdrom/oracle/solarisx86 directory.
Table 21. Solaris x86 32-bit Default Installation Directories
Solaris x86
Utilities
Messages
Tivoli Storage Manager API /opt/tivoli/tsm/client/api/bin

Table 22. Data Protection for Oracle x86 32-bit and Tivoli Storage Manager installable files
and packages
license, utilities
TDPoraclex86.bin
Data Protection for Oracle Languages TDPoraclex86.xx_XX.bin

Data Protection for Oracle Solaris x86 32-bit product.
$ pkgadd -d /cdrom/oracle/solarisx86/TIVsmCapi.pkg

4. Enter the name of the installable file (TDPoraclex86.bin) on the command line
$ TDPoraclex86.bin

desired language (TDPoraclex86.xx_XX.bin) on the command line and press
Enter:
$ TDPoraclex86.xx_XX.bin


the first entry:

$ ln -s /usr/lib/libobk.so $ORACLE_HOME/lib/libobk.so


Solaris x86_64 environment
requirements for installing Data Protection for Oracle in a Solaris x86_64
environment.
The following level of Solaris operating system:
v Solaris 10 (x86_64) and any patches required by Oracle.
v Any Intel EM64T or Opteron AMD64 (or compatible) processor
v Disk space: 8 MB
v Memory: 96 MB
- Consult your Oracle documentation for details regarding support for
Release 1.
v TCP/IP

|
Installing Data Protection for Oracle on Solaris x86_64
All installable files reside under the /cdrom/oracle/solarisx86_64 directory.
Table 23. Solaris x86_64 Default Installation Directories
Solaris x86_64
Utilities
Messages

Table 24. Data Protection for Oracle x86_64 and Tivoli Storage Manager installable files and
packages
Data Protection for Oracle x64 base code,
license, utilities
TDPoraclex86_64.bin
Data Protection for Oracle Languages TDPoraclex86_64.xx_XX.bin
Tivoli Storage Manager API x64 TIVsmCapi.pkg

Data Protection for Oracle Solaris x86_64 product.
$ pkgadd -d /cdrom/oracle/solarisx86_64/TIVsmCapi.pkg

4. Enter the name of the installable file (TDPoraclex86_64.bin) on the command
$ ./TDPoraclex86_64.bin

desired language (TDPoraclex64.xx_XX.bin) on the command line and press
Enter:
$ TDPoraclex64.xx_XX.bin


|
|
|
|
the first entry:

$ ln -s /usr/lib/amd64/libobk.so $ORACLE_HOME/lib/libobk.so

or
$ ln -s /usr/lib/em64t/libobk.so $ORACLE_HOME/lib/libobk.so


|
|
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 and dsm.sys files.
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 63 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=/home/rman/scripts/tdpo.opt)
The TDPO_OPTFILE variable must be specified in upper case characters only. See
Scripts on page 51 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.
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. However, the TDPO_OPTFILE variable
must be specified in upper case characters only.

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). Note that if the Tivoli Storage Manager errorlogname
option is specified in the dsm.sys file (for the stanza used by Data
Protection for Oracle), the errorlogname option will override the value
specified by dsmi_log. If the errorlogname option is being used, make sure
that it specifies a file in a path that has write permissions.
For error log files, create a directory for the error logs and have the
dsmi_log option point to that directory. The user performing backups must
have writable rights to this directory.
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 If this option was set during Data Protection for Oracle backup
operations, this option must be set during restore and delete operations.
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_owner
This option specifies a session-owner name and object owner name. The
value can contain a string of 1 to 64 characters. This value is case sensitive.
For restore and delete operations, this option must specify the same value
that was used during the Data Protection for Oracle backup. Do not set
this option when passwordaccess generate is specified.
tdpo_pswdpath
This option specifies the directory where the TDPO.nodename password
file is located. The default value is the directory where Data Protection for
Oracle is installed. Note that when passwordaccess generate is specified,
Data Protection for Oracle uses the value of the passworddir option
specified in the dsm.sys file and does NOT use the tdpo_pswdpath option.
However, the directory specified by the passworddir option must be a
directory that is writeable by the Oracle user. The Oracle user is the User
ID of the target Oracle database instance.

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tdpo_node
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. It is recommended that you use a node name
that is different from the backup-archive client node name.
Be aware that it is the Tivoli Storage Manager API (and not Data Protection
for Oracle) that negotiates which login credentials (nodename, password)
to use with the Tivoli Storage Manager server. As a result, certain option
settings affect password management. For example, when the tdpo_node
option is specified (in the tdpo.opt file) and passwordaccess prompt is
specified (in the dsm.sys file), the Tivoli Storage Manager API uses the
value of the tdpo_node option and ignores the value of the nodename
option (specified in the dsm.sys file). However, when the tdpo_node option
is not specified and passwordaccess prompt is specified, the Tivoli Storage
Manager API attempts to automatically generate a password (by default),
even though passwordaccess prompt is specified. In this situation,
processing ends and an error message displays. To avoid receiving an error
message, make sure you follow these recommendations:
v When passwordaccess prompt is specified in the dsm.sys file, specify the
tdpo_node option in the tdpo.opt file.
v When passwordaccess generate is specified in the dsm.sys file, do NOT
specify the tdpo_node option in the tdpo.opt file.
To restore data from one Oracle server to another Oracle server using Data
Protection for Oracle, be aware of the following tdpo_node considerations:
v The value of the tdpo_node option in the tdpo.opt file on the target
Oracle server must equal the value of the tdpo_node option in the
tdpo.opt file on the source Oracle server.
v If passwordaccess prompt is specified for the backup, then
passwordaccess prompt must be specified for the restore. For example, if
passwordaccess prompt is specified in the dsm.sys file on the target
Oracle server, run the tdpoconf password command to create the
password locally on the source Oracle server.
v If passwordaccess generate is specified for the backup, then
passwordaccess generate must be specified for the restore. Be aware that
if the password for the Data Protection for Oracle node is unknown (due
to the passwordaccess generate setting), you can reset the password for
the production node on the Tivoli Storage Manager server. Then, after
the password is reset, use the new password to run the tdpoconf
password command on both the production machine (to set the
password for the next backup) and the alternate machine (to set the
password for the restore).
v Data Protection for Oracle and the Tivoli Storage Manager API must be
at the same levels on both the source Oracle server and the target Oracle
server.

Chapter 3. Configuring Data Protection for Oracle 41
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tdpo_date_fmt
This option specifies the format you want to use to display dates. You can
specify a number between 0 and 5 inclusively. The default value is 1.
0 Use the locale-specified date format.
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 1000,00
tdpo_time_fmt
This option specifies the format you want to use to display time. You can
specify a number between 0 and 4 inclusively. The default value is 1.
0 Use the locale-specified time format.
1 23:00:00 (Default)
2 23,00,00
3 23.00.00
4 12:00:00 A/P
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 52 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
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 system options file (dsm.sys) 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 and dsm.sys
files
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 system options
file (dsm.sys by default) and 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 The Tivoli Storage Manager client system options file (dsm.sys by default) must
be located in the directory where the Tivoli Storage Manager API is installed.
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 system options file
(dsm.sys by default) located in the directory where the Tivoli Storage Manager API
is installed:
passwordaccess
Specify whether you want to generate your password automatically or be
prompted to enter your password. You can specify one of the following
values:
prompt You are prompted to enter your password during each session.
This is the default value. When specifying passwordaccess prompt
in the dsm.sys file, set the following values in the tdpo.opt file:
tdpo_node <node name>
tdpo_owner <tdpo owner name>
tdpo_pswdpath (optional) <path to password file>

After specifying these values, use the tdpoconf password
command (as root user) to create the password and password file
(TDPO.nodename) on the local machine. Be aware that when
passwordaccess prompt is specified, the user must be aware of the
password expiration date. A backup failure may occur if the
password is allowed to expire. To allow the Tivoli Storage Manager
API to manage the password, specify passwordaccess generate.
generate
The Tivoli Storage Manager API manages all password actions
after the password is created using the tdpoconf password
command. The Tivoli Storage Manager API stores and manages the
password 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.
When specifying passwordaccess generate, set the following values
in the in the dsm.sys file:
passwordaccess generate
passworddir <directory owned and writable by Oracle owner>
nodename <node name>

However, do NOT specify the following options in the tdpo.opt file
when specifying passwordaccess generate:
v tdpo_node
v tdpo_owner
v tdpo_pswdpath
After specifying passwordaccess generate and the other appropriate
values in the dsm.sys file, run the tdpoconf password command
(as the Oracle user) to create the encrypted password in the
TSM.PWD file.
servername
Specify the name you want to use to identify a stanza that contains the
options used for connecting to the Tivoli Storage Manager server. Although
the name does not have to be the actual name of a Tivoli Storage Manager
server, the name must match the name specified by the servername option
in the dsm.opt file.
tcpserveraddress
Specify the TCP/IP address (in the stanza) 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.
Specify this option in the Tivoli Storage Manager client user options file (dsm.opt
by default) located in the directory specified by the dsmi_orc_config option:
servername
Specify a Tivoli Storage Manager server stanza name that matches the
name specified by the servername option in your client system options file
(dsm.sys by default) that is used to contact Data Protection for Oracle for
backup services.
Other options to consider
It is recommended that you specify these options in the Tivoli Storage Manager
client system options file, dsm.sys:
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.
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 Users Guide.
include
Add an include statement to the dsm.sys 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:
/FilespaceName//ObjectName
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.sys file (used by the Oracle node) would
be as follows:
INCLUDE /adsmorc/.../DB* mgmtclassnameforDBs
INCLUDE /adsmorc/.../LOG* mgmtclassnameforLogs

|
|
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 dsm.sys file.
For example, to enable transparent encryption, set the following options in
the client system options file, dsm.sys:
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 system options file, dsm.sys
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.
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.sys
file:
inclexcl /u01/oracle/include.def
2. Add this include entry to the /u01/oracle/include.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
Administrators 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 56 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.
Attention: For backup and restore operations in a Linux environment, Oracle
recommends that the Oracle LD_ASSUME_KERNEL variable be set for the Oracle
user. For example:
LD_ASSUME_KERNEL=2.4.21; export LD_ASSUME_KERNEL

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. The TDPO_OPTFILE variable must be specified in
upper case characters only.

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=/ora91/scripts/tdpo.opt);
ENV=(TDPO_OPTFILE=/ora91/scripts/tdpo.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=/home/oracle/tdpo.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 Administrators 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 53
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
ENV=(TDPO_OPTFILE=/orc91/scripts/tdpo.opt);

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.
Be aware of the following requirements based on the value of the passwordaccess
setting in the dsm.sys file:
passwordaccess prompt
Run the tdpoconf password command as the root user. This command
creates an encrypted password file, TDPO.Nodename. The Nodename value
will be the value specified by the tdpo_node option in the Data Protection
for Oracle options file specified with the TDPO_OPTFILE variable. This
file is located in the directory specified by the tdpo_pswdpath option. If
the tdpo_pswdpath option is not specified, the TDPO.Nodename file is
placed in the Data Protection for Oracle installation directory. Make sure
that the TDPO.Nodename file can be read by the Oracle user that performs
the backup.
Run the tdpoconf password command as the Oracle user. The password is
placed in the file, TSM.PWD, and is owned by the Oracle user. This
TSM.PWD file is created in the directory specified by the passworddir
option defined in the dsm.sys file. Do not specify the tdpo_node option in
the tdpo.opt file. Data Protection for Oracle uses the value of the nodename
option specified in the dsm.sys file.
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 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.

Chapter 5. Using the utilities 57
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
Below is an output example of the tdpoconf showenvironment command:
DATA PROTECTION FOR ORACLE INFORMATION
Version: 5
Release: 4
Level: 1
Sublevel: 0
Platform: 32bit TDPO Linux86

TSM SERVER INFORMATION
License Information: License file exists and contains valid license data
Server Name: TSMSERVER
Server Type: AIX-RS/6000
Server Address: SERVER.MYSITE.COMPANY.COM
Server Port: 1500
Communication Method: TCP/IP

SESSION INFORMATION
Owner Name: oracle10g
Node Name: AGENT_NODE
Node Type: TDPO Linux86
DSMI_DIR: /opt/tivoli/tsm/client/api/bin
DSMI_ORC_CONFIG: /opt/tivoli/tsm/client/api/bin/dsm.opt
TDPO_OPTFILE: /opt/tivoli/tsm/client/oracle/bin/tdpo.opt
Compression: TRUE
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 60 and PICK Window on page 61 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 60.
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 that
exists on your node. 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
This is an output example of the tdposync syncdb command:
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
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 (/fs//backup file name)
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:
Node Name: AGENT_NODE
Owner Name: oracle10g

Backup Date Size Backup Name
----------------------------------------------------------------
1. | 01/09/2007 09:19:59 108.01MB /adsmorc//1kc2cnfv_1_1
2. | 01/02/2007 11:36:20 56.25MB /adsmorc//4kc3cnfv_1_1
3. | 01/02/2007 07:14:30 102.00MB /adsmorc//4qcgdhfr_1_1
4. | 01/02/2007 07:21:38 78.10MB /adsmorc//4ocf8999_1_1
5. | 01/09/2007 11:00:11 10.99MB /adsmorc//4ocf8999_1_2
6. | 01/09/2007 11:00:12 32.07MB /adsmorc//4ocf8999_1_3
7. | 01/09/2007 11:00:13 623.90MB /adsmorc//4rch25jk_1_1
8. | 01/09/2007 11:00:14 441.61MB /adsmorc//4rch25jk_1_2
9. | 01/09/2007 11:00:15 10.18MB /adsmorc//4rch25jk_1_3
|
|
|
|
|
0--------10-------20-------30-------40-------50-------60-------70
<U>=Up =Down <T>=Top <B>=Bottom <R>=Right <L#>=Left
<G#>=Goto Line # <#>=Toggle Entry <+>=Select All <->=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 an AIX 64-bit 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. Note that you must change the installation paths and library
extensions documented in this procedure if you are using an operating system
other than AIX 64-bit. See page 39 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. Make sure the following link exists:
$ORACLE_HOME/lib/libobk.a -> /usr/lib/libobk64.a

3. Change to the /usr/tivoli/tsm/client/oracle/bin64 directory and copy the
tdpo.opt.smp file to tdpo.opt. Edit the tdpo.opt file to include these options:
dsmi_orc_config /usr/tivoli/tsm/client/oracle/bin64/dsm.opt
dsmi_log <directory with write permissions>

v More information about these options is available on page 40.
4. In this same directory, create a dsm.opt file. Edit the dsm.opt file to include
the following server stanza:
SErvername tdpo

v More information about this option and the dsm.opt file is available on
page 44.
5. Change to the /usr/tivoli/tsm/client/api/bin64 directory and create a
symbolic link to /usr/tivoli/tsm/client/ba/bin/dsm.sys. Edit the dsm.sys
file to include another server stanza with the following options:
SErvername tdpo
COMMMethod TCPip
TCPServeraddress x.x.x.x
PASSWORDAccess generate
passworddir /home/<oracle user>
nodename TDPONodeName

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. Replace <oracle user> with
the Oracle User ID of the target Oracle database instance.
v More information about the dsm.sys file, these options, and their
relationship with Data Protection for Oracle is available on page 44.
6. Register the node to the Tivoli Storage Manager server with the following
command:
REG NODE hostname_oracle password maxnummp=2
Where hostname is the name of the machine where Data Protection for Oracle
is installed and password is the password for this node.

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7. Make sure the Oracle user has the following permissions:
v Read (r) permission to the /usr/tivoli/tsm/client/oracle/bin64 and
/usr/tivoli/tsm/client/api/bin64 directories.
v Read permission (r-) to the tdpo.opt, dsm.opt, and dsm.sys files located in
the /usr/tivoli/tsm/client/oracle/bin and /usr/tivoli/tsm/client/api/
bin directories.
8. Change to the /usr/tivoli/tsm/client/oracle/bin64 directory and run the
tdpoconf password command (as Oracle user) to generate the password file.
v More information about this command is available on page 56.
9. Run the tdpoconf showenvironment command to confirm proper
configuration.
v More information about this command is available on page 57.
10. As Oracle user, run your RMAN backup script with the
ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)
parameter specified.
For example:
run
{
ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.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 51.

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 backuparchive 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 an AIX, HP-UX, Linux, or Solaris scheduler
backup script (schedbkdb.scr) 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 machine where Data Protection for Oracle is installed:
a. Create a single dsm.sys file from which to associate nodes for your client,
Data Protection for Oracle, and scheduled backups.
b. Create the scheduler backup script (schedbkdb.scr). This is the script that
the Tivoli Storage Manager scheduler invokes directly.
c. Create a command script (mysched.scr). This is the script that contains the
Oracle environment information and invokes the RMAN backup script.
d. Create the RMAN backup script (bkdb.scr). This is the script that actually
performs the Oracle RMAN backup.
e. Start the scheduler.
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="08Daily Online DB Backup"
action=command objects="/usr/tivoli/tsm/client/oracle/sched/schedbkdb.scr"
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 will run the scheduler backup script (schedbkdb.scr),
which will run the command script (mysched.scr), which will run the RMAN
backup script (bkdb.scr) located in the /home/oracle/sched 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 client machine (NodeA1)
This example assumes:
v The Tivoli Storage Manager backup-archive client is installed on NodeA1 in the
/usr/tivoli/tsm/client/ba/bin directory.
v Data Protection for Oracle is installed on NodeA1 in the /usr/tivoli/tsm/
client/oracle/bin64 directory.
v An AIX operating system is used.
It is recommended that the password expiration for the Data Protection for Oracle
node (NodeA1) be set to not expire. Otherwise the password will become out of
sync between Data Protection for Oracle and the scheduler. This can be done by
specifying passwordaccess generate. However, if passwordaccess prompt is already
specified, you can prevent password expiration by issuing the following command:
update node NodeA1 passexp=0
Scheduling Data Protection for Oracle backups with the Tivoli Storage Manager
scheduler requires special configuration issues to be addressed. This procedure
addresses this issue by creating a dsm.sys file from which to associate nodes for
your client, Data Protection for Oracle, and scheduled backups:
1. Create a dsm.sys file in the /usr/tivoli/tsm/client/ba/bin directory (if one
does not already exist) and add the following servername stanzas:

|
|
|
|
|
|
|
|
|
|
a. Add a servername stanza for the file system backups associated with your
Tivoli Storage Manager backup-archive client.
For example:
servername TSMbackup
commmethod tcpip
tcpserveraddress site.xyzinc.com
tcpport 1500
nodename client
The servername TSMbackup setting must be specified in the dsm.opt file
associated with the Tivoli Storage Manager backup-archive client. The
default directory location is /usr/tivoli/tsm/client/ba/bin.
b. Add a servername stanza for the backups associated with Data Protection
for Oracle.
For example:
servername TSMOracle
commmethod tcpip
tcpport 1500
nodename NodeA1
Replace <oracle user> with the Oracle User ID of the target Oracle database
instance.The servername TSMOracle setting must be specified in the dsm.opt
file associated with Data Protection for Oracle. The default directory
location is /usr/tivoli/tsm/client/oracle/bin64. This dsm.opt file can
have a unique name, such as dsmoracle.opt. Make sure the dsmi_orc_config
option specifies the user options file (dsmoracle.opt in Step 1b) associated
with Data Protection for Oracle. For example:
dsmi_orc_config /usr/tivoli/tsm/client/oracle/bin64/dsmoracle.opt
c. Add a servername stanza for the scheduled backups associated with Data
For example:
servername DPSched
commmethod tcpip
tcpport 1500
nodename NodeA1
Replace <oracle user> with the Oracle User ID of the target Oracle database
instance.
2. Make sure there is a symbolic link to this dsm.sys file so that the file is
available to the Tivoli Storage Manager API directory (/usr/tivoli/tsm/
client/api/bin64).
3. Create the scheduler backup script (schedbkdb.scr) in the /usr/tivoli/tsm/
client/oracle/sched/ directory. This is the scheduler backup script that was
defined for the scheduler in Step 1 in Part I: On the Tivoli Storage Manager
server on page 66. This scheduler backup script will run the command script
(mysched.scr), which will run the RMAN backup script (bkdb.scr). This is an
example of the scheduler backup script (schedbkdb.scr):
#!/bin/ksh
su - OracleUser -c /home/oracle/sched/mysched.scr

Appendix B. Using the Tivoli Storage Manager scheduler 67
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4. Create the command script (mysched.scr) in the /home/oracle/sched/ directory.
This is an example of the command script (mysched.scr):
#!/bin/ksh
export ORACLE_HOME=/orc91/app/oracle/product/912
export PATH=$ORACLE_HOME/bin:$PATH
rman target agnttest/agnttest@target rcvcat rman/rman@rman
cmdfile /home/oracle/sched/bkdb.scr msglog /home/oracle/sched/bkdb.log
You must place the command text, rman target agnttest/agnttest@target
rcvcat rman/rman@rman and cmdfile /home/oracle/sched/bkdb.scr msglog
/home/oracle/sched/bkdb.log, on the same line in this command script. The
command text is placed on two lines in this example to accommodate page
formatting.
5. Create the RMAN backup script (bkdb.scr) in the /home/oracle/sched/
directory. This is an example of the RMAN backup script (bkdb.scr):
run {
ENV=(TDPO_OPTFILE=/home/oracle/sched/tdpo.opt);
ENV=(TDPO_OPTFILE=/home/oracle/sched/tdpo.opt);

backup
format df_%t_%s_%p_%u_%c
(database); }
6. Login as the root user to the machine where Data Protection for Oracle is
installed as node name NodeA1.
7. Start the scheduler in the inittab. Use the servername parameter to specify the
correct stanza to use in the dsm.sys file:
dsmc sched -servername=DPSched
Data Protection for Oracle is now enabled for scheduled backups.

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 71
v Obtaining fixes on page 71
v Receiving weekly support updates on page 72
v Contacting IBM Software Support on page 72
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. Verify that the Oracle target database instance is symbolically linked with Data
Protection for Oracle:
a. Log in as the Oracle user.
b. Run the following command:
$ ls -al $ORACLE_HOME/lib/libobk.a

Look for the libobk link(s) in the system's respective 32-bit or 64-bit library
directory.
c. Verify that the link points to a file that exists. For example:
$ORACLE_HOME/lib/libobk.a -> /opt/tivoli/tsm/client/oracle/bin64/libobk64.a

or
$ORACLE_HOME/lib/libobk.so -> /usr/lib/sparcV9/libobk.so
/usr/lib/sparcV9/libobk.so -> /opt/tivoli/tsm/client/oracle/bin64/libobk64.so

Make sure that the final link destination is the correct bit level and points to
a file that exists.
6. 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 dsm.sys 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.sys file.
The value of the dsmi_log environment variable. Make sure dsmi_log
(specified in the tdpo.opt file) specifies a directory with Read/Write
permissions for the Oracle user. By default, the dsmi_log environment
variable specifies a directory owned by root.
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.sys file. Make sure errorlogname specifies a directory
and file name with Read/Write permissions for the Oracle user.
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 /home/oracle/rman/tsmapi.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 /home/oracle/rman/tdpo.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.

Appendix C. Support information 71
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.
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 on page 74
3. Submitting problems on page 74
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 running the following commands:
AIX:
lslpp -L "tivoli.tsm.*"
You can also enter the what /usr/lib/libobk.a command
HP-UX:
swlist -v <Data Protection for Oracle installable file>
swlist -v TIVsmCapi
You can also list all Tivoli package names with this command:
swlist | grep Tivoli
Linux:
rpm -qa "TDP*"
rpm -qa "TIVsm-API*"
Solaris:
pkginfo -l <Data Protection for Oracle installable file>
pkginfo -l TIVsmCapi
You can also list all Tivoli package names with this command:
pkginfo -l | grep Tivoli
You can also enter the what /usr/lib/libobk.so command.
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?
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
occurred.
Explanation: An internal processing error has
occurred.
System action: Processing ends.
User response: Retry the operation. If this error
persists, contact your service representative.
ANU0004E An unknown error has been detected.
Explanation: An internal processing error has
occurred that prevents the generation of a message for
a return code.
System action: Processing continues.
User response: Retry the operation. If this error
persists, contact your service representative.
ANU0005E Out of memory. Stop other processes
and try the operation again.
Explanation: The machine has run out of memory.
User response: Close unnecessary processes and try
the operation again.
ANU0053E License file (licensefile) could not be
opened.
Explanation: An attempt to read from the license file
failed.
User response: Install the product again. This ensures
that the correct license file is installed.
ANU0054E Read failure on license file (licensefile).
Explanation: An attempt was made to read from the
license file. This attempt failed.
User response: Reinstall the product. This will ensure
that the correct license file is installed.
ANU0055E Write failure on license file (licensefile).
Explanation: An attempt to write to the license file
failed.
User response: Make sure enough space exists on the
workstation to write to the license file. If enough space
exists, run the command again.
ANU0056E Data in the license file (licensefile) is not
in a valid format.
Explanation: An attempt to read information from the
license file failed.
User response: Install the product again.
ANU0057E The checksum in the license file
(licensefile) does not match the license
string text.
Explanation: An attempt was made to read
information from the license file. The checksum was
not valid so it appears that the license file is not at the
correct level.
User response: Reinstall the product.
ANU0058E The Try and Buy license has expired.
Explanation: This Try and Buy license that was
detected has expired.
User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
ANU0100E Incomplete command:
Explanation: This message displays the incomplete
command that was entered.
User response: Re-enter the complete command.
ANU0101E Invalid argument:
Explanation: This message displays the command that
was entered, up to and including the invalid command
or option argument that was detected.
User response: Re-enter the command specifying a
valid argument for the command or option.
ANU0102E Invalid command:
Explanation: This message displays the invalid
command that was entered.
User response: Re-enter a valid command.
ANU0103E Invalid option for the specified
command:
was entered, up to and including the option that was
detected as invalid for the command.
User response: Re-enter the command specifying valid
command options.
ANU0104E Invalid option:
was entered, up to and including the invalid option
that was detected.

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

ANU0156E Could not load the Tivoli Storage
Manager API.
Explanation: The Tivoli Storage Manager API could
not be loaded.
User response: Ensure the Tivoli Storage Manager API
is correctly installed. Run the Data Protection for Oracle
application client with the /TRACEFLAGS=API
/TRACEFILE=filename options and view the tracefile
to determine why it could not be loaded. Another
possible cause is that the TSMAPI.DLL does not exist in
the system directory. Re-install the Tivoli Storage
Manager API, if this is the case.
ANU0160E An authentication error occurred with
your stored Tivoli Storage Manager
password.
Explanation: You were unable to log on to the Tivoli
Storage Manager server due an authentication error.
System action: Processing stops.
User response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your
Tivoli Storage Manager server administrator.
ANU0161E Authentication error. The password
entered is not valid. You are not logged
on to the Tivoli Storage Manager server.
Explanation: An incorrect password was entered.
User response: Enter the correct Tivoli Storage
Manager password and try again.
ANU0162E The passwords entered do not match.
Please enter them again.
Explanation: An incorrect password was entered.
User response: Enter the passwords again.
ANU0163E The directory path needs to be
fully-qualified.
Explanation: The /intopath option was specified
without a fully-qualified path.
User response: Enter the command again and specify
a fully-qualified path in the /intopath option.
ANU0167E The fully-qualified file name is too
long.
Explanation: An attempt was made to use a
fully-qualified file name that was too long. This
attempt failed.
User response: None
ANU0200E File (filename) could not be opened for
reading.
Explanation: An attempt was made to open a file for
reading. This attempt failed.
User response: None
ANU0201E File (filename) could not be opened for
writing.
Explanation: An attempt was made to open a file for
writing. This attempt failed.
User response: None
ANU0202E Read failure on file (filename).
Explanation: An attempt was made to read from a
file. This attempt failed.
User response: None
ANU0203E Write failure on file (filename).
Explanation: An attempt was made to write to a file.
This attempt failed.
User response: None
ANU0204E File (filename) could not be closed.
Explanation: An attempt was made to close a file.
User response: None
ANU0205E File (filename) statistics could not be
obtained.
Explanation: An attempt was made to obtain file
statistics. This attempt failed.
User response: None
ANU0206E Directory (directory) could not be created.
Explanation: An attempt was made to create a
directory. This attempt failed.
User response: None
ANU0207E Directory path (directorypath) is too long.
Explanation: An attempt was made to use a directory
path that was too long. This attempt failed.
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 81
User response: None
ANU0209E The rename of file (filename1) to
(filename2) failed.
Explanation: An attempt was made to rename a file.
User response: None
ANU0210E The Tivoli Storage Manager high level
qualifier is too long.
Explanation: An attempt was made to use a Tivoli
Storage Manager high level qualifier that was too long.
User response: None
ANU0211E The Tivoli Storage Manager low level
qualifier is too long.
Storage Manager low level qualifier that was too long.
User response: None
ANU0212E The Tivoli Storage Manager filespace
name is too long.
Storage Manager filespace name that was too long. This
attempt failed.
User response: None
ANU0213E The maximum number of objects
allowed per Tivoli Storage Manager
transaction is t oo small.
Explanation: In order to maintain backup data
integrity, multiple backup objects are sent to the Tivoli
Storage Manager server in a single transaction. The
Tivoli Storage Manager server has indicated that the
maximum number of objects allowed per transaction is
less than the minimum required by the Data Protection
for Oracle application client.
User response: Increase the maximum number of
objects allowed per transaction on the Tivoli Storage
Manager server and retry the operation.
ANU0214E The backup objects management class
backup copy group does not exist.
Explanation: The Tivoli Storage Manager server has
indicated that the backup objects management class
backup copy group does not exist.
User response: Contact your Tivoli Storage Manager
server administrator.
ANU0215E All backup objects do not have the same
management class backup copy
destination.
Explanation: In order to maintain backup data
integrity, multiple backup objects are sent to the Tivoli
Storage Manager server within a single transaction. All
backup objects within a single transaction are required
to have the same management class backup copy
destinations.
User response: Contact your Tivoli Storage Manager
server administrator.
ANU0216E Unable to obtain space information for
volume (volumename).
Explanation: An attempt was made to obtain space
information for a volume. This attempt failed.
User response: None
ANU0217E The Tivoli Storage Manager filespace
name is invalid.
Explanation: The filespace name or directory
delimeter is invalid.
User response: Check that the filespace name length,
characters, and directory delimeters are valid.
ANU0218E The Tivoli Storage Manager high level
qualifier is invalid.
Explanation: The high level qualifier name or
directory delimeter is invalid.
User response: Check that the high level qualifier
name length, characters, and directory delimeters are
valid.
ANU0219E The Tivoli Storage Manager low level
qualifier is invalid.
Explanation: The low level qualifier name or directory
delimeter is invalid.
User response: Check that the low level qualifier
name length, characters, and directory delimeters are
valid.
ANU0256E The password in your Tivoli Storage
Manager options file has expired. Please
change your password on the Tivoli
Storage Manager server using the
change password command and then
either change or remove the password
value in your options file.
Explanation: Your Tivoli Storage Manager password
has expired. You need to change your password.
User response: Obtain a new password for your Tivoli
Storage Manager server; node using the change

password command or by asking your Tivoli Storage
Manager Administrator to change your password.
ANU0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password
has expired. A new password needs to be obtained.
User response: Obtain a new password for your Tivoli
Storage Manager node using the change password
command or by asking your Tivoli Storage Manager
Administrator to change your password.
ANU0258E You did not enter a valid password.
Processing ends.
Explanation: The password that was entered was not
a valid password.
valid password.
ANU0259E The password you entered for
verification does not match the
password you entered for your new
password. Your password will not be
changed.
Explanation: The password you entered for
verification of your new password does not match the
new password that was entered.
User response: Try again to change your password
being sure to enter the same password for the new
password and for the verification password.
ANU0260I Password successfully changed.
Explanation: The change password command
completed successfully
User response: None
ANU0261I There are no backups for the server
named servername.
Explanation: There are no backups on the Tivoli
Storage Manager server for the specified server name.
User response: None
ANU0263E Failed to start Web browser with a
return code of returncode.
Explanation: An attempt was made to start the web
browser to view the TSM HTML b ook. This attempt
failed.
User response: Start your web browser manually and
point it to bookfrm.htm in the agent htm directory.
ANU0264I Could not find the default browser
defined. An attempt will be made to use
Microsoft Internet Explorer.
registry to determine the default browser. However, a
default browser is not defined. A determination will be
made where Microsoft Internet Explorer is installed.
User response: It is possible that a default browser is
not defined for the system. This is okay. An attempt
will be made to use Microsoft Internet Explorer.
ANU0265E Could not find Internet Explorer.
registry to determine where Microsofts Internet
Explorer was installed. This attempt failed.
User response: Make sure that the registry is set up
correctly for Internet Explorer.
ANU0266E Could not find the Tivoli Storage
Manager HTML books.
registry to determine where the Tivoli Storage Manager
books were installed. This attempt failed.
User response: It may be necessary to reinstall the
application client code. This will ensure that the
registry entries are set up correctly.
ANU0267E The verify password entered does not
match the new password entered.
Explanation: The verify password does not match the
new password.
User response: Retry the command with a matching
verify password.
ANU0300E Invalid restore type.
Explanation: The type of restore requested is invalid.
valid restore type.
ANU0301E Invalid backup type.
Explanation: The type of backup requested is invalid.
valid backup type.
ANU351E Invalid trace keyword - keyword
Explanation: A TRACEFLAG option in the user
configuration file or on the command line is incorrect.
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
file-name.
Explanation: A TRACEFILE option in the user
configuration file or on the command line used a
directory path and file-name combination to which you
do not have write access.
System action: Client program did not initialize.
User response: Change the TRACEFILE value so that
it is a location to which you have write access.
ANU366E Unable to close trace output file
file-name.
Explanation: An error occurred during the closing of a
trace output file-name (for example, not enough disk
space).
User response: Check the options.doc file for a
description of possible causes of the error, or see your
system administrator.
ANU367E Unable to write to trace file tracefile.
Tracing disabled.
Explanation: An error occurred when writing to the
specified tracefile.
System action: Tracing is disabled. Processing
continues.
User response: Ensure the device that the tracefile
access is available and has sufficient space for the
tracefile. Retry the command.
ANU368E Invalid trace file name (name too long).
Explanation: A TRACEFILE option in the preferences
files used a file name that is too long.
System action: Client program did not initialize.
User response: Change the file name used as the
TRACEFILE so that it is equal to or less than 255
characters in length.
ANU383E Specifying the trace file link as a
symbolic link is not allowed.
Explanation: Trace file linkname cannot be a symbolic
link.
System action: The symbolic link linkname is deleted,
the trace file is recreated, and processing stops.
User response: Specify the trace file location with the
tracefile option.
ANU384E Symbolic link linkname to target was
successfully deleted.
Explanation: Log linkname cannot be a symbolic link.
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 users
manual for the errorlogname option, the
schedlogname option, and the DSM_LOG
environmental variable.
ANU385E Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link.
User response: Delete the symbolic link linkname.
ANU476E program-name: cannot open file file-spec:
error.
Explanation: TDP cannot open the file.
System action: TDP cannot complete the requested
operation.
User response: Retry the operation. If the problem
continues, check with your system administrator.
ANU487E Specifying the error log link as a
symbolic link is not allowed.
Explanation: Error log linkname cannot be a symbolic
link.
the error log is recreated, and processing stops.
User response: Check the location of the new error
log. To specify the location of the error logs, refer to the
users manual for the errorlogname option and
DSM_LOG environmental variable.
ANU488E Initialization functions cannot open the
error log: log-name. errno = errno-value,
Explanation: The file log-name could not be opened
during initialization. The system set the error code
errno-value. If the reason given is access denied, the
current user does not have permission to write to the
log in the directory specified. It is also possible that no
space is available at the given log location.
System action: Processing terminates.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the
current user can write. You may also use the
ERRORLOGNAME option to specify a file to which the
current has write permission.
ANU495E Failure writing to a Tivoli Storage
Manager log or log-related file: file-name,
errno = errno-value, reason
Explanation: A failure was encountered when writing
to one of the log files or a related file named file-name.
The system set the error code errno-value. reason is the
system explanation of that error code. Among other
things, it is possible that no space is available at the
given log location.
System action: Processing terminates.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory with adequate
space to write the log data.

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

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

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

procedure.
User response: Check to ensure that the file named in
the error exists in the path specified and that the file
named has read permissions. Take the necessary
corrective action and try operation again.
ANU2600E There is no Registry entry for the TSM
API.
Explanation: The Windows Registry entry was not
found.
procedure.
User response: Check that the TSM API is installed
correctly.
ANU2601E There is no Registry entry for the Data
Protection for Oracle install path.
Explanation: The Registry Entry for the Data
Protection for Oracle install path was not found.
procedure.
User response: Check that Data Protection for Oracle
was installed correctly.
ANU2602E The object Filespace NameHigh Level
NameLow Level Name was not found on
the TSM Server
Explanation: The object name was not found on the
TSM Server.
procedure.
User response: Check that the object name is correct
and that it exists on the TSM Server.
ANU2603E The option Option Name in file Filename
is invalid.
Explanation: An incorrect option was passed into the
Data Protection for Oracle options file.
procedure.
User response: Verify that your options are correct in
the Data Protection for Oracle options file.
ANU2614E Invalid sequence of function calls to
Explanation: Data Protection for Oracle received a
function call from Oracle that is out of sequence.
System action: Data Protection for Oracle returns to
the calling procedure.
User response: Contact Oracle or Data Protection for
Oracle support.
ANU2615E Options file filename not found.
Explanation: The option file name specified could not
be located.
procedure.
User response: Ensure that an option file exists in the
default path or that the user specified option file is
valid.
ANU2616E Empty parameter specified for option
option in options file filename.
Explanation: The option specified must have a
parameter supplied.
procedure.
User response: Ensure that a valid parameter for the
given option is entered and valid.
ANU2620E Attempting to create or modify Data
Protection for Oracle prompted
password as non-root user.
Explanation: According to the settings in your Data
Protection for Oracle options file you are attempting to
authenticate using passwordaccess=prompt as a
non-root user. Root access is needed to modify the Data
Protection for Oracle password file.
procedure.
User response: To create or modify the Data
Protection for Oracle password file, switch to the root
user and re-run the Data Protection for Oracle
password configuration utility.
ANU2621E Attempting to create or modify Data
Protection for Oracle generated
password as root user.
Explanation: According to the settings in your Data
Protection for Oracle options file the TDPO_NODE is
not defined which indicates that you are attempting to
authenticate using passwordaccess=generate. As a root
user this is not allowed.
procedure.
User response: If you intend to use
passwordaccess=prompt method of authentication
please modify the Data Protection for Oracle and set
TDPO_NODE to a valid registered TSM node and
re-run the password configuration utility as root user.
ANU2622E One or more option parameters contain
invalid values.
Explanation: An invalid parameter value was
specified at the command-line.
procedure.
User response: Check the Users 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 Users 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 users 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
AS/400
DB2
DFS
DFSMS/MVS
DFSMShsm
DFSMSrmm
DPI
Enterprise Storage Server
ESCON
eServer
FICON
FlashCopy
HACMP
Informix
iSeries
Lotus
Lotus 1-2-3
Lotus Approach
Lotus Domino
Lotus Notes
Magstar
MVS
NetView
OpenEdition
OS/2
OS/390
OS/400
Passport Advantage
pSeries
RACF
Rational
Redbooks
RS/6000
S/390
SANergy
SecureWay
StorageSmart
SystemView
Tivoli
Tivoli Enterprise Console
Tivoli Management Enterprise
TotalStorage
TME
VTAM
WebSphere
z/OS
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 93
Index
A
accessibility x
AIX 5L 32-bit
options 40
AIX 5L 64-bit
communication methods 6
disk space requirements 6
hardware requirements 6
installation instructions 7
installation requirements 6
memory requirements 6
operating system requirements 6
options 40
software requirements 6
archive copy group 48
B
backdelete
and backup removal 54
and Data Protection for Oracle
node 43
and Tivoli Storage Manager
policy 48
backup copy group values 47
backups
automating 65
removing 54
bkdb.log 51
bkdb.scr
and the Tivoli Storage Manager
scheduler 65, 66, 68
books
see publications ix
C
command line syntax
characteristics 55
commands
Oracle
change 54
tdpoconf password 56
tdpoconf showenvironment 57
tdposync
syncdb 60
Tivoli Storage Manager server
query actlog 70
query association 66
query node 53, 70
query schedule 66
commmethod
description 45
communication methods
AIX 5L 64-bit 6
HP-UX Itanium 2 64-bit 12
HP-UX PA-RISC 64-bit 9
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
communication methods (continued)
Linux zSeries 64-bit 23
Solaris SPARC 32-bit 26
Solaris x86 32-bit 32
Solaris x86_64 35
compression 45
conventions
typeface x
customer support
See Software Support
D
and Oracle databases 51
configuring 44
generating trace file 70
installation requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
installing 5
overview 2
recommendations 59
Recovery Manager (RMAN) 2
reporting problems 69
supported Oracle versions 2
Tivoli Storage Manager policy
requirements 47
version migration 3
disk space requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
dsierror.log
problem determination 69
dsm.opt
description 44
required options 45
dsm.sys
description 44
recommended options 45
required options 44
dsmi_log 40
dsmi_orc_config 40
scheduler 67
duplex copy
considerations 53
overview 52
E
education
see Tivoli technical training ix
enablelanfree 46
examples
duplex copy 52
include/exclude 48
invoking RMAN 51
removing backups 54
RMAN scripts 52
tdpoconf password command 57
tdpoconf showenvironment
command 58
tdposync syncdb command 61
pick window 61
Tivoli Storage Manager scheduler 65
expiration of objects 47
F
fixes, obtaining 71
H
hardware requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
HP-UX Itanium 2 64-bit
options 40
HP-UX PA-RISC 64-bit

HP-UX PA-RISC 64-bit (continued)
options 40
I
inclexcl
policy 48
include
and duplex copy 53
policy 48
description 46
information centers, searching for
problem resolution 71
installation
instructions
AIX 5L 64-bit 7
Linux on POWER 21
Linux x86 32-bit 16
Linux x86_64 18
node name registration 43
Solaris x86_64 36
requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
Internet
searching for problem resolution 71
K
knowledge bases, searching for problem
resolution 71
L
LAN-free data transfer
description 3
options 46
Linux on POWER
Linux on POWER (continued)
options 40
Linux x86 32-bit
Linux x86_64
options 40
Linux zSeries 64-bit
options 40
M
management class
for automatic expiration 47
using 54
manuals
see publications ix
maxnummp 53
memory requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
migration considerations 3
N
node name
registration 43
nodename 44
numcatalogs
and tdposync syncdb command 60
O
online publications
accessing ix
operating system requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17
Solaris x86_64 35
options 40
ordering publications ix
outfile
and tdpoconf showenvironment
command 57
P
passwordaccess 44
pick window 61
policy domain 47
problem determination
describing problems 74
determining business impact 73
guidelines 69
submitting problems 74
publications
accessing online ix
ordering ix
R
readmedporc_enu.htm 5
retonly
policy 47
RMAN
description 2
invoking 51
scripts 51
S
schedbkdb.scr 67
scripts 51
servername
and dsm.opt 45
and dsm.sys 45
scheduler 66, 68
set duplex 53
software requirements
AIX 5L 64-bit 6
Linux on POWER 20
Linux x86 32-bit 15
Linux x86_64 17

software requirements (continued)
Solaris x86_64 35
Software Support
contacting 72
describing problems 74
determining business impact 73
receiving weekly updates 72
submitting problems 74
Solaris SPARC 32-bit
options 40
Solaris SPARC 64-bit
options 40
Solaris x86 32-bit
options 40
Solaris x86_64
options 40
T
tcpserveraddress 45
tdpo_date_fmt 42
tdpo_fs 40
tdpo_mgmt_class_2 42
tdpo_node 41
tdpo_num_fmt 42
TDPO_OPTFILE
and tdpoconf password command 56
and tdpoconf showenvironment
command 57
and tdposync syncdb command 60
TDPO_OPTFILE (continued)
example 39
tdpo_owner 40
tdpo_pswdpath 40
tdpo_time_fmt 42
tdpo_trace_file 71
tdpo.opt
and version migration 3
description 39
tdpoconf
and password initialization 49
and tdpo.opt 39
description 56
for problem determination 69
password command 56
example 57
syntax diagram 56
TDPO_OPTFILE 56
showenvironment command 57
example 58
outfile 57
syntax diagram 57
TDPO_OPTFILE 57
tdpoerror.log
how to specify 40
tdposync
and tdpo.opt 39
considerations 59
description 58
syncdb command 60
example 61
numcatalogs 60
pick window 61
syntax diagram 60
TDPO_OPTFILE 60
Tivoli software information center ix
functions 1
management class 48
policy requirements 47
scheduler 65
services 1
Tivoli Storage Manager API trace file 70
Tivoli technical training ix
trace file, generating 70
tracefile 71
training, Tivoli technical ix
typeface conventions x
V
verdeleted
policy 47

Index 97
Program Number: 5608-APD

Printed in USA

SC32-9064-03

IBM Tivoli Storage Manager For Databases Data Protection For Oracle For UNIX and Linux Installation and User's Guide Version 5.4.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBM Tivoli Storage Manager For Databases Data Protection For Oracle For UNIX and Linux Installation and User's Guide Version 5.4.1

Uploaded by

Copyright:

Available Formats

Tivoli Storage Manager

Tivoli Storage Manager

publications online and how to order Tivoli publications.

, pSeries, or Power 5 (or compatible) processor

v Forums and newsgroups

operating systems), enroll in Passport Advantage

software products (including, but not limited to, DB2 and

Program Number: 5608-APD

You might also like